1 Dec
2003
1 Dec
'03
9:37 a.m.
VMS can run on it. The backplane contains the KA-660
Board
with extra Memory (MS650), a KLESI- and a KFQSA-Controller
(DSSI), respectively. Typing "config" in the Console-Mode
gives out the adress fopr the SDI-Controller, if I type in
KLESI, KFQSA and KDA50. I installed the controller directly
behind the KFQSA-Board with the address given by config.
It's been a while now but I'm pretty sure that the KFQSA
pretends to be an MSCP device for each disk it has been
configured to recognise. So if you have configured your
KFQSA for two disks, it behaves as two KDA50s. The
exact addresses of these depend on how the KFQSA was
configured.
With your KLESI and KFQSA in the box, try a SHOW QBUS
command. I *think* the KLESI "lives" somewhere else in
the address space so it won't interfere. So you should
see your KFQSA appear once per configured disk. It's
quite likely (if things were working in this config) that
it will be occupying the first two MSCP disk device
addresses. In which case you set the switches on your
KDA50 to be the third such device.
Can the KDA50 be noticed by the "show qbus"
command ?
Yes, definitely. With the post-MicroVAX II systems, it's
one of the quick ways to see if the KDA50 works at all.
It's probably being masked by the KFQSA.
The cycling pattern described in the user guide
appears every
4 seconds, that's why I think that the boards work properly.
How do I know that the VAX found the KDA50 ?
Head over to http://vt100.net/manx and search for KFQSA and
then KDA50. You should be able to pick up scanned installation
manuals for both the KDA50 and the KFQSA.
Antonio
--
---------------
Antonio Carlini arcarlini(a)iee.org