Free Plugin : Memory Plugin

[Imagine Programming]

It does decode it. I just tried it on a different dll. Something must be wrong with sside's dll like you said.

Yes, my point was, I posted a while back that I was going to work on a plugin
allowing users to Open, call and close a library and also from a base64 encoded
string... Seems someone has been 'idea scavaging' lol

I'm not saying anything anymore.

Anyhow, there might be an error in calling the DLL inside the AMSWMemory plugin,
or SSide tried to prevent dll's from being included (which is possible, Un4Seen has
also embeded protection in their BASSMOD etc dll's.) but it could be anything really.

[Centauri Soldier]

It does decode it. I just tried it on a different dll. Something must be wrong with sside's dll like you said.

[Imagine Programming]

Base64 isn't an encryption method. It's an encoding method.

You just have to decode the Base64, or just don't encode it at all.

I'm not sure if I understand, does it or does it not load Base64 encoded strings?
Cuz that would be messed up lol

[Sakuya]

Well, it could be that I'm loading it from encrypted Base64. Is there an unencypted version of Base64? Does anyone have ideas how I'd fix this?

Oh, here's something anomalous. Not sure where the error lies, in the dll or the Memory plugin but I thought I'd bring it up.

A certain DLL call requires a standard call using a return type of string. If I use the Memory plugin to make that call (as opposed to DLL.CallFunction()) then I have to change the return type to long or the program crashes...very odd.

Base64 isn't an encryption method. It's an encoding method.

You just have to decode the Base64, or just don't encode it at all.

[Centauri Soldier]

Well, it could be that I'm loading it from encrypted Base64. Is there an unencypted version of Base64? Does anyone have ideas how I'd fix this?

Oh, here's something anomalous. Not sure where the error lies, in the dll or the Memory plugin but I thought I'd bring it up.

A certain DLL call requires a standard call using a return type of string. If I use the Memory plugin to make that call (as opposed to DLL.CallFunction()) then I have to change the return type to long or the program crashes...very odd.

[Sakuya]

Anyhow, am I wrong here or does Memory now load Base64 encrypted dll aswell?

I was going to ask this too..

[Imagine Programming]

I believe that error is coming from SSides dll, right?

Anyhow, am I wrong here or does Memory now load Base64 encrypted dll aswell?

[Centauri Soldier]

After doing this...

Crypto.Base64EncodeToFile("J:\\AutoPlay 7.0\\TextToSpeech.v.1.0.0.1\\CD_Root\\AutoPlay\\Docs\\TextToSpeech.dll", "AutoPlay\\Docs\\Base64DLL.txt", 100);

and then trying to load it like this...

My_Base64_Dll = TextFile.ReadToString("AutoPlay\\Docs\\Base64DLL.txt");
result = Memory.OpenLibrary(0, My_Base64_Dll);

I get this error.

And yes, I'm wrapping sside's TextToSpeech.dll into a plugin.

[RizlaUK]

This would be a fantastic plugin creation resource.

no, no, no

This IS a fantastic plugin creation resource.

[Centauri Soldier]

Any chance you're gonna release the source code for this plugin, AMSWaves?
This would be a fantastic plugin creation resource.

[tavria2]

Mouse right click on Input1 and Listbox1 - BEEP

WM_RBUTTONDOWN = 516;

function CallBack(hWnd, uMsg, wParam, lParam)
    if uMsg == WM_RBUTTONDOWN then
        DLL.CallFunction("kernel32.dll", "Beep", "800,100", DLL_RETURN_TYPE_LONG, DLL_CALL_STDCALL)
    end
end

hWnd1 = Input.GetProperties("Input1").WindowHandle;
hWnd2 = ListBox.GetProperties("ListBox1").WindowHandle;
Memory.CreateWindowSubClass(hWnd1, 1, "CallBack");
Memory.CreateWindowSubClass(hWnd2, 2, "CallBack");

On Close

Memory.FreeWindowSubClass(1);
Memory.FreeWindowSubClass(2); [COLOR="Red"]-- this line causes an error[/COLOR]

[RizlaUK]

without seeing more code its hard to say its why crashing, try changing the callback function names and have separate callbacks for each object

sub-classing can be very temperamental

[tavria2]

Please Help.

App Crash.

I create Subclass for a few objects:

Memory.CreateWindowSubClass(hWnd1, 1, "test");
Memory.CreateWindowSubClass(hWnd2, 2, "test");

When try to free memory, there is an error: "Memory can't be read".

Memory.FreeWindowSubClass(1);
Memory.FreeWindowSubClass(2);

If to free memory of only one Subclass, an error is not present.

p.s. OS: WinXP

[jassing]

I think we were talking apples & oranges.

The result, tho, is the crash only happens on win7. Hopefully someone with source code ability can help...

[RizlaUK]

I ran that code, and no notice popped up for me...

exactly, because "not" is detecting the value from "type" and reporting true

ok, i just added some non ansci chars to the mix, and same results, no crashes (win7 Home Premium)

you got a funny little bug there, doesent seem to want to show itsself to me