Been out sick.  Sorry about the slow reply.

At 11:28 PM -0800 1/26/01, James Tuman Nelson wrote:
>Chris Tribo wrote:
> >
> > on 1/26/01 4:07 AM, James Tuman Nelson at jimtnelson@earthlink.net wrote
> > something like:
> >
> > > I connected the keyboard directly to the 7500, bypassing the monitor,
> > > with no luck.
> > > I tried this with and without the System Disk (modified) patches.
> > > I am not using an extension cable, just the stock configuration.
> > > I also set the monitor to 66Hz and 640x800 under MacOS.
> >
> >     Uh, 640x800 is not a valid resolution. The 1710 _should_ multisync to
> >         60-85Hz Vertical, 30-110kHz Horizontal, and 640x480-1600x1200 IIRC.
> >         If it's trying to do 800x600 instead of 832x624 it might not work.
> >
>
>You are right, I made a typo.  I tried a lot of other resolutions, but
>no good.
>
> > > I set the input/output to kbd and /chaos/control and auto-boot? off.
> > > When rebooting, the system stops at OF, the monitor screen lights up,
> > > but no output.
> >
> >     Could very well be an invalid sync rate, can you use the monitors menu
> >         system and see what it's trying to drive the display at? I forget
> >         if the 1710 could do that or not...
>
>I tried several sync rates, setting them under MacOS.

That's why I said to disconnect the ADB cable from the monitor. 
Without it the Mac can't tell it isn't just a dumb PC monitor and the 
monitor can't tell it isn't connected to a PC.  The monitor front 
panel controls should act normally and bring up some ugly, but 
functional menus for the usual configuration stuff (instead of 
bringing up the Monitors control panel inside MacOS).

Setting the resolution under MacOS should then be completely 
irrelevant.  When you reboot to OF you revert to 640 X 480 @ 66 Hz. 
(We're talking a 7500 with OF 1.0.5 here remember.)  The monitor 
should see the frequency of the sync pulses and adjust without any 
required intervention.  Looking through the menu's can hopefully 
confirm this though (as suggested above).

> >     Then try resetting your monitors controller with Command-Option-A-V
>
>That is a new one to me.  I will try it.  Someone suggested that the
>output might be off screen, or outside the window, and resetting a few
>things might bring it back in.

This is a new one for me too.  Did it do anything?

>Does any one know if  a low nonvolatile ram battery voltage might be 
>a problem?

No, but I doubt that anyone could rule it out.  A low battery could 
do all sorts of strange things, at least in theory.  FWIW I have a 
7500 and 8500 and they both have the original batteries still. 
They've both been kept powered on most of the time though.

I think I said this already, but try to debug this problem in OF 
directly.  I think NetBSD has nothing to do with it, and just 
inherits a messed up configuration.


Signature held pending an ISO 9000 compliant
signature design and approval process.
h.b.hotz@jpl.nasa.gov, or hbhotz@oxy.edu