SCOUG-HELP Mailing List Archives

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

Date:	Tue, 19 Oct 2004 18:20:34 PDT7
From:	"Harry Motin" <hmotin@sbcglobal.net >
Reply-To:	scoug-help@scoug.com
To:	< "scoug-help@scoug.com" > 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.
=====================================================

On Tue, 19 Oct 2004 12:09:24 PDT7, Steven Levine wrote:

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

When I read your instructions, " this will force the directory content to be read and written
elsewhere", I mistakenly took that to mean "open Incharge in the other directory and
attempt to use the auto backup feature". But I guess it didn't.

>> 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?

I mean that the Incharge Info-Zip backups are labelled, XXXXXXX.Z?, where ? goes from
01 to 20 (I create a maximum of 20 backups). The latest backup is 01, the earliest one is
20. Lately, I've been creating these backups, using my REXX script. That way I don't get
into any trouble with traps. BUT, when I turn on the auto backups and Incharge traps,
then installed Incharge on the C:\ drive and the XXXXXXX.Z01 backup are now both
corrupt. I have to get rid of the XXXXXXX.Z01 backup, renumber the remaining backups,
renaming XXXXXXX.02 as XXXXXXX.01, etc., and finally restore Incharge from the new
XXXXXXX.Z01 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,

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

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.