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

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


Date: Thu, 16 May 2002 09:21:16 PST7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: SysLog PMWP.DLL errors (was: more on backup using compression software)

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

> Peter Skye said:
>
> >What does a SYSLOGPM "Exception type: c0000005"
> >mean? An 0005 is a Bounds Check . . .

Steven Levine wrote:
>
> You are confusing exception codes with
> Intel trap codes. They are not the same.

Figured that, so I asked. The 0005 was the closest association I could
make.

> Open up your copy of the OS/2
> Debugging Handbook and search for:
> exception code
> To save you the stress of locating
> and, perhaps, installing the Handbook:

There's nothing more stressful over here than having to _find_
something.

> 0C0000005H
> XCPT_ACCESS_VIOLATION
>

Thanks, Steven.

> What I do is maintain a boot log. This is
> pretty much automated. A command in startup.cmd
> writes a timestamp record to the log file and an
> object in the startup folder opens the log file
> in EPM and positions it to the last line.

I remember you do this. I ran into a "glitch" with startup.cmd a while
back -- it seems that the boot process doesn't wait for Startup.cmd to
complete before processing the Startup folder. Hence, you can have the
object in the Startup folder execute _before_ the appropriate line in
startup.cmd is executed. I moved some of my startup.cmd contents to
config.sys so I could control the sequence of execution, but rexx stuff
in config.sys requires special handling and I haven't waded through
rxtt32.inf yet to get the details (you need BOS2REXX.EXE from BOOTOS2
and you can't use some library calls of course).

To open at the end of a file, does EPM have a command line option or do
you use a macro?

> >most of my glitches happen during XCOPY or XCOMP
> >(Roman Stangl's XCOPYesque COMP). These are
> >command line but I still think the Elsa driver
> >has something to do with the "glitches" . . .
>
> Perhaps. Are these local or network copy's? I
> would suspect disk controller or NIC respectively.

Local, they're part of my backup-to-disk procedure.

> What amuses me is the number of folks
> that recommend turning off and/or
> disabling all the failure analysis tools.

Are these the same guys who don't do backups?

> Seems to me, it would be better to
> spend a little time to understand
> what's there and make use of it.

I read a management article yesterday that said great leaders focus on
strategy and tactics, and delegate all the logistics and
infrastructure. Spending "a little time to understand what's there" is
logistics; these folks must all fancy themselves great leaders.

Lunch next week? I'll buy.

- Peter

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

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



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.