Date: Wed, 15 Mar 2000 18:05:09 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: DEVLEESCHOUWER Gregory - SQY <Gregory DOT DEVLEESCHOUWER AT sema DOT fr>
cc: djgpp AT delorie DOT com
Subject: Re: coff2exe problem
In-Reply-To: <33AC16542391D3118A35009027CC6B100FD990@sqymes01.sqy.sema.fr>
Message-ID: <Pine.SUN.3.91.1000315175717.20407I-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 15 Mar 2000, DEVLEESCHOUWER Gregory - SQY wrote:

> i am a new user of djgpp et i got a problem with coff2exe :
>  i run coff2exe   ( ex :     coff2exe -s go32.exe hello.exe) , and after
> waiting several minutes coff2exe still running. I stop it and i see that the
> size of hello.exe is about 27000 Ko !!

This is totally incorrect usage.  It's no wonder you get weirdo results.

What version of DJGPP is that?  go32.exe implies version 1.x, which is 
VERY old.  The current version of DJGPP is 2.03, it doesn't use go32.exe 
and doesn't have coff2exe at all (well, it does, but it is a symlink to 
stubify.exe, which is what you should use).

In addition, even in v1.x, coff2exe was not supposed to be used like you 
did, it was meant to produce .exe files from COFF images, like this:

	coff2exe hello

This would produce hello.exe from hello.

The -s switch is for specifying a specific stub file, instead of the one 
built into coff2exe.  But go32.exe is not a stub, it's not even a DJGPP 
program, so nothing good will ever happen to you if you try to use 
go32.exe as if it were a stub.

Perhaps you should begin by telling what exactly were you trying to 
achieve.