Subject: Re: VS2000 bits
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
From: Sheila //or// Bob (depends on who's writing) <email@example.com>
Date: 09/13/1998 16:04:33
I get a chance to help you after the zillions of times you have helped
I have been filing all the 2k and 3100 stuff seperately - I will get my
3100 running soon. Right after my ppp on uVII!!
so many things, so little time, so little beer!
der Mouse wrote:
> Well, thanks to you people, I know have a better idea what my VS2000 is
> like. I managed to get it opened right up, after having no luck
> getting so much as a ROM banner out of it, either on the printer-port
> serial console or the graphics console.
> And I once again I find myself in need of either some kind of VS2000
> FAQ or help from the kind souls on port-vax.
RE: VS2000 tests and other oddities?
Mon, 25 May 1998 03:13:59 +0200
Gunnar Helliesen <firstname.lastname@example.org>
"'Brian D Chase'" <email@example.com>, NetBSD/vax
Mailing List <port-vax@NetBSD.ORG>
Brian D Chase wrote:
> I was poking around for various test numbers and letters on a
> VS2000 when
> I came across the most interesting test 90. It obviously has
> to do with
> stats on the ethernet device, but is there anything else it does?
I got this through someone on this list, I think, but now I can't
remember who or where or ... aarghh! my mind is going! ....
The power-up testing and "console-mode" utilities for the 2000's.
* KA-410-A is a multi-user, uVAX2000 system. -B is the single user
* VAXstation 2000. V1.2 is the ROM rev level. NB for VAXstation
* 4- or 8-plane graphics board, v2.1 is required.
* In the count-down a "_" means the thing wasn't found for test.
? E 0040 0000.0005 < clock battery need charge.
? C 0080 0000.4001 < odd-ball terminal as console(I get it
with a Rainbow used as console,but it works just
If you type T 50 at the >>> prompt should get a display like:
* the ID above is the ethernet hardware adress.
?? MONO 0001.F002
* the base (mono) video option. Naturaly not found on a microVAX,
* only a VAXstation.
? CLK 0000.0005
* This is saying that the battery which maintains the clock has
* out of electricity... leaving the Box powered-up for 24 hours
* should get a display:
CLK 0000.0001 which is the healthy sign.
* the Non-Volatile Read-only memory is healthy.
? DZ 0000.4001
00004001 00000001 00000001 00000001 00000000 00000000
* the DZ display's six eight digit numbers refer to the 4 serial
* lines, the keyboard, and the mouse or tablet.
* A uVAX2000, should always show 00000000 00000000 as the last two
* the .0001 means that the MEMory is healthy, the 0006, and the
* 00600000 both tell you the box has 6 meg of memory. N.B. this is
* hex. If the first line,second half, is not .0001, there will be
* a second eight digit number on the second line telling you the
* details of the memory fault.
* Memory management
* Floating Point
* Interval Timer
00000000 00000000 00000000
* the Hard Disk Controller is healthy, but it can't see any disks
* which is recognizes as ready to use. Where it does see disks,
* the second line shows their size (in Hex) inorder DUA0,DUA1,DUA2
* RD32's=40Mb or 146B8,RD53's=71Mb or 22000, RD54's=159Mb or 4C437
* RX33's are either 1200KB or 960, or, if using RX50's, 400KB or
FFFFFF03 01000001 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05
* the tape-drive port is healthy and it sees a good TK50-z drive
* talk to.
* Main system test is OK.
8PLN 0000.0001 V1.4
* the test found a healthy 8-plane graphics card, and Vx.x shows
* version number. Could alternatively be 4PLN for the 4-plane
NI 0000.0001 V1.3
* a healthy ethernet card was found, with its version number.
* Note, there must be a terminator, or a terminated ethernet cable
* for the card to test healthy.
Test 51 sets the NVR default Boot device.
Valid choices may be DUA0,DUA1,DUA2 (Disks,where available),
MUA0 (Tape) or ESA0 (Ethernet) also .... means no
You type in T 51 and the reply shows the current setting, youi then type
what you want it changed to.
.... ? >>> DUA1 This changes No Default, (....) to Disk
Should you want to clear the default back to none, enter only one
Test 52 sets the NVR default Boot flags.
Test 53 sets the NVR default recovery action flags.
Test 54 sets the keyboard language.
Tests 60,61, and 62 are only used on a VAXstation where no graphics card
T 60 - Displays alignment circle and cross hatch
T 61 - Displays a screen full of Es
T 62 - Displays a white screen
To run the hard disk formatter :
>>> T 70
VSfmt_QUE_unitno (0-2) ? 0
Note 1. The T 70 format is not a valid option to format an RX50 floppy,
but _is_ valid to format an RX33 floppy.
Note 2. The T 70 format utility will format non-Digital disks, but will
go into a series of questions for which you need the appropriate
How to Format a Non-Digital Hard Disk
If the hard disk installed on your system is not a DIGITAL disk, or if
it is a hard disk that the formatter program doesn't recognize, the
formatter goes into a query mode. This query mode allows you to input
specific data about the drive so that the format program can format the
THE FORMATTER PROGRAM DESTROYS ALL USER DATA ON THE DISK.
To run the formatter, type "TEST 70" and "RETURN" at the console prompt
">>>". The following text will be output to the screen:
To format the hard disk in the expansion box type "0" and "RETURN",
to format the hard disk in the expansion box, type "1" and "RETURN".
*N.B. I have entered numbers which are the published, presumeably
*numbers to format an RD32 (aka Seagate ST251). Some of these numbers
*easily obtainable, others.....well, I dunno where they come from.
If the hard disk is not recognized by the formatter routine, the
following output will be seen on the screen:
VSfmt_STS_Siz............. ???? [unknown disk drive]
VSfmt_STS_EntUIB [formatter needs disk specific information]
At this point, the formatter is in the query mode. It will ask for
specific information about the disk drive to be formatted. All the
requested data can usually be found in the technical manual for the
drive in question.
Here is a brief explanation of the data needed to format the drive:
xbnsiz :=54 [enter the number of transfer blocks]
dbnsiz :=48 [enter the number of diagnostic blocks]
lbnsiz :=83236 [enter the number of logical blocks]
rbnsiz :=200 [enter the number of replacement blocks]
surpun :=6 [enter the number of surfaces per unit]
cylpun :=820 [enter the number of cylinders per unit]
wrtprc :=820 [enter the write precompensation cylinder]
rctsiz :=4 [enter the size of the revectoring control
rctnbr :=8 [enter the number of copies of the RCT]
secitl :=1 [enter the sector interleave]
stsskw :=2 [enter the surface to surface skew]
ctcskw :=9 [enter the cylinder to cylinder skew]
mediai :=627327008 [enter the MSCP media ID]
* Note this number is not dependant on disk geometry, but is the
* magic number for VMS to report on the type of disk.
* 627327008 = RD32, and 627327010 = RD33 (I think!)
At this point, the formatter exits the query mode.
The next output to the screen is:
VSfmt_QUE_SerNbr (0-999999999) [enter the serial number for
[or enter a unique number
for each unit]
VSfmt_QUE_RUsure (DUAx 1/0) ? [where x equals the unit number]
[enter 1 for YES, 0 for NO]
The formatter is now running, and the output should look like:
VSfmt_STS_RdMbb.............OK [manufacturer's bad block located]
VSfmt_STS_FMTing............OK [disk formatted OK]
VSfmt_STS_ChkPss............OK [check pass completed OK]
VSfmt_STS_BBRvec := x [number of bad blocks revectored]
VSfmt_RES_Succ [disk is successfully formatted]
At this point, the disk has been succesfully formatted, and the
console command prompt is displayed.
Note:- Another way of formatting an unknown disk is by use of either a
uVAX or PDP-11 with an RQDX-3 disk controller, and maintenance
software. The resulting format is acceptable to the 2000 box.
Also, RD52 = Quantum Q540,RD53 = Micropolis 1325,RD54 = Maxtor XT2190,
RD31 = Seagate ST225,RD32 = Seagate ST251, RD33= Miniscribe 3085.
A related utility is T 71, which is the fixed disk verifier. This will
test (only for reading) a disk.
The tests of the 8n sequence are only applicable if there is a 4-plane
8-plane graphics option board present.
T 80 - Displays Circle cross-hatch (colour & mon monitors)
T 81 - Displays Screen full of Es (colour & mon monitors)
T 82 - Displays White screen (colour & mon monitors)
T 83 - Displays 4-bar colour bar
T 84 - Displays Red screen
T 85 - Displays Green screen
T 86 - Displays Blue screen
T 87 - Displays 8-bar clour bar
T 88 - Displays Gray scale (colour & mono monitors)
Test T 90 tests the Network (Ethernet).
Gunnar Helliesen | Bergen IT Consult AS | NetBSD/VAX on a uVAX II
Systems Consultant | Bergen, Norway | '86 Jaguar Sovereign 4.2
firstname.lastname@example.org | http://www.bitcon.no/ | '73 Mercedes 280 (240D)
> After trying it out of the box (ie, the cpu cards in their metal
> brackets loose, with everything standing on its end), I turned it off,
> felt the foil side of the main card, and found that *something* was
> running hot enough to concern me. So I managed to take it the rest of
> the way apart, and found it's composed of four pieces: the main cpu
> card (with two chips that look like MicroVAX CPUs from my uVAX-II days,
> which were what were running hot), a piece marked "NETWORK INTERFACE",
> a piece marked "2/4 MB MEMORY OPTION", and a piece marked "VS40X 4
> PLANE COLOR OPTION". Figuring that if they were marked OPTION, they
> were optional, I laid these last two aside, connected the network
> interface back up with its ribbon cables, and turned the thing on
> again. (I was careful to stand it so the CPUs, with their cooling
> towers, were in the exhaust airflow from the power supply fan.)
> Now I get something. Four "ESC [ c" terminal type probes, a banner
> "KA410-B V2.1", a countdown and a failure:
> ? E 0040 0000.0045
> ? D 0050 0000.0005
> ? C 0080 0000.4001
> ? 6 00A0 0000.4001
> ?? 1 00C0 0011.700E
> After the E on the last line, I get CR LF ^Q ESC \ ESC [ 4 i ^Q CR LF
> and the text "?15 CORRPTN", then the >>> prompt.
> Of course, I hardly expected it to boot, since I had no possible boot
> medium hooked up. But when I did have it put together, I got a boot
> failure similar to this, ending with the ?15 CORRPTN banner. (The
> terminal I have connected takes the ESC \ as a clear-screen, so I
> couldn't tell what came before it. Now, I have the terminal in monitor
> The CPU chips are running hot enough that, despite being directly in
> the airflow from the fan, I can't stand to leave my finger on their
> little cooling towers for more than a few moments. Hot enough to worry
> me, certainly.
> I've seen references to a T command, which is not something I'm
> familiar with from the MicroVAX-II; I also have no idea what the boot
> device names are for the VS2000. Is there a command summary I could
> pick up from somewhere?
> Does anyone know whether it's normal for the CPUs to run that hot?
> der Mouse
> 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
real address is shsrms at erols dot com
The Herbal Gypsy and the Tinker.