Sleepkevert
Amarr Rionnag Alba Against ALL Authorities
|
Posted - 2009.04.23 12:55:00 -
[1]
Edited by: Sleepkevert on 23/04/2009 12:55:11
Originally by: Southern Suzy I'll take a wild guess on this one,
Option 1: You got a virus/malware/spyware that is attaching itself to the patch file while it downloads. This corrupts the patch coz the sha/md5 sums will not match.
Option 2: You got hardware that is failing without being critical. (memory/hard drive/network card/cable)
Option 3: Your ISP has some weird scanners/filters in use that send along security check data which gets mixed in.
Lol, all perfectly reasonable explanations, but somehow I still think the OP will believe that the patcher is faulty because of falcon, because it obviously can't be his pc's fault.
To op: I know it can be fustrating, but the patch is FINE. the 15 page thread you linked to has been accumalating posts for well over 1,5 month now, and issues have come and gone with the patcher.
If you are getting CRC errors, ONE of the options could be corruption on ccp's end. But then no-one would be able to patch. Since thats going fine, check out the guy I quoted. He has three perfectly valid explanations for your problems. _
Add your own line! |
Sleepkevert
Amarr Rionnag Alba Against ALL Authorities
|
Posted - 2009.04.24 10:04:00 -
[2]
I just tried it on my dedicated box and it passed the 276mb mark like a charm...
admin@*:~/tmp$ wget http://ccp.vo.llnwd.net/o2/EVE_Premium_Setup_86756_m.exe --11:58:26-- http://ccp.vo.llnwd.net/o2/EVE_Premium_Setup_86756_m.exe => `EVE_Premium_Setup_86756_m.exe' Resolving ccp.vo.llnwd.net... 87.248.201.36, 87.248.201.23 Connecting to ccp.vo.llnwd.net|87.248.201.36|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2,253,907,588 (2.1G) [application/octet-stream]
33% [===========> ] 750,925,901 6.29M/s ETA 04:15 Trace is pretty crap though
root@*:/home/admin/tmp# tracert ccp.vo.llnwd.net traceroute to ccp.vo.llnwd.net (87.248.201.23), 30 hops max, 40 byte packets 1 94.23.37.254 (94.23.37.254) 1.300 ms * * 2 * * * 3 fr3.ams.llnw.net (195.69.145.133) 5.793 ms * * 4 * * * 5 * * * 6 * cds113.ams.llnw.net (87.248.201.23) 5.708 ms 5.772 ms Looks like an ISP or an routing issue on llnwd's end. _
Add your own line! |