Solved

Setup locks up detecting hardware.

Posted on 1998-06-11
2
141 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

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

In this article, I will show you HOW TO: Install VMware Tools for Windows on a VMware Windows virtual machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, using the VMware Host Client. The virtual machine has Windows Server 2016 instal…
While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

751 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