SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 16 | October | 2004 ]

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


Date: Sat, 16 Oct 2004 10:06:24 PDT7
From: "Harry Motin" <hmotin@sbcglobal.net >
Reply-To: scoug-help@scoug.com
To: "SCOUG Help" <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.
=====================================================

MORE LATE BREAKING NEWS

I seems I can only get up to a certain point with Incharge and it then will again trap, if I
configure it to make a generation backup upon exiting. There are some operations I
can do in Incharge and it won't cause a trap at exit. Then, there are other operations,
like writing checks, that will cause a trap. I switch back to my previous kernel (October
2003). No help there. Interestingly, if I turn off the generation backups, open Incharge
and perform operations and then close it, it of course saves the changes that I made to
the Incharge installation files area. Then, after that, if I reopen Incharge and turn on the
generation backups, close it and allow it to make the backup, it then does so with out a
problem.

Bottomline: If I open Incharge and don't do anything but turn on the generation backups,
it will make the backup and close down without any problems.

However, if I open Incharge and make some changes, then I'll (most likely) get a trap, if
I if then close it down with the auto generation backup feature on.
HCM

==================BEGIN FORWARDED MESSAGE==================
>X-Apparently-To: hmotin@sbcglobal.net via 206.190.37.125; Sat, 16 Oct 2004 07:21:33
-0700
>X-YahooFilteredBulk: 216.184.211.35
>X-Originating-IP: [216.184.211.35]
>Return-Path:
>Received: from 207.115.63.49 (EHLO vml-ext.prodigy.net) (207.115.63.49)
> by mta808.mail.yahoo.com with SMTP; Sat, 16 Oct 2004 07:21:33 -0700
>X-Originating-IP: [216.184.211.35]
>Received: from scoug.com (scoug.com [216.184.211.35])
> by vml-ext.prodigy.net (8.12.10 083104/8.12.10) with SMTP id i9GELV01409270;
> Sat, 16 Oct 2004 10:21:31 -0400
>Received: from www (scoug.com [216.184.211.35] ) by scoug.com
> (Hethmon Brothers Smtpd) ; Sat, 16 Oct 2004 06:59:50 -0700
>Received: from smtp813.mail.sc5.yahoo.com (smtp813.mail.sc5.yahoo.com
[66.163.170.83] ) by scoug.com
> (Hethmon Brothers Smtpd) ; Sat, 16 Oct 2004 06:59:48 -0700
>Message-Id: <200410160659.4850418.8@scoug.com>
>Received: from unknown (HELO HCM) (hmotin@sbcglobal.net@67.114.229.176 with
login)
> by smtp813.mail.sc5.yahoo.com with SMTP; 16 Oct 2004 13:59:47 -0000
>X-Mailer: PMMail 2.20.2382 for OS/2 Warp 4.5
>In-Reply-To:
>MIME-Version: 1.0
>Content-Type: text/plain; charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>Date: Sat, 16 Oct 2004 06:59:49 PDT7
>X-OldDate: Sat, 16 Oct 2004 06:59:47 -0700 (PDT)
>Sender: scoug-help-owner
>X-Listname: scoug-help@scoug.com
>Reply-To: scoug-help@scoug.com
>From: "Harry Motin"
>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.
=====================================================

On Fri, 15 Oct 2004 08:34:53 PDT7, Steven Levine wrote:

OK, here's all the news that is the news:

>OK. To repeat a prior question. Did you make the dump on diskette or to
>a hard drive partition?

I made it on a single diskette (therefore, just the trap screen info). I don't have a FAT
partition to devote to this.

>There's not much more I can do with just the trap screen. I might be able
>to discover addition clues by looking at a full dump file.

Thanks for your offer here, but I really would not ask you do to that! I have a good
workaround to avoid the Incharge trap. I just don't like having to use it.

>Also, if you look at only of your original trap screen posts, you wil see:
>
>
>Reading A:\DUMPDATA.001 10-11-04 18:28:26
>
>Exception in module:
>

>Note that the module name is missing. For true kernel traps, this is
>usally a reporting error and is corrected by newer kernels. I recommend
>you reinstall the 14.100c kernel and see if this kernel can report the
>actual module name.

Yes, I uninstalled and reinstalled the 14.100c kernel at least twice. Still get the same trap
info.

>Finally, at I noted in a prior post, the traps screen look more like
>process traps than kernel traps. There is the possibility you may have
>configured the kernel to trapdump on process traps.
>
>Exactly what did you put in config.sys to enable trap dump?
>
>If you have
>
> trapdump=on
>
>in config.sys, change it to:
>
> trapdump=r0

When back and set it to TRAPDUMP=R0. It did not make a difference. System still went
to the black screen and ATL-CTL-DEL reboot after that.

LATE BREAKING NEWS:
Late last night I found the source of the Incharge trap. Apparently, I had one or more
corrupt files in the Incharge bookset. I don't know how that happened.

What was going on was that I could use Incharge as usual (update my checkbooks,
savings, etc.) but I could no longer configure it to do auto generation backups at exit. If I
tried to use that feature, it trapped during the exit and backup creation. A restart of
Incharge in that condition would produce another, immediate trap. I had to restore
Incharge from a previous backed up generation, one that was OK. Well, I thought I was
going back and restoring from a good backup, but I still could not configure the auto
generation backups. So, I assumed that somehow my system had changed (I'm doing
a lot of updates with ESCMT, etc.) and that was causing the traps. Also, I was getting
traps with ECSMT and FileStar/2 and that was confusing the problem isolation. So, ...,
my workaround at this point was to turn off the auto backup and do manual backups.

Finally, I went back to a backup generation about 1 month old and tried that. That
worked with the auto generation backup. Now, I have to reconstruct about 1 month's
worth of data in Incharge. And I'm working on a set of REXX scripts to automate
backups and restores, so that I don't have to relie totally on the Incharge system.

Thanks for everyone's help during this time. I appreciate it!
HCM

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

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

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

===================END FORWARDED MESSAGE===================

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

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

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


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

Return to [ 16 | October | 2004 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.