Jump to content

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


Recommended Posts

MDGx,

thanks again for the latest updates ... can you confirm that the Q933360 update replaces Q931836? It seems obvious that it does, but you normally explicitly say something if an update replaces another, and you didn't for this one. So i'm bugging you about it, sorry ;)

EDIT: oh, and both versions you've released of the Scripting engine v5.7 update doesn't work right on my test system,it days i already have the update installed when i jolly well don't. i'm going to try to repackage it i;ll let you know the results ...

is anybody else getting a message saying you already have v5.7 when you actually don't? Is it just me, have i finally lost my marbles?

EDIT2: all i did was repackage the contents and now it installs OK. MDGx, you are doing something different to me, it looks like a version check but it's not working in my case.

EDIT3: oh, and MP936782 replaces the now obsolete kb917734. Let me know if i'm wrong.

Edited by soporific
Link to comment
Share on other sites


Same here, says that 5.7 is already installed. But it does install ok manually, shows up in add/remove programs. I removed it again. Reinstalled 5.6 and then, with a fresh start, installed 5.7 again. Now I don't get the message and it installs automatic.

Link to comment
Share on other sites

256 colors windows icon on the Start button!

The icon shown on the Start button is 16x16, 16 colors in all versions of Win 9x/ME.

That's because it's taken from icon group 105, within user.exe, where there are no 256 colors icons. I thought that maybe just adding a 16x16, 256 colors icon to group 105 would be enough for the 256 colors icon be used instead of the 16 colors one... It was a long shot, but I found I was right!!!

So I decided to also include a 32X32, 256 colors icon, as well as substitute both original 16x16 and 32x32 16 colors icons with retouched icons using a lighter blue for better display.

Now, here I offer you my results, three files: USER.EXE 4.10.0.2233 with new group 105 16x16 and 32x32 icons in both 16 and 256 colors, with the new versions of the tradicional Windows icon; a proof-of-concept version of USER.EXE 4.10.0.2233 with the same icons except for the 16x16, 256 colors, which, in this case, I substituted for Dr. Hoiby's 16x16, 256 colors icon, just to show that this is the icon used in the Start button; and a new version of my USER.EXE 4.90.0.3001, for use with 98SE2ME, with the new icons and hexedited to show the windows version correctly as 4.10.2222 A in SYSDM.CPL. I've tested each of them for more than a month on my system, without any troubles, so I feel they are safe for release.

*** Warning: Of course, these modded versions of USER.EXE can only be used with the matching version of USER32.DLL!***

Download-Link: <http://rapidshare.com/files/52583808/USER256.7z.html>

Thanks to eidenk for starting the topic on how to do it. See:

<http://www.msfn.org/board/index.php?showtopic=93116>

Edited by dencorso
Link to comment
Share on other sites

256 colors windows icon on the Start button!

The icon shown on the Start button is 16x16, 16 colors in all versions of Win 9x/ME.

That's because it's taken from icon group 105, within user.exe, where there are no 256 colors icons. I thought that maybe just adding a 16x16, 256 colors icon to group 105 would be enough for the 256 colors icon be used instead of the 16 colors one... It was a long shot, but I found I was right!!!

So I decided to also include a 32X32, 256 colors icon, as well as substitute both original 16x16 and 32x32 16 colors icons with retouched icons using a lighter blue for better display.

Now, here I offer you my results, three files: USER.EXE 4.10.0.2233 with new group 105 16x16 and 32x32 icons in both 16 and 256 colors, with the new versions of the tradicional Windows icon; a proof-of-concept version of USER.EXE 4.10.0.2233 with the same icons except for the 16x16, 256 colors, which, in this case, I substituted for Dr. Hoiby's 16x16, 256 colors icon, just to show that this is the icon used in the Start button; and a new version of my USER.EXE 4.90.0.3001, for use with 98SE2ME, with the new icons and hexedited to show the windows version correctly as 4.10.2222 A in SYSDM.CPL. I've tested each of them for more than a month on my system, without any troubles, so I feel they are safe for release.

*** Warning: Of course, these modded versions of USER.EXE can only be used with the matching version of USER32.DLL!***

Download-Link: <http://rapidshare.com/files/52583808/USER256.7z.html>

Thanks to eidenk for starting the topic on how to do it. See:

<http://www.msfn.org/board/index.php?showtopic=93116>

Many thanks for the mods.

I'll add USER.EXE 4.90.3001 to 98SE2ME soon.

Keep up the good work. :thumbup

Link to comment
Share on other sites

MDGx,

thanks again for the latest updates ... can you confirm that the Q933360 update replaces Q931836?

EDIT: oh, and both versions you've released of the Scripting engine v5.7 update doesn't work right on my test system,it days i already have the update installed when i jolly well don't. i'm going to try to repackage it i;ll let you know the results ...

EDIT3: oh, and MP936782 replaces the now obsolete kb917734. Let me know if i'm wrong.

1. Indeed it does, Q933360 replaces Q931836.

Added this to the 8-27-2007 update:

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

2. I've updated MSE 5.7: please see 9-3-2007 update:

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

Hopefully it will run ok now.

