MDGx

Unofficial HHUPD.EXE contains newer builds of HTML Help files from the Windows XP patch [same official patch described at KB896358].This way [unofficial patch was suggested by erpdude8] one has the choice to install either the official KB896358 patch [older builds] or the unofficial KB896358 patch [newer builds]. And because files installed by HHUPD.EXE are newer, they will replace the older ones installed by official KB896358 patch [if you installed that one first]. Essentially these files fix the same security vulnerability, they are just meant [officially] for different OSes. There is 1 difference though: unofficial HHUPD.EXE installs also all HHCTRLUI.DLL files into %windir%\SYSTEM\MUI [that are also installed by MS IE 5.5 SP2, 6.0 + 6.0 SP1] for all supported languages. Official KB896358 does not install any of the MUI [Multilingual User Interface] files, because it is meant only as a security fix, not as a whole HTML Help installation. The install order of patches you list above is still valid as far as I know. Hope this helps.

Sorry about that, keep forgetting not everybody has winbot.ini in C:\ root [besides msdos.sys], like I do. But there no reason to panic, your Windows installation is fine, nothing was damaged. What happened is that BSRESTOR.INF [11-30-2005 edition] was creating a new WINBOOT.INI file in C:\ root [only if you didn't have it] with these 2 lines: [Options] SystemReg=0 and after rebooting, if winboot.ini is found in C:\ root, Win9x/ME boots from it instead booting from msdos.sys. But because [in your case] the newly created winboot.ini does not contain a [Paths] section or the 3 lines below it that should point to WinDir, WinBootDir + HostWinBootDrv locations, Windows gets confused, and pops up those error messages. On Win9x/ME computers with winboot.ini present in C:\ root, this error doesn't occur. If you wish to know more about winboot.ini: http://www.mdgx.com/newtip16.htm#WBINI I have removed the winboot.ini fix, please try the 12-1-2005 edition of 98SE2ME: http://www.msfn.org/board/?showtopic=46349 Hope this helps.

I had experienced this a while back with 98SE2ME [this used to be a problem only with option 3 if I recall correctly], but it has been fixed.Please re-install 98SE2ME after you have installed SP 2.1a. 98SE2ME: http://www.msfn.org/board/?showtopic=46349 I don't know if SP 2.1a needs [or not] to be fixed/changed, that is a question for Gape. Hope this helps.

Gape: I have recently noticed [at least on 1 computer] that "UpdateInis" INF directive works properly only if adding the folder handle name in front of the file(s) to be modified. Example: [Version] Signature=$CHICAGO$ [DefaultInstall] UpdateInis=UPDini [uPDini] %31%\MSDOS.SYS,Options,,"SystemReg=0" %31%\WINBOOT.INI,Options,,"SystemReg=0" as opposite to: [Version] Signature=$CHICAGO$ [DefaultInstall] UpdateInis=UPDini [uPDini] MSDOS.SYS,Options,,"SystemReg=0" WINBOOT.INI,Options,,"SystemReg=0" Without "%31%\" setup thinks msdos.sys + winboot.ini are in %windir% [false], not in C:\ root [true]. LDID directory handles for INF files: LDID = Logical Disk IDentifier. Can be one of these values: 00 Null [This LDID can be used to create a new LDID] 01 Source driveletter:\pathname 02 Temp Setup 03 Uninstall 04 Backup 10 Machine (Windows) directory 11 System directory 12 IOSubsys directory 13 Command directory 14 Control Panel 15 Printers 16 Workgroup 17 INF Directory 18 Help directory 19 Administration 20 Fonts 21 Viewers 22 VMM32 23 Color directory 24 Root of drive containing the Windows directory 25 Shared (Windows) directory 26 Guaranteed boot device for Windows (Winboot) 27 Machine 28 Host Winboot 30 Root directory of boot drive 31 Root directory of boot host drive Hope this helps. BTW: I've tried SP 2.1a on 2 different 98SE installations, and worked like a charm. Excellent job, Gape!

You guys have waaay too much time... In order to test all these different builds on all 9x OSes takes some time, especially because I would need to reinstall Win95 retail, 95B OSR2, 98 FE, 98 SP1 + ME all over again. And I'm afraid I don't have that kind of free time at the moment. Maybe sometime in the near future... BTW: This link is invalid outside Ifrance.com servers: http://snoopy81.ifrance.com/snoopy81/dl_en/WinPack300b.zip WinPack home [English]: http://snoopy81.ifrance.com/snoopy81/en/winpack.htm D/l page: http://snoopy81.ifrance.com/snoopy81/download.htm WinPack300b.zip must be downloaded from within that server [page above]. I guess Ifrance servers have anti-leech protection.

You're right, TSHOOT.OCX is not really necessary to fix this bug, but [as you already noticed] this TSHOOT.OCX build is newer than all others, so besides fixing the REG entries, this fix also updates TSHOOT.OCX to newest version. This TSHOOT.OCX build is from this MS update: * Microsoft Windows 98/98 SP1/98 SE Troubleshooter HTML Help TSHOOT.OCX build 1.0.1.2123 + TSHOOT98.CHM Update: http://support.microsoft.com/support/windows/tshoot/ Direct download [385 KB, English]: http://www.mdgx.com/files/TSHOOT98.ZIP posted here [scroll all the way down to the bottom of topic]: http://www.mdgx.com/web.htm#98SE Hope this helps.

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 Newest CRYPT*.DLL files that work with 9x/ME I'm aware of [unofficial]: http://www.mdgx.com/web.htm#CPT File: http://www.mdgx.com/files/CRYPT9X.EXE CRYPT9X.EXE installs newest versions of: CRYPT32.DLL CRYPTDLG.DLL ENHSIG.DLL RSAENH.DLL SCHANNEL.DLL SOFTPUB.DLL XENROLL.DLL Newest TTF Fonts that work with 9x/ME [unofficial]: http://www.mdgx.com/add.htm#TTF File [3.75 MB]: http://www.mdgx.com/files/TTFPAK.EXE TTFPACK.EXE installs newest versions of: ANDALEMO.TTF ARIAL.TTF ARIALBD.TTF ARIALBI.TTF ARIALI.TTF ARIBLK.TTF COMIC.TTF COMICBD.TTF COUR.TTF COURBD.TTF COURBI.TTF COURI.TTF GEORGIA.TTF GEORGIAB.TTF GEORGIAI.TTF GEORGIAZ.TTF GOTHIC.TTF GOTHICB.TTF GOTHICBI.TTF GOTHICI.TTF IMPACT.TTF LSANS.TTF LSANSD.TTF LSANSDI.TTF LSANSI.TTF LUCON.TTF MICROSS.TTF OCRAEXT.TTF TAHOMA.TTF TAHOMABD.TTF TIMES.TTF TIMESBD.TTF TIMESBI.TTF TIMESI.TTF TREBUC.TTF TREBUCBD.TTF TREBUCBI.TTF TREBUCIT.TTF VERDANA.TTF VERDANAB.TTF VERDANAI.TTF VERDANAZ.TTF WEBDINGS.TTF BTW: OLE files build 2.40.4526 from Win2000 hotfix Q886765: http://www.mdgx.com/files/Q886765.EXE can be used successfully with 98/ME only if using these 3 files: ASYCFILT.DLL 2.40.4526 OLEPRO32.DLL 5.0.4526 STDOLE2.TLB 2.40.4526 together with older OLEAUT32.DLL build 2.40.4522 from Win2000 SP4. OLE 2.40.4526 [as listed above] for 98/ME is here: http://www.mdgx.com/add.htm#OLE File: http://www.mdgx.com/files/OLEUP.EXE If ones wishes to install all 4 older 2.40.4522 files: http://www.mdgx.com/files/OLEUPME.EXE A bit later: I tried OLE files from Win2003 SP1. OLEAUT32.DLL, same as 2.40.4526 from Q886765, does *not* work properly. Older OLEAUT32.DLL 2.40.4522 *must* be used. The other 3 files seem to work ok. I put together an installer for this [448 KB]: http://www.mdgx.com/files/OLEUP2.EXE Please try it out, and post here any bugs/errors. Hope this helps.

Those updated files [only the ones I know for sure work ok with 98SE] are already part of 98SE2ME. 98SE2ME installs the most recent WinME USB + FireWire WDM drivers. Just install 98SE2ME options 1 or 2. Hope this helps.

98SE2ME installs same files no matter which "minimize windows" program you have used [98lite, mindows, etc].But 98SE2ME does not install updated files from MS hotfixes/updates [all included in C:\9!M] if files with same version number/build already exist [i'm using the freeware GETVER tool to detect version numbers]. As PsycoUnc put it so well, the best bet is to allow 98SE2ME to backup your entire OS [if installing 98SE2ME for the 1st time], and then restore the files you want from C:\W98SEOLD [if necessary]. 98SE2ME creates a full OS backup *only* if installing options 1 or 2. All other options [from 3 to up 7] backup only replaced files. Complete details in READ1ST.TXT [100 KB]: http://www.mdgx.com/9s2m/READ1ST.TXT Hope this helps.

Please see READ1ST.TXT [100 KB]:READ1ST.TXT respectively the * Option 3: section under the "98SE2ME.PIF COMPLETE GUIDE" chapter. If you want more installation details, please open these files with Notepad: - C:\9!M\RSTR3F.INF = look under the [3M] section. - C:\9!M\98SE2ME.BAT = look under the :X3 section. Also, you may want to open IMGVIEW.HTT in Notepad, and look at the differences between this file and the original one from the WinME setup CD. Hope this helps.

98SE2ME options 1 and 2 install a bunch of WinME drivers, especially USB, FireWire [iEEE 1394] and WDM. Most are SYS WDM model and install into %windir%\system32\drivers . Complete list is found here: http://www.mdgx.com/98-5.htm#FME Some of these drivers are actually newer [fixed by MS] versions than the ones found on the WinME setup CD. All those files are found as separate WinME downloads: http://www.mdgx.com/web.htm#WME and except for UPDATE.SYS + KRNL386.EXE they are all official releases from MS. Unofficial + MS fixes are specified as such. 98SE2ME READ1ST.TXT has extensive details about the order in which to install updates/upgrades/patches/packs/fixes/etc [100 KB]: http://www.mdgx.com/9s2m/READ1ST.TXT and what files are installed by 98SE2ME, and where they are installed. If you care to try 98SE2ME, please start here: http://www.msfn.org/board/?showtopic=46349 and look also here: http://www.mdgx.com/98-5.htm#KRM9S Enjoy.

I have changed the uninstall string from Control Panel > Add/Remove Programs to read:Uninstall unofficial Windows 98/98 SE/ME Q891711 Patch It fits into the window now. Hope this helps.

... or one could try to install 98SE2ME: http://www.msfn.org/board/?showtopic=46349 which installs [options 1 + 2] newer VCACHE.VXD from Windows ME setup CD. Hope this helps.

Your wish is my command... U891711.EXE updated [110 KB]: http://www.mdgx.com/files/U891711.EXE Hope this helps.

I have uploaded the correct version of the patch with modified SED file [please see post # 31 above], which now allows to install directly on WinME, and even if official MS05-002 patch was already installed, it properly overwrites it.Same behavior if installed on Win98 FE or 98 SE: U891711 can be installed over official MS05-002, it will properly overwrite the MS files, which are older builds [even v2]. I have also replaced "hotfix" with "update" in the text file. U891711.EXE [110 KB]: http://www.mdgx.com/files/U891711.EXE U891711.TXT: http://www.mdgx.com/files/U891711.TXT Please try it out at your convenience.

Win98 exit is not a reboot, unless you chose the restart option, or unless there's something wrong. Problems with the shutdown sequence are common.Typically Win98 will try to turn off the computer on shutdown. However, it can be made to return to the DOS prompt pretty easily. Right on the money. And here is how to do it, in case anybody is interested: http://www.mdgx.com/98-4.htm#98ATX http://www.mdgx.com/newtip1.htm#DOS http://www.mdgx.com/last3.htm#DOS2DOS Please remember that MS-DOS 7/8 is the 8-bit layer on top of which Win9x 16-bit layer loads. With some modifications to autoexec.bat, config.sys + msdos.sys [MS-DOS 7 + 8 only, because in MS-DOS 6.xx MSDOS.SYS is a binary file], one can actually regain full access to native/true MS-DOS, upon exiting Windows GUI [instead of shutting down], and that includes WinME, if patched with a Real-mode DOS patch: http://www.mdgx.com/dos.htm#ME Hope this helps.

You're probably right, I keep an updated page for UMBPCI + HIRAM, just in case... http://www.mdgx.com/umb.htm I also use them whenever I boot into Win98SE from my old P3 Intel 440BX PC. My relevant config.sys lines: DOS=HIGH,UMB,AUTO DEVICE=C:\MAX\RAM\UMBPCI.SYS DEVICE=C:\MAX\RAM\HIRAM.EXE DEVICEHIGH=C:\MAX\HIMEM.SYS /NUMHANDLES=120 /TESTMEM:OFF /Q

My bad, guys, I forgot to upload the new ME version of the patch. Here it is... [110 KB]: http://www.mdgx.com/files/U891711.EXE It should install on Windows ME without any problems, even if official MS05-002 patch was already installed. Please try it out, should fix the same security vulnerability as MS05-002 [but using better patching technique], under Windows 98 (FE), 98 SE and ME. ___________________________________________ I believe a decent proof of concept demo for LOADIMAGE icon [.ANI file] is found here: http://www.xfocus.net/flashsky/icoExp/ Please try this demo first without official MS05-002 or U891711 installed. Then install MS05-002 first, try the demo again. Then uninstall MS05-002 and then install U891711, and try the demo again. To install U891711 on top of MS05-002, it is not necessary to uninstall MS05-002 first, U891711 should overwrite the MS05-002 files upon installation. Hope this helps. ___________________________________________ I was playing a local wav file. I don't use Media player for online (much if ever) Your 98SEMP10 automated install was applied some time ago and I was reporting this as it was the first time I'd seen this problem having installed this unofficial 891711 patchAny ideas ? I don't think that WMP generic [not found] image placeholders issue was related to either 98SEMP10 or U891711.I still blame it on server error, lag or timeout. What you experienced, could have also been poor quality of the internet connection [at the time] due to problems at your ISP's end. Hop this helps.

bristols: This the author's answer to your question: Hope this helps.

You're right, WMP is very tightly linked to IE, after all, WMP streaming is done thru IE's engine. I have sent your bug report to the patch author.I'll post the answer here. Thanks for your time and concern.

Did you notice this when trying to play online or offline?If this happened while online [over the internet], it might have been because a particular server was either lagging, timed out or had maintenance/repair/backup issues [?], because some of the graphics/icons you see in the WMP window [while online] are located on remote [internet based] servers. And because the problem was fixed after restarting the app, that is one more reason to believe a remote server was the cause. PS: I assumed this was related to installing 98SEMP10 [WMP10 files from WinXP]. Hope this helps.

Thanks for your feedback.I will relate this to the author.

Actually QEMM 8.0x and 9.0 [last one] releases are [or should be] compatible with all Win 9x builds, according to the Quarterdeck docs.This also depends which of QEMM extra "features" one uses. If used strictly as a plain EMS/XMS memory provider, without using any of the "stealth" modes or "advanced" switches, QEMM 9.0 should be almost 100% compatible with all Win 9x builds. I believe QEMM 9.0 is still available here [4.8 MB]: http://downloads.planetmirror.com/pub/dv/qemm97.zip Make sure to read the install guide in info#2.txt . I've been experimenting with QEMM 9.0 on Windows 95 OSR2.1, 98, 98SE and ME, and worked great most of the time. This is the config.sys line I was using: DEVICE=C:\QEMM\QEMM386.SYS X=F000-FFFF I=B000-B7FF RAM AU BE:N DM=128 HA=240 MA=128 TA=32 More info: http://www.mdgx.com/newtip20.htm#9SMM Please see also MEMORY.TXT, part of W95-11D.EXE [1.25 MB]: http://www.mdgx.com/95.htm W95-11D.EXE also contains autoexec.bat + config.sys files with examples of use for QEMM 9.0 and 2 text files [DOS9XMEM.TXT + WIN9XMEM.TXT] with MEM/A/C/P stats while using QEMM both in native MS-DOS and in a DOS box. Hope this helps.

The ASUS [NVidia based] card shouldn't need any memory manager [EMM386 or UMBPCI or any other 3rd party] in order to work.But when you installed the vid card software, some utility [TSR] loaded itself from within config.sys or autoexec.bat, and that particular utility seems to require EMM386 [in other words requires expanded memory to either load or for its own memory needs]. I don't think that utility is necessary for proper operation in Windows, it's probably just a compatibility tool for DOS based video modes [?], and you can safely disable it: REMark it by using ; in config.sys or :: in autoexec.bat in front of it followed by a space, and then reboot. If that tool provides VESA VBE compatibility modes, you can use instead Scitech Display Doctor UNIVBE.EXE tool [freeware]: http://www.mdgx.com/speed.htm#VGA which if I recall correctly, doesn't require an expanded memory manager, just upper memory in order to save conventional ["low"] memory when it loads. If your vid card already has VESA/VBE support built into its BIOS, then you don't need any such tools. BTW: UMBPCI.SYS does not provide/enable expanded [EMS] or extended [XMS] memory, only upper memory blocks [uMBs]: http://www.mdgx.com/umb.htm DOS based video tools may interfere with Windows video APIs [GDI] operation, which may result in errors and/or lockups. Also, NVidia Forceware [universal] video drivers in current releases: http://www.nvidia.com/object/win9x_archive.html usually provide most video modes support to Windows apps/games, and even for DOS games played from within Windows [DOS box]. It's best [if you can help it] to avoid using such tools, unless you plan on using native/true/pure MS-DOS mode to play DOS games, for example. Hope this helps.