Shoutbox

code:

---

var Handle = Interop.Call("Kernel32","GetModuleHandleW",null);
    var sBuffer = Interop.Allocate(PatchOld.length);
    Address = (Address - 0x00400000) + Handle;

---

quote:

---

Originally posted by TheGuruSupremacy
I assume that at least the byte to patch is your own work.

---

quote:

---

Originally posted by Mnjul

quote:

---

Originally posted by TheGuruSupremacy
I assume that at least the byte to patch is your own work.

---

No, I presume?

---

quote:

---

Originally posted by blessedguy
If it DOES contain copied code and stuff from other places, uncreditted and not-explicitely-allowed, shouldn't it be removed from the database?

---

quote:

---

Originally posted by TheGuruSupremacy

quote:

---

Originally posted by blessedguy
If it DOES contain copied code and stuff from other places, uncreditted and not-explicitely-allowed, shouldn't it be removed from the database?

---

Well it's not needed.He credited Cookie but he forgot to credit TB(To Credit me is not important my code to patch is anyway based on cookie's code)

---

quote:

---

Originally posted by TheGuruSupremacy
The Function patch was made by me not by Cookie.

---

code:

---

var Handle = Interop.Call("Kernel32","GetModuleHandleW",null);
    var sBuffer = Interop.Allocate(PatchOld.length);
    Address = (Address - 0x00400000) + Handle;

---

quote:

---

Originally posted by NanaFreak
this can be easily done with the registry setting made available by Patchou with MP!L.

see Messenger Plus! Live - Registry Settings and search for "OverrideImgTransfer"

a simple .reg file would be all that is required to fix the issue...

---

code:

---

MsgPlus.DisplayToast("Photo Sharing", "Windows Live Messenger " + Messenger.Version.toFixed(1) + ".0" + Messenger.VersionBuild + "\nis not supported");

---

code:

---

MsgPlus.DisplayToast("Photo Sharing", "Windows Live Messenger " + Messenger.Version.toFixed(1) + "." + ("000" + Messenger.VersionBuild).slice(-4) + "\nis not supported");

---

quote:

---

Originally posted by CookieRevised

quote:

---

Originally posted by NanaFreak
this can be easily done with the registry setting made available by Patchou with MP!L.

see Messenger Plus! Live - Registry Settings and search for "OverrideImgTransfer"

a simple .reg file would be all that is required to fix the issue...

---

No, that registry setting will not completely disable Photo Sharing....
This script does...

see OverrideImgTransfer and photo sending
in which you actually corrected the OP and said the exact same thing I do now: that the registry key does not completely disables Photo Sharing; it only disables Photo Sharing for pasted image data, not for dropped graphic files

---

quote:

---

Originally posted by CookieRevised
Sorry, but if you want to talk origins and be precise, then the patch function like it is written was actually made by me. (so are the many other code flows like the SignIn function etc, which are all almost literally copies of what I did before in my memory patching scripts). See all my patch scripts where I used the exact same code.

The patch functions in your NudgesToolScript and Idle Liar scripts for example are also a word for word 'copy' of the one I used in Auto-Emoticons, Unlimited Nudges, etc... including the variable names (but minus the comments from my scripts).

Not that I didn't wanted you to copy them though, but correct is correct

---

quote:

---

Originally posted by CookieRevised
Can't be 'be stolen' because it is almost strait forward stuff to convert a base address to the correct virtual address in case the module is loaded in a different base offset. Nothing unique at all. It is (should be) used in almost every program and script which deals with memory patching (although not always like in my scripts where I simply ignore the possebility ). It is in fact a mandatory step for such programs and thus should be common knowledge* and can not be owned or be claimed that "someone came up with it" or "invented it" and thus "stole it". It's another thing when someone (eg: TB) points out the nessecity of it of cours

---

Javascript code:

---

// Do the actual patching.
function Patch(nAddress, sByteString) {
    // Make a decent byte array out of the string.
    // This is again where Plus! comes short with its WriteString() function IMHO.
    // Also notice that older Plus! versions expect signed bytes with SetAt(), so we use WriteWORD() instead.
    var sBuffer = Interop.Allocate(++sByteString.length);
    for (var j = 0; j < sByteString.length; j++) sBuffer.WriteWORD(j, sByteString.charCodeAt(j));
    var hProc = Interop.Call("Kernel32", "GetCurrentProcess");
    Interop.Call("Kernel32", "WriteProcessMemory", hProc, nAddress, sBuffer.DataPtr, sByteString.length, 0);
}

---

quote:

---

Originally posted by CookieRevised
You got that patch function from the 'Unlimited Nudges' script I think. A few days after I wrote the 'Idle on Demand' script (already 3 years ago, wow ) I wrote the 'Unlimited Nudges' script. And in that script there is a function:

Javascript code:

---

// Do the actual patching.
function Patch(nAddress, sByteString) {
    // Make a decent byte array out of the string.
    // This is again where Plus! comes short with its WriteString() function IMHO.
    // Also notice that older Plus! versions expect signed bytes with SetAt(), so we use WriteWORD() instead.
    var sBuffer = Interop.Allocate(++sByteString.length);
    for (var j = 0; j < sByteString.length; j++) sBuffer.WriteWORD(j, sByteString.charCodeAt(j));
    var hProc = Interop.Call("Kernel32", "GetCurrentProcess");
    Interop.Call("Kernel32", "WriteProcessMemory", hProc, nAddress, sBuffer.DataPtr, sByteString.length, 0);
}

---

looking familiar?

Anyways, enough jabber talk, I'll shut up now

---