[Simh] Lost rqb->rqd controller in V3.5.0?

[Schaffer Michael]

Hi There!

Actual we operate about 40 VMS 6.2 systems (SIMH-version 3.2.1) on
RedHat Linux Enterprise Ed. 3.0 and all works fine..
Now we are trying to replace our hardware (HP ML370 G4 with DL385), with
te goal to run 4 VAXen instead of 2 on each server.

After downloading and compiling the V3.5.0 our tests pointed out, that
the disks on rqb, rqc, and rqd Controller 
are not available at ">>>"-prompt.

Our config:

---part of vax.ini---

; enable controllers
set rqb ena
;
; define disk drives
set rq0 rauser=200
set rq1 rauser=4500
;
set rqb0 rauser=1000
set rqb1 rauser=3000
;
; attach disk drives
att rq0 /vms/v3.5.0/BIN/page.dsk
att rq1 /vms/v3.5.0/BIN/recover.dsk
;
att rqb0 /vms/v3.5.0/BIN/user.dsk
att rqb1 /vms/v3.5.0/BIN/data.dsk

---- show conf @ sim> prompt ----

RQ, address=20001468-2000146B*, no vector, 4 units
  RQ0, 200MB, attached to /vms/v3.5.0/BIN/page.dsk, write enabled,
RAUSER
  RQ1, 4502MB, attached to /vms/v3.5.0/BIN/recover.dsk, write enabled,
RAUSER
  RQ2, 159MB, not attached, write enabled, RD54
  RQ3, 409KB, not attached, write enabled, RX50
RQB, address=200000F4-200000F7*, no vector, 4 units
  RQB0, 1000MB, attached to /vms/v3.5.0/BIN/user.dsk, write enabled,
RAUSER
  RQB1, 3001MB, attached to /vms/v3.5.0/BIN/data.dsk, write enabled,
RAUSER
  RQB2, 159MB, not attached, write enabled, RD54
  RQB3, 159MB, not attached, write enabled, RD54
RQC, disabled
RQD, disabled

---> devices are present

---- show device in vms console mode ----

sim> b cpu


KA655X-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>sho dev
UQSSP Disk Controller 0 (772150)
-DUA0 (RA82)
-DUA1 (RA82)
-DUA2 (RD54)
-DUA3 (RX50)

Ethernet Adapter 0 (774440)
-XQA0 (08-01-2B-AC-AC-B1)
>>>

---> DUBn disks got lost.....

-----

Any suggestions?

Kind regards,
Michael Schaffer


PS: we tryed both images (v3.2.1 & v.3.5.0 compiled on Intel Xeon and
AMD Opteron) on both systems, 
the v3.5.0 image lost the disks on each system, the v3.2.1 instead works
fine...