See also unofficial MSE 5.6 [install it in case MSE 5.7 doesn't work]:

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

3. MP936782 does not replace MP917734, because MP917734 is for WMP71, not for WMP9.

BTW:

I've fixed MP936782, now installs also on Win98 (FE) + 98 SP1.

Windows 98 (FE) + 98 SP1 require Unofficial WMP9 already installed:

http://www.mdgx.com/wmp.htm#WMP9

WMP90_98.EXE is a repackaged WMP9 which installs on all Win98 editions.

More updates + fixes here:

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

HTH

Link to comment
Share on other sites

256 colors windows icon on the Start button! [...]
Many thanks for the mods.

I'll add USER.EXE 4.90.3001 to 98SE2ME soon.

Keep up the good work. :thumbup

You're welcome!

Thank you for your site, 98SE2ME and all your efforts that help us keep Win 9x alive and kicking! :thumbup

BTW, I sent you a PM on Jul 27th... Did it reach you?

Edited by dencorso
Link to comment
Share on other sites

[...]

- ASYCFILT.DLL 2.40.4528 > 2.40.4530

- OLEPRO32.DLL 5.0.4528 > 5.0.4530

- OLEAUT32.DLL 2.40.4522 > 2.40.4519

[...]

Thanks for testing those newer OLE files. But could you tell me why OLEAUT32.DLL was downgraded?

Hi, bristols! erpdude8 is right: oleaut32.dll 2.40.4519 *is newer* than 2.40.4522! ;)

This is just a versioning conundrum caused by M$ habit of late of releasing parallel series of updates starting at different versions for different OSes. But it can be solved, in the case of PE executables like oleaut32.dll, by looking at the file compilation dates (aka PE Timestamps, which are MUCH more stable, becuse they're tucked away in the PE header, than common file dates, which reside in the directory entry an can change easily). To see the compilation dates in readable format one must use MiTeC EXE Explorer, or PEDUMP.EXE by Matt Pietrek, a somewhat more technical console app. For the latter, try <pedump filename.dll | find /i "timedatestamp"> and consider the first value listed (the others are usually zero, anyway, because it tries to get the PE Timestamps of the .dll dependencies and fails silently... yes, they are the result of a bug...). I've compiled a list, for some versions of oleaut32.dll, so here is it:

Versions of oleaut32.dll known to work with Windows 9x/NT4/ME

==========================================

PE Timestamp 04/23/1999 16:37:36 V. 2.40.4275.1

PE Timestamp 08/31/1999 23:15:11 V. 2.40.4277.1

PE Timestamp 05/04/2001 21:34:09 V. 2.40.4517.0

PE Timestamp 03/16/2001 23:09:34 V. 2.40.4518.0

PE Timestamp 07/31/2006 18:12:40 V. 2.40.4519.0

PE Timestamp 06/20/2003 02:43:41 V. 2.40.4522.0

Of course, if one knows from which packages or updates those files came, and their relative release dates, it should not be necessary to go for the PE Timestamps, but that is not always the case. But I don't think the existence of PE Timestamps is very widely known, and this is a good exemple to show their utility. Too bad only PE executables (sometimes referred to as Win 32 executables), among all possible types of executables present in the Windows OSes carry their compilation date inside. Then again, they are becoming more and more the standard for .exe, .dll, .ocx and .tlb, and that is good news!

In a nutshell, changing oleaut32.dll from v. 2.40.4522.0 to v. 2.40.4519.0, despite all the apearances, *is an upgrade*, not a downgrade! HTH

<Additional musings... It seems there always IS something more to be said :) >

Relevant files found in VB6-KB924053-x86-ENU.exe, having internal name oleaut32.dll

===========================================================

PE Timestamp 07/11/2006 07:19:34 V. 2.40.4531.0 Size: 631,053 bytes Name: oa2k.dll

PE Timestamp 07/31/2006 18:12:40 V. 2.40.4519.0 Size: 626,960 bytes Name: oant4.dll

PE Timestamp 07/31/2006 18:43:21 V. 2.40.4519.0 Size: 626,960 bytes Name: oant4ts.dll

oa2k.dll was tested by erpdude8 and by MDGx, and both found it's unsuitable for use with Win 9x/ME. So I didn't test it myself but I mention it here because its version number indicates it's presently the most up-to-date version of oleaut32 in the series 4522 .... 4531, that M$ intended for Win 2k. Of these only 4522 does work with Win 9x/NT4/ME.

Now, oant4.dll and oant4ts.dll, despite having the same version number and the same size, are a long way from being the same file, because they exhibit 27,906 differences in a direct binary compare. They are both intended by M$ for NT4 systems, but oant4ts is for NT4 *Terminal Server*, which, in IMHO, is much more different from Win 9x/ME than plain-vanilla NT4, so I decided the right file to pick would be oant4.dll, which I've been using, renamed to oleaut32.dll, in my system, for some time now, without any problems. I do believe erpdude8 reasoned along these same lines to select which of the 4519 files that he tested and found it works OK. I've checked the oleaut32.dll that is inside the Unofficial 98fe SP v2.2.0, he has just released. It is the same oant4.dll that I'm currently using, from its PE Timestamp.

Now, the 4519 files are the latest in the series 4275....4518, which M$ had stopped updating for some time, but since they were released in the same update pack as 4531 I took it to mean, to me at least, that they are equivalent from the hotfix point-of-view, both being the most up-to-date at the moment, the main difference being that 4519 lacks the Win 2k specific features present in 4531, most possibly *the features* that render 4531 unusable with Win 9x/ME. Of course, this last comment is just my opinion, so YMMV.

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
  • Recently Browsing   0 members

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