Subject:	RE: RESEND: Re: File UItils at Clio 2.04 Query
MIME-Version:	1.0
Date:	Fri, 6 Dec 2002 12:32:16 +0100
X-MimeOLE:	Produced By Microsoft Exchange V6.0.6249.0
content-class:	urn:content-classes:message
Message-ID:	<250B3114DA16D511B82C00E0094005F809D319FE@MSGWAW11>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic:	RESEND: Re: File UItils at Clio 2.04 Query
Thread-Index:	AcKdGij9v6P7X0MfRKCGyrtNX7yxTAAAL1nA
From:	=?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= <wojciech DOT galazka AT polkomtel DOT com DOT pl>
To:	<djgpp-workers AT delorie DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id gB6BWLf18557
Reply-To:	djgpp-workers AT delorie DOT com

Hi,
Could you describe why it hooks int 21h ?

-----Original Message-----
From: Richard Dawe [mailto:rich AT phekda DOT freeserve DOT co DOT uk]
Sent: Friday, December 06, 2002 11:51 AM
To: djgpp-workers AT delorie DOT com
Subject: Re: RESEND: Re: File UItils at Clio 2.04 Query


Hello.

[...]
OK. I've retested now. My DOS CD-ROM driver was hooking INT 21h. It looks like
there is a bug in the port of 'df', because it does not report sizes
correctly, despite statfs returning the right information. (I checked by
building a test program in the sources - it agrees with Explorer.)

BTW shouldn't the docs for statfs, statvfs and fstatvfs list a few programs
that can hook INT 21h? E.g.: CD-ROM drivers. Maybe it should say how to debug
INT 21h hooking? Otherwise it's not very helpful.

I'll take a look at the problem with 'df' sometime.

Thanks, bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

- Raw text -