Author | Message | Time |
---|---|---|
AC_Drkan | [code] [10:21:23] Failed version check! [10:21:24] Searching for latest version code... [10:21:24] The version code must be manually updated. [/code] Thats on spht Bot and on flawed i get this: [code] [10:22:07] CDkey Error! Unknown byte: &H101 [/code] Can anone tell me what bnet did last night? or maybe i did? Nvm, Fixed it. Please delete this message EDIT * 2: Just reboot the computer and mine worked fine. | February 28, 2005, 3:22 PM |
Kp | Flawed bot is apparently living up to its name. 0x101 cannot fit in a byte. That it would ever claim so is a flaw. | February 28, 2005, 3:38 PM |
Mephisto | Isn't 0x01 an error code reported from 0x51? And for that matter it's an unsigned long, not a byte as Kp mentioned. | February 28, 2005, 4:32 PM |
UserLoser. | [quote author=SoR-Mephisto link=topic=10754.msg101953#msg101953 date=1109608351] Isn't 0x01 an error code reported from 0x51? And for that matter it's an unsigned long, not a byte as Kp mentioned. [/quote] No. It could be, but because I highly doubt this bot was written in another language than VB (supports signed longs only) judging by what it outputs, I doubt it was an unsigned long. | February 28, 2005, 8:12 PM |
iago | You also can't assume that an "unsigned long" is 4 bytes. The correct term for the error code would be an "unsigned 4-byte little endian integer" :) | February 28, 2005, 8:36 PM |
Kp | [quote author=iago link=topic=10754.msg101983#msg101983 date=1109622962]You also can't assume that an "unsigned long" is 4 bytes. The correct term for the error code would be an "unsigned 4-byte little endian integer" :)[/quote] Commonly known in these parts as luint32_t. ;) uint32_t is acceptable if you don't mind endianness ambiguity. | March 1, 2005, 5:18 AM |