3 ms·
To be precise, most computers had only a monochrome or a color card, but nothing prevented you from having (and using) both. I remember a debugger that gave yo
by bombcar 3y ago
To be precise, most computers had only a monochrome or a color card, but nothing prevented you from having (and using) both.
I remember a debugger that gave you dual screen on a 8086 by using the monochrome for text/debugging whilst the color screen was for the program.
- stevenwoo 3y agoSoftICE was amazing at the time.
- hnthrowaway0328 3y agoI heard modern OS protection mechanisms prevent debuggers do things like SoftICE did. Is it true? Where can I grab more information?
- stevenwoo 3y agoI don’t know about that sorry. It did let you suspend Windows totally, not sure how different that is than today. I had to take over responsibility for a device driver in windows 95/98 era and SoftICE offered a better debugger than microsoft for the task under Windows at that time.
- vardump 3y agoWindows kernel debugger also lets you to totally suspend Windows. You can configure it to connect over ethernet.
- saagarjha 3y agoDesigning a debugger like SoftICE is unnecessary now: modern processors support virtualization, which means you can run the entire OS inside a VM and debug it from your hypervisor.
- weinzierl 3y agoAbsolutely. I still remember the disbelief when I realized that you could observe Windows 95 booting. It hooked into system before the OS.
- zabzonk 3y agothe microsoft debugger back then allowed the use of dual screens
- hinkley 3y agoI have always strongly suspected that this is how print debugging got cemented into the ethos. You had developers using it as a power feature.
- weinzierl 3y agoI did that with Turbo Pascal in the 90s. Having your app on the color monitor, while the debugger was on the Hercules one was amazing.
- ngcc_hk 3y agoOoo. I do not know that. … many decades too late.
- hyperman1 3y agoIf I remember correctly, even with a color card, applications switching to a monochrome video mode was possible if a bit rare. Creating UMBs in vram segments A000, B000 or B800 was always considered a suicidal configuration, and EMM386 would not do it unless forced. If I see the man page http://www.manmrk.net/tutorials/DOS/help/emm386.exe.htm http://www.manmrk.net/tutorials/DOS/help/emm386.exe.htm the vram segments are not allowed for the FRAME= and Mx options, rang A000-BFFF is forbidden.