Index
> Windows > run dll example error: The handle is invalid |
| Author |
|
|
revolution 03 Apr 2009, 06:31
I think that depends upon your system. Things like which apps you have installed that hook into the startup DLLs. Maybe you have an app the uses the standard DLL injection to catch hotkeys?
I get this: lasterr.exe wrote: The operation completed successfully. |
|||
03 Apr 2009, 06:31 |
|
|
nazha 03 Apr 2009, 07:05
But why the masm32 dll example is ok? does it means the fasm compiled dll is easier be injected?
I have try re-downloaded the latest fasm package from this website to other machine and even run the dll example in safe model, got same error, regardless of re-compiled or not, the machine is cleaning. |
|||
|
03 Apr 2009, 07:05 |
|
|
revolution 03 Apr 2009, 07:14
Can you give the url for the masm source please.
|
|||
|
03 Apr 2009, 07:14 |
|
|
nazha 03 Apr 2009, 07:29
|
|||
|
03 Apr 2009, 07:29 |
|
|
revolution 03 Apr 2009, 07:40
Erm, I don't feel like downloading the whole package for a few KB of source. Perhaps you can post the relevant files here instead. Then we can compare an see what the masm source is doing differently.
|
|||
|
03 Apr 2009, 07:40 |
|
|
nazha 03 Apr 2009, 07:45
the source code is not same with fams's
_________________ Assembly Asker |
|||||||||||
|
03 Apr 2009, 07:45 |
|
|
revolution 03 Apr 2009, 07:52
Well the difference is that the masm code calls a number of functions that all change the lastError flag. So you will see the result of just the last call only. Whereas the fasm code calls no functions that affect the lastError flag and simply gets whatever error the Win32 loader last encountered.
Most notably is the very first call in the masm code is "invoke GetModuleHandle, NULL" which sets the lastError flag and overwrites any previous flag. |
|||
|
03 Apr 2009, 07:52 |
|
|
nazha 03 Apr 2009, 08:06
Oh, sorry, is my misunderstanding.
|
|||
|
03 Apr 2009, 08:06 |
|
< Last Thread | Next Thread > |
Forum Rules:
|