Xref:	news2.mv.net comp.os.msdos.djgpp:1197
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Help! Not COFF (again)
Date:	Fri, 16 Feb 1996 12:26:43 CST
Organization:	Rice University, Houston, Texas
Lines:	18
Message-ID:	<3124cc63.sandmann@clio.rice.edu>
References:	<4g137g$ftm AT ds2 DOT acs DOT ucalgary DOT ca>
Reply-To:	sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host:	clio.rice.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

> 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" 

This message is coming from the stub.  It means that it checked the
starting data in the COFF image attached, and it does not seem to
be a COFF image.  The image is corrupted.  Since you seem to have
this problem on lots of images, I would guess you either have a virus
or a hardware problem.  Because of the way V2 stubbed images are 
created, it leaves no room for a virus to easily infect the file and 
make it continue to run.

> and just terminate.  Not all of the .EXEs do this, but STUBIFY and 
> EXE2COFF do this, which prevents compilation of anything.  What's 

These two images are less than 64K and so probably looked OK to infect
by a virus, would be my guess.  If you would like, you can send me a
copy of one of your binaries and I will confirm what corruption has
taken place.

- Raw text -