Message-ID:	<386A95CC.DAED1EF7@home.com>
From:	"Edward F. Sowell" <sowelled AT home DOT com>
X-Mailer:	Mozilla 4.7 [en] (Win98; I)
X-Accept-Language:	en
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: new release of LFN for Windows NT 4.0
References:	<83nrl0$qo4$1 AT sunsite DOT icm DOT edu DOT pl>
Lines:	68
Date:	Wed, 29 Dec 1999 23:13:40 GMT
NNTP-Posting-Host:	24.0.195.218
X-Complaints-To:	abuse AT home DOT net
X-Trace:	news1.alsv1.occa.home.com 946509220 24.0.195.218 (Wed, 29 Dec 1999 15:13:40 PST)
NNTP-Posting-Date:	Wed, 29 Dec 1999 15:13:40 PST
Organization:	@Home Network
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Wojciech


I tried you new NT lfn today. There is a minor error in the readme.txt regarding
installation: lnfsrv.com is
referred to, but its actual name is lfnload.com. No big deal.

I put the 2 files in a new directory and did the
recommented test. Got the message saying it was "registered". I notied, however,
that
this does not seem to mean in the WinNT registry. At least regedit|Find can't
find any
evidence of it, other than in the most recently used files list. You must mean
some other
kind of "registration." Not important.

To test it further I used my software that fails with DJGPP on NT  but runs on
Win95/98 with DJGPP.

Let me explain a little better what I am doing. I have a C++ program buildsolver
that reads a preference file to
get, among other things, the name of the make program to be used and other
things about the
build process about to begin. Then buildsolver sets up a command line and
launches make. The makefile
refers to dependencies with long file names, so make will fail if they are not
supported. Buildsolver
can be executed at the command line, but there is also a MFC Windows application
that gives the user
a GUI and launches buildsolver with CreateProcess(). This all works fine under
NT, Win98,
Win95 with DOS heritage C++ compilers and their  associated make programs and
linkers. Also works with DJGPP under Win95 and 98. Fails under NT due to lack of
the lfn API.

Now, with your lfn it works at the command line in a DOS box in which I have
run lfnload (Hurray!), but fails when launched with CreateProcess() from within
the Windows application.

The questions are, what's wrong, and how can I fix it? Obviously I have to
somehow do the
equivalent of running lfnload as a first step in the same process that
buildsolver is to run in. But,
merely doing another CreateProcess("lfnlaod"), so to speak, will not work
because it's a separate
process. I'm thinking out loud here... somebody help me along.

Ed Sowell


Wojciech Galazka wrote:

> Hi,
>
> I'm happy to announce a new version of my long filename services for Windows
> NT 4,.0
> based on NT-LFN by Andrew Crabtree. This version is much better than
> previous ones.
> You can grab a copy of it from http://www.cybertrails.com/~fys/longfile.htm
>
> Some thests have been performed and the results are in docs/results.txt
> file.
> The source code has been included as well.
> Have fun and please let me know if you find errors when playing with this
> piece of code. I don't have much time to read c.o.m.djgpp so I'd appreciate
> an e-mail message should you find anything unusual.
> Thanks

- Raw text -