From: JMK <jeffrey DOT m DOT klopotic AT lmco DOT nospam DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: My NT installation wants '\' in the dir command
Date: Fri, 08 Nov 2002 12:24:40 -0800
Organization: Lockheed Martin Corporation
Lines: 37
Message-ID: <3DCC1D88.B56C4E6@lmco.nospam.com>
References: <B66B0B4BF675D411BDCF00508BE32B120C8D3834 AT emss01m06 DOT ems DOT lmco DOT com> <3dcaed25 DOT sandmann AT clio DOT rice DOT edu>
NNTP-Posting-Host: 129.197.49.226
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com



Charles Sandmann wrote:
> 
> > However on an NT machine, it appears to want back slashes('\') versus
> > forward slashes ('/') for directory names.
> 
> This is probably not the problem.
> 
> > When I compile a simple hello world program, the W2000 works great, the NT
> > says it can't find file c:/djgpp/include/otherincludefile.h.  I do a dir on
> > c:\djgpp\include\otherincludefile.h and it *is* there.
> 
> If it has a long name (over 8.3 characters) you will either need to use
> the short name or install the long file name TSR.  Read the FAQ, and
> get v2misc/ntlfn08b.zip (from Simtel) to enable long file names under
> Windows NT.
> 
> If you can prove it's a problem with / instead of \, I'd be interested in
> a simple example which shows the problem.

Charles,
Thanks for the response.

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.

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.

I'll try the zip file.  This seems to be homing in on the filenames
issue.

Jeff

BTW, The '\' v '/' *is* there, even on Win2000.  But that's evidently
not what is causing the problem I'm seeing.