Another Ridiculous Torrent issue

So I've downloaded two separate Guilty Gear XX Slash torrents, one from somewhere the other from slops2. In both cases the file came in multiple archived files, but when the torrent hits 100% the files still look like this...



I can't imagine it is the torrent itself, Slops2 as far as I know Slops2 has a pretty good reputation for decent files, so I dont know I dont know, I'm pretty useless so please help :S

Jam it back in, in the dark.

That means that the file you downloaded was broken up into several smaller parts using winrar. You will most likely find these individual files have a extention like: ".rar, .r01, .r02, .r03" etc, without any repeats.
All you have to do is unpack one of these with Winrar, and the rest will be taken care of. (I hope)

There's nowhere I can't reach.

I've been in this situation before, usually ALL the files are recognized by winrar and unzipping them does exactly what it should...

but my problem is that not all the files are recognized and look as though they're still half-downloaded even though the torrent itself says 100% and all the files are the appropriate size, and thus when unzipping I get a corrupt message.

If you look at the picture you can see some of the files dont look right.

Most amazing jew boots

Can you force a re-check or verification on the torrent? What program do you use?
Are all of the files the same size as well?(well, all but one)

I am a dolphin, do you want me on your body?

All the files are the size they're supposed to be and I'm using BitComet mostly, although I also have uTorrent.

I was speaking idiomatically.

The size of the files don't matter if you've set BitComet to pre-allocate the filesize.

Go to BitComet, right click on the torrent and force a hash check (or whatever the equivalent is). If it's corrupted, the completion percentage will fall and you'll have to resume downloading.

(Also, go into your folder view settings and set it NOT to hide well-known file extensions. I'm betting there is a .bc! file extension on those files.)

How ya doing, buddy?

Do what BigBlah said first, and force a verification/check for that torrent.
(took me 10 minutes to write this thing?)

Otherwise, some malicious (or purposefully retarted) person is uploading invalid file data. If this is the case, then your only option, as someone who I figure is not too much of a 1337 h4xx0r(no offense), is to delete only the corrupt files, restart the torrent(remove from the BT queue, and reload, with the same directory), and hope for the best.

If those files are from someone who is seeding invalid data, then you might just get lucky and download from someone else who has a complete share.

If some of the files that you downloaded again work afterwards, then you might get lucky again with another iteration of the actions I described to you earlier.

If you find that all of the same files are bad again, then you might as well just scrap this torrent, and go for another one.

You might also want to report the torrent for that failure, although I'm not sure if Slops2 does that.

FELIPE NO

While it is possible to break the SHA-1 hash algorithm that BitTorrent uses, it is not all that easy to compromise downloads through the BitTorrent protocol, especially for large files such as ISOs in my opinion (not that it is exactly easy to break the SHA-1 algorithm to my knowledge, but I could be wrong).

In order for hash checking to have failed for Rasputin, a complete piece must have been downloaded from a malicious peer. So you have to ask yourself were you downloading large magnitudes of this torrent from one single peer?

Since every piece is split up into some chunks, it is quite likely that you'll get some chunks from a regular peer and some other chunks from the malicious peer. As hashing algorithms takes all the bytes of a piece and runs the algorithm on it to produce the 40-digit hexadecimal number, I'm curious as to whether it is actually currently feasible to have malicious chunks combined with good chunks and produce a valid hash as while it's possible to have a malicious block of data produce the correct SHA-1 hash, this mish mash of the two may not be possible (again, I could be wrong).

Azureus performs hash checks after a full piece has been downloaded and I believe it also double-checks each piece again when the torrent has completed. I'm not sure if BitComet does the same, but I would certainly think so (at least, certainly the former, or else you'd be wasting a lot of time if you get to 100% and realize half your files are bad).

Nonetheless, you should motion for forcing a rehash check and opening all file extensions and the viewing of hidden files as aforementioned.

What, you don't want my bikini-clad body?