Jump to content

Service Pack for Windows ME

the_guy

By the_guy
in Windows 9x Member Projects

 Share

Recommended Posts

erpdude8

erpdude8

Posted
Posted (edited)

Riched32.dll

Version 5.0.2134.1 : Size = 3,856 bytes. Wrapper Dll for Richedit. Dependencies are Riched20.dll and User32.dll.

Is there a reason not to use the later versions ? It seems to me when looking at the sizes and dependencies that what Riched32 was doing could now be handled by Riched20 so that if there is a newer Riched20, there should also be a newer Riched32. Or am I wrong ?

Maybe the reason is that none of these files is available in any Service Pack or update. This file only can be bought with Windows NT 4.0 or Windows 2000 or Windows XP or Windows Server 2003.

Petr

Incidentally, about RICHED32.DLL: the version included in the unofficial RICHED9X.EXE for 9x is 5.0.1461.82. The version that eidenk and Petr were talking about above is 5.0.2134.1, which was (at least) included with Windows 2000.

However, there's another RICHED32.DLL included in MDGx's RICHEDNT.EXE (the same build number as the Win2k file, but with a later date: in Win2k it's 1999, while in RICHEDNT.EXE it's 2001). So, the fact that RICHED32.DLL build 5.0.2134.1 is included in RICHEDNT.EXE means that it is distributable, and can be used instead of the older 5.0.2134.1 in RICHED9x... right?

I've tested it (98 SE) with no problems so far. :)

I have a different opinion on using v5.0.2134.1 of riched32.dll file under 9xME systems. it has the potential of breaking some older programs and not functioning correctly under Win9xME. Versions 5.0.2134.1 and 5.0.1461.82 of the RICHED32.DLL file have VASTLY different file sizes. If either one of them is stored in the \WINDOWS\SYSTEM\ folder and some of your programs do not work correctly because of the RICHED32.DLL file, copy that DLL file onto the program's folder to see if the problems go away. if not, try using a different version of RICHED32.DLL file and store that version in the program's folder and NOT the 'WINDOWS\SYSTEM' folder.

AND I do NOT recommend using v5.4 and 5.5 of RICHED20.DLL file on a Windows machine without MS Office XP or 2003 installed [Office 97 & 2000 may not work well with riched20.dll v5.4 & higher]. stick with version 5.3.

Edited by erpdude8
Link to comment
Share on other sites

Petr

Petr

Posted
Posted
AND I do NOT recommend using v5.4 and 5.5 of RICHED20.DLL file on a Windows machine without MS Office XP or 2003 installed [Office 97 & 2000 may not work well with riched20.dll v5.4 & higher]. stick with version 5.3.

Have you found any problem with riched20.dll 5.4 and Office 97 & 2000? I have on my system with Office 2000 and no problem so far.

Metapad 3.51 cannot be used without version 5.4 on some Windows versions.

I cite form http://www.liquidninja.com/metapad/faq.html#Q18

The version 4.0 RICHED20.DLL which ships with Office XP has fixed a major bug: non-english character display problems with certain fonts (e.g., Terminal).

Maybe it is no problem in English version at all, maybe just minor.

Petr

Link to comment
Share on other sites
erpdude8

erpdude8

Posted
Posted
Any Updates on the service pack?

currently it's in beta 3 stage, Hussain. beta 3 added the missing Q318307 vmouse.vxd hotfix and fixed several installation & un-installation problems. the next upcoming beta should fix the problem when the installer prompts for the hh.exe and cdfs.vxd files. I've figured out how to fix those.

Metapad 3.51 cannot be used without version 5.4 on some Windows versions.

I cite form http://www.liquidninja.com/metapad/faq.html#Q18

The version 4.0 RICHED20.DLL which ships with Office XP has fixed a major bug: non-english character display problems with certain fonts (e.g., Terminal).

Maybe it is no problem in English version at all, maybe just minor.

Petr

I tested MetaPad v3.51 and using v5.3x of riched20.dll file on my WinME machine. worked ok. just be sure you have updated most of the font files on your computer.

Link to comment
Share on other sites
Petr

Petr

Posted
Posted

Metapad 3.51 cannot be used without version 5.4 on some Windows versions.

I cite form http://www.liquidninja.com/metapad/faq.html#Q18

The version 4.0 RICHED20.DLL which ships with Office XP has fixed a major bug: non-english character display problems with certain fonts (e.g., Terminal).

Maybe it is no problem in English version at all, maybe just minor.

Petr

I tested MetaPad v3.51 and using v5.3x of riched20.dll file on my WinME machine. worked ok. just be sure you have updated most of the font files on your computer.

The problem is on Windows with "non-english" character set, it means codepage 1250 for example. I suppose you have Windows with "english" codepage 1252.

Petr

Link to comment
Share on other sites
app103

