Jump to content

98 FE + 98 SE + ME updates + patches + (hot)fixes

MDGx
 Share

Recommended Posts

erpdude8

erpdude8

Posted
Posted
Regarding the 834158 Web Page Print Errors SHDOCLC.DLL 6.00.2800.1443 Fix:

I've tried installing it on two different 98 SE installations, both with IE6 SP1 installed, and have received this error message:

This update requires Internet Explorer 6.0 SP1 to be installed.

are u sure? if you have IE918899 or any other IE6 SP1 patch that has newer mshtml.dll files than the one found in the 834158 patch, you need to un-install it. My guess is that you have an IE patch with a version of mshtml.dll file higher than 6.0.2800.1443 installed which is preventing the installation of the 834158 patch. Restore the mshtml.dll file to version 6.00.2800.1106 and then try installing the 834158 patch.

the 834158 patch is really the "Web Page Print Errors MSHTML.DLL + SHDOCLC.DLL 6.00.2800.1443 Fix" which MDGx should rename the patch that way.

Link to comment
Share on other sites

erpdude8

erpdude8

Posted
Posted (edited)
This might be a little off topic but on MDGx's NT4 Essentials page lists the unofficial GDI32.DLL 4.0.1381.299 security fix for NT4. I now recommend this unofficial NT912919 patch be removed off MDGx's web site. The NT4 KB891711 patch has GDI32.DLL 4.0.1381.7270 while NT4 KB835732 has 4.0.1381.7263 of GDI32.DLL. So the unofficial NT912919 patch has a seemingly OLDER version of the gdi32.dll file.

MDGx, I wonder if the author of U912919/U918547 would be interested in patching the GDI32.DLL file for Windows NT4 SP6 and fix the WMF security flaws (and release GDI32.DLL as v4.00.1381.7271)? I'd been wondering if it'll be patched at all.

Edited by erpdude8
Link to comment
Share on other sites
bristols

bristols

Posted
Posted
My guess is that you have an IE patch with a version of mshtml.dll file higher than 6.0.2800.1443 installed which is preventing the installation of the 834158 patch.

You're quite right erpdude. I have MSHTML.DLL 6.00.2800.1556 (but only SHDOCLC.DLL 6.00.2800.1106). This is preventing the installation of the newer SHDOCLC.DLL. Thanks for prompting me to look at the patch more closely.

the 834158 patch is really the "Web Page Print Errors MSHTML.DLL + SHDOCLC.DLL 6.00.2800.1443 Fix" which MDGx should rename the patch that way.

I agree that the patch should be renamed, for clarity's sake.

Link to comment
Share on other sites
the_guy

the_guy

Posted
Posted

As we are talking about renaming descriptions, might I suggest renaming 830849 to

Automatic Detect Settings Errors INETCPL.CPL + SHDOCVW.DLL 6.00.2800.1413 Fix
Just a suggestion, for clarity's sake. Does anyone else agree with me?

the_guy

Link to comment
Share on other sites
erpdude8

erpdude8

Posted
Posted (edited)
Anyone know why CRYPT9X.EXE causes Windows Updates not to work?

wrong. totally the opposite. CRYPT9X.EXE should make Windows Update site work properly again after installing unofficial Win98se SP 1.62. version 1.62 of the 98se SP is what caused Windows Update not to work and was fixed in version 2.1a.

and you MUST also install the latest version of ROOTSUPD.EXE to resolve the Windows Update error of "expiring certificates" as noted in this thread:

http://www.msfn.org/board/index.php?showtopic=81676

Edited by erpdude8
Link to comment
Share on other sites
PROBLEMCHYLD

PROBLEMCHYLD

Posted
Posted

Anyone know why CRYPT9X.EXE causes Windows Updates not to work?

wrong. totally the opposite. CRYPT9X.EXE should make Windows Update site work properly again after installing unofficial Win98se SP 1.62. version 1.62 of the 98se SP is what caused Windows Update not to work and was fixed in version 2.1a.

and you MUST also install the latest version of ROOTSUPD.EXE to resolve the Windows Update error of "expiring certificates" as noted in this thread:

http://www.msfn.org/board/index.php?showtopic=81676

Sorry to tell you but its the other way around for me.Soon as i install

CRYPT9X.EXE Windows Update breaks.

Link to comment
Share on other sites
MDGx

MDGx

Posted
  • Author
Posted (edited)
Soon as i install

CRYPT9X.EXE Windows Update breaks.

