My god, I was getting up to 52 MB/s download speeds - beats the usual 100-200k if I'm lucky!!
(2010-09-02 19:00)Gerrard DuNord Wrote: [ -> ]My god, I was getting up to 52 MB/s download speeds - beats the usual 100-200k if I'm lucky!!
ahem, that was the checksum thingy, not download speed
There is no way any regular person in the world dowloads things at 52mb/s, unless he's sitting on an industrial connection and has a really, really cool networking setup and hard drive.
(2010-09-02 19:34)Crazy Vania Wrote: [ -> ] (2010-09-02 19:00)Gerrard DuNord Wrote: [ -> ]My god, I was getting up to 52 MB/s download speeds - beats the usual 100-200k if I'm lucky!!
ahem, that was the checksum thingy, not download speed There is no way any regular person in the world dowloads things at 52mb/s, unless he's sitting on an industrial connection and has a really, really cool networking setup and hard drive.
Heh, thought it was far too good to be true
Still, in my non-technogeek defence, it did say 'downloading client' at the time, and only later on it said 'checksumming' (whatever the hell that is!
(Sidetracking: "Checksum" is a number you can somehow calculate from data. Think of it as "just add all the bytes together" (there are various ways to make a "checksum", it's more complicated than that, and there's a lot of math involved for those who care; terms to look for are MD5 and SHA1). This "sum" is then used to "check" whether a file is correct - if you know the correct checksum and have it in the client files, you can verify using that that the client is correctly downloaded.
This can be also used to "fix" clients with less data transfer involved. You can make checksums of every file, or blocks of every file, and just compare those with the checksums on a server; you then only need to download those files or parts of files where the checksum doesn't match.)
(2010-09-02 20:09)Arkady Sadik Wrote: [ -> ]This can be also used to "fix" clients with less data transfer involved. You can make checksums of every file, or blocks of every file, and just compare those with the checksums on a server; you then only need to download those files or parts of files where the checksum doesn't match.)
I think the repair.exe provided nowadays to fix gone-bad patching process does that(?).
(yeah, it does:
FAIL: res/audio/Jukebox/Ambient018.mp3, local md5: 4f93a294f20d48bba7d8d7a8a529ad6d, target md5: bcfec7a756874aa3f496b61098823fd2
...
Initializing download, please wait...
Creating BITS job with file:
http://ccp.vo.llnwd.net/o2/client_repair...018.mp3.7z
Downloading file replacements...
Download complete
Repairing files...
res/audio/Jukebox/Ambient018.mp3 successfully repaired
Log file: D:\EVE\repairlog.txt
)
Another feature not that much marketed by CCP, but should work.