Hi Sebastien, congrats!

The later iMac G4s are on the upper end of machines that have less support for sound and video devices. I'm not sure there's much you can do, but try plugging something into the headphone jack. You can usually get internal sound working on Mac Minis by doing this, otherwise it may work with speakers/headphones plugged in.

I need to dig out my iMac G4 800, there's a few things like this that I still need to test!

Like

0

Hi again, thanks for the replay! I've actually managed to get it working on 2 of my iMacs, I'm gonna do a bit more testing and may have soon a small OS9 app to share that enables output for the Pro Speakers. I'll keep you updated.

Like

0

Oh wow that's fantastic! Looking forward to hearing your progress!

Like

0

Yes it works on iBooks, see the compatibility list here on MacOS9Lives.com.

I believe some require the "screamer" fix noted above, and there's even an iBook GPU driver that allows some Radeons to have full GPU acceleration. I'll try dig that out this weekend and will upload when I get time

Like

0

Hi Gerry,

Unfortunately this only works on G4 machines. G5s are unsupported as their hardware and architecture are vastly different from the G4s which natively supported OS9. Mac OS X 10.4 runs OS9 under emulation through the Classic Environment. This is different to running an operating system natively, and is the reason why the Classic Environment has poorer performance/support of software when compared to OS9 being run natively.

Later model G4s were intentionally prevented from running OS9 by Apple, when support could have easily been added, and this is what this hack enables. G5s are a giant technological leap into a different direction, and there is zero system/driver support within Mac OS 9 to support the newer hardware, so running it isn't possible.

Like

0

That could be it, I find that burning a CD with Toast is the most reliable method to get a working boot CD. What type of machine are you trying to boot this with?

Like

0

I use Powerbook 5,8, the final 15” model.

Like

0

If you can't boot the CD then the only issues I can see would be:

• The NVRAM code is invalid

• The CD wasn't burned correctly (e.g. correct Mac format, burned with Toast on an older Mac etc.)

Check your NVRAM code again, and ensure it's exactly the same as the example above. Note the spaces preceding device names like "[SPACE]cpu-version", "[SPACE]screamer" are important etc.

Also try with and without the screamer fix. If that fix doesn't apply to your machine then it could cause issues if you're trying to apply it.
Otherwise, after you've booted into Open Firmware, navigate through the device tree to see if the location of the "screamer" device is the same as in this example. E.g.:

dev /
ls

Or

dev /pci@F2000000
ls

These list the child devices underneath the device you're specifying, where / is the root/top level device.

Once you're in side a device (e.g. dev /pci@F2000000) you can type .properties to view names/values of the selected device.

Like

0

I think that it cannot boot because the final powerbook models had ddr2 ram.

Like

0

Ah that makes sense! Thanks for the update I'll note that on this page.

Like

0

It sounds like there's an error in the commands you've saved to the NVRAM. If you're getting a not valid message it usually means it can't evaluate what you're telling it.

Try running `nvedit` and clearing everything/every line, and then apply the the hack again. Be careful to enter every line exactly as it is below:

dev /cpus/PowerPC,G4@0
80010201 encode-int " cpu-version" property
device-end

Then run the commands:

nvstore
setenv use-nvramrc? true
reset-all

Like

0

I believe it should work, I've had it working right up to the 1.67Ghz models. Have you tried the screamer soundcard fix (the last block of example code in the post)?

Like

0

I finally got it to boot and install on my PowerBook G4 5,4. I burned tried 3 different burning speeds and finally got past the grey screen when I burnt at 4x and held C at boot. Thank you for your help!

Like

0

That's great! I'm glad it was a simple fix. Thanks for letting me know, I'll add a note to this page.

Like

0

Hi, and sorry for the slow response!

I'm not too sure I haven't tried with an eMac before, but my first guess would be that it needs the screamer soundcard patch (in the last code example), or something may be slightly off in your NVRAM code.

Otherwise I would highly recommend visiting the MacOS9Lives forum, they will have a dedicated eMac page. Now that I think about it, you may actually need a different boot CD (from MacOS9Lives), I think some of the Mac Minis and eMacs require a slightly different Mac OS ROM.

Like

0

Hey Bolkonskij,
A while back I did some testing with a 1.0Ghz 15" but stopped after I couldn't get video acceleration. The GeForce4 MX was supported in Mac OS 9, but the chipset is slightly newer (NV18) than the one supported by the Mac OS 9 drivers (NV17) - thanks to darthnVader for this info. I believe the system was still usable but I haven't booted it for over a year. It's sitting out at the moment so I'll fire it up in the weekend if I get time.

I did have a 1.25Gz 17" but unfortunately sold that before I found the work by iMic and Mac OS 9 Lives!

Like

0

Hi Retter, thank you very much!

