From:	Alexander Stapff <a DOT stapff AT gmx DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Exectuable size = 0 after Ctrl+Break?
Date:	3 Jul 2003 14:48:33 GMT
Lines:	36
Message-ID:	<Xns93ADAAFDD8ED9astapffgmxde@130.133.1.4>
References:	<Xns93AD8C1CF7375astapffgmxde AT 130 DOT 133 DOT 1 DOT 4> <be15ud$rsh$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
NNTP-Posting-Host:	p508e888b.dip0.t-ipconnect.de (80.142.136.139)
X-Trace:	fu-berlin.de 1057243713 229441 80.142.136.139 (16 [171242])
User-Agent:	Xnews/06.01.10
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi,

> It being the least commonly used component of your setup, and yours
> being the first time I remember ever having seen a report of a
> misbehaviour like this, my prime suspect would be some horrible bug in
> ROMDOS's file handling code.

I already searched for a documented bug in Romdos but couldn't find 
anyone reporting such a misbehaviour. The datalight support hasn't 
answered yet.
 
> Please try doing without this and see if that gets you rid of the
> problem. 


I just disabled alle CRC checking and all writing to files. The only file 
I use right now is an allegro data file which is opend at start up und 
closed as soon as all data has been copied to memory. So this file isn't 
used after the program start up anymore. But the problem still exists.

 
> Since you're using allegro: did you by any chance embed some allegro
> data into the executable?  That might keep a handle the executable
> file open, too.
> 

No, there is no allegro data embeded into the executable. I use an 
allegro data file which is only read at program start up and closed after 
that.


Alexander

P.S.: Thanks for your fast answer
P.P.S.: I just noticed, that we are nearly neighbours. I am in Stolberg 
right now...

- Raw text -