Xref: utzoo comp.sys.ibm.pc.programmer:596 alt.msdos.programmer:1419
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!mit-eddie!bu.edu!ncsuvx!ncsugn!emigh
From: emigh@ncsugn.ncsu.edu (Ted H. Emigh)
Newsgroups: comp.sys.ibm.pc.programmer,alt.msdos.programmer
Subject: Problem with disk full in programs compiled with Turbo-C
Message-ID: <5705@ncsugn.ncsu.edu>
Date: 26 Mar 90 17:09:39 GMT
Reply-To: emigh@ncsugn.UUCP (Ted H. Emigh)
Organization: Genetics, North Carolina State University, Raleigh, NC
Lines: 63

I am using Turbo-C (Version 2.0), and am having trouble determining if the
disk is full.  I have tried the obvious (at least to me obvious):
1)	Code fragment:
	result=fprintf(...)
	if(result==EOF) { do something}

	result always returns the number of characters -- even if the disk
	is full.  There is disk activity, but nothing is written (obviously).

2)	Code fragment:
	harderr(hardware_handler);
	...
	int hardware_handler() { do something }

	This routine is never called for disk full.  It functions OK for write-
	protect and disk not ready, but not for disk full.

Do you have any suggestions to help detect disk full?  Thanks.

PS.  What, really, is the difference between comp.sys.ibm.pc.programmer and
alt.msdos.programmer?

-- 
Ted H. Emigh, Dept. Genetics and Statistics, NCSU, Raleigh, NC
uucp:	mcnc!ncsuvx!ncsugn!emigh	internet:  emigh@ncsugn.ncsu.edu
BITNET: emigh%ncsugn@MCNC.UUCP  or  emigh%ncsugn@ncsuvx.ncsu.edu