Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!bloom-beacon!oberon!sdcrdcf!trwrb!scgvaxd!ashtate!cy
From: cy@ashtate.UUCP (Cy Shuster)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Problem: duplicate .BAT and .COM in DOS 3.3
Message-ID: <304@ashtate.UUCP>
Date: Mon, 6-Jul-87 13:54:10 EDT
Article-I.D.: ashtate.304
Posted: Mon Jul  6 13:54:10 1987
Date-Received: Sat, 11-Jul-87 04:38:45 EDT
References: <302@ashtate.UUCP> <1352@bellcore.bellcore.com>
Reply-To: cy@ashtate.UUCP (Cy Shuster)
Distribution: world
Organization: Ashton-Tate, Torrance, CA
Lines: 14
Keywords: DOS 3.3 BAT batch
Summary: Search order is .COM, .EXE, .BAT

Thanks for the reminders: if files FOO.COM, FOO.EXE, and FOO.BAT all
exist and the external command "FOO" is typed, the search precedence
has always been .COM, .EXE, and then .BAT (the way I remember the
COM/EXE distinction is that after running EXE2BIN on a .EXE to make a
.COM, you have to delete the .EXE to execute the new .COM). I apologize
for not checking this behavior under prior DOS releases before blaming
3.3.

I suspected 3.3 because I was testing the behavior of the new "CALL"
statement. Anytime syntax calls for "drive:\path1\path2...\filespec"
I tend to include the extension as well. I guess I never realized that
if you keyed in the extension, it was ignored.

--Cy--          cy@ashtate.UUCP