From:	babcock AT shell1 DOT cybercom DOT net (Robert Babcock)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Error in _use_lfn documentation
Date:	3 Feb 1997 21:25:48 -0500
Organization:	A poorly-installed InterNetNews site
Lines:	16
Message-ID:	<babcock.855022594@cybercom.net>
NNTP-Posting-Host:	shell1.cybercom.net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

The documentation for _use_lfn says

     "Note that on Windows 95 you don't need to distinguish
      between different drives: they all support LFN API."

This isn't quite true.  For example, I find that when running a program over
a peer-to-peer link from an OS/2 FAT disk, _use_lfn(0) returns 0.  I haven't
tested, but I wouldn't be surprised to find the same behavior with a Netware
disk which does not have the long namespace installed.

It was kind of funny.  Originally, my program broke because it was seeing
long file names and not expecting them, so I disabled LFN's.  Now, I'm adding
LFN support, and I couldn't figure out why I wasn't seeing the long names.
It wasn't until I copied the program to a Win95 disk and ran it from ther
that I understood what was happening.  It seems that I can fix the problem by
making an early call to _use_lfn("c:\\");.

- Raw text -