app103

Posted
Posted

Have you considered adding the unofficial WMF exploit patch from Paolo Monti?

Since Microsoft isn't going to fix this problem for WinME users, it might be a good idea to include this. It is the only patch I have found that is for 9x too.

You'll find it at the bottom of the page here: http://www.nod32.ch/en/download/tools.php

BTW...I am glad you guys are doing this. It's nice to know that someone is gathering this stuff and putting this together for those that may want to reinstall WinME on their old pc at some point in time after Windows Update goes dark for them.

I own a P1 that is unfriendly to most versions of Windows. Seems only Win3.1 and 9x drivers are available for most of it's hardware and it has modem/sound issues with 98SE. Only WinME has been able to make this PC stable and fully usable.

Not too many people would go through the trouble & work that you guys are.

Thanks for caring about us. :wub:

Link to comment
Share on other sites
MDGx

MDGx

Posted
Posted
Have you considered adding the unofficial WMF exploit patch from Paolo Monti?

Since Microsoft isn't going to fix this problem for WinME users, it might be a good idea to include this. It is the only patch I have found that is for 9x too.

You'll find it at the bottom of the page here:

http://www.nod32.ch/en/download/tools.php

Thanks a lot for your tip.

We also have another patch [*912919.EXE] created [anonymously] and posted here at MSFN forums:

- WinME patch found here:

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

* Unofficial Windows ME WMF Graphics Rendering Engine GDI32.DLL + GDI.EXE 4.90.3002 Security Vulnerability Fix:

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

Direct download [399 KB, English]:

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

More info:

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

More info:

http://www.kb.cert.org/vuls/id/181038/

Alternative Windows 98/ME WMF Patch:

http://www.nod32.ch/en/download/tools.php

WMFPATCH11.ZIP [944 KB]:

http://d1.nod32.ch/download/wmfpatch11.zip

- Win98/98 SP1/98 SE Patch found here:

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

* Unofficial Windows 98/98 SE WMF Graphics Rendering Engine GDI32.DLL + GDI.EXE (build 4.10.2003 for Win98/98 SP1 + build 4.10.2226 for Win98 SE) Security Vulnerability Fix:

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

Direct download [393 KB, English]:

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

More info:

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

More info:

http://www.kb.cert.org/vuls/id/181038/

Alternative Windows 98/ME WMF Patch:

http://www.nod32.ch/en/download/tools.php

WMFPATCH11.ZIP [944 KB]:

http://d1.nod32.ch/download/wmfpatch11.zip

Differences:

- Paolo's patch [wmfpatch11.zip]: as far as I can tell self-registers [using REGSVR32.EXE] GDIHOOK.DLL into the registry and then runs INJECT.EXE with the -U parameter, which loads GDIHOOK.DLL into memory = temporary patch.

- Anonymous patch [*912919.EXE]: replaces GDI32.DLL + GDI.EXE with patched ones = permanent patch.

These 2 patches seem to be mutually exclusive, probably because they both try to access same GDI API functions.

Of course, there are advantages and disadvantages to either of these 2 patches.

Hope this helps.

Link to comment
Share on other sites
erpdude8

erpdude8

Posted
Posted

The unofficial WMF Patch by Paolo Monti is nice but it is a temporary solution. The unofficial KB912919 WMF fix for WinME is already included in the latest beta release of the ME service pack, so there is no need to add Monti's unofficial WMF patch onto the ME pack because the unofficial Q912919 patch made by an anonymous user is a long term fix. thanks anyway, app103.

Link to comment
Share on other sites
erpdude8

erpdude8

Posted
Posted
Sounds like this project is almost done. Any chance of a release candidate soon ???

we're getting there. INFEX.EXE will need to be modified to no longer show the Beta Testing Only dialog box in the RC & final releases.

Link to comment
Share on other sites
foothills

foothills

Posted
Posted

Sounds like this project is almost done. Any chance of a release candidate soon ???

we're getting there. INFEX.EXE will need to be modified to no longer show the Beta Testing Only dialog box in the RC & final releases.

Any idea when we might see that first RC ?? I'm really looking forward to this.

Link to comment
Share on other sites
PsycoUnc

PsycoUnc

Posted
Posted

-hmm, this project really has me reconsidering my stance on winME... :yes:

...

I was wondering if I could get some personal views/input from you guys, about why you would choose winME over, say, win98se *with* 98se2me installed?

What are the benefits of straight ME, since we (win98se+98se2me) are getting 700+ of winME's system files transplanted directly into the OS anyway?

I have the option of installing either OS; and I'm just about to start a new fresh install (was going to be 98se+98se2me again, for sure, but now I wonder...?)

...

any input/personal feelings either way would be great!

>;]

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
 Share
Go to topic listing

  • Recently Browsing   0 members

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