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 [ 12 | October | 2004 ]

>> Next Message >>


Date: Tue, 12 Oct 2004 04:55:45 PDT7
From: "Harry Motin" <hmotin@sbcglobal.net >
Reply-To: scoug-help@scoug.com
To: "SCOUG Help" <scoug-help@scoug.com >
Subject: SCOUG-Help: Multiple Traps

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

Hello,
I'm hoping someone can help me! I'm having a couple of traps on my system as
follows:

1. Incharge traps, when Info-Zip saving Incharge files during closing of
Incharge

2. FileStar2 traps, when clicking on the "Directory" menu item

I read the June 2001 MrKIA article about how to interpret the trap dump, using Theseus.
But I have a couple of questions. For example, here is the dump from the Incharge trap
(I extracted the trap dump, using the "DumpTrapScreen.cmd" file, as suggested by the
MrKIA article):

Reading A:\DUMPDATA.001 10-11-04 18:28:26

Exception in module:
TRAP XXXX ERRCD=XXXX ERACC=XXXX ERLIM=XXXXXXXX
EAX=XXXXXXXX EBX=XXXXXXXX ECX=XXXXXXXX EDX=XXXXXXXX
ESI=XXXXXXXX EDI=XXXXXXXX EBP=XXXXXXXX FLG=XXXXXXXX
CS:EIP=XXXX:XXXXXXXX CSACC=XXXX CSLIM=XXXXXXXX
SS:ESP=XXXX:XXXXXXXX SSACC=XXXX SSLIM=XXXXXXXX
DS=XXXX DSACC=XXXX DSLIM=XXXXXXXX CR0=XXXXXXXX
ES=XXXX ESACC=XXXX ESLIM=XXXXXXXX CR2=XXXXXXXX
FS=XXXX FSACC=XXXX FSLIM=XXXXXXXX
GS=XXXX GSACC=XXXX GSLIM=XXXXXXXX

P1=00000002 P2=0fa00f1a P3=XXXXXXXX P4=XXXXXXXX
CS:EIP=005b:1c029d01 CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:013dffa8 SSACC=f0f3 SSLIM=ffffffff
EBP=013e00a8 FLG=00012202
EAX=013f0000 EBX=1c7a2c64 ECX=013effbc EDX=0fa00f06
ESI=013ef844 EDI=013eff94
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********

c0000005
15f8182e

P1=00000002 P2=0fa00f1a P3=XXXXXXXX P4=XXXXXXXX
EAX=013f0000 EBX=1c7a2c64 ECX=013effbc EDX=0fa00f06
ESI=013ef844 EDI=013eff94
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:1c029d01 CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:013dffa8 SSACC=f0f3 SSLIM=ffffffff
EBP=013e00a8 FLG=00012202

c0000005
15f8182e
P1=00000002 P2=0fa00f1a P3=XXXXXXXX P4=XXXXXXXX
EAX=013f0000 EBX=1c7a2c64 ECX=013effbc EDX=0fa00f06
ESI=013ef844 EDI=013eff94
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:1c029d01 CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:013dffa8 SSACC=f0f3 SSLIM=ffffffff
EBP=013e00a8 FLG=00012202

C215MT.DLL 0001:0001182e

NOTE: C215MT.DLL is an Incharge DLL. Below, is the trap dump from FileStar2. It's
nearly identical to the Incharge trap:

Reading A:\DUMPDATA.001 10-10-04 08:47:38

Exception in module:
TRAP XXXX ERRCD=XXXX ERACC=XXXX ERLIM=XXXXXXXX
EAX=XXXXXXXX EBX=XXXXXXXX ECX=XXXXXXXX EDX=XXXXXXXX
ESI=XXXXXXXX EDI=XXXXXXXX EBP=XXXXXXXX FLG=XXXXXXXX
CS:EIP=XXXX:XXXXXXXX CSACC=XXXX CSLIM=XXXXXXXX
SS:ESP=XXXX:XXXXXXXX SSACC=XXXX SSLIM=XXXXXXXX
DS=XXXX DSACC=XXXX DSLIM=XXXXXXXX CR0=XXXXXXXX
ES=XXXX ESACC=XXXX ESLIM=XXXXXXXX CR2=XXXXXXXX
FS=XXXX FSACC=XXXX FSLIM=XXXXXXXX
GS=XXXX GSACC=XXXX GSLIM=XXXXXXXX

P1=00000001 P2=00000154 P3=XXXXXXXX P4=XXXXXXXX
CS:EIP=005b:0003f57b CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:000e4334 SSACC=f0f3 SSLIM=ffffffff
EBP=000e43f4 FLG=00012286
EAX=ffffffbf EBX=00000c80 ECX=000e4364 EDX=00000000
ESI=00cbd904 EDI=800001ab
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********

c0000005
0003f57b

P1=00000001 P2=00000154 P3=XXXXXXXX P4=XXXXXXXX
EAX=ffffffbf EBX=00000c80 ECX=000e4364 EDX=00000000
ESI=00cbd904 EDI=800001ab
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:0003f57b CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:000e4334 SSACC=f0f3 SSLIM=ffffffff
EBP=000e43f4 FLG=00012286

c0000005
0003f57b
P1=00000001 P2=00000154 P3=XXXXXXXX P4=XXXXXXXX
EAX=ffffffbf EBX=00000c80 ECX=000e4364 EDX=00000000
ESI=00cbd904 EDI=800001ab
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:0003f57b CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:000e4334 SSACC=f0f3 SSLIM=ffffffff
EBP=000e43f4 FLG=00012286

FILESTAR.EXE 0001:0002f57b

Based on the MrKIA article, I'm not sure if this is a kernel trap or a driver trap. Here are
my questions:

1. What do I do with the CSLIM=XXXXXXXX values? The article did not
say anything about that,

2. Next, for CS:EIP=005b:1c029d01 and CSLIM=ffffffff, I used EIP=005b to
look up the
(16 bit?) driver that seems to be causing the problem. It says the following:

Hdr addr Limit Stategy Limit Name/Units Attr...
0DC8:0000 0005C 0DD0:0000 0005B DOS$ 9880 CHR SHR OPN
LVL=OS/2

OK! I don't know what to do from here. I don't know what DOS$ means. Can you help me
here.

I STRONGLY suspect that these traps are related to my very recent use of the InnoTek
crystal_off.reg file. I use Crystal soundcard drivers on my system. And I also have the
InnoTek Runtime. Recently, when I tried to install ECSMT 2.1.7.6, I got a trap 0008
everytime I tried to open ECSMT. Chuck McKinnis traced the problem to the call that the
new ECSMT makes to the InnoTek iwquery.exe program. The fix was to import the
cystal_off.reg file into the registry editor. That worked. No more ECSMT traps. But
shortly after that I noticed the Incharge and FileStar2 traps.

Question: How do I revert my registry files back to the condition before my importing of
the crystal_off.reg file? Where are the registry files stored? If I know their location, I can
restore them from a backup.

Thanks for any and all help on this.
HCM

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

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


>> Next Message >>

Return to [ 12 | October | 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.