3 ms·
So a funny story which relates. The actual "feature" of resetting the system (sending it the appropriate non-maskable interrupt) was handled in early PC's by th
by ChuckMcM 13y ago
So a funny story which relates. The actual "feature" of resetting the system (sending it the appropriate non-maskable interrupt) was handled in early PC's by the keyboard controller, which was a chip on the motherboard. I was at a company and we were building our own "lights out" server system, no keyboard, so the hardware engineer deleted the keyboard controller from the schematic. The issue was that the BIOS we got from AWARD couldn't deal with the fact that there was no controller, it would enable the interrupt anyway and I guess the pin was simply not connected on the interrupt controller so we'd get random interrupts. Back and forth half in English and half in Chinese to get the BIOS fixed, every time an update came it would be broken again. It became such an issue that the HW engineer built a small board that had the controller on it that could be 'blue wired' into the circuit so that we could continue to debug/build stuff while the BIOS guys were in a 'broken' cycle. In later versions we switched to AMI and had a much better time of it but sheesh it was a pain.