I am trying to move a drives files to another drive (both new and tested) around using the byte source comparison. I am using the copy function (though I would like a delete after confirmation). I have been trying to clear a 500 Gb drive for several days now (just leaving the machine alone and letting DOpus run). When I checked again this morning we were at 88% and barely moving in short bursts. During these bursts Vista would report 100% processor usage and 50% memory usage. DOpus is the only app running that shows up in Task Manager. Since one of my major issues is moving files around I am concerned that DOpus is not going to work for that purpose and I really need a file mover that does an MD5 or CRC confirmation on the fly with "move" capability. Anyone have any ideas?
Are you copying the data from or to an extremely fragmented drive?
Are you running a virus checker which may have gone haywire when inspecting one of the files being copied? (If that happens it will often appear that dopus.exe is using the CPU because the virus scanning code gets hooked into the process.)
Does copying the same data with something else work?
Adjusting the copy buffer size helps sometimes but shouldn't be needed for a copy from one HDD to another. That said, some poor USB devices/drivers are sensitive to buffer sizes so if one of the HDDs is connected via USB it might be worth a try. (I've only heard of this mattering for memory cards and FTP sites, though.)
Once the copy is complete you can use Opus's Synchronize tool in MD5 mode to confirm that the data is identical on both drives.
Do you have any sort of Desktop Search Engine installed? Don't forget that Windows comes with its own search indexer service, and it is notorious for slowing down large copy operations.
I'd double check your chipset Storage drivers, especially if it happens to be a new machine but of course it could be any number of things.
I've even had serious issues copying large amounts of files with a particular antivirus program, where explorer would just stop, saying that it had run out of memory, which was total nonsense. I'd say that Opus wouldn't give up so easily as explorer
