Date: Wed, 22 Dec 1999 12:20:54 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Wojciech Galazka <wojciech DOT galazka AT polkomtel DOT com DOT pl>
cc: djgpp AT delorie DOT com
Subject: Re: new release of LFN for Windows NT 4.0
In-Reply-To: <83nrl0$qo4$1@sunsite.icm.edu.pl>
Message-ID: <Pine.SUN.3.91.991222121931.25983D-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 Tue, 21 Dec 1999, Wojciech Galazka wrote:

> 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

I have one problem with this version: it says in the README to edit
CONFIG.NT.  This requires access privileges that mere mortal NT users
don't have (at least on the NT machine to which I have access).
                                                                                
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?