FM> Created testexec.exe and testexec.bat and no testexec.com.

 FM> TESTEXEC runs testexec.exe TESTEXEC.EXE runs testexec.exe
 FM> TESTEXEC.BAT runs testexec.bat TESTEXEC.COM "Bad command or
 FM> file name"

 FM> When did they change this????

 BL> Isn't that what it always did... check COM first, then EXE,
 BL> then BAT?

 PE> The change he's talking about is taking notice of the ".EXE"
 PE> bit at the end AT ALL. It used to be TOTALLY IGNORED. BFN.

  What Frank means depends on how he created his files. If it was a 
real EXE file, then what I said is true: DOS checks "testexec" first 
for COM, then EXE, then BAT. If he calls "testexec.exe" then it only 
tests for EXE and the same with "testexec.com" when it finds the file 
does not exist. It "ignores" the ".EXE" only so far as
checking the 
file header for EXE.

  DOS is supposed to check the file header itself to stop you running
a false EXE by accident, but I tried this yesterday with DOS6.22 and
it locked the computer, so I assume DOS has changed and now runs
anything you call ".exe" as if it is a *real* executable with crazy
results.

Regards,
Bob
 
___ Blue Wave/QWK v2.12
@EOT:

---