Nexus Memory Manager 2.0 and madExcept

delphi package - automated exception handling

Nexus Memory Manager 2.0 and madExcept

Postby Aapo Laitinen » Mon Aug 16, 2004 11:32 am

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.
Aapo Laitinen
Posts: 1
Joined: Mon Aug 16, 2004 11:24 am
Location: Finland

Postby madshi » Mon Aug 16, 2004 1:11 pm

That's exactly the right order (so well done :D). The next madExcept version will automatically use this setting.
Site Admin
Posts: 10200
Joined: Sun Mar 21, 2004 5:25 pm

Return to madExcept

Who is online

Users browsing this forum: No registered users and 11 guests