|
Forum > Miscellaneous
[QUESTION] Blizzard Downloader
<< < (4/5) > >>
stoneharry:
--- Quote from: "happyhack" ---
--- Quote from: "stoneharry" ---The filesplitter would only be used for sending using the torrent protocol, correct?
--- End quote ---
correct, almost :D actually peers send pieces to each others trough TCP, not HTTP (if i remember well). But you are right, the downloader get same pieces from the http server than it would get from a peer.
--- Quote from: "stoneharry" ---The direct download URL is sent in the tracker response, however my downloader does not appear to be using it
--- End quote ---
hmmm... does the downloader gives u any error or warning message?
are you sure the pieces are available to the downloader? can u download them through a browser?
Does the View > Connection info menu show u the correct url in the "Direct HTTP download" row?
--- End quote ---
Okay, I'm a bit confused as to what I should point to.
At the moment I just have the download URL set to the binary file on a web server.
The parts (0 to 29) and the hash.txt is uploaded in the same directory as the binary file.
happyhack:
Wow.exe should be a folder, not a file.
Delete Wow.exe, create a directory with that name, then place all the part files inside. it should work now.
u can remove hash.txt too, it is unused.
stoneharry:
--- Quote from: "happyhack" ---Wow.exe should be a folder, not a file.
Delete Wow.exe, create a directory with that name, then place all the part files inside. it should work now.
u can remove hash.txt too, it is unused.
--- End quote ---
That makes more sense. :) It now starts to download but then it stops and a bad.piece is created at the download location.
The torrent piece size is set to 256 kb. That's 262144 bytes. So I am splitting the file using filesplitter @ 262144 bytes.
When the download stops the Wow.exe.part has reached 768 KB. The bad.part is 255 KB (261,396 bytes).
Since it seems to fail almost immediately and due to the size of the bad.part I think this is because one of the bits that the filesplitter has created is an incorrect size. So I recreated the parts and uploaded the new ones to the same result. Am I splitting it by the wrong value? Should it be 256KB - 1?
happyhack:
--- Quote from: "stoneharry" ---Since it seems to fail almost immediately and due to the size of the bad.part I think this is because one of the bits that the filesplitter has created is an incorrect size. So I recreated the parts and uploaded the new ones to the same result. Am I splitting it by the wrong value? Should it be 256KB - 1?
--- End quote ---
no. filesplitter is correct, it writes in the console how many bytes are written to each file, u can check it by hand too.
The part size doesnt matter, i tried with 256, 512, 1024, it worked just well.
In the torrent file there is a field "pieces" which contain concatened sha1 hash of all pieces. If µtorrent didnt set this correctly the download will fail because of piece integrity check.
(this is what the hash.txt file is used for)
If u change the pieces size without updating the torrent, the download will fail because of piece integrity check.
If u resume the download without delete "yourfiledownloaded.exe.part" after changing pieces size, the download will fail because of piece integrity check.
stoneharry:
--- Quote from: "happyhack" ---
--- Quote from: "stoneharry" ---Since it seems to fail almost immediately and due to the size of the bad.part I think this is because one of the bits that the filesplitter has created is an incorrect size. So I recreated the parts and uploaded the new ones to the same result. Am I splitting it by the wrong value? Should it be 256KB - 1?
--- End quote ---
no. filesplitter is correct, it writes in the console how many bytes are written to each file, u can check it by hand too.
The part size doesnt matter, i tried with 256, 512, 1024, it worked just well.
In the torrent file there is a field "pieces" which contain concatened sha1 hash of all pieces. If µtorrent didnt set this correctly the download will fail because of piece integrity check.
(this is what the hash.txt file is used for)
If u change the pieces size without updating the torrent, the download will fail because of piece integrity check.
If u resume the download without delete "yourfiledownloaded.exe.part" after changing pieces size, the download will fail because of piece integrity check.
--- End quote ---
I see. You are correct, it seems uTorrent does not populate the hash. I google'd a bit on how to fill this field and came up with info_hash being the required field. The hash.txt is 1200 in length. So I added it like so:
--- Code: ---d8:announce31:http://127.0.0.1:54177/announce9:info_hash1200:[...]10:created by13:uTorrent/331013:creation datei1380975771e8:encoding5:UTF-84:infod6:lengthi7704216e4:name7:Wow.exe12:piece lengthi262144e6:pieces600
--- End code ---
Where [...] = the contents of hash.txt.
However it is still failing to get any piece correctly. Is this the correct field? Do you recommend another program for generating torrent files?
Thanks for helping me with what are probably silly mistakes. :P
Navigation
[0] Message Index
[#] Next page
[*] Previous page
|