[Whyren]

I recently bought a 300 GB Seagate drive to add to my Quicksilver 2002. The intent of this drive is to replace to standard 40GB (which will eventually be erased and used for backup). After installing the new drive (setting new one to master and old one to slave), and formatting the drive, I used Carbon Copy Cloner to copy all the data on my old drive to the new one. Upon completion, I began checking the data. OS X seems to be a perfect clone, but OS 9 would not start on the new drive. In OS 9 on the old drive, I ran Drive Setup and noticed the "Update Drivers" option was greyed out for the new drive. Figuring I must have unchecked the "Install OS 9 drivers" in Disk Utility, I erased the new drive and ran CCC again. OS 9 still refuses to start. Specifically:

1.) The computer starts with a flashing disk icon for a short time, then brings up the Happy Mac icon.

2.) On the first CCC, it would just hang on that and do nothing. On the second CCC, it now shifts to the OS 9 system on the old volume and starts from that.

The only things that strike me as odd are:

1.) Drive Setup still has "Update Drivers" greyed out.

2.) Startup Disk (OS 9) lists the system on the new drive as Mac OS 9.2.2 (Classic 9.1.8)

3.) When opening Startup Disk, it seems to take a long time scanning the new drive (and rescans every time the Control Panel is brought to front) and once the OS 9 on the new drive is highlighted, it stays that way (even when selecting another startup).

Anyone have ideas as to what's happening? Any help is appreciated. Thanks!

EDIT: A couple of other tidbits of information. Disk Utility (OS X) says that my old drive is HFS+ (Journaled), but the new drive is just HFS+. Disk First Aid (OS 9), when asked to verify the new drive, states "This is not an HFS disk."

[reader50]

Avoid the case-sensitive version of HFS+, I suspect OS9 will have problems with it.

Check the new drive with Disk Utility in OSX. It will show in the summary info if OS9 drivers are installed on the drive. Depending on your OSX version, you may need to click to the Partition tab to see if the OS9 drivers box is checked. If you are in 10.3 or 10.4, you can also see if OS9 drivers are installed by checking Apple System Profiler. Check the ATA bus, it will show that infor for each attached volume.

Next, the OS9 system folder may not be blessed. While booted into OS9 on the old drive, open the OS9 System Folder on the new drive. Move the Finder, System suitcase, and Mac OS ROM files to the desktop. Close the System Folder. Now drop all three files on the closed System Folder. The folder icon should change to show a happy Mac on the folder, this indicates it's blessed as a valid System folder.

[Yose]

Is the drive partitioned? It might bethat OS9 cannot handle that size of a HDD.

[Whyren]

The new drive has OS 9 drivers, and the according to Apple's KBase, OS 9 should be able to handle an unpartitioned drive up to 2 TB in size.

Blessing the system folder DID make it change from a normal folder icon to a system folder icon, but it still wouldn't start from it.

Is it possible the Master/Slave jumper configuration has anything to do with it?

[reader50]

Try System Picker. It's an old utility (possibly from the System 7 days) used to select/bless any available system folder for the next reboot. Remember, OS9 can have multiple system folders.

I don't really know if it will help in your situation, but I've kept the utility around because it's sometimes gotten system folders to boot in 9 when nothing else did. It knows nothing about OSX, but it does launch in Classic. It hasn't trashed anything on me, but I haven't used it in ages either. Use at your own risk.

[komodomac]

Its possible that your Clone (like my SuperMac S900) is only supported to OS 9.1. OS 9.2+ can only be used w/ OS 9 helper from <http://www.os9forever.com/os9helper.html>.

Good luck, aand let us know...


Dono'
<http://isitartyet.com/>

[Whyren]

No luck using those methods, but I do believe I've found the answer. As a last attempt I initialized the disk in OS 9 which left it with only 128GB of space. I went to Apple's KBase to confirm this was a the max size OS 9 partitioned, and ran across this:

http://docs.info.apple.com/article.html?artnum=86178

As OS 9 started with the 128GB initialization, I went back to OS X, ran Erase with Disk Utility again, except I partitioned a 199GB drive out of the 300GB, then CCC'd the System Folder 9 to it. It worked.

So, it would seem that Yose was right: while OS 9 can read disks up to 2 TB in space, my computer's BootRom is one month too old for 9 to read anything larger than 200GB, or at least that's how it appears.

Solution: since I'm continuing to use the old 40GB in my computer anyway, I'll just copy it to the new one (so I can keep all my Classic settings) and when I need to reboot in OS 9 (which is rare anymore anyways), I'll use OS 9 off the old 40GB.