Message-ID: <01FD6EC775C6D4119CDF0090273F74A455A6A9@emwatent02.meters.com.au> From: "da Silva, Joe" To: "'opendos AT delorie DOT com'" Subject: RE: batch file problems Date: Thu, 9 Aug 2001 17:51:24 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Reply-To: opendos AT delorie DOT com Have you run "chkdsk" or "scandisk" lately? Joe. > -----Original Message----- > From: DONALD PEDDER [SMTP:jims_son AT jedi DOT apana DOT org DOT au] > Sent: Thursday, August 09, 2001 12:34 PM > To: opendos AT delorie DOT com > Subject: batch file problems > > I have a batch file with a copy in it, followed by the line... > > if errorlevel 1 goto nofile > > The "nofile" part of the script just writes a message to the screen to > say the file doesn't exist and exits. Here is the problem... > > I tried the command, and was told the file didn't exist - I knew it > did. Doing the command manually works. I've already found before there > are (annoying) differences between DR-DOS and MS-DOS, so I re-booted into > Windows. The batch file worked okay, so I re-booted to DR-DOS again. > After this re-boot, it worked. "just a glitch" I thought. I then found > however that even putting a file that DOESN'T exist allowed the batch file > to still continue as though it did. > > So, in my first session I was told files didn't exist, whether they did > or not, and after the re-boot I was told they DID exist, whether they did > or not. Anyone know what is going on here? I don;t know if the copy > actually ran the first time (but I think it did), as I wasn't paying that > much attention. Now I can't re-create it as I now have the OPPOSITE > problem. > > > regards, > DONALD - Left-Brain Extraordinaire,Right-Brain in Rehab. > > E-mail - donaldp AT au DOT mensa DOT org > BIG DON's Home-page - http://www.jedi.apana.org.au/~jims_son > (Pedder Passer(Quarterback) Rating,Kirlian photo's,the best of The Beast) > > "What I always wanted is to be accepted,not understood" - MAN RAY