NeXT
Veteran Member
Okay, so the console issues are totally sorted out on the VAXstation 2000 but now I'm scratching my head on getting it to boot. Originally it came with the hard drive removed but I tracked down and reinstalled the original RD32 drive in the hopes there's still an install on it. On power-up you get the following:
For comparison to a machine which completely works (my MicroVAX2000, which is the same machine but at least boots up to OpenVMS)...
My assumption as I can't find anything to reference is that the lines E, D, C, 7, 6, 1 refer to faults detected followed by a code to narrow down the fault (again, can't find any documents). Reading from this document however, E and D refer to the RTC and NVRAM (because the battery is most likely dead), C refers to the serial controller (neither system has the keyboard or mouse installed so it might be that), 7 is the disk controller (I'll get to that in a moment), 6 is the SCSI controller but neither box uses that so I'm unsure what it's upset about and 1 refers to the ethernet controller which both machines have a problem with???
Anyways, when I reinstalled the RD32 I followed the instructions here and jumpered the drive to DRIVE SELECT 3. I only seem to get the "? 7 0090 7750.7751" line when it's jumpered this way.
So ignoring the bad nvram I still cannot boot the machine. "b <enter>" should start it but it sits for about 30 seconds , blinks the light on the hard drive and then tries booting from ESA0 (the network)
So I run TEST 70 which is the ROM formatting utility.
Well the machine not only knows there's a drive installed but it can even autodetect its parameters but because I don't want to format (yet) I exited out and tried TEST 71 which is a drive verify test.
Now suddenly it can't see a disk again and fails.
It's also worth noting at this point that the RX33 is being detected..
...however because I'm not wanting to unintentionally nuke the RD32 I'm leaving that alone for now.
Is anyone with more experience with the ROM prompt able to give me some assistance?
Code:
KA410-B V2.2
F...E...D...C...B...A...9...8...7...6...5...4...3_..2_..1?..
? E 0040 0000.0045
? D 0050 0000.0005
? C 0080 0000.4001
? 7 0090 7750.7751
? 6 00A0 0000.4001
?? 1 00C0 0000.7004
>>>For comparison to a machine which completely works (my MicroVAX2000, which is the same machine but at least boots up to OpenVMS)...
Code:
KA410-A V1.2
F_..E...D...C...B...A...9...8...7...6...5...4_..3_..2_..1?..
? E 0040 0000.0045
? D 0050 0000.0005
? C 0080 0000.4001
? 6 00A0 0000.4001
?? 1 00C0 0000.7004
>>>My assumption as I can't find anything to reference is that the lines E, D, C, 7, 6, 1 refer to faults detected followed by a code to narrow down the fault (again, can't find any documents). Reading from this document however, E and D refer to the RTC and NVRAM (because the battery is most likely dead), C refers to the serial controller (neither system has the keyboard or mouse installed so it might be that), 7 is the disk controller (I'll get to that in a moment), 6 is the SCSI controller but neither box uses that so I'm unsure what it's upset about and 1 refers to the ethernet controller which both machines have a problem with???
Anyways, when I reinstalled the RD32 I followed the instructions here and jumpered the drive to DRIVE SELECT 3. I only seem to get the "? 7 0090 7750.7751" line when it's jumpered this way.
So ignoring the bad nvram I still cannot boot the machine. "b <enter>" should start it but it sits for about 30 seconds , blinks the light on the hard drive and then tries booting from ESA0 (the network)
So I run TEST 70 which is the ROM formatting utility.
Code:
>>> test 70
KA410-A RDRXfmt
VSfmt_QUE_unitno (0-2) ? 0
VSfmt_STS_Siz ............. RD32
VSfmt_QUE_SerNbr (0-999999999) ? ^C
VSfmt_RES_Abtd
84 FAIL
>>>
Code:
>>> test 71
KA410-A RDver
VSmsv_QUE_unitno (0-1) ? 0
VSmsv_STS_Siz .????
VSmsv_RES_ERR #2
84 FAIL
>>>It's also worth noting at this point that the RX33 is being detected..
Code:
>>> test 70
KA410-A RDRXfmt
VSfmt_QUE_unitno (0-2) ? 2
VSfmt_QUE_RXmedtyp
( 1=RX33 ) ? 1
VSfmt_QUE_RUsure (DUA2 1/0) ? ^C
VSfmt_RES_Abtd
84 FAIL
>>>Is anyone with more experience with the ROM prompt able to give me some assistance?
