X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112261832.AA21518@clio.rice.edu>
Subject: Re: lfn from scratch...
To: djgpp-workers AT delorie DOT com
Date: Wed, 26 Dec 2001 12:32:09 -0600 (CST)
Cc: dj AT delorie DOT com (DJ Delorie), eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
In-Reply-To: <3995-Wed26Dec2001192507+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Dec 26, 2001 07:25:08 PM
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

> > What's the best way to tell djgpp programs that *one* drive supports
> > LFNs and the others don't?
> 
> DJGPP doesn't cope well with this situation.

Should we look at fixing it?

> Also, UNC file names always force a call to 71A0h, because we don't
> know what drive do they map to.

I've seen lots of badness happen using UNC names under DJGPP - it will
see the file from findfirst but fail on stat (or somesuch).  I always
assumed UNCs were not supported at all.  Should we fix this?

(I *live* UNC names in my distributed NT/Win2K/98 environment - not 
enough drive letters for all the disk farm.  I notice this when I use
a DJGPP toolchain image instead of a VC built one).