From:	"Greg Donnells" <gad AT donnesys DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	fread() problems
Lines:	18
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID:	<e37w6.982$eX4.229562@typhoon.tampabay.rr.com>
Date:	Tue, 27 Mar 2001 20:51:22 GMT
NNTP-Posting-Host:	24.164.23.148
X-Complaints-To:	abuse AT rr DOT com
X-Trace:	typhoon.tampabay.rr.com 985726282 24.164.23.148 (Tue, 27 Mar 2001 15:51:22 EST)
NNTP-Posting-Date:	Tue, 27 Mar 2001 15:51:22 EST
Organization:	RoadRunner - TampaBay
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I'm currently using 2.03 to write and read information from a binary file.
(records are 516 bytes in length). fread() will read the 1st 6 records
perfectly - then it locks up on the next read and requires me to kill the
program (3-fingered salute), and to kill the window the program is running
in. It's like fread() doesn't know hos to read the next disk cluster in the
file.

The docs state that if it has a read problem, that it will return the number
of recs read - it locks.

I've searched (as best as I know how) the bug archives, but have seen
nothing like this. Any help would be greatly appreciated (I'll be hapy to
share input/out and source files if necessary).

Thanks,
Greg D.

- Raw text -