Xref:	news2.mv.net comp.os.msdos.djgpp:1223
From:	Stephen Leung <sjleung AT acs DOT ucalgary DOT ca>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Help! Not COFF (again)
Date:	16 Feb 1996 05:03:44 GMT
Organization:	University of Calgary
Lines:	39
Message-ID:	<4g137g$ftm@ds2.acs.ucalgary.ca>
NNTP-Posting-Host:	@ts2-port-2.acs.ucalgary.ca
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Okay.  Let's try this again... this time my call time isn't 
running out on my provider!

A few days ago, my copy of DJGPP just stopped working properly.  
All of a sudden, whenever I try to run most of the binaries, they 
error out with the message "C:\DJGPP\BIN\<filename.exe>: not COFF" 
and just terminate.  Not all of the .EXEs do this, but STUBIFY and 
EXE2COFF do this, which prevents compilation of anything.  What's 
strange is that it worked just beautifully for a few months prior 
to when this all started.  This doesn't just happen when GCC 
spawns these programs either.  If I try to run STUBIFY (it 
doesn't even seem to get to the bit about interpreting any 
command-line options), it gives the error.

Now, that's not the strangest part.  Originally, it happened to my 
old copy of the v2 beta.  Then I decided to upgrade once my v2 
beta just stopped working.  So I installed the newest version I 
could find (whatever that happens to be) and that worked fine... 
for a couple of days.  Then, it started giving me these errors 
too.  So I unzipped the binaries again, and it worked... this time 
for a few minutes.  Then it screwed up again.  Now every time I 
unzip the binaries at least STUBIFY is screwed, which is annoying 
since now my compiler is useless...

All this would seem to indicate that something has changed on my 
system which is causing all this mayhem.  But my computer hasn't 
changed in a while.  I installed Win'95 (ugh) without a hitch, I 
upgraded RAM with no problems.  Other than that, I can't see 
anything that would cause an error, and especially nothing NOW 
since nothing's different!!!!!  It also can't be the .EXEs 
themselves, since they check out in the zips all ok, and it 
doesn't seem like this problem is very common!  ARGH!

So *please*, does anyone have any ideas on this?  I have a 
Computers assignment due Tuesday, and I'd like to do this one at 
home!!!!

Thanks.

- Raw text -