It works great on WIndows2000/XP, but on Windows98, sometimes, I mean seldom, the shared memory gets trespassed by other process, or say that the memory contents get altered with no valid reason. For example, I have process A and process B using the shared memory, none of them did any change to the shared memory, but after a while some of the memory contents get modified mystically.
This never happened on Windows 2000/XP, but did from time to time on Windows9x. My 2c, do not use system page file, use a private disk file instead, to do so, give a valid file handle value to the first parameter of "CreateFileMapping".
Friend of mine uses this class on Win95 and has no problems with altered memory contents.
I designed this class only for WinNT like systems and support for different versions has been added later only because of very small and not important project.
I think your suggestion about using file for sharing memory on Win95 may help, but the real problem lies somewhere else - you are running process which damages that memory accidentally (assuming from your description).
C'mon we all know computers are experimental devices and should only be used for playing games.
Using them for alternative stuff like business, is clearly not using them for what they are intended.
Last Visit: 31-Dec-99 19:00 Last Update: 28-Apr-16 17:50