After updating the Nexus Memory Manager to version 2.0, my application wouldn't start anymore. After disabling madExcept, the application started just fine. As there didn't seems to be any information already posted, I experimented a bit to come up with the following patch unit initialization order value:
ShareMem, HPMM, MultiMM, nxllFastCpuDetect, nxllFastFillChar, nxllFastMove, nxllMemoryManagerImpl, nxllMemoryManager, nxReplacementMemoryManager
Of these, nxllMemoryManagerImpl may be superfluous, but I added it just to be safe. All the other units are required and must appear in that order. With these changes, everything seems to work fine again.
Nexus Memory Manager 2.0 and madExcept
-
- Posts: 1
- Joined: Mon Aug 16, 2004 11:24 am
- Location: Finland