[<<]Message[>>]    [<<]Author[>>]    [<<]Subject        [<<]Thread    

Number   :  5400
Date     :  2003-08-22
Author   :  Garry Deane
Subject  :  Re: "Insufficient memory"
Size(KB) :  1


--- In xxcopy@yahoogroups.com, "Colin Culpitt-Smith"  
wrote:
> PS - has anyone any idea why the Progess Bar hangs, when
> used in a batch file? At least it does in mine, when using
> XXCOPY under Win98SE in a Dos box.

I just tested your command using v.2.84.9 Freeware on a
W98SE PC and it closed the window on completion.

I'm not sure what's wrong with your setup other that what
Kan has already mentioned. You could try adding a cls; exit;
to your batch file which is the usual way to close a command
window when a batch completes (I didn't have this in my test,
just the 'close on exit' setting for the shortcut).

The usual reason for a command window not to close is that
it still has processes running (the progress bar). To debug
this situation, you could get a process explorer utility to
see which processes the command window still owns which
might point to why the process is not ending. If you can't
resolve it, you could always get a KILL utility to terminate
the errant process which should then allow the window to close.

Garry



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.