From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: My NT installation wants '\' in the dir command
Date:	Sat, 09 Nov 2002 11:10:34 CST
Organization:	Rice University, Houston TX
Lines:	18
Message-ID:	<3dcd418a.sandmann@clio.rice.edu>
References:	<B66B0B4BF675D411BDCF00508BE32B120C8D3834 AT emss01m06 DOT ems DOT lmco DOT com> <3dcaed25 DOT sandmann AT clio DOT rice DOT edu> <3DCC1D88 DOT B56C4E6 AT lmco DOT nospam DOT com>
NNTP-Posting-Host:	clio.rice.edu
X-Trace:	joe.rice.edu 1036862057 21679 128.42.105.3 (9 Nov 2002 17:14:17 GMT)
X-Complaints-To:	abuse AT rice DOT edu
NNTP-Posting-Date:	9 Nov 2002 17:14:17 GMT
X-NewsEditor:	ED-1.5.9
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> I did read the readme.1st file and noted that unzip did put long
> filenames to the disk, i.e., sysmacros.h versus sysmacro.h.

You used a Win32 unzip utility instead of a DOS based one.

> There is something different with NT.  When I do 'dir', I see support
> for long filenames.  When I do 'ls' I see 8.3 filenames.

Windows NT has two APIs - a native Win32 API which supports long file
names - and a virtual DOS machine which supports DOS interrupts.  DJGPP
applictions are DOS API.  Microsoft chose to not provide long name support
for DOS applications.  So "dir" uses Win32 calls - sees long names.
"ls" is a DJGPP application and only sees short names because that's all
Microsoft decided to allow.  The ntlfn08b.zip distribution contains a
cool workaround/fix for this problem to support the DOS long name API
under Windows NT, which makes it behave like Windows 2000 (but with
fewer bugs than Windows 2000...)

- Raw text -