crc sum of original pak0.pk3 is 43665d07 not C6554324.
Possibly, but i use a filefingerprint and this just checks if the files are right, the fastest way
but it doesnt change fact it shows the file is not valid.
You'r right, i did some checking and found that MY pak0.pk3 is slighty diffrent. I just can't copy the stupid thing from my cd atm to fix it, as my drive is broken (long live NEC *duuh*) so it will have to wait
Actualy, got the original pak0.pk3 now, turned out the checksum verification is good enough, it is compared to another (not true crc32) checksum based on the original pak0.pk3. So if it brings a error your file is definatly faulty no matter how you look at it
: I hope you had a good reason to be absent. Get well soon, my friend.
: Impressive
: I am half Russian and half black. I'm black on the bottom half. Don't forget to lubricate your ass
: ok, bring it on analbolic hohol
: Come tomorrow to watch my battle with ShadyХУЙ at SexyFraggers 8 on central european, 22:00 Moscow time. He said he would win because he was a deft monkey. ХУЙ don't forget to put on makeup, I'll record us on video. You must be beautiful.
: broheim it is oke!!! I saw Moldova elections on the news, and referendum before that. HOPE life will get better (but nothing ever changes)
Actualy, got the original pak0.pk3 now, turned out the checksum verification is good enough, it is compared to another (not true crc32) checksum based on the original pak0.pk3. So if it brings a error your file is definatly faulty no matter how you look at it
Something....