Problems with SeaMonkey 1.1.18 on Windows 95?
Posted 16 September 2009 - 01:54 PM
After installing the update last night, I was prompted with this dialogue whenever I ran the browser:
Reverting to 1.1.17 fixed the problem. Seeing that I use Windows 95 OSR2, might this be an OS version-dependent bug?
Posted 16 September 2009 - 02:29 PM
I cured it by enabling MS Cryptography in Windows Setup (Control Panel, Add/Remove Programs, Windows Setup). This installed RSABASE.DLL in windows/system, and created the following reg key:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography] [HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Machine Settings] "CatRoot"="C:\\WINDOWS\\SYSTEM\\CatRoot\\" [HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Defaults] [HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Defaults\Provider] [HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Defaults\Provider\Microsoft Base Cryptographic Provider v1.0] "Image Path"="rsabase.dll" "Type"=dword:00000001 "Signature"=hex: (a long string of hex data here) [HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Defaults\Provider Types] [HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Defaults\Provider Types\Type 001] "Name"="Microsoft Base Cryptographic Provider v1.0"
No more complaints from FF, and now full functionality. Maybe this is related to your issue.
This post has been edited by chromatic47: 16 September 2009 - 02:34 PM
Posted 17 September 2009 - 11:48 AM
The problem is that 1.1.18 updates the NSS component to the latest version, which is responsible for SSL. This newest version was not meant to run on Win9x. However, it does run fine on Windows 98 with IE. That's because the IE4 shell implements the API that is missing in plain Windows 95 and Windows 95 without IE4.
I have filed bug#514955 on this. There is no definite resolution yet, though solutions have been proposed.
Posted 17 September 2009 - 12:58 PM
Ah, I was afraid of that. Unfortunately, it feels as though nowadays the developers would rather wash their hands of "Windows versions sans IE" entirely than fix the bug. Talk about sleeping with the enemy!
(For what it's worth, the MozillaZine thread is here...)