If this is failing on a PC other than where it was compiled, perhaps you need to install the vcredist.exe (Visual C++ 2005 runtime redistributable)
On Wed, May 28, 2008 at 6:40 PM, Andy Finkenstadt <[EMAIL PROTECTED]> wrote: > The actual problem is likely related to this post: > > <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/2008-May/010742.html> > > You may need to copy one/all of the files found in these directories into > your application directory, in order to let the Debug CRT libraries (etc) be > correctly bound to your application, on a machine which does not have Visual > Studio 2005 installed. > > Microsoft Visual Studio > 8\VC\redist\Debug_NonRedist\x86\Micorosft.VC80.DebugOpenMP\Microsoft.VC80.DebugOpenMP.manifest > Microsoft Visual Studio > 8\VC\redist\Debug_NonRedist\x86\Microsoft.VC80.DebugCRT\Microsoft.VC80.DebugCRT.manifest > Microsoft Visual Studio > 8\VC\redist\Debug_NonRedist\x86\Microsoft.VC80.DebugMFC\Microsoft.VC80.DebugMFC.manifest > > andy > > > Jeffrey Walton wrote: > > Hi Zhao, > > Unfortunately, my test systems do not exhibit the behavior: > Vista/VS2008 and XP/VS2005. > > > > Maybe I ignored other places? I used the VS2005. > > > Vista? If so, try running as Administrator (i.e., elevated > privileges): Start -> Program Files -> Visual Studio. _Right Click_ > Visual Studio, and click Run As Administrator. > > > > Could you please send me the valid debug/release DLL'S, Libs and PDBs. > > > Ouch! Where should I mail the DVD? > > The following was written by Garth Lancaster and myself. It may help > you. http://www.codeproject.com/KB/tips/CryptoPPIntegration.aspx > > When using the Dll, the lib for linking against the Dll shows up in > Dll_Output if I recall. (The lib for Dll linking versus static linking > is different). > > Finally, is the Dll (or FIPS Dll) a requirement? If not, ditch it. It > causes too many link problems :) If you have to use a Dll: follow the > advice from the article above with repect to setting up paths. Instead > of copying the static library into C:\Crypto++, copy the Dll's lib and > the Dll into C:\Crypto++ [I presume it went into C:\Crypto++ - adjust > as necessary]. > > Jeff > > On Wed, May 28, 2008 at 6:34 AM, Zhao Yu <[EMAIL PROTECTED]> wrote: > > > Hi Jeff, > > I checked the cryptopp.dll by cacls, the result is that it permits > every one to access with full control. So, the problem still exists. > Maybe I ignored other places? I used the VS2005. > Could you please send me the valid debug/release DLL'S, Libs and PDBs. > (I have compiled the source and linked with VS2005, but still exists > the problem.) > Thanks, > Zhao > > On 5月28日, 下午3时15分, [EMAIL PROTECTED] wrote: > > > Hi Zhao, > > > > ... got the initialization error which shows "Application > initialize(0xc0000005) failed". > > > This is access denied. Run cacls over the dll to see who has > permission to read and execute it. > > Jeff > > On 5/27/08, Zhao Yu <[EMAIL PROTECTED]> wrote: > > > I downloaded the Crypto++5.52 windows version from SourceForge with > Release32/Debug32 DLLs and Libs. In debug mode, I complied and linked > my project with Crypto++'s debug libs(not static link), it succeeded. > Next I copied the debug DLL to the .exe directory and run my .EXE, I > got the initialization error which shows "Application > initialize(0xc0000005) failed". It looks like causing by binary couple > problem at linkage stage. I was crazy with such a problem which waste > me lots of time. Gentelmen, please help me!Thanks you in advance!! > > > > > > > -- "Thou shalt not follow the null pointer for at its end madness and chaos lie." --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
