MDGx

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

1,295 posts in this topic

Please post here any problems you might encounter with Unofficial MSE 5.6 or 5.7.

Many thanks for your work on this!

I recently noticed there is a newer MSE 5.6 jscript.dll in KB942840. Could that be added to your MSE 5.6 update?

0

Share this post


Link to post
Share on other sites

All December 2007 TZ (Time Zone) DST (Daylight Saving Time) updates for all Windows 32-bit (Win32) OSes are finally here [as of December 4 2007]:

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

Of particular interest in this 98/ME forum...

* Microsoft Windows 98/98 SP1/98 SE/ME 2006-2008 December 2007 Cumulative Daylight Saving Time (DST) Time Zone Updates (English):

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

- Unofficial DST Update for Windows 98/98 SP1/98 SE/ME [114 KB, English]:

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

- Unofficial DST Update for Windows 98/98 SP1/98 SE/ME [117 KB, Italian]:

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

ALL these DST Updates MUST be installed by ALL Windows users REGARDLESS of geographical or Time Zone location!

ALL Unofficial Cumulative DST Updates above install ALL Time Zone Updates and also delete obsolete 2006 Australian (Melbourne Commonwealth Games) DST registry entries (if any):

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

Windows 98, 98 SP1 + 98 SE require ALL Year 2000 (Y2K) Updates + Q237493 TIMEDATE.CPL Fixes already installed:

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

DST Help and Support Center:

http://support.microsoft.com/gp/cp_dst/

List of products affected by DST:

http://support.microsoft.com/gp/dst_prodlist/

How to Configure 2007 DST:

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

DST Changes:

http://www.microsoft.com/windows/timezone.mspx

DST Updates MSFN Forum:

http://www.msfn.org/board/?showtopic=87399

Wikipedia: Daylight Saving Time (DST):

http://en.wikipedia.org/wiki/Daylight_saving_time

HTH

0

Share this post


Link to post
Share on other sites
I recently noticed there is a newer MSE 5.6 jscript.dll in KB942840. Could that be added to your MSE 5.6 update?
Here you go...

* Microsoft Windows 98/98 SP1/98 SE/ME Scripting Engines (MSE) v5.6 include: VBScript (VBS) 5.6, JScript (JS) 5.6, Windows Script Components (WSC), Windows Script Host (WSH) 5.6 + Windows Script Runtime (WSR) 5.6:

http://msdn2.microsoft.com/en-us/library/ms950396.aspx

- Unofficial MSE 5.6 5.6.0.8834 for Windows 98/98 SP1/98 SE/ME [669 KB]:

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

Enjoy.

0

Share this post


Link to post
Share on other sites

Well, here is a brief version history for DiskVSD.VxD:

04/23/99 10:22PM 4.10.0.1998 10,194 DISKVSD.VXD Win 98 SE (original distribution, same for FE)

06/08/00 05:00PM 4.90.0.3000 10,140 DISKVSD.VXD Win ME (original distribution)

08/09/00 05:00PM 4.90.0.3001 10,140 DISKVSD.VXD Win ME Q271277

Unpatched Win ME DiskVSD.VxD will not load under Win 98 SE (or FE). Windows'll instead throw a "file is damaged" message and freeze while loading. This can be solved by downversion patching. So here I offer you the patched version of Win ME DiskVSD.VxD v 4.90.0.3001, renumbered as 4.90.0.3002, to reflect the fact it has been patched and runs OK under Win 98SE and FE (but not anymore under Win ME!).

:w00t: Download-link: DiskVSD.VxD v. 4.90.0.3002 for Win 98 SE (and FE) :yes:

Q271277 "Computer Hangs Accessing Removable Disk Such as Magneto-Optical Disk" corrects a problem documented by Microsoft only for Win ME (it does not necessarily mean it doesn't exist in the Win 98 SE/FE version...), but since many of us are now running the patched version of Win ME DiskTSD.VxD, I think it's advisable to also run this matching DiskVSD.VxD just to be on the safe side. And, in any case, this is the most up-to-date existing version of DiskVSD.VxD known to work with Win 98SE (and FE).

As always, the standard disclaimer applies: It works great for me, but YMMV and I can guarantee nothing whatsoever about this patch, and about the use you make of it. By deciding to use it you fully accept that anything you do is of YOUR SOLE RESPONSIBILITY... Moreover, modding files voids the EULA, of course. You have been warned.

0

Share this post


Link to post
Share on other sites

That's a huge list indeed.

MSE 5.7 requires MS IE 6.0 SP1 or newer already installed

Seems to be working just fine with IE 5.5 SP2 as well.

0

Share this post


Link to post
Share on other sites
...

Updates:

Too many to list here... ;)

