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 [ 31 | July | 2002 ]

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


Date: Wed, 31 Jul 2002 17:07:17 PST7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: significance of Trap E

=====================================================
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 <3D4857B5.446FF6A9@pacbell.net>, on 07/31/02
at 12:33 PM, "J. R. Fox" said:

>One of many details I did not know. Too bad there is no os design (or at
>least none available to
>us) that can just deflect such fatal requests, telling the requesting

This all exists and is available. Most end-users are unwilling to put in
the minimal planning and effort required to use the available tools.

>service "No, you cannot go
>there," and generate a report for the user that makes identifying and
>correcting the error much more

This is somewhat of an oxymoron request. You are asking the kernel which
is doing something wrong to know it's doing something wrong and to
correctly interpret what it is doing wrong so that it can write out an
meaningful diagnostic. This get even more interesting when the kernel is
asked to do this for code it has not control over (i.e. CAD's
kbdbase.sys). When you figure out a design to will implement this, let me
know and we can talk to Peter's patent lawyers.

>ic27649 (which I saw on some past SCOUG cd's), or possibly another
>archive called TCPIPUPD.EXE, but
>that another one, ic32802 was a pre-requisite for these. I was unable
>to locate the latter two.

You should be able to find links at:

http://www.warpupdates.mynetcologne.de/english/site_contents.html

>files in one of the fix archives I did find are dated only a couple weeks
>later. Did they fix that
>much in two weeks time ?

I doubt it. It is probably just different packaging released by different
groups responsible for different support issues.

Steven

--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.31a #10183 Warp4/FP15/14.085_W4
www.scoug.com irc.webbnet.org #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".

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


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

Return to [ 31 | July | 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.