New "patch" d/l today, then checksum error??

Dusty wrote:
> As I was once again suffering from insomnia and playing waay too many hours
> of CoX, I stopped after the last map server error and went to do some thing
> foolish, like read my e-mail. About an hour or so later, I fired up CoX and
> was told it needed to get a new patch all 1.5GB of it.. "OK, fine, this
> shouldn't take too long.." (yes, this is -after- the I7 patch). So, then I
> log in and select my server... this is what I got:
Nah it's not that you need a new patch of 1.5GB, the patch may be as
small as 1k but then it has to apply it to the whole 1.5GB of game in
your hard drive. The actual download is just that 1k. Only when we
have big releases like I7 is when you get patches of 100 or 200 or even
300MB, but they normally spread it over several weeks so you don't
really notice it.
 >> Stay informed about: New "patch" d/l today, then checksum error?? 

"Marcel Beaudoin" <marcel.beaudoin RemoveThis @gmail.com> wrote in message
news:Xns97E1741797B2Fmbeausympaticoca@130.133.1.4...
> "Dusty" <No.One RemoveThis @home.org> wrote in
> news:ONudnW15ae7ZUhPZnZ2dnUVZ_q6dnZ2d@adelphia.com:
>
>> WTF, over?? What new screw up is hitting us this time..? Or is it just
>> me......
>
> Noe, not just you. This seems to be hittinig CoX hard. Best guesses from
> the official Forums is that there is a disconnect between updating the
> patcher and updating the patches. They were supposed to be locking the
> base
> storage real soon (due to a potentially game-crashing bug they found).

Guess what - we found it!
 >> Stay informed about: New "patch" d/l today, then checksum error?? 

I just checked again, for the heck of it, seems everything is back to normal
again..
 >> Stay informed about: New "patch" d/l today, then checksum error?? 

"Marcel Beaudoin" <marcel.beaudoin DeleteThis @gmail.com> wrote in message
news:Xns97E1741797B2Fmbeausympaticoca@130.133.1.4...
> "Dusty" <No.One DeleteThis @home.org> wrote in
> news:ONudnW15ae7ZUhPZnZ2dnUVZ_q6dnZ2d@adelphia.com:
>
>> WTF, over?? What new screw up is hitting us this time..? Or is it just
>> me......
>
> Noe, not just you. This seems to be hittinig CoX hard. Best guesses from
> the official Forums is that there is a disconnect between updating the
> patcher and updating the patches. They were supposed to be locking the
> base
> storage real soon (due to a potentially game-crashing bug they found).

I'll be happy when they fix whatever memory leak they have going. I can end
a couple of hours of CoX with the game taking up 1.5 gig or so and my game
becoming i/o bound just trying to move across a zone as CoX tires to swap in
zone stuff while trying to hold onto a bunch of other stuff it thinks it
needs and doesn't. It takes my machine about a minute of uninterrupted time
to clear the swap file out, something that didn't happen pre-I7. I'm
starting to think they want me to buy another gig of memory.


--
John Trauger,
Vorlonagent


"Methane martini.
Shaken, not stirred."


Vorlonagent (M), level 38 Blaster (Electric/Energy), Guardian
RolIing Thunder (F), Level 36 Defender (Storm/Electric), Infinity
Lemon Tree (F), Level 32 Scrapper (Spine/Invuln), Liberty
Pulsar Staraven (F), Level 27 Controller (Grav/Rad), Liberty
Fury- (F), Level 27 Brute (Energy/Energy), Liberty
Dr. Akagi (F), Level 25 Mastermind (Robots/Traps), Guardian
 >> Stay informed about: New "patch" d/l today, then checksum error?? 

Dusty wrote:
> As I was once again suffering from insomnia and playing waay too many hours
> of CoX, I stopped after the last map server error and went to do some thing
> foolish, like read my e-mail. About an hour or so later, I fired up CoX and
> was told it needed to get a new patch all 1.5GB of it.. "OK, fine, this
> shouldn't take too long.." (yes, this is -after- the I7 patch). So, then I
> log in and select my server... this is what I got:
>
> ---------------------------------
> Wrong Game Version, run patcher and reconnect, server 12.20060526.1
> Bad Client Checksum. Revivifying files.
> ---------------------------------
>
> So, I tell CoX to verify the files, the screen goes blank and the CoX
> initialization box disappears from view and does NOT check anything.
>
> I reboot. Login to CoX.. same thing.
>
> I start to run systems checks and diags like a mad man.. nothing wrong. So
> I try again.. nada, zip. CoX dies on connection to X server after login.
>
> WTF, over?? What new screw up is hitting us this time..? Or is it just
> me......

Oddly enough, I just logged in and didn't see any new patch.
--
[The address listed is a spam trap. To reply, take off every zig.]
Richard Clayton
"During wars laws are silent." -- Cicero
 >> Stay informed about: New "patch" d/l today, then checksum error?? 

On 2006-06-13, Marcel Beaudoin <marcel.beaudoin DeleteThis @gmail.com> wrote:
> "Dusty" <No.One DeleteThis @home.org> wrote in
>> WTF, over?? What new screw up is hitting us this time..? Or is it just
>> me......
>
> Noe, not just you. This seems to be hittinig CoX hard. Best guesses from
> the official Forums is that there is a disconnect between updating the
> patcher and updating the patches. They were supposed to be locking the base
> storage real soon (due to a potentially game-crashing bug they found).

I believe the phrase is "game-breaking". There's been a few fairly
obvious exploits with the way the base storage and base crashing issues
interact, and it seems likely that someone finally found a way to
replicate them reliably.

Apparently they do log base storage enough to know what really goes in
and comes out. While going into those logs to restore lost objects for
people who were bitten by the bug, they may have discovered evidence
that people were... dupin' rares.

--
--- An' thou dost not get caught, do as thou wilt shall be the law ---
"Religion disperses like a fog, kingdoms perish, but the works of
scholars remain for an eternity." - Ulughbek
 >> Stay informed about: New "patch" d/l today, then checksum error?? 

In article <slrne8u2jk.rrj.sw.DeleteThis@haven.eyrie.org>, sw.DeleteThis@eyrie.org says...

> While going into those logs to restore lost objects for
> people who were bitten by the bug, they may have discovered evidence
> that people were... dupin' rares.

Gasp! You mean...JERK HACKERS?

--
"I'm sorry, did I offend you just now? Pardon me--I'm
sorry, I didn't mean to offend you. Really, I'm sorry,
I didn't mean to offend you. Should I like, change my
attitude? Should I change my whole way of being? Huh?
I'm sorry, I'm sorry, I'm sorry, I'm sorry. BITE ME HARD!"
--Jim's Big Ego
 >> Stay informed about: New "patch" d/l today, then checksum error??