If anyone has used 1.6B4 to do a MOP nfs install to local DSSI drive, 
please tell me how-to!

I have a 4000-200 and a 4000-705A, both in BA440 cabinets.

I use MOP to install from an Intel box as server.  Received 1.5.2 on CD, 
running 1.5.2 on the Intel box.

The 4000-200 has a KFQSA connected to a DSSI RF73.  Ditto the 4000-705A 
configuration.

When I do the MOP install of version 1.5.2, on the Vax 4000-200, everything 
works AOK.  I can install to the local DSSI drive, shut everything down, 
and boot from the local DSSI drive (DUA0).

When I do the MOP install of version 1.6B4 on the Vax 4000-200, it seems to 
install correcty, will partly boot from the hard drive (DUA0), and stops - 
when trying to open netbsd, netbsd.vax, netbsd.old, etc. etc.  It says 
"device not configured".

When I do the MOP install of version 1.6B4 on the VAX 4000-705, I get the 
identical situation as 1.6B4 on the 4000-200, "device not configured".

So, I used the 1.5.2 installation (netbsd.ram and sysinstall) to put the 
1.6B4 tarballs on the 4000-200.  Eureka!  I have 1.6B4 running on the 
4000-200, and it will boot from DSSI.

Then I removed the RF73 from the 4000-200 and installed in the 4000-705A. 
 Same boot problems as before, "device not configured".

Additional information:  DEC boot to the >>> prompt disgnostics say I have 
a KA-692 CPU, but the netbsd boot during nfs boot (netbsd ramdisk) says I 
have a KA694.  Do I have a 705A or a 700A (cabinet says 705A)?

Any clues?

I'm something of a Unix newbee, I understand disklabel -B etc but haven't 
attempted to compile a kernel (yey!).

I'll try to get screen captures for the next go-round.