SCOUG-HELP Mailing List Archives
Return to [ 10 | 
June | 
2004 ]
<< Previous Message << 
 >> Next Message >>
 
 
 
Content Type:   text/plain 
=====================================================  
If you are responding to someone asking for help who  
may not be a member of this list, be sure to use the  
REPLY TO ALL feature of your email program.  
=====================================================  
 
On Wed, 9 Jun 2004 13:40:36 PDT7, DAVID ROSE wrote:  
 
>when you do the alt-f2 and the screen says   
>'loading screen01.sys' is it honestly trying to    
>load the actual screen01.sys driver ...or...the  
>driver before screen01.sys???? if it's screen01,  
>how would specify any other but scitech's(when there  
>is no others)????  
 
 
OK! First, I just want to make DOUBLY sure that you REALLY are seeing the   
screen01.sys driver as the hang, and not some other driver. The point that I am trying to   
make here is that, if you REALLY have not effectuated the "Alt-F2" button, then you are   
REALLY not seeing all the drivers as they load. And if that is the case, your problem   
may not be the screen01.sys driver.  
 
Physically pressing ALT-F2 on some computers will not activate the list of loading   
drivers, because (I believe) some computers are too fast. Basically, the computer   
blows right past your pressing of ALT-F2. IBM had a kernel fix for this, but, in my opinion,   
it was still an "iffy" affair (pressing sometimes worked and sometimes not!).  
 
To know for certain that "ALT-F2" is working, you should first see an list of loading   
drivers, one driver at a time, as it loads on your system. That list remains stationary in   
the lower left hand corner of your monitor. That's important! Later on in the boot   
sequence the list of loading drivers becomes a scrolling list that fills your screen from   
top to bottom and usually moves fast, but sometime halts for a few seconds on one   
driver or another.  
 
On the other hand, if you have not REALLY effectuated ALT-F2, you then get the   
scrolling list, only. And that list does not show all the drivers!  
 
So, ..., which is it? Do you have a scrolling list, only? Or, does your list start out at the   
bottom left of your screen and listing one driver at a time?  
 
 
 
>if not could we make floppies to totaly avoid apm.sys  
>(by rem'ing them in the floppy's config.sys) (if  
>that's the offending driver 'before screen01.sys')???  
 
Reading (and interpreting) the FAQ.TXT information, the hang on the APM.SYS driver   
happens only after you have gotten past phase 1 and you are loading drivers, based   
on the CONFIG.SYS file on your hard drive.  
 
HCM  
 
 
=====================================================  
 
To unsubscribe from this list, send an email message  
to "steward@scoug.com". In the body of the message,  
put the command "unsubscribe scoug-help".  
 
For problems, contact the list owner at  
"rollin@scoug.com".  
 
=====================================================  
 
  
<< Previous Message << 
 >> Next Message >>
Return to [ 10 | 
June | 
2004 ] 
  
  
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.
 
 |