[erpdude8]

MDGx, on Jan 16 2006, 11:07 AM, said:

Same patch, but removed mandatory WinME installation instructions because they are *not* necessary anymore:
* Unofficial Windows ME Graphics Rendering Engine GDI32.DLL + GDI.EXE build 4.90.3002 Security Vulnerability Fix:
http://www.microsoft...n/ms06-001.mspx
Direct download [390 KB, English]:
http://www.mdgx.com/files/ME912919.EXE
More info:
http://www.msfn.org/board/?showtopic=46581&st=193

unfortunately, the WinME install instructions ARE STILL NEEDED as the revised ME912919.EXE file that included the Nircmd.exe file to kill SFP, System restore, Vxdmon etc., DID NOT WORK properly under my WinME computer SAD!

it still generated that "Windows detected and repaired inconsistencies..." error message after reloading WinME & after installing ME912919 w/ Nircmd.exe file. I think the patch installed the updated GDI files to soon (or should I say "too quickly") before Nircmd had a chance to finish. The patch should WAIT until Nircmd finishes shutting down, SFP, system restore & Vxdmon and THEN install the updated files. AND note that the WININIT.LOG file is created AFTER rebooting & reloading WinME desktop, NOT right after installing the ME912919 patch.

MDGx told me it worked on a clean ME OS on his test machine. But it's a completely different story on my WinME computer and on my relative's WinME computer, both of which are slower than the one MDGx has. Looks like ME912919 doesnt work well on slow computers.

I have created .INF files that fix the "T2EMBED.DLL Fix Installer Error" problems under Win98 & ME. I have also created an .INF file that fix the "NWNP32.DLL Fix Installer Error" problem after installing the IPF Error Nwnp32.dll fix under Win95 osr2 and Win98 FE/Gold. I have sent these .INF files to MDGx and should post up these fixes as soon as possible. MDGx should also mention that the Nwnp32.dll FIX requires either MS Client for Netware Networks or Novell Netware v3.x/4.x Client to be installed in order for the Nwnp32.dll patch to really work & install the updated file.

This post has been edited by erpdude8: 23 January 2006 - 05:12 AM

[erpdude8]

ok MDGx. I have obtained the newer ME912919.EXE patch. It properly shut down SFP, system restore and Vxdmon and installed the updated GDI files after waiting for Nircmd to finish shutting down SFP/system restore. It no longer prompted the "Windows has found and repaired inconsistencies..." message after restarting the ME machine BUT the "You must restart the computer..." message popped up after reboot. And when I restarted the computer the second, third, fourth times, the Restart Computer message kept on popping up. And I noticed the wininit.ini file was still there in the Windows folder. I had to delete the wininit.ini file manually after the second or third time I rebooted when I ran ME912919.EXE again. Hopefully this will be fixed in V4 of ME912919.

Also, you may want to create a separate Unofficial HTML Help 5.20.3790.2453 patch just for WinME that will include the NIRCMD file (and call it HHUPDME.EXE). Ditto for Unofficial OLE Automation 2.40.4526 Update for WinME with the inclusion of NIRCMD file (and call that one OLEUPME.EXE).

[erpdude8]

erpdude8, on Jan 13 2006, 10:02 AM, said:

OH boooooo! BOOOOOOOO! booooo! BOOOOOOO!
<the crowd in my mind is BOOing at Petr for not attempting to ask microsoft support for thw winme Q828028 hotfix>

Then the way you requested for the Win98 Q828028 hotfix from microsoft support by email with "no problems" was a FLUKE! A stroke of LUCK! Then how do I really know that it was easy to ask for the Q828028 patches from MS support. what is your secret? I know I had a hard time asking for Win98 Q828028 patch by email several times and I just kept getting convoluted, circuitous responses.

i'm getting a little suspicious...

some Win9xME users prefer the Microsoft patches instead of "unofficial" patches because they are uncomfortable with unofficial solutions. And I get that.

AND I am NOT going to change my opinion on this until the WinME kb828028 msasn1.dll hotfix has been obtained (either by Petr, me or someone else) from MS. so far, Petr has not responded to this yet.

