32-BIT DRIVERS

Explain? Did you get MSDos compatability mode after a Windows 95 install? What are the components of your system, i.e. hard drive, motherboard, memory? Give us a few more clues as to what you installed, and the hows of it.

Thanks,
Mike

Edited text of question

First you should verify this is your problem.  Go to Control Panel ans start thr System applet.  Click on the performance tab.  This dialog wil tell you if you are using the 16-bit or 32-bit drivers.

Tom

Post your config.sys and autoexec.bat

The 32-bit drivers should either be already supplied by win95 OS, or you should have a disk with your devices.  Check this out.

Steps for running a 32-bit system are as follows--

Autoexec.bat and config.sys- REM all drivers from these 2 files.  Especially CDROM drivers.  Win95 does not require these 2 files and to use them OVERRIDES Win95's startup.

Load win95-- check System propoerties--are you running in MSDOS compatibility mode?  Let me know---

If you are running in optimal performance, your problem is fixed.  let me know, so I can post the answer.

steve

Check http://support.microsoft.com 
for:

Troubleshooting MS-DOS Compatibility Mode on Hard Disks
Last reviewed: May 20, 1998
Article ID: Q130179

and see if this helps.

If Ralph's assumption is correct, you can manage without a reinstall.
Go to "system" in the control panel, in the device manager delete every device you have (do not reboot after each one) and let Windows detect your devices on next startup.
WARNING: Back up your registry first!  This procedure is not foolproof and can screw up your system.

Alex,
What about all the junk that may be left over in the registry from prior software installations, etc?
I think that fooling with that stuff is counter-productive and time-consuming when attempted by someone without experience at it.  My thinking was to clean it all up for best performance via the fastest & simplest methods.
Ralph

>> What about all the junk that may be left over in the registry from prior software installations, etc?

Huh?  If the only stuff changed was the HW, all SW installations will continue to work.
This is similar to your "next best" solution with the added benefit of removing old HW references from the registry[*] which plain reinstall does not do (they are deactivated but remain there).

[*] I'm only 90% sure about this.

I agree with alexo on this one.  At least try it first.  If you are going to reinstall the system anyway it won't hurt.  I have used this technique to clear up hardware driver problems after installing a disk image of Win95.

Tom

Well, I guess I jumped the gun here.
Don't get me wrong guys, I'm not saying that what you suggest won't work.  It's just been my experience that there are issues which tend to tie knots in Win95 when trying to make repairs.
Now I don't know this, because we haven't heard from CHERFOS yet, but I've also assumed (I know, I shouldn't do that!) that along with the new M/B came different memory, video card and possible other changes not mentioned.
Just motherboard components alone (PCI bridges, IDE controllers, etc.) can keep you rebooting and chasing conflicts for hours.
When you do a fresh install in cases such as this, things usually go a lot smoother.
BTW, There are ways to get a re-install to force a clean-up of the registry.  I guess we better hear from CHERFOS now.....
Reject my answer to reopen this for others.
Regards,
Ralph