The programs of those days were hard-coded to the graphics adapter resolution. In the "good old days" the user interface was 640px x 480px (original VGA, skipping past the original MDA, CGA, and Hercules graphics cards since they predated "modern" GUIs). The abstraction layer has only remained the same visually, and only for a loose definition of "visually."
Changing this to only update once a second fixed it entirely.Īnd that's how I DoS'd myself with a spinner. Then I finally realized what was happening: I was refreshing the spinner on EACH ROW and remote machine was going through the rows so quickly that sending refreshes for the spinner saturated my tiny dial-up connection. This stumped me for an hour or so until I ran it without the verbose option. But as soon as the script finished, it would suddenly start working again.Īs you can imagine, this was very confusing since the script was running entirely on a remote system. Every time I ran the script to test it, my Internet connection would become nearly unusable. Being as that I had no idea if the script was actually working until it completed awhile later, I decided to put in a neat little ASCII spinner in it when you ran it with verbose options.Īt the time I was on a slow dialup connection as I was on break from school, and something weird would happen. It had to loop through a bunch of text log data and generate some reports. This reminds me of one of my favorite old tech stories.Ī long while back (seems like this was the late 90s or early 2000s) I was working on a script that did some data processing on a remote machine.