Fast web browser for 98?

[oc_dt]

Thanks for your suggestion. I'll try update the VC runtime to SP4 first to try for improvement. And only update to later (SP5 or even SP6) if necessary.

I'm reading the info document for vcredist.exe and found no uninstall instruction there. Also I found the advpack.dll included there as follows:

Product Name: Microsoft® Windows NT® Operating System

Product Version: 4.71.1015.0

I double checked their installation instruction which mentions that this is for Windows 98 too. Is it something wrong?

[CharlotteTheHarlot]

Thanks for your suggestion. I'll try update the VC runtime to SP4 first to try for improvement. And only update to later (SP5 or even SP6) if necessary.

I'm reading the info document for vcredist.exe and found no uninstall instruction there. Also I found the advpack.dll included there as follows:

Product Name: Microsoft® Windows NT® Operating System

Product Version: 4.71.1015.0

I double checked their installation instruction which mentions that this is for Windows 98 too. Is it something wrong?

I don't have a link handy but have this clue as to where that latest MSVCRT.DLL came from. I found a note mentioning: UnOfficial Q932590 aka MV6 (nothing else, sorry). It may have been from the Axcel/MDGx site now that I think about it. Search over there or hopefully someone will respond here with a link. It also might have been contained within one of those large Visual Studio updaters.

Sometimes those Runtime Updater packages will not work, it is highly dependent on what system files you do have. If you extract it manually and find that exact MSVCRT.DLL displayed above, you can do the upgrade yourself by hand if necessary. Because that file is almost sure to be in use by the shell, it will have to be replaced either in WININIT.INI or manually in F8 command line mode.

BTW: another important code base which can make or break applications are the matched quad set of ASYCFILT.DLL, OLEAUT32.DLL, OLEPRO32.DLL, STDOLE2.TLB. Check out what you have. Currently on Win9x I have 2.40.4519. These are changed in matched sets of four, using those same two methods. And I know I have seen those packages somewhere at Axcel/MDGx.

The point I am making is that if Firefox 2 is not working on Win9x, it is likely a local code base problem: (1) MSVC libs (2) MSVB libs (3) OLE/DCOM sets. Iron them out, not just for Firefox but many other apps as well.

[oc_dt]

Just one minor point to clarify. My FF2 works happily on 98SE.

I triggered the IPF on MSVCRT.DLL on the following 2 occassions only:

* opening insanely many tabs; or

* leaving the FF2 idle for a while

The SP4 vcredist.exe should contain the consistent set of files required:

VCREDIST INF 3,208 08-30-00 3:43p VCRedist.inf

PRESETUP EXE 28,672 08-30-00 3:45p PreSetup.exe

50COMUPD EXE 509,984 06-24-00 10:40a 50comupd.exe

ASYCFILT DLL 147,728 02-11-00 4:58p asycfilt.dll

ATLA DLL 73,785 02-11-00 4:58p atla.dll

COMCAT DLL 22,288 02-11-00 4:58p comcat.dll

MFC42 DLL 995,383 02-11-00 4:58p mfc42.dll

MFC42U DLL 995,384 02-11-00 4:58p mfc42u.dll

MSVCIRT DLL 77,878 06-16-98 7:45p msvcirt.dll

MSVCP60 DLL 401,462 06-16-98 7:52p msvcp60.dll

MSVCRT DLL 278,581 03-07-00 3:22p msvcrt.dll

OLEAUT32 DLL 598,288 02-11-00 4:58p oleaut32.dll

OLEPRO32 DLL 164,112 02-11-00 4:58p olepro32.dll

STDOLE2 TLB 17,920 02-11-00 4:58p stdole2.tlb

ATLU DLL 58,938 02-11-00 4:58p atlu.dll

ADVPACK DLL 74,960 02-14-00 12:24p ADVPACK.DLL

W95INF32 DLL 4,608 02-14-00 12:24p W95INF32.DLL

W95INF16 DLL 2,272 02-14-00 12:24p W95INF16.DLL

Regarding the quad, I tend to keep my existing ones as they are newer:

ASYCFILT.DLL 2.40.4518

OLEAUT32.DLL 2.40.4518

OLEPRO32.DLL 5.00.4518

STDOLE2.TLB 2.40.4518

Though I upgraded to the SP4 already, the cause of the problem should be related to GDI resources. After opening insanely many tabs, the GDI resources are used up. Are there any tuning can be done for GDI under 98?

I can't find the solution yet; however, this article is explanatory: Difference between Ram and Resources

Edited December 15, 2008 by oc_dt

[oc_dt]

Today, Firefox 2.0.0.19 is available. Are you going to install this one?

[rainyd]

Yes, I've upgraded automatically Firefox to the newest version. The lack of anti-phishing isn't a problem: I'm using NoScript.

[BenoitRen]

I would wait for Firefox 2.0.0.20. They forgot a last-minute fix. AGAIN. Fortunately it was a Firefox 2.0-only issue, so SeaMonkey doesn't need an additional update.

Phishing doesn't require JavaScript, though it helps. NoScript is so overhyped.

[oc_dt]

I would wait for Firefox 2.0.0.20. They forgot a last-minute fix. AGAIN. Fortunately it was a Firefox 2.0-only issue, so SeaMonkey doesn't need an additional update.

Phishing doesn't require JavaScript, though it helps. NoScript is so overhyped.

Firefox 2.0.0.20 is ready and installed.