Re: DEC 3000 M500 CXT error ?
From: Robert Deininger (rdeininger_at_mindspring.com)
Date: 08/05/03
- Previous message: Bob Jenkins: "Re: Free UNIX for non-commerical use."
- In reply to: opcom: "DEC 3000 M500 CXT error ?"
- Next in thread: Jeroen M.W. van Dijk: "Re: DEC 3000 M500 CXT error ?"
- Reply: Jeroen M.W. van Dijk: "Re: DEC 3000 M500 CXT error ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 04 Aug 2003 21:06:58 -0400
In article <3F2DE050.D389A2D0@swbell.net>, opcom
<nounwantedmail_eccm@swbell.net> wrote:
>Well here's a good one for all the hardware wizards.. And I know someone
in this most wise and august group has got to know the answer.
>
>This questions' been floating around out here for a long time.. never
found an answer to this -only unanswered questions going back to 1998! So
it should be worthy of a challenge, finally put it to rest.
>
>--
>
>Firing up Ye Olde DEC3000-500 (Flamingo/Pelican), the self test is fine
except this error:
The model 500 is a Flamingo. Pelicans are the 3000-300 family. The
3000-400, -600, and -700 models are the Sandpiper family. Colletively,
they are the "birds"
>CXT ?? 000 0064
Thist is the built-in graphics device. I think it is equivalent to the
PMAG-BA turbochannel adapter.
I don't know this specific error. I have the model 400 service manual at
hand, but unfortunately the built-in graphics is the one thing that's
missing in all but the 500 and 500X models. So my manual is silent about
your error.
The TEST CXT command might give a slightly more detailed error message.
Are you using the serial console, or the graphics console?
What is setting of the CONSOLE environment variable?
What is the setting of the SERVER environment variable?
Is there a monitor connected to the graphics connector?
I've seen a number of old 3000-500 systems with CXT errors. They appear
to work, but the error keeps the system from booting automatically when
power is turned on.
I don't know if this is a design problem that shows up with old age, or a
configuration problem, or a common failure induced by some external
influence.
The CXT can tell if there's a monitor connected, as Stuart noted in
another reply. Make sure the monitor is connected when you run the
self-tests.
Here's something to try...
Use a serial console, such as a VT terminal. Set CONSOLE to serial, and
SERVER to 1. In this configuration, the firmware might treat the CXT
problem as an informational instead of an error, and auto-boot anyway.
Sandpipers will ignore a missing keyboard or mouse when SERVER is 1.
I'll scratch around in piles of old stuff at work and see if I can find a
model 500 manual. Maybe I can find the precise meaning of the error code.
>I am trying to get the DEC3000 M500 going for free to give to a new VMS
hobbyist, so any info on what this cryptic error means, and where I can
learn more, would be greatly appreciated. The machine seems to run in
spite of this,
>but I have only just installed VMS, no licences yet etc, so I can't say
what it might affect.
>
>I can't find the information on this anywhere, and don't have the manuals
on the old turbochannel machine. I don't really know what the CXT is! Hate
to have to pitch it, it's got a 19" CRT and all. And this guy NEEDS VMS.
He's
>using a MAC for goodness sakes!
Well, I'm typing this note on my Mac. Fine systems, but not as good as VMS.
- Previous message: Bob Jenkins: "Re: Free UNIX for non-commerical use."
- In reply to: opcom: "DEC 3000 M500 CXT error ?"
- Next in thread: Jeroen M.W. van Dijk: "Re: DEC 3000 M500 CXT error ?"
- Reply: Jeroen M.W. van Dijk: "Re: DEC 3000 M500 CXT error ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|