• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
the_guy

Service Pack for Windows ME

550 posts in this topic

I have also found a typo in the opening WinME service pack dialog box.

---------------------

UNOFFICIAL WindowsME Service Pack 2.0.2

This update is only for *ENGLISH* version of Windows98 SECOND EDITION (4.90.3000). This update is NOT from Microsoft. It is a unofficial compilation of Microsoft's update files and more.

---------------------

The next alpha or beta release of the winme SP should be corrected to say:

"This update is only for *ENGLISH* version of Windows Millennium Edition (4.90.3000). This update is NOT from Microsoft. It is a unofficial compilation of Microsoft's update files and more."

I first thought that I couldnt get the winme pack from the Rapidshare site but I did. I was lucky my dialup connection was a little faster and stable enough to get it, even though it took about an hour to fully download the pack.

0

Share this post


Link to post
Share on other sites
"This update is only for *ENGLISH* version of Windows Millennium Edition (4.90.3000). This update is NOT from Microsoft. It is a unofficial compilation of Microsoft's update files and more."

BTW, Microsoft uses often also "Microsoft Windows Millenium Edition" spelling, with one "n" only, especially in the MS Knowledgebase it is confusing.

Petr

BTW, what is the magic in MS Windows Me hotfixes that they don't require to switch file protection off?

I'm not very familar with Windows Me.

Petr

0

Share this post


Link to post
Share on other sites
BTW, what is the magic in MS Windows Me hotfixes that they don't require to switch file protection off?

For those whose files are in use and are replaced after reboot there shouldn't be any particular magic as SFP monitors only file access not size or checksum AFAIK. For the others I don't know as 1) I don't use SFP at all, 2) Inf syntax is way beyond me.

0

Share this post


Link to post
Share on other sites
BTW, Microsoft uses often also "Microsoft Windows Millenium Edition" spelling, with one "n" only, especially in the MS Knowledgebase it is confusing.

BTW, what is the magic in MS Windows Me hotfixes that they don't require to switch file protection off?

I'm not very familar with Windows Me.

Petr

The single "n" spelling is wrong [as you well know], therefore MS developers need sometimes to check their spelling. :blink:

WinME hotfixes contain CAT files which are digital signatures [MDSum or MD5Sum probably ??] of newly installed files, and because of that System Restore always updates its database accordingly.

The INF file usually contain a postsetup command to run [generic example]:

%windir%\SYSTEM\SUCATREG /D:Qxxxxxx.CAT

after respective CAT file was copied to %windir%\INF\CATALOG folder.

I have never tried to find out how CAT files are created by MS.

Hope this helps.

0

Share this post


Link to post
Share on other sites
WinME hotfixes contain CAT files which are digital signatures [MDSum or MD5Sum probably ??] of newly installed files, and because of that System Restore always updates its database accordingly.

The INF file usually contain a postsetup command to run [generic example]:

%windir%\SYSTEM\SUCATREG /D:Qxxxxxx.CAT

after respective CAT file was copied to %windir%\INF\CATALOG folder.

I have never tried to find out how CAT files are created by MS.

Hope this helps.

I supposed something like that. In fact, I never seen any use of .CAT files in Windows 98 SE, is this different in Windows Me?

I just looked at some Q310695 fix and the sequence (in the form of .SED file lines) is:

AppLaunched=QFEREG.INF

PostInstallCmd=310695UP.INF

QFEREG.INF contains lines:

[DefaultInstall]
CopyFiles = Register.cat
RunPostSetupCommands = UnprotectMe

[SourceDisksNames]
1="CAT File Source","",1

[SourceDisksFiles]
WSE22366.cat = 1

[DestinationDirs]
Register.Cat = 17,CATALOG; Windir\inf\catalog directory

[Register.Cat]
WSE22366.cat

[UnprotectMe]
;The following command will register the CAT file. Add another entry
;just like it if there are more than one, specifying the next CAT.
"%11%\SUCATREG.EXE /D:WSE22366.CAT"

So at first tha .CAT file is copied to

So at first the catalog file is copied to Windir\inf\catalog directory and then it is registered.

And after this, 310695UP.INF copies file to three locations: (unneeded lines removd)

[DefaultInstall]
CopyFiles=WMeUpd.Copy.qfe,WMeUpd.Copy.Hlp,WMeUpd.Copy.Install,WMeUpd.Copy.Options,WMeUpd.Copy.VMM32
AddReg=WMeUpd.AddReg

[DestinationDirs]
WMeUpd.Copy.Options=10,options\cabs
WMeUpd.Copy.Install=10,options\install
WMeUpd.Copy.VMM32 = 22

