From:	Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id:	<200101061244.NAA18812@father.ludd.luth.se>
Subject:	Re: Fw: Patch for statfs.c
In-Reply-To:	<5567-Sat06Jan2001131954+0200-eliz@is.elta.co.il> from Eli Zaretskii at "Jan 6, 2001 01:19:55 pm"
To:	djgpp-workers AT delorie DOT com
Date:	Sat, 6 Jan 2001 13:44:07 +0100 (MET)
Cc:	ceo AT nbensacomputers DOT com
X-Mailer:	ELM [version 2.4ME+ PL54 (25)]
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

According to Eli Zaretskii:
> > From: "Norberto Alfredo Bensa" <ceo AT nbensacomputers DOT com>
> > Date: Fri, 5 Jan 2001 18:40:47 -0300
> > 
> > I've just tested on Win98 plain DOS mode and 213600 gives:
> > blocks = 32768, bsize = 4096, resulting in 134,217,728 or 128MB...
> 
> Expected: 213600 is limited to 128MB, by its very definition.

That is a little surprising as it manages to report drive sizes up to
~4GiB in DOZE...

> > 2F1510 gives:
> > blocks = 308862, bsize = 2048, resulting in 632,180,736 or ~602.9MB
> 
> That's the right value (the actual number depends on how full is the
> CD, of course: it can go up to 700MB).
> 
> > Under Windows (DOS box) with 217303, I get:
> > blocks = 19275, bsize = 32768, resulting in 631,603,200 or ~602.3MB
> 
> That's a lie: the block size is reported incorrectly (2048 is the
> right value).  This clearly shows that we shouldn't use 217303 for
> CDs.

I realise that a bsize of 32768 is a lie, however ...

> > Properties for my E: drive gives 631,603,200, that's what 217303 is
> > reporting.
> 
> Small wonder: I guess Windows uses 217303 itself.

... shouldn't we let WINDOZE have it's way. The INT21 AX=0x7303 calls
do give reasonably accurate values when they succeed and it's what
WINDOZE itself reports.


Right,

						MartinS

- Raw text -