Chris: Are you talking about doing this on my development box or on the machine where I intend to deploy? I'm running Active State Perl, 5.6. On my development box, I've already done the ppm install, which is why the program works in interpretive mode. I found that if I put ssleay.dll and libeay32.dll in the directory where my program runs, it works. My question is why doesn't the copy of the dlls that's packed into the exe become available to the running program the way other dlls do?
Thanks for your reply, Ken -----Original Message----- From: Chris Greenhill [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 3:55 PM To: LeFevre, Ken Cc: '[EMAIL PROTECTED]' Subject: RE: can't find ssleay.dll If you're using Active State Perl, go to the command line, type 'ppm' (Perl Package Manager). If you have version 5.8,type install http://theoryx5.uwinnipeg.ca/ppms/Crypt-SSLeay.ppd If you have version 5.6,type install http://theoryx5.uwinnipeg.ca/ppmpackages/Crypt-SSLeay.ppd half way through the installation, it should ask you if you want to install the SSLeay.dll -----Original Message----- From: LeFevre, Ken [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 2:37 PM To: [EMAIL PROTECTED] Subject: can't find ssleay.dll I have an application that is accessing a site using a secure socket (https) connection. It works great on my machine, where I have perl installed. When I distribute the perlapp-produced executable it fails with the message that it can't find SSLeay.dll. I searched the registry on my machine but didn't find the dll registered. I looked at the output from the compile and found the following line: +++ c:\Perl\site\lib\auto\Crypt\SSLeay\SSLeay.dll (which leads me to believe that the executable package contains the dll). Any ideas why the executable can't find it? The same program uses Daemon.dll, which is also not in my machine's registry, but is in the executable package (+++ c:\Perl\site\lib\auto\Win32\Daemon\Daemon.dll). Any ideas what I'm doing wrong? Thanks for your help, Ken
