Printable View
hello guys:
tht scenario, it's interesting and somehow weird,yesterday i copied OS's dll 'gdi32.dll' to c:\ from c:\windows\system32\,and i ran loadlibrary/getprocaddress things in a MFC dialogbox-based application, i'm sure tht i've locatted the function 'CreateCompatibleDC' from 'c:\gdi32.dll' correctly; then i invoked tht function,my app shown me a collapse of memory error,i can't understand tht, Ain't those OS dlls supposed to be available anytime anywhere?
Did you call it with correct arguments? And BTW, why would you do something like that?
several of the system DLL's simply won't work if you copy them to anothe rlocation or force them to be loaded in a different location in memory.
If you already have a GDI32, then force-load another GDI32 by copying the DLL to another location and calling loadlibrary... Doesn't surprise me at all it ends up crashing or not working.
Hopefully you run this malware only on your own system and not screw up someone elses.Quote:
Originally Posted by Entrant_phil
Regards,
Paul McKenzie
so i guess msft had something in OS DLLs as principle for security's sake, and yep i'd have this awesome procedure only running on my own system lol. thank you guys for replies;
have a nice day