0x51, Invalid Version

[Ryan Marcus]

I think this one might be a intelligent question...

No matter what I do, I continue to get an invalid version error from 0x51. I am almost completely sure its not formatting.


The 0x51 packet, sent to BNCS:

Send data (106 bytes).
<0000003B< FF 51 6A 00  00 00 00 48  09 03 01 01  A5 EA 8F E1  .Qj....H........
<0000004B< 01 00 00 00  00 00 00 00  82 26 31 0D  00 00 01 00  .........&1.....
<0000005B< 00 75 38 90  00 00 00 00  8A E1 2B 1C  03 77 89 B2  .u8.......+..w..
<0000006B< A5 AE B3 A7  CD 77 1E C3  FD B5 8B 15  73 74 61 72  .....w......star
<0000007B< 63 72 61 66  74 2E 65 78  65 20 30 38  2F 30 37 2F  craft.exe 08/07/
<0000008B< 30 35 20 31  32 3A 30 36  3A 34 32 20  31 30 39 33  05 12:06:42 1093
<0000009B< 36 33 32 00  4C 75 78 65  72 00                     632.Luxer.

The JBLS response for VersionCheck:

Receive data (55 bytes).
>000000AE> 37 00 09 01  00 00 00 09  03 01 01 A5  EA 8F E1 73  7..............s
>000000BE> 74 61 72 63  72 61 66 74  2E 65 78 65  20 30 38 2F  tarcraft.exe 08/
>000000CE> 30 37 2F 30  35 20 31 32  3A 30 36 3A  34 32 20 31  07/05 12:06:42 1
>000000DE> 30 39 33 36  33 32 00                               093632.

BnetDocs page for 0x51:

(DWORD)          Client Token
(DWORD)          EXE Version
(DWORD)          EXE Hash
(DWORD)          Number of keys in this packet
(BOOLEAN)        Using Spawn (32-bit)

For Each Key:
(DWORD)          Key Length
(DWORD)          CD key's product value
(DWORD)          CD key's public value
(DWORD)          Unknown (0)
(DWORD[5])       Hashed Key Data

(STRING)         Exe Information
(STRING)         CD Key owner name 

BnetDocs page for the BNLS response to VersionCheck:

(BOOLEAN)        Success 

If Success is TRUE:

(DWORD)          Version.
(DWORD)          Checksum.
(STRING)         Version check stat string.

Thanks in advance for any help!

P.S. I tried posting on vL and not bugging you guys, but Arta deleted my post because I included the BnetDocs page... Thanks for being cool, x86! :D