The idea here is that it seems very tricky to get the value of 2 to "stick" to the static address of 142782E19 and there is no rhyme or reason as to when it sticks and when it doesn't, so I have it applying twice AND came up with this compare loop to make sure the address of 142782E19 has accepted the value of 2 or it's SUPPOSED to jump back up and do it again, etc...
What's happening is:
1) Most of the time, the value of 2 never gets accepted by the 142782E19 address. There HAVE been times it has stuck but I can't figure out why.
2) When the compare checks to see if it has been changed to a 2, it acts like it was successful (even though it was not a value of 2) so it FAILS to jump back up and try to apply the 2 value again.
What's the explanation for why this is happening, and the correct way to write what I am trying to attempt here? (you can ignore the mov edx line)
That is working; it's just that something else is writing to it that overwrites the value you wrote.
Set a breakpoint on your code and watch what happens.
Also, I'm pretty sure that's writing a 4-byte value. If you only want to write one byte:
Code:
mov byte ptr[142782E19],2
_________________
I don't know where I'm going, but I'll figure it out when I get there.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum