SCOUG-HELP Mailing List Archives

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

Date:	Tue, 19 Oct 2004 12:09:24 PDT7
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Multiple Traps

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

In <200410190540.2650417.110@scoug.com>, on 10/19/04
at 05:40 AM, "Harry Motin" said:

>> - move the Incharge directory try to another volume
>> this will force the directory content to be read and written elsewhere.
>> - delete the Incharge directory tree
>> - both to a maintenance volumen and chkdsk the original Incharge volume

sheesh. I wish I could proofread. This should have read "boot to a
maintenance volume."

>> - reboot to your production volume
>> - move the files back
>> - use the Incharge install program to recreate any lost Desktop objects
>>
>>If the traps persist, please send me a fresh copy of the data extract by
>>DumpTrapScreen and I will have some further questions.

>I tried your suggestions, all to no avail.

Well sorta. You did take significant poetic license, but you don't seem
to have made anything worse. You certainly did nothing close to what I
suggested.

> 2. Opened Incharge by directly double clicking on the file, sff.exe, in
>that new directory.

I had reasons for not attempting to run Incharge during the move, but oh
well.

> 6. Booted to a maintenance partition, using bootAble. Ran CHKDSK on all
>volumes. I used both the "F:2" and the "F:3" parameter on all volumes.

For those reading along, I generally recommend against running /F:3. It
usually causes more problems than it solves.

> 7. Rebooted and restored Incharge to my C:\ drive, using my last clean
>backup (had to first remove the last backup made, the one that resulted
>in a trap; had to renumber the remaining backups)

I assume you mean the Incharge data backup?

> 11. I'll send you another trap screen dump tonight

OK.

One other possibility is that there is something corrupted in the Incharge
INI file data. None of this should cause ring 0 kernel traps, but one
never knows.

What you might try after you try my original suggestions is to use
Unimaint to deletet the Restoreback key from the Incharge application.
The key data contains some screen specific data that could possibly cause
problems if corrupted.

You might also try Unimaint's EA Test feature on the Incharge directory
tree. It may or may not find EA problems chkdsk misses.

Regards,

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.60b #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------

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

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

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.