Message-Id: <199803110051.TAA11353@owl.INS.CWRU.Edu>
Date: Tue, 10 Mar 1998 19:51:20 -0500 (EST)
From: jls11 AT po DOT cwru DOT edu (John L. Spetz)
To: opendos AT delorie DOT com
Subject: Re: Long File Name Use  
Reply-To: jls11 AT po DOT cwru DOT edu (John L. Spetz)
Precedence: bulk

Reply to message from chrispwilson AT juno DOT com of Sat, 07 Mar
>
>On Sat, 7 Mar 1998 12:42:54 +0000   Robert Parker
><rparker AT thefont DOT demon DOT co DOT uk> writes:
>>Hi,
>>I've installed the long filename beta product but when I try to pass a
>long
>>filename to the DJGPP compiler (gcc) it complains that the file cannot
>be found.
>>
>Windows 95 / Caldera LFN uses a completely different method of accessing
>file names than standard MS-DOS. Programs using LFN support use a
>different system call (INT 21h, AH=71h) to access file system routines
>instead of the standard DOS ones. Even with LFN support loaded, programs
>that don't recognize LFN support can still access the old 8.3 file names.
>DJGPP probably doesn't recognize long filenames - you still need to use
>8.3 ones with it, like you do with almost every DOS program.
>

AFAIK the DJGPP compiler does support LFN.  I would imagine that many
W95 compatible programs check for W95 before calling the new INT functions
though since they are brand new in W9x/WNT.  I *am guessing* that DJGPP
checks for Windoze 95, says to itself no W95 too bad, then goes ahead
and uses SFN for compatibility.  I remember reading in the latest 4dos
update list that JPSoft added support for LFN from Dos rather than W95
presumably in anticipation of tsrs like the one in OpenDOS.  I imagine
many programs don't bother with this. :(

Actually isn't there an LFN= setting in DJGPP.ENV that controls this 
support?  Is that turned on?