> All MS-DOS versions prior to 5.0 allowed simple editing of the AUTOEXEC.BAT
> string in COMMAND.COM to startup a different batch file. This doesn't work with
> subsequent versions. Billy must have hidden an encrypted startup string
> Has anyone been able to locate it or am I just rompin' down the wrong road?
I just tried it on COMMAND.COM from MS-DOS 6.2. It worked fine after some
tweaking. I won't go into the changes I made that did NOT work--only the
ones that did.
The AUTOEXEC.BAT string occurs twice in COMMAND.COM. I edited both (using
Norton's disk editor) so that they were changed to the same string that was
of *EQUAL LENGTH* to "AUTOEXEC.BAT" (8+3 filename). These changes were
made to COMMAND.COM itself. I backed up my original with a different name
first, of course! :)
A few interesting observations without explanation (I didn't do much
1) I could not use a patched COMMAND.COM that had a different
name, even if I set the new name in CONFIG.SYS with the shell command.
2) When my original tests did not work, I found that I did not
need to use a boot disk. I simply re-booted and pressed <F5> to bypass
the startup files. To my surprise, I was prompted for the proper name
of the COMMAND.COM file. When I entered it (in this case COMMAND.BAK),
I was able to use the system to make the necessary restoration.
case ABOVE of
'OPINION' : DISCLAIMER:=' is my own, but should be yours too.';
'FACT' : DISCLAIMER:=' was made up by me, so you can believe it.';
'BATCH' : DISCLAIMER:=' probably contains at least one error.';
'FLAME' : DISCLAIMER:=' was written by someone else using my account.';
DISCLAIMER:='The above '+ABOVE+DISCLAIMER;