Xref: utzoo comp.sys.dec:4027 comp.os.vms:30356
Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!rutgers!njin!spcvxb.spc.edu!terry
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr)
Newsgroups: comp.sys.dec,comp.os.vms
Subject: Re: SCSI disks on a MicroVAX 2000
Message-ID: <1990Sep16.235416.519@spcvxb.spc.edu>
Date: 16 Sep 90 23:54:15 GMT
References: <1712.26ef97e1@hamavnet.com> <1669@shodha.enet.dec.com> <7716@sunquest.UUCP>
Followup-To: comp.sys.dec
Organization: St. Peter's College, US
Lines: 24

> In article <1669@shodha.enet.dec.com>, alan@shodha.enet.dec.com ( Alan's Home for Wayward Notes File.) writes...
> 
>	I wouldn't trust it.  And of course any attempts to do so
>	will result in an unsupported configuration.  If something
>	breaks it may not be covered by any Field Service contract
>	that you have.

  More importantly, where would you find a device driver for the disk? You'll
need two, a regular one and one integrated into VMB (which is, of course, in
ROM on the 2000) if you want to boot from it.

  Just because a controller speaks SCSI out the device side doesn't mean
it is supported by the DEC generic SCSI support in later VMS V5 releases.
The generic SCSI is for supported SCSI interfaces on the newer systems.

  If you decide to live with the restriction of the disk being a non-system
disk and you do write a driver, you'll discover that the protocol is a bit
different in the 2000, and you'll need the source to the disk drive's firm-
ware and possibly some hardware mods to the drive. All in all, not a pretty
sight.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, US
	terry@spcvxa.spc.edu	(201) 915-9381