- Forum
- Windows Programming
- Shared Memory DLL problem
Shared Memory DLL problem
Hi
I'm trying to use a vendor's specific DLL to communicate with a bioreader. I have multiple instances of the same application, each one to communicate with a particular reader. The problem is that the DLL provided uses shared memory and changes made to the shared data are replicated into each application.
Changing the DLL filename to each instance of the could be a solution, but instances of the application are dynamically started.
Is there any way to isolate the memory space of an application to a DLL? In practice i Want to have multiple instances of the same DLL, one for each application, but don´t know how to do it.
Thank you very much for helping me,
Greg
I'm trying to use a vendor's specific DLL to communicate with a bioreader. I have multiple instances of the same application, each one to communicate with a particular reader. The problem is that the DLL provided uses shared memory and changes made to the shared data are replicated into each application.
Changing the DLL filename to each instance of the could be a solution, but instances of the application are dynamically started.
Is there any way to isolate the memory space of an application to a DLL? In practice i Want to have multiple instances of the same DLL, one for each application, but don´t know how to do it.
Thank you very much for helping me,
Greg
Changing the DLL filename will not necessarily change the shared memory mapping name.
That's not what is the issue here. Shared memory is mapped by name. The mapping is made at runtime (with MapViewOfFile). The DLL needs to support different names.
BTW, what about synchronisation?
| Is there any way to isolate the memory space of an application to a DLL? |
BTW, what about synchronisation?
Topic archived. No new replies allowed.