meanwhile I succeeded in loading a ocx from memory, but I had to solve some issues, which also partly affected MemoryModule.

First I ran into a problem as the OCX DLL invokes GetModuleFileName() using the instance handle passed in DllEntry(), which cannot work, as this is not a valid instance handle for the OS.

Second I always ended in a runtime error R6002 inside the memory loaded DLL, which means, there’s no FPU support loaded. I finally found that the DLL calls _IsNonwritableInCurrentImage() before the FPU initialisation and this didn’t work correct. I ended up inside MemoryModule.c CopySections() where the section structs union member PhysicalAddress is set. On the DLL side this union is interpreted as VirtualSize, which is not correct any more. After removing the lines which set PhysicalAddress the FPU support was loaded correctly. So my question is, whether you know if it’s necessary to set PhysicalAddress or if it’s OK to keep it as VirtualSize?

Perhaps this is also some kind of help for other developers,
Gelbaerchen

I’d like to load a dll from memory that’s needed later on by another library (which is a ocx control). But this ocx control always loads the original dll and not the one which has been already preloaded from memory. So probably I need a way to define a “filename” for the dll loaded from memory, that is used by the win32 LoadLibrary() to check, whether this dll is already loaded. Is there any chance to do this?

Thanks and best regards,
Gelbaerchen

first I extracted the manifest from the dll I want to load with some kind of resource extractor and save this to a temporary file. Then ..

ACTCTX actctx = {sizeof(actctx)};
ZeroMemory(&actctx, sizeof(actctx));
actctx.cbSize = sizeof(actctx);
actctx.lpSource = static_cast(TempFilename);
HANDLE hActCtx = CreateActCtx( &actctx );
ULONG_PTR cookie = 0;
if ( ActivateActCtx( hActCtx, &cookie ) )
{
hMemModule = MemoryLoadLibrary( pBuffer );
DeactivateActCtx( 0, cookie );
ReleaseActCtx( hActCtx );
}

HTH
Gelbaerchen
}

müsste bei der derzeitigen Konfiguration:

#define DLL_FILE “..\\..\\SampleDLL\\Debug\\SampleDLL.dll”

heißen!

INVALID_HANDLE_VALUE wird nur bei z.B. CreateFile() zurückgegeben.
LoadLibrary() gibt NULL zurück! (in LoadFromFile).

Gruß

Unhandled exception at 0×75f4d36f in DllLoader.exe: Microsoft C++ exception: Debug::Error at memory location 0×001dde5c..

I’m loading a DLL that seems to depend on QT. This is what gets put to the console before the above runtime error is displayed:

QFileInfo::absolutePath: Constructed with empty filename

Unhandled exception at 0×75f4d36f in DllLoader.exe: Microsoft C++ exception: Debug::Error at memory location 0×001dde5c..

I’m loading a DLL that seems to depend on QT. This is what gets put to the console before the above runtime error is displayed:

QFileInfo::absolutePath: Constructed with empty filename

How did you solve that problem exactly? The DLL I’m trying to MemoryLoadLibrary() depends on msvcr90.dll and msvcp90.dll. LoadLibrary fails to load these because (i’m assuming) of this manifest issue.