SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 24 | May | 2001 ]

<< Previous Message << >> Next Message >>


Date: Thu, 24 May 2001 16:20:07 PDT
From: Tom Brown <thombrown@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Interpreting Trap error screens

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.
=====================================================

Steven,

OK, I set up the Trapdump on a spare drive. I had NS 4.61 and InJoy 2.30
running as well as a couple of other things that I don't remember. InJoy had
timed out and disconnected, so I clicked the Dial button and it dumped. Here
is what I got from the DumpTrapScreen.cmd:

[F:\]dumptrapscreen -d g:\dumpdata.001
Reading g:\dumpdata.001 05-24-01 15:52:14
Selected 67373 :##01

##0168:fff1f322 - 000e:c322 , 06860642
9084
Selected 536 :Exce

Exception in device driver:
TRAP 000e ERRCD=0000 ERACC=**** ERLIM=********
EAX=00000000 EBX=de6fde6f ECX=000004b1 EDX=00000001
ESI=de6fde6f EDI=fab57af4 EBP=000056d8 FLG=00012206
CS:EIP=0168:f6bbff60 CSACC=c09b CSLIM=ffffffff
SS:ESP=0030:000055f4 SSACC=1097 SSLIM=000048bf
DS=0160 DSACC=c093 DSLIM=ffffffff CR0=8001001b
ES=0160 ESACC=c093 ESLIM=ffffffff CR2=000004b1
FS=0000 FSACC=**** FSLIM=********
GS=0000 GSACC=**** GSLIM=********
Selected 185 :P1=X

How do I use this with THESEUS to find the bad module? Or should I RTFM the
doc for THESEUS?

Thanks!

Steven Levine wrote:

> The best way to capture the trap screen info is with a trap dump. If you
> are not set up for that, get:
>
> http://home.earthlink.net/~steve53/os2diags/DumpTrapScreen.zip
>
> This will allow you to capture the screens from a dump diskette.

--
Tom Brown
thombrown@earthlink.net
SCOUG Member
Warp 4.0 + FP15, JAVA 1.1.8
OS/2 system uptime is 0 days 00:16 hours

=====================================================

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 [ 24 | May | 2001 ]



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.