Subject: Re: [uwin-users] fyi: extensionless executables
--------

> "Fyi", this might be useful, or it might not be, or it might seem useful and 
> the
> n not be.
> I tried out "Services for Unix" recently.
> I noticed in taskmgr stuff without ".exe" extensions.
> This got me experimenting.
> Leading to these findings:
>  CreateProcess does not care about extension. Or at least, it can run 
> extensionl
> ess executables. I can't vouch for batch files and 16 bit files.
> The usual Windows command line, cmd, does care.It does some sort of nested 
> searc
> h over %PATH% and %PATHEXT%.PATHEXT is a list of extensions that are runnable.
> If youset PATHEXT=.;%PATHEXT%
> then cmd as well can run extensionless executables.
> If you are living in "your own" sh/ksh/bash/xterm/rxvt that youcan 
> control/chang
> e/"fix", then you can "just do this" -- createextensionless files.
> If you don't mind cmd users having to alter PATHEXT, ditto.
> But if you want interop with a default cmd environment, then this is useless 
> tri
> via.
> I didn't experiment with running stuff from the Explorer GUI.i.e. if you are 
> cre
> ating Windows GUI apps...don't know.Maybe you can make an "association" (see 
> the
>  ftype and assoccommands).
> 

Unlink windows95, windows98, and windows2000, NT/XP, and Vista
do not require the .exe.  However, if you run from cmd they might
be needed so I decided to keep the .exe suffix.  Note that
commands that look for paths, will find the .exe if it is there
and otherwise ignore it.

David Korn
[EMAIL PROTECTED]
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users

Reply via email to