When booting unsupported machines Mac OS 9 often thinks there are two monitors attached, and incorrectly assigns the wrong one as the default monitor. Try pressing the F7 key (with the two squares icon). This should switch monitors, then you can open the Monitors/Monitors & Sound control panel to redefine the screen arrangement.

If pressing F7 doesn't help, try connecting a second monitor to the DVI port and performing the same steps. See the images at the end of the article for more detail on how to do this.

I've also updated the article to note this (thanks for your reminder!).

Like

0

No, it works, I have tried it with different disk images, and I can't get past the gray screen. I don't know what I could be doing wrong. Could there be something wrong with the Open Firmware? I do not know what to do

Like

0

Ah right, do you see the "Happy Mac" at all when trying to boot?

You will probably need to apply the "screamer" fix if you haven't already. The full statement you save in the NVRAM editor should look something like this:

dev /cpus/PowerPC,G4@0
80010201 encode-int " cpu-version" property
device-end

dev /pci@f2000000/mac-io/i2s/i2s-a
" screamer" encode-string " compatible" property
device-end

Like

0

Now we are on the right track, but there is a problem, because when the east side that says 9.0 appears and the transport bar reaches the end, it freezes, and the mouse does not work, I have tried with the extensions disabled and the same thing happens.

Like

0

Thank you very much, thanks to your instructions I have managed to install the system, it has some strange things, I see as if the video acceleration does not work and the adio does not work in any way, it is as if it does not detect the internal interface

Like

0

No problem. The freezing is usually due to the Multi Processing folder not being removed before booting, in which case you boot from the CD again and remove it.

That's right, there's no video acceleration on these models since there were no drivers/support added for Mac OS 9 with the GPUs used in these machines. The sound issues are occurring for the same reason.

The best models I have used are the `M8793LL/A` (1.0Ghz 17"), and the `A1046` (1.0Ghz 15"). These models have full sound, trackpad support, and good GPU support with darthnVader's ATI extension. The only problem with all models is that sleep is unsupported due to there being unrecognized hardware devices. I have been trying to find a solution to this but haven't had any luck yet.

Like

0

With the Darth Vader ATI extension the screen goes completely black

Like

0

Hi Retter,
Apologies for the delayed response. That's interesting.. Have you tried removing all NVIDIA extensions, and also some/all of the existing ATI extensions?

Like

0

Hi cyberish! Thanks for the kind words I'm glad you've found it interesting!
I haven't setup external boot devices for a while now but I believe you are correct with the structure of these commands, although your device ID may be different.

In another article (Changing the boot device with Open Firmware) there is an example for booting from USB devices, which is the same as what you have. Booting from a FireWire device should be the similar although you should view Open Firmware's device tree with devalias to find the device ID of your FireWire drive.

Some computers have different device names based on their port configuration. For example, my PowerBook G4 Ti has the devices fw and fwx. I'm assuming fw is for the single FireWire port but I'm not sure what fwx is for. It has two USB ports so the usb0 and usb1 devices are both present.

Let me know how you get on :)

Like

0

