Currently Being ModeratedMar 29, 2013 6:03 AM (in response to noospy)
The disc needs to a "retail" disc (the type sold separately for PowerPC Macs that can run Tiger), not a disc that came with another Mac model (including Intel Macs). Is the disc, and the source used for the FireWire attempt, a retail Mac OS X installation disc?
Currently Being ModeratedMar 29, 2013 6:13 AM (in response to Kenichi Watanabe)
Also, I vaguely recalled a problem with WD external FireWire drives being bootable. I found this...
and it has a LONG list of WD external drives that are NOT bootable over FireWire on PowerPC Macs. So that may or may not be a problem in your situation.
Currently Being ModeratedMar 29, 2013 6:55 AM (in response to Kenichi Watanabe)
Yes, the disc is the retail version, I purchased it years ago. The problem is the hard drive, since I found mine (MyBook Home Edition) in the "not be bootable on Power PC based Mac" list that you linked me. :( Thank you so much, now I know what the problem is. But I still need to install Tiger on the iMac. What can I do? I only have Intel Macs so I don't think I can install it on the iMac putting it into Target Disk mode..
Currently Being ModeratedMar 29, 2013 7:08 AM (in response to noospy)
If the reason you cannot install directly using that disc is because the G4 iMac's optical drive is flakey, and you have some other Mac with an optical drive and FireWire, you can try it this way...
Start up the Intel Mac (not the G4 iMac) in FireWire Target Disk Mode
The G4 iMac should be started up normally, connected to the Intel Mac over FireWire. Insert the Tiger disc into the Intel Mac's optical drive. See if it appears on the G4 iMac's Desktop. If it does, see if the G4 iMac can use the Intel iMac's optical drive to run the installation.
NOTE: Depending on the Mac model in FireWire Target Disk Mode, its optical drive is not always accessible in this way to the "host" Mac.
Currently Being ModeratedMar 29, 2013 7:21 AM (in response to Kenichi Watanabe)
Yes, I have a MacBookPro with optical drive, but with a FW800 port only. Unfortunately, I don't have a FW400-to-FW800 adapter, I need to buy it. Do you think it will work through the adapter? Or I will have to wait a week or more for my father to come back with my old polycarbonate MacBook. Anyways, thank you very much for your help, you probably solved my problem :)
Currently Being ModeratedMar 29, 2013 7:28 AM (in response to noospy)
It should work through an adapter, or with a cable that has FW800 (9-pin) on one end and FW400 (6-pin) on the other end. Like this one
Currently Being ModeratedApr 26, 2013 7:32 AM (in response to Kenichi Watanabe)
Unfortunately, it didn't work :( so the situation now is as follows: I bought a FW400-to-FW800 adapter on eBay, and it perfectly works; my mid-2010 MacBookPro (Snow Leopard) has a perfectly working SuperDrive; I have a copy of Tiger's retail DVD with some scratches and a copy of the same DVD I made from a disk image of Tiger that I made when I bought the disk some years ago.
So I connected the 2 Macs via the FireWire cable+adapter, I booted the MacBook in Target Disk Mode and put the DVD (I tried with both of them) in the SuperDrive, and then turned on the iMac on OS 9.2, but nothing appears on it's desktop. On the System Profiler, in the Devices&Volumes tab, in the FireWire section I only see a kind of code that I also see when there's nothing plugged in. I tried to change FireWire ports but nothing happens, apart from the iMac freezing sometimes. Am I doing something wrong? Or is it the case my MacBook is not suitable to do this job?
Currently Being ModeratedApr 26, 2013 11:16 AM (in response to noospy)
Try it this way. With the installation disc in the MacBook Pro (which is in FireWire Target Disk Mode), connect it to the old iMac while it is powered off. Start it up while holding down the Option key, which should give you the Startup Manager screen
(the screen will look somewhat different on your older iMac)
If the Mac OS installation disk in the MacBook Pro appears on the list of choices, select it and try to continue startup.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points