S
sonnu
Hello,
I am very well aware that a 32-Bit process can never load a 64-Bit Dll
since the address space of the 32-Bit Process and the 64-Bit
Process/Library are not well matched.This is not even possible if I
restrict the DLL loading to the lower 1 GB of the 32-Bit Process
Address Space.
But I have scenario where I would need such loading to be made possible
as it was availabe in case when we moved to 8086 to 80386 processor
architecture (i.e when we moved from 16-Bit to 32-Bit). We had an
option to write THUNKING DLL layer which would do the job for us.
The 16-Bit application would call "LoadLibrary32W(..)" for loading a
32-Bit DLL in its process address space.
I am intersted in knowing if this kind of stuff could be done for
64-Bit Process as well, I have an idea that these THUNKING functions
are not made available on Win64, I am wondering if we have any other
similar wayout to support this.
Thanks,
sonnu
I am very well aware that a 32-Bit process can never load a 64-Bit Dll
since the address space of the 32-Bit Process and the 64-Bit
Process/Library are not well matched.This is not even possible if I
restrict the DLL loading to the lower 1 GB of the 32-Bit Process
Address Space.
But I have scenario where I would need such loading to be made possible
as it was availabe in case when we moved to 8086 to 80386 processor
architecture (i.e when we moved from 16-Bit to 32-Bit). We had an
option to write THUNKING DLL layer which would do the job for us.
The 16-Bit application would call "LoadLibrary32W(..)" for loading a
32-Bit DLL in its process address space.
I am intersted in knowing if this kind of stuff could be done for
64-Bit Process as well, I have an idea that these THUNKING functions
are not made available on Win64, I am wondering if we have any other
similar wayout to support this.
Thanks,
sonnu