Gape

erpdude8, Thanks for the feedback. But I'm afraid of that 2000, XP and XP SP1 don't have this problem. It occurs only if you use both Windows 98 and IE 6.0.

soldier1st, No, not yet. I already announce any news on this forum, you don't have to ask.

I don't understand the above problem. Is it a particular hotfix? Which one? If a file's revision 2223, it contains only one fix. If it's 2224, it contains two fixes etc. Of course, 2224 revision has 2223's fix. Adding QFECHECK information is a difficult process because of the SP's mechanism. I need a more powerful installer such as InnoSetup or NSIS for these complex processes. But they are some disadvantages, too. (For example, you can't see inside of a InnoSetup file with WinZip/WinRar).

You can uncompress VMM32.VXD with DEVLIB.EXE or VXDLIB.EXE. Both of them are available on Axcel216's site. For example, a compressed VMM32.VXD is 800 KB, after uncompressing it, its size is more than 2 MB. It is still ONE file. I didn't extract any VXD file into VMM32 directory. I tested uncompressed VMM32.VXD with WinTune98 and PCPlayer 3D Benchmark on the April 2000. The results were: Compressed VMM32.VXD: PC Player Direct3D Benchmark - 38.4 Uncompressed VMM32.VXD: PC Player Direct3D Benchmark - 42.8 You're right about the resource problem. Updated VMM32 files in the SP 2.0 is approximately 500 KB, it was 1 MB in the SP 1.x. The reason of difference is VMM.VXD file. I use RPLCLDR.EXE tool (it is also available on the above link) in the SP 2.0 for replacing VMM.VXD (one of the VMM32.VXD files). If we reconstruct the VMM32.VXD with updated files, we can get resources back. But I think the performance doesn't change.

zoem, Could you try to delete VPICD.VXD and VMCPD.VXD from \Windows\System\VMM32 ?

VMM32.VXD is a compressed file of a collection of VXD files. Its contents depend on system configuration. Because it's a compressed file, any corruption affects most of VXD files in it. For example: Assume that you have a ZIP file which has 10 files in it. If this ZIP file corrupts, you cannot extract ANY of these 10 files with using normal ways. On my tests, an uncompressed VMM32.VXD file (still ONE file like a TAR package) has a small performance improvement. But, the booting process is slower a bit, too. In the 2.0, I only copies updated VXD files onto VMM32 directory. Perhaps, a reconstructed VMM32.VXD will be better, but it is not an easy process. Perhaps it will be on the future versions.

Still working on patching process and uninstallation. I can't find a good patcher. I hope I'll release it in this week. Sorry.

zoem, If the reason is your Xircom card, you should revert back to original cbss.vxd file from \Windows\System. Extract cbss.vxd from BASE5.CAB, and copy it into \Windows\System.

It's only better than original Win9x/WinME's Notepad. I've only added some missing shortcuts.

Windows ME with IE 6.0?

This problem comes from IE 6. Because if you use IE 5.5 or older version, you don't have this problem. Problem files are BROWSEUI.DLL and BROWSELC.DLL. The only fix I know is that you must replace these two files with IE 5.5 SP2 versions. For more information, please look at this link. A fix for this problem is not in the SP 2.0, because adding a IE 6.0 specific fix is difficult. I hope I can add it in the 2.1.

It is a good tool, but as I said, generally I don't like to add any 3rd party tool into the SP. If I add a 3rd party tool, it must be useful for most of users. So, this tool is not suitable for the SP.

Announcement: After releasing 98 SE SP 2.0 final, I hope I will work on Windows ME Service Pack.

Only patching process and uninstallation are missing now. Perhaps, if Tarun finds a better way for recreating of VMM32.VXD, I'll add it , too. I hope I'll release RC (Release Candidate) in this weekend. If RC works good, I hope FINAL will released in 1 December.

egorz, Good idea, but I think it's not necessary for 2.0. I can do it for 2.1. I'm very close to finish 2.0, so I'm working on only missing features and testing now. Workaround: Write the option name in a long format. For example, we can write "Adaptec ASPI Drivers Update (Version 4.60.1021)" instead of "ASPI Update".

Look here

What's fixed in this regedit? About Defrag, I should research legal issues, after that perhaps I can add some Windows ME files into the version 2.1.

Windows Installer 3.0 does not support Windows 9x/ME.

Tarun, just for clarification: you say "adding -ANY- WinME file into the Unofficial Service Pack is not a problem". Right?

Adding Windows ME files in a downloadable software is not legal. I think I can only add Windows ME files, if I have to fix a serious Windows 98 problem, so it will be probably in "fair use".

Tarun, I think reconstruction of the vmm32 is a difficult and risky process. Is there an easy way to do it? I have to read information from registry, and INF technology cannot do this.

I don't understand the problem. Can you try to explain? Perhaps, you can add a screenshot...

Tarun, you're right. However, I have to copy these 5 files into \Windows\System\VMM32, because they're updated. But I will only copy these updated files, I will NOT copy other VXD-Fix files.

ujjwal, with the version 2.0, conservative swap file is in the "Performance Tweaks" option. soldier1st, we can discuss this task manager for 2.1.

All drivers of Windows 9x are in the \Windows\Inf. Extract it somewhere. Copy INF file into \Windows\Inf, SYS file into \Windows\System32\Drivers, PDR file into \Windows\System\Iosubsys. To remove these drivers, delete these files.