At 1:13 AM -0400 7/17/00, Michael Wolfson wrote:
>At 9:21 PM -0700 7/16/00, Henry B. Hotz wrote:
>
>:)I'm in the same boat.
>:)
>:)I'm suspicous that it has something to do with the nvramrc patches,
>:)since it was after I downloaded System Disk and ran it that I started
>:)having these problems, but OTOH I have the same problem at home where
>:)I've only ever used Boot Variables.
>
>Zapping the PRAM will clear all nvram patches.  Command-Option-P-R.  After
>resetting the PRAM, all OF settings will be returned to default and it'll
>start booting MacOS.  So, you'll need to do the Command-Option-O-F again to
>set things up again.

And then I'll have to run System Disk or Boot Variables in order to 
get back into OF with kbd & /chaos/control.  Don't have a serial 
option handy here.

In case I didn't say so the main machine I'm worried about is a 7500 
with 604 (OF 1.0.5) and the 1.5 alpha tarballs from the iso image.  I 
think the install floppy used was the one from Feburary.

What I think is wierd is that everything seemed to be working fine 
until I installed MacOS on a spare 80MB disk and downloaded System 
Disk.  I was only able to boot into NetBSD after I set use-nvramrc? 
to false after that.  Of course I lost the more stable screen and 
presumably the power-on booting when I did that.

>I've never seen this before, but could it be related to having console set
>as screen/kbd?  Various 1.0.5 and 2.X machines have problems with
>screen/kbd and must use a serial port for console.

That's really not an appetizing option.  Thanks for reminding me though.


Signature failed Preliminary Design Review.
Feasibility of a new signature is currently being evaluated.
h.b.hotz@jpl.nasa.gov, or hbhotz@oxy.edu