X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Bad command or file name error Date: 8 Mar 2002 13:40:12 GMT Organization: Aachen University of Technology (RWTH) Lines: 28 Message-ID: References: <6480-Fri08Mar2002152714+0200-eliz AT is DOT elta DOT co DOT il> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1015594812 243 137.226.32.75 (8 Mar 2002 13:40:12 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 8 Mar 2002 13:40:12 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote: >> From: "Robert" >> Newsgroups: comp.os.msdos.djgpp >> Date: Fri, 08 Mar 2002 12:31:14 GMT >> >> I am getting the following when I run a program from the DOS prompt under >> Windows XP >> " Bad command or file name error " >> >> But then the program comes up directly underneath..?? > Yes, I've seen this on W2K as well. I have no idea why is the error > message happening, though. If someone can explain that, please do. Just a vague idea: on NT-based platforms, the "command prompt" is not really a DOS prompt. The command line processor is cmd.exe, not command.com. This means that this environment only becomes a DOS VM in the moment you start a DOS program from it. This would mean that any startup actions for DOS VMs (including equivalents of autoexec.bat, dosstart.bat, if any such exist, or even commands stored in the registry), would be executed in this moment, before your DOS program is started. In a nutshell, I guess a broken path in an autoexec.bat-workalike startup procedure could cause this message. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.