This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin B20 won't run any executable that doesn't have a .exe extension
- From: "Larry Hall (RFK Partners, Inc.)" <lhall at rfk dot com>
- To: David dot Paterson at csiro dot au
- Cc: cygwin at cygwin dot com
- Date: Thu, 15 May 2003 23:33:44 -0400
- Subject: Re: cygwin B20 won't run any executable that doesn't have a .exe extension
- References: <1C63B6BC1CF8BF408FCED3B2D202C58E0120BD79@arch-hr.mel.dbce.csiro.au>
- Reply-to: lhall at rfk dot com
Cygwin B20 is ancient - So ancient, that you cannot upgrade, you must do a
clean install of the current Cygwin.
I'll send that on to CFX. I doubt if they'll do anything as they're not
upgrading 4.4 any more, just sending occasional bug fixes. Version 4.4 was
released in 2001, in time for Windows NT 4.0 with service pack 5.
Is CFX really commercial software? (The website seems to suggest so).
I'll say it is, with a hefty annual fee. It's my bread and butter. I've
previously run it on SGI machines, never before on Intel.
Which leads up to the question: Which Loader is Cygwin using?
The wrapper is Demoshield demo32.exe
Inside that is 1996 Install Shield Software Corportation full.exe calling
stub.exe & stub32.exe. Package For The Web Stub. File version 22.214.171.124
Product version 2.02.001
Inside that is 1991 GNU GENERAL PUBLIC LICENSE Version 3. Free Software
Foundation Inc. 675 Mass Ave Cambridge, MA 02139, USA.
You may want to hold onto your copy of B20, I am sure you will receive
requests for copies of it soon.
Yeah, I can sense the orders coming in already.
So, is your advice "Grin and bear it" or "Fix B20 yourself" or "Force
CFX-4.4 to accept the latest Cygwin" or "Give up on Cygwin and install
Yeah, that's it. Sorry. It's not clear why your CFX installation wouldn't
work with the latest DLL though. If it's just a permissions issue, you
might try adding "nontsec" to your CYGWIN environment variable and then
reloading the Cygwin DLL (exit all progies using it). Otherwise, you
might try running strace on CFX to see if there's anything useful there.
Or you could try renaming your CFX executable to append the ".exe".
Can't imagine why that would make a difference but the information
you provided prompts such a WAG. Still, this is really an issue for
the provider of CFX. Even if B20 wasn't as old as the hills, this
list really can't support someone else's distribution of Cygwin tools.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html