Have tried EVERYTHING!

Has anyone got a fix?

"Stan" said in news:993001c40597$340f1220$(E-Mail Removed):
> Have tried EVERYTHING!
>
> Has anyone got a fix?

Might help if you tell us just what you DID try. Obviously you haven't
tried everything since: (1) The problem would've gotten fixed; or, (2)
You would've wiped the hard disk and started all over with a fresh
install but that's a royal pain.

I just had the same problem (okay, might be the same since you don't
really describe your problem in detail). Checkout
news:(E-Mail Removed). I performed a "recommended"
change from Microsoft but which killed my ability to use SSL (unless TLS
was also enabled).

Stan, this should do it:

Click Start, and then click Run.

In the Open box, type cmd, and then click OK.

At the command prompt, type the following lines and press
ENTER after each line:

regsvr32 softpub.dll
regsvr32 wintrust.dll
regsvr32 initpki.dll
regsvr32 dssenh.dll
regsvr32 rsaenh.dll
regsvr32 gpkcsp.dll
regsvr32 sccbase.dll
regsvr32 slbcsp.dll
regsvr32 cryptdlg.dll

Click OK when you receive the message that
DllRegisterServer in FileName succeeded each time.

Type exit to quit Command Prompt.

You should be immediately able to access jave password
sites.




>-----Original Message-----
>Have tried EVERYTHING!
>
>Has anyone got a fix?
>.
>

"Jim" said in news:99b701c405a6$443f0fb0$(E-Mail Removed):
> Stan, this should do it:
>
> Click Start, and then click Run.
>
> In the Open box, type cmd, and then click OK.
>
> At the command prompt, type the following lines and press
> ENTER after each line:
>
> regsvr32 softpub.dll
> regsvr32 wintrust.dll
> regsvr32 initpki.dll
> regsvr32 dssenh.dll
> regsvr32 rsaenh.dll
> regsvr32 gpkcsp.dll
> regsvr32 sccbase.dll
> regsvr32 slbcsp.dll
> regsvr32 cryptdlg.dll
>
> Click OK when you receive the message that
> DllRegisterServer in FileName succeeded each time.
>
> Type exit to quit Command Prompt.
>
> You should be immediately able to access jave password
> sites.

Note that the register of initpki.dll may take a long time. When I
registered it, it was something like a couple minutes later when it
"succeeded" popup window appeared. So, just go continuing the register
of the other files in the meantime.

Also note that Jim didn't come up with this gem. He is recounting the
information found in Microsoft's KB article # 813442:

Detecting Digital Signing Issues in Windows XP
http://support.microsoft.com/?kbid=813442

He missed one, however: Mssip32.dll.