At 08:21 AM 8/25/2002, you wrote:
>At 8/24/2002 07:03 PM, Ian Porter wrote:
>
>Anyone know what might be calling this W98SE error?
>
>'Exception 0E at 0028:C00CDFC3 in VxD VPD(01) + 0000112F
>called from 0028:C0050D60 in VxD VPICD(01) + 0000099C'
>=========
>
>This is caused by a corrupt Virtual eXtended Driver, VPD.vxd to be exact.
>
>A quote I wrote down from a source long forgotten:
>
>-------
>"If a virtual device driver (VxD) is missing or damaged, Windows 98
>displays an error message that indicates which VxD is involved. If the VxD
>is critical to the operation of Windows 98, then Windows 98 does not start
>and the screen displays the command prompt. You might need to run Windows
>98 Setup and select Verify or Safe Recovery to replace the missing VxD."
>
>But there is an easier solution to this problem.
>
>The generic driver Vmm32.vxd (located in C:\Windows\System) was built when
>you first installed Win98 on your computer. Depending on your hardware
>specs, it may contain some or all of the following VXDs (Virtual eXtended
>Drivers): biosxlat.vxd, configmg.vxd, dynapage.vxd, ebios.vxd, enable.vxd,
>ifsmgr.vxd, int13.vxd, ios.vxd, parity.vxd, reboot.vxd, vcache.vxd,
>vcd.vxd, vcomm.vxd, vcond.vxd, vdd.vxd, vdef.vxd, vfat.vxd, vfbackup.vxd,
>vflatd.vxd, vkd.vxd, vmcpd.vxd, vmouse.vxd, vmpoll.vxd, vpd.vxd, vsd.vxd,
>vtdapi.vxd, vwin32.vxd, vxdldr.vxd. Vmm32.vxd is not only slow to load
>(because of its huge size), but if you have added/changed your hardware
>devices after installing Win98, this old driver might not match your system
>specs anymore.
>
>Certain system errors, like random lockups, error messages at startup, VMM
>errors, erratic and/or slow mouse movement, etc, might be resolved by
>selectively overriding a VXD included within Vmm32.vxd.
>Start by manually extracting one or more of these individual drivers from
>the .CAB files found in the \Win98 folder on your Win98 Setup cd-rom, and
>then copying them to your C:\Windows\System\Vmm32 folder (change the
>Windows folder name if different on your machine). Use this command line
>(example):
>EXTRACT /Y /A D:\WIN98\BASE4.CAB VCOMM.VXD
>
>to extract VCOMM.VXD to the current directory. Typing in the first .CAB
>file name in a given folder (in this case BASE4.CAB), forces EXTRACT.EXE to
>search all CABs in the same directory for the file you specify.
>
>Change the cd-rom drive letter if different on your system.
>Now move VCOMM.VXD to C:\Windows\System\Vmm32, and reboot.
> From now on Win98 will use the individual VXD instead of the one contained
>in Vmm32.vxd, because if the same VXD loads twice, the second instance (in
>this case the one in C:\Windows\System\Vmm32) intercepts all the calls to
>that particular VXD.
>Alternatively you can edit System.ini (located in your Windows folder)
>using Notepad, and add an entry for the VXD you know creates "problems",
>under the [386enh] section. Example:
>
>device=vcomm.vxd
>
>========
Doug is quite correct. Though the solution is much easier than he
proposes above. We maintain a fix file on our web site for Win98 or
Win98Se... it is called VXD_Fix:
http://www.freepctech.com/pc/002/files007.shtml#VXD
This is the most popular download from our web site and cures the
problem the easiest. Just place your Windows98 install CD in the
drive and run this file. It will extract all seven files that comprise the
Vmm32.vxd file and builds you a new one. Typically, this process
will solve BSODs on Windows98 machines.
Bob Wright
The NoSpin Group, Inc.
http://freepctech.com - http://nospin.org
"Hold No Punches.." Rode brings you great shareware/freeware
programs with his honest opinions in this weekly column.
http://freepctech.com/rode
|
