It was a very handy method of passing around binaries in text-oriented chat systems.
https://virtuallyfun.com/2009/12/03/partitioning-with-debug/
I managed to carve out the boot sector, learn assembly, and rewrite the virus code to more human readable format, and then the cherry on top: read the original boot sector off the disk (which I learned about through the virus code itself) and write it on top of the virus code. All this just from the user manual pages for DEBUG. The code for both reading and writing the virus code and the original boot sector, which was offset to a different sector, was right there in the virus. So it was an unusual self-documenting solution.
That was so much fun, I went head first into learning how to program in Assembler using TASM (Borland Turbo Assembler), which is in every way a more friendly way to write assembler. I still have the TASM programming book I bought way back then on my severely nerdy book shelf.
Those sure were the days.
Unsurprisingly, I kept up on viruses and antivirus, then hacking, then firewalls, then pentesting, in that order, as they were invented. The STONED virus and the DOS manual literally gave me a career path.
If I remembered correctly, debug was only capable of writing 64kB (mono-segment) data? Though one can always create an in-RAM program inside debug to output larger files.
Depending on what you were doing, even a ^C character in a script would throw it off, too.
HN hugged? lol
> PHP Fatal error: Uncaught TypeError: ActionScheduler_Action::set_schedule(): Argument #1 ($schedule) must be of type ActionScheduler_Schedule, ActionScheduler_NullSchedule given
I've been able to take 2 million hits a day, so it's not that!