jmk2
asked on
long pause in startup
I've had to reload Win95 (for the millionth damn time). This most recent time, there is a long pause (20+ seconds) in startup. I stepped through startup. The pause seems to occur initializing the CD device driver (SAME ONE I've always used!). I noticed that IFSHLP.SYS was loaded afterward (This helps backward compatability for device drivers, right?). I moved loading this before it in case that was causing the problem. No difference. CONFIG.SYS has bare SETVER, HIMEM, DOS=HIGH (IFSHLP loads no matter what).
Please don't respont with "Why don't you try reloading Windows again?". I am as much interested in the cause of the problem as the solution.
Please don't respont with "Why don't you try reloading Windows again?". I am as much interested in the cause of the problem as the solution.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
IFSHLP.SYS is loaded whether or not I include a device command for it or not. At the good old Micros**t tech support area there is a description of the boot sequence
http://premium.microsoft.com/support/kb/articles/q174/0/18.asp
This suggests that ifshlp.sys is a "required file" for real mode compatability. I prefer this so I can check dos-mode compatability under windows. (Also, no network installed [unless you count DUN]).
As for the driver, as I mentioned, same driver. Also same command line (inserted by batch setup). I will look for an update later.
As for suggestion of trying plain dos floppy boot, sounds like a good idea (probaby why I didn't think about it). I'll post the result. But I'm still not sure it addresses the problem.
I never thought anything could possibly make me miss Win 3.x. Shows how wrong I can be. NT is down the road a bit.
http://premium.microsoft.com/support/kb/articles/q174/0/18.asp
This suggests that ifshlp.sys is a "required file" for real mode compatability. I prefer this so I can check dos-mode compatability under windows. (Also, no network installed [unless you count DUN]).
As for the driver, as I mentioned, same driver. Also same command line (inserted by batch setup). I will look for an update later.
As for suggestion of trying plain dos floppy boot, sounds like a good idea (probaby why I didn't think about it). I'll post the result. But I'm still not sure it addresses the problem.
I never thought anything could possibly make me miss Win 3.x. Shows how wrong I can be. NT is down the road a bit.
On that last comment, that's what I thought myslef. Honestly, I've hated Windows 3.x the day I got it on my system. Same thing with Windows 95. I now like Windows 3.x _a bit_ for it runs fine on a Pentium. (I had to wait till the Pentium for it to run fast enough :)) Windows NT is, I think, a nice alternative to Windows 95.
ASKER
I have traced the problem to the large-drive utility (EZ-Drive) which is necessary to get DOS5 to recognize the large disk correctly. (I still have some some DOS code out there I have to support.) I know that Win95 doesn't like such utilities, but I have had it and the CD working OK in the past. For the time being, I'm just going to have to work around it.
Thanks to those that offered help.
Thanks to those that offered help.
I get a few seconds delay usually under these condiditons:
1. When my computer is bogged with stuff
2. When my SCSI card for my scanner is installed.
The latter slows down my computer after each refresh - ie wake up from suspended mode, restarting windows without restarting the computer, etc. Just thought i'd mention it...
1. When my computer is bogged with stuff
2. When my SCSI card for my scanner is installed.
The latter slows down my computer after each refresh - ie wake up from suspended mode, restarting windows without restarting the computer, etc. Just thought i'd mention it...
Second, I've been going through the same pain as you with Windows 95. Not that specfic problem, but many others, forcing me to reinstall 12 times in less than a year. At the last crash, I finally gave up and install NT 4.0. It seems much more stable. You might want to think about it, with a multiboot :)
As for this specific problem, try to boot from DOS and see if detecting your CD ROM takes as much time.