I just installed CRYPT9X.EXE on my 98SE, and after I rebooted WU + WUC sites work just fine:

WU:

http://windowsupdate.microsoft.com/

WUC:

http://windowsupdate.microsoft.com/catalog/

Please d/l the file again [664 KB]:

http://www.mdgx.com/files/CRYPT9X.EXE

and reinstall.

Then reboot.

HTH

_______________________________________

the 834158 patch is really the "Web Page Print Errors MSHTML.DLL + SHDOCLC.DLL 6.00.2800.1443 Fix" which MDGx should rename the patch that way.
Done.

Also added SHDOCVW.DLL to Q830849.

Both here:

http://www.mdgx.com/ietoy.htm

Edited by MDGx
Link to comment
Share on other sites
erpdude8

erpdude8

Posted
Posted
CRYPT9X.EXE its working now. maybe i had a bad copy.thanks guys

yup, my thought exactly. you may have had an older version of CRYPT9X that broke WU and MDGx revised it a few times to fix the WU problems. the CRYPT9X.EXE file I got in mid August 2006 worked ok and did not break WU.

new XML security update (replaces previous XML 2.6, 3.0, 4.0 & 6.0 security updates/hotfixes):

http://www.microsoft.com/technet/security/...n/ms06-061.mspx

Link to comment
Share on other sites
MDGx

MDGx

Posted
  • Author
Posted (edited)

UPDATED · 10-11-2006

Updates:

- Added IE 6.0 SP1 Updater (IE6UPD) [thank you the_guy].

- Added new DX 9.0c October 2006 edition: full install + web setup.

- Added unofficial MSXML3.DLL + official MSXML4.DLL fixes [MS06-061 Q924191].

Enjoy.

P.S.:

MSXML* fixes above install also on NT4 + SP6a + IE 6.0 SP1.

___________________________________

the_guy:

I've also updated DXMNT* files with the latest versions you sent.

Thanks.

Edited by MDGx
Link to comment
Share on other sites
the_guy

the_guy

Posted
Posted (edited)

@MDGx: To me, it just looked like they wouldn't install. I didn't test them. 925486 I'm unsure over, but I'm positive 918899 won't install. The way the .inf files are: Q######.inf is for NT-based OS's, while Q######_d.inf is for 98/ME. Just my observation.

For your unofficial 924191, you are missing the following registry entries:

HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1b-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1c-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1d-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1e-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1f-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f20-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f21-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f22-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f26-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f28-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f29-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,"400"

Also, KB887606 for MSXML 4 is replaced.

the_guy

Edited by the_guy
Link to comment
Share on other sites
erpdude8

erpdude8

Posted
Posted (edited)
@erpdude8: I'll be making unofficial fixes for that by the end of the week. Also, there is no fix for msxml 2.6.

the_guy

that's because Microsoft will not release ANY MSXML 2.6 (msxml2.dll) fixes whatsoever.

Reading MS article 924191 carefully:

http://support.microsoft.com/kb/924191

After you install this security update, you cannot use Microsoft XML Parser version 2.6 in Microsoft Internet Explorer. This behavior is by design. The security update packages set the "kill bit" for this version of MSXML. The "kill bit" prevents the component from running in Internet Explorer.
the KB924191 security updates disable use of the msxml2.dll files; thus no fix for MSXML 2.6 will be developed.

Also, DirectX October 2006 Redist pack released. This one DOES work under Win98 & ME unlike the original August 2006 Redist. DirectX package. I didnt realize MS revised the Aug. 2006 DirectX Redist pack in late August to make it work under Win98/ME.

@MDGx: To me, it just looked like they wouldn't install. I didn't test them. 925486 I'm unsure over, but I'm positive 918899 won't install. The way the .inf files are: Q######.inf is for NT-based OS's, while Q######_d.inf is for 98/ME. Just my observation.

I think the_guy is on to something

You may want to take a look at the KB889669 patch for IE6 SP1:

http://support.microsoft.com/kb/889669

the KB889669 fix has Q889669.inf and Q889669_d.inf; note that this was before MS made GDR and QFE editions of updated IE6 SP1 files.

IE918899 and IE925486 should work under NT4 when using Q918899.inf & Q925486.inf respectively BUT Service Pack 6a and IE6 SP1 are required. IE6 SP1 cant install under NT4 systems less than SP6. for Win98/ME, create the Q918899_d.inf and Q925486_d.inf files and revise the unofficial fixes again.

Edited by erpdude8
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...