Date: Mon, 20 Oct 1997 15:00:05 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
cc: djgpp-workers AT delorie DOT com, ralf AT pobox DOT com
Subject: Re: Detecting fat32 drives.
In-Reply-To: <199710192150.KAA06994@teleng1.tait.co.nz gatekeeper.tait.co.nz>
Message-ID: <Pine.SUN.3.91.971020145914.29791J-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 20 Oct 1997, Bill Currie wrote:

> Actually, I think I found a better method: use int 21 ax=7305 
> cx=ffff and if it's not supported (al=0,nc), fat32 is 
> not supported and so the fat32 calls need not be made, otherwise it 
> doesn't hurt.

We need to think about this in the context of libc functions.  Suppose
some function needs to know whether to issue a FAT32-specific call or
not.  If it will try to call 217305 every time, won't that make that
function prohibitively slow?  If it will, we need a faster way.

What happens if you issue a FAT32 call on a FAT16 drive but under a
version of DOS/Windows that supports FAT32?  Will that work or fail?