You’ll never see a shorter wait loop than this one. <\/p>\n
It looks like this: <\/code> There is some sense to it. After all, it doesn’t need to check if a mag card is inserted into a card reader (it doesn’t have one). It doesn’t need to check if you’ve switched to PRGM mode (it doesn’t have one). This is one of the few calculators where you can almost make it this simple.<\/p>\n Why almost? Well, there is a small flaw in this loop. It’s easy to miss and, in the same circumstances and at the same time, I probably would have missed it too.<\/p>\n You see, to my amazement, the HP-21 had a software-driven low power display. I really thought this came in much later in the series. The classic series, before this, all had hardware driving the low power display. I’m pretty sure (guess but consistent with the release times) that the HP-21 was the first to move to this.<\/p>\n On the HP-21, all of the dots, except the real one, light up to show low power. I thought of an inverter or an XOR gate somewhere in the logic driving the decimal point line of the display and a voltage sensor driving it. If volts is too low then the output swaps. Dots get displayed where they wouldn’t be, and don’t where they would. It should be easy in hardware but they did it in software (saves some hardware and you already have a processor right there on the printed circuit board).<\/p>\n It’s quite possible that the idea to do it in software came up after the rest of the software, or this loop, had been written.<\/p>\n The obvious problem, now that I’ve mentioned it, is “what about low power?”<\/p>\n The calculator can sit in this loop, waiting for a keypress, until the battery runs out. The calculator is on. The display is on. Power is being consumed; but it only checks the low power situation after it gets out of this loop. If you don’t press a key, you’ll never know that the battery is about to run out.<\/p>\n An interesting aspect of the microcode. It’s not a significant glitch as it would be a rare problem in the real world, and you probably shouldn’t leave your calculator on if you’re not using it (pressing keys). However, it may explain a few occasions where you pressed a key on the real thing, the low power indicator came on, and it died immediately afterward.<\/p>\n
\n<\/p>\n\r\n\r\nC:\\Test\\hp21w>hp21w -d\r\n\r\nHP21w Ver 0.01\r\nCopyright 2018 Greg Sydney-Smith\r\n\r\nCPU speed is 200 kHz\r\n\r\n>>> g\r\n>>> dr\r\nA=0000FFFFFFFFFF D=00000000000000 M1=00000000000000 P= 0\r\nB=21000000000000 E=00000000000000 M2=00000000000000\r\nC=00000000000000 F=00000000000000 S =...3.5..........\r\n>>> dp\r\n00376: if 0 = s 15 then goto 00376\r\n>>>\r\n<\/pre>\n
\nThat’s a one line wait loop.<\/p>\n