...getting even MORE suspicious on how Petr got the Win98 KB828028 patch. I no longer believe him when he emailed me a few weeks ago saying he got this patch with "no problems" from MS. I can only speculate he got it by other means.

[Petr]

Hello MDGx,

may I know why you have used the old crypt32.dll from Q329115 and not the new one from Q835732?

Petr

[MDGx]

Petr, on Feb 8 2006, 11:18 AM, said:

Hello MDGx,

may I know why you have used the old crypt32.dll from Q329115 and not the new one from Q835732?

Petr

Because of different CRYPT32.DLL builds:

- Q329115 = 5.131.2133.6 = newer [but older date 9-12-2002]
- Q835732 = 5.131.1880.14 = older [but newer date 1-23-2004]

I have used the newer build.

P.S.:
Have you tested this new CRYPT9X.EXE on your 9x computer(s)?
Please let me know if it doesn't work ok.
Thanks.

This post has been edited by MDGx: 09 February 2006 - 03:30 AM

[Petr]

MDGx, on Feb 9 2006, 10:28 AM, said:

Petr, on Feb 8 2006, 11:18 AM, said:

Hello MDGx,

may I know why you have used the old crypt32.dll from Q329115 and not the new one from Q835732?

Petr

Because of different CRYPT32.DLL builds:

- Q329115 = 5.131.2133.6 = newer [but older date 9-12-2002]
- Q835732 = 5.131.1880.14 = older [but newer date 1-23-2004]

I have used the newer build.

P.S.:
Have you tested this new CRYPT9X.EXE on your 9x computer(s)?
Please let me know if it doesn't work ok.
Thanks.

I think that 5.131.1880.xx are for Windows 98 and WinNT and 5.131.2133.xx version is for Windows ME.

5.131.1880.14 is much newer build with fixes not implemented in 5.131.2133.6 and therefore I'd recommend this newer fix for Windows 98 and Windows 98 SE, and older 5.131.2133.6 for Windows ME because according to erpdude8 posts there is no Q835732 crypt32.dll file that would work on Windows Me.

Sometimes the file date is modified and does not reflect the real date when it was built, but for PE executables you can find the build date/time in the PE header and for these files it is the same as file date-

Petr

[erpdude8]

Petr, on Feb 9 2006, 04:04 AM, said:

MDGx, on Feb 9 2006, 10:28 AM, said:

Petr, on Feb 8 2006, 11:18 AM, said:

Hello MDGx,

may I know why you have used the old crypt32.dll from Q329115 and not the new one from Q835732?

Petr

Because of different CRYPT32.DLL builds:

- Q329115 = 5.131.2133.6 = newer [but older date 9-12-2002]
- Q835732 = 5.131.1880.14 = older [but newer date 1-23-2004]

I have used the newer build.

P.S.:
Have you tested this new CRYPT9X.EXE on your 9x computer(s)?
Please let me know if it doesn't work ok.
Thanks.

I think that 5.131.1880.xx are for Windows 98 and WinNT and 5.131.2133.xx version is for Windows ME.

5.131.1880.14 is much newer build with fixes not implemented in 5.131.2133.6 and therefore I'd recommend this newer fix for Windows 98 and Windows 98 SE, and older 5.131.2133.6 for Windows ME because according to erpdude8 posts there is no Q835732 crypt32.dll file that would work on Windows Me.

Sometimes the file date is modified and does not reflect the real date when it was built, but for PE executables you can find the build date/time in the PE header and for these files it is the same as file date-

Petr

I've made a CRYPT9X patch of my own that has the latest crypt32 files for Win98, plus the latest msasn1.dll file from NT4 835732 patch. The CRYPT9X.EXE file should only be used under Win95/98 and NOT under ME.

Petr, I wonder if you would mind emailing Czech MS support for Hotfix 828028 for Windows ME. Looks like they seem to be more intelligent than the ones from the english MS email support address and know more of the 828028 hotfixes for win98/me. thanks for the email you sent me.

