• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 150
  • Last Modified:

win 95 install

after installing 95 during the hardware find the system stops and  I'm getting an Exception OE 0028:C00046A0 VVD Vmm(01) + 000036A0???
1 Solution
You might have a conflict.  Check your autoexec.bat and config.sys and add REM to the beginnings of all lines.  these 2 key files are no longer needed in Win95 and if they are loading DOS real mode drivers they can conflict with the Win95 driver it is trying to add during the hardware find.  Do this and reboot and see if Win95 loads.  If not, run the install again.  

Stevemiller is correct that sometimes 16-bit drivers loaded in your startup files can cause conflicts when Windows attempts to detect your hardware. Unfortunately, the conflicts are usually related to the CD-ROM or network drivers. If you disable these, you will lose access to the files you are trying to install in the first place (catch 22). To avoid this, make sure you copy setup.* and *.cab from the Windows 95 CD onto your hard drive, then run setup.exe from your hard drive. Make sure your have himem.sys loaded in your config.sys or setup.exe will not run. You can "rem" out everything else though.

If that does not do the trick, there is another problem. Basically, plug and play devices announce themselves to the OS, which is plug and play "aware" and their resources are assigned by the OS. PCI devices work similarly, in that the BIOS controls their resources and therefore Windows 95 can easily detect their presence. Older ISA cards are another story altogether. In order to "detect" these cards, Windows 95 is actually loading a driver into memory, seeing if it gets an expected response, then unloading the driver. Sometimes the driver Windows 95 throws into memory causes a device to behave unexpectedly and lock up the system.

In order to diagnose that type of problem, we will need to know a little bit of detail about the hardware you are running. It may be possible to remove the offending device, load Windows, then install the device again. If you install the offending device AFTER loading Windows 95, you do not have to perform the detection process and can manually load a newer version of the driver for that device.

Let us know how this turns out . . .
Have you made any progree with your problem yet?

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now