Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Can't find Classic on 10.0.1 System
Background first: These symptoms did not occur until I updated to OS X 10.0.1.

I'm working on a iBook 466/192MB - OS X 10.0.1 and 9.1 on a single partition.

When I select OS X in the Startup Disk Control Panel (while in OS 9.1) I am warned that there is no system folder selected and that unpredictable things may happen.

If I reboot, OS X boots fine. Selecting Classic in the System Preferences provokes the notice that there is no MacOS 9.1 or later installed anywhere (I've got three now) so Classic cannot start. I've reinstalled OS X (& the update - 10.0.1), reinstalled 9.1 and rebuilt the desktop (in 9.1, not Classic). I can still select OS 9.1 as the startup disk from System Preferences.

I'm at a loss here. I need Classic to run some everyday stuff. Any ideas?
  • Currently 4.50 / 5
  You rated: 5 / 5 (2 votes cast)

Can't find Classic on 10.0.1 | 5 comments | Create New Account
Click here to return to the 'Can't find Classic on 10.0.1' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
I had the same problem.
Authored by: Munimula on Apr 26, '01 07:37:49AM

I'm not sure what causes this, but I had it happen to me twice. The workaround is simple, if annoying.

Startup off your MacOS 9.1 CD, then trash all the visible files and folders for X on the root of your harddrive.
Then Open Sherlock and search for invisibles (just to make the search quicker I also set it to "name-doesnt contain -'icon'") and throw away all invisibles pertaining to X. (they will also be on the root level of your harddrive.) this will include folders like "bin" and "volume" and "usr" and anything beginning with a period. Just be careful not to delete your AppleSharePDS or your Desktop files, as these are needed by 9.

If you have installed any apps in X, you will want to have moved them to a folder other than your MacOS X Applications folder.

Then reinstall X.

There is probably a way of doing this that does not require you erasing your Documents or Applications folders, I just erased it all on my machine to save having to do it again in case it didn't work.

When you go back into X, copy (don't move) your apps that you backed up back to your Applications folder, as well as any doc you might have kept. This will make sure that you have sufficient permissions to use those files.

It sounds harder than it really is, the whole process takes about 20 min. on my DP500.
BTW, I havn't had this problem again since I installed 10.0.1, but I suspect it has something to do with some core file being corrupted during an install with 9 on the same partition.

[ Reply to This | # ]
I had the same problem.
Authored by: soconnor on Apr 26, '01 10:26:16AM

There is a simpler solution. If you use "System Disk" a utility that came with the public beta it will allow you to select your OSX partition and reboot into X without destroying the OS9 system file from which you were just in. This technique can be applied to corrupted system disks. This phenomenon is only apparent when switching file systems on the same volume. I do not know were to find this utility other than the PB CD but I am sure with some hunting around it can be found.

[ Reply to This | # ]
I had the same problem.
Authored by: Munimula on Apr 27, '01 04:59:07PM

the problem isn't the MacOS 9 system getting hosed (although after several times this can happen). It is a corruption of Both X and 9. This originally happened to me because I had installed X over the PB (which was also installed over DP4 and 3). The System Disk utility is no longer needed. PLEASE DO NOT USE IT! It can cause conflicts with the system. The MacOS 9 Startup Disk control panel now supports switching to the MacOS X system folder on the same partition, as the original thread implies this user did.

[ Reply to This | # ]
Here's my advice
Authored by: gigabyte on Apr 28, '01 08:30:52PM

I'v never seen this before, but it sounds like you are having problems with having the two systems on the same partition. try using the "drive setup" app (OS9) or for OSX, the "disk utility" app to partition your disk, then install OSX on a seperate partition. Another option is to buy a second hard drive if you don't have one already. They are relativiely inexpensive, and solve a lot of problems, and prevent hours of data back-up (which shold have been done prior to installing OSX)
-good juck to you

[ Reply to This | # ]
An EASY solution!
Authored by: Anonymous on Apr 29, '01 02:18:41PM

I had this problem, but didn't have to do all this reinstall business.

First, have you installed Startup Disk v. 9.2 (available on the Apple website)? I think it fixes this problem...

Either way, the problem is that the OS 9 startup disk control panel does something that prevents the OS 9 system folder from being recognized by classic. (I suspect some funky "blessing" issues.) If you open the "classic" control pane, you'll see that the OS 9 system folder you wish to use is greyed out. How to "re-bless"? Simple -- run the "startup disk" control pane. Wait until it finishes the scan, then select the OS9 system folder as the boot folder... this will fix whatever blessing problems happened.
Now you can go into the classic control pane and select that folder. Finally, go back into the startup disk pane and reselect your OS X disk...

But I think all these problems can be averted by simply installing the new "Startup Disk" control panel.

(Also, I believe that the information given regarding having to reboot into OS 9 and ferreting all the hidden OS X files out is pretty spurious. The OS X installer is good at finding broken files and replacing them -- so every reinstall is a "clean" reinstall... no need to manually clean out the system for something so simple as reinstalling to fix a glitch in classic. [More serious problems might merit wiping all traces of OS X off the disk, but I've never seen such a problem...]).


PS. "Blessing" refers to the process by which the OS "blesses" a folder to be the boot folder, so that the ROM can recognize that folder as the one to start the system from.

[ Reply to This | # ]