Use BitTorrent To Verify, Clean Up Files
jweatherley writes "I found a new (for me at least) use for BitTorrent. I had been trying to download beta 4 of the iPhone SDK for the last few days. First I downloaded the 1.5GB file from Apple's site. The download completed, but the disk image would not verify. I tried to install it anyway, but it fell over on the gcc4.2 package. Many things are cheap in India, but bandwidth is not one of them. I can't just download files > 1GB without worrying about reaching my monthly cap, and there are Doctor Who episodes to be watched. Fortunately we have uncapped hours in the night, so I downloaded it again. md5sum confirmed that the disk image differed from the previous one, but it still wouldn't verify, and fell over on gcc4.2 once more. Damn." That's not the end of the story, though — read on for a quick description of how BitTorrent saved the day in jweatherley's case.
jweatherley continues: "I wasn't having much success with Apple, so I headed off to the resurgent Demonoid. Sure enough they had a torrent of the SDK. I was going to set it up to download during the uncapped night hours, but then I had an idea. BitTorrent would be able to identify the bad chunks in the disk image I had downloaded from Apple, so I replaced the placeholder file that Azureus had created with a corrupt SDK disk image, and then reimported the torrent file. Sure enough it checked the file and declared it 99.7% complete. A few minutes later I had a valid disk image and installed the SDK. Verification and repair of corrupt files is a new use of BitTorrent for me; I thought I would share a useful way of repairing large, corrupt, but widely available, files."
jweatherley continues: "I wasn't having much success with Apple, so I headed off to the resurgent Demonoid. Sure enough they had a torrent of the SDK. I was going to set it up to download during the uncapped night hours, but then I had an idea. BitTorrent would be able to identify the bad chunks in the disk image I had downloaded from Apple, so I replaced the placeholder file that Azureus had created with a corrupt SDK disk image, and then reimported the torrent file. Sure enough it checked the file and declared it 99.7% complete. A few minutes later I had a valid disk image and installed the SDK. Verification and repair of corrupt files is a new use of BitTorrent for me; I thought I would share a useful way of repairing large, corrupt, but widely available, files."
I was sick of multipart files in 1991, ha!
All your points are solved by software, split rars are a hack on deficient protocols or routers that limit BW per tcp connection.
Oh and, what is it with these stupid long ass crap file names, S05E03-XDVD-HPEP-LOL-FUKME.avi
This is not 1972 cobol days dudes, if its unlikely to be a hit like friends, stick to one digit to seasons, S3, E03 is ok.
Kill the lame postfix acronyms, except sensible ones not in caps as they take more pixel, (dvd) or (ts) is smaller.
As gordan ramsey says, "you guys a fuking tossers, your a shit head".
TvShowName-S4ep23.avi is nicer, i always rename because they are TOO DAMN long on HTPC systems. Again, this aint 1200bps modem days. (they werent this bad btw)
Oh and another pet peve of mine to your so called elites, stop resizing 720 rips or tv shows to 604 or 624, if its done only to compress better, or
to play on PSP, then why should 90% suffer, 720 original is best on 42in LCDs. Stop resizing because you own a crap 12in crt. Or want to watch tv shows in a psp, cartoons are ok, but not good tv shows. Dont give me this 624 is ntsc in usa shit, only trailer trash own CRTs. If you can afford to download, you own an LCD. If you own a shit tv, well you'll get a better quality any way. Again, read my lips, 624 or 608 sucks 1980s style.
Liberty freedom are no1, not dicks in suits.