Subject: Re: CMD qbus scsi issues
To: Tom Ponsford <tponsford@theriver.com>
From: Lord Isildur <mrfusion@uranium.vaxpower.org>
List: port-vax
Date: 01/31/2003 18:09:41
cabling is not the issue here, as the device works perfectly with one OS
and bombs with the other, even when the only difference physically is
swapping a disk in the same enclosure... the uvax-III kit is basically
the metal s-box plate which has C50's on it as opposed to an IDC connector
right on the board, which is what all the pdp11/uv2 versions had. i
drilled out the rivets on one of my 223's and replaced the s-box plate with
a metal spine from some other dead qbus card, to properly mount it in my
ba123 years ago... it was quite happy.
isildur
On Fri, 31 Jan 2003, Tom Ponsford wrote:
> I picked up a MV 3600 a few months ago at the UA auction that had a CMD
> CQD 220/223 mscp scsi adapter. After ;putting 1.6 on it. I compiled
> several programs for over
> 36 hours without a hiccup. I did have problems with a NFS mount when
> ximit died.
>
> An interesting item is in the CMD Users manual which I noted:
>
> "The CQD-223 consists of the CQD-220 and a microvax III adapter kit.
> A shielded SCSI cable (with shielded connectors) is required to
> connect the
> CQD-223 to scsi devices."
>
> As I recall I once had another CMD scsi->mscp controller and disk that
> acted
> flacky until I replaced the SCSI cable with a newer one and the problem
> went away.
>
> Tom