Hi folks,

I'm trying to move a string from pointer A to B. The debugger states that an exception has occurred while executing RtlMoveMemory, without any specific information. Interop.GetLastError() returns 2, which means a specified file is not found. I don't see what files have to do with moving memory data.

Can anyone help me on this one?

Care to paste full code? (including the GetLastError part)

js code:

---

var ptrA = Interop.Allocate(4);
var s = 'this is some text';
var ptrA_string = Interop.Allocate(2*s.length+2)
    ptrA_string.WriteString(0, s);
    ptrA.WriteDWORD(0, ptrA_string.DataPtr);
var ptrB = Interop.Allocate(4);

Interop.Call('kernel32', 'RtlMoveMemory', ptrB, ptrA, 4);

Debug.Trace(ptrB.ReadString(0));

---

JScript code:

---

var PagePtr = lParam;
if(PagePtr === 0) {
    Internet(Script.WebURL);
    return API_SUCCESS;
}
var Size = lParam;
var oPage = Interop.Allocate(Size);
Interop.Call("Kernel32.dll","RtlMoveMemory",oPage.DataPtr,PagePtr,Size);
TraceWin32Error();

---

Well, you're taking lParam for PagePtr's use and Size's use, I guess one should be wParam.

And matty, a 4-byte DataBloc can not hold "this is some text", which is a couple dozen bytes.

well, that's another stupid one

Thanks anyway

quote:

---

Originally posted by Mnjul
And matty, a 4-byte DataBloc can not hold "this is some text", which is a couple dozen bytes.

---

quote:

---

Originally posted by matty
This post was edited Today at 02:30 PM by matty.

---

Is there a reason that you're using RtlMoveMemory rather than RtlCopyMemory? 

If the two buffers don't overlap (which they don't)  you should not be using RtlMoveMemory.

quote:

---

Originally posted by TheSteve
Is there a reason that you're using RtlMoveMemory rather than RtlCopyMemory? 

If the two buffers don't overlap (which they don't)  you should not be using RtlMoveMemory.

---

There is.

I use this system for communication between two different scripts. RtlCopyMemory would mean lots of extra memory management to prevent leaks. Let me put it this way:

Script A sends a pointer to script B. Script B is now responsible for handling that pointer, to relieve script A (the contents of the pointer will most likely be stored in a variable). Script B then destroys the pointer (allocated by the Interop object) when it's no longer needed.

Using RtlCopyMemory would mean extra work for script A.

RtlMoveMemory does not free the pointer.  You still have to manage memory yourself.

The only difference between RtlMoveMemory and RtlCopyMemory is that RtlMoveMemory is designed to work on two buffers that overlap each other. Other than that, they are the same.

If you are using DataBloc, the memory is automatically free'd when the JScript garbage collector is run. So as long as you have a reference to the object in a variable, the data will not be free'd. If you are using the Win32 API SendMessage function, the function will not return until the message has been received and handled.  All of this time, you still have a reference to the DataBloc, so the memory is still valid.