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 [ 20 | December | 2003 ]

>> Next Message >>


Date: Sat, 20 Dec 2003 10:03:24 PST8
From: jack.huffman@worldnet.att.net
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Upgrading tcp/ip stack to 32 bit

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

-------------------------------------------------------------------------
The following message is forwarded to you by jack.huffman@worldnet.att.net
-------------------------------------------------------------------------
>From: jack.huffman@worldnet.att.net
>Date: Fri, 19 Dec 2003 16:05:54 -0500
>To: "Harry Motin"
>Subject: Re: SCOUG-Help: Upgrading tcp/ip stack to 32 bit

In, on 12/19/2003
at 05:26 AM, "Harry Motin" said:

Harry,

After I sent my first post to you, I realized I had not asked if you would
pass along any tips you have for installing wr08621 after installing
wr08610.

I would sure appreciate them because I have questions as you will see if
you read my reply to Steven's post on this thread.

Jack

>Jack,

>I assume that you are trying to upgrade MPTS on a Warp 4.0 system. I
>completed that upgrade on my system and it took a lot of effort, because
>I did not know about all the pitfalls.

>I recommend that you:

> 1. Do the upgrade ONLY on your fully up and running Warp 4.0 system. Do
>not try it from a diskette maintenance installation of Warp.

> 2. Fully backup your system before you do the upgrade and make sure
>that you can do a full restore of your system from that backup (back up
>and make sure that your backup/full restore method works)

> 3. Do the upgrade from full up Warp. You have to be verrrry careful
>using the base installation of MPTS (what you now currently have). The
>Select Install for MPTS does not work, if you have any lines in your
>CONFIG.SYS file that are over 256 characters. Any lines in the
>CONFIG.SYS over 256 will bomb out the install, not just those that deal
>with the MPTS upgrade.

>I have a series of REXX scripts that helped me get around this problem.
>Unfortunately, they use the REXX Library set of functions and you may
>not have that on your system. If you like, I could try to rewrite them
>to use other REXX functions, like the REXX Utility functions, instead.
>If successful, I could E-Mail them to you.

>HCM

>On Thu, 18 Dec 2003 22:50:53 PST8, jack.huffman@worldnet.att.net wrote:

>>=====================================================
>>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.
>>=====================================================
>>
>>I boot to A:\ with updated utility diskettes, put the first WRO8610
>>diskette in the floppy drive, and type "mpts" as the instructions for
>>wr08610 specify. Immediately "SYS1804 The system cannot find the file
>>NLS" appears on the screen.
>>
>>NLS.DLL is loaded by the third utility diskette.
>>
>>Disregarding this fact, I added NLS.DLL to the first WRO8610 diskette.
>>Typing "mpts" at the A:\ prompt results in some floppy activity, Then I
>>get the A:\prompt again and I let it sit like that for a minute or two
>>like that.
>>
>>If someone can tell me what is going wrong, I would sure appreciate it.
>>
>>Jack
>>
>>-----------------------------------------------------------
>>jack.huffman@worldnet.att.net
>>-----------------------------------------------------------
>>
>>
>>=====================================================
>>
>>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".
>>
>>=====================================================
>>
>>

--
-----------------------------------------------------------
jack.huffman@worldnet.att.net
-----------------------------------------------------------

-----------------------------------------------------
-- End of forwarded message
-----------------------------------------------------
--
-----------------------------------------------------------
jack.huffman@worldnet.att.net
-----------------------------------------------------------

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

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

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


>> Next Message >>

Return to [ 20 | December | 2003 ]



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.