Thanks for identifying how it possibly could have happened. It kept nudging the back of my brain, and now I can lay it to rest!
But it will only come up once.
Easiest way I found to bring it up multiple times is use Windows Key-F1.]]>
Excellent! Oh, the evil plots one must ponder. (”You hear maniacal laughter in the distance…”)]]>
Oh yes, though in my recollection it was the TRS-80 which had a magic memory location which could fry the machine when the wrong value was poked into it. If the Atari had one, I don’t think I knew about it.
Nowadays I work on embedded systems, including the firmware for a Power Over Ethernet controller. 48 volts available at my slightest whim! By changing the software I can make the _other_ system catch fire.]]>
I am in the middle of a post about using software to damage hardware, a topic I wanted to write more on based on a mystery in my book about software that causes a cell phone to catch fire. From your comment on the Atari thread, I suspect you might be familiar with “the killer poke.” Ah, the days…]]>