[the_guy]

MDGx,
I have just made an unofficial WMP7.1 update for Windows 98/SE/ME. I just need to make sure that it will work on ME without SR/SFP needing to be disabled.
As of my check, it will need to be for ME. I'll email you the patches in a couple of days.

Isn't the 892313 update superseded by 911565 (on all platforms except 2003 SP1 and 64-bit OSes)?

the_guy

[MDGx]

the_guy, on Feb 15 2006, 06:36 PM, said:

MDGx,
I have just made an unofficial WMP7.1 update for Windows 98/SE/ME. I just need to make sure that it will work on ME without SR/SFP needing to be disabled.
As of my check, it will need to be for ME. I'll email you the patches in a couple of days.

Isn't the 892313 update superseded by 911565 (on all platforms except 2003 SP1 and 64-bit OSes)?

the_guy

Thanks for making the patch.
I'll post it as soon as you send it.

Yes, the older Q892313 is superseded by newer 911565.
I have removed all links to 892313 from:
http://www.mdgx.com/wmp.htm
Thanks.

[Petr]

MDGx, on Feb 16 2006, 02:10 AM, said:

UPDATED 2-15-2006

Please see top of this topic for newest updates:
http://www.msfn.org/...showtopic=46581

Hello MDGx,

MS06-006 patch is also available on standard download page:

Security Update for Windows Media Player 9 for Windows 98 and Windows ME (KB911565)

It is not necessary to use the Windows Update location and file name.

Petr

[erpdude8]

the_guy, on Feb 15 2006, 07:36 PM, said:

MDGx,
I have just made an unofficial WMP7.1 update for Windows 98/SE/ME. I just need to make sure that it will work on ME without SR/SFP needing to be disabled.
As of my check, it will need to be for ME. I'll email you the patches in a couple of days.

Isn't the 892313 update superseded by 911565 (on all platforms except 2003 SP1 and 64-bit OSes)?

the_guy

You will need to make the unofficial WMP 7.1 update install under Win95 & NT4 as well. there is a way to make WMP 7.1 install under Win95 and NT4 systems and is mentioned at MDGx's Media Player page:
http://www.mdgx.com/wmp.htm

Petr, on Feb 16 2006, 03:04 AM, said:

Hello MDGx,

MS06-006 patch is also available on standard download page:

Security Update for Windows Media Player 9 for Windows 98 and Windows ME (KB911565)

It is not necessary to use the Windows Update location and file name.

Petr

Great job finding the MS download site for Win98/ME kb911565, Petr. I never thought MS will make that patch available there instead of just only the Windows Update site.

[erpdude8]

erpdude8, on Feb 17 2006, 08:59 AM, said:

the author of U891711 needs to use more "common sense" when dating and versioning files.
when giving kb891711.exe 4.10.2224 a date of 10/4/2005, and you revise it as 4.10.2225
you absolutely do NOT date it 10/4/2005. that can cause major confusion to Windows users
because they can not tell if the file was modified or not.

If Microsoft were to do such a thing in not changing the date of when a file was modified and the file was given a different version number,
I would be critical of them too.

