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 [ 09 | August | 2002 ]


Date: Fri, 9 Aug 2002 09:22:38 PST7
From: "J. R. Fox" <jr_fox@pacbell.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: current TCP version level ?

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

Steven wrote:

> Fixpaks are almost always cumulative.

And my best info is that MCP-2 was applied to my eCS, shortly after the base install. But I don't know exactly which components get serviced by that.

You may recall, during the Trap-E thread, that I went looking for some items like ic32802. You suggested that German site, which I scoured without finding this. Subsequently, I did find it on the eCS site. But now, I'm left
wondering whether these (separate) mini-fix archives would be outdated or redundant for me ? (And I don't know what safeguards -- if any -- may be built-in re avoiding redundancy or unintended backlevelling of components,
when you go to install them. My impression is that IBM never did that good a job in the area of systematizing component version levels. Archives are released, withdrawn, superceded, repackaged with different file dates or
archive names, leaving confusion behind as to just what is what. That's why the WarpUp cd, with its system analysis tool, was such a revelation.) My eCS Inetver reports as 6.3. I've seen some of the *same* files from this
group listed in newsgroup messages, claiming the same version level, but they have different dates or file sizes than what I have.

Maybe the short answer is that if what I have seems to be working, leave it alone . . . . And that might go ditto for the testcase kernel I haven't bothered to switch back from.

Jordan

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

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 [ 09 | August | 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.