SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Thu, 24 May 2001 00:06:31 PDT
From:	Tom Brown <thombrown@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	Help Scoug <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.
=====================================================

Over the past week or so, I have been getting multiple trap screens per
day. They are mostly trap Es with a few trap Cs. The error location is
always the same: 0168 : fff1f322 - 000e : c322. The top of the trap
screen says: "Exception in device driver" but does not give a module
name. Many of the register values are 0, f, or *. The rest of the values
are not the same from one trap to the next, but some have similar or
close values. I cannot think of any change that I made that started this
off. I have tried removing unnecessary drivers from my CONFIG.SYS, but
that has not helped.

My question is: How can I pin this down to the offending module? Can
anyone point me to a debugging procedure?

Thanks!

--
Tom Brown
thombrown@earthlink.net
SCOUG Member
Warp 4.0 + FP15, JAVA 1.1.8
OS/2 system uptime is 0 days 00:00 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".

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

Return to [ 24 | May | 2001 ]

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.