Benches macOS

17

OS 9 No longer boots

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hello,

I'm running OS 10.4.11 on a Quicksilver G4 tower. I have a Nikon LS-2000 film scanner that runs on a parallel port, and I've always booted into OS 9 which resides on a second physical hard drive to use my scanner because it hangs when I try to scan film negatives in Classic.

Now I can't seem to straight boot into OS 9, although I am able to still run Classic within OS X. I've tried blessing the OS 9 System Folder on the second physical disk, and ran Disk Warrior which reported an error and also blessed the System Folder on disk 2.

I think the problem stems from when I renamed the second disk a number of months ago to facilitate a symlink in OS X to my Pictures directory which I moved to disk 2 because of space considerations. There now seems to be a path naming conflict and I'm not sure how to resolve it. To facilitate the symlink command, I had to change the name of disk 2 from +Macintosh HD 2+ to
OS_9 because the symlink didn't play well with spaces in its path.

Now, when holding down the ALT key on bootup, my OS_9 drive still displays with the old +""Macintosh HD2""+ (including the quotes), so something somewhere is still referring to the old volume name even though I changed the name and re-blessed the OS 9 Startup Folder. When I choose this +""Macintosh HD2""+ option, my computer attempts to boot but then shuts down completely.

Does anyone know how I can resolve this? I've tried zapping the PRAM, changing the name back to the original, etc. but nothing seems to help. Thanks in advance.

17 replies

