Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


MDGx

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

Recommended Posts

erpdude8:

I have updated Windows ME PCI.VXD fixes:

* Microsoft Windows ME PCMCIA Adapter Code 10 Device Manager Error PCI.VXD build 4.90.3004 Fix:

http://support.microsoft.com/?id=276602

Direct download [175 KB, English]:

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

BUG: Long Delay With Multiple Flash Memory Storage Devices after installing PCI.VXD 4.90.3004 Fix:

http://support.microsoft.com/?id=810447

FIX: MUST install OLDER PCI.VXD 4.90.3003 Fix below IF using more than 1 Flash Memory Device/Drive!

* Microsoft Windows ME Standby Hang With Multiple MS-DOS Prompt Sessions PCI.VXD build 4.90.3003 Fix:

http://support.microsoft.com/?id=285882

Direct download [173 KB, English]:

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

Edited by MDGx

Share this post


Link to post
Share on other sites

a belated happy new year 2006, MDGx. can you package the Win95/IE HTML Help v1.33 build 4.74.9273 addon into IExpress/Wextract? the current HHUPD95.EXE file will NOT work when running it directly from a write-protected floppy disk or a CD disc; the HHUPD.EXE and HHUPDNT.EXE files, on the other hand, do work on write-protected floppies and CD discs because those two HTML Help EXE installers extract files to a temp folder while HHUPD95.EXE does NOT; HHUPD95.EXE extract files on the current folder where HHUPD95.EXE is stored. I'll check back in a few days if HTML Help v4.74.9273 (hhupd95.exe) is created from IExpress/Wextract.

I'll also send you my unofficial DCOM95 Update pack for Win95 & unofficial DCOM98 Update pack for Win98 which includes the imagehlp.dll file from WinME and iprop.dll file from NT4 SP6a. Both of the imagehlp.dll and iprop.dll files I mentioned work under Win9xME. Please post up the unofficial DCOM update packs on your site ASAP.

also, take note that installing WMI 1.5 under Win95 requires DCOM 95. If DCOM95 is not installed under Win95, the WMI 1.5 installer will refuse to install the WMI files.

Edited by erpdude8

Share this post


Link to post
Share on other sites
a belated happy new year 2006, MDGx. can you package the Win95/IE HTML Help v1.33 build 4.74.9273 addon into IExpress/Wextract? the current HHUPD95.EXE file will NOT work when running it directly from a write-protected floppy disk or a CD disc; the HHUPD.EXE and HHUPDNT.EXE files, on the other hand, do work on write-protected floppies and CD discs because those two HTML Help EXE installers extract files to a temp folder while HHUPD95.EXE does NOT; HHUPD95.EXE extract files on the current folder where HHUPD95.EXE is stored. I'll check back in a few days if HTML Help v4.74.9273 (hhupd95.exe) is created from IExpress/Wextract.

I'll also send you my unofficial DCOM95 Update pack for Win95 & unofficial DCOM98 Update pack for Win98 which includes the imagehlp.dll file from WinME and iprop.dll file from NT4 SP6a. Both of the imagehlp.dll and iprop.dll files I mentioned work under Win9xME. Please post up the unofficial DCOM update packs on your site ASAP.

also, take note that installing WMI 1.5 under Win95 requires DCOM 95. If DCOM95 is not installed under Win95, the WMI 1.5 installer will refuse to install the WMI files.

HNY 2 u 2. ;)

I have repacked HHUPD95.EXE [html Help 1.33] with iexpress [696 KB]:

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

posted here:

http://www.mdgx.com/add.htm#HHU

and here:

http://www.mdgx.com/web.htm#HH95

I got the DCOM95 update from you a few days ago, but didn't have time to look at it yet.

If you wish to send [newer] DCOM95 + DCOM98 updates, please go ahead. I'll get to them as soon as I can.

I have added a DCOM95 warning for Win95 users who want to install WMI:

http://www.mdgx.com/add.htm#WMI

BTW:

