X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Rugxulo <rugxulo AT gmail DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Isues concerning the INT 21 Windows95 - LONG FILENAME FUNCTIONS
 (0x71XX) implementation.
Date: Sat, 17 Sep 2011 11:52:56 -0700 (PDT)
Organization: http://groups.google.com
Lines: 42
Message-ID: <2dc464f3-6f8c-4139-8dcb-0719e25116bf@i39g2000yqn.googlegroups.com>
References: <201109171356 DOT 53360 DOT juan DOT guerrero AT gmx DOT de> <CAA2C=vD-Lzrt2z=gkkQcrgmssdh6F7vgU_kwVgu6o9iPGykMJQ AT mail DOT gmail DOT com>
NNTP-Posting-Host: 65.13.115.246
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1316285992 13905 127.0.0.1 (17 Sep 2011 18:59:52 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Sat, 17 Sep 2011 18:59:52 +0000 (UTC)
Complaints-To: groups-abuse AT google DOT com
Injection-Info: i39g2000yqn.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-Header-Order: HUALESNKRC
X-HTTP-UserAgent: Mozilla/5.0 (X11; Linux i686; rv:5.0.1) Gecko/20100101 Firefox/5.0.1,gzip(gfe)
Bytes: 2926
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p8HJF2um030740
Reply-To: djgpp AT delorie DOT com

Hi,

On Sep 17, 8:56 pm, Ozkan Sezer <seze DOT  DOT  DOT  AT gmail DOT com> wrote:
> On Sat, Sep 17, 2011 at 2:56 PM, Juan Manuel Guerrero
>
> <juan DOT guerr DOT  DOT  DOT  AT gmx DOT de> wrote:
> > Here is a patch
> > - to set always the CF flag before calling a 0x71XX function
> > - to check that AX does not contain 0x7100 after return signaling
> > that the driver supports the called function.
> > - to react if the driver does not support the function.
> > In almost all cases I followed Eli Zaretskii's suggestions.
>
> Tested this _very_ briefly on IBM PC-DOS 7 + DOSLFN 0.40e
> (from http://adoxa.110mb.com/doslfn/) by running hexen2 for dos,
> no problems so far with or without doslfn loaded in memory.
> FWIW, though, I have to note that all disk access was in 8.3 style.

You mean Hammer of Thyrion? I assume this means you rebuilt it.

http://uhexen2.sourceforge.net/

> <rant>
> With doslfn loaded, the hard disk scratching was unbearable to
> hear. Living with conventional dos is a bliss..
> </rant>

Yeah, LFNs are a pain sometimes. But most .ZIPs these days refuse to
live without them.   :-/

Anyways, DOSLFN is still a bit buggy, and technically I don't think
it's maintained (by Henrik or Jason) anymore. Recently Japheth did
contribute a very small (third-party) patch (re: FCBs or whatever),
but it still has issues.

Anyways, here's his (minor) fix w/ binary if you're curious, though of
course it's unofficial.

https://sites.google.com/site/rugxulo/DOSLF40F.ZIP?attredirects=0&d=1

P.S. You quoted his whole (long) message. Oops! Luckily I'm not one of
those that cares.   ;-)