I have obtained some XP SP2 hotfixes such as the 885295 ipnathlp.dll fix and the post-837001 [KB870753] fix. And yes maybe, MDGx, I may send you these patches (I'm feeling a little psychic) BUT after you post up the U891711 patch with the "corrected" date for v4.10.2225 of the KB891711.exe file. I insist that you post up the U891711 fix I sent you a few days ago so that when users download the updated U891711 fix containing KB891711.exe v4.10.2225 and Q891711.dll v4.10.2224, they will notice the newer build of KB891711.exe file has a different date than the previous build.

This post has been edited by erpdude8: 20 February 2006 - 07:24 AM

[erpdude8]

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.

[miko]

i just installed (or tried to) MP911564.EXE and the install program doesn't work correctly

it restarts the computer but the npdsplay.dll after restart is still 3.0.2.625 (initially installed with wmpplugin.exe)

i put it in place by hand.

[bristols]

miko, on Feb 25 2006, 11:31 PM, said:

i just installed (or tried to) MP911564.EXE and the install program doesn't work correctly

it restarts the computer but the npdsplay.dll after restart is still 3.0.2.625 (initially installed with wmpplugin.exe)

i put it in place by hand.

Same here. It created a directory - c:\program - and left npdsplay.dll there, except the file didn't have its .dll extension.

[miko]

i just checked that and had the same, moreover, when i deleted the folder i got a "could impact installed program" warning

[PsycoUnc]

-yup, same thing here...

[MDGx]

Guys,

I have updated MP911564.EXE to correctly install NPDSPLAY.DLL into the detected WMP directory. Default is C:\Program Files\Windows Media Player .
After install, the computer will not reboot anymore, because it is not necessary.

* Microsoft Windows 95/NT4/98/ME Media Player (WMP) Plug-in With Non-Microsoft Web Browsers NPDSPLAY.DLL 3.0.2.629 Security Vulnerability Fix:
http://www.microsoft.com/technet/security/...n/ms06-006.mspx
Unofficial WMP Patch for Windows 95/NT4/98/ME [223 KB, English]:
http://www.mdgx.com/files/MP911564.EXE

This post has been edited by MDGx: 30 March 2006 - 10:13 AM

[erpdude8]

MDGx, on Feb 27 2006, 03:41 PM, said:

UPDATED 2-27-2006

Please see top of this topic for newest updates:
http://www.msfn.org/...showtopic=46581

_________________________

Guys,

I have updated MP911564.EXE to correctly install NPDSPLAY.DLL into the detected WMP directory. Default is C:\Program Files\Windows Media Player .
After install, the computer will not reboot anymore, because it is not necessary.

* Microsoft Windows 95/NT4/98/ME Media Player (WMP) Plug-in With Non-Microsoft Web Browsers NPDSPLAY.DLL 3.0.2.629 Security Vulnerability Fix:
http://www.microsoft.com/technet/security/...n/ms06-006.mspx
Unofficial WMP Patch for Windows 95/NT4/98/ME [223 KB, English]:
http://www.mdgx.com/files/MP911564.EXE

GOOD!

Link to get Root Certificates Update:
http://download.windowsupdate.com/msdownlo...en/rootsupd.exe

I have downloaded this recently and file size is now 229 KB. Has Digital Signatures date of Jan. 16, 2006 and newer root certificate files.

[bristols]

MDGx, on Feb 27 2006, 03:41 PM, said:

UPDATED 2-27-2006

Please see top of this topic for newest updates:
http://www.msfn.org/...showtopic=46581

_________________________

Guys,

I have updated MP911564.EXE to correctly install NPDSPLAY.DLL into the detected WMP directory. Default is C:\Program Files\Windows Media Player .
After install, the computer will not reboot anymore, because it is not necessary.

* Microsoft Windows 95/NT4/98/ME Media Player (WMP) Plug-in With Non-Microsoft Web Browsers NPDSPLAY.DLL 3.0.2.629 Security Vulnerability Fix:
http://www.microsoft.com/technet/security/...n/ms06-006.mspx
Unofficial WMP Patch for Windows 95/NT4/98/ME [223 KB, English]:
http://www.mdgx.com/files/MP911564.EXE

Nice one MDGx, thank you for putting this right.

erpdude8, on Mar 3 2006, 11:00 PM, said:

Link to get Root Certificates Update:
http://download.windowsupdate.com/msdownlo...en/rootsupd.exe

I have downloaded this recently and file size is now 229 KB. Has Digital Signatures date of Jan. 16, 2006 and newer root certificate files.

Thanks for this erpdude8 - good spot.

Although it certainly contains updates to my current root certificates, I tried to run this file and it wouldn't install them (on 98 SE with SP2.1, and 98 SE with SP2.1a and 98SE2ME). Could you explain how you installed them, if it involved anything more than just running the .exe file, please?

This post has been edited by bristols: 12 March 2006 - 01:48 PM