Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VMM32.VXD
- Thread starter susando
- Start date
TekTippy4U
Technical User
unfortunately, the solution may not be so simple, though hopefully it is. Vmm32.vxd is a Monolithic combo of about 30-50 drivers specific to your box's hardware and gets created/compiled during Setup.
If you still have probs post back..
You need the 98 CDROM most probably, or the .cab and setup files available to you.
FIRST check the C:\ drive for SYSTEM.1st file
one solution is to
Rename SYSTEM.INI SYSTEM.old
Rename SYSTEM.1st SYSTEM .INI
you'd need to first Copy system.1st from root drive(C:\ usually) to Windows(%winbootdir%), as system.ini resides in the Windows Directory.
Doing this procedure will start Windows as if Hardware Detection was just begun , as is done during Setup (usually 2nd or 3rd reboot during Setup). Basically it'll put Windows Back to that initial phase, which "may" or "may not" be a good idea, depending on which System Restore Disks and OEM disks and Product Key (COA) you have available.....and also drivers for "after Factory" installed Hardware....
TT4U
Notification:
These are just my thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs
If you still have probs post back..
You need the 98 CDROM most probably, or the .cab and setup files available to you.
FIRST check the C:\ drive for SYSTEM.1st file
one solution is to
Rename SYSTEM.INI SYSTEM.old
Rename SYSTEM.1st SYSTEM .INI
you'd need to first Copy system.1st from root drive(C:\ usually) to Windows(%winbootdir%), as system.ini resides in the Windows Directory.
Doing this procedure will start Windows as if Hardware Detection was just begun , as is done during Setup (usually 2nd or 3rd reboot during Setup). Basically it'll put Windows Back to that initial phase, which "may" or "may not" be a good idea, depending on which System Restore Disks and OEM disks and Product Key (COA) you have available.....and also drivers for "after Factory" installed Hardware....
TT4U
Notification:
These are just my thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs
It is a combination of drivers that are called if more recent ones are not found.
Because it is created during setup, I would suggest that the better solution would be an "over the top" reinstall. That will re-create one specific to your hardware, with little risk of corruption. But note that I said little, not none.
Ed Fair
Give the wrong symptoms, get the wrong solutions.
Because it is created during setup, I would suggest that the better solution would be an "over the top" reinstall. That will re-create one specific to your hardware, with little risk of corruption. But note that I said little, not none.
Ed Fair
Give the wrong symptoms, get the wrong solutions.
TekTippy4U
Technical User
The "more recent ones" reside in the C:\WINDOWS\SYSTEM\VMM32 folder
Anything found in here will void/override the monolithic Vmm32.vxd driver
TT4U
Notification:
These are just my thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs
Anything found in here will void/override the monolithic Vmm32.vxd driver
TT4U
Notification:
These are just my thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs
- Status
Similar threads