the drivers for the motherboard are different to the ones installed for your
oold motherboard
reisntall

Signature
-- -- -- -- --
Adaware http://www.lavasoft.de
spybot http://www.safer-networking.org
AVG free antivirus http://free.grisoft.com/
Etrust/Vet/CA.online Antivirus scan
http://www3.ca.com/securityadvisor/virusinfo/scan.aspx
Super Antispyware http://www.superantispyware.com/
Panda online AntiVirus scan http://www.activescan.com
Panda online AntiSpyware Scan
http://www.pandasoftware.com/virus_info/spyware/test/
Catalog of removal tools (1)
http://www.pandasoftware.com/download/utilities/
Catalog of removal tools (2)
http://www3.ca.com/securityadvisor/newsinfo/collateral.aspx?CID=40387
Trouble Shooting guide to Windows http://mvps.org/winhelp2002/
Blocking Unwanted Parasites with a Hosts file
http://mvps.org/winhelp2002/hosts.htm
links provided as a courtesy, read all instructions on the pages before
use
Grateful thanks to the authors/webmasters
_
> I installed a different motherboard today with one that came out of a
> Windows 98 machine (no problems with that machine). I get this error when I
[quoted text clipped - 4 lines]
> I DO NOT want to reformat and install clean. Isn't there a vxd file I can
> delete and when I reinstall, its created again.Any ideas?
> I installed a different motherboard today with one that came out of a
> Windows 98 machine (no problems with that machine). I get this error when I
[quoted text clipped - 4 lines]
> I DO NOT want to reformat and install clean. Isn't there a vxd file I can
> delete and when I reinstall, its created again.Any ideas?
If you can boot to safe mode...
delete the enum key in the registry...
the hardware will be re-detetected on bootup...
you may have to hunt down some drivers though
Julie - 27 Dec 2007 02:30 GMT
I can get into safe mode, but deleting enum does not work. Any other ideas?
> > I installed a different motherboard today with one that came out of a
> > Windows 98 machine (no problems with that machine). I get this error when
[quoted text clipped - 13 lines]
> the hardware will be re-detetected on bootup...
> you may have to hunt down some drivers though
philo - 27 Dec 2007 12:40 GMT
> I can get into safe mode, but deleting enum does not work. Any other ideas?
>
[quoted text clipped - 17 lines]
> > the hardware will be re-detetected on bootup...
> > you may have to hunt down some drivers though
You may have to perform a parallel installation...
You can reinstall windows in a 2nd folder and that will essentially give you
a clean install
but you will NOT have to format the drive.
If you do that, all your data willbe there...but all your apps will have to
be reinstalled
and all your custom setting will be lost.
Julie - 27 Dec 2007 15:16 GMT
I'm not worried about my data - its all backed up. What I do want to keep is
exactly what you said i would lose - my apps and custom settings. Isn't
there something else?
> > I can get into safe mode, but deleting enum does not work. Any other
> ideas?
[quoted text clipped - 29 lines]
> be reinstalled
> and all your custom setting will be lost.
philo - 27 Dec 2007 20:15 GMT
> > You may have to perform a parallel installation...
> >
[quoted text clipped - 7 lines]
> > be reinstalled
> > and all your custom setting will be lost.
All I can think of would be to get a motherboard similar to your original
one...
the same chipset etc.
| I installed a different motherboard today with one that came out of a
| Windows 98 machine (no problems with that machine). I get this error
[quoted text clipped - 5 lines]
| I DO NOT want to reformat and install clean. Isn't there a vxd file I
| can delete and when I reinstall, its created again.Any ideas?
VMM32.vxd is the file that likely contains the low-level drivers you
need to replace. It is a monolithic file containing many drivers. It was
my understanding that the file would regenerate during an over-install
of Windows, which I think you said you have done. What is the date on
yours? Here is mine...
C:\>dir c:\vmm32.vxd /s
Directory of C:\WINDOWS\SYSTEM
VMM32 VXD 941,094 07-22-99 12:21a VMM32.VXD
If yours is still the old one, perhaps you must delete it first, per...
http://support.microsoft.com/kb/141898/en-us
Windows 95/98 Boots Directly to "Shut Down" Screen
......Quote the article............
To Re-Create the Vmm32.vxd File
1. Restart your computer.
For Windows 95, when you see the "Starting Windows 95" message, press
the F8 key, and then choose Command Prompt Only from the Startup menu.
For Windows 98, press and hold down the CTRL key after your computer
completes the Power On Self Test (POST), and then choose Command Prompt
Only from the Startup menu.
2. Type the following line to change to the Windows\System folder:
cd \windows\system
3. Type the following line:
ren vmm32.vxd vmm32.old
4. Reinstall Windows 95/98.
NOTE: If you installed Windows 95 from a CD-ROM, you may need to enable
the Mscdex.exe line in the Autoexec.bat file or reinstall the real-mode
CD-ROM drivers included with the CD-ROM drive before you can reinstall
Windows 95. After you enable the real-mode CD-ROM drivers, repeat step 1
to restart the computer.
......EOQ..............................
Notes...
(a) Ensure you have that Mscdex.exe in Autoexec.bat (or at least in
DOSStart.bat) whether or not you are Win95.
(b) To undo instruction 3 (if necessary), reverse the names after "ren".
(c) Some say an over-install of Windows (into the same folder) can lead
to DLL-Hell. If you actually haven't done it yet, you may instead
install Windows into a new folder, as philo said. Then, just copy
VMM32.vxd from that new folder into the current one. Also, you must
change the folder names in MSDOS.sys back to what they are now. Here are
what mine look like...
[Paths]
WinDir=c:\windows
WinBootDir=c:\windows
HostWinBootDrv=c
I think that's all, (but I'm not quite sure). I wonder, what is in your
VMM32 folder? Here is mine...
C:\>dir C:\WINDOWS\SYSTEM\VMM32 /a
Directory of C:\WINDOWS\SYSTEM\VMM32
IFSMGR VXD 186,438 09-19-00 12:57p IFSMGR.VXD
IOS VXD 69,570 04-23-99 10:22p IOS.VXD
MRCI2 VXD 53,403 04-23-99 10:22p MRCI2.VXD
QEMMFIX VXD 9,792 04-23-99 10:22p QEMMFIX.VXD
ESSDRV <DIR> 08-07-01 10:36p ESSDRV
Whatever is in that folder will override a .vxd of the same name inside
the monolithic VMM32.vxd file.

Signature
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net