Beep Boop Bip
Posting mode: Reply
Subject   (reply to 1306)
BB Code
File URL
Embed   Help
Password  (for post and file deletion)
  • Supported file types are: BMP, CSS, EPUB, FLAC, FLV, GIF, JPG, OGG, PDF, PNG, PSD, RAR, TORRENT, TXT, WEBM, ZIP
  • Maximum file size allowed is 10000 KB.
  • Images greater than 260x260 pixels will be thumbnailed.
  • Currently 753 unique user posts.
  • board catalog

File 143147892257.gif - (592.50KB , 370x335 , 1431073832439.gif )
1306 No. 1306 [Edit]
Here we talk about torrents particulaly how uTorrent is shit.

Lately it seems like my torrent downloads have corrupted packets (if thats the right term for it). What happens is my download gets to 100%, but then when I restart the torrent program it checks for corrupt packets and restarts the download from 90% or so. I have to close and restart the program 2-3 times to fix all the corrupted packets or else I get problems like programs not installing properly or not being able to extract rars/zips/7z file properly. Anyone else get this problem?
Expand all images
>> No. 1307 [Edit]
What client are you using?
>> No. 1308 [Edit]
>> No. 1309 [Edit]
File 143148322623.png - (583.02KB , 3100x2885 , 1417555542754.png )

are you using a wifi connection? If so, that may be the problem. wifi packet loss and whatnot.

Otherwise, if you want to talk about Shitty torrent software, there's Vuze.

It was fairly nice, though a tad bloated, then they threw out the backdoor "security force update" that updated to the new version without giving the user a choice in the matter.

Oh, the "new version" has advertisements bult in.
>> No. 1310 [Edit]
Never had this problem.

Using deluge on winbox and transmission-cli/daemon on linuxbox. It requires some effort to get a "new" version of transmission on Debian stable, with launchpad, experimental and backport repo + some special commands.
>> No. 1311 [Edit]
I remember when that was still just 'azureus'. It was my primary client up until it got combined with that Vuze shit.
>> No. 1318 [Edit]
Torrent client check the data as it is downloaded, packet loss shouldn't be an issue, sounds more like a storage/filesystem problem.

I had some torrents on transmission that caused trouble like that, after deleting the .resume files named like the corrupted torrents in the clients directory and re-adding the .torrent they started working again. Other clients should have similar metadata.

Vuze has some unique features, like i2p plugin or the ability to use multiple connections, but it's also pretty bloated.
>> No. 1347 [Edit]
File 143856670137.png - (442.98KB , 520x580 , 1427058741177.png )
I just learned about Tixati and fell in love.
>> No. 1348 [Edit]
You know, one thing I miss about ĀµTorrent is that torrents would have an error state for when the target directory couldn't be found (usually because the hardware was unplugged). In the clients I've used since though, the torrents simply reset to 0% after failing to find resume data, meaning when I do re-connect the hardware, they try to re-download what's already there. Does anyone know a way around this?
>> No. 1349 [Edit]
I thought most clients would just sync the progress with the .part file and carry on from there.
>> No. 1378 [Edit]
File 145014347121.jpg - (37.54KB , 444x448 , 1408220060188.jpg )

look for a verify/recheck option in a right-click menu (or equivalent for non-windows systems). That will work for one-off type events.

View catalog

Delete post []
Report post

[Home] [Manage]

[ Rules ] [ an / foe / ma / mp3 / vg / vn ] [ cr / fig / navi ] [ mai / ot / so / tat ] [ arc / ddl / irc / lol / ns / pic ] [ home ]