MDGx

Nope, they don't. The last NVidia driver for 9x OSes is 81.98 [WHQL certified]. 81.98 supports only 6xxxx GeForce series, as you can see from this fragment extracted from the NVAGP.INF file, which contains vendor strings for all supported NVidia GPUs: HTH

Unless one wants to spend money on an obsolete/limited functionality zipping/unzipping tool, there is no reason why one should use WinZip, when there are so many other similar tools, and most are free(ware): http://www.mdgx.com/toy.htm#ZIP Or if any1 likes the command line, there are always tools like PK(UN)ZIP, ARJ, 7ZA, LHA etc. HTH

My experience with UMBPCI.SYS: Just because you had problems with UMBPCI, doesn't mean that nobody else should use it. I've been using UMBPCI for more than 7 years now, without any problems, but I guess that's because of the mobo chipsets [intel based] I've been using it on. That's why I recommend everybody to try UMBPCI see if it works ok, because if it does, it provides a lot of free [usable] upper memory [without slowing the computer too much] for those of us who use native/true/real mode DOS based games/apps. But if not using any native/true/real mode DOS based software, UMBPCI is of no use. About memory slowdowns: To my knowledge, EMM386.EXE and similar EMS managers are the ones which slow down the computer, not UMBPCI. According to this graphic: http://www.mdgx.com/umbpci.gif EMM386 is ~ 3 times slower than UMBPCI. On the other hand, any memory manager will slow down the overall performance a bit [or more, depending on their functions, memory areas accessed/mapped, page frame etc], no matter which one you use. Even HIMEM.SYS slows down the computer. But out of all memory managers I know [and I've tested most all available ones], UMBPCI is the only one which slows down the least. About B000-B7FF UMA area: UMBPCI can't access it because it is not an actual memory manager [like EMM386 or QEMM386], UMBPCI is only a memory "extender" which works with HIMEM.SYS, and maps the unused DMA memory as UMBs. That's all it does. And DMA memory can be mapped only within the C000-FFFF area [X86 IBM/PC clone limitation, not UMBPCI's fault], and only if it is not occupied by other BIOSes/BIOS extensions at boot time, and only in contiguous "chunks" of 16 KB each. That's probably why [as you say] the granularity of its mapped memory is "coarse". Incompatibility with drivers/floppy controllers: the floppy bug is well known, and together with its fix, they are all well documented by the author of UMBPCI, at his home page: http://www.uwe-sieber.de/umbpci_e.html and also at my UMBPCI guide page: http://www.mdgx.com/umb.htm Sound card drivers should not interfere with UMBPCI [unless they are poorly written], because UMBPCI does not occupy any memory, only maps it into UM blocks, which can be used by any properly written software meant to load/work in UMA. And if sound drivers need to occupy UMA areas mapped by UMBPCI, you can always limit the UMA mapped by UMBPCI with the /I=Mxxx-Nyyy switch. ZENO 1.74 [you're right, that's the newest one everybody should use]: http://www.mdgx.com/files/ZENO174.ZIP accelerates certain DOS mode BIOS functions [screen writes], but it does it in a completely different way compared [if you can even compare them] from FastVid or MTRRLFBE. FastVid + MTRRLFBE enable certain video BIOS functions which may not be available on some mobo chipsets, and accelerate the linear frame buffer, banked VGA and write posting. That's why I recommend to use both FastVid [or MTRRLFBE] and ZENO if using native/true/real mode DOS games/apps. HTH

Sorry, forgot about NT4.

You're welcome. I hope this works for you.

UPDATED · 11-21-2006 Updates: - updated IE922760.EXE critical IE 6.0 SP1 fix = fixed INF + SED code. - updated TTFPAK.EXE = added newest fonts [now total of 44] from Win2003 SP2 RC: http://www.microsoft.com/technet/windowsserver/sp2.mspx - updated RUNHELP.EXE = fixed files do NOT work on WinME = now installs only on Win98/98 SP1/98 SE.

noguru: I have fixed the installer. Please download it again [3.61 MB]: http://www.mdgx.com/files/IE922760.EXE Should work ok now. Thanks. ___________________________________ Petr: Thanks for noticing the buggy code. I have fixed the INF + SED code. Notes: - Under the [FileSectionList] section = corrected version strings. Although it installed ok on my Win98 SE computer the 1st time. - Under the [FileSectionList] section = I've renamed %Warn2% to %IEWarn% and also renamed correspondent item IEWarn= under the [strings] section. - _sfx_manifest_ file = I have modified it to adapt it to 9x MSPATCHA.DLL / IEUPDATE.EXE usage, original was for NTx OSes with different file names specific to Win2000. Also removed the [Verify] section code to force it to install the newer QFE versions no matter if code verification matches or not. - I found the reg keys for "CLSID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}",,,"Window List in Shell Process" inside the original INFs from Win2000 SP4 patch. - I have removed the "Active Setup\Installed Components\%GUID%" reg keys from the [user.AddReg] section, and moved them under the [Actsetup.Reg] section, where they should be. HTH

This issue is not related to U891711 as far as I can tell.You may want to look into other system settings or installed programs/updates. HTH

UPDATED · 11-20-2006 Updates: - updated IE922760.EXE critical IE 6.0 SP1 fix = added Q922760 registry values. - updated DXM9X.EXE + DXM9XIE5.EXE = added newest DLLs from Q922760. - updated U891711.EXE = changed install folder + fixed INF (un)install issues.

Looks good to me, if everything works ok on your computer.Let me ask you something: What do you need EMS memory for? Do you play any DOS games that require EMS? If you don't, you can delete the EMM386.EXE line, and replace it with UMBPCI.SYS, which is much faster and occupies way less [or zero] memory. To force UMBPCI to occupy no memory, you need HIRAM.EXE. Complete guide: http://www.mdgx.com/umb.htm#HIR Of course, to use UMBPCI you need a supported mobo chipset. HTH

2000/XP, 98SE + ME all support FAT16 + FAT32. Therefore you can place your 9x swap file [called paging file in 2000/XP] on any FAT16 or FAT32 drive/partition. Try to load XMSDSK from config.sys [example]: INSTALLHIGH=c:\xmsdsk\xmsdsk.exe 720896 Y: /c1 /t /y label Y: Scorpion instead of loading it from autoexec.bat, or the other way around if you load it from config.sys. Replace INSTALLHIGH with INSTALL if you don't load any upper memory manager [uMBPCI, EMM386, QEMM386, RM386 etc] from config.sys. Reboot see what happens. If you allocate too much RAM for xmsdsk RAMdisk, your computer performance will decrease significantly, or you may even experience errors/lockups with some apps/games. If you are experiencing random errors with scandisk [scandskw], maybe you should consider disabling [some] overclocking features, i.e. bring back FSB or RAM timings to normal values. HTH

This installer has been a project I've put on hold for a while, but now I fixed all (un)install issues.Please try again [118 KB]: http://www.mdgx.com/files/U891711.EXE I tested it on my Win98 SE computer, with and without official M$ KB7891711 installed. Works ok. Uninstalls any older U891711 [if any] and M$ KB891711. And it you want to uninstall U891711, just open Control Panel -> Add/Remove Programs. Complete details: http://www.mdgx.com/files/U891711.TXT More info in the U891711 forum: http://www.msfn.org/board/?showtopic=58780 P.S.: Please post all/any U891711 related issues in the dedicated U891711 forum from now on: http://www.msfn.org/board/?showtopic=58780 Thanks. HTH

This is in short what I did [from READ1ST.TXT]: In detail:Replaced BMP, CUR + ICO files with my own [attached into ZIP at bottom of this post]: 100.BMP 101.BMP 102.BMP 300.CUR 301.CUR 302.CUR 303.CUR 306.CUR 200_16.ICO 200_2.ICO using exescope: http://hp.vector.co.jp/authors/VA003525/emysoft.htm#6 Each file name above starts with the respective number found in winfile.exe resources, which you can see when you open winfile.exe in exescope. In exescope [example]: Bitmap -> highlight 100 -> click File -> Import... -> browse to 100.BMP -> double-click on it. Repeat this with all other files listed above, but make sure that filename numbers correspond with winfile.exe resource numbers in exescope. 200_2.ICO = replaces Icon 200 -> 32*32, 2 Color 200_16.ICO = replaces Icon 200 -> 32*32, 16 Color About MORESTAK: Forget about it, it's unnecessary, doesn't help in any way. Please see this post for details: http://www.msfn.org/board/?s=&showtopi...st&p=556609 Consequently, I have removed MORESTAK from my site. If you want to try it, you can find it here: http://www-user.tu-chemnitz.de/~heha/hs_fr...re/morestak.htm P.S.: If you can find another resource editor that works with 16-bit NE (New Executable) files besides exescope, and which supports changing resource file sizes, you may be able to replace the 2 icons above with better 256 colors complex icons [XP style]. If you do, please use WINFILE.ICO, also included in the ZIP attached here, and then please let me know, because I'm looking for such a tool. This is because the two 16 color icons above [200_16.ICO + 200_2.ICO] are ugly. ;( I created PATFM.EXE using Vpatch [free(ware)]: http://www.tibed.net/vpatch/ from modded winfile.exe [target], using WinME setup CD-ROM [English] original winfile.exe as reference [source]. FM_SRC.ZIP HTH

As far as I'm aware, the difference is that official M$ MSI installer copies MSXML4.DLL in %windir%\winsxs\x86_Microsoft.MSXML2_6bd6b9abf345378f_4.20.9841.0_x-ww_18171213 and MSXML4R.DLL is copied in %windir%\winsxs\x86_Microsoft.MSXML2R_6bd6b9abf345378f_4.1.0.0_x-ww_29c3ad6a . Normally both these files should be in %windir%\system .MSXML4A.DLL: I already had this newer version, so it didn't install on my computer. Therefore I don't know the exact dir name without hacking the MSI installer. Unofficial installer installs same files but in correct directory: %windir%\system . So if you install M$ patch first and then the unofficial patch, you'll have 2 copies of same files in different directories. But only the ones in %windir%\system will be used, because those are properly regsvr32-ed [latest install]. The others in %windir%\winsxs\..... can be safely deleted after you install the unofficial patch. HTH

Tihiy: Re: PNGFILT.DLL Could you make a patch for the current version?GDR build = 6.00.2800.1578 QFE build = 6.00.2800.1579 To install PNGFILT.DLL on 98/98 SE/ME [3.62 MB]: http://www.mdgx.com/files/IE922760.EXE To install the GDR build [6.00.2800.1578]: delete [if any] this registry value: REGEDIT4 [HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer] "QFEInstalled"=dword:00000001To install the QFE build [6.00.2800.1579]: add [if not present] registry value above. I'd like better if you can patch 6.00.2800.1579 , because that's the newest 1. Thanks in advance.

Thanks for the reminder.I forgot to mention that this works best with at least 256, 384 or 512 MB of RAM [more the better]. Also, since the swap file is now fixed and maxed out, make sure you assign it a really large size in system.ini [example]: [386enh] PagingDrive=F: PagingFile=F:\WIN386.SWP MinPagingFileSize=819200 MaxPagingFileSize=819200 In this case the swap file is fixed in size at 800 MB [note the identical values for both minimum + maximum size]. If the swap file is fixed in size, there will be no more HD thrashing [swap file resizing]. Also, if the swap file resides on a local hard drive/partition, make sure it's the fastest one [if you have more than 1], preferably partitioned with FAT16 [fastest file system]. Best is to dedicate an entire FAT16 HD partition [2 GB] to the swap file. Or put it on a USB stick [if available], or if you have RAM to spare, create a huge XMSDSK RAM disk [at least 700-800 MB] and put it on it. HTH

Thanks, guys. I've updated Flash + Shockwave links: http://www.mdgx.com/toy.htm#SHFL

98SE2XP:http://www.mdgx.com/982xp/98SE2XP.TXT installs BROWSELC.DLL 6.00.2800.1106 from XP SP1. It does not install BROWSEUI.DLL. Before this week's critical patch was released, newest BROWSEUI.DLL was 6.00.2800.1892 [from obsolete IE918899.EXE]. ____________________________ the_guy: Thanks for the Shockwave link. Updated: http://www.mdgx.com/toy.htm#SHFL

UPDATED · 11-17-2006 Updates: - added IE922760.EXE critical IE 6.0 SP1 fix = replaces IE918899.EXE. - added Q927978.EXE XML 4.0 for IE 5/6 fix = replaces Q925672.EXE. - added Flash 9.0.28.0 player + plugins links. - added Shockwave 10.1.4.020 player + plugins links.

Updates, updates... I've made an unofficial iexpress installer for 98/98 SP1/98 SE/NT4 SP6a/ME [using this Tuesday's M$ IE 6.0 SP1 critical patch for Win2000 SP4]: Unofficial Internet Explorer 6.0 SP1 for Windows 98/98 SP1/98 SE/NT4 SP6a/ME Cumulative BROWSEUI.DLL, DANIM.DLL, DXTRANS.DLL, IEPEERS.DLL, INSENG.DLL, JSPROXY.DLL, MSHTML.DLL, PNGFILT.DLL, SHDOCLC.DLL, SHDOCVW.DLL, SHLWAPI.DLL, URL.DLL, URLMON.DLL + WININET.DLL Security Vulnerabilities Fix (English): http://www.microsoft.com/technet/security/...n/ms06-067.mspx Direct download [3.61 MB]: http://www.mdgx.com/files/IE922760.EXE Replaces IE918899.EXE [obsolete]. Posted here: http://www.mdgx.com/ietoy.htm#IEC I've also made an unofficial iexpress installer for MSXML4.DLL critical update [using Win2000 SP4 patch]: Unofficial Internet Explorer 6.0 SP1 for Windows 98/98 SP1/98 SE/NT4 SP6a/ME XML HTTP MSXML Control v4.0 SP2 MSXML4.DLL Security Vulnerability Fix (English): http://www.microsoft.com/technet/security/...n/ms06-071.mspx Direct download [647 KB]: http://www.mdgx.com/files/Q927978.EXE Posted here: http://www.mdgx.com/ietoy.htm#XML Please try them out. HTH

