Slow File Copy

  • Thread starter Thread starter Troy Murphy
  • Start date Start date
T

Troy Murphy

Terminal Server seems to be very slow when doing a file copy unless the user
continues to click in the client area during the copy operation. I can
reproduce this behavior in a VFP form and a .NET form running on Windows
2003 using the native file copy operations (VFP copy file x to y .NET
FileCopy) as well as the windows scriptiong host
(createobject("scripting.filesystemobject") and the CopyFile API in
Kernal32. The source and destination are local folders (local to Termianl
Server - they are NOT client shares.) and when the button is pressed to copy
a file, the system can take several minutes to copy a 12k file or eventually
timeout. However if the user keeps clicking the form after the copy
operation starts, it happens quickly.
Help!
 
Wow, I figured a 'supergeek' would have had this answered by now :-).
Just kidding - anyway some more information on this problem:

This only happens when the client is using Windows 2000. XP works fine.

Updating the tsclient application on the 2000 client does not resolve
this issue.

The application we are testing is VFP and displays a clock on the
statusbar and the clock also stops when the pause occurs.

Creating a new file from the contents of a file seems to work fine
(string to file of file to string). Of course this will not work on large
files.

Clicking on the taskbar also resumes the copy operation.

Behavior is the same regardless of remote desktop connection or web entry
to the RDP.

So, if Windows XP works and 2000 does not even with an update tsclient, what
else is there to check?
 
Back
Top