Search results

Yeah; it should work fine on a G4 iMac. The Mini's from late 2005; the last G4 iMac is from 2004. The one I think you're talking about is from 2002 and could boot natively into 9.2.2, which means you can just toss the CHRP ROM and the System Enabler into a System 7.5.0 System Folder (on an HFS...

Do those ones use the magnetic pull? I had some newer Powerbooks that did, and the issue was that the latches became misaligned with the magnet. Once those got lined back up again, they latched properly again.

With that era of C2D machines, I tend to run both Snow Leopard and El Cap. For a long time, I was using El Cap more, but now it's far enough out of support that it is starting to break in the same ways Snow Leopard is broken -- so I tend to boot into Snow Leopard more now, and work on fixing...

Because Apple was trying to push Mac OS 8 adoption. There was no reason for them to desire to provide backwards support. Especially as everything was supposed to be moving to Copland to begin with, and then Rhapsody. Providing backwards support would have spread them even thinner.

I just set up 7.5.0 yesterday... and 7.6.1, and 8.1.

Based on the threads on here on CHRP and on System Enablers, there's some interesting potential to improve the current TBXI and Enabler files to make things even more stable and support more OS versions :)

Current strategy is actually to set the metadata, then macbinary-encode the files, and not depend on compression. A macbinary file is just a data file, so as long as it's not being treated as a text stream, shouldn't be garbled by Windows -- and yet, you can still open it with a hex editor and...

To quote @Protocol_7: Essentially, like with Toast (only moreso), Disk Utility messes with the image headers; more recent versions of Disk Utility appear to lean on the fsplugin architecture to build the header, and if it can't find the correct fsplugin, it just writes a raw data stream with no...

For those who don't know -- dd (data definition/definer) is a general purpose file read/write tool that can pipe to/from various interfaces including sockets, block devices and text streams. This means it can leverage existing filesystem drivers or serial read/write a hardware device, and if...

Not all versions have the same handling of default sector sizes or header data; They’ll all get you what you want in the end (an image of the disc’s contents), but do you know how to enforce the reading of gap data on all versions of dd?

Also, it was disscovered when making the script that not all versions of dd are created equal. So the script does some extra checking now to make sure the images are generated correctly whether you're running OS X 10.2 or macOS 26.

Arcane and insignificant, but I feel like we all need to get better at identifying, extracting, and patching features, as it appears that we can mix and match for OSes all the way back to 7.5.0 at this point.

And we've done a fair bit of testing and feedback to ensure those scripts cover the edge cases. I have yet to find an optical disc where the current version of the scripts fail to do the correct thing.

The "This won't work on your model" can be patched out... however, some of that stuff... won't work on your model. So instead of throwing an error, the machine will lock up or crash.

In my experience, flux itself tends to be non-conductive, but often ends up with conductive particles suspended in it.

It's in the github repo linked at the bottom of the sheet :) Or, to get a better organized version: https://68kmla.org/bb/index.php?threads/gray-ndrv-solution.50969/page-3#post-576037 - @joevt's fork is in better shape currently.

Have you tried one of the intermediate ROM versions? 9.0.4 spans ROM 3.7 through 5.5.1, and 9.1 spans 6.1 through 7.9.1, so there's lots of things that could change between ROM version for the same OS release.

Ah; and hence your questions regarding ROMs. General rule is: you need a ROM version that matches or is later than the one that came with the OS version. Unfortunately, as things progressed, some features got stripped from later ROMs. It'd be really great if we could eventually get to the...

Do you have a driver partition on the same volume as those partitions? The boot manager needs to be able to write which boot path is blessed to the driver partition. I suspect there may also be an issue of booting off of HFS AND booting off of HFS+. I haven't got around to following in your...

Which build of NT4 did you download? I presume you got a PPC build, but there were a number of builds, some of which were VERY hardware-constrained.