Windows 98 Drivers Bug
Posted by: Newsfactory on: 09/03/2002 01:46 PM [ Print | 1 comment(s) ] · 3040 views
Just spotted this @ Speedguide.net! I got to say that I run windows 98se and I've not noticed any crashes, not had one for @ least 6 months but hey if it help someone else? you never know.
This bug in the installation of Windows '98 is not reported or confirmed by Microsoft, and there seems to be some controversy on whether extracting the vxds really improves anything. Judging by the hundreds of positive replies we're getting, it fixes numerous problems in the operation of Windows.
Windows '9x / ME does not install some vxd files in your system directory by default, adding them manually has proven to help for a healthy setup with less crashes. To resolve 20 to 50% of the system errors in any Win9x build, extract these vxd files manually from cab 47 and 48 into
c:windowssystemvmm32 and c:windowssystem The following files should be extracted: vcomm.vxd, vdmad.vxd, configmg.vxd, vdd.vxd, vmouse.vxd, ntkern.vxd, vflatd.vxd. Extract these files and reboot. Your system will love you for it. Note: In Windows 98SE, the files are located in CABs 53 and 54.
To check if you need the vxd's yourself, look in the Driver File Details tabs in your Device Manager ( Control Panel > System > Device Manager ). If you find entries containing 'vmm32', there's a good chance you need to extract these manually. For example, in my Modem Driver details, I had " C:WINDOWSSYSTEMVCOMM.VXD (VMM32) " before, and just " C:WINDOWSSYSTEMVCOMM.VXD " after I extracted the vxd's. Note: if you're upgrading, rather than doing a clean install of Windows '98, you might have the old, Windows '95 vxd's in your system. You can check the file versions ( they should be 4.10.1998 ) if you want to find out whether you need the vxd's
This bug in the installation of Windows '98 is not reported or confirmed by Microsoft, and there seems to be some controversy on whether extracting the vxds really improves anything. Judging by the hundreds of positive replies we're getting, it fixes numerous problems in the operation of Windows.
Windows '9x / ME does not install some vxd files in your system directory by default, adding them manually has proven to help for a healthy setup with less crashes. To resolve 20 to 50% of the system errors in any Win9x build, extract these vxd files manually from cab 47 and 48 into
c:windowssystemvmm32 and c:windowssystem The following files should be extracted: vcomm.vxd, vdmad.vxd, configmg.vxd, vdd.vxd, vmouse.vxd, ntkern.vxd, vflatd.vxd. Extract these files and reboot. Your system will love you for it. Note: In Windows 98SE, the files are located in CABs 53 and 54.
To check if you need the vxd's yourself, look in the Driver File Details tabs in your Device Manager ( Control Panel > System > Device Manager ). If you find entries containing 'vmm32', there's a good chance you need to extract these manually. For example, in my Modem Driver details, I had " C:WINDOWSSYSTEMVCOMM.VXD (VMM32) " before, and just " C:WINDOWSSYSTEMVCOMM.VXD " after I extracted the vxd's. Note: if you're upgrading, rather than doing a clean install of Windows '98, you might have the old, Windows '95 vxd's in your system. You can check the file versions ( they should be 4.10.1998 ) if you want to find out whether you need the vxd's
« PC Buyers Guide - September 2002 · Windows 98 Drivers Bug
· ATi RenderMonkey v0.52 Beta Toolsuite »
Comment
|
Anon Unregistered |
#38243 Posted on: 09/03/2002 05:36 PM
This "story" is BS. Here's the deal from a guide I wrote; Like previous versions of Windows 9x, Millennium Edition supposedly “suffers” from the same Missing VXD’s installation problem of “missing” VXD’s (When it actually isn’t a problem). The VMM32.VXD file is a combination of these “missing”, & many others. To see what I mean, click on Start, Run, type regedit & hit Enter. Go to [HKEY_LOCAL_MACHINESystemCurrentControlSetControlVMM32Files]. Listed here are the files that make up VMM32.VXD. Right click on My Computer select Properties. Click the Device Manager tab. Open any Device category, e.g. Modem, then double click on the device listed there. When opened select the Driver tab then the Driver File Details button (Some devices may have this option greyed out so skip onto another one). What you are looking for is any bracketed, (), files. Below is an example of you are trying to find. (screenshot) In this case the vcomm.vxd is bracketed. This essentially means that vcomm.vxd is one of the driver files being used by a device, although it being obtained/loaded via the VMM32.VXD. Basically the point of this is that you do not need to extract any VXD’s from *.cab files & copy them into the WINDOWSSYSTEMVMM32. The files never were missing in the first place. |
