Not quite sure why I'm letting this bother me so, other than the fact that I can't seem to fix it, but here goes:
The
thread the other day from Micky got me started on this - when I had a look at my own Classic installation, I discovered that it had gone astray. I got the message
QUOTE
The previously selected system folder "/IBM - OS9.2.2/System Folder", is no longer available. Please select another system folder to use with Classic.
If I clicked on that partition, I got "IBM OS 9.2.2 could not be opened because you do not have sufficient privileges".
Aha, says I...I'll repair my permissions. WRONG ANSWER. No change. Ran DFA - both from OS X and from an OS 9 disk. Tried re-running the 9.2.2 updater on that partition. Nope and nope.
So then I logged in as root. Well, lo and behold, we had two "Previous System Folders" but no System Folder! Where had it gone? Who knows. Tried tricking it into using one of the Previous System Folders by lopping off the Previous in the name - well, that didn't work (didn't think it would). So, now I'm contemplating one of two things - logging back in as Root and backing up anything useful on that partition to somewhere else and then wiping the partition (drastic solution) or trying to simply copy a system folder from my 9.2.2 installation on another partition into the offending one - and then doing the nuisance work of comparing all the third party bits.
The silly part of all this is that I cannot honestly remember the last time I actually USED Classic. I did boot into 9.2.2 (the offending partition) about two months ago for some reason which I have now forgotten - it worked then. This all seems to have happened since I upgraded to 10.2.5 on the new drive. Oh - further tidbit, in all of this fiddling, I did try booting into 10.1.5 on the old drive and at that point, the 9.2.2 partition showed up as the partition to be used in Classic. Why does 10.1.5 think there is a blessed, working System Folder when 10.2.6 (yes, tried updating to that too, to see if it would fix things) doesn't?
And the answer to Micky's problem probably isn't fixing his permissions either - he needs to read this Apple article (none of which worked for me though):
http://docs.info.apple.com/article.html?artnum=106678