|
|
|
|
|
|
by jim_lawless
806 days ago
|
|
|
DEBUG was also able to read/write disk blocks and it could load / save files from memory based on register settings. I had written a batch file and a file of DEBUG commands ( redirected into DEBUG ) that would load the blocks from 1.44M diskettes at about 64K at a time, save each just-under-64k segment with a separate filename, and then zip up the whole collection. I also had written the counterpart scripts to decompress and block-write the data back out to a 1.44M floppy. This allowed us to archive the .zip collections as disk images for some critical boot disks and such. I had also written a utility in C published in Windows/DOS Developer's Journal (April 1995) before some email clients could UUDECODE or Base64-decode attachments. This utility wrote a short loader as a text file followed by the G command to execute it. Following the G command were lines of UUENCODED data. The assembly language loader code would begin reading lines from the standard input device and would UUDECODE them as it added them into DEBUG's current working buffer starting at 100h. At the tail end of the script, the N command was used to name the output file, the CX register was updated via RCX to set the output length, and the W command was used to save the file. This allowed me to send some encoded binary files embedded in the body of the email to folks that didn't have sophisticated email clients. They could just pipe this portion of the email into DEBUG and it would ultimately write the decoded binary file. |
|
|