View Full Version : Can no longer launch Classic
05-08-2002, 02:39 PM
So I installed an additional hard drive and a Tempo ATA100 PCI card to drive it. Empty media drive, nothing on it.
Now I can't launch Classic! I get a message saying I must have 9.1 or later installed. I have 9.2.2 installed. I can boot from 9.2.2 no problem.
Any ideas anyone?
Phil St. Romain
05-08-2002, 03:48 PM
Mark, you say you rebooted into 9.2.2. Are you able to select it as your Startup Disk in the OS X System Preferences? If so, then reboot into 9.2.2 after switching, then in OS 9, change your startup disk back to OS X. When you reboot in X, see if you can select your 9.2.2 Classic system folder. That little trick has worked for me before.
Otherwise . . . time for the Unix guys to step up on this one. ;)
05-08-2002, 04:51 PM
Yes, that's exactly what I've done:
1) Boot up in OSX
2) Try to launch Classic either by launching a Classic app or using the System Preferences Classic pane. Either way, get the message that OS 9.1 or higher is required.
3) Use the startup disk pane to select 9.2.2 as my startup disk
4) Restart in 9.2.2
5) Chooser->startup disk, select OSX
6) Reboot in OSX
7) Repeat 2)
ad infinitum. Don't know what else to try. Never had a problem running Classic until yesterday when I did two things:
1) Swapped the two drives connected to my main ATA bus. Made the master the slave and visa versa so that my boot drive was the master. Slave is a media only drive for editing; master has all apps and both OSX and 9.2.2 on it (no partitions)
2) Installed a third, new drive connected to a new Sonnet ATA100 card. Drive is formatted but completely empty.
Any other really smart people out there have any ideas of what I could try? Thanks for the suggestion, Phil.
05-09-2002, 12:08 AM
Maybe blessing the OS 9 System Folder from the terminal? Look at man bless, but I believe the code is:
bless -folder9 "/Volumes/Mac OS 9/System Folder"
Of course, change /Volumes/Mac OS 9/ to whatever the drive OS 9 resides on is called.
05-09-2002, 01:16 PM
Ok, so I tried that. My hard drive (not partition, has both OS 9.2.2 and X) is named "Seventeen".
In terminal, I entered
bless -folder9 "/Volumes/Seventeen/System Folder"
and this is what I got:
ERROR(bless):Not run as root, enabling -noexec mode
ERROR(bless):Error while getting directory ID of /Volumes/Seventeen/System Folder
ERROR(bless):No mount point for /Volumes/Seventeen/System Folder
ERROR(bless):Can't determine mount point of ' ' and '/Volumes/Seventee/System Folder'
Any ideas on what I could try next?
05-09-2002, 01:30 PM
sudo bless -folder9 "/Volumes/Mac OS 9/System Folder"
and enter your admin password when prompted to
05-09-2002, 01:36 PM
markspen, hmm, greater than one problem, i believe. firstly, you should bless under the guise of sudo...
$ bless -folder9 "/Volumes/tango/System Folder"
ERROR(bless):Not run as root, enabling -noexec mode
$ sudo bless -folder9 "/Volumes/tango/System Folder"
second problem are the errors after the 'not root' blurb.
did you copy/paste that directly? see that last error about mount point? see how it's not 'seventeen'? what happened to the 'n'? i can't help but think that there's something wrong with the hw config, or that there's a funny char in the volume name.
$ /bin/ls -lq /Volumes/
drwx------ 23 merv wheel 738 May 8 11:59 banshee
drwx------ 30 merv wheel 976 May 8 11:59 chunder
05-09-2002, 01:59 PM
No, I didn't paste directly, that was a typo...I'm writing this on my powerbook, my desktop G4 is the one with the problem.
It's now tied up capturing video for a project I'm working on, as soon as it's done, I'll try your "sudo bless" suggestions. Thanks.
05-09-2002, 02:14 PM
still, i think the subsequent bless errors are problematic, so show us your
/volumes dir and
Filesystem 512-blocks Used Avail Capacity Mounted on
/dev/disk2s9 14652512 4538312 10114200 30% /
devfs 97 97 0 100% /dev
fdesc 2 2 0 100% /dev
<volfs> 1024 1024 0 100% /.vol
/dev/disk2s10 14652512 3006400 11646112 20% /Volumes/banshee
/dev/disk2s11 14652512 4563320 10089192 31% /Volumes/chunder
automount -fstab  0 0 0 100% /Network/Servers
automount -static  0 0 0 100% /automount
05-09-2002, 03:13 PM
If you only have one drive, with no partitions, you should just enter
sudo bless -folder9 "/System Folder"
/ would be the same as /Volumes/Seventeen if you are booted from Seventeen.
05-09-2002, 05:19 PM
Did sudo bless -folder9 "/System Folder", got request for password, entered admin password, tried to launch Classic, no go.
Did /Volume dir, got "Permission denied".
05-15-2002, 12:54 PM
So I'm still stuck here...need to launch 9.2.2 directly if I want to run any non-OS X apps. Anyone have any other ideas on how I can fix my system so it will launch Classic? Used to work just fine.
Thanks in advance,
05-15-2002, 01:08 PM
I didn't catch in all of that terminal thrashing if you had tried any of the following:
1. find the "classic" files in your 9.2.2 system folder (I'm not at an OSX machine right now, so I forget the exact names..there's at least three, something like "classic gui support" and such. They should be at the top level of your system folder.
2. delete them.
3. restart. You should now NOT have a classic-enabled choice....
4. go into system preferences, and select your system 9.2.2 folder as your classic choice. OSX will install fresh classic helper files.
5. optimize the classic folder (from the advanced tab)
6. log out and back in and see if that helps.
Since you can boot from your 9.2.2, but OSX doesn't recognize it, this leads me to think its classic files are corrupt.
I couldn't tell from your note whether you have yet initialized the new drive. Remember, a tempo-attached drive THINKS its a scsi drive even though its a IDE drive. You may have to first initialize it with disk setup while booted under 9, then boot under OSX and reinitialize with OSX drivers.
I couldn't tell if you had partitions on your original drive and were booting from that, or if you were trying to boot from the new additional drive, or what.
If possible, partition both with at least three partitions, your classic folder on one, your OSX on another, and third for legacy 9 things.
see if that allows you to address your classic problems.
other than that, I'll need more precise info....good luck!
05-15-2002, 01:11 PM
Originally posted by markspen
Did /Volume dir, got "Permission denied". sigh.
please show us your /volumes dir and filesystem report by issuing:
% /bin/ls -lq /Volumes
and copy/paste us the results, wrapped in the vB 'code' tags, if you would.
05-15-2002, 02:32 PM
Got it to work, thanks lerkfish!
I had a drive that wasn't being recognized in 9.2.2 that I use for video. I reinitialized it in 9.2.2 and I trashed the Classic files in the 9.2.2. system folder. Rebooted in 10, was able to launch Classic. Thanks, everyone, for your excellent suggestions, I really appreciate it.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.