VAXStation 2000 (Was: TK50Z-GA and MicroVax 3100/90?)

From: Rod Young <rodyoung_at_shaw.ca>
Date: Wed May 22 12:33:01 2002

Funny! "dead sergeant". Nope, no counting down, no text other than the
lines with "?" marks (which do relate to the F...1) reporting errors.
*Only* errors (and their coresponding lines #'s F thru 1 IF an error/warning
was detected) are reported. I suspect I have a cable issue, as the other
expected console chatter isn't there. The system is likely reporting erros
out the 9pin, and doesn't know it's a console port... the pin 8-9 issue.

Thought I read somewhere, that a VS/MV2000 will not complete the POST
without happy ethernet termination. Could be wrong, but best bet is to
resolve the cable issue first, so I can see what's going on...

I might have odd thichwire cables, but then I have 3 of them ! hummmmm!

Anyone have an electronic copy of the VS system guides?
rod

----- Original Message -----
From: "Christopher Smith" <csmith_at_amdocs.com>
To: <cctalk_at_classiccmp.org>
Sent: Wednesday, May 22, 2002 11:01 AM
Subject: VAXStation 2000 (Was: TK50Z-GA and MicroVax 3100/90?)


> > -----Original Message-----
> > From: Rod Young [mailto:rodyoung_at_shaw.ca]
>
> > I actually have a DEC printer adapter (MMJ->9pin) which kind
> > of works in the
> > 9pin port on the VS2000 (I think) as it does display some
> > text... but not
> > all from what I can tell. Appears to only report lines with
> > "?" marks...
> > which are warnings and "??" marks I assume are errors. I get
> > a ?? on the
>
> It's odd that it works at all. :) Even stranger if you really
> are only getting lines with ? in them ;)
>
> Are you getting the "dead sergeant?" It looks like:
>
> >>>
>
> Do you see the system counting down in hex? (From F to 1, I think)
>
> > device line "1" (ethernet) and thought I read somewhere that
> > the thinwire
> > had to be terminated or forget it... and given the 9 pin
>
> Forget what? That will prevent an auto-boot, but won't keep the
> system from operating. It's not serious; just serious enough that
> they wanted to wait for some console input before going ahead. Go
> ahead and try booting it.
>
> > Yes, tried hooking up the AUI port too, but the thickwire
> > cables I have
> > won't fit! The gender is fine, but both the cables and the
> > AUI port on the
> > VS have the locking posts. I seem to be hitting dead ends
>
> That's odd :) They might be strange cables.
>
> > all over... but
> > will try to connect the thinwire to resolve the "??"
> > reported, and also make
> > a proper 9pin cable, then will see where that gets me.
>
> If you're getting the prompt, the counting in hex, and the
> CPU ID (something like KAXXX-XX, I think), you're doing
> fine in the cable department. I suppose if not, maybe the
> VAX prints its errors to all the ports on bootup. In that
> case, it won't take input from that port, and you'll need
> to get the right cable to tell it to boot. You still don't
> absolutely have to get the network connected, though.
>
> Chris
>
>
> Christopher Smith, Perl Developer
> Amdocs - Champaign, IL
>
> /usr/bin/perl -e '
> print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
> '
>


----------------------------------------------------------------------------
----
> --------------------------------------------------------------------------
-----------
>
> The information contained in this message is proprietary of Amdocs,
> protected from disclosure, and may be privileged.
> The information is intended to be conveyed only to the designated
recipient(s)
> of the message. If the reader of this message is not the intended
recipient,
> you are hereby notified that any dissemination, use, distribution or
copying of
> this communication is strictly prohibited and may be unlawful.
> If you have received this communication in error, please notify us
immediately
> by replying to the message and deleting it from your computer.
> Thank you.
>
> --------------------------------------------------------------------------
-----------
>
Received on Wed May 22 2002 - 12:33:01 BST

This archive was generated by hypermail 2.3.0 : Fri Oct 10 2014 - 23:35:17 BST