Date: Thu, 30 Dec 1999 09:45:18 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Edward F. Sowell" <sowelled AT home DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: new release of LFN for Windows NT 4.0
In-Reply-To: <386A95CC.DAED1EF7@home.com>
Message-ID: <Pine.SUN.3.91.991230094456.20984N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 29 Dec 1999, Edward F. Sowell wrote:

> 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.

This is expected.  CreateProcess creates a separate Virtual Machine
and runs the program inside that VM.  You need to arrange for the LFN
driver to be loaded in that VM as well.

> But,
> merely doing another CreateProcess("lfnlaod"), so to speak, will not work
> because it's a separate process.

Try creating a batch file which loads the LFN driver and then runs
your *real* application.  Then launch that batch file by calling
CreateProcess to run it via cmd.exe.