From:	Bill Currie <bill AT taniwha DOT tssc DOT co DOT nz>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Question: getcwd() and LongFileName support
Date:	Wed, 01 Jul 1998 19:45:52 +1200
Organization:	NetLink Wellington, New Zealand.
Lines:	24
Message-ID:	<3599E930.CADB651D@taniwha.tssc.co.nz>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 980630102452 DOT 6274Q-100000 AT is>
NNTP-Posting-Host:	nzlu02.tssc.co.nz
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

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.

Yeah, it's called command.com.  if you cd into a directory using the
SFN, the Windows LFN getcwd function returns the SFN :(.  Actually,
that's not *quite* true, it returns whatever you typed (cd StUdLy into
studly would return StUdLy, IIRC).  Just another reason to hat M$ :)

Bill
-- 
Leave others their otherness.

- Raw text -