On Wed, 20 Dec 2000, Chuck McManis wrote:

> When you run mopd use 'mopd -d' initally (or "mopd -d -d" as more "-d" 
> options get you into higher diagnostic levels). WHen your vax tries to boot 
> it should show up on the tty where mopd is running.
> 
> Most common problem is that mopd wants things in all UPPPERCASE like 
> MOPBOOT.SYS even though you type the name to the vax in lower case.

Also, beware that trying to boot netbsd.ram.gz won't work, as it doesn't
have support for the 4000/200 built in.

Netbooting a generic kernel and nfs mounting root works great,
though.  Beware that the mopd that is distributed with 1.5 doesn't work,
either - you'll have to compile mopd from -current (or, at least I
did) due to a PR with mopd (bin/11253 - closed, but not in 1.5, perhaps in
-release?)

With the mopd change, and booting a generic kernel, my 4000/200 works
great.  I've yet to attempt a manual install due to lack of time, so I
can't vouch for anything past that yet.

-Jon
 --------------------------------------------------------------------
 "Trout are freshwater fish, and have underwater weapons."
 "Zing, zing zing zing!"
 "Keep away from the trout."
 -- The opinions expressed are not necesarily those of my employer --
 "Who stole my lawn?"