Frederick Bruckman wrote:

>If you can cpout the kernel, you can rule out the file system by
>booting from a MacOS file using the booter option, and running fsck.
>You could also do that with a gzipped kernel, but not with a tarred
>gzipped kernel. (That's why you should try to cpout.)
>

cpout succeeded.

>There is a known problem where the Booter gets confused if the kernel
>is not using a low numbered inode in the first cylinder. If that's the
>problem, and if you can boot from a MacOS file kernel, you might be
>able to fix this with

Boot stopped at:

fpu0 at mainbus 0 (mc68882)
boot device: sd1
root on sd1a dumps on sd1b
...and hangs

previously the boot found:
sd1 at scsibus 0 targ 6 lun 0: blah blah...

I finally found a reference to the fstat message in INFO - it says the msg
is harmless. Which unfortunately leaves me clueless...

Dan Killoran

______________________________________________________________________________
Got a device you would like to have run on the Mac? Call:
                 Daniel-the-Driver-Maker
      Fast service - accurate work - responsive support

         (Offer void wherever taxed or prohibited!)