From: "Wojciech Galazka" <wojciech DOT galazka AT polkomtel DOT com DOT pl>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: new release of LFN for Windows NT 4.0
Date: Thu, 23 Dec 1999 09:53:38 +0100
Organization: http://news.icm.edu.pl/
Lines: 19
Message-ID: <83snur$3vl$1@sunsite.icm.edu.pl>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 991222121931 DOT 25983D-100000 AT is>
NNTP-Posting-Host: plus249.polkomtel.com.pl
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 8bit
X-Trace: sunsite.icm.edu.pl 945939227 4085 193.58.71.122 (23 Dec 1999 08:53:47 GMT)
X-Complaints-To: abuse AT news DOT icm DOT edu DOT pl
NNTP-Posting-Date: 23 Dec 1999 08:53:47 GMT
X-Newsreader:  Microsoft Outlook Express 4.72.3110.5
X-MimeOLE:  Produced By Microsoft MimeOLE V4.72.3110.3
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


Eli Zaretskii napisał(a) w wiadomości: ...
>
>Is there any alternative way of enabling NTCMDPROMPT?  If not, why does
>the LFN support require NTCMDPROMPT, and what bad things will happen if I
>don't enable it?

Hi,

You can create a shortcut to %SystemRoot%\System32\cmd.exe on the desktop
and you do not need modify the config.nt file.

One can use LFN without NTCMDPROMPT  but once they're run in the "Command
Prompt" window then DosKey stops workings which is quite annoying.