To: thecow who wrote (15531 ) 1/29/2001 6:06:26 PM From: PMS Witch Read Replies (1) | Respond to of 110623 VMM32VXD.VXD ... The file VMM32VXD.VXD is an amalgamation of a few .VXD files. It is created when Win98 is first installed. The motivation behind this is faster booting as systems only need read one large file instead of many smaller ones. This was a good idea, but in the implementation, some hickups were introduced and as a result, Win98 systems using VMM32VXD.VXD may prove less robust. Recent posts have links to people and articles addressing this issue, and as well, some suggestions for circumventing this file. The goal is a boost in system reliability. With today's speedy disks and processors, the increase in time to boot is undetectable. As commonly suggested, most systems have seven 'magic' .VXD files which when copied to the appropriate directory, replace amalgamated code and solve most causes of system crashes. Some even hint that all .VXD file code be used in the form of the original .VXD files, effectively circumventing VMM32VXD.VXD entirely. I'm of the opinion that this is a reasonable approach. After all, if Win98 introduces errors in amalgamating the magic seven, how can I have faith that the others have been dealt with properly? That leaves me with deciding how to proceed. First, I must determine which .VXD files VMM32VXD.VXD contains. I simply check my Registry, and find the files listed under the following key: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\VMM32Files] I highlight this key, (The key's icon opens) and select Export Key after clicking File. REGEDIT saves this key in a .REG file, which looks like this ... ================================================================================ REGEDIT4 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\VMM32Files] "vdd.vxd"=hex:00 "vflatd.vxd"=hex:00 ... <I removed 38 lines from here to make this post shorter> ... "vmouse.vxd"=hex:00 "mtrr.vxd"=hex:00 ================================================================================ This .REG file becomes the basis of a .BAT file to automate the work. A bit of editing and I get a .BAT file that looks like the following. I'm sure every system is different, so don't just cut-and-paste my .BAT file. Each must make their own. Also, substitute the proper letter for the CD and disk drive. My CD is G: and I use F: for messy work. I included REM (Remarks) for clarity, but they could be left out to save typing. My system uses forty- two .VXD files. Other systems may differ. It's a good idea to check C:\WINDOWS\SYSTEM\VMM32 and make sure your system doesn't already have copies of these files in this directory. If it does, don't replace or overwrite them. How this .BAT file works ... It creates a directory \JUNK for temporary use It extracts all .VXD files from the Win98 CD and stores them in \JUNK It copies the .VXD files used to create VMM32VXD.VXD in C:\WINDOWS\SYSTEM\VMM32 It removes the temporary files and directory REM ============================================================================ @ECHO OFF REM REM Extracts .VXD files from Win98 CD REM Win98 uses files in C:\WINDOWS\SYSTEM\VMM32 in place of VMM32VXD.VXD REM By overriding the entire VMM32VXD.VXD, system stability increases REM REM REM REM Files combined into VMM32VXD.VXD are listed under Registry key REM REM [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\VMM32Files] REM REM REM REM Create a temporary directory to hold .VXD files F: MD \JUNK CD \JUNK REM REM REM REM Extract all the .VXD files in all cabinets on Win98 CD REM EXTRACT /A G:\WIN98\WIN98_22.CAB *.VXD REM REM REM REM Copy files from temporary directory REM COPY vdd.vxd C:\WINDOWS\SYSTEM\VMM32 COPY vflatd.vxd C:\WINDOWS\SYSTEM\VMM32 ... <Again, I removed 38 lines from here to make this post shorter> ... COPY vmouse.vxd C:\WINDOWS\SYSTEM\VMM32 COPY mtrr.vxd C:\WINDOWS\SYSTEM\VMM32 REM REM REM Erase temporary directory and contents REM CD F: DELTREE /Y F:\JUNK REM REM REM ============================================================================ Once these .VXD files are located in C:\WINDOWS\SYSTEM\VMM32, they will provide the code Windows uses instead of VMM32VXD.VXD when the system boots. Obviously the system must be booted for the change to take effect. This change can be reversed easily. Edit the .BAT file changing the copy commands to delete. This will remove the files that were added. It would be a good idea to print this post and understand it completely before proceeding. Also, a fresh back-up may prove beneficial. Murphy's law has not been repealed. Cheers, PW.