From: sandmann AT clio DOT rice DOT edu (Charles Sandmann) Message-Id: <10109201335.AA19141@clio.rice.edu> Subject: Re: W2K error message documentation To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii) Date: Thu, 20 Sep 2001 08:35:05 -0500 (CDT) Cc: djgpp-workers AT delorie DOT com (DJGPP developers) In-Reply-To: from "Eli Zaretskii" at Sep 20, 2001 10:36:35 AM X-Mailer: ELM [version 2.5 PL2] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 > > "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?). It's on the Win2K status page as a problem, but he couldn't remember when/where it happened. Trying to clean up loose ends. > > 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). Just wondering if we should be smart about if CMD.EXE is around. The error message doesn't bug me. I've ignored it until now :-) > > Change the makefile to suppress it? Ignore it? > > Why not report it to Microsoft? Who knows, they might even fix it... I'll probably report it, but a cosmetic error in a legacy subsystem ... > > 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? I just noticed in testing that md with a long name truncated it to 8 characters. I haven't done any further testing yet. I know that many of the long name functions do work, so it's a partial thing. Another thing that doesn't work: cd "program files" fails (but works OK on 9x). cd "windowsupdate" doesn't work either. Redirection into a long name does work. > 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. Why I sent the heads up before complete testing.