Sign in or join Beachball Help to reply.

  1. 0

    Don Archibald

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi, Jim -

    My OS 9 System Folder resided on a separate physical hard drive (250GB)...

    OS 9 can not be used for booting if the volume it is on is more than 200GB.


    Article #HT2544 - Using 128 GB or Larger ATA Hard Drives

    This limitation does not apply to OS 9 when used as Classic within OSX; it applies only when OS 9 is used for booting.

    ...I can now boot to OS 9 on this 3rd SCSI drive, but when I'm in the Finder I can't select any OS 9 menus (although I can move my mouse freely about) so it's not usable.

    • Have you tried booting to that OS 9.2.2 with Extensions Off (holding down the Shift key from the beginning of booting)? If the menus are then accessible to the mouse, that would indicate there is an extensions conflict of some kind.

    There are some known problem causers in 9.2.x; if you have any of these, try disabling or removing them - IdleTime (extension); N2MP3 (extension); and True Finder Integration (control panel).

    • When the menus are not responsive, are other items (like drive icons, folders, or files) selectable and responsive to mouse clicks?

    • Are you using an Apple-brand wired mouse? If you are using a non-Apple mouse, or a wireless one, additional software (software not part of a standard OS 9 install) may be needed.

  2. 0

    Grant Bennet-Alder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You debug this sort of problem using a half-interval search.

    Divide the total into two groups (roughly in half).

    Install one group, uninstall the other group.

    ? Problem persist ?

    - Yes: problem is in the Installed group. Divide the installed group in half and do it all again.

    - No: problem is in the uninstalled group, swap with the Installed group and proceed.

    You may find it helpful to print out a list of all installed extensions and mark it up with a pencil as you go along. I know that sounds archaic, but it works well while you remove and install portions of your computer's brain.

  3. 0

    Grant Bennet-Alder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    When you defer the Startup Disk selection to Startup Manager (option key held down at Startup) you have only ROM code available to help and/or diagnose. Faced with a problem, it appears your Mac does the only thing it can do from there -- shut down.

    The usual way to boot OS 9 when Mac OS X is fully available is to use:

    System Preferences > Startup Disk

    ... which should display every acceptable Boot Device and give you the full benefit of any diagnostic and reasonableness checking available, such as Disk Name, Blessed Folder selected/Not, drivers not found, etc. The full running System is available to present any errors that may be detected.

    In addition, I expect selecting your Startup Disk in this way will add insight to exactly what that Disk is now called.

  4. 0

    Jim Epler

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for your response. Unfortunately, in the Startup Disk pane the OS 9 Volume name displays as +Mac OS 9.2.2 on OS_9+. However, when I hold down the ALT/OPTION during boot it reads "/"Macintosh HD2"/"'", the old name I had assigned it.

    I'm wondering if I wipe the second drive, reformat with OS 9 drivers installed and copy everything back it will fix itself? This was my option of last resort.

    I'm perplexed as to where the returned "/"Macintosh HD2'/"'" is stored. Is it a flat database file at the kernel which is loaded into low-level boot memory? I performed a root level grep command yesterday in the Terminal and was not returned any results of files that contained this particular string.

  5. 0

    Don Archibald

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi, Jim -

    You might try a reset of PRAM, but do it from a cold boot, not a restart. To do that, shut the machine down, wait a minute or two. Then boot it up; immediately press the Command-Option-P-R keys, keep them held down until you've heard three additional sets of boot chimes; then release the keys and let startup continue.

    You might also consider a reset of NVRAM - the instructions for doing that are in this Apple KBase article -


    http://support.apple.com/kb/TS1812

  6. 0

    Jim Epler

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks, Don. I'll give it a try and let you know...

  7. 0

    Jim Epler

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Well....

    Reset the PRAM on a cold boot. After the third chime it shut down immediately. Tried to power on but continued to shut down immediately after first chime. Waited about 5 minutes and tried again, this time it booted to a blinking cursor.

    hmmmmm........

    User uploaded file

  8. 0

    Don Archibald

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    HI, Jim -

    That is odd. Resetting PRAM is a benign function - it returns the settings in PRAM to defaults, and nought else.

    It may be that it is looking for a bootable volume, since the setting for that was zeroed, too. Try starting up holding the Option key down. This should bring up Startup Manager in which you can select one of the available boot volumes -


    Article #HT1310 - Startup Manager: How to Select a Startup Volume

    You might also try replacing the internal battery - if that has not been replaced in a few years, or ever, it is time to do so.

  9. 0

    Jim Epler

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    yes, it might be time for a battery change. In fact, sometimes after my tower has been sleeping for a few hours, I touch the spacebar to wake and it just shuts down immediately. I've assumed it might be because the internal components were running hot-- probably a poor assumption and worth some more diligent research. My observation was based on the fact that after I blow out the internals and clear the cooling area it doesn't seem to shutdown this way (until another internal cleaning is needed).

  10. 0

    Jim Epler

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Update

    I swapped out the old with a new battery. I then held Option/Alt during startup and was greeted with both volumes as choices in the Startup pane, but neither displayed the little OS X icon next to the hard drive icon. I think I may have somehow accidentally blessed the OS X volume as an OS 9 volume during this troubleshooting exercise.

    User uploaded file

    I selected the +Macintosh HD+ volume and it immediately went back to the blinking cursor. I shut everything down and this time held the X key on boot. Again, nothing. Again, I shut down but this time booted into Open Firmware (Cmd
    Opt+OR) and typed the printenv command. The following screen shot shows my somewhat unexpected results at the boot-device output. I was expecting these values to contain some type of unique reference to my physical hard drives.

    User uploaded file

    Not sure what to do next, but is appears I need to somehow re-bless the +Macintosh HD+ as an OS X volume. Am I on the right track?

  11. 0

    Don Archibald

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi, Jim -

    As far as I know, drives themselves aren't blessed as being bootable for any specific OS. An OS may be blessed (tagged as bootable), but not drives.

    One of the characteristics of Startup Manager that makes it not quite as usable as it could be is that it will display only the last OS used for booting for any given volume. This means that if you have a volume which has both OSX and OS 9 on it, if you last booted to it using OS 9 then only OS 9 will be shown for it in Startup Manager; likewise, if you last booted to that volume using OSX, then only OSX will be displayed for it. In this context a volume = an unpartitioned drive, or a partition of a partitioned drive.

    Not sure what the meaning is for the info that you garnered via printenv in Open Firmware. As far as the "tbxi" line item goes, this is the only reference to it that I could find in Apple's KBase -


    http://support.apple.com/kb/TA22535

    There's more info other places but I did not investigate it - just Google
    tbxi

    ***

    If you can boot the machine into OS 9, can you then select OSX as the boot OS?

    ***

    If you have not yet done so, running a disk utility program would not hurt - that can be OS 9's Disk First Aid (from an OS 9 Install CD, ideally an OS 9 or OS 9.2.1 install disk), OSX's Disk Utility (from an OSX install disk), or DiskWarrior (while booted to its CD).

  12. 0

    Jim Epler

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks, Don. I've made some progress. I booted in target mode and selected my primary OS X drive as the startup volume. This fixed the OS X boot problem and I'm now able to boot into OS 10.4.x, again. After some further research, I came to the conclusion that, after following instructions on Bombich's site (
    http://www.bombich.com/mactips/openfirmware.html) to "rebless" the System Folder, I think I may have missed an apostrophe in the command which caused the problem of the quotations marks. So that's fixed.

    My OS 9 System Folder resided on a separate physical hard drive (250GB) so it never shared the same physical location as my OS X System. I wondered if my OS 9 boot problem stemmed from the fact that the drive was so big, so I threw in an old 80GB SCSI drive, formatted and installed OS 9.2.2 on this 3rd drive to see if I could boot into OS 9. It worked and I can now boot to OS 9 on this 3rd SCSI drive, but when I'm in the Finder I can't select any OS 9 menus (although I can move my mouse freely about) so it's not usable. Strange....

  13. 0

    Don Archibald

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi, Jim -

    My OS 9 System Folder resided on a separate physical hard drive (250GB)...

    OS 9 can not be used for booting if the volume it is on is more than 200GB.


    Article #HT2544 - Using 128 GB or Larger ATA Hard Drives

    This limitation does not apply to OS 9 when used as Classic within OSX; it applies only when OS 9 is used for booting.

    ...I can now boot to OS 9 on this 3rd SCSI drive, but when I'm in the Finder I can't select any OS 9 menus (although I can move my mouse freely about) so it's not usable.

    • Have you tried booting to that OS 9.2.2 with Extensions Off (holding down the Shift key from the beginning of booting)? If the menus are then accessible to the mouse, that would indicate there is an extensions conflict of some kind.

    There are some known problem causers in 9.2.x; if you have any of these, try disabling or removing them - IdleTime (extension); N2MP3 (extension); and True Finder Integration (control panel).

    • When the menus are not responsive, are other items (like drive icons, folders, or files) selectable and responsive to mouse clicks?

    • Are you using an Apple-brand wired mouse? If you are using a non-Apple mouse, or a wireless one, additional software (software not part of a standard OS 9 install) may be needed.

  14. 0

    Jim Epler

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ahhhh.... I had no idea about this limitation with OS 9 and large drives. This is has been the cause of much of my frustration. Okay. Thanks!

    Yesterday I decided to partition my large 250 GB drive into 3 volumes. I installed Panther 10.3.8 on the first 70 GB volume and OS9 on a second 25 GB volume. The 3rd and remaining partition will be just used for data storage. My other 300 GB hard drive is now solely running Tiger 10.4.11. It seems that the bootBlocks command is available in 10.3.x but not 10.4.x (as well as some other stuff), so I decided I probably should have both 10.3 and 10.4 available just in case. I moved the OS 9 System from my SCSI (now just data storage) and on to the OS9 partition and blessed the 9 System Folder.

    I figured I'd be home free but after trying to boot into OS9 on the new partition I was greeted again with the blinking question mark. I'll probably next try a clean install of OS9 from software CDs to see if that fixes it, and then I'll re-address the problem of the clickable menus by doing what you suggest and turning off extensions, using an Apple mouse (I'm using a Logitech), etc.

  15. 0

    Jim Epler

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I booted with extensions OFF this time and lo and behold, I'm able to access all menu items in OS 9. So, it is definitely an extension conflict. I guess my next question is how best to resolve it? I don't see any of the 3 listed as "problem children," so what is my next step? Do I have to go one-by-one and enable/disable, reboot to figure out the culprit? This will take a lot of time as I probably have over 100+ extensions listed!!!! I haven't troubleshooted this type of problem in OS 9 so I'm a bit out of my comfort zone...

  16. 0

    Grant Bennet-Alder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You debug this sort of problem using a half-interval search.

    Divide the total into two groups (roughly in half).

    Install one group, uninstall the other group.

    ? Problem persist ?

    - Yes: problem is in the Installed group. Divide the installed group in half and do it all again.

    - No: problem is in the uninstalled group, swap with the Installed group and proceed.

    You may find it helpful to print out a list of all installed extensions and mark it up with a pencil as you go along. I know that sounds archaic, but it works well while you remove and install portions of your computer's brain.

  17. 0

    Jim Epler

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Okay, then that's how I'll proceed. I was hoping there might be a quick way to look at the list globally using a third party tool to identify a conflict (sort of like device manager in Windows) to eliminate this little game of "hide and seek." I'm just SO glad I can now see the light at the end of the tunnel! Thanks, Grant!

    Message was edited by: Jim Epler