...

WHOA :o !

Who said 9x was dead? - Oh wait, it was just a small pain in the side of my head!

Talk about a mammoth fourth quarter of updates for 2007 and what a start to 2008 with a hiss and a roar!

MDGx, how do you find time to keep up all those updates? You make up the hub of 9x support!

Maybe we should call you 'Little Microsoft'? - Just friendlier!

Well, 2008 is lookin' goooood!

Long Live Windows 9x!

0

Share this post


Link to post
Share on other sites

denCorso,

patching Windows ME files to run on Windows 98 is awesome :thumbup . However to avoid confusion could you change for example patches the version numbering from 4.90.300x to 4.10.300x

The 4.10.3000 series will tell us that these files are not original Windows 98 files, since these files are in the range 4.10.1998 to 4.10.22xx

It will also prevent people from installing these files on Windows ME.

For example I would prefer it if your 4.90.0.3001 DISKVSD.VXD patched file now would be named 4.10.0.3001 keeping build subnumbers the same as the original patch.

0

Share this post


Link to post
Share on other sites

Acheron:

Your proposal makes sense. Then again, downversioning 4.90.0.xxxx to 4.10.0.xxxx is a major version change, that implies the patched version has some kind of continuity with previous 4.10.0.22xx VxDs, which is not quite the case. Sure, I know I don't need to explain to you anything about version numbers, but I provide the link to Petr's post about it for any reader who may need it. I had thought about upversioning the patches as 4.90.1.xxxx, then opted for the simpler 4.90.0.(xxxx+1) scheme because: (1) no real good solution exists for perfect versioning of patched versions, as you fully know, for you have participated in an analogous discussion regarding the versioning of LLXX patches in Enable48BitLBA, some time ago; (2) the solution reached there of not changing the version numbers doesn't appeal to me, for I feel there should be an easy way of recognizing a patched from an unpatched file, as PassingBy pointed out to me, even if at first I disagreed, because I had in mind precisely the discussion regarding the versioning of LLXX patches, and (3) my patch changes the file very little to achive its aim, so I opted for the present scheme that denotes this, and it seems safe since MS won't be issuing any more hotfixes for Win 9x/ME. In any case, the files are already released, and modifying their versioning scheme at this point would just add further confusion, by creating pairs of files differing only in their versioning scheme, since it is impossible to substitute all files everywhere after the initial release. So, I think it better to leave things as they are, at this point. But I promise you I'll muse about it for some more time and perhaps use a different versioning scheme for patched files in future releases of other patched files.

0

Share this post


Link to post
Share on other sites

Is there any way that you can make Windows Movie Maker it's own option, disabled unless Option 3 is installed?

the_guy

0

Share this post


Link to post
Share on other sites

UPDATED · 12-20-2007

0

Share this post


Link to post
Share on other sites

Hello, after to have installed the security update q941569 for the MediaPlayer 7.1, me they are shrewed that 90% of the MP3 did not sound :realmad: , mediaplayer signaled them like corrupts, replacing the file wmasf.dll (7.10.00.3081) with the previous version (7.10.00.3059) the problem disappears. :yes:

Bye.

Mcv'93

0

Share this post


Link to post
Share on other sites
Hello, after to have installed the security update q941569 for the MediaPlayer 7.1, me they are shrewed that 90% of the MP3 did not sound, mediaplayer signaled them like corrupts, replacing the file wmasf.dll (7.10.00.3081) with the previous version (7.10.00.3059) the problem disappears.

Bye.

Mcv'93

I didn't have WMP 7.1 to test. :(

Removed WMPASF.DLL from fix.

Please download and install corrected fix [480 KB]:

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

Thanks for your patience.

HTH

0

Share this post


Link to post
Share on other sites

UPDATED · 12-24-2007

Enjoy.

0

Share this post


Link to post
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

  • Recently Browsing   0 members

    No registered users viewing this page.