A Guide to Debug.exe

Reminds me about how I nearly got kicked out of highschool for changing the background color of sol.exe.<p>Back in my HS days, the &quot;computer class&quot; teacher (in quotes because it wasn&#x27;t a computer class at all, rather a typing class) used to walk around and say &quot;I don&#x27;t want to see any green screens&quot;. Green, of course, being the background color of the built-in solitaire card game back in Windows 3.11 days.<p>I took a screenshot as a bmp, and found the hex value for the background color. Then I fired up debug, having nearly no idea what I was doing, searched for that hex value, found it, and then changed it to a nice mauve color. Thought it would be funny, maybe even praise-worthy.<p>Instead, the teacher lost his shit. These computers were &quot;locked down&quot; by basically just putting all the admin-type shortcuts into a password protected program group. But File-&gt;Run was still there, and it had no problem firing up COMMAND.COM. I didn&#x27;t think it would be a big deal, but of course it was completely blown out of proportion by the teacher, who didn&#x27;t exactly like my attitude.<p>I still dislike that man.

It&#x27;s interesting that you can write relatively complete programs with Debug.exe assembler.<p>This link made me remember my weird experiment from 2009 to write a NES Battle City [1] clone with debug.exe assembler [2]. Of course it wasn&#x27;t completed, but nevertheless, it even switches to a graphic mode and draws a single sprite on the screen and takes input from the keyboard. :)<p>The demo [3] still should be working in DosBox.<p>[1] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Battle_City_(video_game)" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Battle_City_(video_game)</a><p>[2] <a href="https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;asmbattlecity&#x2F;source&#x2F;browse&#x2F;" rel="nofollow">https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;asmbattlecity&#x2F;source&#x2F;browse&#x2F;</a><p>[3] <a href="https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;asmbattlecity&#x2F;downloads&#x2F;detail?name=tanks_demo_02.zip" rel="nofollow">https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;asmbattlecity&#x2F;downloads&#x2F;detail?nam...</a>

This article really brought back some great memories for me. I learned about computers as a kid back in the early 80s on an MS-DOS clone PC. The only manuals I had was one listing the various MS-DOS commands (sadly, excluding anything about debug.exe though) and one that was a command reference for gwbasic.exe [1].<p>I spent many hours trying to write games in gw-basic but quickly realised that the performance was atrocious, to say the least. Eventually I stumbled across a magazine that had a two-page article about debug.exe and it was my gateway to a whole new hidden world. I went on to learn 8086 assembly with debug.exe by trial and error and from stepping through other programs. Eventually I figured out I could write little 8086 assembly routines in debug.exe myself, take the sequence of bytes that made up that routine, declare them as a DATA statement in a BASIC program and then just make call that DATA line to run the machine code directly [2]. It wasn&#x27;t until many months later I finally managed to get my hands on some compilers and assemblers (Borland Turbo Pascal and Turbo Assembler being my favourites back then) which of course made my life a whole lot easier! I continued to use debug.exe for many years though, primarily for reverse engineering.<p>I&#x27;ve just managed to dig up an obfuscated &quot;Hello World&quot; batch file I wrote many years ago that makes use of debug.exe, see [3] below (If you actually want to run it you&#x27;ll probably need an MS-DOS emulator [4][5] or an older version of Windows that still has debug.exe).<p>[1] <a href="http:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;GW-BASIC" rel="nofollow">http:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;GW-BASIC</a><p>[2] <a href="http:&#x2F;&#x2F;www.antonis.de&#x2F;qbebooks&#x2F;gwbasman&#x2F;appendix%20d.html" rel="nofollow">http:&#x2F;&#x2F;www.antonis.de&#x2F;qbebooks&#x2F;gwbasman&#x2F;appendix%20d.html</a><p>[3] <a href="http:&#x2F;&#x2F;www.redyeti.net&#x2F;extra&#x2F;hello.bat" rel="nofollow">http:&#x2F;&#x2F;www.redyeti.net&#x2F;extra&#x2F;hello.bat</a><p>[4] <a href="https:&#x2F;&#x2F;jamesfriend.com.au&#x2F;pce-js&#x2F;ibmpc-games&#x2F;" rel="nofollow">https:&#x2F;&#x2F;jamesfriend.com.au&#x2F;pce-js&#x2F;ibmpc-games&#x2F;</a><p>[5] <a href="http:&#x2F;&#x2F;www.dosbox.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.dosbox.com&#x2F;</a>

One of the more useful things that was done with debug.exe was a binary-to-ascii converter for sending files in email or usenet and the recipient didn&#x27;t need any extra tools. I think the program was called &quot;xxdebug&quot; after xxencode which was a descendent of uudecode. But Google doesn&#x27;t help, so either my memory is wrong or the internet has forgotten.<p>I&#x27;m positive I have it on an archived disk somewhere. If I were inclined to resurrect it.

Another relic of old times is the font installer embed on Windows. Since Windows 3.1 to Windows XP has the exact same program! You can check that it&#x27;s keeps using the old GUI to navigate across the filsesystem, not showing the &quot;Destop&quot; false root.<p>On Windows Vista and forward was replaced by something more modern.

The smallest program I ever wrote, I wrote using debug.exe. It was 7 bytes long. I think it reset the graphics card. This was around 1991.