Date: Thu, 20 Sep 2001 10:36:35 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: DJGPP developers <djgpp-workers AT delorie DOT com>
Subject: Re: W2K error message documentation
In-Reply-To: <10109200249.AA17712@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1010920103610.3922G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 19 Sep 2001, Charles Sandmann wrote:

> The command (present in the mak3791 makefile) under Windows 2000 or XP:
> 
> "command.com /c if not exist glob\nul md glob" 
> 
> Returns "Extended Error 183" only if directory exists.  If not, it creates it.

Yes, this was reported before by someone (Andrew?).

> I think this is cosmetic W2K bug/issue.  Should we worry about it?

Probably not, since there's no easy solutions (using %COMSPEC% doesn't
always work, and can even have adverse effects if the user has 4DOS or
4NT installed).

> Change the makefile to suppress it?  Ignore it?

Why not report it to Microsoft?  Who knows, they might even fix it...

> Using command.com only allows the md command to be limited to short names,
> something I found in testing

That might actually be very bad.  Are you saying that COMMAND.COM
which comes with Windows 2000 and XP doesn't support long file names
at all, or is that non-support limited to md?

If there's no LFN support in COMMAND.COM, various config.bat files
will start failing in mysterious ways, because they generally assume
that LFN is supported in the same way by the shell and by DJGPP
programs.  In that case, I think we will have to figure out a way to
run cmd.exe on such systems.