SCOUG-HELP Mailing List Archives
Return to [ 18 | 
January | 
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.  
=====================================================  
 
For the past few weeks I've been getting a bootup trap when SMSTART  
runs.  (I'm Warp 4 Fixpak 10.)  
 
Here are my CONFIG.SYS lines which I used to isolate what part of the  
bootup causes the trap:  
 
  CALL=G:\OS2\CMD.EXE /Q /C G:\BootPaus.cmd TEST POINT 1 SMSTART+  
  RUN=G:\OS2\SMSTART.EXE  
  CALL=G:\OS2\CMD.EXE /Q /C G:\BootPaus.cmd TEST POINT 2 SMSTART-  
 
BootPaus.cmd just displays the specified message and then pauses.  
 
The big problem is that there are two traps displayed, one right after  
the other.  The second one scrolls the top of the first one off the  
screen so I can't see the first few lines.  Is there any way to send  
these trap messages to a file or slow down the display so I can read  
them?  
 
Here's what happens during my bootup:  
 
-- 1. My SMSTART+ message (above) displays and pauses.  I wait a few  
seconds to make sure everything is stable and then press a key to end  
the pause.  
 
-- 2. I hear something running (apparently SMSTART) and then my SMSTART-  
message (above) displays and pauses.  I can still hear disk activity so  
I don't press a key to end the pause.  
 
-- 3. After a few seconds there is a momentary message on the screen  
"Message file not found." and then two multi-line trap messages scroll  
very quickly onto the screen.  The first one partially scrolls off the  
top; the second one says c00000005 and FFST.EXE.  I don't have my docs  
here in San Diego so can't look up a trap 05.  
 
-- 4. I wait a few seconds to make sure everything has stabilized and  
then press a key to end the pause from 2. above.  My bootup proceeds  
normally after I press a key to end the pause.  
 
-- 5. I tried booting with RESTARTOBJECTS=NO to see if some object was  
trying to start and causing the trap, but I got the same traps so that's  
not the cause.  
 
-- 6. UniMaint Repair runs to completion and doesn't fix the problem.   
CheckINI freezes part way through its run (I've tried about 10 times  
now).  CheckINI has been somewhat intermittent over the years on this  
machine; it will work fine for months, then freeze for months, then  
start working again.  I've never figured out what the problem was.  I  
haven't tried CleanINI since it usually messes up my INI files and I  
have to restore them.  
 
Any suggestions on how to see the first trap or what I should do next?  
 
- Peter  
 
 
=====================================================  
 
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 [ 18 | 
January | 
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.
 
 |