diagnosing a .cmd file that is not working

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

pj - 30 Nov 2006 12:05 GMT

I have used a .cmd file to backup with xcopy on a couple of XP machines just
fine. It lives on the desktop and a double click runs the back-up.

Trying the same file on a new machine and it does not work and the dos
window disappears before I can read it.

No doubt this is a really simple thing, but I can't find out how to make the
dos window persist till I have read the error message.

All help gratefully received. A pointer to a primer on these things would be
great too, my searches return more complex stuff than I need or understand!

All the best, PJ

Reply to this Message

Grand_Poohbah - 30 Nov 2006 14:52 GMT

Open up a command window (Start -> Run CMD) and then navigate the old way to
your .cmd file and execute it. Since you manually opened the command window,
it won't go away until you type EXIT at the prompt.

GP

> I have used a .cmd file to backup with xcopy on a couple of XP machines just
> fine. It lives on the desktop and a double click runs the back-up.
[quoted text clipped - 9 lines]
>
> All the best, PJ

Reply to this Message