🚀 go-pugleaf

In article <1992Oct31.031157.3949@qiclab.scn.rain.com> 70465.203@compuserve.com writes:
>cgordon@vpnet.chi.il.us (gordon hlavenka) writes:
>
>>Actually, you should be able to try it by specifying the EXE file when
>>you run CHKDSK.  Instead of typing "CHKDSK", type "CHKDSK.EXE" and
>>this should force the loader to pull in the correct file.
>
>Believe it or not, this *won't* work. COMMAND.COM *ignores* the
>extension on executable files. 

In MS-DOS versions 1.00 - 3.x, yes, Leonard, you're right. But in 
4.0 and later, specifing "A.EXE" means that "A.EXE" will be 
executed, not "A.COM". They did add a few features in 4 besides MEM...

And if you are using MS-DOS 5 with DOSKEY, macros override .COM, 
.EXE, .BAT, and internal command names. IE, you can redefine DEL
or ERASE if you want. Like...

doskey erase=attrib -h -s -r $1 $t del $1

causes erase to delete almost any file :-) and 

doskey mem=mem.exe $1 $b more

causes mem to always pipe through more. 

-jen, who is not speaking for microsoft