I looked at IPROP.DLL you sent [from WinNT4 SP6a] with DCOM95 update, and compared with IPROP.DLL from WinME setup CD [the 1 I use with Win98 SE] using GETVER.EXE:

IPROP.DLL NT4 SP6a = 4.0.1381.326 11-18-1999 96016 Bytes

IPROP.DLL WinME CD = 4.0.1381.4 6-8-2000 110592 Bytes

Looks like the 1 from WinME is newer and byte size is larger, but I got no idea if code works better with 9x OSes [?].

Hope this helps.

Share this post


Link to post
Share on other sites

Posted unofficial patches [by anonymous developer] for:

- Windows 98 FE (First Edition)

- Windows 98 SE

- Windows ME

to fix the Security Vulnerability described in MS06-001 Security Bulletin:

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

This exposes Win98 (FE)/98 SE/ME computers to *critical* security risk when a malware WMF [Windows Metafile Format] file is accessed from the internet [embedded into web page], due to a flaw in Windows graphical rendering engine [GRE].

These patches replace GDI32.DLL + GDI.EXE from %windir%\SYSTEM [usually C:\WINDOWS\SYSTEM] with newer versions [click links below to download patches]:

- GDI32.DLL + GDI.EXE 4.10.2003 for Win98 FE:

http://www.mdgx.com/web.htm#9SU

- GDI32.DLL + GDI.EXE 4.10.2226 for Win98 SE:

http://www.mdgx.com/web.htm#9SU

- GDI32.DLL + GDI.EXE 4.90.3002 for WinME:

http://www.mdgx.com/web.htm#MEU

Patch author's explanation:

It looks like M$ is not going to create a security update for Win9x/ME.

Therefore I have created unofficial KB912919 GDI WMF [MS06-001]fixes, where support for the SETABORTPROC record type has been removed from the META_ESCAPE record in a WMF image.

Support for ABORTPROC functions registered by application SetAbortProc() API calls has *not* been removed.

I am providing these fixes 'as is' with no warranties expressed or implied etc.

BTW:

The author told me to post these patches without asking for beta testing, because...

I strongly advise against explicit beta testing here. The bugs in GDI.EXE (please remember my comments to 'eidenk') are one reason, the need for WMF files with various (and known!) META_ESCAPE records are another reason. I do not know how common such records are in typical WMF files. However, I have RF test equipment that produces lots of WMF files that happen to have some META_ESCAPE records. Ironically, these files cause a severe, but temporary GDI resource leak (a few % each time the screen is redrawn!) when used with MS Office applications under Win9x (_not_ related to META_ESCAPE records).

Hope this helps.

Edited by MDGx

Share this post


Link to post
Share on other sites

Just a note:

GDI.EXE contains the following note:

HE KB912919 hotfix - beta version!

Petr

Share this post


Link to post
Share on other sites
Just a note:

GDI.EXE contains the following note:

HE KB912919 hotfix - beta version!

Petr

That's a personal note from the author of the patch. ;)

But the author told me to post this patch without asking for beta testing, because...

I strongly advise against explicit beta testing here. The bugs in GDI.EXE (please remember my comments to 'eidenk') are one reason, the need for WMF files with various (and known!) META_ESCAPE records are another reason. I do not know how common such records are in typical WMF files. However, I have RF test equipment that produces lots of WMF files that happen to have some META_ESCAPE records. Ironically, these files cause a severe, but temporary GDI resource leak (a few % each time the screen is redrawn!) when used with MS Office applications under Win9x (_not_ related to META_ESCAPE records).

Hope this helps.

Edited by MDGx

Share this post


Link to post
Share on other sites
Hi MDGx,

could you ask the author of the patch to patch also the files for Windows 98 Gold, i.e. version 4.10.2002? They are contained in this fix: http://www.winpack.org/petr/98/289635USA8.EXE

Petr

hopefully the author should patch the ones from Win98 Gold ASAP.

