Problems creating bootable OS 9.2.2 volume on FW HD

Hello,

I had a perfectly functional install of OS 9.2.2 on its own partition of
a LaCie FW HD, for use as Classic Mode when booted from a G4 Quicksilver
running OS X 10.4.10. I got the system on the Classic Mode volume to
boot the machine once, too, before I started messing around with things
(and I don't recall now what all I changed). Usually, I'm not too
destructive with OS 9.x, as I'm far more familiar with it than I am with
OS X. Well, I reached a point where trying to boot from that 9.2.2
volume got me the gray floppy disk with flashing question mark, forcing
a manual shutdown and startup.

I learned that I should not have formatted the partition for the Classic
Mode volume as "journalized," so I booted the machine from my OS 9.2.2
install CD and erased the volume, choosing Mac OS Extended format. After
succeeding in that, I performed a clean install of the OS, minus
Airport, Internet, and Speech items. I chose to update Apple disk
drivers. All went well, so I selected the new system in Startup disk and
restarted. This time, I got a screen with a blue folder with flashing
question mark on it. This reminded me that I'd forgotten a FW driver.

After booting from another system volume and dropping the LaCie Firewire
Support extension in the new Extensions Folder, I tried restarting again
to boot from the new system. This time, I again got the gray floppy with
flashing question mark.

I'm completely stumped at this point, as I didn't touch anything in the
newly-installed system other than to add the extension. I want an
install of OS 9.2.2 that I can use as Classic Mode under OS X, and to be
able to boot the Quicksilver from it and run under 9.2.2. I know this is
possible, because it worked before, but I'm clearly missing some detail
that I can't recall.

Any helpful advice that will further me along toward success with this
project will be greatly appreciated!

Thanks and happy computing,
Eric

Eric P. Peterson wrote:
> Hello,
>
> I had a perfectly functional install of OS 9.2.2 on its own partition of
> a LaCie FW HD, for use as Classic Mode when booted from a G4 Quicksilver
> running OS X 10.4.10. I got the system on the Classic Mode volume to
> boot the machine once, too, before I started messing around with things
> (and I don't recall now what all I changed). Usually, I'm not too
> destructive with OS 9.x, as I'm far more familiar with it than I am with
> OS X. Well, I reached a point where trying to boot from that 9.2.2
> volume got me the gray floppy disk with flashing question mark, forcing
> a manual shutdown and startup.
>
> I learned that I should not have formatted the partition for the Classic
> Mode volume as "journalized," so I booted the machine from my OS 9.2.2
> install CD and erased the volume, choosing Mac OS Extended format. After
> succeeding in that, I performed a clean install of the OS, minus
> Airport, Internet, and Speech items. I chose to update Apple disk
> drivers. All went well, so I selected the new system in Startup disk and
> restarted. This time, I got a screen with a blue folder with flashing
> question mark on it. This reminded me that I'd forgotten a FW driver.
>
> After booting from another system volume and dropping the LaCie Firewire
> Support extension in the new Extensions Folder, I tried restarting again
> to boot from the new system. This time, I again got the gray floppy with
> flashing question mark.
>
> I'm completely stumped at this point, as I didn't touch anything in the
> newly-installed system other than to add the extension. I want an
> install of OS 9.2.2 that I can use as Classic Mode under OS X, and to be
> able to boot the Quicksilver from it and run under 9.2.2. I know this is
> possible, because it worked before, but I'm clearly missing some detail
> that I can't recall.
>
> Any helpful advice that will further me along toward success with this
> project will be greatly appreciated!
>
> Thanks and happy computing,
> Eric

Sorry to waste the space, all...this was a ridiculously simple fix: Get
Info on the Classic Mode volume, uncheck "Ignore ownership on this
volume" and all is well :)

- E