DataMuseum.dk

Presents historical artifacts from the history of:

Rational R1000/400 DFS Tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about Rational R1000/400 DFS Tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download

⟦624338255⟧ ERRMESS, TextFile

    Length: 3072 (0xc00)
    Types: ERRMESS, TextFile
    Names: »P2TYP.ERRMESS«

Derivation

└─⟦b4205821b⟧ Bits:30000743 8mm tape, Rational 1000, DFS, D_12_7_3 SEQ288
    └─ ⟦this⟧ »P2TYP.ERRMESS« 
└─⟦b434774df⟧ Bits:30000528 8mm tape, Rational 1000, DFS, D_12_6_5
    └─ ⟦this⟧ »P2TYP.ERRMESS« 
└─⟦bc1274df5⟧ Bits:30000750 8mm tape, Rational 1000, DFS backup from PAM's R1000
    └─ ⟦this⟧ »P2TYP.ERRMESS« 

TextFile

0	No errors detected by P2TYP.
1	TYP WCS Addressing error detected (P2TYP).
2	TYP WCS data bit error detected (P2TYP).
3	TYP WCS parity detection error detected (P2TYP).
4	TYP WCS RAM error. A cell in one of the WCS RAMS is either stuck
	high or stuck low (P2TYP).
5	The TYP board cannot load data into the WDR from the TYP BUS (P2TYP).
6	The TYP board cannot load correct parity into the WDR from the
	TYP BUS (P2TYP).
7	The TYP board cannot load correct parity into the WDR from the
	TYP BUS. No further isolation was done so the problem could be caused
	by any of the following: a problem on some other board connected to the
	TYP bus, a problem with the foreplane, or a problem with th TYP board.
	(P2TYP)
8	The TYP board cannot load data into the WDR from the TYP BUS.
	No further isolation was done so the problem could be caused
	by any of the following: a problem on some other board connected to the
	TYP bus, a problem with the foreplane, or a problem with th TYP board.
	(P2TYP)
9	The TYP board cannot receive data correctly from the FIU BUS (P2TYP).
10	The TYP board cannot receive data correctly from the FIU BUS.
	No further isolation was done so the problem could be caused
	by any of the following: a problem on some other board connected to the
	FIU bus, a problem with the foreplane, or a problem with th TYP board.
	(P2TYP)
11	The TYP LOOP COUNTER cannot be loaded correctly (P2TYP).
12	The TYP LOOP COUNTER cannot count correctly (P2TYP).
13	TYP LOOP COUNTER overflow does not work correctly (P2TYP).
14	TYP RF data bit error detected (P2TYP).
15	RF frame addressing error detected (P2TYP).
16	RF GP addressing error detected (P2TYP).
17	The NOVRAM returned a bad checksum when reading the BOARD REV
	address. (P2TYP).
18	RF parity checker error detected (P2TYP).
19	Logical ALU error detected (P2TYP).
20	The ALU cannot generate all ones or all zeros (P2TYP).
21	The zero drivers on the A_BUS cannot drive all zeros (P2TYP).
22	The PASS_A_HIGH or PASS_B_HIGH randoms do not work porperly (P2TYP).
23	Arithmetic ALU error detected (P2TYP).
24	An error in the ALU carry look ahead logic was detected (P2TYP).
25	A Register File location has a stuck at fault.
26	A problem was found in the logic that compares the parity bits coming
	out of the RF parity RAMS with the parity bits generated by the data
	on the A_BUS  (P2TYP).
27	A problem was found in the logic that compares the parity bits coming
	out of the RF parity RAMS with the parity bits generated by the data
	on the B_BUS  (P2TYP).
28	An error was detected in an address bit to one of the RF A parity RAMS
	(P2TYP)
29	An error was detected in an address bit to one of the RF B parity RAMS
	(P2TYP)
30	An error was detected in a location in one of the RF A parity RAMS. A
	cell in the bad RAM is either stuck high or stuck low (P2TYP).
31	An error was detected in a location in one of the RF B parity RAMS. A
	cell in the bad RAM is either stuck high or stuck low (P2TYP).«nul»