Reinstalling Windows 95 - Important Issues

Kenn's
Tech
Notes

19981203: Reinstalling Windows 95 - Important Issues

December/1998
Tech Note #3

"Refreshing" Windows 95. Trevor H brought this one to my attention. Sometimes it is helpful to reinstall Windows on top of itself, when a system is acting up. This allows you to freshen the system files without having to reinstall all the software. In Windows 3.1x it was a quick and easy process and often effective in solving "flaky" Windows problems.

In Windows 9x, it is not so quick, not so easy, and it often has undesirable side effects.

For example, on two systems we had re-installed Windows 95 on, the boot process was interrupted by an error "unable to load a driver specified in SYSTEM.INI c:\windows\system\vmm32\ntkern.vxd ... the file is missing or damaged ... press any key to continue" The system would boot, but the error message occurred at every reboot. And oddly enough, "ntkern.vxd" was not specified in SYSTEM.INI!

The reason problems like this occur is that running a "refresh" or "upgrade" install of Windows 95 has the benefit of retaining all existing software settings, but also the downside of redetecting all system hardware, causing driver problems which have to be readdressed. Also, depending on how you answer version conflict messages during the reinstall, you can get a variety of system driver conflicts.

If the system in question had previously had the Px4Patch, Bus Master Driver, and USB Supplement installed, those updates will all have to rerun after the install!

Also, D-Link DE530 drivers will be replaced by the PCI Ethernet DECchip 21041 Based Adapter driver and any new video driver (like the Virge DX) will be replaced by the generic VGA driver. So expect also to have to reinstall video and network drivers.

If the system had LockIt95 installed, LockIt95 has to be reinstalled, too.

If the system has Internet Explorer 4 installed, you will probably have to uninstall IE4, and then reinstall IE4 again, before the system will work properly.

Technicians often have the urge to reinstall Windows to try and quickly determine whether an odd problem is software or hardware. If you opt to do so, please remember all the above-noted issues, and keep your eyes peeled for other software and drivers which may have to be reinstalled.

However, there is another, much easier option, which I recommend. If you have a system which you think has corrupt system files and it is a lab workstation, try the following:

a. Remove the hard drive from the problem workstation, and change the jumper settings so it is set to be slave.
b. Install the hard drive in an identical workstation which is working normally.
c. Detect the hard drive in CMOS.
d. Boot Win 95, and go to the MS-DOS prompt.
e. FORMAT D: /U /Q /V:WSD#1
f. SYS D:
g. XCOPY C:\*.* D:\ /H /I /C /K /E /R
h. Remove the second hard drive, change the jumper settings back to master, and reinstall it in the original workstation.
i. Boot the original workstation and change the computer name back to its original (so it doesn't conflict with the copy).
j. Remember to remove the second hard drive settings in CMOS from the workstation you copied the files on.

At the end of the process you are guaranteed to have a workstation which is identical - in terms of system software configuration - to a working computer. If the same problems recur, you can begin immediately to suspect a hardware problem.

You should be able to complete this whole process in less than an hour. Reinstalling Windows 95 and reinstalling all your drivers, LockIt95, and Internet Explorer 4 (and quite possibly other components, too!) is guaranteed to take longer than an hour, is a lot more aggravation, and because of all the additional fiddling you have to do, you are not guaranteed to have your workstation set up identically to a working system. Therefore, suspecting the hardware following this process is not so assuredly a safe assumption.



DISCLAIMER: This document is intended for the reference of computer support personnel within Winnipeg School Division No. 1. There is no warranty or liability if procedures recommended here have an adverse affect on any systems. Use them at your own risk. Any trademarks mentioned are the property of their owners, none of whom have certified any information provided here. Opinions expressed here are personal only and do not represent the policy of Winnipeg School Division No. 1 or any other organization anywhere.


Got a Tech Note to share? Submissions are most welcome! [Click here.]

To return to the Tech Notes home page, click here.

To download a copy of all the December/1998 Tech Notes in Rich Text Format, click here.
Click here to visit the Information "Super-Cul-De-Sac". This page was updated
2001 June 9


This page hosted by
Get your own Free Homepage
Check out my neighbours here in Silicon Valley Peaks by clicking here.