said: 
>3 or 4 drivers that load before HPFS.IFS. The longest one takes about 10 
>seconds. Then comes HPFS.IFS. My computer just sits there for the next 8 
>minutes. 
My guess is that it's looking for drives that do not exist.  Exactly what 
is your drive configuration?  What's connected to what? 
Just to be sure that it is the .IFS that's busy, I've attached a copy of 
pause.sys.  Add a device statement pointing to it right after the IFS 
statement for HPFS.IFS.  This way we will be sure what is busy. 
>I just took a look at my CONFIG.SYS and I had a thought. I notice that I 
>have autochecking for my HD partition. I know that it isn't actually 
>going through CHKDSK (unless it needs to). Nevertheless, when CHKDSK has 
>to be run, it takes a long time. Could the autocheck be the timing 
>culprit? 
That's not it.  More likely HPFS.IFS is invoking OS2DASD.DMD looking for 
drives that don't exist.  Have you done a full hardware detection since 
you last shuffled your disk drive setup? 
Also, has the boot up always been slow or is this something new? 
Steven 
--  
--------------------------------------------------------------------- 
"Steven Levine"   MR2/ICE 2.35 #10183 Warp4/FP15/14.085_W4 
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST) 
--------------------------------------------------------------------- 
Content Type: application/x-zip-compressed
File attachment: 
pause2.zip
<< Previous Message << 
 >> Next Message >>
Return to [ 18 | 
January | 
2003 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA  92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group.  ALL RIGHTS 
RESERVED. 
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International 
Business Machines Corporation.
All other trademarks remain the property of their respective owners.