Hi, Bob.

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

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

BL>  FM> When did they change this????

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

Yes, but what I thought was that it did so regardless of any supplied
extension. Either I was wrong, or it's changed.

BL>  BL> It was the idea I liked, not the execution. He should have
BL>  BL> added "c:" and "cd\" lines as well, to
return to the root
BL>  BL> directory (or wherever), but it never occurred to me to replace
BL>  BL> most of the PATH with batch files. That's the idea I liked.

BL>  FM> Much easier just to put *everything* in the root directory I
BL>  FM> would have thought. :-)

BL>   There's a reason not to do that... it always checks the root. If
BL> everything is in the root, it checks *everything* every time you give
BL> it a command.

Are you *sure* it always checks the root? (BTW, the correct answer is
that it doesn't.) If you don't have the root in your path create say
TEST.BAT in the root, go to another dir and type TEST. "Bad command or
file name".

I have absolutely nothing in my root that I can avoid - not even
COMMAND.COM. IBMBIO.COM, IBMDOS.COM, AUTOEXEC.BAT, CONFIG.SYS, 2 files
that 2 of my Norton utilities insist on putting there, and a zero-length
file which identifies the drive (eg SYSTEM.04C on this one).

Regards, fIM.

 * * Deadlines amuse me.
@EOT:

---