From: Erwin Waterlander Newsgroups: comp.os.msdos.djgpp Subject: Re: Question: getcwd() and LongFileName support Date: Tue, 30 Jun 1998 18:26:06 +0000 Organization: XS4ALL, networking for the masses Lines: 35 Message-ID: <35992DBE.8C7C06BC@xs4all.nl> References: NNTP-Posting-Host: dc2-modem1574.dial.xs4all.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Eli Zaretskii wrote: > On Mon, 29 Jun 1998, Erwin Waterlander wrote: > > > It seems that the getcwd() function does not return LFN path under > > windows 95 but the DOS 8+3 style path. > > This is certainly NOT true in general. Assuming that you have > set LFN=y in the environment, and that other file-oriented functions > do support long file names, the only possible cause I could think of > is that some other non-DJGPP program that you are using causes > Windows 95 to become confused and return short 8+3 name of the current > directory. I have heard one such report in the past from somebody who > discovered that some program, when used in the same DOS box, would > cause Windows to behave that way. > > Anyway, for the record: getcwd works for me on Windows 95 and returns > long directory names. When is the LFN support activated then? At compile time or at run time? Can I compile a program under DOS 6.2 with LFN=y set and give this program to another person who runs it in a win95 dosbox and who has not DJGPP installed. Does that person need to set LNF=y in order to get LFN support? (I don't have win95 to verify this.) -- Erwin Waterlander Jongemastate 125 5655 HS Eindhoven The Netherlands www: http://www.xs4all.nl/~waterlan/