> > OK, I've verified that  it actually does get at least  as far as calling
> > harry().  
> 
> That's a good start...  That means that it's probably getting to the
> jump into the kernel.  Take a look in machdep.c.  There's a function
> there called gray_bar() that's ifdef'd out these days.  You can include
> that function and then put "jbsr gray_bar" into locore.s to trace where
> you go from there...  It's painful, I know...  You can also, of course,
> call gray_bar() and gray_bar2() from C--I expect you're hanging in
> setmachdep() or something like that...
Well, I can't  compile any kernels because I can't boot, and I doubt that I
could display any gray bars if I can't control the console.  How can I trace
into the boot code without affecting the environment.  Using the
debugger won't work.   Is this something  that MacsBugs can do for me.
I've never used MacsBugs, so any pointers would be helpful!