thank you Greystash for the HDD hint! - I got my Powerbook 6,2 booting into OS 9 but it hangs and freezes just before completing the boot process, before getting to the Desktop. - The same occurs even with Extensions and Control Panels off... - I had this very computer working once with the "unsupported MacOS9Lives" Cd. (There is a little hick on this page : it should be "reset-all" (not " reset all" !)

Like

0

Glad to hear you got it booting! After installing from the MacOS9Lives CD did you remove the Multi Processing folder from Extensions? Leaving this within the system folder will crash the boot process. Maybe this is seen as an essential part of the OS and loads even if extensions are disabled.

If you can boot from the MacOS9Lives CD it means that there is probably something wrong with your system folder. It might be worth trying to re-install from the CD, and then removing the Multi Processing folder before rebooting.

Thanks for letting me know about the typo! I've just fixed that up.

Like

0

This is it! Removing the ‘Multi Processing’ folder did the job. Thank you ! For what reason the ‘Multi Processing’ folder is still in the System Folder on the MacOS9Lives distribution? Will post over there too...

Like

0

I'm not sure but it has been brought up previously, although I can't remember what the outcome was. That's great you've got it working now!

Like

0

Hello! No worries, but I can't take credit for all the initial work that got us to this point - that goes to the folks mentioned on this page.

Great to hear that you've got it all set up!
I've got the same setup FW800 1.4Ghz with 2x SSDs (one OS9 and the other Tiger). I don't have any issues selecting boot drives after restarts etc. but I know that SATA adapters can influence this a lot.

On the ATA66 Bus I have my OS9 SSD connected, and no other devices attached. This is the SATA adapter I'm using and it's set to Master.

My OSX drive is connected to the IDE bus closest to the CPU and uses this SATA adapter. I'm not sure which jumper setting this defaults to since there are no pins to bridge, I'm guessing it's either Cable Select or Slave? Again there are no other devices connected to this cable.

What sort of hard drive adapters are you using (if any)? I previously used different adapters and after restarting OS9 I could never boot into OSX, but it would work if the machine was completely shut down, and then turned on again. After holding the option key to bring up the boot selector I could then choose the OSX drive and it would boot. Restarts would never work, it would always boot the OS9 drive. The combination I am now using works well and I haven't had any issues with these adapters.

This probably isn't going to help but you could try this alternative Startup Disk version and see what happens.

Hopefully this helps. If you want more details on my setup let me know, I am happy to help!

Like

0

I have the 7.5.6 version here, but if you're after the beta version I assume this would be found within a 7.5.6 beta system update.

Like

0

Hi Steph,
The line you need to enter into Open Firmware is this:

setenv boot-device hd:\bootscript

The boot script should be a plain text file (txt) created by SimpleText, and the name in the command above should be whatever you named the script file.

It's likely you're getting stuck on the grey screen because the boot script isn't being read. The script is what tells Open Firmware to modify the CPU version which enables Mac OS 9 to boot. You will also need to make sure your HD is formatted correctly for OS9 to run.

See more on setting up the boot script here.

I haven't tried this on a 1.25Ghz eMac but it should work fine. Best of luck!

Like

0

Hi, thanks for the answer! I did that already, I found the info here. My partition is on an external firewire drive, no luck. Do I need to replace "hd" by "disk1s2" for example? I'm almost there, frustrating, thanks in advance.

Like

0

I haven't actually tried this on an external disk before, but I have used a partitioned drive. hd is an alias for the internal disk and it seems to search all partitions for the script. I would assume that swapping hd for your disk identifier would work, but I'm not 100% sure as I haven't tested this.

When you're setting the boot device/pointing to the bootscript in Open Firmware you would replace this with something like the following (this is an example with a USB device ID, so replace it with your FireWire device ID and partition number):

setenv boot-device usb0/disk:2,\bootscript

And in your bootscript you should replace boot hd:,\\:tbxi with boot usb0/disk:2,\\:tbxi, but with your FireWire device ID/partition number.

If that doesn't work you might be limited to using an internal disk. I'm interested to hear how you get on!

Like

0

It's working, just quite unstable and I have a lot of privileges problems, OS9 games are on the X partition, I can live with it, thanks!

Like

0

Glad to hear you got it working!!

Like

0

I've come across this also and I think there's a bug involving some of the ATI drivers. Try this:

After booting wait at the desktop for a while in the frozen state. After waiting, open the Force Quit prompt (command + option + Esc). The prompt should ask you to force quit an ATI utility (because this is what's currently hanging the system).

If you don't get this wait a little longer after the next restart.

Once you've booted successfully into the system, disable all NVDIA drivers, and try disabling/toggling some ATI drivers. I can't remember which one causes the issue but it's not going to make much difference disabling some/all since GPU acceleration isn't available anyway. The modified Jasper driver is essential for screen resolution and color support.

Like

0

Hi Roman. After checking my model I noticed that it's not the DLSD model, instead it's the PowerBook 5,6.

If yours crashes immediately after selecting the boot device then I would assume it's an issue with incompatible RAM (DDR2). I don't think there were any machines supported by OS9 that used DDR2 memory.

If the system begins loading, and then crashes then it could be a video issue. The GPU is unsupported but may work with the modified ATI driver made by darthnVader from MacOS9Lives. This would need to be moved to the Extensions folder of the System Folder you are trying to boot.

Good luck!

Like

0

Hi Roman, as far as I'm aware it does work with the screamer fix mentioned above. I managed to get it working on an overclocked 1.8Ghz model (1.67Ghz 15" model although I can't remember if it was DLSD).
The main issue is that these later models have a USB track pad that is unsupported by OS9, so the tracking is incredibly slow making it barely usable. If someone were able to write a driver for this it would be by far the best portable unsupported Mac OS 9 machine. If you're willing to use a mouse instead it would be fine.

Like

0

Hi there, I've edited the page to explain the monitor/resolution problems in more detail. I've also added an alternative link for the video driver, so see above for these edits.

Like

0

If the speakers are working fine then it's likely you won't need the screamer fix. If they aren't functioning correctly you don't need to download anything, just add the screamer fix code detailed above to your Open Firmware script.

Like

0

Hi there! That's great news! Do both speakers work correctly under OSX?
If they do it might be a driver compatibility issue under OS9.

If you haven't tried the "screamer" fix mentioned above you could try that, otherwise if it's already present in your script/NVRAM you could try removing it.

Also, this probably isn't the issue but check the speaker balance in the Sound control panel.

Like

0