Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Trying to boot up my Windows 98 & getting an error message: Vmm32.vxd required to run windows, not in path, reinstall windows. Crt, Alt, Del to restart. Keep getting same results after every reboot. Put startup disk in and same results. Please advise next steps. Thanks.
John Polites
John,
http://support.microsoft.com/?id=kb;en-us;Q194679
You may have to install Windows 98 again.
Good luck.
I - Sandor J
Knowledge is the treasure, but judgment is the treasurer of the wise man.
- William Penn (1614 - 1718)
0 
You can extract a fresh vopy from WIN98_54.CAB on the CD.
Not sure where it belongs. Probably
\windows
or
\windows\system
It may not be the only thing missing. In which case a re-install is in order.
If at first you don't succeed, you're about average.M2
0
Do NOT extract a "fresh copy".
VMM32 is built at install time and is unique to the individual configuration. The one in the CAB files is just a shell.
This error can be caused by a bad install that mucks with the PATH.
You indicate you get the same error with the startup disk?? If so, it sounds like it is NOT booting from that disk, but rather from the harddrive. Ensure that the BIOS settings have the diskette drive before the harddrive.
Or, during the boot sequence, hit F8 to get to a command prompt.
There, enter PATH and post back the results.BTW You don't happen to have the Windows CD in the drive do you? If so, remove it and boot again.
0
You might try this supposed fix.
Also I'd speculated in an earlier thread that since vmm32.vxd apparently doesn't change when hardware or software is added or removed--even changing the motherboard--that a vmm32.vxd copied from another computer might work.
If you'd like to experiment I can send you a copy of vmm32.vxd from my SE machine.
0
Dave:
I believe that the "originally" created file may not change, BUT if any vxds are changed that are part of it, they are dropped into the \Windows\System\VMM32 folder. Windows, as it loads VMM32 will override with any vxds in this folder.
And,not all hardware installs would affect some of these vxds.Also, VMM32 doesn't "just" disappear between boots. I would suspect that if John can get to a DOS prompt, he will find that the file still exists.
0
... and for the future, when you get your machine running again take a backup copy of vmm32.vxd
DerekW
0
Yeah, I've noticed the contents of the vmm32 folder can vary. Ifsmgr, ios and qemmfix are the vxd files put there on a fresh installation. One of my 98 PCs also has Vtdapi.vxd there. And there's one or two other files I've seen in that folder. I suppose having them in the folder is the reason vmm32.vxd isn't updated.
Obviously he should check to see if the file is actually missing. I guess I'm waiting for an opportunity to test my hypothesis.
0
mine changed date about a year ago, so i made a copy of the new .vxd (i keep one in \helpdesk). Now doing a checksum on both they are identical. A list is in the registry:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\VMM32Files]
0
As long as the upgrade will run it won't matter if vmm32.vxd is missing. Typically to recreate the file you reinstall the OS over itself. The same should be true if you upgrade to a newer OS.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