[WMeUpd.Copy.VMM32]
UDF.VXD,,,32

[WMeUpd.Copy.Options]
UDF.VXD,,,32

[WMeUpd.Copy.Install]
UDF.VXD,,,32

So this is the official way.

But what is the meaning of "Options" and "Install" directories?

Can we do the same in the servicepack? For all official updates/hotfixes for sure, the procedure would be:

1. To copy all .CAT files from MS fixes

2. To register them by SUCATREG

3. To copy all files as it is done at present, maybe also into "Options" and "Install" directories.

The question - how it is with unofficial, patched files? They never have correct .CAT file. I suppose this file has to be signed by Microsoft to be valid.

If it is possible to switch SFP off, copy any updated files (with no .CAT files), reboot and switch SFP on, what are these .CAT files meaningful at all?

I also suppose that could be possible to switch off the SFP by the installator, or not?

I don't have Windows ME experience but I believe there should be a way how to handle everything by the Service Pack installator.

Petr

0

Share this post


Link to post
Share on other sites
But what is the meaning of "Options" and "Install" directories?

During a fresh install of WinMe, all the setup files are copied by setup into windir/options/install. When installing a hotfix, updated files are also copied into this directory and into a sibling directory windir/options/cabs. AFAIK runing setup again should use the updated files copied in those directories instead of the original ones in the cabs.

0

Share this post


Link to post
Share on other sites
There are also some other things I will be changing:

-Updating Adaptec ASPI to 4.71a2

the_guy

Why would you do this ? Everyone says (me included) that 4.60 performs better.

0

Share this post


Link to post
Share on other sites

"This update is only for *ENGLISH* version of Windows Millennium Edition (4.90.3000). This update is NOT from Microsoft. It is a unofficial compilation of Microsoft's update files and more."

BTW, Microsoft uses often also "Microsoft Windows Millenium Edition" spelling, with one "n" only, especially in the MS Knowledgebase it is confusing.

Petr

the word "millennium" is commonly misspelled the first time, Petr. I looked at most of the MS KB articles and MS does spell it with two n's instead of one. I think they made the corrections.

0

Share this post


Link to post
Share on other sites
WinME hotfixes contain CAT files which are digital signatures [MDSum or MD5Sum probably ??] of newly installed files

Not really important but the checksum algorithm used is SHA1 apparently.

0

Share this post


Link to post
Share on other sites
There are also some other things I will be changing:

-Updating Adaptec ASPI to 4.71a2

the_guy

Why would you do this ? Everyone says (me included) that 4.60 performs better.

uh yeah, everyone except me. The Adaptec ASPI v4.71 drivers worked fine on my WinME system. I even installed them on my brother's XP laptop machine and they worked fine. and the v4.71 drivers are more

compatible with ME/XP/2k3 systems than the v4.60 drivers. go for it, the_guy.

other inclusions for the WinME pack I like to see:

-unofficial winme krnl386.exe 4.90.3001 patch [fixes a bug that microsoft forgot to patch]

-unofficial winme update.sys 4.90.3001 patch

-Metapad 3.51 [new release]

BTW - Win2000, XP & 2003 hotfixes also use .CAT files. some but not all Win98se hotfixes also contain .CAT files to digitally sign updated files.

0

Share this post


Link to post
Share on other sites

BTW, does anybody know good worldwide list of used operating systems? Here it is for Czech Republic: http://www.toplist.cz/global.html and Windows 98 has about 10% but Windows Me below 0.1%, 100 times less. Is it similar in USA or in UK?

Petr

0

Share this post


Link to post
Share on other sites

Actually in the UK there is only one user of Windows ME and that's me. (Joke) Seriously it must as low or almost as low as in the Czech Republic I believe which bears the question whether a service pack is really worth the effort. Rhelic from the US posted a stat of hits on a website in the form of a graphic the other day. Windows ME did not even appear on it.

0

Share this post


Link to post
Share on other sites

I have decided not to update the adaptec aspi to 4.71a2. It will stay as 4.6. As for Metapad, I will probably include 3.51.

As for the unofficial updates, I will add them (as an option)

the_guy

0

Share this post


Link to post
Share on other sites

good thing I had tested the ME service pack on two ME machines (one slow and one fast).

alpha 1 of the ME pack is a DUD! after I clicked on OK to install the Main hotfixes from the ME pack,

the pack crashed with a RUNDLL32 error message. and many of the updated files did NOT install.

what a bummer! It kept on crashing each time it tried to install the fixes, even when ME's SFP feature

was disabled completely [on BOTH computers].

I noticed the ME pack was created with version 5.0.2920.0000 of the Wextract. Try creating the ME pack

