After removing the Intel DX 486 card from my RiscPC (running RiscOS 3.6), the computer doesn't start up properly. Instead, it displays the text
POST in red.
What does this error message mean?
Retrocomputing Stack Exchange is a question and answer site for vintage-computer hobbyists interested in restoring, preserving, and using the classic computer and gaming systems of yesteryear. It only takes a minute to sign up.Sign up to join this community
On the RiscPC, "POST" stands for Power On Self Test. The POST sequence is performed on computers running RiscOS 3, and ensures that the computer is working properly before it starts up. If the computer fails this test, an error message will be displayed on the screen, informing you that there was a POST error.
You may notice your floppy-drive light flashing. After a POST error is detected, the floppy-drive light will output a sequence of flashes a little like Morse Code. The error code is a 32-bit binary number, where a long flash represents
1 and a short flash represents
0. Here are some common fatal error codes and their causes:
0000 0000 0001 0000 1001or
0000 0000 0001 0001 1001
0001 0000 0000 0100 1001or
0001 0000 0000 0101 1001
0010 0000 0001 0100 0001
Note that these error codes all have
0s at the beginning. You don't need to count exactly how many there are of these, so long as you have the end part of the code.
To reset the CMOS data to its default values, follow these instructions:
The error codes are designed so that each binary digit corresponds to a specific fault code. Some of the fault codes aren't errors; these are just informative. If a code is an error the text will be bold. The bits are numbered from right to left, where bit 0 is the right-most digit (the
0000 0000 0000 0000 0001).
0: Self-test due to power-on. This is normal.
1: Self-test due to interface hardware. This shows that the POST test wasn't started directly from the boot sequence.
2: Self-test due to test link. This means that you manually triggered the POST test (I think!)
3: Long memory test performed. This just tells you that nothing went wrong before the long memory test.
4: ARM3 fitted / ARM ID read and not ARM2. This gives information about the hardware. If you have an ARM2 installed and this shows up, there might be a problem, but likely not a major one.
5: Long memory test disabled. This is not a problem; it just means that the long memory isn't tested.
6: PC-style IO world detected.
7: VRAM detected.
8: CMOS RAM checksum error. The CMOS checksum is invalid, which means that the CMOS memory is corrupt. This can be fixed by resetting the CMOS data (see above). This error is often caused by a flat CMOS battery, so if the error persists after resetting the CMOS data, you might need to replace the battery.
9: ROM failed checksum test. This means that your ROM is corrupt. This might not be significant enough to cause much of a problem, but expect erratic behaviour and the occasional crash.
10: MEMC CAM mapping failed.
11: MEMC protection failed.
12: IOC register test failed.
13: Reserved code (RISC PC). This code should never appear. If it does, please ask a question about it!
14: VIDC Virq (Video Interrupt) timing failed. This means that things probably won't display properly on the screen, because the "draw screen content" timing doesn't line up with the actual screen refresh.
15: VIDC Sirq (Sound Interrupt) timing failed. This is similar to the Virq failure, but for sound. Audio might sound stuttery, or play in segments that are the wrong way around (e.g. 2143658709 instead of 1234567890).
16: CMOS unreadable. This probably means that your CMOS battery has leaked and damaged the CMOS chip itself. This is harder to fix, requiring not only a new battery but also a CMOS chip.
17: RAM control line failure. This means that the RAM control line is probably damaged, which is difficult to repair.
18: Long RAM Test failure. The long memory test from bits
19: Reserved code (RISC PC). This code should never appear. If it does, please ask a question about it!
32: Unused codes. These should all be
0, if they are shown at all.
i found following resource for Archimedes POST faults which might help: