3 ms·
had a little "sidecar" TSR that would copy RAM into the monochrome display area every nth timer tick as a debugging aid; it was a window into running programs w
by h2odragon 5y ago
had a little "sidecar" TSR that would copy RAM into the monochrome display area every nth timer tick as a debugging aid; it was a window into running programs without being a full debugger.
Few people actually used dual monitors in the DOS / EGA era, so seeing one doing a matrix type display while the other was running games blew a lot of minds.
TFA says "f you are using an extended memory manager such as EMM386, you need to make sure that it isn't using the video RAM for its own purposes." ... you could just let that be a live window on "some random RAM" that way but it wasn't interesting. My TSR had more settings for screensaver uses than for debugging.
- anyfoo 5y agoI remember being blown away seeing expensive debugging software providing a debugging interface on a second, monochrome monitor. It's hard to bring across how "1 computer : 1 monitor" seemed like such a strong relation inherent to home computers, that seeing a multi-monitor configuration was sort of mind bending. It's two screens, but the same computer, how can that be?[1] That feeling continued on when I had my own, first two monitor setup many years later. Nowadays, it's of course all very mundane. [1] Arrangements with (e.g.) mainframes and terminals had been common among workplaces and universities for decades, but were basically an entirely different world from home computers, including PCs. It didn't "translate".