with version 6.0.2800.1106 of Wextract instead. The 98FE and 98SE packs were created from version

6.00.2800.1106 of Wextract.

0

Share this post


Link to post
Share on other sites

Ok, I will use that version for alpha2. I am using a 2000 computer to make the service pack.

Expect a new version this weekend.

the_guy

0

Share this post


Link to post
Share on other sites

Hey guys.

I have updated metapad.exe to 3.51. I have also added U891711. It is uploaded to filefactory.com. I will not update the ASPI layer until enough people want it. I have also added numerous updates. They are:

260710

268356

268452

277784

278368

289635

300889

301540

304082

304708

307908

309081

311430

321635

and some other updates that mdgx has posted. I have also added some other files that people have suggested. I was asked to add rpclt4.dll version 4.71.3336.0. Does ME include a newer version? I have removed the 2000 color scheme.

The download link is here.

This version is alpha 2.

the_guy

0

Share this post


Link to post
Share on other sites
I was asked to add rpclt4.dll version 4.71.3336.0. Does ME include a newer version?

You certainly mean rpcrt4.dll. WinMe version is 4.71.3335.0. Q269874 installs 4.71.3336.0.

Edited by eidenk
0

Share this post


Link to post
Share on other sites

Sorry. I will update that file in the next version.

Please test this version out as much as possible.

the_guy

0

Share this post


Link to post
Share on other sites

I have just tried the service pack in a virtual machine. It still does crash rundll32 in setupX when trying to install the main update like the previous one did.

You could also try to use Gape's new Infex O.3 in alpha3.

0

Share this post


Link to post
Share on other sites

I think I'll reduce the size of the copyfiles line if that is the problems. I hope this will be fixed in the next version.

the_guy

0

Share this post


Link to post
Share on other sites

About the OPKFIX.CAT file from Q271434. Remove it from the ME pack. that file requires ME's sytem file protection feature to be enabled in order for it to be registered and to have any effect. having that file installed [and SFP disabled] will not have any effect on ME [and will be worthless] unless SFP is on. plus most OEMs might have already have it pre-installed on many OEM versions of Windows ME (like with my HP Pavilion computer I got back in early 2001 with pre-installed Winme).

I'll try out alpha 2 as soon as I can. next alpha release should exclude the opkfix.cat file.

Edited by erpdude8
0

Share this post


Link to post
Share on other sites
I'll try out alpha 2 as soon as I can. next alpha release should exclude the opkfix.cat file.

never mind. I'm not going to download MESP alpha 2 as eidenk said the pack crashed like the alpha 1 version.

and the link to get alpha 2 of the me pack is no longer working.

the_guy should check very carefully the stuff written in ALL the .INF files included in the ME sevice pack. there could be a problem or problems found in the .INF files and he should make the necessary corrections to any of the .inf files. that could also be the reason why the ME pack keeps on crashing.

and I should also suggest to the_guy to post the next release of the me pack to at least two sites, instead of one. if he also needs more ME fixes, get them from Petr as I recently sent most of the ones I have to him.

0

Share this post


Link to post
Share on other sites

the ME fixes I sent to Petr have been sent from him to MDGx. see "New 98 FE + 98 SE + ME patches available" topic:

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

the Q271434 opkfix.cat fix is for some OEM versions of ME only and does not apply to retail versions of ME.

The retail (upgrade & full) editions of Windows ME [ones that come from the ME product boxes] dont have the problem and the fix is worthless under those editions.

0

Share this post


Link to post
Share on other sites
About the OPKFIX.CAT file from Q271434. Remove it from the ME pack. that file requires ME's sytem file protection feature to be enabled in order for it to be registered and to have any effect. having that file installed [and SFP disabled] will not have any effect on ME [and will be worthless] unless SFP is on. plus most OEMs might have already have it pre-installed on many OEM versions of Windows ME (like with my HP Pavilion computer I got back in early 2001 with pre-installed Winme).

furthermore, the opkfix.cat file actually requires WinME's SFP feature to be loaded at startup and left on. simply registering the opkfix.cat file with the SUCATREG.EXE file w/out SFP enabled wont properly register the .cat file. a good reason to leave out the Q271434 opkfix.cat fix.

a choice between the inclusion of either Q276602 pci.vxd 4.90.3004 fix or Q285882 pci.vxd 4.90.3003 fix. It's safe to include Q285882, which has no side effects. Q276602 for ME has a known problem documented in MS article 810447.

so far, the MESP has been a disappointment. it has long ways to go before an actual beta can be produced.

0

Share this post


Link to post
Share on other sites

...and i'm still waiting for alpha 3 of ME service pack. guess it will take even more time to flush out the crucial problems found in previous alpha releases.

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.