New dispatcher with May patch...

[Didi]

It looks like the dispatcher for the early May (sorry, don't remember the exact date) patch which broke ShowEQ 5 (sniff, sniff) looks like:

448eb7: 83 c0 f5 add eax,0xfffffff5
448eba: 33 db xor ebx,ebx
448ebc: 3d 31 03 00 00 cmp eax,0x331
448ec1: 57 push edi
448ec2: 0f 87 bb 28 00 00 ja 0x44b783
448ec8: 0f b6 80 0b d1 44 00 movzx eax,BYTE PTR [eax+4509963]
448ecf: ff 24 85 3f ce 44 00 jmp DWORD PTR [eax+4509247]

I'm hoping someone else might find this useful to get the decode stuff fixed faster than I can.

Been a long time since I've been in assembly language.
Is this right, or am I off in the weeds? Hope this helps get skittles back up and running...

[Cryonic]

Wrong forums....

WE DON'T USE A MEMORY SNIFFER......

[Didi]

I wasn't implying the current versions of SEQ used memory sniffing to determine the decryption key. My apologies if I implied that.

I was doing some research on some older threads (for example, here (http://seq.sourceforge.net/forums/showthread.php?s=&threadid=3917&highlight=find+opcodes)).

It seemed that finding the dispatcher, what value it used to manipulate the opcode, and what limit value it used, were useful in trying to determine the new opcode values. At least, that's what I got from some of the threads I researched.

Again, apologies if I'm off in the weeds.

[uRit1u2CBBA=]

In case you are wondering, and you prolly aren't or else you wouldn't have posted such idiocies here, the version that was up-to-date back in February still works just fine with 2 small updates to packet sizes.

[Didi]

A thousand pardons. Getting an all-new set from the CVS cleared up my problem.

I was thinking the decoder was broken, as it was working fine until the early May patch, and hadn't seen any patches since. Coincidence does not imply causality.

Sorry for having gone down a stupid path, and brought a person or two with me. On the plus side, a they got a chance to vent some vitriol, so I'm happy to have provided some small service.