Shoutbox

There is a 00023e60 with EB 36, a 00023fc0, a 00036db0, 00036f00

no 000023FCA though, which of those should i edit? Also what does this edit do?

quote:

---

Originally posted by Rapid_W
There is a 00023e60 with EB 36, a 00023fc0, a 00036db0, 00036f00

no 000023FCA though, which of those should i edit? Also what does this edit do?

---

00023FCA is in the row marked 00023FC0 it should start on the tenth byte on that row (hence why it's got A. 0xA=10)

This modifies a function that sends data over a UDP based socket. In my case, for some reason the call to send on the socket was failing with a fatal error message, but messenger treated it like an error that would automatically fix itself by trying to send again.

This hex edit changes the code so that it will break out of the loop when it receives a fatal error. 

If you want to get technical: (if not feel free to skip this part)
0xEB is the machine code that means jump to a close address via offset.  This edit just changes the jump destination forward a few bytes.

ahh ok thanks, while i can convert hex to base10 (or any other for e-penis points), i have no idea about its coding properties

TheSteve, the man from Japan, thanks for your Hex code, it fixed a severe issue with my Messenger. <3

quote:

---

Originally posted by James Potter
thanks for your Hex code

---

You're welcome.

quote:

---

Originally posted by James Potter
it fixed a severe issue with my Messenger. <3

---

Yeah, it really is a severe issue, (for those who need to use UDP networking). I have reported the error to Microsoft, and I'm hoping they will fix it for the next release.

Hasn't worled for me. I still get freezes and hogging of one core. Sometimes wlm will be fine and work perfectly, othertimes it won't work at all. ahh well.

It appears that your problem is else where then.  What you can do is install the "Debugging tools for windows" then follow the instructions in this page to setup Process Explorer to give better stack traces.
When messenger freezes, use Process Explorer to view the call stack of the frozen thread.  This should give a little more insight as to what the problem might be.