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

Number   :  4925
Date     :  2003-07-01
Author   :  Melissa Evans
Subject  :  Re: xxcopy hanging in scheduled tasks
Size(KB) :  2


--- In xxcopy@yahoogroups.com, Joe Armstrong-Champ  wrote:
> The fact that you see it happen with copy means that it may be a 
problem
> with the scheduler rather than xxcopy. Did you have any luck testing
> over the w/e?
> 
> Joe

Joe, We run scripts at will ("scripts"=batch files & Python code), to 
push data files around between the server and many locals
("many"=more than several). None of it is run through the scheduler. 
When a part has been tested, the test software uploads the data; 
likewise with the analysis software and "run" software. In addition, 
there are scripts that update our "Master" directory on the server, 
and the local copies of the Master with their individual 
requirements. and, there are scripts that archive data files from the 
server to CDs. None of this would be possible without xxcopy.exe and 
its myriad switches; I rarely write a script that uses /clone. When 
Kan's team releases a new version, I cringe in fear at the same time 
that I drool at new possibilities.

Our server OS is Windows 2000. The locals run from W95 to WME.
Because we are cursed with some legacy software that as yet has not 
been rewritten, we still need a DOS 16-bit window and xxcopy16.exe.

We have two particular "hanging" problems. When the more benign one 
occurs, the script appears to hang, but then over a minute later it 
begins to work again, v-e-r-y s-l-o-w-l-y. We see this less often 
since we replaced Lantastic software with Windows Client software,
but it still happens. Usually, restarting the PC helps. Sometimes 
restarting makes no difference.

The less benign problem happens on certain computers more than
others, but it has happened on every computer at least once, and,
this is what happened at least once using command.com's COPY. A 
copy activity hangs up while copying a file from the local to the 
server. On the server, the file's name with "now" as date and time 
has been written, but that's all. The file cannot be deleted because 
the permission is locked. The local computer has to be restarted 
with the Reset button or turning off and on. If a script was 
running an xxcopy command line that was going to clear the archive 
bit after copying (/m), the archive bit was not cleared. On the 
server, the corrupt file is either zero bytes in size, or it will be 
about 1500b; it is expected to be about 1.2Mb.

I have had to write a script that finds these files on a local, and 
replaces the corrupt ones on the server with the uncorrupted ones
from the local.

Part of my problem is that I don't know how computers and network 
software work. Mostly I watch some bizarre thing happen, and wail, 
"What the ---- is it DOING."

Melissa Evans
ASML Optics, LLC
Richmond CA



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