Fixpack 15 made really easy (I hope)
Aaron Lawrence
I finally got around to packaging up Warp 4 Fixpack 15 and uploading it
to Hobbes.
ftp://hobbes.nmsu.edu/pub/incoming/fp15.zip
later
ftp://hobbes.nmsu.edu/pub/os2/system/patches/fixpack/fp15.zip
I hope you'll find it appropriately simple:
Download fp15.zip (25MB)
Unzip fp15.zip
Run install.cmd
I've been using this basic arrangement for a while on various computers
at my work here, and it seems to be fine. But if there are problems I'm
sure we can update it or delete it. Give it a try.
Of course I make no guarantee about the *contents* of the fixpack ;-)
For those who care about such things, the zip includes the latest CSF
files (v1.43). My reasoning for including this was:
A) Simplicity:
People don't have to find, download, unzip and configure another file.
B) Makes sense:
Generally you're only installing one fixpack at once, so it doesn't
really matter that we're "wasting" a bit of time downloading CSF.
Especially if it's a new PC.
C) Frequent changes:
IBM keeps changing CSF, so even if you have it, it's likely you won't
have the latest.
D) Simplicity.
Oh wait, I said that. Well, I'll say it again. For years the design of
CSF and it's seperation from the fixpacks made it intimidating to get
fixpacks installed. Even once you've got CSF, you have to figure out
which of the many EXEs to run, and/or which environment variables to
set. Well ... it's all very powerful... but.
If people like this one, I'll package up other relevant fixpacks, like
MPTS or Warp 3 FP40 or non US-English fixpacks.
Cheers
Aaron
Cornelis Bockemuehl
<3A7A7246...@advantagegroup.no.spam.co.nz>:
Sounds great!
Not that I would need it (I installed FP15 yesterday already, and in
german...), but it's exactly the way I am installing fixpaks now for
quite a while: FP as ZIPs, latest CSF and a few-lines batch file
setting the necessary environment variables and starting the thing! I
never had the installation troubles that are reported by so many that
way!
Very strange that IBM didn't publish their fixpaks in exactly that
way already, because for somebody who is not familiar with the issue
even getting the few necessary informations together (e.g., the
environment settings) is not very straightforward!
Greetings,
Cornelis
--
Cornelis Bockemühl
< c b o c k e m @ d a t a c o m m . c h >
PmAs - Astronomy for the Presentation Manager
Homepage: http://home.datacomm.ch/cbockem
Irv Spalten
one is the SIZE of the image and the likelyhood of being able to
complete the d/l without error. More a problem in other parts of the
world than the US.
We've also documented how and what is needed to be done to essentially
make a CD image. See the FixTool documentation in READ.ME file in the
FixTool ZIP file. Specifically section 7.
Irv
Cornelis Bockemuehl
<3A7AC6DC...@us.ibm.com>:
>Cornelis, there are a few reasons why we don't publish like that.
>Major one is the SIZE of the image and the likelyhood of being able
>to complete the d/l without error. More a problem in other parts of
>the world than the US.
>
>We've also documented how and what is needed to be done to
>essentially make a CD image. See the FixTool documentation in
>READ.ME file in the FixTool ZIP file. Specifically section 7.
I understand these reasons very well! And as for myself, you could
probably distribute the FPs in whatever form you want: I would try
and find my way somehow and be glad that they exist at all!
But still I am only talking about what I see: I am reading so many
postings everywhere about people not being able to install FPs for
whatever reason (RSU problems, problems with unpacking DSK files,
maybe also "unability" to read any READMEs...), so this came to my
mind - simply because it worked for me now many times so well! But it
is "home-brew" - and Aaron Lawrence is providing that kind of thing
now "for the rest of the world". Ok, could still be split up in
bunches, for just in case the download makes troubles.
And concerning the more userfriendly RSU option, which is supposed to
be the "one click solution", I indeed never try that, just because of
the fact that I want to make sure I have downloaded everything ok
first before I start with the installation: Both processes can fail,
and I prefer the "divide et impera" solution ;-) (must be something
like "divide and conquer" in english?!?)
Alex Taylor
>>We've also documented how and what is needed to be done to
>>essentially make a CD image. See the FixTool documentation in
>>READ.ME file in the FixTool ZIP file. Specifically section 7.
>
>I understand these reasons very well! And as for myself, you could
>probably distribute the FPs in whatever form you want: I would try
>and find my way somehow and be glad that they exist at all!
>
>But still I am only talking about what I see: I am reading so many
>postings everywhere about people not being able to install FPs for
>whatever reason (RSU problems, problems with unpacking DSK files,
>maybe also "unability" to read any READMEs...), so this came to my
The problem is in the way the README is organized.
It is written in such a way, unfortunately, as to imply that the "first
choice" method of install is to create floppy disks.
Most people, when reading a README, basically scan for the "install"
instructions, and maybe skim the known issues section.
IIRC, the only actual reference about how to install from a non-floppy
drive (other than CID) is a terse description of the CSFCDROMDIR
environment variable, buried under the heading "Environment variables"
near the end of the file. This is not a section, a location, nor a title,
that jumps out at most users to say "this is how you install without
floppies".
As for the CID information... for years I dismissed CID as "wizardry stuff
only LAN admins need to understand" and skipped over any section dedicated
to it.
A mention that floppy disks is only the default mechanism, not the only
one, near the top of the file, might go over well. Maybe a mention of
RSU, as well...
>mind - simply because it worked for me now many times so well! But it
>is "home-brew" - and Aaron Lawrence is providing that kind of thing
>now "for the rest of the world". Ok, could still be split up in
>bunches, for just in case the download makes troubles.
<shamless plug>Or there's my own REXX script + instructions collection for
creating installable FixPak CDs or directories, FIXPAKCD.ZIP in the
FixPaks directory on Hobbes... :)</shameless plug>
--
--------------------------
Alex Taylor
al...@eddie.cis.uoguelph.ca
--------------------------
rj friedman
<aar...@advantagegroup.no.spam.co.nz> wrote:
»Folks,
»
»I finally got around to packaging up Warp 4 Fixpack 15 and uploading it
»to Hobbes.
»
» ftp://hobbes.nmsu.edu/pub/incoming/fp15.zip
» later
» ftp://hobbes.nmsu.edu/pub/os2/system/patches/fixpack/fp15.zip
Slight correction - the file has been moved to:
/pub/os2/system/patches/fixpack/warp_4/fp15.zip
(You seem to have omitted the warp_4 directory in your URL.)
Thank you very much for doing this - it is greatly
appreciated.
--
________________________________________________________
[RJ] OS/2 - Live it, or live with it.
rj friedman Team ABW
Taipei, Taiwan r...@yyyindoserv.com
To send email - remove the `yyy'
________________________________________________________
rj friedman
Bockemuehl) wrote:
»And concerning the more userfriendly RSU option, which is supposed to
»be the "one click solution", I indeed never try that, just because of
»the fact that I want to make sure I have downloaded everything ok...
Hah - me, I'm just the opposite - I ALWAYS try the RSU
option - but it never seems to work for me. It always finds
something wrong with my system and just quits. In the past I
resorted to getting the CDs from BMT and Indelible Blue -
but 20 minutes ago I read the posting by Aaron Lawrence and
decided to try his implementation.
I downloaded it, unzipped it, clicked on the 'install.cmd'
icon, and it went in like clockwork. Rebooted, and here I am
again. Easiest fixpack installation I have ever done, by
far.
life...@xxvol.com
><shamless plug>Or there's my own REXX script + instructions collection
>for creating installable FixPak CDs or directories, FIXPAKCD.ZIP in the
>FixPaks directory on Hobbes... :)</shameless plug>
Uh Oh! Syntax error. Shamless doesn't match shameless. <G>
Jim L
MR/2 ICE, version 2.2
Remove XX from address to Email
Will outlawing guns keep outlaws from using them?
lcl...@lynxus.com
07:31 AM,
Aaron Lawrence <aar...@advantagegroup.no.spam.co.nz> said:
>If people like this one, I'll package up other relevant fixpacks, like
>MPTS or Warp 3 FP40 or non US-English fixpacks.
Omigod, do. Please do. Even the DDPaks.
--
---------------------------------------------
les clark / edgewater, nj / usa
---------------------------------------------
life...@xxvol.com
>>If people like this one, I'll package up other relevant fixpacks, like
>>MPTS or Warp 3 FP40 or non US-English fixpacks.
>Omigod, do. Please do. Even the DDPaks.
Even better, figure SOME way to clear up the TCP/IP update mess.
rj friedman
<aar...@advantagegroup.no.spam.co.nz> wrote:
»If people like this one, I'll package up other relevant fixpacks, like
»MPTS or Warp 3 FP40 or non US-English fixpacks.
I tried it. I loved it. Absolutely the easiest, most
convenient fp installation I've ever done (and I've done
plenty). Thanks a million.
stee...@kickass.com
of zipfile. How did you do this? Is it split into multi parts
like maybe rar's? Is Ftppm.exe on a creaky 24.6k VerizonNY
connection up to such a stunt? IDIS (I doubt it, sir)!
At least RSU has a managed connection and can pick up a dropped
connection. And RSU is grabbing separate files(?), not just the
25mb biggie.
Maybe someone could up/l to Hobbes an 8 part Rar version of the
fixpak? Or Zipsplit. For extra credit, or at least eternal
admiration??
I just honked up $20- for the WarpUP cd (10/2000) thinking it
might be the last fixpak. I'm not *really* into doing that again
for the next fp which might not be all that significant an
improvement anyway.
TIA for any input.
r...@yyyindoserv.com (rj friedman) so spake:
> On Fri, 2 Feb 2001 15:36:23 cbo...@datacomm.ch (Cornelis
> Bockemuehl) wrote:
>
> ŻAnd concerning the more userfriendly RSU option, which is supposed to
> Żbe the "one click solution", I indeed never try that, just because of
> Żthe fact that I want to make sure I have downloaded everything ok...
>
> Hah - me, I'm just the opposite - I ALWAYS try the RSU
> option - but it never seems to work for me. It always finds
> something wrong with my system and just quits. In the past I
> resorted to getting the CDs from BMT and Indelible Blue -
> but 20 minutes ago I read the posting by Aaron Lawrence and
> decided to try his implementation.
>
> I downloaded it, unzipped it, clicked on the 'install.cmd'
> icon, and it went in like clockwork. Rebooted, and here I am
> again. Easiest fixpack installation I have ever done, by
> far.
>
>
> ________________________________________________________
>
> [RJ] OS/2 - Live it, or live with it.
> rj friedman Team ABW
> Taipei, Taiwan r...@yyyindoserv.com
>
> To send email - remove the `yyy'
> ________________________________________________________
>
Vacuo
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
He who votes determines nothing; he who counts the votes
determines everything.
. . . Joseph Stalin ;^/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Aaron Lawrence
can help here.
Aaron Lawrence
Aaron
Aaron Lawrence
>
> Cornelis, there are a few reasons why we don't publish like that. Major
> one is the SIZE of the image and the likelyhood of being able to
> complete the d/l without error. More a problem in other parts of the
> world than the US.
Can you publish in both forms then? For most corporations it would be
easier to do what I've done. (And many home users as well; I don't
consider it miraculous any more to get a 25MB download on my 56k modem).
Anyway, the number of the files isn't so much the problem. The real
problem is the confusing seperation of CSF, and the fact you don't
provide a trivial command file like I've done, to install it from hard
disk. Instructions buried in a many page readme don't count ;-)
Aaron
bste...@redshift.com
>You skip over the real beauty part- downloading 25 bit-perfect mb of
>zipfile. How did you do this? Is it split into multi parts like
>maybe rar's? Is Ftppm.exe on a creaky 24.6k VerizonNY connection up
>to such a stunt? IDIS (I doubt it, sir)!
I recommend using WGET or better yet, AWGET. Works beautifully and can
automatically pickup where it left off after reconnecting.
--
-----------------------------------------------------------
Bob Stephan bste...@redshift.com or BobSt...@compuserve.com
Happily using OS/2 Warp on the Central California Coast.
Visit me at http://www.redshift.com/~bstephan
-----------------------------------------------------------
stee...@kickass.com
> <<snip'd>>
> <shameless plug>Or there's my own REXX script + instructions collection for
> creating installable FixPak CDs or directories, FIXPAKCD.ZIP in the
> FixPaks directory on Hobbes... :)</shameless plug>
>
> --
> --------------------------
> Alex Taylor
> al...@eddie.cis.uoguelph.ca
> --------------------------
Could you please expand and contrast on your program as opposed
to Aaron's fp15.zip, which I just unzipped sucessfully (whew!).
What is an 'installable cd or directory'? I plan to burn fp15.zip
to a cd, but would yours be better for permanent archiving for
some reason? Seems the 'last' fp should be archived in some
fashion.
Darryl Sperber
<aar...@advantagegroup.no.spam.co.nz> wrote:
> If people like this one, I'll package up other relevant fixpacks, like
> MPTS or Warp 3 FP40 or non US-English fixpacks.
Question: how can MPTS and TCP/IP updates which I've always thought HAD to
be applied from diskette be applied from hard drive?
In other words, I myself use the OS2SERV approach to applying OS/2 fixpacks
from harddrive, rather than RSUINST or the old multi-diskette approach. But
that's because OS2SERV is intended to do this.
And now that the "secret recipe" (i.e. the command line operands) is out, we
can download the ZIP files ourselves from the RSU site, unzip them all into
one large directory structure (as the RSUINST method would do), and invoke
the CSF tools through OS2SERV to apply the service directly from this
unzipped large hard drive directory structure.
So the OS2SERV is really sort of a manual version of RSUINST.
Only problem I've encountered so far is I can't seem to COMMIT with SERVICE.
I suspect I may have to create the first diskette of the fixpack to get the
product list, and then maybe SERVICE will be happy with my existing archive
and backup directories. But for now I've just run in an un-committed state.
But I didn't know that MPTS (for the MPTS service) or SERVICE (for the TCP/IP
service) could be run from hard drive rather than from diskette.
Is it actually possible? What's the method? I'm not asking about your
ultimate UNZIP/INSTALL method... I'm asking about how MPTS and SERVICE can
fundamentally be told to get the service input from a single hard drive
directory structure.
Thanks.
--
//
// Darryl Sperber (spe...@airmail.net)
//
ha...@xxxpacbell.net
>
>But I didn't know that MPTS (for the MPTS service) or SERVICE (for the TCP/IP
>service) could be run from hard drive rather than from diskette.
>
>Is it actually possible? What's the method? I'm not asking about your
>ultimate UNZIP/INSTALL method... I'm asking about how MPTS and SERVICE can
>fundamentally be told to get the service input from a single hard drive
>directory structure.
>
Must be beginner's luck, but I've always done it this way ... just used
the cmd program from one of the methods on hobbes (fastkick ?),
put everything in the same directory, diunpacked or dskxtracted
and away we went ... easy.
--
härad ængravvåd
Darryl Sperber
Not so fast...
The files for MPTS and TCP/IP service are only available in DSK format, so
far as I know. There is no RSU (i.e. ZIP) version available, is there.
And that means requiring the use of LOADDSKF to produce diskettes, does it
not? If not, then how does one unpack a DSK format file onto hard drive?
And then how do you "combine" these? Would it be obvious if I simply took my
multiple diskettes and copied the contents back to hard drive? What would be
the directory structure? Or does the LOADDSKF-alternative unpacking utility
(whatever it is) itself create the integrated hard drive directory structure?
And the installation instructions for both of these service groups involve
using programs which read the updatable product from the first diskette, not
to mention running SERVICE from the CSF tools diskette for the TCP/IP update.
So assuming SERVICE can be run from hard drive, how does one avoid requiring
the first diskette of the service to get the product list? Are there
operands to SERVICE to override where it looks, forcing it to look in, just
as OS2SERV has operands specifically intended to provide this?
Same with MPTS. You're supposed to be changed to A:\ when you invoked MPTS.
So how does one avoid that?
> the cmd program from one of the methods on hobbes (fastkick ?),
> put everything in the same directory, diunpacked or dskxtracted
> and away we went ... easy.
Please be more specific. Exactly what was used from Hobbes, and exactly what
sequence of steps or commands (or URL-provided recipe) did you follow?
I'm very interested in this and would love to get MPTS and TCP/IP service off
of diskette and onto hard drive.
Darryl Sperber
> Must be beginner's luck, but I've always done it this way ... just used
> the cmd program from one of the methods on hobbes (fastkick ?),
> put everything in the same directory, diunpacked or dskxtracted
> and away we went ... easy.
(1) Ok, did a bit of looking and answered my first question. You don't use
something provided by IBM, you use DSKXTR12.ZIP from Hobbes. That creates
the directory structure implied in the multiple DSK files, just the same as
UNZIP does. And DSKXTRCT can use a wildcard mask ("?") like UNZIP, so it is
as simple as can be to unpack all the DSK files.
(2) Next question, also apparently answered. MPTS run from the DSKXTRCT'ed
directory opens with the INSTALL button highlighted. This is just as I
remember it would look when running from diskette. Presumably if I pushed
that button it would simply chug along, doing everything it's supposed to and
never asking me for a diskette. Wonderful!!!
Although I don't have to install WR08423 or WR08425, I will be sure to use
this approach the next time I'm forced to reinstall OS/2.
I had no idea that all it took was to recreate the directory structure on
hard drive, run MPTS from there, and it would properly.
(3) Final question, DSKXTRCT'ing the UN_0980 files still doesn't explain how
you run SERVICE pointing to the unpacked hard drive directory. Looking at
the documentation in CSF143 for SERVICE, I can't find how you specify any
source directory through optional operands. There don't appear to be
optional operands.
So what am I not seeing? How does one apply UN_0980 from hard drive using
SERVICE?
Thanks for the tip on DSKXTRCT.
ha...@xxxpacbell.net
>On Mon, 05 Feb 2001 04:08:47 GMT, ha...@XXXpacbell.net wrote:
>
>> Must be beginner's luck, but I've always done it this way ... just used
>> the cmd program from one of the methods on hobbes (fastkick ?),
>> put everything in the same directory, diunpacked or dskxtracted
>> and away we went ... easy.
>
>Not so fast...
you're makng this too hard :-)
>The files for MPTS and TCP/IP service are only available in DSK format, so
>far as I know. There is no RSU (i.e. ZIP) version available, is there.
we don' need no steenkin .zip files, grab the dsk files and ...
>And that means requiring the use of LOADDSKF to produce diskettes, does it
>not? If not, then how does one unpack a DSK format file onto hard drive?
I use diunpack but Trevor says (for sure true if Trevor says it, too !)
that's dumb, you should use dskxtrct because it checks for crc errors ...
don't know where it is but google oughta find it.
>And then how do you "combine" these? Would it be obvious if I simply took my
>multiple diskettes and copied the contents back to hard drive? What would be
>the directory structure? Or does the LOADDSKF-alternative unpacking utility
>(whatever it is) itself create the integrated hard drive directory structure?
>
been a little while, but pretty sure I just make a temp directory. Stick
cs_143.exe in there. Expand (run) CSF 143. Copy all the dsk files in there.
Run diunpack/dskxtrct, the .dsk's will nicely unpack themselves into a
directory structure. Run this cmd file (think it came from fastkick ?)
------------
/* REXX */
'@ECHO OFF'
PARSE SOURCE os2 type invocation
lastslash = LASTPOS('\',invocation)
path = SUBSTR(invocation,1,lastslash-1)
'set CSFUTILPATH='path
'set CSFCDROMDIR='path
path'\SERVICE.EXE'
-------------
wham, bam, thank you ma'am ... done
swear to god that's all I've done for every mpts/tcpip/device driver/
fixpack I've run for the past two years ... seems to me I've had to mess
with the file names on occasion - one of the unpackers doesn't like
*.1DK type names, you have to change to *-1.DSK or similar. That's
been the only peculiarity I can remember ... bet you could do this
from a CD, too ...
--
härad ængravvåd
Darryl Sperber
> I use diunpack but Trevor says (for sure true if Trevor says it, too !)
> that's dumb, you should use dskxtrct because it checks for crc errors ...
> don't know where it is but google oughta find it.
Found it earlier (see my other reply) on Hobbes... DSKXTR12.ZIP.
> been a little while, but pretty sure I just make a temp directory. Stick
> cs_143.exe in there. Expand (run) CSF 143. Copy all the dsk files in there.
> Run diunpack/dskxtrct, the .dsk's will nicely unpack themselves into a
> directory structure. Run this cmd file (think it came from fastkick ?)
>
> ------------
>
> /* REXX */
> '@ECHO OFF'
> PARSE SOURCE os2 type invocation
> lastslash = LASTPOS('\',invocation)
> path = SUBSTR(invocation,1,lastslash-1)
> 'set CSFUTILPATH='path
> 'set CSFCDROMDIR='path
> path'\SERVICE.EXE'
>
> -------------
How about an example of its use (showing operands)?
But now that you've pointed out CSFUTILPATH and CSFCDROMDIR and this REXX, I
was able to find documentation on this in CS_143.TXT down at line 674
describing just these objects.
IBM's usage example (after unpacking the fixpack, and unpacking CSF143) is
something along the lines of:
SET CSFUTILPATH=x:\CSF (note, I already have the tools
unzipped into x:\OS2SERV for
my OS2SERV approach to OS/2
fixpack application, so I would
use that)
SET CSFCDROMDIR=x:\XR_W035 (I would simply point to the
unpacked x:\UN_0980 directory
for TCP/IP, etc.)
x:
CD CSF
SERVICE
So this is how you direct SERVICE to a hard drive location!
And obviously, this is also a suitable alternative to the OS2SERV approach
that I've been using for fixpack application. I don't know that there's any
advantage one way or the other.
So for an OS/2 fixpack where both forms of diskette image (ZIP and DSK) are
available, armed with all of these tools and techniques it doesn't really
matter if you start from the RSU ZIP files and UNZIP them (as RSUINST would
do), or start from the DSK files and DSKXTRCT them. You've going to end up
with the same consolidated hard drive directory structure.
And then, for example, you have a choice of two equivalent methods of
applying the unpacked hard drive resident service (assuming CSF143 was
unzipped into x:\OS2SERV, and FP15 was UNZIP'ed or DSKXTRCT'ed into
x:\XR_M015):
(1) x:
cd os2serv
os2serv x:\os2serv\csf x:\xr_m015
(2) set csfutilpath=x:\os2serv
set csfcdromdir=x:\xr_m015
x:
cd os2serv
service
P.S. - I think the use of CSFUTILPATH and CSFCDROMDIR solves my other
outstanding problem of how to COMMIT my service applied with OS2SERV from
hard drive. That was the missing piece... namely how to direct SERVICE to
the fixpack directory when it wasn't on diskette, in order to do a COMMIT.
This has been TREMENDOUSLY ENLIGHTENING and worthwhile.
Thank you very much for all the leads, directions, and tips.
ha...@xxxpacbell.net
>> ------------
>>
>> /* REXX */
>> '@ECHO OFF'
>> PARSE SOURCE os2 type invocation
>> lastslash = LASTPOS('\',invocation)
>> path = SUBSTR(invocation,1,lastslash-1)
>> 'set CSFUTILPATH='path
>> 'set CSFCDROMDIR='path
>> path'\SERVICE.EXE'
>>
>> -------------
>
>How about an example of its use (showing operands)?
>
Darryl - all ya gotta do is save this rexx program, name it something like
"fix.cmd" Put it in the same directory as your expanded csf program with
the dsk files expanded from that same temp directory. Execute it. Done.
It'll set all the paths and everything. Try it out, you'll like it ...
>This has been TREMENDOUSLY ENLIGHTENING and worthwhile.
>
>Thank you very much for all the leads, directions, and tips.
>
Stop it, you'll give me a swelled head. Even a pig rooting for acorns
finds a truffle sometimes. And I'm glad if this helps make something
easier for someone. All I did was pervert the intent of fastkick ...
--
härad ængravvåd
bob...@home.com
ha...@XXXpacbell.net said:
> Stop it, you'll give me a swelled head. Even a pig rooting for acorns
> finds a truffle sometimes. And I'm glad if this helps make something
> easier for someone. All I did was pervert the intent of fastkick ...
And well done.
--
----------------------------------------------------------------------------------------------
Bob Germer from Mount Holly, NJ - E-mail: bob...@home.com
Proudly running OS/2 Warp 4.0 w/ FixPack 14
MR/2 Ice 2.20 Registration Number 67
"640K ought to be enough for anybody." - Bill Gates, 1981
---------------------------------------------------------------------------------------------
Darryl Sperber
wrote:
> (1) x:
> cd os2serv
> os2serv x:\os2serv\csf x:\xr_m015
>
> (2) set csfutilpath=x:\os2serv
> set csfcdromdir=x:\xr_m015
> x:
> cd os2serv
> service
Well, upon further inspection I must correct myself.
While the OS2SERV program is in the primary unzipped CSF143 directory, the
SERVICE program is not. It is in the \OS2SERV\CSF sub-directory.
So the invocation of SERVICE in (2) above should have been"
x:
cd os2serv\csf
service
Bob Eager
wrote:
> (2) Next question, also apparently answered. MPTS run from the DSKXTRCT'ed
> directory opens with the INSTALL button highlighted. This is just as I
> remember it would look when running from diskette. Presumably if I pushed
> that button it would simply chug along, doing everything it's supposed to and
> never asking me for a diskette. Wonderful!!!
That's right. That works for (say) WR08423 whiich is a 'refresh' as
IBM calls it (a full install). Then things like WR08425 are simply
applied the same as any other fixpack.
I keep a CD around with all of the fixpacks on it (one per
directory)...and this command file in each fixpack directory. A top
level directory contains an unpacked version of the fix tool:
/*
* File: FIX.CMD
*
* Apply service from redirected directory
*
*/
/* Get locations */
parse source . . this
volume = filespec('drive', this)
path = filespec('path', this)
utilpath = volume || '\fixtool'
'@set csfutilpath=' || utilpath
'@set csfcdromdir=' || volume || substr(path, 1, length(path)-1)
utilpath || '\service'
exit
/*
* End of file: FIX.CMD
*
*/
--
Bob Eager
rde at tavi.co.uk
PC Server 325; PS/2s 8595*3, 9595*3 (2*P60 + P90), 8535, 8570, 9556*2,
8580*6,
8557*2, 8550, 9577, 8530, P70, PC/AT..
James J. Weinkam
>
> On Mon, 05 Feb 2001 04:08:47 GMT, ha...@XXXpacbell.net wrote:
>
> > >But I didn't know that MPTS (for the MPTS service) or SERVICE (for the TCP/IP
> > >service) could be run from hard drive rather than from diskette.
> > >
> > >Is it actually possible? What's the method? I'm not asking about your
> > >ultimate UNZIP/INSTALL method... I'm asking about how MPTS and SERVICE can
> > >fundamentally be told to get the service input from a single hard drive
> > >directory structure.
> > >
> >
> > Must be beginner's luck, but I've always done it this way ... just used
> > the cmd program from one of the methods on hobbes (fastkick ?),
> > put everything in the same directory, diunpacked or dskxtracted
> > and away we went ... easy.
>
> Not so fast...
>
> The files for MPTS and TCP/IP service are only available in DSK format, so
> far as I know. There is no RSU (i.e. ZIP) version available, is there.
>
> And that means requiring the use of LOADDSKF to produce diskettes, does it
> not? If not, then how does one unpack a DSK format file onto hard drive?
>
> And then how do you "combine" these? Would it be obvious if I simply took my
> multiple diskettes and copied the contents back to hard drive? What would be
> the directory structure? Or does the LOADDSKF-alternative unpacking utility
> (whatever it is) itself create the integrated hard drive directory structure?
>
<snip>
> I'm very interested in this and would love to get MPTS and TCP/IP service off
> of diskette and onto hard drive.
The fixpacks for mpts and tcpip can all be installed without recourse to floppies. For example the
fixpacks for the version of mpts and tcpip that comes with warp 4.0 are: wr-08423 (6 disk images),
wr_08425 (2 disk images), and un_980 (7 disk images). These must be installed in order with a
reboot after each one. wr_08423 is installed using mpts.exe which is supplied as part of the
fixpack. wr_08425 and un_980 are installed using the service tool csf142 or later (I think. You
might even be able to use earlier ones but I wouldn't recommend it). It is certainly safe to use
the latest, csf143.
First you set up a virtual floppy drive. Several virtual floppy drivers can be found on Hobbes or in
the EWS collection. If the one you use is configurable it should be set up as a 1.44 MB floppy.
For any given fixpack you set up a directory on one of your hard drives to receive the fixpack
structure then do the following for each .dsk file in the fixpack:
Use loaddskf to unpack the .dsk file to your virtual floppy (say drive m:).
Use xcopy with the /h/o/t/s/e/r/v switches to copy the complete directory structure from drive m to
your chosen path.
For wr_08423 you then run mpts.exe. I don't remember for certain exactly what I did, but I think I
just went to the directory containing mpts.exe and ran it. The rest of the fixpack is in the
directory containing mpts.exe and in the structure below it. You then just follow the on screen
directions. The fixpack includes an install.cmd file but I don't remember using it.
For the other two, I include below copies of the .cmd files I used to invoke the fix tool. Needless
to say the must be adapted as necessary.
g:
cd \$rsutmp$\csf
set csfutilpath=g:\$rsutmp$\csf
set csfcdromdir=g:\tcpip\8425\fix
set csfstagedrive=g
set csftimestamp=1
service
g:
cd \$rsutmp$\csf
set csfutilpath=g:\$rsutmp$\csf
set csfcdromdir=g:\tcpip\un980\fix
set csfstagedrive=g
set csftimestamp=1
service
The csfutilpath environment variable specifies the path to the directory containing the fixtool.
The csfcdromdir environment variable specifies the path to the fixpack to be applied.
I set up a tcpip directory on my g drive to pull together all the fixpacks related to
telecommunications. Under it I created directories 8423, 8425, and un980. Each of these contains
the .dsk files any .txt files that came with the package, and any .cmd files that I used to apply
the fixpack. Below each of these directories, I created a FIX directory which is where the root of
each floppy image went. The rest of the directroy structure is built by xcopy following that of the
.dsk images.
Unfortunately, I don't remember at the moment where I saved the .cmd file I used to unpack the disks
but it isn't hard to write one.
Hope this helps. Don't forget to reboot after each fixpack. If you try to do more that one before
rebooting or try to do other operations first you will most likely screw up the processing of the
locked files and leave your system in an inconsistent state. Also it is prudent to do a full backup
before applying any service. Restoring a proper backup is the only certain method for returning the
system to a specific previous state.
rj friedman
»You skip over the real beauty part- downloading 25 bit-perfect mb
»of zipfile. How did you do this?
Nothing to it. I fired up my trusty ENSFTP ftp program (one
of the old Netsuite components now taken over by the guy who
did ZOC, I believe).
»Is it split into multi parts
»like maybe rar's?
Nope - one big file - all you do is unzip it, run
'Install.cmd' and not very minutes later you have an
installed fixpack.
»Is Ftppm.exe on a creaky 24.6k VerizonNY
»connection up to such a stunt?
I didn't have a problem, but I would use a program (like
ENSFTP) that lets you resume a failed download. Even if you
get dropped a couple of times, what's the difference?
--
Irv Spalten
IBM via phone. Before, it had been diskettes, almost 30 of them
depending on OS/2 version. Now, we have a CD. Pop it in your system and
run OS2SERV.
One reason I'd not post it is because it is US ONLY. Sure, might work
for you, but I have obligations around the world. With all the countries
IBM supports, we'd need a TON more of DASD out in Boulder, and more
testing, etc.
If you want the image on CD, call into IBM Support to get it (yes, FP's
are free). Sure, you can't get it the day it is released and have it in
your hands, but it is available, usually 1 week after ship by us. We
need to get the CD produced, test it, and OK it for release.
Irv
Irv Spalten
the files on the disk, RSUINST essentially does this, and it passes
control to OS2SERV. If 'figures out' what it needs to do to allow
SERVICE/FSERVICE (FixTool) run.
Putting together multiple FP's on one CD has some problems. Namely,
LOCKED FILES. It is far safer to install SINGLE product fixes at one
time. You could create DIRECTORIES and hold each product in individual
directories, and ALL files for it goes there. OS2SERV uses the same file
names as well, so you'd need extra copies for it.
Some LAN product FP's are not FixTool format. You'd have to handle those
individually with CMD files probably.
Irv
Alex Taylor
>
>> <shameless plug>Or there's my own REXX script + instructions collection for
>> creating installable FixPak CDs or directories, FIXPAKCD.ZIP in the
>> FixPaks directory on Hobbes... :)</shameless plug>
>
>to Aaron's fp15.zip, which I just unzipped sucessfully (whew!).
>What is an 'installable cd or directory'? I plan to burn fp15.zip
>to a cd, but would yours be better for permanent archiving for
>some reason? Seems the 'last' fp should be archived in some
>fashion.
Mine doesn't contain any FixPaks itself -- it's just a collection of REXX
scripts applicable to any FixPak.
It basically (once set up) lets you install a FixPak by typing a command
like "FIX warp4/fixpak15".
How it works is this: you download the FixPak DSK image files. You use
DSKXTRCT (included in my p ackage, with a REXX script for running it) to
extract these disk image files to the hard drive.
You also need to download CSF143 from the RSU FTP site -- the version
containing OS2SERV.EXE is preferred.
You put the REXX scripts from my package in a directory. You put the
FixPaks in subdirectories of that directory. You unzip CSF143.ZIP into
the same directory as my REXX scripts. (This creates a subdir 'CSF'.)
You should end up with a directory tree something like (you can choose how
to name & organize it yourself, of course):
/
+---CSF
+---Warp4
| +---fixpak12
| +---fixpak15
|
+---Warp3
| +---fixpak40
|
+---TCPIP
+---UN_0959
+---UN_0980
Then you can use the REXX script FIX.CMD which sets all the necessary
environment variables and starts OS2SERV.EXE, or APPLYFIX.EXE which does
the same but runs SERVICE.EXE directly instead.
You can run it from the hard drive, a CD-R, a LAN drive, wherever. It's
probably most useful on a CD-R, that way you can take it to any machine.
As a "one-shot" fixpak application tool, QF (quickfix) is probably easier
to use. But for something reusable, I think my method is easier. (It
doesn't require you to reboot to command-line, unlike QF last time I
checked.)
stee...@kickass.com
> On Sun, 4 Feb 2001 16:47:03 this correspondent wrote:
>
> ŻYou skip over the real beauty part- downloading 25 bit-perfect mb
> Żof zipfile. How did you do this?
Of course, after making a hardcopy kvetch about it, I was able to
d/l the whole 25mb file after all. Maybe 'cause it was Sunday?
3.5 hrs @2.1k/sec.
But true to form I blew away the first 8+mb by hitting the
'saving location>cancel' button instead of minimizing the window!
(Netsc 4.61- nice feature having NO confirm on 'Cancel' ! ! !)
But I was able to increase cache size on-the-fly so Ntesc would
hold the whole 25mb. Nice.
Thanx for the AwGet and EnsFTP suggestions. I registered Emtec
news, but not the ftp; ZOC was the cat's meow back then-
definitely feature-laden.
Vacuo
Bengt Johansen
Darryl Sperber wrote:
>
> On Fri, 02 Feb 2001 07:31:04 GMT, Aaron Lawrence
> <aar...@advantagegroup.no.spam.co.nz> wrote:
>
> > If people like this one, I'll package up other relevant fixpacks, like
> > MPTS or Warp 3 FP40 or non US-English fixpacks.
>
-- snip -- snip -- snip --
>
> But I didn't know that MPTS (for the MPTS service) or SERVICE (for the TCP/IP
> service) could be run from hard drive rather than from diskette.
>
> Is it actually possible? What's the method? I'm not asking about your
> ultimate UNZIP/INSTALL method... I'm asking about how MPTS and SERVICE can
> fundamentally be told to get the service input from a single hard drive
> directory structure.
>
Here is how I do it: first i create a directory structure...
X:\FIXES
+ csf --> unzip csf143.zip or latest to make this directory
+ ip08414
+ wr08610 --> run install.cmd for this one
+ wr08621
+ un_0980
using dskxtrct.exe: from a temorary directory with the disk image files:
eg.
dskxtrct /s:IP08414.?DK /t:X:\FIXES\ip08414 /rn /la
then i run my little apply.cmd for each of the fixpaks: eg. (apply
ip08414)
dont forget to reboot in between!!!
the apply.cmd:
---
/* */
'@Echo off'
Call RxFuncAdd 'SysLoadFuncs', 'REXXUTIL', 'SysLoadFuncs'
Call SysLoadFuncs
Parse Arg fixdir .
curdir = directory();
Parse source . . me .
path=Filespec('DRIVE',me)||Filespec('PATH',me)||fixdir
If right(path,1)='\' Then
path=left(path,length(path)-1)
'SET CSFCDROMDIR='path
tool=Directory('.')||'\CSF'
'SET CSFUTILPATH='tool
/*****************/
/* Start service */
/*****************/
Call Directory(tool)
'@START SERVICE'
---eof---
--
regards
Bengt Johansen
ICQ # 26533206
Jim Smith
This was the easiest fixpack install I've ever done.
Way to go Aaron
Thanks
Jim Smith
Aaron Lawrence wrote:
> Folks,
>
> I finally got around to packaging up Warp 4 Fixpack 15 and uploading it
> to Hobbes.
>
> ftp://hobbes.nmsu.edu/pub/incoming/fp15.zip
> later
> ftp://hobbes.nmsu.edu/pub/os2/system/patches/fixpack/fp15.zip
>
> I hope you'll find it appropriately simple:
>
> Download fp15.zip (25MB)
> Unzip fp15.zip
> Run install.cmd
>
> I've been using this basic arrangement for a while on various computers
> at my work here, and it seems to be fine. But if there are problems I'm
> sure we can update it or delete it. Give it a try.
>
> Of course I make no guarantee about the *contents* of the fixpack ;-)
>
> For those who care about such things, the zip includes the latest CSF
> files (v1.43). My reasoning for including this was:
>
> A) Simplicity:
> People don't have to find, download, unzip and configure another file.
>
> B) Makes sense:
> Generally you're only installing one fixpack at once, so it doesn't
> really matter that we're "wasting" a bit of time downloading CSF.
> Especially if it's a new PC.
>
> C) Frequent changes:
> IBM keeps changing CSF, so even if you have it, it's likely you won't
> have the latest.
>
> D) Simplicity.
> Oh wait, I said that. Well, I'll say it again. For years the design of
> CSF and it's seperation from the fixpacks made it intimidating to get
> fixpacks installed. Even once you've got CSF, you have to figure out
> which of the many EXEs to run, and/or which environment variables to
> set. Well ... it's all very powerful... but.
>
> If people like this one, I'll package up other relevant fixpacks, like
> MPTS or Warp 3 FP40 or non US-English fixpacks.
>
> Cheers
>
> Aaron
life...@xxvol.com
>Ah yes... a very beautiful thing. But I don't know that anyone but IBM
>can help here.
>> Even better, figure SOME way to clear up the TCP/IP update mess.
It sounds like you are saying it is impossible for anyone but IBM to
figure it out. I know it has proven impossible for me to figure out,
but I've seen posts that talk about people doing it. I can't remember
anything in the posts, but I remember such subjects have been posted.
There was one web site that had a pretty good list of what was
necessary, but I lost the URL. Someone gave me a URL that I thought was
it, at first, but when I tried to figure out how to update things, I
discovered that it covered a zillion variations on as many separate
pages. I couldn't even figure out the sequence of pages, let alone the
sequence of updating.
I hope I can find that URL again.
Jim L
MR/2 ICE, version 2.2
Remove XX from address to Email
Will outlawing guns keep outlaws from using them?
Darryl Sperber
> I hope I can find that URL again.
(0) Create appropriate directories on your hard drive for the download of
necessary files, and the unpacking of the diskette or ZIP images. I suggest
the following structures:
x:\OS2SERV target for CSF143.ZIP
x:\FIXPAK target for all fixpack diskette sets, DSK or ZIP
\WR08423
\WR08425
\UN_0980
\DOSBOX
\XR_M015 (for FP15)
\XR_D002 (for device driver fixpack 2)
Presumably you have the current UNZIP. If not, you can obtain the latest
v5.42 (including support for UNSHRINK) from:
ftp://hobbes.nmsu.edu/pub/os2/util/archiver/uzs542x2.exe
The latest versions of the "official" product (in all flavors, including
Win9x, etc.) is available from the InfoZip site (although the OS/2 version
does not contain support for UNSHRINK):
ftp://ftp.info-zip.org/pub/infozip/
You can also get the latest ZIP product (latest is v2.3) there as well.
(1) MPTS updates WR08423, followed by WR08425 (both can be obtained from the
following link):
ftp://service.boulder.ibm.com/ps/products/mpts/fixes/english-us/
You need to apply both WR08423 and WR08425. Download all diskette images of
both fixpacks into the appropriate target directory. They will be expanded
using DSKXTRCT.
(2) DOSBOX
ftp://service.boulder.ibm.com/ps/products/tcpip/fixes/dosbox/latest/
Download DOSBOX.EXE into the appropriate target directory. DOSBOX.EXE is a
self-expanding ZIP file. Just run it to expand, and look at the README.
Of the five files in this collection, three of them are included as part of
UN_0980. For some reason, two of the files are not. You'll have to manually
copy these two "orphans" to the proper target locations, and you may need to
be booted to a command prompt to do that because the files may be locked when
WPS is running:
VDOSTCP.SYS ---> x:\TCPIP\BIN
WINSOCK.DLL ---> x:\TCPIP\DOS\BIN
(3) TCP/IP UN_0980
ftp://service.boulder.ibm.com/ps/products/tcpip/fixes/v3.1os2andv4.0os2/universal/un_0980/
Download all diskette images into the appropriate target directory. They
will be expanded using DSKXTRCT.
(4) You'll need the latest fixtools application package, CSF143.ZIP to apply
virtually all of IBM maintenance (including the above MPTS and TCP/IP
services):
ftp://service.boulder.ibm.com/ps/products/os2/rsu/
Download to the OS2SERV directory and unzip.
(5) You'll want DSKXTRCT, available from Hobbes, to unpack the fixpacks to
hard drive, thereby avoiding the necessity of unpacking to diskette. This,
coupled with CSF143 and its redirecting capability, will allow you to apply
the fixpacks directly from the hard drive directories.
http://hobbes.nmsu.edu/pub/os2/system/patches/fixpack/dskxtr12.zip
Unzip DSKXTR12.ZIP and copy the DSKXTRCT.EXE program to some directory on
your PATH, so that it's easily run.
(6) For the sake of discussion example, let's apply WR08423 first.
cd \
x: change to target drive
cd fixpak\wr08423 change to proper fixpack
dskxtrct /s:w08423b?.dsk /t:. expand all DSK files in fixpack
creating proper sub-directories
and DSKXTRCT.LOG, all within
x:\fixpak\wr08423
mpts apply WR08423 fixpak
(7) Now let's apply WR08425 and UN_0980.
cd \
x: change to target drive
cd fixpak\wr08425 change to proper fixpack
dskxtrct /s:wr08425.?dk /t:. expand all ?DK files in fixpack
cd \ change to CSF143 directory
cd os2serv\csf which contains SERVICE
set csfcdromdir=x:\fixpak\wr08425 point to fixpack
service apply fixpack
cd
cd fixpak\UN_0980
dskxtrct /s:un_980b?.dsk /t:.
cd \
cd os2serv\csf
set csfcdromdir=x:\fixpak\un_0980
service
(8) You can now copy the two files from DOSBOX.
Naturally, the DSKXTRCT and UNZIP steps only need to be done once... the
first time you apply service to your system. Assuming you keep the FIXPAK
directory, if you ever have to reinstall OS/2 and want to apply service
again, you can use the hard drive expanded fixpacks directly.
I hope this is all correct, and that I haven't unwittingly inserted a typo
somewhere.
Also, others may choose to unzip CSF143 into each of the fixpack
sub-directories, along with a small generalized REXX to invoke SERVICE
without having to type any operands. This accomplishes the same thing as
I've detailed above as manual steps, but a bit simpler. However this is just
another way to achieve the same result... as SERVICE must still be invoked,
and CSFCDROMDIR must still be set, either by you or the REXX.
My own preference is to have CSF143 in only one location, in the \OS2SERV
directory. I use OS2SERV out of that same \OS2SERV directory to apply base
OS/2 fixpacks as well, using the following approach.
Assuming you want to download FP15 into x:\FIXPAK\XR_M015. The 18 ZIP files
can be obtained from:
ftp://service.boulder.ibm.com/ps/products/os2/rsu/xr_m015
Then you do the following:
cd \
x:
cd fixpak\xr_m015
unzip -o xr_m015?.zip
cd \
cd os2serv
os2serv x:\os2serv\csf x:\fixpak\xr_m015 y:
where "y" is your target OS/2 partition to which you want service applied.
Note that this OS2SERV approach is essentially identical to what RSUINST is
really doing, if you choose to apply your OS/2 fixpacks using the RSU method.
I simply prefer to do the ZIP downloads myself (using an FTP client), and
then to unzip and apply them myself using the above very simple manual
method. But at its heart, it's really RSU.
Richard Gelderblom
whispered cautiously :
<big snip>
I have a 'fixed' cmd-file for applying service.
When a fix needs to be done I copy the contents of that directory
plus the *dk files to a temp dir and do it from there.
Afterwards I remove the whole tree that was created.
It's not that your method is 'bad', but this saves some file-editing
(directory-paths) :-)
<bigger snip>
> --
> //
> // Darryl Sperber (spe...@airmail.net)
> //
rg,rg
--
I make every mistake twice :
The First time and the Last time