Simon100

Established Members
  • Content Count

    116
  • Joined

  • Last visited

  • Days Won

    1

Simon100 last won the day on December 14 2014

Simon100 had the most liked content!

Community Reputation

3 Neutral

About Simon100

  • Rank
    Advanced Member
  1. Not happening here... maybe a corrupted settings file? try with a blank settings.dat or resume.dat I've tried that as well... running in /recover mode w/ blank *.dat files... It's not a serious bug, when you put it in perspective, compared to the other bugs... I can live w/ repeating the command more than once...
  2. no... if you wait 2 minutes and then recheck - does it work? No, it still didn't work.. I just finished d/l a few more torrents about 200-400MB in size, and waited about half-hour to one hour before doing the "Force Re-Check" and it still took two tries before it kicked in.... Can someone verify this if it's not too much trouble? Not on something VERY large as it'll be time consuming but something in the half GB or less range... I remember in an older 3.3.x beta it took many tries to make Force Re-Check to work... but now, it takes two or three tries, at least a slight improvement, but a bug non-the-less....
  3. On uTorrent v3.3.2 build 30260, when a torrent just finished and I do a "Rght-Click Force Re-Check", nothing happens. Only if I do a "Rght-Click Force Re-Check" more than once, sometimes twice does uTorrent begins doing a "Force Re-Check". Is this a KNOWN ISSUE already? It seems uTorrent has ALOT of issues lately...
  4. I'm using the latest 3.3.1 RC r29812 and after using it for awhile, I noticed after downloading the torrent directory is moved into my "completed" directory, but the *.torrent file itself remains in the "incomplete" directory, which I have setup. This happens "randomly" it seems... Sometimes both the torrent directory & torrent file is moved, sometimes not. I then did a forced re-check & both items was immediately moved properly to the "completed" directory. This issue has never happened in any previous version that I've tried.
  5. v3.3.1 RC Build 29801, the menu - Help | Download Translation appears to be STILL broken...
  6. v3.3.1 RC Build 29801, the menu - Help | Download Translation appears to be STILL broken...
  7. Did uTorrent 3.3.1 stopped being "portable"? I use to simply copy the "*.dat" files into the same directory as uTorrent and it worked fine. eg on a USB drive or portable HDD. The FAQ that tells how it is done is still present, but the behavior has changed. But now, the *.dat files are copied all over the place and I also get that dreaded "Old Version of uTorrent Running" WARNING when I test different versions of uTorrent and Bittorrent v3.3.1/7.8.... Can someone point me to the new FAQ or instructions of how to make uTorrent "portable" again, without letting it copy its data files all over the place? Thanks...
  8. v3.3.1 beta 29594 BUGS I noticed a few minutes of testing: 1. Download Translation is broken. 2. uTorrent Help (F1) is OLDER -- v3.2.1 by Rafi whereas v3.3's help file is v3.3 by Rockett 3. Force Re-Check on a selection of completed Torrents ONLY checks 1st selected Torrent whereas the others/rest of them are immediately given "Finished" labels even though some of them are in fact incomplete. These 3 BUGS were not present in previous versions.....
  9. Force Re-Check is BROKEN in this Stable release. I have a group of finished torrents... and if I select several of them, it ONLY checks the 1st one and skips the rest.... Force Re-Check in 3.2.3 works, though... 3.3 does NOT....
  10. Can this build be runned as a portable app... executed on a higher drive letter, eg a large flash drive and NOT write ANY crap & junk onto the C: drive...???
  11. Just reverted another computer to v3.2.3 from v3.3.... Seems torrents were getting frozen in the middle of the night....Status bar turned "red"... w/ an error.... I had to exit and restart before v3.3 start working again.... or I could probably have just hit "start" button "again".... this is getting on my nerves... cache issue??? not sure, but this should NEVER have left beta testing....
  12. I think I'm gonna revert to 3.2.3 as well... appears 3.3 Stable isn't particularly "stable" after all.... I'll wait awhile for all you guinea pigs to submit the bug reports and the headaches and get it at least a bit more stable before I'm gonna use again.... perhaps wait for v3.3.1
  13. I have a torrent I created in the past of several episodes I recorded on my pvr.. I wanted to re-seed to my other computers downstairs.. but uTorrent 3.3 "Stable" claimed the 1st file is incomplete.. I verified it w/ my media player... then I fired up uTorrent 3.2.3 and entire torrent checked out fine. Is anyone else having problems w/ torrent verification?? It seems to be really buggy in v3.3 "Stable"...
  14. After finishing half dozen torrents, a Force-Recheck command will only perform the re-check on 1st selected file, the others checked WAY too fast to be believable..... It claims Finished when in fact nothing was checked.... that's cheatings
  15. MirceaForce, To be honest, SSDs are still a bit too expensive for massive storage... with a 1Gigabit/sec connection, which is about 125 MEGABYTES/sec... very few if any single HDD can sustain such speeds.... A Windows Server 2008 R2 or Server 2012 system is best to fully utilize such speeds w/ utorrent 3.3. Disk stripping would be required, where you can simultaneously write to more than one disk... Also a single 1Gigiabit/s NIC to your server is NOT enough... you should use dual port pci-e x4 Intel discrete NICs connected to a smart switch w/ support for Link Aggregation (10Gigiabit/s NICs/switches are still too expensive). HP smart switches use to be the best value & stability... Also Benchmark your motherboard SATA controllers.... I've noticed only more expensive server motherboardswhich has more than one discrete SATA 3.0 controllers can simultaneously write to several HDDs w/o slowing down. Anyhow, to avoid bottlenecks, you REALLY need to build / rebuild a better computer server for your particular high I/O requirements... disk striping for storage and link aggregation for connectivity is the lowest cost way of getting around your problem.... Even if you change your bittorrent client, you'll still must deal w/ the bottlenecks in your computer system.