Date:	Sun, 3 Jan 1999 18:48:34 +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:	<199901031607.RAA15693@father.ludd.luth.se>
Message-ID:	<Pine.SUN.3.91.990103184216.13506B-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com

On Sun, 3 Jan 1999, Martin Str|mberg wrote:

> On my system it switches to full screen mode and
> WINDOZE demands that you insert a disk in drive A: followed by B:. The
> system recupperates though.

Same here, except that it didn't recover in my case.

Usually, I switch the DOS box to a full-screen mode before trying such 
dangerous things (it makes Windows much less prone to nasty problems, 
such as messing up the color palette etc.), but this time I didn't...

> What platform did you try it on? 

Windows 95 v4.00.950r7.  I can test in DOS 5.0 and NT 4.0, if you need 
that.

> Thinking about the caching. Should that be done on an open() file
> basis or just once (when the first file on that partition is
> opened)?

The latter, I think.  It should work in the same manner as _use_lfn does 
(except that in your case there's no complications with environment 
variables).

> I'm mainly thinking of what would happen if somebody
> reformats their D: drive to another FAT system, while a DJGPP program
> is running.

Can Windows itself survive such an atrocity?  I would guess not.  It 
should be the same as disabling long file names (which requires to 
reboot).

> The X in FAT32X (cf. Subject)? Is that relevant?

I don't know.  Where did it come from?  Did I somehow mistyped the 
subject?  If so, it's not relevant.

- Raw text -