On 4/23/08, Douglas E. Engert <[EMAIL PROTECTED]> wrote: > > I would have added the OpenSC bin directory to the path instead of > > copying these. > > > > > > > There may be issues with ssleay32 and libeay32 in system32 if > > > other applications also require their own versions of these dlls. > > > > > > > I don't like to add new stuff into system32... > > > > I don't either, but the way I read this, the "application" is winlogin, > so the dlls have to either all be loaded with LoadLibraryEx, or > in the system path. > > http://msdn2.microsoft.com/en-us/library/ms682586(VS.85).aspx?topic=306132
Again, why not add this to the system PATH? > Well have you ever gotten a CSP to call OpenSC during winlogin? > I wanted to see it work before believing, and there are still LoadLibrary > issues. It is standard DLL, it is not important. There are no issues I am aware of. Alon. _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
