0x51 Wrong product

[PaiD]

What causes this error in 0x51.
0x203: Wrong product

It has done this sometimes using a valid w3 key with client as WAR3, any ideas?

[UserLoser.]

Supply a valid product

[Topaz]

Did you reverse the product string?

[UserLoser.]

Did you reverse the product string?

There are no such strings that are to be reversed

[Topaz]

DWORD.

[dxoigmn]

DWORD.

Definitions of  DWORD on the Web:

    * Double word, ie 4 bytes on x86.
      www.kernelhacking.org/docs/kernelhacking-HOWTO/indexs17.html

    * Double word. A data element that is 2 words, 4 bytes, or 32 bits in size.
      www.ti.com/sc/docs/products/msp/intrface/usb/terms.htm

    * A portion of memory, usually a variable, which has a length of four bytes. The term dword is given to anything which is four bytes in length. Literally, a dword is a "double word." Back
      www.pietschsoft.com/programming/vbapi/ref/glossary.html

I don't see string nor reverse.

[Eric]

If your key is indeed valid then you're either sending SID_AUTH_CHECK incorrectly or your CD-Key decoding algorithims are flawed.  Yes, it's a vague answer, but it was also a vague question.

[Topaz]

Recall how you have to send WAR3 as 3RAW to battle.net? Same thing with STAR -> RATS.

[Warrior]

That's only if you decide to use the trick to get around sending a DWORD by sending a non null terminated string reversed (which ends up a DWORD)

[Eric]

That's only if you decide to use the trick to get around sending a DWORD by sending a non null terminated string reversed (which ends up a DWORD)

People who consider a "non-null terminated string" to be a valid datatype shouldn't expect to make a working bot.

[Lenny]

Let's not go through this topic over and over again ad nauseam.

Topaz, read Sizes & Types in BnetDocs and do some searches in the forum.