From:	j-cerney1 AT ti DOT com (John Cerney)
Subject:	re: Weird NT problem
21 Apr 1997 14:10:09 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<BMSMTP8616352414a0182636.cygnus.gnu-win32@dsbmail.itg.ti.com>
Reply-To:	John Cerney <j-cerney1 AT ti DOT com>
Mime-Version:	1.0
X-Mailer:	BeyondMail for Windows/Professional 2.3
Original-To:	jonathan AT westwood DOT com
X-BeyondMail-Priority:	1
Conversation-ID:	<9704211253 DOT AA05833 AT nbserv2 DOT dseg DOT ti DOT com>
In-Reply-To:	<9704211253.AA05833@nbserv2.dseg.ti.com>
Original-Cc:	gnu-win32 AT cygnus DOT com
X-Receipt-From-Agent:	true
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

>  
>  I'm getting this really weird problem on NT.  I've posted about this 
>  before I think but I was slightly mistaken about the actual 
>  circumstances, so I thought I'd repost this problem, so that if any of 
>  this rings a bell with any of you, even if you can't help but you've seen 
>  this happen, please email me so that I know I'm not alone...
>  
>  Basically, I've got this really big program (with symbols ~21MB) that 
>  links and runs under Win95 (well it kinda crashes but that's a different 
>  problem).  Attempts to debug under Win95 have proven fruitless, so I 
>  thought I'd give WinNT a try.  Well, the program compiles and links under 
>  NT as well, but the resulting executable won't run on NT.  But get this:  
>  It WILL run on Win95.  The NT error returned from CreateProcess() is 193, 
>  ERROR_BAD_EXE_FORMAT, and when trying to load the .exe from a command 
>  prompt, I get a dialog box that's telling me that it's not a valid 
>  Windows NT application.  I've got a few thoughts on why this might be 
>  happening, but I'm kind of ignorant about WinNT internals, and I've 
>  already searched the MicroSoft knowledge base and I can't find anything.  
>  I'm hoping someone out there (maybe from Cygnus?) can shed some light on 
>  this for me.  I'd really like to know what constitutes a 'valid Windows 
>  NT executable'.

I have seen this problem before, but I can't recall the exact circumstances
(sorry). 

You might try running the PEDUMP utility on it with /l /r /s options to see
what it says about the format. I have found that PEDUMP would find problems
with a executable file when Microsoft's dumpbin and Borland's tdump wouldn't.
PEDUMP is a fairly exhaustive Portable-Executable format dumper that appeared
in the March '94 Issue of the Microsoft Systems Journal. You can get it from
ftp://ftp.microsoft.com/developr/msj/MSJMAR94.ZIP.


-John Cerney
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -