You don’t know that any of that is applicable. The way this guy tests, he changes six different things at once. EVERY variable is uncontrolled.
Focus on the idea that the Open Office torrent is slow. Now, what could slow it down? It was fast, now it’s slow, he says.
I don’t think that the version is relevant, or the language. Nevertheless, let’s still eliminate those as variables, so try the torrent for the US English version without JRE.
Try to make this transfer slow.
Start it in no-listen mode.
Disable LT-seeding which also disables LT downloading.
Ban every client except µtorrent.
How’s the speed? Still maxed out?
Stop delete the task and files, close BC, restart it, load the task again with all those conditions on/active.
How’s the speed? Still maxed out after a few minutes? Me, too.
Until you can duplicate this problem, you’re still just guessing. And if you trust his reporting, then it will have to be something that does NOT slow down µtorrent, so that eliminates network issues as such.
A man, as Harry Callahan said, has to respect his own limitations. You’ve got to have an awareness of the possibility of your own faults and flaws. He has none. It is all someone or something else’s fault.
The most common issue in flight disorientation, “my instruments went haywire”, is not that the instruments misbehave, it’s that the pilot doesn’t believe what they’re telling him, so he filters it and reports that.
Make the open office torrent slow for BitComet but not for µtorrent. Eye on the ball.
Now if you can’t make it happen, then what?
(BTW, if you really want to run this off a new partition and think that’ll make a difference, then make yourself a new user account and run BC off a thumb drive. There, it’s on a different partition.)