X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10504260350.AA14166@clio.rice.edu>
Subject: Re: FAT32 extended bit + Network share bug status
To: djgpp-workers AT delorie DOT com
Date: Mon, 25 Apr 2005 22:50:41 -0500 (CDT)
In-Reply-To: <200504240940.j3O9ePqu007567@speedy.ludd.ltu.se> from "ams@ludd.ltu.se" at Apr 24, 2005 11:40:24 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavis-20030616-p6 at mail.rice.edu
X-DCC--Metrics: handler8.mail.rice.edu 1066; Body=1 Fuz1=1 Fuz2=1
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
Precedence: bulk

> One more thing. I can create >2GB files in MS-DOS 7.10 (plain DOS) if
> I use the FAT32 extended flag, but not without it.

The bug author sent me a boot disk containing his environment.  I am
able to reproduce the network open bug using his boot disk, using either 
Windows 2000 or Windows XP as a disk server.  

If the file does not exist, everything works fine.  If the file exists, it
fails to open it with "file exists" error code on a network share.  Works
fine on the local disk; also works fine with the FAT32 extended bit clear
on the network share.

Eli's suggestion of just clearing the bit and trying again is what I may
try next.  I would only retry if a special flag was set and the error
code matched.