From: j DOT aldrich6 AT genie DOT com
Message-Id: <199604120022.AA280978575@relay1.geis.com>
Date: Fri, 12 Apr 96 00:02:00 UTC 0000
To: djgpp AT delorie DOT com
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Subject: Re: Paths and .COM files

Reply to message 1827855    from ELIZ AT IS DOT ELTA. on 04/11/96  4:59AM


>Yes, it does; it also knows about .BTM files from 4DOS/NDOS.  Any file
>that is runnable by DOS is reported as executable by that function.  This
>includes many files you won't suspect being executables, like Windows
>DLLs, and some other Windows files which include a small DOS stub that
>just prints an error message.  That function is the engine behind the
>'execute bit' reported by `stat' and `fstat' in DJGPP.

Actually, that makes it even worse for me, because I only want those
programs that you can run from the command line; you can't run foo.dll
by typing 'FOO'.

I actually have the program running now, and working just fine.  My
final problem relates specifically to the behavior of searchpath() --
it can only look for one specific filename at a time.  I not only need
to see if there are any matching .COM, .EXE, or .BAT files in the path,
but which comes first.  :)  Can you recommend any way around thisbesides simply
writing my own version of searchpath()?  If I did this,
would I run into any copyright or licensing troubles, as I'd simply be
copying the code and making a few changes?

Thanks,

John