Sorry about misunderstanding your question.

The USER*.* files don't have anything to do IMO with DOS mode exit/restart.
What you describe are 2 different DOS modes, which you can go to in different ways.
1. DOS box/window/session is a virtual DOS mode emulated within Windows [a.k.a. Virtual Machine (VM)].
From that [either windowed or even full screen, don't let that fool you] you can type EXIT and press Enter to return to the Windows UI [User Interface].
2. Native/pure/true/real MS-DOS mode is outside Windows UI, and can be achieved 2 ways:
A. Either boot directly to real MS-DOS [with no way to return to Windows UI, unless you type WIN and hit Enter, which loads the UI] by tweaking your MSDOS.SYS:
http://www.mdgx.com/msdos.htm
and CONFIG.SYS:
http://www.mdgx.com/mem7.htm#7
or
B. Go to native MS-DOS [but be able to return to Windows UI by typing EXIT or WIN and pressing Enter] by running the MS-DOS Prompt shortcut created by Windows when you 1st installed your OS.

More info:
http://www.mdgx.com/last3.htm#DOS2DOS
http://www.mdgx.com/lastweek.htm#MSDOSPROMPT
http://www.mdgx.com/newtip1.htm#DOS

Therefore, the inability of returning to Windows UI by typing EXIT and pressing Enter is not related [to my knowledge] to replacing system files with WinME versions by 98SE2ME.
That is because I'm usually very careful not to disable Win98 SE features, especially the ability of accessing DOS modes.
DOS shortcut properties can be changed by modifying a PIF file settings [the "Exit To DOS.PIF" shortcut for example] or whatever custom PIF [Program Information File] you might be using, or a PIF created/modified by some software/game you were installing/running [please see 3 URLs above for more details].

When you access native DOS under Windows [native DOS, but with the WIN module loaded in memory as TSR, you can see by running MEM/C/P], Windows creates temporary *.WOS files [backs up config.sys + autoexec.bat] and modifies original files to add this line:
DOS=SINGLE
This line won't allow Windows UI to (re)load/(re)start until you remove it from your config.sys and then reboot. More details at URLs above.

There are other ways of disabling the return to Windows UI after going to DOS mode [similar to running "Exit To DOS.PIF"]. Example:
modding WIN.COM as described here [you can download as 98ATXFIX.ZIP linked at URL below]:
http://www.mdgx.com/98-4.htm#98ATX
and/or loading NOOFF.COM in memory [as TSR = Terminate and Stay Resident] from autoexec.bat or from config.sys or from DOS prompt.
NOOFF.COM is also linked at URL above.

VPOWERD.VXD cannot be replaced with WinME version, because does not work at all.
The explanation in the BUG + FIX issue you have read, refers to vpowerd.vxd, only to explain better the dependencies among system files.

The USER*.* files from WinME to my knowledge [I have not compared them byte by byte nor decompiled them, and there is no documentation at MS web site that would explain such differences] correct a few system bugs [like mouse random moves, lockups, GPFs, IPFs etc], enhance performance by using better memory access, and probably streamline some UI features. Of course, all this is speculation, found by searching MSKB for USER.EXE + USER32.DLL bug fixes:
http://support.microsoft.com/search/?qu=us....dll+windows+98

I've been using the WinME USER*.* files on my 98SE computers for > 5 years, and never had any errors that I could have linked back to them.
I've also installed 98SE2ME on some friends' computers, with similar effects.

I see no need to associate the USER*.* files strictly with option 3, because the file dependencies resolve ok with the WinME system files replaced by option 2, and these 2 files bring a large enough benefit to the OS in my opinion, in order to keep them as part of option 2.

Another thing you may want to try, is fix or disable APM/ACPI/BIOS/CMOS/USB/monitor/hard disk power management features, which are the more likely culprit for DOS lockup and/or Windows shutdown/power off errors:
http://www.mdgx.com/98-5.htm#FWUE

In conclusion, to my knowledge 98SE2ME does not change DOS access abilities, but if you determine otherwise after detailed research, please let me know and I'll try to fix it.

A good place to start is to restore 98SE system files 1 by 1 from the backups created by 98SE2ME option 2 in %windir%\SYSTEM.9ME [usually C:\WINDOWS\SYSTEM.9ME].
Reboot each time after restoring a file.
Please notice any difference in behaviour, and if you do, please let me know.

Hope this helps

Sorry, I have not kept old 98SE2ME versions to compare, and besides, all the changes I've made in the past ~ 8 months or so are too numerous and too complex to try to go back.
But if you kept the old 12-14-2005 98SE2ME.EXE edition, please send it to me attached to email [please click the blue E-mail link]:
http://www.mdgx.com/form.htm
and I'll see what I can do.

As I said before, I don't think 98SE2ME is related to shudown/power off errors, those are Win98 SE errors that are quite well known, and there are a lot of things that can be done to fix them.
More info:
http://www.mdgx.com/98-5.htm#FWUE
APM/ACPI/BIOS power saving issues are usually involved.

Another good idea is to restore 98SE system files 1 by 1 from the backups created by 98SE2ME option 2 in %windir%\SYSTEM.9ME [usually C:\WINDOWS\SYSTEM.9ME].
Reboot each time after restoring a file.
Please notice any difference in behaviour, and if you do, please let me know.

Hope this helps

@MDGx:

I have attached a list of file changes between 12-14-2005 and now.

Just thought I'd help you out a little bit.

the_guy

the_guy:

Million thanks for taking the time to do this.
That was the easy part though, to enumerate the added/removed/changed files.
But the hard part [I was thinking of] is to figure out all the INF + REG changes since Dec 2005.
Although I just reviewed all the INF files [and REG entries], and didn't find anything that would make a difference.

In a nutshell [thank you again]:

GDI.EXE/GDI32.DLL->912919
COMMDLG.DLL->WIN_19.CAB
INTERNET GAMES
MPLAYER.EXE->98SE
DEVMGR32.DLL->98SE
MPREXE.EXE->98SE
START MENU
TASKMGR->IE6SP1
DZIP32.DLL/DUNZIP32.DLL/ZIPFLDR.DLL->329048
TELNET.EXE->MS99-033
WEBVW.DLL->900725
MOVIEMK.EXE->262806
GDI.EXE/GDI32.DLL->918547
CLIPBOOK.EXE/CLIPSRV.EXE->ME

The only files I can think of that could make a difference here might be the GDI*.* files [although they shouldn't].
The rest don't matter.
____________________________

PROBLEMCHYLD:

Please try to use the GDI*.* files from 98SE2ME 12-14-2005 on your syster's computer, see if they make any difference.

Thanks.

MDGX, remember my old problem left unsolved?

This week I reinstalled Windows. After installing 98SE2ME, the problem was back. This time I investigated the problem. It's not related to network, but to windows disk cache.
When I copy files from network (shared on Windows XP, one switch between computers) tranfer rate drops when the disk cache is full.
See the atached images:
First image = Disk cache set to 512MB - network tranfer and disk write speed drops
Second image = Disk cache set to 64MB - network transfer and disk write speed remains high

Replacing VCACHE.VXD v4.90.3000 with default Win98 version solved the problem.

ived notice similar things happening.i guess if a app(program want to check for a pickilar user exe version and its different u might have problems.i guess its impossible to try every program on any of these projects =rp5 98se2me etc.etc.

-re: 98se2me install issues...
...
-ok, I re-dl'd 98se2me, and it *is* different than the previous dl (version 5.9 vs. 5.7, and diff. file contents)... weird, first time that's happened to me...
...
running it still had some same problems: same junk (repeated) left in autoexec.bat, and it did not backup/replace my old/current files (such as GDI* ver: 4.90.0.3002 to the new (in 9!M): 4.90.0.3003)... but this time it didn't create/leave any root dirs ("%WINDIR%", "9S2M")...
...
it's most likely related to the new(ish) version-checking code in 98se2me, since none of this stuff ever happened before that new code (these are the 1st runs of 98se2me that I've done which included that new code). If you'll point me to that newish code, I'll try debugging...
...
{ps: same/similar stuff happened when I tried it on a small, old, minimal "Control" partition of win98se (fully updated to 02-2006, incl. 98se2me of that period)...}
...
{pps: I never do/use "98-lite" or any other "special" mods/tweaks to my OS's, just the std. sesp2/98se2me plus your updates/patches... I do use XOSL (boot loader) & BIOS settings to switch between 3 HD's, which sometimes does seem to change the drive letters during boot, between DOS and windows GUI, but I doubt that should make any difference to the new(ish) 98se2me code...?... -any chance the new code could be thrown by unexpected values in %windir% or unexpected version numbers? -again, if you'll point me to that newish code, I'll try debugging...}

-re: 98se2me install issues...
...
>update: taking a peek at some of your .bat code, I noticed u use the existance of %windir% variable and file(s) named NUL (like in \windows, etc) as branching conditions... I set %windir% and %winbootdir% manually as the first lines in my AUTOEXEC.BAT, and I sometimes have files named NUL in \windows, etc... ?... any chance that's a problem? (and if it is, ya really should use more "unique" branching methods when coding, such as relatively random, unique variable/file names...)
?
...
...
>> update2: modifying/correcting according to (above), I have been able to get (some) more functionality out of 98se2me, hinting that that is/may be the prob... I'll finish testing this properly, shortly...
...
...
>>> update3: yup, confirmed (mal)functioning of 98se2me's USB (Option #8), which was exhibiting the same malfunctions, corrected when I remarked-out my windir lines in autoexec... safe to assume same will apply to #2 (since it used similar branching methods/code)... again, I'll verify soon, but safe to say this needs to be modified in 98se2me branching code...
...
...
>>>> UPDATE4 (final): yup, confirmed w/Option#2, now... a programming note: never assume anything; must use unique (nearly random) variables/filenames, nothing that a user might possibly use/set/modify himself... {I didn't follow thru the "windir" thing to find out *why* you use that as a branching condition, but it needs changing... along with the "NUL" filename branching (when doing ATTRIB stuff, etc; much too common of a filename) }

-grrr!
...
this latest (8-1-06) 98se2me also BROKE my usb thumbdrive driver (on two different test partitions), and uninstalling #8 did NOT fix it!
-it keeps on AUTOMATICALLY installing it as "Unknown Device", no options, no errors, just automatically finds a listing of "Unknown Device", installs it as such, and immediately Disables it! Nothing I've tried has corrected this... -the usual way, manually pointing the Driver Updater to the dl'd Lexar driver folder just says that no driver can be found in this folder for this device, when in the past it did NOT say that, it found the driver fine and then installed it... and it worked perfectly before this, w/older 98se2me...
...
I really believe you should include a link to older, "safe" versions of 98se2me in the main dl post...
(there are some other relatively recent changes to 98se2me I've not been thrilled about, as well... I believe in at least one case, you removed one of the file replacements, because some IE6 update installed a newer one, but what about those *many* of us who refuse to suffer w/IE6? That ticked me off... perhaps that particular case has been rectified, it was a little while ago...)
...
I'm now looking at a full reinstall just to get my -bleepin- thumbdrive to work again... (I new I should've made yet another full OS backup before trying this latest 98se2me, but ran out of extra HD space... and my older backups would need so many changes/tweaks/updates that it wouldn't be worth it... sigh)

You... do realize that this is an experimental patch, right? Problems like this are possibly going to occur.

Also, what options did you use? I see you used Option 8, but what came first?

I'm not going to lie, I've had problems when updating old installs of 98SE2Me to newer versions, and have had to re-image my virtual machines.

Its the New Gdi.exe & Gdi32.dll 4.10.2227 causing trouble.
Before i installed it everything was working fine.After installation I wasn't able to install 98SE2ME at all.
Even after i replace it with the original files things are still broken.Power Management/98SE2ME can't
install it.It seems like the newer they get the worse they are.I will be using my older version 98SE2ME 4-20-06
where Power management and everything else works.
Keep up the good work though. And i always test Unofficial patches on a clean install.

-yes, and as I usually state, I'm still of course VERY appreciative of all the EXCELLENT work done on these projects, by MDGx, Gape, and all of you very knowledgeable and helpful people...
-it's my own dam fault, just haven't had the time to catch up on all the backups lately (WAAY too busy to catch up on ANYTHING, lately), so believe me, when this stuff happens I'm yelling at myself 10 times as much as I do in the posts...
...
-re: options...
I used #2 first, then the "shell"-stuff (#3 or #4, forget), then #8...
...
-and honestly, I thought I already had pretty much all the updated USB files in place; -any chance there's some (improper) registry stuff done in 98se2me in #8? The thumbdrive was already installed before, shouldn't have had to re-install it at all, much less get the "Unknown Device" AS the installed device! Why can't it recognize the thumbdrive, even when directly pointed to the dl'd driver files, when it was already easily perfectly installed WITH those very same files before? What could 98se2me's #8 have done to cause this? I don't get it... and can't seem to fix it...
-there *may* be a conflict, somehow, with my (lousy!) SiS 7001/7002 (SiS650 chipset) USB crap, especially the part where it has to disable USB2.0 for win98...? dunno, just gonna *have* to find/force the time to do some experimenting w/clean installs, multiple driver sets, many updates/tweaks, etc, again...
...
[[if I had ANY money, I'd upgrade mobo to a nice, simple, stable Intel/etc... never never EVER buy a cheap SiS mobo! ]]
...
--ps: Re: "it's the new Gdi...":
I haven't noticed any problems (or any difference, at all) with ANY of the gdi* versions of/over the past year, myself... (been playin around w/both 98 & ME versions)...

Does anyone know what files I need to leave out to keep the 98SE format dialog box and selections?

I would like to keep the 98SE "Copy System Files Only" option.

Thanks

Tmod

Please note that GDI*.* files installed by 98SE2ME are not 4.10.2227 [which are 98SE files] but 4.90.3003 [which are WinME files].
So you probably mean that GDI*.* 4.90.3003 are the culprit for your power management problems?
If that's the case, I will post a new build of 98SE2ME on 8-21-2006 which installs older GDI*.* 4.90.3002 files.
Hope that will fix your problem.
As the comparison TXT file shows [thank you the_gui], the only files that could make a difference for power management are the GDI*.* files.
All others have nothing to do with power management, as far as I can tell.
USER*.* files also have something to do with power mangement, but those WinME files are the same since I posted the 1st 98SE2ME build, and nobody reported any issues so far.

Thanks for your feedback.

PsycoUnc:

Sorry about all your troubles.

1. I have changed the batch code from %windir%\NUL and %winbootdir%\NUL to %windir%\*.??? and %winbootdir%\*.??? .
I'll also try to change all autoexec.bat pasting commands code in all my batch files to wininit.ini code.
This way autoexec.bat won't be used anymore by 98SE2ME.

2. About your USB thumb drive:
maybe it's the new [reduced] USBSTOR.INF installed in %windir%\INF which is also installed by Max-Decim's NUSB 2.3:
http://www.mdgx.com/web.htm#9SU
that causes your errors?
Can you confirm that?
If that's the case, I'll remove USBSTOR.INF from 98SE2ME.

3. About backups:
98SE2ME options 1 + 2 now make backups of individual system files only [take very little disk space] into:
%windir%\WIN98SE.9ME = original folder name is %windir%
%windir%\SYSTEM.9ME = original folder name is %windir%\SYSTEM
%windir%\SYSTEM32\DRIVERS.9ME = original folder name is %windir%\SYSTEM32\DRIVERS
If you restore individual files 1 by 1 from there [reboot after restoring each file], you may be able to find the culprit.

Thanks a lot for your feedback.

P.S.:
I'll post a new 98SE2ME build 8-22-2006 sometime tomorrow.

1. If you installed 98SE2ME option 3, then all common dialog boxes will change to WinME style [because of newer COMDLG32.DLL from WinME setup CD].
To restore older Win98 SE file from setup CD, run this command [example]:
EXTRACT/Y C:\TEMP D:\WIN98\WIN98_27.CAB /L COMDLG32.DLL
Where D: is the CD/DVD drive letter, change if necessary to match yours.
Then reboot to native MS-DOS [or from a boot floppy/CD/DVD] and copy it to %windir%\SYSTEM [example]:
COPY/Y C:\TEMP\COMDLG32.DLL %winbootdir%\SYSTEM
Reboot normal.
Done.

2. If you installed 98SE2ME options 1 or 2:
newer COMMDLG.DLL + COMMCTRL.DLL from WinME setup CD will be installed.
These 2 files should not change common dialog boxes.
But if you wish, you can restore older Win98 SE setup CD files into %windir%\system :
COMMDLG.DLL + COMMCTRL.DLL
found as:
COMMDLG.NEW inside WIN98_51.CAB
and
KOMMCTRL.DLL inside PRECOPY1.CAB
Extract them using a command line like this [example]:
EXTRACT/Y D:\WIN98\WIN98_51.CAB /L C:\TEMP COMMDLG.NEW
EXTRACT/Y D:\WIN98\PRECOPY1.CAB /L C:\TEMP KOMMCTRL.DLL
Where D: is the CD/DVD drive letter, change if necessary to match yours.
Then rename them:
C:
CD\TEMP
REN COMMDLG.NEW COMMDLG.DLL
REN KOMMCTRL.DLL COMMCTRL.DLL
Then reboot to native MS-DOS [or from a boot floppy/CD/DVD] and copy them to %windir%\SYSTEM [example]:
COPY/Y C:\TEMP\COMMDLG.DLL %winbootdir%\SYSTEM
COPY/Y C:\TEMP\COMMCTRL.DLL %winbootdir%\SYSTEM
Reboot normal.
Done.

It does work well thanks.I didn't realize at first cause most of my Win98SE computers are tweaked
exactly the same but i did notice the difference.

You're wrong, MDGx. SHELL.DLL [shell.new] is responsible for this!

Then just do that instead with SHELL.DLL [found as SHELL.NEW on WinME setup CD inside WIN_19.CAB].

A little more polite formula [hint ] would have been...

"The actual file that causes this is SHELL.DLL [SHELL.NEW] from WinME setup CD.

HTH"

HTH

Tihiy & MDGx,

Thanks for letting me know what I needed to do.

It worked like a champ!!

Tmod

-hi MDGx, thx for the recent help...
...
(-and here comes the BUT ): -BUT, I noticed in your .bat files that you didn't change/remove the
>IF "%winbootdir%"=="" GOTO N@
>IF NOT "%windir%"=="" GOTO N@
stuff... ?... I believe the 2nd one, "%windir%", may cause problems when the user sets that var in autoexec... (unless your recent change of moving the checking to wininit executes the conditional *before* autoexec.bat executes; I'm not familiar w/wininit stuff...) ?
...
-Re: thumbdrive:
hmmm, MD2.2 worked fine w/it, do u think the changes made into 2.3 are the culprit?
(haven't had the time to find/restore/update/tweak an old backup for testing, yet... might be a while... and it kinda looks like once the thumbdrive was "re"-installed as "Unknown Device", that re-installation nuked it for good, regardless of restoring the 98se2me backup files; at least nothing I've tried has helped, incl. hacking the reg manually... oh well, I was overdue for a clean reinstall anyway, that's part of the reason I haven't kept current on the backups...)
>;]

-btw, MDGx, when you remove a file from 98se2me, do you include code to automatically restore that file's 98se backup? If not, that would be a VERY good/helpful idea... (and absolutely vital for people who aren't techies... and even us techies can flake-out sometimes , so automating such corrections might save some potential troubles...)
.
You could create another simple, small .bat and a filelist of all removed files, looping thru em, so in the future it'd be easy to just tack on any additional files to the filelist...
.
-and for compatibility's sake, make sure you look in all 4 places, sequentially, for the (newest) 98se replacement version:
1) 9!M (or win98se's /options/cabs dir), in case such file has been updated;
2) the current 98se2me Backup dir;
3) previous version 98se2me Backup dirs (old full-OS-backup style)
4) win98se's /options/cabs/xxx.CAB file (for original w98se version, if no newer ones found, above)

I have remarked [::] all "IF NOT "%windir%"=="" GOTO N@" lines in all batch files.
That is until I have time to convert all autoexec.bat code to wininit.ini.
Please try 98SE2ME again, see if it works ok this time [3 MB]:
http://www.mdgx.com/4

Yes, I do include code in O2.BAT [which installs options 1 + 2] to restore all files previously installed from WinME CABs, but later on found to be buggy one way or another.
Just open O2.BAT with Notepad and scroll down till you find this line [and all lines below it except the RUNDLL32.EXE lines]:And yes, the DOS based tool LOCATE.COM scans *all* local fixed and removable drives for Win98SE setup CABs.
If it finds them, all files listed there are extracted, copied over to C:\9S2M and then restored to original locations upon next reboot.
In my experience most users have those CABs somewhere on their local drives.
But you have a good idea, to also search for those files in older backups, just in case the 98SE CABs were not found on any of the local drives.
I guess I could use the LOCATE.COM tool for this purpose, specifying 1 file at a time, and add GETVER.EXE version check.
I'll think about it.
Thanks.

About your USB problems...
Please try the older NUSB 2.2:
http://rapidshare.de/files/1217842/nusb22e.exe.html
and then the newer 2.3:
http://www.mdgx.com/spx/NUSB23E.EXE
and see if it makes any difference, and if it does, please let me know.
Thanks.

HTH

Hi,

With regard to a post "I can install the drivers under a "98Lited" Win98SE for AC'97 Motherboard sound cards, but when I install the "ME replacements" I get the error icon showing in device manager for the sound driver. Uninstalling and reinstalling the drivers makes no difference." I have found if I remove the original drivers before installing 98SE2ME, on PC reboot Windows attempts to re-install the drivers and when I point Windows to the Me divers... success!

Also the 8-22-2006 edition of 98SE2ME will now allow the Power Management Options in Windows to work on my PC configuration.



Many, many thanks to Gape and yourself for all your hard work and effort in to keeping Win98 Alive and Kicking.

I nearly went to Win2000 in favour of XP (I hate that activation crap, on principle, let alone all the headaches it can cause) until I saw... the long, long list of critical updates!

Keep up the Brilliant work.

Waywyrd

1. I have not tried 98lite recently, because way back, when I tried an older [full] version, it messed up my 98SE computer. That experience steered me away from using 98lite.
That's why I do not test 98SE2ME nor any other of my upgrades/replacements on "98lite-ned" 9x Oses.
And that's why I practically don't have any experience with 98lite.
But I'm glad your AC97 sound drivers work again, even if by using a re-install workaround.

2. I'm also glad your APM features work again.
T'was my intention to fix this lil bug in the 98SE2ME 8-22-2006 edition.

3. Win2000 can be used today [only if SP4 and all post-SP4 updates are installed] (almost) as well as XP for all purposes: gaming, CAD, 3D graphics/modeling, A/V editing/encoding, CD/DVD burning etc.
Actually, all u need to do is install AutoPatcher 2000:
http://www.neowin.net/forum/?showforum=89
http://www.neowin.net/forum/?showtopic=486485
But personally, I still prefer a fine-tuned Win98SE anytime.

4. Many thanks for your [too] kind appreciation + compliments.
I'm glad you find 98SE2ME useful.
Enjoy.

@MDGx: Why when I install 3 option, there isn't moviemk.exe in %programfiles%\moviemaker?
I've read that this file is taken from WinME hotfix Q262806, why didn't you include directly in the package?
So I must install file separately...

Ps: I've WinME CD not updated, maybe is this?

I tested option 3 on my tweaked 98SE system and also on a "virgin" [from scratch, "fresh" install] 98SE system.
Updated Movie Maker 1.0.1377.0 installs properly on both.
Please look inside the "C:\Program Files\MoviMakr" folder [default]. Right-click on MOVIEMK.EXE, should say 1.0.1377.0 under the Version tab.

TIP:
You must have the WinME setup CD English edition for this to work, because 98SE2ME option 3 extracts original moviemk.exe file from the WinME CABs, and then patches it to the newer version [1.0.1377.0] using a Vpatch patch [PATMM.EXE = found in C:\9!M].
Excerpt from READ1ST.TXT:
http://www.mdgx.com/9s2m/READ1ST.TXTI also posted this at the 98SE2ME forum [please see 1st post]:
http://www.msfn.org/board/?showtopic=46349

Hope this helps.

Is having a file with a newer date but older version better than a file
with a newer version but older date.The reason i ask is because i notice
Wmp 7 bonus pack have a newer version of DUNZIP32.dll,DZIP32.dll
but have older dates.

@MDGx: I'm translating 98SE2ME in italian language, but I have a VPATCH error during installation of option 3, also if continues.
"No suitable patches were found"

Where is the problem?

I've translated all files, I think, but always this error.

Important
IE6 SP1 has these files with older versions but with newer dates

Systemagent.exe
Mapistub.dll
cool.dll
imagehelp.dll
comcat.dll
advapi32.dll
sage.vxd

and you might wanna replace Internat.exe with the WinMe version since its newer by version and date

This is why a version detection tool would come in handy.

After installing the unofficial DCOM98 Full Update ( http://www.mdgx.com/add.htm#COM ) and using SFC to check the updated files, I noticed discrepancies between replaced files with the same build number. All these files were replaced by files from DCOM98UP.EXE with the same build number, but with an earlier date:

dllhost.exe (build 4.71.3328) went from 08/06/00 to 29/03/99
comcat.dll (build 5.0) went from 08/06/00 to 28/03/99
compobj.dll (build 2.3.2) went from 08/06/00 to 28/03/99
iprop.dll (build 4.00) went from 08/06/00 to 18/11/99
ole2.dll (build 2.3.2) went from 08/06/00 to 28/03/99
olecnv32.dll (build 4.71.3328) went from 08/06/00 to 28/03/99
olethk32.dll (build 4.71.3328) went from 08/06/00 to 28/03/99
rpcltccm.dll (build 4.71.3328) went from 08/09/99 to 08/09/99
rpcltscm.dll (build 4.71.3400) went from 07/02/02 to 07/02/02
storage.dll (build 2.3.2) went from 08/06/00 to 28/03/99
ole32.dll (build 4.71.3328) went from 08/06/00 to 29/03/99

Although the files in DCOM98UP.EXE share the same build number with those installed by 98SE2ME, they are often quite smaller than the ME files (and again, are older).

The files from DCOM98UP.EXE are clearly not the same as the files they replace. Does anyone have any ideas about which Of the two sets of files I should prefer to have installed? If not the DCOM98UP.EXE files, then should DCOM98UP.EXE be updated with the newer files, perhaps?

(Thanks.)

Can you add this or atleast test it
http://www.msfn.org/board/index.php?s=&...st&p=489343

Also will you upgrade Vmouse.vxd with this one
http://www.mdgx.com/files/ME318307.EXE

Just to say - one more happy user. I reinstalled Windwoes last Friday and thought I might as well try it. Nice, smooth install. I didn't do Option#3. I figured that since I use an alternate shell, I didn't need that too much. Don't need the games either, but I can shuck 'em.

Some things are noticeably improved, and nothing has refused to function so far. My cranky old eMachine600 originally came with ME but my sister sensibly replaced it with 98 - so I inherited both when she gave up on it and dropped it on me.

Edited to add:

HELLLLLLLLLLLP!!!
Modplug Tracker won't run any more!
HELLLLLLLLLLLP!!!

Fragdabbit! This is not as bad as not being able to run GIMP, but it is bad. I can't get any version of mpt to do anything but lock up and crash the whole works. Even profiling with Dependency Walker ends in a lockup. Owoo!

This is my Dr Watson report

If the Taskbar is behaving strangely, try exiting Multimedia background task support module.

Module Name: mmtask.tsk
Description: Multimedia background task support module
Version: 4.90.3000
Product: Microsoft Windows
Manufacturer: Microsoft Corporation

File version matters, not file date.
Newer is usually better [but there may be exceptions].

Thanks for the find.
I'll add the newer D*ZIP.* 4.xx files to 98SE2ME soon.

As I said, the vpatch file [PATMM.EXE] was created from the English moviemk.exe, not from the Italian version, therefore the file md5 checksum is different.
You need to either recreate patmm.exe from the Italian moviemk.exe or add patched moviemk.exe ver 1.0.1377.0 from Q262806 directly into Italian 98SE2ME.EXE.
If you add moviemk.exe, you need to modify 98.ISS [using Notepad] and replace PATMM.EXE with MOVIEMK.EXE, then recompile 98SE2ME.EXE using this command [example]:

D:\INNO\COMPIL32 /CC D:\INNO\98.ISS

or by using INNOSET.BAT.
Change paths names to match your computer setup.

You also need to replace all PATMM instances from o2.bat + o3.bat with code to copy moviemk.exe into C:\Program Files\MoviMakr , same as the other files that are copied using the cscript code [which detects properly movie maker location] in o2.bat.

Hope this helps.

If IE6 SP1 files are older versions, then it's probably better to use newer ones from WinME CD, even if file dates are older [as I said in previous post, file version is important, file date doesn't matter].
98SE2ME already installs all files you listed above, including internat.exe.
You can find them listed in o2.bat [open it in Notepad].

Correct file names [respecting 8.3 short filename.extension convention]:

sysagent.exe
imagehlp.dll

Way back when I started replacing files with newer ones from WinME, I used SFC to update to newer versions.
Then I started to compare files side by side.
To my knowledge 98SE2ME already contains newest files available [except for dzip* + dunzip* DLLs].
If I use older files from 98SE, that means newer ones from WinME are incompatible.
READ1ST.TXT should give all details you need:
http://www.mdgx.com/9s2m/READ1ST.TXT

HTH

_________________________________


I've also noticed these discrepancies a while back, but didn't pay much attention, because both older and newer date-stamp files worked ok, I have not noticed any errors.
I guess MS recompiled files from DCOM98 [with same version] and put them into WinME setup CD.
But I have no idea why they have different sizes.

______________________________________


1. I'm aware of the systray.exe hexed code, but it works only with the 98SE version(s), not with WinME version(s), because the hex string is different.
75 1B 52 68 does not match anything in systray.exe 4.90.3002 from WinME.

2. 98SE2ME does not install any mouse files, and that includes vmouse.vxd.

If you want to try vmouse.vxd on your 98SE computer, just copy this vmouse.vxd to %windir%\system\vmm32 and then reboot.
I don't think this WinME file works with 98SE.

HTH

Sorry, I'm not familiar with [never heard of] modplug tracker.

Have you tried modplug tracker without 98SE2ME installed?
I don't think it makes any difference.

If mmtask.tsk is the culprit, just "kill" it using for example CoolKill [freeware]:
http://www.prowebsitemanagement.com/cooltools/coolkill.html
and then run mpt again.
Then you can test mpt using Win98SE mmtask.tsk from the setup CD [CABs].
Every time after you replace mmtask.tsk you must reboot.

To my knowledge these 2 mmtask.tsk files are almost identical except the version number text strings [newer 1 has been updated to read 4.90.3000, the older 1 was 4.03.1998].
I even compared them in wdiff, they are almost identical.

I've been using WinME mmtask.tsk for a very long time with 98SE [was 1 of the 1st files I replaced from WinME more than 5 years ago], and never experienced any errors so far.

If you find that mpt works better with 98SE mmtask.tsk, please post here your test results, so we can all benefit. This way I know to replace WinME mmtask.tsk with the 1 from Win98SE in 98SE2ME.

I've been using GIMP [different versions] with 98SE, with and without 98SE2ME installed, and with WinME. It always worked ok as far as I can recall.
Please try the newest version of GIMP available (if not already):
http://www.gimp.org/windows/
http://gimp-win.sourceforge.net/stable.html

Hope this helps.

Have a reg entry that allows a person that likes the convenience of compressed folders to open a zip file in the same window. Personally I like that. Don't get me wrong I mostly use Izarc for everything else, it's just sometimes I'm lazy.

for simplicity's sake I've named it ddeexec.reg(simple until you find it's too long to hook to the msbatch.inf)

REGEDIT4

;It's definitely the ddeexec.reg that allows a zip to open in the same folder.
[HKEY_CLASSES_ROOT\CompressedFolder\Shell\Open\ddeexec]
@="[ViewFolder(\"%l\", %I, %S)]"

[HKEY_CLASSES_ROOT\CompressedFolder\Shell\Open\ddeexec\Application]
@="Folders"

[HKEY_CLASSES_ROOT\CompressedFolder\Shell\Open\ddeexec\IfExec]
@="[]"

[HKEY_CLASSES_ROOT\CompressedFolder\Shell\Open\ddeexec\Topic]
@="AppProperties"


or if a person prefers to add it right to their msbatch or some other inf

;CompressedFoldersFix
HKCR,CompressedFolder\Shell\Open\ddeexec,,,"[ViewFolder(%l,%I,%S)]"
HKCR,CompressedFolder\Shell\Open\ddeexec\Application,,,Folders
HKCR,CompressedFolder\Shell\Open\ddeexec\IfExec,,,[]
HKCR,CompressedFolder\Shell\Open\ddeexec\Topic,,,"AppProperties"

I have this added to my msbatch to see if it works; not tested in that tho'.
I had this in a dummy .inf w\ an addreg and it worked for me.

So here's two different ways to add it. Although it would make a nice small update to some really cool upgrader\installer.
- Jaymo

Just a heads up, Modplug Tracker is a media player for MOD-format music. You can use Winamp w/ a plugin to play such things - in fact, I remember winamp having very decent plugins for MOD files. I use MediaMonkey now, which supports Winamp plugins, so I'll try and see if such plugins still work, when I get home (at work right now).

Jimmsta you confuse Modplug Player with ModPlug Tracker. ModPlug Tracker is a tracker as it's name says.

Nice reg trick.

I am seriously considering adding this to 98SE2ME option 2 [+ option 1 which implicitly installs option 2].

Thanks.
Keep up the good work.

Added 9-25-2006.

Also added newer D*ZIP32.DLL 4.00.04 files from WMP7 Bonus Pack.

Also added SUCATREG.EXE 4.90.3000 from WinME setup CD into O2.BAT.

After installation all my icons which i modded from registry were intact, except the shortcut icon. Its not there anymore. How do i get it back? Overall its looking good.

Another question: Can these updates be installed over it?

Millenium Updates

1.Can you change the Systray.exe icon to anything else.

2.Can you replace the files you have backed up that you said was not
necessary to restore

Example-options 5,6,7 and other files that maybe backed up
no need to backup/restore if such files are obselete/buggy

3.Don't forget about sigverif.exe/winpopup.exe

4.If you un-install option 3 their is a folder left in My Network Place/Network Neighborhood
that can not be removed at all

5. if you can find somebody to create a small patch with the code i gave you
you can extract the original files for Windows Movie Maker from WinMe CD which will allow you to add
it back to option 1 & 2. Also it will decrease the size of 98SE2ME.So the only file you would need is MOVIEMK 1.0.1377.0
from Q287564

6.Is their some type of code/trick/hack that you can add to 98SE2ME that will install just the update ONLY if you already have a previous version INSTALLED.
But it would still install the full version if not a previous version found.
I'm trying to cut down space and time so please bare with me.

just a few suggestions
hope you consider

I have just read MDX's guide on it and have solved the problem, by incorporating the address to shell32 in the registry.


However i still curious to know that are the updates for Windows98SE and Windows ME same? If not then: can and or these updates be installed on WIN98SE2ME?

Problemchild: Systray.exe's icon can easily be changes using Microangelo tools. There are 5 icons in the file and the main icon is 16x16 16 colours. I can change it for you, if you want? But i do not anything about the rest of the things in your post.

MDGX, can I use your update with a WinME CD in portuguese language, to a Win98, in same language????

1. Desktop icons shortcut overlays are annoying to most users, so they will be disabled if you install 98SE2ME options 1 or 2.
But there is a registry entry you can restore to bring them back, as quoted from READ1ST.TXT [the "98SE2ME.PIF COMPLETE GUIDE" section]:
http://www.mdgx.com/9s2m/READ1ST.TXT
2. Windows Millennium Edition (ME) patches/updates/(hot)fixes/service packs canNOT and should NOT be installed on 98SE, with or without 98SE2ME or with any other patch/update/mod/tweak, official or unofficial.
Quoted from READ1ST.TXT [the "FAQ" section]:
http://www.mdgx.com/9s2m/READ1ST.TXT

BTW:
This site you mention:
http://www.hpcfactor.com/support/patching/winme/
has only a few older/obsolete updates.
All newer/current available updates [official + unofficial] for WinME are here:
http://www.mdgx.com/web.htm#WME
http://www.mdgx.com/add.htm
http://www.mdgx.com/ietoy.htm
http://www.mdgx.com/wmp.htm
http://www.mdgx.com/dx.htm

HTH

Here is the complete guide on how to translate 98SE2ME into any language other than English and then recompile the installer [using InnoSetup]:
http://www.mdgx.com/9s2m/INNOFILE.ZIP
Please start by reading INNOFILE.TXT.

HTH

Post #623