Solved

Setup locks up detecting hardware.

Posted on 1998-06-11
2
140 Views
Last Modified: 2013-12-16
I'm installing Windows 95 onto a 486sx system that was running Windows 3.11 for workgroups.  During the hardware detect portion the computer locks up and has to be rebooted.  I choose "safe"  mode when prompted and it gets 1% further in the detect screen.  Then I do it again.  After hours of this, Windows 95 is installed.  But when I check the performance tab for the system it tells me that my IDE drive is forcing windows into DOS compatibility mode, degrading performance.   How do I fix this?
0
Comment
Question by:fly64d
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 1

Accepted Solution

by:
tchris earned 50 total points
ID: 1756406
The hardware detection phase of Windows 95 setup probes each and every nook and cranny of your system.  Some of these activites can cause a hardware lockup.  (Note that when the setup wizard says "...if there is no disk activity for a long time..." it means a LONG time!  The hardware detection phase can take more than 10 minutes without noticeable signs of life.  Try letting it sit longer before rebooting.)

While performing the detection, a log file is created.  When you reboot following a hardware lockup, Windows sees the log file, looks for the last entry, and skips that device on the next pass IF, and only IF, you choose "Safe Recovery" when asked to do so.  Note that this is NOT the same as starting Windows in "Safe Mode".  If you don't choose "Safe Recovery" it will hit the same hangups repeatedly.  Perhaps "Safe Recovery" is what you meant in your question?

Another consideration:  Win95 uses clues it finds in your old configuration files (CONFIG.SYS, AUTOEXEC.BAT, WIN.INI, SYSTEM.INI) for hardware configuration.  If any of those settings are incorrect, they may be carried into Win95 incorrectly too.

Try temporarily renaming these files before performing the upgrade, then create a minimal CONFIG.SYS that only has DEVICE=HIMEM.SYS in it and your CD-ROM driver.  The AUTOEXEC.BAT file can get away with only the MSCDEX.EXE line for your CD-ROM drive, and SMARTDRV.EXE for disk caching.  It is usually best to make Win95 figure out all the hardware by itself this way.

Terry
0
 

Author Comment

by:fly64d
ID: 1756407
I gave up and upgraded to a Pentuim.  System now running well.  Thanks.
0

Featured Post

Don't miss ATEN at NAB Show April 24-27!

Visit ATEN at NAB Show to learn how our "Seamlessly Entertaining" solutions deliver fast, precise video streaming without delays for the broadcasting and media environment. ATEN will showcase its 16x16 Modular Matrix Switch (VM1600) and KVM Over IP Solution (KE6900 series).

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
Learn how to PXE Boot both BIOS & UEFI machines with DHCP Policies and Custom Vendor Classes
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question