Message-ID: <817531784725D411BB9F00508BC97CDC026A95@CLAVIUS>
From: Pat Ritchie <pritchie AT logikos DOT com>
To: "'Wojciech Galazka'" <wojciech DOT galazka AT polkomtel DOT com DOT pl>
Cc: "'Eli Zaretskii'" <eliz AT is DOT elta DOT co DOT il>, djgpp AT delorie DOT com
Subject: RE: Autodependencies and long filenames with Windows NT.
Date: Mon, 26 Jun 2000 08:24:29 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id JAA26775
Reply-To: djgpp AT delorie DOT com

thank you.
that worked for me.  when I manually invoked the lfnload, it worked.  I had
added that line to the autoexec.nt, but it still didn't work.  The FAQ only
has you copy the lfnsrv.dll file to the winnt\system32 directory, not the
lfnload.com file.  Anyway, long story short, the lfnload was not happening
as I thought it was.  I've got that fixed now, and it works as expected.
Thanks for the help, you steered me to the problem.

-----Original Message-----
From: Wojciech Galazka [mailto:wojciech DOT galazka AT polkomtel DOT com DOT pl]
Sent: Monday, June 26, 2000 2:30 AM
To: 'Patrick Ritchie'
Subject: Re: Autodependencies and long filenames with Windows NT.


Hi,

I have no problems with
gcc -MM test.c

I've created a dummy file2.h file that is included by longfilename.h

Then I loaded the LFN driver by issuing
lfnload in the directory where both lfnload.com and lfnsrv.dll reside
then I run gcc -MM test.c to receive in return

test.o: test.c longfilename.h file2.h

If you still have problems with the driver (I assume you're using the latest
version from lfn005.zip)
then please send me the error messages that gcc may generate

Thank you

Wojciech Gałązka
MCSE, MCDBA



> ----------
> Od: 	Patrick Ritchie[SMTP:pritchie AT logikos DOT com]
> Wysłano: 	23 czerwca 2000 16:25
> Do: 	Wojciech Gałązka
> Temat: 	Re: Autodependencies and long filenames with Windows NT.
> 
> <<Plik: test.c>><<Plik: longfilename.h>>
> you did what many times?  you have used header files will long filename
> and
> successfully were able to create autodependencies as the original post
> suggests?
> 
> are you able to:
> gcc -MM test.c
> ...on a Windows NT 4.0 machine and get the following output:
> test.o: test.c longfilename.h
> 
> If so, has this always worked, or did you have to do something, (install
> something) or what?
> Thanks for the help.
> 
> 
> 
> ----- Original Message -----
> From: Wojciech Galazka <wojciech DOT galazka AT polkomtel DOT com DOT pl>
> Newsgroups: comp.os.msdos.djgpp
> Sent: Friday, June 23, 2000 3:49 AM
> Subject: Re: Autodependencies and long filenames with Windows NT.
> 
> 
> 
> Pat Ritchie wrote in a message: <395346dc DOT 0 AT news DOT nownuri DOT net>...
> >Yes, I already did this before posting to this group.  I am just
> wondering
> >if anyone successfully performed this on a Windows NT 4.0 system?
> >
> 
> 
> Yes ,I did this many times. Did you experience any problems with that ?
> 
> 
> 
>