On Tue, 7 Apr 1998, Dudley M. Bertram wrote:
> Brian D Chase wrote:

> Thanks for the suggestions so far. I should add that there is still a
> bootable VMS 5.4 O/S installation on the internal drive and that boots
> and sees both the internal and external SCSI disks with no problems
> at all. Any other possibilities ???

Maybe VMS doesn't detect that there's really a problem? :-)  NetBSD could
be broken, but in either case of it being broken hardware or broken NetBSD
I'm gonna bet that the quickest way to booting your VS3100 will be to
check the integrity of your 2nd SCSI controller and its device chain (2nd
SCSI controller is SCSI/B in the console boot program and ncr1/scsibus1 in
NetBSD/vax).  The 2nd SCSI controller is the one tied to the external SCSI
port on the back of the VS3100.

Could you give us a listing of what you get by entering the SHOW DEV
command at your ">>> " prompt?

> P.S. : So far I have had 2 requests to explain how I use a VMS based
>        system as the bootserver using MULTINET V4.0A. I was wondering
>        if this should be part of the netboot-howto....

Why of course it should.  VMS is in pretty common use amongst those
involved with the NetBSD/vax and VAX/Linux ports. I'm sure there are
people who've got VMS systems they'd like to netboot from.

-brian.
---
Brian "JARAI" Chase | http://world.std.com/~bdc/ | VAXZilla LIVES!!!