Now that I think of it, I did have 1.5.2 on it before I upgraded to 1.6.
As I recall there were no problems either, but I didn't do a big compile
on it. If it is an OS problem, it is before 1.5.2.

I think I will dig the 3600 out of mothballs, I just got a big rack with 
an AS2100
on the bottom. I think I can get the 3600 (ba123) in the top half.
Now if I can just get a Sbox cab for my 4000 cpu board which is in a 
ba23,, I can stick it in
along with 2 more memory boards and have a "real fast" qbus   and at 
least have
a "tower O' decs" LOL.



Lord Isildur wrote:
> 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
> 
>