68kMLA Classic Interface

This is a version of the 68kMLA forums for viewing on your favorite old mac. Visitors on modern platforms may prefer the main site.

Click here to select a new forum.
Installing OS X on a slave drive
Posted by: quinterro on 2008-04-24 11:40:09
Now that my G3 MT is working, I'm trying to install Jaguar (10.2) to it. I added a slave 6GB drive attached to the same cable as the 4GB master. MacOS 9 sees both drives. The ROM is revision B and has slave support.

The G3 loads the installer from CD and lets me choose the slave drive. Once the install is finished it restarts and promptly boots from CD again. If I remove the CD, it boots into MacOS 9.

Any suggestions besides making the 6GB a master and the 4GB a slave?

Posted by: Christopher on 2008-04-24 12:13:56
Just for the hell of it, try XPostFacto, even though it is fully supported by 10.2.

Posted by: Anonymous Freak on 2008-04-24 13:07:23
Have you tried going to the "Startup Disk" control panel in OS 9 and changing your startup disk to the newly installed copy of OS X?

That might do it. But, yeah, the beige G3s have all sorts of odd issues with slave drives. An XPostFacto assisted install should also work; but it would mean reinstalling.

Posted by: Christopher on 2008-04-24 14:55:58
Have you tried going to the "Startup Disk" control panel in OS 9 and changing your startup disk to the newly installed copy of OS X?
That might do it. But, yeah, the beige G3s have all sorts of odd issues with slave drives. An XPostFacto assisted install should also work; but it would mean reinstalling.
Maybe not. I think you can just have it mod the kernal.

Posted by: jhvaughan2 on 2008-04-24 16:52:39
IIRC, what i've seen is that the beige G3 will not boot OSX from the slave at all. Even with rev2 or 3 roms.

LEM concurs: http://lowendmac.com/ppc/beige-power-mac-g3-1997.html

xpostfacto might get around this but I think you have to setup the master as the helper disk. If you haven't got it figured out before this weekend. I can try to do some disk swaping to do some testing.

Posted by: quinterro on 2008-04-25 06:34:55
While my G3 MT has a Rev2 ROM which does support slave drives, I think the motherboard is a Rev 1 which does not.

Somewhere in my office I have a Rev 2 board with a 333mhz processor on it. Once I find it I'll give that one a try.

Posted by: coius on 2008-04-25 10:15:04
use XPostfacto to use the 4GB as a "helper" disk. It will install files on the 4GB that redirects it to the 6GB.

try that first. I did this to get a Beige PowerMac and a PowerMac B&W to boot from Firewire

http://coius.dyndns.org:10455/coius/FireWire_Booting.html

Posted by: madmax_2069 on 2008-04-25 22:47:23
if you ask me its a software limit put in place in OS X by Apple to try to discourage you from installing OS X onto it and to try and force you to buy a new Mac, its Apples tactic. i had OS X tiger installed on my 120gb HDD (it has 3 partitions and i could instal and run OS X from any of the 3) in my Beige G3 AIO thanks to Xpostfacto and it allows you to install and run OS X on a HDD or partition (dont have to be the first one either) bigger then 8gb. normally when installing OS X jag on the Beige G3 you would see you could only choose the master drive if it was 8gb or smaller, or if the partition was the first one and 8gb or smaller.

i also used Xpostfacto to boot the tiger CDs from my external Lacie drive (which is SCSI) to install OS X on my Beige G3 AIO.

Xpostfacto removes many limits but also using it adds limitations to OS X that i have found. mainly in panther and above, dont know about jag tho cause i never had to use Xpostfacto to install jag, it always worked after a bit of tinkering with the HDD jumpers.

While my G3 MT has a Rev2 ROM which does support slave drives, I think the motherboard is a Rev 1 which does not.
Somewhere in my office I have a Rev 2 board with a 333mhz processor on it. Once I find it I'll give that one a try.
even if the mobo is a rev 1 you can still fix it by putting a rev b or c rom in it and it will fix the no slave drive issue. cause it was the roms fault and not the mobo.

1