Subj : Re: Windows 2000 and legacy programs To : Steven.Horn From : Tony Ingenoso Date : Mon Feb 26 2001 06:34 pm From: "Tony Ingenoso" You can also insert PAUSE's between each line to simulate single step -- this is a universal version neutral fits all solution. To make it less offensive and not need to be constantly edited do it like this: rem to turn on debugging enable this line set BATDEBUG=PAUSE rem to turn off debugging enable this line set BATDEBUG=rem blah, blah, blah... %BATDEBUG% blah, blah, blah... %BATDEBUG% blah, blah, blah... %BATDEBUG% This way you need only enable the batch file debugging one place to have it apply globally in the batch file. When turned off, the PAUSE's just morph into harmless REM's. wrote in message news:a07d22.5a985c@harborwebs.com... > * Copied (from: BINKLEY) by Steven Horn using timEd/386 1.10.y2k+. > > Paul Quinn (3:640/384) wrote to Steven Horn at 15:48 on 26 Feb 2001: > > PQ> Later versions of MS-DOS are capable of 'stepping-through' batch > PQ> execution. Try this in a DOS box: > > PQ> command /y /c [name_of_your_batch] > > PQ> Enter a message into some sort of local/test echo, and then follow > PQ> the logic flow of your batch to find the problem. It gets a bit > PQ> tedious, but it should certainly show the fault. > > By God, you've solved my problem. I found that I'd looked at the batch file so > long that I'd mis-written part of it and I had a path problem as well but all > is OK in the Yukon again.:-) > > ------------------ > I am passing this on because it addressed my problem. > > Take care, > > Steven Horn (shorn@yknet.ca) > Moderator, ALASKA_CHAT and CAN_SYSLAW > --- timEd/386 1.10.y2k+ > * Origin: North_of_60ø, Whitehorse, YT, Canada (1:17/67) --- BBBS/NT v4.00 MP * Origin: Barktopia Gating Project http://HarborWebs.com:8081 (1:379/45) .