uTorrent -Serenity- 2.2.1 Build 25130 - NEW4

[Biltu]

Will it working good on VMware Workstation ? I mean is there any possibility that using virtual operating system uSerenity send corrupted data to tracker ? kindly reply please.

[Lucius]

Will it working good on VMware Workstation ? I mean is there any possibility that using virtual operating system uSerenity send corrupted data to tracker ? kindly reply please.

I don't think so.

[anon]

VMware is used by companies and hosting providers to run virtualized servers. You can consider it to have proven reliability.

[Sazzy]

VMware is used by companies and hosting providers to run virtualized servers. You can consider it to have proven reliability.

Those don't use Workstation though but stuff like ESX.
But your point still stands.

[rizmack]

Hi there,

I'm looking for some help, when I try to extract the uSerenity folder, I receive the following error:


Any ideas on how I can solve this please?

Thanks!

[anon]

Windows cannot decrypt ZIP archives that use AES-256. Use 7-Zip or WinRAR to decompress it.

[rizmack]

Awesome, many thanks anon.

[yoco]

Noob question. What does "disk overloaded" mean? Honestly, I'm using uSerenity forever and I've never seen this before. It happens when I download multiple files at one!

[anon]

Disk overload means uTorrent can't write files to disk faster than they're downloaded (which is the expected behavior). You need to tweak the disk cache settings in the program to avoid this. Try something like the following.

[X] Override automatic cache size and specify the size manually (MB): [ 600 ]
[ ] Reduce memory usage when the cache is not needed

[X] Enable caching of disk writes
    [ ] Write out untouched blocks every 2 minutes
    [X] Write out finished pieces immediately

[X] Enable caching of disk reads
    [ ] Turn off read caching if the upload speed is slow
    [ ] Remove old blocks from the cache
    [ ] Increase automatic cache size when cache thrashing

[Master Razor]

My logic is this:
Since uTorrent is 32-bit process, it cannot access more than 2GB of RAM. If you put 2GB as cache, uTorrent will use the entire ammount for caching but will not remain any memory left for uTorrent itself if it needs to.
Thus, 1800MB cache, with 200MB on the side for uTorrent process.

[yoco]

Disk overload means uTorrent can't write files to disk faster than they're downloaded (which is the expected behavior). You need to tweak the disk cache settings in the program to avoid this. Try something like the following.

[X] Override automatic cache size and specify the size manually (MB): [ 600 ]
[ ] Reduce memory usage when the cache is not needed

[X] Enable caching of disk writes
    [ ] Write out untouched blocks every 2 minutes
    [X] Write out finished pieces immediately

[X] Enable caching of disk reads
    [ ] Turn off read caching if the upload speed is slow
    [ ] Remove old blocks from the cache
    [ ] Increase automatic cache size when cache thrashing

I'll try that!

[anon]

My logic is this:
Since uTorrent is 32-bit process, it cannot access more than 2GB of RAM. If you put 2GB as cache, uTorrent will use the entire ammount for caching but will not remain any memory left for uTorrent itself if it needs to.
Thus, 1800MB cache, with 200MB on the side for uTorrent process.

Version 3.4.7 forces you to set a cache size between 32 and 1800 MB, what about 2.2.1?

I'll try that!

Did it work?

[yoco]

I think it did. I also lowered number of downloads to 5.

[Master Razor]

Version 3.4.7 forces you to set a cache size between 32 and 1800 MB, what about 2.2.1?

Exactly. Developers are forcing you to set a maximum of 1800 with 200 left for the process.
2.2.1 has no such limit but you get the idea.

[simexi]

Are you getting "proper" speeds with this?

---------- Post Merged at 12:21 ---------- Previous Post was at 12:10 ----------

Nevermind, maybe just bad luck...