Hi there, a newly discovered problem on my DOpus installation,
copying any particular group of files to an external drive causes dopus to consume 100% cpu usage. Even during the filecount phase.
Copying the same files to another internal drive is fine.
Copying the same files again, using explorer only uses about 10% cpu, and is nice and fast...
Anyone else having this problem?
I've only copied with drag and drop a 350 MB file to my external HDD and everything went fine, normal CPU usage.
Weird - what happens if you copy a different set of files FIRST with explorer - and THEN again with opus?
What have you got set for the various File Operations preferences that would affetc file copyying and progress window info...?
Hi.
I tried using Windows Explorer first, same end result.
In directory opus settings, im using the settings:
Clear read only tags from cds
preserve attributes, and timestamps.
64kb buffer
in progress indicators im using:
count files before copying
800ms time delay on progress bar
show percent complete
Today i swapped my drives, internal->external. and the problem is gone.
I am a little confused, but i might just leave the drives as they are for the moment.
Okay. Its my system. I has to be...
Placing the drives back to their original configuration, everything is working as expected. No cpu hangups, and full speed transfers.
Either windows has had a moment with the via/usb drivers, or its just one of those weird conflict things ?? 
Thanks all the same.
Sometimes changing the buffer size helps with certain USB devices, but if the problem occurs before the copy itself starts then that probably won't help. It's quite odd.
Might be worth a try disabling your anti-virus program to see if that is going wrong in this situation. The effects of most AV programs will apply to the processes which access files, rather than the exe for the AV program's process.
There's nothing in Opus that should cause the problem, but Opus does copy files in a slightly different (but still perfectly normal) way to Explorer, so sometimes Opus triggers problems that Explorer doesn't. (Also, everyone tests their stuff works with Explorer, of course.)