Thanks, Petr.I see their files located on the fpdownload.macromedia.com server are different from the ones on download.macromedia.com . Links updated: http://www.mdgx.com/toy.htm#SHFL P.S.: Another link to Flash 9.0.28.0 for Firefox, [and probably Netscape 8.x based on Firefox] Mozilla + Seamonkey is this one [XPI (XUL) format]: http://download.macromedia.com/get/flashpl...hplayer-win.xpi In this case the file is identical with the one here: http://fpdownload.macromedia.com/get/flash...hplayer-win.xpi

Probably not, but I don't have DSL connection to test this.___________________________ U891711 is not an official patch from M$, therefore is not listed as a Windows Update.That's why WU [Windows Updates web site] doesn't "see" it on the list of installed patches. Only official M$ patches should be on that list, of course. HTH

1. Yes. This shell32.dll fix [as always with all patches at my site] is cumulative, which means all previous bugs have been fixed in the current version.There are only 2 exceptions that I'm aware of: - LLXX's HD > 137 GB patches [all ESDI_506.PDR versions older than 4.10.2225] are not cumulative: http://www.msfn.org/board/?showtopic=78592 - LLXX's Copy2GB patches [all KERNEL32.DLL versions older than 4.10.2225] are not cumulative: http://www.msfn.org/board/?showtopic=81200 2. No, that's optional. Shell32.dll patch [older version 4.72.3812.610] is an alternative to LLXX's Copy2GB kernel32.dll patch. But the anonymous author of the shell32.dll Copy2GB patch states that shell32.dll fix is better than the kernel32.dll fix. Your choice. This is also specified at my site: http://www.mdgx.com/web.htm#9SU Since shell32.dll is now updated to this newer version, I have installed both on my computer, anyway.HTH

I don't think this is a good one. In my experience I found that it significantly degradated system performance.Some people like this tweak [fixed swap file size] better than the Win98/ME default dynamic swap file:http://www.mdgx.com/98-4.htm#COSW I've been also using it for quite a while, with no noticeable performance degradation. I've also installed this tweak on a couple of friends' Win98SE PCs which I service on a regular basis, also without any problems. Please notice that this tweak depends on the amount of RAM installed. If you have 64 MB or less, do not do this. HTH

I have modified HHUPD.EXE INF to install all files no matter which other versions [even newer] you might have. If you happen to have a newer version, it is from one of the 2000/XP/2003 updates, but you should have the files from HHUPD.EXE, because they are meant specifically for Win9x/ME OSes. I have also added a "finished install" message: "Install completed. You must reboot for this Update to take effect." Your computer will reboot when you click the OK button. IMHO: Personally, I like it better when it reboots automatically without any extra prompts/dialog boxes to click. The text which appears when you first start HHUPD.EXE now lists all files that will be installed [when you click the Yes button] with locations and version builds. So please download the updated file [710 KB, English]: http://www.mdgx.com/files/HHUPD.EXE and try it out. HTH