> As it has been said before by Ken, any VS2000 even without the expansion
 > box has a SCSI-interface which can be used for disks, even if DEC didn't
 > use this interface for anything else but the SCSI-variant of the TK50.
 > I've checked this by connecting by connecting two disks (500MB and 2GB)
 > to a VS2000 and they worked! Thus the disksize should not be the problem.
 > 
 > One of the major problems with the support for VS2000 and the different
 > models of VS3100 is that these machines are quite different to the yet
 > supported VAXen, which yields in some changes to the main source tree. 
 > Thus these changes won't go into the main source tree until sometime after 
 > the 1.2 release of NetBSD.
 > 
 > Ciao,
 > 	bertram
 > 
 > PS: If this has not been stated before: support for VS2000 is more or
 >     less there, there are still some parts incomplete/unfinished, but
 >     the heart of it is already beating. Since support for 3100 will be
 >     derived from that, same/smiliar holds for some of the models of 3100.
 > 

	I'd like to echo what Bertram said, plus. Thanks to his hard
work and guidance, I have NetBSD running on a VS2000 with 6 MB memory,
RD54, and TK50 on the sortof-SCSI. Since the ethernet and NFS code work,
I have /usr mounted from a microvax II with an RA81. Leaves plenty of
space on the RD54 for swapping :-) But he's right - the source is hacked
pretty heavily in spots, and it'll be a while before it's ready for
the unified Vax source tree. I am in the midst of getting the bitmapped
display to work as the system console (current support is for one of the
rs232 lines as console). So you can add me to the "support/beta test" list.

_________________________________________________________________________
|   Mike Young     young@purdue.edu     Purdue University ECE Dept.     |
|   W. Lafayette, IN 47907-1285    http://dynamo.ecn.purdue.edu/~young/ |
_________________________________________________________________________