Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Service Pack for Windows ME

* * * * * 1 votes

  • Please log in to reply
549 replies to this topic

#126
the_guy

the_guy

    Creator of the Windows ME Service Pack

  • Member
  • PipPipPipPipPip
  • 914 posts
  • Joined 15-July 05
  • OS:ME
  • Country: Country Flag
Thanks for the report.

New version! This is still Beta 2, but it is version 2 of the beta.

Hosted on mytempdir, id 498247.

Fixed all bugs reported.

the_guy
Creator of the Windows ME Service Pack.


How to remove advertisement from MSFN

#127
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04

Thanks for the report.

New version! This is still Beta 2, but it is version 2 of the beta.

Hosted on mytempdir, id 498247.

Fixed all bugs reported.

the_guy


I'll hold off til beta 3. the spupdate.inf file needs to be modified some more.

I saw the following in the spupdate.inf file about the Movie Maker desktop shortcut info-
----
setup.ini, progman.groups,, "Desktop="%49758%""
setup.ini, Desktop,, """Windows Movie Maker"", """"""%24%\progra~1\Moviem~1\moviemk.exe"""""",,,,,,""This application allows you to record, organize, edit and share Windows Media on your computer, via e-mail or the Internet."
----

Please add "49758=DestA,5" in the [CustomDestinationSection] section of the spupdate.inf file. Got this string from the 287564up.inf file. Also create the [DestA] section that has the following:

----
[DestA]
HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders","Desktop",,"%25%\%DESK_TOP%"
----
And add DESK_TOP = "Desktop" in the [Strings] section. Adding all these things should make the ME pack correctly create the Windows Movie Maker shortcut on the Start Menu and on the Windows ME desktop.

Also can you add newer Root Certificates Update? Download it here:
http://download.wind...en/rootsupd.exe
File size is now 228kb or 229kb.

Edited by erpdude8, 08 March 2006 - 09:02 AM.


#128
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04

I'll hold off til beta 3. the spupdate.inf file needs to be modified some more.


scratch that. I did test V2 of ME SP v2.02 beta 2. I was right. The spupdate.inf file needs more editing AND proofreading.

The "RunPreCommands.Section" mentioned in the spupdate.inf file does not exist. actually it was given a different name called [RunPreSetupCommands.Section] which should have launched NIRCMD but the ME pack did not execute NIRCMD because it can not find "RunPreCommands.Section". Change [RunPreSetupCommands.Section]
to [RunPreCommands.Section]. Otherwise, without the ME pack executing NIRMCD to shut down SFP, SFP will start restoring many of the updated system files from the ME pack with the original ones.

In the [Del.Windows] section the "wininet.log" file should be listed as "wininit.log" file. change "wininet.log" to "wininit.log"

The section that mentions the SPUPD_2.INF file; it should be named to SPUPD2-INF file. Otherwise, an error message will pop up saying it can not find the SPUPD_2.INF file during installation because that file was given a slightly different name.

The "DestA" section should be the following:
[DestA]
HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders","Desktop",,"%25%\Desktop"

And the ME pack prompted me for the CDFS.VXD and HH.EXE files. I clicked on OK and it continued as normal.

Hopefully these corrections (and the suggestions about the Windows Movie Maker desktop shortcut mentioned in my last post) AND the newer Rootsupd.exe file will be included in the next beta release.

Edited by erpdude8, 12 March 2006 - 11:25 AM.


#129
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04
And in the last few days I've found even more problems with the ME service pack.

good thing I took the liberty AND the time to edit and proofread most of the INF files inside the ME pack.

The UNOFFUPD.INF file needs some more tweaking. What I did was add the "SmartReboot = N" string in the [DefaultInstall] section and changed the "wininet.log" string in the [Del.Machine] section to "wininit.log". Without the SmartReboot = N string, the ME pack will display the Restart Computer dialog box before the ME service pack is almost finished installing the updated files.

Un-installing the ME service pack did not work as expected as many of the system files were not restored to their original ME versions. I gave the SPUNINST.INF file a MAJOR makeover, changing most of the files that end in ,,,32 to either ,,,1028 or ,,,4. that will make WinME setup overwrite the updated files with the older & original ones from the ME setup files. I also removed the [Copy.Install] and [Copy.Options] sections from the SPUNINST.INF file because copying the original system files to those sections is UNnecessary (and wastes some disk space). Now the SPUNINST.INF file is a little smaller.
Also removed the "SmartReboot = N" string in the SPUNINST.INF file so that the Restart Computer dialog box WILL show up after un-installing the ME service pack. I removed references to some system files in the SPUNINST.INF file because some of them do NOT exist in the original WinME setup files (such as hhsetup.dll, unicows.dll and vmm.vxd < those files are not found in the WinME setup files).

About these lines in the SPUNINST.INF file:
---
"RunDll32.exe %11%\AdvPack.Dll,LaunchINFSection %17%\Preserve.inf,DefaultUninstall"
"RunDll32.exe %11%\AdvPack.Dll,LaunchINFSection %17%\Wuinfo.inf,DefaultUninstall"
"RunDll32.exe %11%\AdvPack.Dll,LaunchINFSection %17%\Tweaks.inf,DefaultUninstall"
"RunDll32.exe %11%\AdvPack.Dll,LaunchINFSection %17%\Qfe.inf,DefaultUninstall"
---
I transferred them from the [RunPostCommands.Section] to the [RunPreCommands.Section]. It was like that in the spuninst.inf file of Gape's Win98se service pack. These commands needed to be executed before those 4 INF files get deleted. When these lines were placed in [RunPostCommands.Section], they dont execute and I get error messages saying it can not find those INF files, probably because they were deleted before the ME pack got a chance to execute them. So those lines should really belong in the [RunPreCommands.Section].

I've also modified SPUPDATE.INF file to make a copy of the NIRCMD.EXE file and store it into the WINDOWS\INF folder so that we need it later when we un-install the ME service pack. Without copying the NIRCMD file, the NIRCMD commands in the SPUNINST.INF file will not work because it can not find the NIRCMD file. I also modified the the SPUNINST.INF file so that it will execute the NIRCMD file found in the Windows\Inf folder.

I will send the modified INF files to the_guy later this week. what would he do without me!

Edited by erpdude8, 15 March 2006 - 08:23 AM.


#130
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04
also the Q318307 Vmouse.vxd file ver. 4.90.3003 should also be added onto the ME service pack. The Q318307 Vmouse.vxd hotfixes for Win98 & ME were packaged inside Microsoft's Intellipoint Mouse v4.12 software, which I have installed on my WinME computer.

#131
the_guy

the_guy

    Creator of the Windows ME Service Pack

  • Member
  • PipPipPipPipPip
  • 914 posts
  • Joined 15-July 05
  • OS:ME
  • Country: Country Flag
All of those errors are fixed in beta 3, which should be released in a few days. Vmouse.vxd is also added.

Also, I noticed that MDGx has an unofficial 314147 update for ME posted on his site.

the_guy
Creator of the Windows ME Service Pack.

#132
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04

All of those errors are fixed in beta 3, which should be released in a few days. Vmouse.vxd is also added.

Also, I noticed that MDGx has an unofficial 314147 update for ME posted on his site.

the_guy


wonderful. in beta 4 or release candidate 1 we should add the un-install confirmation dialog box to the ME service pack. i've figured out how to do it.

#133
the_guy

the_guy

    Creator of the Windows ME Service Pack

  • Member
  • PipPipPipPipPip
  • 914 posts
  • Joined 15-July 05
  • OS:ME
  • Country: Country Flag
I think I've found that out as well. If it's the same as WMP 6.4, I have it in already. It might be wrong, though. Please post your method as well.

the_guy
Creator of the Windows ME Service Pack.

#134
foothills

foothills

    Newbie

  • Member
  • 12 posts
  • Joined 25-January 05
Are you guys still working on this?? This will be a huge time saver when its done, since updating via windows update requires hours of downloading, installing, and rebooting over and over again, even with a DSL connection.

#135
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04

Are you guys still working on this?? This will be a huge time saver when its done, since updating via windows update requires hours of downloading, installing, and rebooting over and over again, even with a DSL connection.


oh yes, foothills. I have a WinME machine and I have tested beta 2-v2 of the ME service pack. beta 3 is almost ready.

I think I've found that out as well. If it's the same as WMP 6.4, I have it in already. It might be wrong, though. Please post your method as well.

the_guy


maybe after you release beta 3 of the ME service pack, whenever it is ready. should be more stable than previous betas.

#136
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04

just wondering, is the FP4AWEC.DLL file included in the ME service pack? The Q282132 security patch for WinME has 4.0.2.4715 of that file and is installed in the 'Program Files\Common Files\Microsoft Shared\Web Server Extensions\40\bin' folder. Fp4awec.dll file is also included in the Web Folders KB892211 update.

Those who have MS Frontpage 2000 installed can install the FP2000 version of the Q282132 patch instead of the Windows ME version or they can install the KB892211 update. I've found a FP2k hotfix mentioning a newer version of the Fp4awec.dll file which has version 4.0.2.9010. I will request this Frontpage 2000 hotfix from MS that has the newer build of the fp4awec.dll file.


follow up on this: I recently have obtained the FP2K KB843616 hotfix that updates the FP4AWEC.DLL file to version 4.0.2.9010. Let me know if you want to include it into the ME service pack.

#137
the_guy

the_guy

    Creator of the Windows ME Service Pack

  • Member
  • PipPipPipPipPip
  • 914 posts
  • Joined 15-July 05
  • OS:ME
  • Country: Country Flag
I wouldn't mind including that file.

Once I get that file, the SP should be released about a day after.

the_guy
Creator of the Windows ME Service Pack.

#138
foothills

foothills

    Newbie

  • Member
  • 12 posts
  • Joined 25-January 05
Any word on a new release??

#139
the_guy

the_guy

    Creator of the Windows ME Service Pack

  • Member
  • PipPipPipPipPip
  • 914 posts
  • Joined 15-July 05
  • OS:ME
  • Country: Country Flag
Beta 3 now available.

The link is on mytempdir, file id 567134

Changes in beta 3:
-fixed inf files

Please try and see if it works.

the_guy
Creator of the Windows ME Service Pack.

#140
eidenk

eidenk

    MSFN Addict

  • Member
  • PipPipPipPipPipPipPip
  • 1,527 posts
  • Joined 28-March 05
I have tried the main update in a virtual machine.

I got two errors : Can't find CDFS.VXD and can't find HH.EXE. I just had to click on OK both times and it carried on.

Then for quite a long time a DOS windows remains on screen with file not found written in it but the install process carried on.

And I have been able to reboot. It's getting good.

Edited by eidenk, 03 April 2006 - 11:35 PM.

Asus A8V Deluxe - Athlon 64 FX-55 2.6Ghz - 1GB DDRAM 400 - Windows ME (IE 5.5 SP2 Shell) + KernelEx 4.0 and Revolutions Pack 10

#141
jimmsta

jimmsta

    computer janitor

  • Member
  • PipPipPip
  • 388 posts
  • Joined 04-May 05
  • OS:Windows 8.1 x64
  • Country: Country Flag
I'll test it out today... I'm doing an OS drop on a buggy system, to try and figure out if the hardware is ok (ACPI problems and Soundcard issues - system came in with German Windows Me). Hope this works... if not, I'll just ghost my bare Me Image back on and try again.

Edited by jimmsta, 04 April 2006 - 11:03 AM.

Creator and Maintainer of BootZilla.org

#142
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04

I'll test it out today... I'm doing an OS drop on a buggy system, to try and figure out if the hardware is ok (ACPI problems and Soundcard issues - system came in with German Windows Me). Hope this works... if not, I'll just ghost my bare Me Image back on and try again.


unofficial ME service pack is currently for English edition of ME, not for German edition. do not use if you dont have the english version of ME.

#143
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04

I have tried the main update in a virtual machine.

I got two errors : Can't find CDFS.VXD and can't find HH.EXE. I just had to click on OK both times and it carried on.

Then for quite a long time a DOS windows remains on screen with file not found written in it but the install process carried on.

And I have been able to reboot. It's getting good.


I had that installation bug since beta 2 and I've figured out why it's been prompting those two CDFS.VXD and HH.EXE files. A buggy version of INFEX.EXE included in the ME Service Pack didnt quite run the "right" command.

I viewed version 0.2.0.0 of INFEX.EXE in Wordpad from the 98 SE service pack and it was supposed to run
"rundll32.exe advpack.dll,LaunchINFSection, DefaultInstall" or something like that. The version of INFEX.EXE file included in ME service pack is version 0.3.0.0 and when I viewed this version in Wordpad, it does NOT mention DefaultInstall and I saw the line that says "Rundll32.exe Advpack.dll,LaunchINFSectionEx" The LaunchINFSectionEx command is INCORRECT. It should be LaunchINFSection [NOT LaunchINFSectionEx] with DefaultInstall. So this means that 0.2.0.0 of INFEX.EXE installs files correctly while 0.3.0.0 does not.

So it looks like the INFEX.EXE file from the ME service pack needs to be revised OR we can just include 0.2.0.0 of INFEX.EXE file (from the 98SE service pack) which does install files correctly.

I'll give the_guy the newer build of the fp4awec.dll file [4.0.2.9010] after Easter. I'll be busy next week.

#144
jimmsta

jimmsta

    computer janitor

  • Member
  • PipPipPip
  • 388 posts
  • Joined 04-May 05
  • OS:Windows 8.1 x64
  • Country: Country Flag


I'll test it out today... I'm doing an OS drop on a buggy system, to try and figure out if the hardware is ok (ACPI problems and Soundcard issues - system came in with German Windows Me). Hope this works... if not, I'll just ghost my bare Me Image back on and try again.


unofficial ME service pack is currently for English edition of ME, not for German edition. do not use if you dont have the english version of ME.


Sorry, I should have been a bit more... descriptive. I was doing something that we call a drop - a ghost image with English Windows Me. It worked fine with the service pack - in a VMWare machine ;) ... The customer's machine that I mentioned... well, it didn't get the service pack, because I figured it wasn't compatible at all... except I think I did something a bit more :wacko:

I did an install on top of the old version of Me, which was German, with an English version. The system wouldn't fully install... So, I ended up taking the backed up registry from before I tried installing it on top, and dropped that into place. I also grabbed a copy of the German Explorer.exe file, and the system worked fine....albeit, very strange -- a system with both English and German text labels, working perfectly with applications and such. I won that battle. ;)
Creator and Maintainer of BootZilla.org

#145
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04


I have tried the main update in a virtual machine.

I got two errors : Can't find CDFS.VXD and can't find HH.EXE. I just had to click on OK both times and it carried on.

Then for quite a long time a DOS windows remains on screen with file not found written in it but the install process carried on.

And I have been able to reboot. It's getting good.


I had that installation bug since beta 2 and I've figured out why it's been prompting those two CDFS.VXD and HH.EXE files. A buggy version of INFEX.EXE included in the ME Service Pack didnt quite run the "right" command.

I viewed version 0.2.0.0 of INFEX.EXE in Wordpad from the 98 SE service pack and it was supposed to run
"rundll32.exe advpack.dll,LaunchINFSection, DefaultInstall" or something like that. The version of INFEX.EXE file included in ME service pack is version 0.3.0.0 and when I viewed this version in Wordpad, it does NOT mention DefaultInstall and I saw the line that says "Rundll32.exe Advpack.dll,LaunchINFSectionEx" The LaunchINFSectionEx command is INCORRECT. It should be LaunchINFSection [NOT LaunchINFSectionEx] with DefaultInstall. So this means that 0.2.0.0 of INFEX.EXE installs files correctly while 0.3.0.0 does not.

So it looks like the INFEX.EXE file from the ME service pack needs to be revised OR we can just include 0.2.0.0 of INFEX.EXE file (from the 98SE service pack) which does install files correctly.

I'll give the_guy the newer build of the fp4awec.dll file [4.0.2.9010] after Easter. I'll be busy next week.



tried replacing INFEX.EXE file with earlier version. no change. ME service pack still prompted for HH.EXE and CDFS.VXD files. perhaps these two files need to be included in BOTH SP2.CAB and SUPP.CAB files. might also want to move the [COPY.Install] section from the SPUPDATE.INF file and put it into the SPUPD-2.INF file. I did that. Solving the problem of the ME pack prompting for some files is harder than I thought.

let's try looking at the SPUPDATE.INF file of the 98se service pack to see how files are installed. maybe we can get a clue of how the files are installed without prompting for any files.

The "File Not Found" message is caused by the "del %winbootdir%\wininit.log" command in the RUNPOST.BAT file. That command should be removed as it is unnecessary and the wininit.log file will be deleted upon restart. Then the Runpost.bat file will run normally as before.

Edited by erpdude8, 09 April 2006 - 08:05 PM.


#146
foothills

foothills

    Newbie

  • Member
  • 12 posts
  • Joined 25-January 05
Any chance of a new release with cdfs.vxd and hh.exe fixed?? It appears that this project is getting close to completion :)

#147
Petr

Petr

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 981 posts
  • Joined 15-April 05
  • OS:98SE
  • Country: Country Flag
Hello MDGx,

do you remember what applications have problems with riched20.dll 5.40 (from Office XP) or 5.50 (from Office 2003)?

Petr

Newest RICHED20.DLL that works with 9x/ME I'm aware of is 5.31.23.1224 from Win2003 SP1:
http://www.mdgx.com/ws3toy.htm#SP1
Available as unofficial RTF (RichEdit) fix for 95/98/ME:
http://www.mdgx.com/add.htm#RTF
File:
http://www.mdgx.com/files/RICHED9X.EXE
RICHED9X.EXE installs newest versions of:

RICHED.DLL
RICHED20.DLL
RICHED32.DLL
USP10.DLL
RICHTX32.OCX



#148
erpdude8

erpdude8

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,141 posts
  • Joined 24-November 04

Any chance of a new release with cdfs.vxd and hh.exe fixed?? It appears that this project is getting close to completion :)


foothills,

there is NO need for newer versions of the cdfs.vxd and hh.exe files. those files are NOT the ones that actually cause the problem. I've found a way to fix the problem with the installer prompting those two files.
I've decided to remove the [Copy.Install] and [Copy.Options] sections from the SPUPDATE.INF file and put them in separate INF files. I put [Copy.Install] in SPUPD-3.INF and [Copy.Options] in SPUPD-4.INF. THAT seem get rid of the problem because the setupx.dll & advpack.dll installers keep switching back and forth between copying some files to the \WINDOWS\OPTIONS\CABS\ and \WINDOWS\OPTIONS\INSTALL\ folders and may cause confusion. they do not copy all files first to \windows\options\cabs\ folder and then copy all files to \windows\options\install\ folder. guess there were too many files for the installers to remember since the [Copy.Install] and [Copy.Options] sections mention so many files.

I've sent the new INF files and the revised spupdate.inf and spuninst.inf files to the_guy a few days ago.
maybe the next release should be a release candidate instead of beta 4.

btw - Happy easter to all!

Edited by erpdude8, 17 April 2006 - 05:32 AM.


#149
MDGx

MDGx

    98SE2ME + 98MP10

  • Super Moderator
  • 2,678 posts
  • Joined 22-November 04
  • OS:none specified
  • Country: Country Flag

Hello MDGx,

do you remember what applications have problems with riched20.dll 5.40 (from Office XP) or 5.50 (from Office 2003)?

Petr

Newest RICHED20.DLL that works with 9x/ME I'm aware of is 5.31.23.1224 from Win2003 SP1:
http://www.mdgx.com/ws3toy.htm#SP1
Available as unofficial RTF (RichEdit) fix for 95/98/ME:
http://www.mdgx.com/add.htm#RTF
File:
http://www.mdgx.com/files/RICHED9X.EXE
RICHED9X.EXE installs newest versions of:

RICHED.DLL
RICHED20.DLL
RICHED32.DLL
USP10.DLL
RICHTX32.OCX

Sorry, I have no experience using riched20.dll 5.40 or 5.50 . I don't have Office XP/2003 CDs.
IMO:
But since those newer versions were released with MS Office packages, they probably have extra code for Office applications.

Win2003 SP1 [which installs riched20.dll 5.31] was released March 30 2005.
MS Office 2003 was released [probably] a few months before that.

Hope this helps.

#150
bristols

bristols

    Advanced Member

  • Member
  • PipPipPip
  • 451 posts
  • Joined 24-September 05
  • OS:none specified
  • Country: Country Flag

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

Edited by bristols, 17 April 2006 - 06:53 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users