Vaxstation 3100 - I have console access

[Bryan C. Everly]

Peter,

Thanks for the email.  My challenge is that this machine has a floppy and a
SCSI drive (both appear to be cabled correctly when I open things up) and
yet neither show up when I do a "show device" from the console.

>>> show device

 VMS/VMB  ULTRIX    ADDR    DEVTYP  NUMBYTES  RM/FX  WP  DEVNAM  REV
 -------  ------  --------  ------  --------  -----  --  ------  ---
 ESA0     SE0     08-00-2B-16-58-20

Therefore, when I issue a "boot" command, it's trying to boot from the
network and not from the floppy I currently have inserted.

Any ideas on troubleshooting I can do to determine why it isn't seeing
things on the SCSI bus?  (I'm assuming this is a SCSI floppy - please let
me know if I'm incorrect in that assumption.)


Thanks,
Bryan

On Thu, Feb 18, 2016 at 5:30 AM, Peter Coghlan <cctalk at beyondthepale.ie>
wrote:

> >
> > Hi everyone.  I'm hoping that one of the VAX experts out there can help
> me
> > figure out how to get my 3100 booting.  I managed to cobble together the
> > necessary cabling and was able to run a "TEST 50" from the serial
> console.
> > Unfortunately my Google-fu isn't sufficient to help me figure out what
> the
> > results mean.  Here is what I'm getting below.  Any ideas where my
> problem
> > lies?
> >
> > >>> test 50
> >
> >
> >
> > KA42-A  V1.3
> > ID 08-00-2B-16-58-20
> >
> >    MONO     0000.0001
> >  ? CLK      0000.0005
> >    NVR      0000.0001
> >  ? DZ       0000.4001
> >       00000001 00000001 00000001 00004001 00000000 00000000
> >    MEM      0010.0001
> >       01000000
> >    MM       0000.0001
> >    FP       0000.0001
> >    IT       0000.0001
> >    SYS      0000.0001
> >    8PLN     0000.0001  V1.3
> >    NI       0100.0001
> > >>>
> >
>
> Hi Bryan,
>
> This looks pretty good.  There are no double question marks which would
> indicate possibly more serious failures.
>
> ? CLK suggests the time of year clock is not set because the battery is
> bad.
> (I suggest removing the battery before it leaks.)
>
> ? DZ usually means that one of the serial ports could not be tested (the
> one
> you have the console terminal connected to).
>
> The other results are all good.
>
> What happens when you give it a BOOT command?
>
> Regards,
> Peter Coghlan.
>