Date: Sun, 3 Jan 1999 11:07:52 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>
cc: DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
Subject: Re: FAT32X and DJGPP
In-Reply-To: <199901021618.RAA08436@father.ludd.luth.se>
Message-ID: <Pine.SUN.3.91.990103110725.12860O-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com


On Sat, 2 Jan 1999, Martin Str|mberg wrote:

> Please try the program and see if it reports the right FAT file system.
> (And yes I know it's hackish, including hick-ups.)

It wedged my entire system, but hey, you *did* warn me ;-).

It does seem to report correct filesystem type, though.

In the final code, please be sure to test for the DOS version.  v3.x
didn't support function 69h, so you should only issue the call for
later versions.  Perhaps, if the function is limited to reporting
FAT32 or not (as opposed to reporting other types, such as CDROM,
FAT16, FAT12, etc.), then only version 7 and up should at all issue
the call, since FAT32 was first introduced with DOS 7.1.

Alternatively, report the correct results for DOS 4+ and fall back on
some default for 3.x (yes, DJGPP still wants to support DOS 3).

> Well, an interrupt and a strncmp should suffice. Is that expensive? Perhaps
> we should/could cache it?

I think this info should be cached, yes.