32-bit and 64-bit Application Interoperability – Windows (part 1)

I needed a solution for making an application which is native 32b to “discuss” with a 64b client.
The client is creating a shared memory in which some data is saved. The server needs to process the data.

Amazon: Bestsellers Electronics and Photo


My company, Endpoint Cybersecurity, offers consulting on how to prepare for TISAX, ISO27001, NIS2, CSMS and SOC2 audits. It also works with companies to create and deploy a Secure Software Development Lifecycle, with various levels of AI support.
Get in touch with us here: https://www.endpoint-cybersecurity.com/contact/

Here is how MSDN describes the problem:
Running 32-bit Applications (on 64-bit OS): http://msdn.microsoft.com/en-us/library/aa384249(VS.85).aspx

And my problem is addresses here:
http://msdn.microsoft.com/en-us/library/aa384203(VS.85).aspx

Interprocess Communication

Amazon: Bestsellers Electronics and Photo

The following techniques can be used for communication between 32- and 64-bit applications:

* Handles to named objects such as mutexes, semaphores, and file handles can all be shared.
* Handles to windows (HWND) can be shared.
* RPC.
* COM LocalServers.
* Shared memory can be used if the contents of the shared memory are not pointer-dependent.
* The CreateProcess and ShellExecute functions can launch 32-bit and 64-bit processes from either 32-bit or 64-bit processes.
Amazon: Bestsellers Electronics and Photo


© Copyright 2008 Sorin Mustaca, All rights Reserved. Written For: Sorin Mustaca - Security & Technology


Want to work with me on this topic?
Check Endpoint Cybersecurity to see the consulting services we offer.