Yes, kernel 'new' and 'delete' was my idea also. And after the dll is loaded, but before the rest of the code requires it, they should be changed back to "normal" new and delete. This, however, seems to me to be a non-trivial task, and probably requires some esoteric knowledge of Windows and/or C++. I don't know how to change them back to normal before the rest of global objects initialize.
What bothers is that it looks to me that even if I manage to place my non-CRT new and delete it will probably end up failing on CryptAcquireContext again. Maybe calling DoDllPowerUpSelfTest again really is the way to go. Thanks for your help anyway. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [EMAIL PROTECTED] More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
