FileCopy Eats CPU
Keywords: filecopy
Question:
I often have to copy files at about 600 MB. I use the WBT command "FileCopy". But on my NT 3.51
machine the batch eats nearly 98% of processor time making all other applications extremely slow.
NT does "multi-task", other applications do run, but are extremely slowed down.
They do not get enough
pieces from the CPU cake.
Any idea how to make FileCopy more "cooperative"?
Answer:
In the 32 bit version we just call the FileCopy Windows API. It copies the file for us.
- Are you using the 32 bit version of WinBatch?
- Is WinBatch the active window? If you're doing the FileCopy from a "Call"ed WinBatch
script (using the Call function), you need to make that window active, with something
likes the BoxOpen command (see the WINBATCH.HLP file) during the FileCopy process. This
will give WinBatch the focus during the FileCopy.
Some people with vaguely similiar problems use the DOS filecopy instead.
(But that was on Windows 3.1) Then you can configure such things via a PIF file...
Article ID: W13061
Filename: FileCopy Eats CPU.txt
File Created: 1999:04:15:16:51:30
Last Updated: 1999:04:15:16:51:30