From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10111291626.AA16420@clio.rice.edu>
Subject: Re: df on NT/W2K (was: Re: statfs not ... 7302h and GNU df don't
To: djgpp-workers AT delorie DOT com, wojciech DOT galazka AT polkomtel DOT com DOT pl
Date: Thu, 29 Nov 2001 10:26:34 -0600 (CST)
Cc: eliz AT is DOT elta DOT co DOT il, dennis-louie AT att DOT net, acottrel AT ihug DOT com DOT au
In-Reply-To: <250B3114DA16D511B82C00E0094005F8055AC796@MSGWAW11> from "=?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?=" at Nov 29, 2001 09:02:48 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> Could you please check if the values returned by df for network drives are
> correct when LFN driver is loaded ?

The values for df seem correct when the LFN driver is loaded on the systems
I tested (I didn't know it already extended this interrupt, good job!)
I tested Win NT and Win 2K (my XP system is gone...)

ntlfn08b.zip is your friend :-)  I'll add this issue to the bugs and
workarounds on clio.  It appears the LFN TSR is the *only* way to fix this
one.