Message-ID:	<386BB7E8.CE542B7B@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:	31
Date:	Thu, 30 Dec 1999 19:51:28 GMT
NNTP-Posting-Host:	24.0.195.218
X-Complaints-To:	abuse AT home DOT net
X-Trace:	news1.alsv1.occa.home.com 946583488 24.0.195.218 (Thu, 30 Dec 1999 11:51:28 PST)
NNTP-Posting-Date:	Thu, 30 Dec 1999 11:51:28 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

The following suggestion by Wojciech works great. My code now runs under NT,
both
from command prompt and when launched with CreateProcess(). So, I suggest that
NT/DJGPP  users may want to put Wojciech's lfnload.com and lfn.dll files in
their system32 directory
and modify their autoexec.nt file as he suggests. In my case, there were some
examples
of other things being done in autoexec.nt that made it easy.

I will continue to use it and post any problems that bay arise.

Thanks, Wojciech, for this nice piece of work! Also thanks to Eli for his
guidance.

Ed Sowell

Wojciech Galazka wrote:
"Just an idea
Copy the lfn.dll into windows\system32 directory and add a line to
autoexec.nt to execute lfnload.com.
So if you call CreateProcess with the DOS app then ntvdm.exe which creates
DOS box should read autoexec.nt and
load the lfn services.

The "registered" message has nothing to do with Windows registry. I'll Check
MSDN if this "service" can be registered
so that it loads automatically on DOS box start-up

Thanks for trying out the codes."

- Raw text -