Hi... Put them in a unique folder/directory, available to all app's. An "easy" (if dirty) way, is in the System32 folder under Windows (or WinNT.) Make sure you have one set, AND ONLY ONE SET of them on your system, and all apps etc will use them as needed, so they only see the same version.
Or, put them in their own folder, and add the direct path to that in the systems default search path. When an app call's another resource, it first searches it's own (same) local path where the main .exe is. If it isn't there, it them searches Windows system path(s) if still not found, then according to the default search path, as defined by the system variables. Unless you specify the exact path and file you want. You can often make a "Huge" performance improvement, knowing how to manipulate paths etc. Keeping the default search path short helps a lot, as does setting up shortcuts to app's correctly, so the app "stars in" the corect folder, hence has a direct path to it's own needed resources. You can also "Register" them with Windows, so Windows will only ever look in one place. It can speed things up a lot, but at the expense of some flexability. This is exactly why some app's misbehave on some systems, and not on others. because they find other versions of the same DLL's (typicaly) before the ones you realy want them to use. A little experimenting with any compiler and making some simple DLL's that pass back a name (or one DLL that passes back it's own path) as a string to the caller, and then scatter coppies in the usual places, and you might be suprised what call's what and when. The default install's of Delphi in the past, do not do the "optimum" thing either, for the health of the system as a whole. Been there, got the 'T' shirt, and the numb brain cells etc... Regards. Dave B. > -----Original Message----- > From: Albert Wiersch [mailto:[email protected]] > Sent: 14 September 2009 23:44 > To: 'ICS support mailing' > Subject: Re: [twsocket] Specify full paths to libeay32.dll > and ssleay32.dll > > > I think I found a solution to my problem. I am adding the > needed path to the "PATH" environment variable (if it's not > already there) and this seems to work. > > If there is a better solution, then I'd still like to know. > > Thanks. > > -- > Albert Wiersch > AI Internet Solutions > [email protected] > http://www.htmlvalidator.com/ > > > > -----Original Message----- > > From: [email protected] > [mailto:[email protected]] > > On Behalf Of Albert Wiersch > > Sent: Monday, September 14, 2009 5:23 PM > > To: [email protected] > > Subject: [twsocket] Specify full paths to libeay32.dll and > > ssleay32.dll > > > > > > I have run into an issue where my application (the DLL part) cannot > > find libeay32.dll and ssleay32.dll when it is loaded from a > 3rd party > > app. I suspect because the 3rd party app path is searched > instead of > > my application's path - and these DLLs are in my app's > path, not the > > 3rd > party > > app path. > > > > So how can I specify a direct path to these DLLs to make > sure they are > > found? > > > > I checked TSslContext and it did not seem there was a way > to specify > > the full paths to the DLLs. > > > > Thanks. > > > > -- > > Albert Wiersch > > AI Internet Solutions > > [email protected] > > http://www.htmlvalidator.com/ > > > > > > > > -- > > To unsubscribe or change your settings for TWSocket mailing list > > please goto > http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket > > Visit our website at http://www.overbyte.be > > > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
