I'm trying to run v1.5.4 on my Win95-C laptop. KM installed fine and runs great unless I try to visit an HTTPS site, then I get the error message: "Could not initialize the browser's security component".
Maybe I shouldn't be trying to run this friendly little browser on Win95. Do I have to go back to Opera v10.00?
I remember some time ago someone had this problem in Win95, this is due to some OS dll that is not include in Win95. Really is Win95 that not support SSL you can try update to Win98 or some people solved this problem updating to IE6 SP1.
SSl dll is included in IE6 but not in IE5.
2.go to start menu > run
in run type this:
regsvr32 shlwabi.dll
click ok
should displayed registered successfully..and kmeleon will be able to access secure websites..
if it still doesn't work..try a minimum internet explorer 5 or 5.5. install to get the missing components
I've tried all the suggestions of the "add this file" variety listed in this thread (and the other two linked threads) without any luck.
AHZVX claims to have made K-Meleon work by installing IE v6.0 first, but he was running Win98 to begin with. I am not prepared to do that and risk mucking up my perfectly well-running Win95 installation.
The good news is that in the course of researching a fix for getting K-Meleon to run on Win95, I have found another browser, Firefox v1.5, which has a lot of the "look and feel" of K-Meleon. It WILL run on Win95, right out of the box, without adding anything. I used the "portable" version from here: http://portableapps.com/apps/internet/firefox_portable
Quote desga2
What is the website where have you this problem?
I used https://www.google.com/analytics/home/ as a quick test, but any URL that starts with "https" generates the SSL error. Or try http://www.netflix.com and click "Member Sign In." Also the K-Meleon GUI, without even being connected to the Internet, triggers the error message:
Edit -> Preferences -> +Privacy -> Encryption
Stupid question sorry, but when you type "about:config" and filter for ssl2, they ARE all on "true", right?
Can hardly be any missing windows file, or FF couldn't do it either. It's just hard to imagine for me that a gecko-1.8 KM couldn't do what a gecko-1.8 Firefox can, and a much older version at that. Still suspect just one of those hundreds of settings inside, or some certificate file or such, hmm...
I reinstalled a fresh copy using the K-Meleon1.5.4en-US.exe installer, using the default components suggested by the installer. "about:config" with a filter of "SSL2" returned seven entries, all set to "false." I set these all to "true."
Edit -> Preferences -> +Privacy -> Encryption
still returns "Could not initialize the browser's security component."
i found this:
http://www.pocketsoap.com/pockethttp/
sez there:
"Windows 95 requires DCOM95 Installing first
Windows 95/98 requires additional installs for SSL support, see this KB article for details."
since they specifically mentioned 95 and 98(not se) that sounds like winsock update
I don't have MSI installer on my machine, and I don't particularly want it. Do you know what's in that MSI link you posted? Is that just another way of installing the DCOM95 update?
Thanks.
Jerry
Edited 1 time(s). Last edit at 04/27/2010 02:35AM by Jerry.
it's not dcom.. it's an active desktop update which updates ssl as well .ms is only offering sslfor 95 with dsclient and not standalone.
inside the msi installer is an installable cab file dsclient.exe and an eula license readme. inside the dsclient cab is a bunch of dlls. 2 of them i suspect is your needed files. secur32.dll and crypt.dll.. i'd compress them and upload them so you can save in windows\system folder but i don't really think that would be a good idea as they might be rely on other dlls and because they are system files they will need a proper install routine so they can be registered correctly because a version mismatch could send the system into an endless boot loop.
the installable cab is just as good as the msi..so you can just use it instead to update.
I ran the DSCLIENT.EXE setup, but it stalled on the screen that says:
"Please wait while the wizard configures your system. Destination file:"
The thermometer (progress bar) filled completely, but there was no activity after that, and the CANCEL button was the only active button available. I let it sit for 20 minutes, then canceled.
I had used TOTALUNINSTALL before running DSCLIENT.EXE, so I had a list of all the changes it had made, even though the last message told me I had not installed DSCLIENT.
I rebooted and tried K-Meleon, but I still get the "Cound not initialize . . . " message from EDIT -> PREFERENCES -> PRIVACY -> ENCRYPTION.
K-Meleon seems to have clumps of DLLs in only two folders, so I tried putting all the DSCLIENT DLLs in each of those folders to see if K-MELEON would find anything it liked and use it, but it didn't.
BTW, the DCOM95 in the DSCLENT package *is* the same one I've been running all along.
I have to give you A+ for your persistence, though.
From information in the link at [forums.techarena.in], I checked for a CERT8.DB file, but there wasn't one anywhere in my K-Meleon tree.
I uninstalled v1.5.4, and installed v1.5.3 and found that SSL works fine there. There is also a cert8.db file in the v1.5.3 in the \K-Meleon\Profiles[unique].default folder, so I copied it to the similarly named folder in v.1.5.4, but still no joy.
v1.5.3 also had a key3.db file which v.1.5.4 didn't have. I added it, but it didn't help.
On your other suggestion:
The three files cryptdll.dll, instsec.dll, secur32.dll were copied and registered, but produced this error message with each registration: "Cryptdll.dll was loaded, but the DllRegisterServer entry point was not found." I also tried putting copies of the three files in \k-meleon as well as \windows\system, but Still no SSL function with v1.5.4.
v.1.5.3 is probably just the end-of-the-line for Win95 users. I tried the BETA version of v.1.6.0a4, and it won't even begin to load. At least with v.1.5.4 the GUI would load, so it appears we're heading off in a new direction without backward compatibility. You may have to hit me over the head with a brick, but eventually I will see the handwriting on the wall.
Thanks for all your help. You definitely get A+ for effort.
that's kinda weird, this means that gecko 1.8.1.24 no longer supports 95? which is quite strange since it works on 98 so it's probably missing some file or component in 95 that 24 gre needs but is available in 98
km 1.6 drops support for win 9x naturally but it's no kmeleon devs fault, it's because mozilla doesn't support 9x in gecko 1.9. there's an unoffical 9x update called kernelx which makes it possible for 9x users to run nt programs.. i'm not sure if it works on 95, personally i wouldn't fiddle with it on 95. you don't need to see the writing on the wall, i'd never tell anyone to update their os for a browser or any program..that's what others do in some forums but not here. it's great that 1.5.3 is working, you don't really need 1.5.4, i'd stick with 1.5.3. 1.5.4 fixes a couple of bugs in km macros, you'll probably never notice or need and the gre update is trivial security fix, so you aren't really at risk.
if you really wish to use 1.5.4 or future km for nt, only then i'll suggest updating to a more updated os yet usable with your hardware' that'd be windows 98se
I'm just going to continue with v1.5.3, which seems to work on all the sites I visit that require a "modern" browser, and it runs much better than Opera v10.00, which seems to have trouble releasing memory after its been used.
I use the HPGURU managed HOSTS file that blocks malicous sites, so I've never had any "security" problems.
OK -- now that I am comfortably ensconced in KM v1.5.3 for the rest of my life, how do I go about turning off that annoying start-up message that tells me there is a newer version of K-Meleon available?
Thanks! I never even looked there. I didn't think I had any "plugins." I always thought "plugins" were things like "Flash" and "Quicktime" and I knew I didn't have anything like that.
no, no, NO, disrupted! don't register the instsec.dll file!I found out that dsclient for win9x during setup renames the "instsec.dll" file to "secur32.dll" if dsclient setup detects certain 128bit encryption editions of certain DLL files.
INSTSEC.DLL is really a 128bit version of SECUR32.DLL
the normal SECUR32.DLL found in dsclient9x, dcom95 & dcom98 is a 56bit version.
Edited 1 time(s). Last edit at 11/16/2010 02:58AM by 4td8s.