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

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.

Share this post


Link to post
Share on other sites

Hello MDGx,

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

Petr

Share this post


Link to post
Share on other sites
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.

Edited by MDGx

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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

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.

Share this post


Link to post
Share on other sites
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.

Edited by erpdude8

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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

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...