From: leathm AT solwarra DOT gbrmpa DOT gov DOT au (Leath Muller)
Message-Id: <199708140600.QAA20079@solwarra.gbrmpa.gov.au>
Subject: Re: NT 4 ?s/Problems
To: andrewc AT rosemail DOT rose DOT hp DOT com (Andrew Crabtree)
Date: Thu, 14 Aug 1997 16:00:32 +1000 (EST)
Cc: djgpp AT delorie DOT com
In-Reply-To: <01bca802$1c2f15a0$45111d0f@ros51675cra> from "Andrew Crabtree" at Aug 13, 97 06:24:43 pm
Content-Type: text
Precedence: bulk

> My trustworthy Win95 pentium machine was just replaced with 
> a PPro NT 4.0 machine.  Most things appear to be working OK.  Bash
> finally runs for me even.  I just can't figure out what apppears to be an 
> LFN related problem.  I have mapped a network drive from my unix 
> machine through Samba.  The problem is that most of the DJ type tools
> don't see files on this drive.  If I do a 'dir' I get a good directory
> listing.  If I try 
> 'ls' I get enoent errors.  I have tried setting LFY to yes and no, but get
> the same 
> error both times.  I know that the NT LFN api is not up to snuff, but this
> is impossible to use it seems.

NT will _sometimes_ work fine with LFN's, and then othertimes not... I
have pretty much come to the conclusion it depends on what sort of mood it
is in... ;)

For example, if you change into a long filenamed dir, it will change fine
and update the prompt fine. Run a program such as vi though, and when you
chunk out again it truncates the LFN to a SFN... This is just something
that appears to be unavoidable on NT4's cmd.exe...

I think the NT dir command is deliberately coded to look at LFN's for
files done in Win95 and NT (NTFS) but ls must used a DOS interrupt or
something different to dir...

Leathal.