.--- [ On Mon, 6 Jan 1997, John P. Wittkoski wrote: ]
|
| You said you get to the "Enter shell or press reutrn for sh".
| Did it list any ADB devices? Look for lines that start with
| "adb:" or "pm:" before this point. It there ARE devices listed,
| the ADB stuff should be working ok. It may be some other issue
| that this causing the hang. 
`---

The following is_most_ of what booting returns regarding adb devices:

		[ top-o-screen, but there seems to be 
		some initial adb stuff going on	here ]

adb:  bus subsystem
Got following HwCfgFlags: 0xed00, 0x  401f3f, 0x  10932, 0x          0
mrg:  skipping egret setup
adb:  calling ADBReInit
adb:  using PowerBook 100-series hardware support
adb:  cleanup; nothing returned
adb:  200 dpi mouse at 3
mainbus() (root)
obio() at mainbus()
adb0 at obio() (ADB event device)

And thats all she wrote with the GENERIC-77 kernel.

With the PowerBook kernel I get the following (this is the kernel one
revision old, as the new kernel hangs during ADBReInit):

the same thing...

I did notice though, that just above the line that sks for my shell,
it says:

PRAM time does not appear to have been read correctly.
PRAM:  0x83da4f80, macos_boottime: 0x32d089e4

Could this have anything to do with it???

One last possible deviation from the norm.  Since I had only 2500k of
RAM available, I am running the Booter with only that much memory.  Is
it possible it is being flaky because of not enough RAM???


Daniel Lipton