Thanks; it worked. 

I had forgotten to change the "WINNT" libraries libnspr4.lib, libplc4.lib,
and libplds4.lib to the "WIN95" libraries nspr4.lib, plc4.lib, and
plds4.lib.


Another question:
After executing the application, which is designed to automatically insert
several certificates into the certificates database, I use the Personal
Security Manager (PSM) and the certutil tool for verification.

On the Windows 98 and Windows NT computers, both PSM and certutil were able
to display all of the certificates inserted by the program.

On the Windows 2000 computer, certutil displayed all of the certificates
inserted by the program, but PSM did not display all of the certificates
inserted by the program.

PSM on the Windows 95 computer also displayed a partial list of the
certificates inserted by the program and the "WIN95" version of certutil
would not execute.  The certutil program on Windows 95 presented the
following error message:
   "This program has performed an illegal operation and will be shut down."

Do you think there is a configuration issue causing PSM not to display
particular certificates that are displayed by another application?



-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 25, 2002 2:36 PM
To: Meadows Tyron
Cc: '[EMAIL PROTECTED]'
Subject: Re: WSOCK32.DLL on Windows 95?


Meadows, Tyron wrote:

> I've compiled two versions of a program to run in Windows 95/98 and
Windows
> NT/2000 environments by assigning the values WIN95 and WINNT respectively
to
> the OS_TARGET environment variable.  The "WINNT" program works as expected
> on computers running Windows 98, NT, and 2000.  On a computer running
> Windows 95, the "WIN95" program generates the following error when
starting
> the program:
> 
>      "The LIBNSPR4.DLL file is linked to missing export WSOCK32.DLL:1141."


If the file name is LIBNSPR4.DLL, you are using the WINNT
version.

The WIN95 version of NSPR is called NSPR4.DLL.

Wan-Teh

Reply via email to