From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP and Windows 2000
Date:	Thu, 09 Aug 2001 22:56:35 +0300
Lines:	23
Message-ID:	<3B72EAF3.FFF6CCB0@is.elta.co.il>
References:	<09D1E9BD9C30D311919200A0C9DD5C2C03E08983 AT mcaexc01 DOT msj DOT maxtor DOT com> <09D1E9BD9C30D311919200A0C9DD5C2C03E0898A AT mcaexc01 DOT msj DOT maxtor DOT com> <3b71da94 DOT sandmann AT clio DOT rice DOT edu> <9kuogu$ndb$1 AT pippin DOT nask DOT waw DOT pl>
NNTP-Posting-Host:	diup-218-115.inter.net.il (213.8.218.115)
Mime-Version:	1.0
X-Trace:	fu-berlin.de 997387015 7193669 213.8.218.115 (16 [61365])
X-Mailer:	Mozilla 4.7 [en] (Win98; I)
X-Accept-Language:	en
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Wojciech Galazka wrote:
> 
> Charles Sandmann wrote in <3b71da94 DOT sandmann AT clio DOT rice DOT edu>...
> [...]
> >2) Many bugs in the long file name support.  A quick workaround is to
> >   set lfn=n if something doesn't work right.  Example: rename to the
> >   same name library call fails (strip/ar fail).  Touch fails.  You can
> >   always set it back via lfn=
> 
> Could you provide more details on this ?

There are too many details ;-)

In a nutshell, the LFN-aware functions are not to be trusted on W2K.  In
particular, handles created by an LFN variant of _open fail some important
functions of Int 21h that take a file handle, such as functions 5700h and
5701h, and all subfunctions of function 44h (IOCTL) seem to return zero
instead of valid info.  The latter problem is the reason why ">/dev/null"
doesn't work on W2K.

In other words, the LFN API implementation introduced with W2K is a can of
worms, and it will take time to work around that.  Wherever you take a good
look, you find subtle misfeatures and bugs.

- Raw text -