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

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


Date: Fri, 26 Dec 2003 15:04:53 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.
=====================================================

In , on 12/19/2003
at 07:20 PM, "Steven Levine" said:

>=====================================================
>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 <20031219214837.EE39218E1D1@mx2.zoneedit.com>, on 12/19/03
> at 01:47 PM, jack.huffman@worldnet.att.net said:

>>FixTool 1.42 used to install wr08621 is on the first diskette of te 8621
>>fixpak set. It offers as the first method of installation a boot to a:
>>with the utility diskettes, insert the diskette with 1.42 on it and type
>>FPINST Warp4, then follow the instructions.

>Yes. wr08621 is a normal FP, so you can run fsevice from the command
>line.
> However, you had better do some additional research before proceeding.
>fpinst warp4 is going to try to install a warp4 FP.

Did the research and found that inputting A:\FPINST Warp4 leads to:

if %1. == warp4. goto warp4
:warp4 @Echo Starting FSERVICE ...fservice /r:response.wp4
goto end

I put together this file, response.fil on a:. I know a:\fservice
/r:response.fil must be run to make it usable.

:SOURCE A:\
:FLAGS REPLACE_PROTECTED
:SERVICE
:SYSLEVEL C:\OS2\INSTALL\SYSLEVEL.OS2

The second line allows a chance to see what files,if any, are being back
dated since I will replace newer files if any, that appear.

The last line should restrict updating to my boot drive, c:, so I should
not need to input CSFDRIVEAPPLY=C before I run FPINST but I will rename
the syslevel.os2 file on my maintenance partition just to be sure it is
not changed. I don't think I need ARCHUTIL OFF A: since there is no
archive line in the response file. The CSF 1.42 read me says MPTS fixes
are not archived too.

Changes? Comments?

Thanks.

Happy holidays,

Jack

>>I have an archive from some old fixpak and on't want to create one with
>>this fixpak since I have a backup. Should I use ARCHIUTIL OFF A: as the
>>read. me recommends for 1.42?

>You can do this.

>> I have the impression that, left unchecked, CSF1.42 will try to fix
>>every installation of Warp 4 in different partitions. The quotes below
>>from the CSF1.42 read.me file will show you why.

>Yes. It searches for syslevel files that match up with the FP content.

>>My maintenance partition, I: is a WPS version created by bootos2, it has
>>a syslevel.os2 file that is identical to the one in my boot partition c:.
>> Soo, I want to be sure CSF 1.42 doesn't alter anything in I:. Since I
>>will be working from a:, will SET CSFDRIVEAPPLY=c do the trick?

>You can do that or you can just temporarily rename the syslevel.os2.
>file.

>>And, at last, what do you recommend for any message that says the file
>>being installed by the fix is older than the one it should replace? Keep
>>the newer file? Replace it with the older one?

>In your case, I would probably replace. I doubt it's going to happen
>with MPTS.

>Regards,

>Steven

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

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


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

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