HELP (Virtual memory manager)

[phandam]

Dear Mr. Simon

I am unable to login to my window, It said, "C:\Windows\System\vmm32.vxd missing\unable to load. after a while it is automatically shut down. I try to reinstall window again but it is still doesn't work. But once in a while I can login to my window. It is required to turn on and off computer two or three time in order to login normal window. How can I fix this problem without reformat my hard drive.

phandam@hotmail.com

[Anonymous]

this should give you some help

Boot to dos only. Extract vmm32.vxd. From the windows cab files to the windows\system.

here's the dope from MS


Err Msg: Cannot Find a Device File That May Be Needed...


The information in this article applies to:

Microsoft Windows 95
Microsoft Windows 98




IMPORTANT: This article contains information about editing the
registry. Before you edit the registry, make sure you understand how
to restore it if a problem occurs. For information about how to do
this, view the "Restoring the Registry" Help topic in Regedit.exe or
the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS
When you start Windows, you may receive the following error message:



Cannot find a device file that may be needed to run Windows or a
Windows application.

The Windows registry or SYSTEM.INI file refers to this device
file, but the device file no longer exists.

If you deleted this file on purpose, try uninstalling the
associated application using its uninstall program or setup
program.

If you still want to use the application associated with this
device file, try reinstalling that application to replace the
missing file.


<filename>.vxd

NOTE: The specific file may not be named.


CAUSE
This error message can occur for either of the following reasons:

A Windows virtual device driver (VxD) referenced in the System.ini
file or registry is missing or damaged.


One of the StaticVxD values in the registry contains invalid data.
For example, the value is blank or contains only spaces. In this
case, the missing device driver is not named in the error message.





RESOLUTION
WARNING: Using Registry Editor incorrectly can cause serious
problems that may require you to reinstall your operating system.
Microsoft cannot guarantee that problems resulting from the
incorrect use of Registry Editor can be solved. Use Registry Editor
at your own risk.

For information about how to edit the registry, view the "Changing
Keys And Values" Help topic in Registry Editor (Regedit.exe) or the
"Add and Delete Information in the Registry" and "Edit Registry
Data" Help topics in Regedt32.exe. Note that you should back up the
registry before you edit it.

To resolve this problem, follow each step below until the error no
longer occurs:

If you have recently removed a program or component, reinstall the
program or component, then run the uninstall tool if one is
available. If no uninstall tool is available for the program or
component, contact the manufacturer to obtain instructions on
uninstalling.


If the missing device driver has a .386 extension, disable the
line referring to this device driver in the System.ini file by
placing a semicolon (;) at the beginning of the line. For example,
if the line referencing the missing device driver reads

device=Example.386

change the line to read

;device=Example.386




If the missing device driver has a .vxd extension, it is a driver
designed for use with Windows 95 or Windows 98 and is referenced
in the registry. In most cases, a program or component with
drivers designed for use with Windows 95 or Windows 98 will also
be listed in the Add/Remove Programs tool in Control Panel.
Following the instructions in step 1 should correct the problem.
For Windows 98
If the error message still occurs after following the instructions
in step 1 or it does not apply, use System File Checker to extract
the missing file from the Windows 98 CD-ROM as follows:


Click Start, point to Programs, point to Accessories, point to
System Tools, and then click System Information.


On the Tools menu, click System File Checker.


Click "Extract one file from installation disk," type the name
of the file you want to extract in the "Specify the system file
you would like to restore" box, and then click Start.


In the Restore From box, type the path to the Win98 folder on
the Windows 98 CD-ROM. Type the destination folder in the Save
File In box if necessary, and then click OK.


Click OK, click OK, and then click Yes when you are prompted to
restart your computer.


For Windows 95
Use the following syntax to extract a file from a known cabinet
file:
extract <cabinet> <filename> /l <destination>
For example, to extract the Windows 95 Unidrv.dll file from the
Win95_10.cab file on a disk in drive A to the Windows\System
folder on drive C, use the following command:
extract a:\win95_10.cab unidrv.dll /l c:\windows\system
For more information about how to extract a file, please see the
following article in the Microsoft Knowledge base:
ARTICLE-ID: Q129605
TITLE : How to Extract Original Compressed Windows Files



If a specific device driver is not named in the error message, one
of the StaticVxD values in the registry is probably blank or
contains only spaces. The StaticVxD values are located in the
registry keys below the following key:


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD


Use Registry Editor to locate and delete any StaticVxD value in
the registry that contains invalid data, is blank, or contains
only spaces.




MORE INFORMATION
When Windows starts, the System.ini file and the registry are read
to obtain a list of device drivers to load. When Windows cannot
locate a virtual device driver that it is attempting to load, an
error message is generated.

Virtual device drivers are files required by various programs to
communicate with your computer's hardware.

The following sample registry key contains a StaticVxD value:


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\COMBUFF

The data for this StaticVxD value is "*COMBUFF" (without the
quotation marks; the quotation marks appear in Registry Editor but
are not part of the VxD name). The asterisk (*) preceding the VxD
name indicates that the VxD is internal to the Vmm32.vxd file. If
the VxD referenced by the StaticVxD value is not internal to the
Vmm32.vxd file, its name is not preceded by an asterisk and
typically has a .vxd extension.


Additional query words:
Keywords : kbenv kberrmsg win95 win98
Version : 95
Platform : WINDOWS
Issue type : kbprb



Last Reviewed: January 20, 1999
© 1999 Microsoft Corporation. All rights reserved. Terms of Use.



Article ID: Q132008
Last Reviewed:
January 20, 1999
Provided by Support Online from Microsoft Product Support Services.



Did the information in this article help answer your question?

Yes
No
Did not apply
Please provide additional comments about this information. If you
require a response or technical support, please click Contact Us.
(255 character max)

[Paul D]

Vmm32.vxd cannot be restored from the Setup CD. It is different for each machine and is built on installation, and the one in the cabinet is just a shell.
http://www.windows-help.net/windows98/vmm32.shtml has some more information.
You'll have to cut & paste the ref - one day they'll fix the bugs in html here.

[southlondon]

Phandam,
I don't want to disappoint you but the same happened to me over a period of about 2 weeks. I kept getting more and more "Blue Screen of Deaths", and with each BSD, a new VMM or VXD problem was encountered.
I have to tell you that even after reformatting numerous times, I was still having problems (don't ask me how - see my Post "Elusive Registry"). I am wondering if there is some kind of new virus that is sitting on the BIOS to avoid deletion, as the way I finally resolved my issue was to clear all CMOS data and reformat again.
Good Luck anyway,
Southlondon.