SCOUG-HELP Mailing List Archives

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

Date:	Sun, 19 May 2002 18:16:04 PST7
From:	Michael Rakijas <mrakijas@oco.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help <scoug-help@scoug.com >
Subject:	SCOUG-Help: Trap inquiry

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

Okay, folks. This is to follow up a question that I was talking to Steven
about during the meeting yesterday. I'm looking into a trap that's occuring
regularly in a kid's machine. Specifically, I am getting a trap000d in module
HPFS.DLL at shutdown. This happens at every shutdown and occurs after the
desktop disappears but before the drive's dirty flag is cleared. At next boot
up, CHKDSK dutifully runs, finding nothing more than a single "minor file system
error". It clears that and everything seems to work fine afterwards. I suppose
this situation could go on indefinitely with no adverse affect except the
general disquiet of a machine trapping, the delay at reboot and the foreboding
of something worse happening in the future but I'd like to solve it if I can.

I used a few diagnostic tools, all of which I can't remember but I tried DFSee
and it doesn't seem to see any problem. Steven suggested that the system is
having trouble writing to a file and closing it. So, I looked at the trap dump
and below are all the open files at the time of the trap (i.e. all those
recognizable that don't have a \DEV\ in front of them. The list is at the end
of the e-mail. I copied all of them (except those with an asterisk) to a
temporary directory, booted to floppy, and copied them back to the original
location. None seemed to have a problem being written to and then closed. The
ones with an asterisk were locked by another process and I couldn't get to them
to copy over. Since I didn't know their function, I didn't feel comfortable
deleting them after booting to floppy (for the presumed re-creation at next
boot).

Anyone have any ideas? Should I delete the asterisked files? Is it worth
reporting the DFSee info log? Thanks in advance.

-Rocky

C:\IBMCOM\LT0.MSG
C:\IBMCOM\MPTN.MSG
C:\IBMLAN\NETPROG\NET.MSG
C:\IBMCOM\PRO.MSG
C:\DMISL\BIN\SLDB.DMI (*)
C:\OS2\SYSTEM\RAS\LOG0001.DAT (*)
C:\OS2\DLL\DOCK2.CFG
C:\OS2\ETC\SOM.IR
C:\OS2\ETC\WPSH.IR
C:\OS2\ETC\WPDSERV.IR
C:\OS2\ETC\REXX.IR
C:\LOTUSW4\ETC\WPSC2.IR
C:\LOTUSW4\ETC\APPROACH.IR
C:\LOTUSW4\ETC\L14SOM.IR
C:\LOTUSW4\ETC\LTSCTO31.IR
C:\LOTUSW4\ETC\LTSOMO10.IR
C:\LOTUSW4\ETC\LTSRXO20.IR
C:\LOTUSW4\ETC\LTOLSO20.IR
C:\LOTUSW4\ETC\FLG.IR
C:\OS2\SYSTEM\OSO001.MSG
C:\MMOS2\SOUNDS\SPACE\SP_SHUT.WAV
C:\OS2\ETC\SOM.IR
C:\OS2\ETC\WPSH.IR
C:\OS2\ETC\WPDSERV.IR
C:\OS2\ETC\REXX.IR
C:\LOTUSW4\ETC\WPSC2.IR
C:\LOTUSW4\ETC\APPROACH.IR
C:\LOTUSW4\ETC\L14SOM.IR
C:\LOTUSW4\ETC\LTSCTO31.IR
C:\LOTUSW4\ETC\LTSOMO10.IR
C:\LOTUSW4\ETC\LTSRXO20.IR
C:\LOTUSW4\ETC\LTOLSO20.IR
C:\LOTUSW4\ETC\FLG.IR
C:\OS2\SYSTEM\SOMD.MSG

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

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 [ 19 | May | 2002 ]

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.