Hey Amit,

The msvcr80.dll is there already. Looking more closely
at the libeay32.dll which it appears ssleay32.dll
uses.

I am seeing Warning: At least one module has an
unresolved import due to a missing export function.
MPR.dll used by both libraries looks to be at fault.
Specifically WNetRestoreConnectionA is highlighted in
red.

Thanks,
Garyc
--- Amit Hakoo <[EMAIL PROTECTED]> wrote:

> Try to drop in MSVCR80.dll in system32
> 
> --Amit
> 
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of gary clark
> Sent: Friday, June 01, 2007 4:13 PM
> To: openssl-users@openssl.org
> Subject: RE: openssl clients for windows
> 
> Hey Amit,
> 
> I built the visual studio project very similar
> except
> without the batchfile you created. I managed to
> successfully run the testclient on this machine. 
> 
> However I did build it with Visual Studio 2005. I'm
> not sure if this causes issues when trying to port
> to
> a machine without a previous installation of
> openssl.
> 
> Anyway took the libraries and carried them over to
> the
> machine without openssl installed. I get the same
> problems as before.
> 
> One thing I did notice and did correct was that
> msjava.dll was not installed on the test machine and
> dependency walker caught this. Also there appear to
> be
> calls made which seem to fail
> "FlsAlloc","FlsGetValue"
> ,"FlsSetValue" and "FlsFree". 
> 
> I'm a little at loss.
> 
> Thanks for your patience and help on this.
> 
> Garyc
> 
> --- Amit Hakoo <[EMAIL PROTECTED]> wrote:
> 
> > What version of Visual Studio do you use?
> > 
> > Lets see.
> > First create a batch file (buildOpenSSL.bat)
> > Add the following lines
> > 
> > setlocal
> > 
> > call "C:\Program Files\Microsoft Visual Studio
> .NET
> > 2003\Vc7\bin\vcvars32.bat" > nul:
> > 
> > set PATH=%PATH%;
> > 
> > nmake -f ms\ntdll.mak
> > nmake -f ms\ntdll.mak test
> > nmake -f ms\ntdll.mak install
> > 
> > Put the batch file under \\0.9.8e\openssl-0.9.8e.
> > Then run the batch
> > file (double click will also do). 
> > 
> > Try it out
> > 
> > --Amit
> > 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf
> > Of gary clark
> > Sent: Friday, June 01, 2007 12:18 PM
> > To: openssl-users@openssl.org
> > Subject: RE: openssl clients for windows
> > 
> > Thanks Amit. I have never built the openssl
> > libraries
> > in visual studio. I built it for windows machine
> but
> > never use Visual Studio to build the libraries.
> > Using openssl-0.9.8e.
> > 
> > > cd /d C:\build\openssl-0.9.8e
> > 
> > > perl Configure enable-camellia
> > --openssldir=C:/www/openssl VC-WIN32
> > 
> > > nmake -f ms|ntdll.mak
> > >nmake -f ms\ntdll.mak test
> > 
> > > nmake -f ms\ntdll.mak install
> > 
> > How do you build these libs using visual studio?
> > 
> > Thanks,
> > Garyc
> > 
> > --- Amit Hakoo <[EMAIL PROTECTED]> wrote:
> > 
> > > Hi Gary,
> > > 
> > > Did you build the openssl dlls yourself or you
> got
> > > them pre-built? 
> > > 
> > > I had exactly the same problem. I just built the
> > > openssl dlls using
> > > visualstudio 2003 and it all worked fine (my app
> > was
> > > also built using
> > > VS2003).  
> > > 
> > > Please also send information about what dlls
> > > SSLEAY32.DLL depends on.
> > > You can find that information via the Dependency
> > > walker UI
> > > 
> > > --Amit
> > > 
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On
> Behalf
> > > Of gary clark
> > > Sent: Friday, June 01, 2007 11:52 AM
> > > To: openssl-users@openssl.org
> > > Subject: RE: openssl clients for windows
> > > 
> > > Hello,
> > > 
> > > I changed my codeGeneration for the console
> > > application to be /MT. It appears to be the only
> > way
> > > I
> > > can at least run the application. I then profile
> > the
> > > application using dependency walker.
> > > 
> > > I see :
> > > 
> > > Loaded "C:\windows\system32\SSLEAY32.DLL" at
> > address
> > > 0x10000000by thread 1. Successfully hooked
> module.
> > > LDR:LdrpWalkImportDescriptor() failed to probe
> > > C:\WINDOWS\system32\ssleay32.dll for
> > > manifest,ntStatus
> > > 0xc0150002
> > > Unloaded "C:\windows\system32\SSLEAY32.dll at
> > > address
> > > 0x10000000 by thread 1.
> > > LoadLibraryW("ssleay32.dll" returned NULL by
> > thread
> > > 1.
> > > Error This application failed to start because
> the
> > > apllication configuration is incorrect.
> > > 
> > > The same happenned for the libeay32.dll.
> > > 
> > > Can somebody explain what is happenning?
> > > 
> > > Thanks,
> > > Garyc
> > > --- gary clark <[EMAIL PROTECTED]> wrote:
> > > 
> > > > Hello,
> > > > 
> > > > I ran the dependency walker and performed a
> > > profile.
> > > > 
> > > > The see the error Message
> > > > 
> > > > "Failure to starting the process. The
> > application
> > > > has
> > > > failed to start because the application
> > > > configuration
> > > > is incorrect"
> > > > 
> > > > Whats interesting I dont see the ssleay.dll or
> > > > libeay32.dll?
> > > > Am I suppose to? I wanted to load these
> > > dynamically?
> > > > Can they be loaded dynamically using
> > LoadLibrary?
> > > > 
> > > > When I run it on the installed openSSL machine
> > no
> > > > problem.
> > > > 
> > > > Thanks,
> > > > Garyc
> > > > 
> 
=== message truncated ===

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to