> The release build of dlltest.exe should work. I'm confused about what you
> tried to do, what worked and what didn't. Can you please describe it in
> more detail, step by step?
Ok, I downloaded the 5.0.4 FIPS DLL version, and opened up the DllTest\dlltest.dsp
The release build doesn't seem to build off the bat, so I set up a C++ tab preprocessor directory of "..\include" and a Linker tab library path of "..\Release" (according to the way it's set up by default, I could also have moved the lib into the DLL_Release directory, but this should be inconsequential).
I built the project. The release version is automatically put in DllTest\DLL_Release and I copied the Release\cryptopp.dll to DllTest\DLL_Release and DLLTest (I could have also set my VC++ to execute in the DLL_Release directory saving this copy).
I executed the program from explorer and from VC++ and it crashed every time. The first time the crash was an Application Error "The instruction at X referenced memory at X" right after the "FIPS 140-2 Sample Application completed normally." However, every other one from then on is an unhandled exception (0xC0000005 Access Violation) generated after "6. DSA key encode/decode succeeded."
> Also, what OS are you using?
Windows XP.
I should note that if I build the Release DLL and lib from the code in Source, they do not match the size of the one provided in the package and they do work without error.
The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, forwarding, or otherwise copying of this message is strictly prohibited. If you have received this communication in error, please notify Padcom immediately by e-mail at [EMAIL PROTECTED] and delete the original message. Although Padcom utilizes industry accepted methods to scan email and attachments for viruses, it does not guarantee that either is virus-free and accepts no liability for any damage sustained as a result of viruses. Padcom makes no representation or warranty (express or implied) as to the accuracy or completeness of any information provided in this e-mail message and expressly disclaims any and all liability that may be based on information contained therein.
