> *embarassed* :)
>
> Well, sort of. If I type 'b' (single char commands only) it
> tries to boot but gives up saying 'none of the bootable
> devices contain a program image'. The activity LED on the
> RD52 (DUA0?) stays on and I can't get any signs of life out
I don't have any experience of the uVAX I, but the uVAX II
has no NVRAM and so it goes through a "sniffer boot"
where it looks for a bootable device in a particular
order. I expect that the uVAX I does something
similar.
I would exepct that you can type B DUA0 and it will
have a go (or complain that it doesn't understand you).
Some of the machines (like the VAX 8200) implemented
the console in microcode and so the commands were
extremely limited (as was the error reporting, which
you'll know if you ever used a VAX 8200!). However,
the uVAX II implemented the console in VAX macrocode
(i.e. ordinary VAX instructions) and I would have thought
the uVAX I would have done the same. Have a go
with B DUA0 (and then DUA1,2,3) and see if you
get any reaction whatsoever out of the disk or RX50.
Another approach might be to remove the uVAX I CPU and
memory and drop in a KA630 - or better yet a KA650/KA655.
That way you could poke around on the Qbus and see if
anything is visible, check for conflicts and try
to boot.
Antonio
--
---------------
Antonio Carlini arcarlini_at_iee.org
Received on Mon Jan 26 2004 - 17:05:27 GMT