>> How the heck is a diagnostic ROM going to
diagnose a dead CPU? I
>> must be missing something here...
Yeah, I've said some stupid things on this list, and yesterday's was
record breaking.
On Wed, 28 May 2008, der Mouse wrote:
Well, if it's a little more than just ROM but fits
in a ROM socket, it
could, for example, notice a lack of read cycles. If it's enough more
than ROM it could run a CPU emulator and notice that it isn't obeying
the instructions it's fetching (though that's hard to do right, since
the ROM socket doesn't see things like interrupts or RAM).
Fischer's setup was just a ROM (EPROM?), plus he had a serial board that
was hardware configured for 9600, so that it would not be dependent on the
initialization code to setup the port.
Now, if you had a setup that connected to the bus, to the ROM sockets, to
the RAM sockets, and had a CPU plus connection to the 8088 and 8087
sockets, . . .
There was once a POST card that did CLAIM to test everything, in true
marketing form: "Power lights good, no Power On Self Test codes = "Bad
CPU", replace motherboard". Tony would be happy to know that they didn't
stay in business very long.
--
Grumpy Ol' Fred cisin at
xenosoft.com