<< Previous Message <<
Date: | Sun, 20 Aug 2000 12:10:32 PDT |
From: | "Gary Granat" <ggranat@earthlink.net > |
Reply-To: | scoug-help@scoug.com |
To: | < "scoug-help@scoug.com" > scoug-help@scoug.com > |
Subject: | SCOUG-Help: TRAP0003 |
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.
=====================================================
I just finished running EXEINFO on my TRAP0003 problem. This is what I found:
CS:EIP=04d0:00000d65
CS:LIM=000020fd
exeinfo -f -l20fd d:\*.*
D:\OS2\BOOT\RESOURCE.SYS
39992bytes 96-08-12 01:10:48
002 020fe CODE EXECUTEONLY(moveable)
I'm running Warp 4 w/FP12 on both systems. I checked my desktop system and the
RESOURCE.SYS there was 55354 bytes in length and was dated 7-12-99 3:17p, as
was the one on my Utility Diskette set (also at FP12). So, I renamed the
existing driver and copied the one from the Utility Diskette 1 and tried a new
boot. It still traps (TRAP0003) but the values are different:
CS:EIP=04d0:00000deb
CS:LIM=000024e2
exeinfo -f -l24e2 d:\*.*
D:\OS2\BOOT\RESOURCE.SYS
55354bytes 99-07-12 15:17:00
002 024e3 CODE EXECUTEONLY (moveable)
So, the system is still trapping on RESOURCE.SYS, but I have no idea why. It
occurs to me that the CHKDSK /F:3 that I did yesterday scrambled the system
completely and that I might have components from several different fix levels
all trying to run at the same time. Just a thought. If this is the case, I
don't know how far out of luck I might be. I don't know whether/if I could run
the fixpack from the SCOUG CD Of The Month (I have Volume 4.2) with the system
booted from the Utility Diskette set. Any advice on this front? If that
doesn't work, my next fallback is to save the INI files (for application
registration information) and to do a format and reinstall. I'm beginning to
think that it is time to reformat partitions, anyway, because the ThinkPad
hasn't had that done for quite a while (ever, in fact). That means that those
partitions have been running for about three years.
As far as the xWorkplace stuff is concerned, I'm tending to discount it as the
issue, for now, for a couple of reasons: 1) basically, it is a set of
replacement and additional Workplace Shell classes; the Workplace Shell doesn't
even exist at the trap point, and 2) the hook I mentioned that I had activated
is into the Presentation Manager (to intercept and filter messages) and that
part of the system is still dormant when the trap occurs. This is based on my
understanding of how and when various system components are loaded and become
active and on what EXEINFO reports as being "the problem". If anyone has a
better interpretation, let me know.
--gary
=====================
ggranat@earthlink.net
=====================================================
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 [ 20 | August | 2000 ]