Sign in to follow this  
Followers 0
speedi

how can I keep dos command window open after runwait

5 posts in this topic

When I am debugging a runwait command, how can I keep the DOS command window open so I can see what errors might have occurred??

The window closes so fast I can't read it...

Thanks!

Share this post


Link to post
Share on other sites



assuming you are using @ComSpec: just change the /C to /K

These lines are not using @comspec --- they are like this: Run("C:\WINDOWS\SYSTEM32\XXCOPY.EXE " etc. etc.

Can I use @comspec for this line??? Thanks!

Share this post


Link to post
Share on other sites

These lines are not using @comspec --- they are like this: Run("C:\WINDOWS\SYSTEM32\XXCOPY.EXE " etc. etc.

Can I use @comspec for this line??? Thanks!

How about:
Run(@COMSPEC & "/k C:\WINDOWS\SYSTEM32\XXCOPY.EXE C:\Temp1\*.* C:\Temp2", @TempDir, @SW_SHOW)

:P


Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law

Share this post


Link to post
Share on other sites

In DOS, you can add the command "Pause" to the end, and you can see the error. for example, if you wish to edit a autoexec.bat file, you could put the following

c:\dos\loadhigh.exe
pause

For DOS, the "Pause"command will pause the script until you press a key. this way you can see what is happening.

More information here:

http://www.computerhope.com/pausehlp.htm

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0