so Petr, have you worked on getting the KB828028 hotfix for Windows ME? please respond as soon as you obtain the WinME kb828028 patch.

note to MDGx about D3DIM700.DLL build 4.7.0.723 Fix for ME; this fix is included in DirectX 8 and higher. May want to put "DirectX 8 and higher include D3DIM700.DLL fix". Or put "DirectX 9.0c installs newer D3DIM700.DLL file build 4.09.00.0902."

Share this post


Link to post
Share on other sites

-MDGx: re: 1/9 fix:

"* Microsoft Windows 98/98 SE MSASN1.DLL build 5.00.2195.6824 Security Vulnerability Fix"

-uh oh...

-I already had a newer ver. of MSASN1.DLL (5.0.2195.6905), and that 1/9 fix of yours renamed it to msasn1.qfe, but it did NOT replace it with anything... I had NO msasn1.dll in windows/system anymore, and that broke winUpdate... (among other things, I'm sure)...

...as soon as I renamed it back, winUpdate worked again...

???

[-EDIT: the specific winUpdate error was 0x80070485, supposedly relating to CABINET.DLL, and recommending to reinstall windows installer, but my cabinet.dll file was fine, and following the (annoying) MS instructions for "properly" reinstalling winInstaller of course didn't fix the error...]

Edited by PsycoUnc

Share this post


Link to post
Share on other sites

MDGx:

The unofficial WinME Gdi.exe/Gdi32.dll v4.90.3002 patch did not work.

Even though I shut down Stmgr.exe with either Coolkill or Winkill

and ran the WinME patch & rebooted, I got message "Windows detected

and repaired inconsistencies in some of your system files. Before

these repairs can take effect, Windows must be restarted.

Do you want to restart Windows now?"

Looks like WinME's SFP feature ran at startup and saw the wininit.log

file (NOT wininit.ini file) referencing the gdi.exe and gdi32.dll files

and restored the older GDI files after a Windows restart. You have

to prevent Stmgr.exe from loading at startup (from Msconfig) and then

run the unofficial WinME GDI patch for it to work just right.

In order for the unofficial WinME Gdi.exe/Gdi32.dll 4.90.3002 patch

to really work, you MUST disable System Restore, shut down Stmgr.exe AND

disable the SFP [statemgr] Startup entry by running System Configuration

Utility [msconfig.exe], click on Startup tab and uncheck Statemgr

and click on OK; dont reboot yet. Now run the unofficial WinME kb912919

patch, and after WinME loads, delete the wininit.log (NOT the wininit.ini)

file from the Windows folder. If you dont delete the wininit.log file and

you re-enable SFP [or run Statemgr.exe or Stmgr.exe], the dialog box

saying "Windows detected and repaired inconsistencies..." will appear and

restore the older Gdi.exe and Gdi32.dll files. So before re-enabling

WinME's SFP feature, delete the wininit.log file first.

Please post up these instructions on how to really get the unofficial

WinME Gdi.exe/Gdi32.dll 4.90.3002 patch to work.

Also the two GDI files from unofficial Win98se 4.10.2226 Gdi.exe/Gdi32.dll fix

have the wrong version dates. They should be dated 1/6/2006

instead of 10/4/2005.

Good that you posted both the WinME pci.vxd 4.90.3003 and 4.90.3004 fixes and

that you listed the problem the pci.vxd 4.90.3004 fix causes.

I was a little ticked off that you first posted the pci.vxd v4.90.3004 Q276602 fix w/out listing the problem that it causes. You know better not to prematurely

post up patches that have problems and not list the problems. Hopefully you won't commit any kind of mental blunder like that again.

-MDGx: re: 1/9 fix:

"* Microsoft Windows 98/98 SE MSASN1.DLL build 5.00.2195.6824 Security Vulnerability Fix"

-uh oh...

-I already had a newer ver. of MSASN1.DLL (5.0.2195.6905), and that 1/9 fix of yours renamed it to msasn1.qfe, but it did NOT replace it with anything... I had NO msasn1.dll in windows/system anymore, and that broke winUpdate... (among other things, I'm sure)...

...as soon as I renamed it back, winUpdate worked again...

???

[-EDIT: the specific winUpdate error was 0x80070485, supposedly relating to CABINET.DLL, and recommending to reinstall windows installer, but my cabinet.dll file was fine, and following the (annoying) MS instructions for "properly" reinstalling winInstaller of course didn't fix the error...]

PsycoUnc,

The 1/9 MSASN1.DLL 5.00.2195.6824 fix is NOT exactly MDGx's even though it is listed at the MDGx site. That patch was from Microsoft. Microsoft created the MSASN1.DLL 5.00.2195.6824 fix for Win98, NOT MDGx.

Edited by erpdude8

Share this post


Link to post
Share on other sites
"Windows detected

and repaired inconsistencies in some of your system files. Before

these repairs can take effect, Windows must be restarted.

Do you want to restart Windows now?"

There may be a incorrent checksum in file(s) or file(s) is in HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\SessionManager\WarnVerDLLs (CheckVerDLLs).

Share this post


Link to post
Share on other sites
could you ask the author of the patch to patch also the files for Windows 98 Gold, i.e. version 4.10.2002? They are contained in this fix: http://www.winpack.org/petr/98/289635USA8.EXE

Petr

I will ask.

BTW:

This fix is also available here:

http://ftp.isu.edu.tw/pub/CPatch/msupdate/.../289635usa8.exe

note to MDGx about D3DIM700.DLL build 4.7.0.723 Fix for ME; this fix is included in DirectX 8 and higher. May want to put "DirectX 8 and higher include D3DIM700.DLL fix". Or put "DirectX 9.0c installs newer D3DIM700.DLL file build 4.09.00.0902."
Done.
-MDGx: re: 1/9 fix:

"* Microsoft Windows 98/98 SE MSASN1.DLL build 5.00.2195.6824 Security Vulnerability Fix"

-uh oh...

-I already had a newer ver. of MSASN1.DLL (5.0.2195.6905), and that 1/9 fix of yours renamed it to msasn1.qfe, but it did NOT replace it with anything... I had NO msasn1.dll in windows/system anymore, and that broke winUpdate... (among other things, I'm sure)...

...as soon as I renamed it back, winUpdate worked again...

???

[-EDIT: the specific winUpdate error was 0x80070485, supposedly relating to CABINET.DLL, and recommending to reinstall windows installer, but my cabinet.dll file was fine, and following the (annoying) MS instructions for "properly" reinstalling winInstaller of course didn't fix the error...]

MSASN1.DLL Q828028 fix is not by me, it was obtained by Petr from Microsoft.

I am aware that it is older than MSASN1.DLL from Gape's SP2 2.1a, but Q828028 is the only one available for separate install.

Please notice that all patches at my site which start with Microsoft are official patches from MS.

Similarly, all patches at my site which start with Unofficial are unofficial patches by me or by others.

Hope this helps.

Edited by MDGx

Share this post


Link to post
Share on other sites
The unofficial WinME Gdi.exe/Gdi32.dll v4.90.3002 patch did not work.

Even though I shut down Stmgr.exe with either Coolkill or Winkill

and ran the WinME patch & rebooted, I got message "Windows detected

and repaired inconsistencies in some of your system files. Before

these repairs can take effect, Windows must be restarted.

Do you want to restart Windows now?"

Looks like WinME's SFP feature ran at startup and saw the wininit.log

file (NOT wininit.ini file) referencing the gdi.exe and gdi32.dll files

and restored the older GDI files after a Windows restart. You have

to prevent Stmgr.exe from loading at startup (from Msconfig) and then

run the unofficial WinME GDI patch for it to work just right.

In order for the unofficial WinME Gdi.exe/Gdi32.dll 4.90.3002 patch

to really work, you MUST disable System Restore, shut down Stmgr.exe AND

disable the SFP [statemgr] Startup entry by running System Configuration

Utility [msconfig.exe], click on Startup tab and uncheck Statemgr

and click on OK; dont reboot yet. Now run the unofficial WinME kb912919

patch, and after WinME loads, delete the wininit.log (NOT the wininit.ini)

file from the Windows folder. If you dont delete the wininit.log file and

you re-enable SFP [or run Statemgr.exe or Stmgr.exe], the dialog box

saying "Windows detected and repaired inconsistencies..." will appear and

restore the older Gdi.exe and Gdi32.dll files. So before re-enabling

WinME's SFP feature, delete the wininit.log file first.

Please post up these instructions on how to really get the unofficial

WinME Gdi.exe/Gdi32.dll 4.90.3002 patch to work.

Also the two GDI files from unofficial Win98se 4.10.2226 Gdi.exe/Gdi32.dll fix

have the wrong version dates. They should be dated 1/6/2006

instead of 10/4/2005.

I have updated the WinME GDI patch installation instructions:

http://www.mdgx.com/web.htm#MEU

The patch author date-stamped the GDI files for Win98 SE. I do not know the reason why.

Hope this helps.

Share this post


Link to post
Share on other sites
-oops, one old link at the top of topic needs updating:

"12-15-05: - Unofficial MS IE 5.5 SP2 Patch for Windows 98/98 SE [3.07 MB]:

http://www.mdgx.com/files/IE896688.EXE..."

...

-s/b IE905915.EXE

The unofficial IE Q896688 patch was created by a concerned user, it is not official from Microsoft, therefore I cannot update it whenever MS updates their official IE cumulative patch.

But recently I have received the newer unofficial IE905915 patch from the author, and I'll post it as soon as I can at my site. ;)

Hope this helps.

-MDGx: re: 1/9 fix:

"* Microsoft Windows 98/98 SE MSASN1.DLL build 5.00.2195.6824 Security Vulnerability Fix"

-I already had a newer ver. of MSASN1.DLL (5.0.2195.6905), and that 1/9 fix of yours renamed it to msasn1.qfe, but it did NOT replace it with anything... I had NO msasn1.dll in windows/system anymore, and that broke winUpdate... (among other things, I'm sure)...

...as soon as I renamed it back, winUpdate worked again...

???

[-EDIT: the specific winUpdate error was 0x80070485, supposedly relating to CABINET.DLL, and recommending to reinstall windows installer, but my cabinet.dll file was fine, and following the (annoying) MS instructions for "properly" reinstalling winInstaller of course didn't fix the error...]

I have reproduced the error you mention when trying to install MSASN1.DLL from Q828028.

After reboot, all I have in %windir%\system is MSASN1.QFE [the newer build 5.00.2195.6905 from Gape's SP2] and no DLL.

I had to rename it back to MSASN1.DLL to make it work. :(

Therefore I have added a warning:

* Microsoft Windows 98/98 SE MSASN1.DLL build 5.00.2195.6824 Security Vulnerability Fix:

http://www.microsoft.com/technet/security/...n/ms04-007.mspx

Direct download [166 KB, English]:

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

More info:

http://erpman1.tripod.com/current/asn1fix.html

Do NOT install this Fix IF already installed Unofficial Windows 98 SE SP2:

http://exuberant.ms11.net/98sesp.html

which installs newer MSASN1.DLL build 5.00.2195.6905!

Hope this helps.

Share this post


Link to post
Share on other sites

New MS06-002 KB908519 update is available.

Direct download:

Windows98-KB908519-ENU.EXE

Prerequisities: Windows 98 or 98SE, IE 5.5 SP2 or newer

WindowsME-KB908519-ENU.EXE

Prerequisities: Windows Me, IE 5.5 SP2 or newer

Contains

File: T2EMBED.DLL

Size: 163,600 bytes

Date: 24-Nov-2005 16:54

Version 5.00.2195.7073

The same file for 98FE, 98SE, ME and for all languages.

Petr

Edited by Petr

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...