Windows native and system copy

[GCC Consulting]

> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com 
> [mailto:filepro-list-bounces at lists.celestial.com] On Behalf 
> Of Kenneth Brody
> Sent: Tuesday, March 22, 2005 10:31 AM
> To: Nancy Palmquist
> Cc: Filepro 2 List
> Subject: Re: Windows native and system copy
> 
> Quoting Nancy Palmquist (Tue, 22 Mar 2005 10:15:56 -0500):
> [...]
> > Ken,
> >
> > While I understand you always work in a world where the OS works 
> > perfectly,
> 
> Hardly.  I've had my XP systems bluescreen, and I know what 
> horrors await if my 98 box goes to 0% resources available 
> (it's currently down to 15%).  I even had a Unix box lock up 
> hard (no crash, no panic, just everything freezes for all 
> terminals immediately) when you tried to do the equivalent of 
> "unlink( (char *)-1L )" due to a bug in filePro at the time.
> 
> > I also understand that we are talking about Windows and I 
> have yet to 
> > see any Windows version work perfectly.  There are always driver 
> > issues, network issues, OS bugs and no matter how many patches you 
> > install it is still broken in one way or another.
> 
> I've run into plenty of issues.  However, I haven't (yet) run 
> into the problem of a file not being there until later.  
> Apparently, others have, and the SLEEP appears to work around 
> the system bug.
> 
> > So if a small pause gives the wacky OS time to get itself together, 
> > then so be it.
> 
> True.  On the other hand, what's going to happen when the 
> system bug requires a 6-second delay to work around?  ;-)
> 
> --
> KenBrody at BestWeb dot net        spamtrap: 
Ken,

Change the sleep to 6000 or something longer.

All that aside, the file I am copying is there, the problem is, I think, that
the OS still has it locked.  It is "taking its own sweet time" to release it for
other uses. :) 

Maybe this wouldn't be a problem if I ran the task from on of the XP
workstations that are never shut 
off.  Maybe the network latency would compensate for any problems with the task
manager.

Richard