Injecting ASM problems

[lanman92]

I'm having a few issues with injecting to cast a spell. This piece of code is not even putting the asm into the WOW.exe process. I don't see why it's not, seeing that everyone else does this fine.

g_clientCon = magic.ReadUInt(0x11CB310);
s_curMgr = magic.ReadUInt(g_clientCon + 0x28A4);
codecave = magic.AllocateMemory(0x1000);
if (g_clientCon == 0)
  return;
magic.Asm.Clear();
magic.Asm.AddLine("retn");
magic.WriteUInt(codecave, (uint)1000);
magic.Asm.Inject(magic.ProcessHandle, codecave);
uint value = magic.ReadUInt(codecave);
MessageBox.Show(value.ToString());

Here's even a shortened down version of what I had, doesn't do the same thing but has the same result. I'm having no problems doing standard Reads/Writes. It looks like BlackMagic.Asm doesn't want to write to the process, but I'm not sure why. I thought all of the ProcessHandle setting etc. was handled inside the constructors... I even tried just assembling it with the Asm subclass and writing it with the original BlackMagic class. Still no working.

[Nesox]

Do you copy the FASM.dll to the output directory? wont work otherwise.
If that wont work try if ure using vista switch to the Administrator account and disable UAC and DEP

[Cypher]

Do you copy the FASM.dll to the output directory? wont work otherwise.
If that wont work try if ure using vista switch to the Administrator account and disable UAC and DEP

Don't disable DEP. Fix your software to be DEP compatiable.

DEP is one of the worst things you can disable, it protects you from a whole range of potential nasties.

There's a good reason for enforcing page execute flags.

[lanman92]

D'oh. I sure wish it at least threw me an exception when it can't find the FASM.dll file... Sorry for the hassle.

[SKU]

D'oh. I sure wish it at least threw me an exception when it can't find the FASM.dll file... Sorry for the hassle.

You're not the first one missing FASM.dll. It's the first thing I do now whenever I create a new project, move FASM.dll in the debug/release folder.

[Nesox]

You're not the first one missing FASM.dll. It's the first thing I do now whenever I create a new project, move FASM.dll in the debug/release folder.

Or add it to the project. And then in the properties Copy to output directory: copy if newer

[Shynd]

Oh ****, I thought I had released the version of fasmdll_managed that didn't require FASM.dll anymore. Check the GameDeception page in a few minutes or so and it'll be updated. Shit, I'm sorry that you guys had to go through all of that FASM.dll shit while I've been gone

[storage]

Hey Shynd i have downloaded your new version, but i´cant debug with the new version.

[Shynd]

Comes with the source, recompile as Debug instead of Release.

[Apoc]

Oh ****, I thought I had released the version of fasmdll_managed that didn't require FASM.dll anymore. Check the GameDeception page in a few minutes or so and it'll be updated. Shit, I'm sorry that you guys had to go through all of that FASM.dll shit while I've been gone

Nice job Shynd. The less DLLs the better.

Just wish you could embed a C++/CLI with native C++ as a satellite assembly. (Basically, merging the DLLs into a single DLL.)

[Cypher]

Nice job Shynd. The less DLLs the better.

Just wish you could embed a C++/CLI with native C++ as a satellite assembly. (Basically, merging the DLLs into a single DLL.)

Eeeew. C++/CLI. Please go kill yourself now.

[Apoc]

Eeeew. C++/CLI. Please go kill yourself now.

The managed FASM has C++/CLI you tard.

[Cypher]

Go

kill

yourself.

[lanman92]

Off-topic, but how do you access the buffs/debuffs for players and units now? I remember it being changed a lot from TBC->WOTLK. Isn't it buried in UNIT_AURA or something?

[SKU]

I'm pretty sure g3gg0/Sillyboy posted it somewhere lanman.