USING RSU - REMOTE SOFTWARE UPDATES

  RSU - Remote Software Updates is an IBM utility which allows you to download
  and install OS/2 FixPaks using a web browser.

  RSU requires OS/2 Warp (version 3 or higher), a web browser, and an active
  TCP/IP (Internet) connection.

  All of the steps below must be performed from the same OS/2 system onto which
  you will be installing the FixPaks.



Installing RSU

  1. Download RSUINSTN.EXE to a temporary directory and execute it.  This is a
     self-extracting ZIP file that contains RSUINST.EXE, RXFTP.DLL and
     UNZIP.EXE.

     (If you download RSUINSTN.EXE using your web browser, it may attempt to
     open the file directly instead of downloading it.  If this happens, hold
     down the Shift key when clicking on RSUINSTN.EXE to bring up the "Save as"
     dialog.)

  2. Place RSUINST.EXE and UNZIP.EXE in your \TCPIP\BIN directory.  Make sure
     that no other copy of these files exists elsewhere in your system PATH.

  3. Check your \TCPIP\DLL directory for an existing file named RXFTP.DLL.
     If this file exists, and is dated 1997-09-04 or later, continue to
     step 4.

     Otherwise, place the copy of RXFTP.DLL from RSUINSTN.EXE into your
     \TCPIP\DLL directory.  Make sure that no other copy of this file exists
     elsewhere in your system LIBPATH.

  4. You may now delete RSUINSTN.EXE and any remaining files that were
     extracted from it.



Enabling Your Web Browser for RSU

  Before you can use RSU, it must be properly enabled within the web browser
  that you will be using.

  * If you are running a freshly installed OS/2 Warp 3, OS/2 Warp Connect, OS/2
    Warp Server, or OS/2 Warp 4, then most likely IBM WebExplorer is the only
    web browser installed.  In this case, see the instructions for 'RSU using
    IBM WebExplorer', below.

  * If you will be using Netscape Navigator or Communicator, see the
    instructions for 'RSU using Netscape', below.

  * If you will be using Mozilla or the IBM Web Browser, see the instructions
    for 'RSU using Mozilla', below.

  * If you will be using Firefox, see the instructions for 'RSU using Firefox',
    below.

RSU using IBM WebExplorer:

  If you are using OS/2 Warp 4, IBM WebExplorer should be at version 1.2, and
  is already enabled for RSU.  No further steps are necessary.

  If you are running a version of IBM WebExplorer prior to 1.2, you may need
  to perform the following steps.  (Note: x: indicates the drive that TCP/IP
  is installed on.)

  1. Close the IBM WebExplorer if it is running.

  2. Determine the location of your ETC directory by entering this command
     from an OS/2 prompt:

     ECHO %ETC%

     (Note: the following steps will assume that the ETC directory is
     x:\MPTN\ETC; substutite the correct value as needed.)

  3. Edit x:\MPTN\ETC\MAILCAP and make sure it contains the following:

        application/rsu; x:\tcpip\bin\rsuinst.exe %s

  4. Edit x:\MPTN\ETC\EXTMAP and make sure it contains the following:

        application/rsu rsu

  5. Edit x:\TCPIP\ETC\EXPLORE.INI, locate the [advanced] section, and
     make sure it contains both of the following:

        mailcap=x:\MPTN\ETC\MAILCAP
        extmap=x:\MPTN\ETC\EXTMAP

RSU using Netscape:

  If you are running Netscape Communicator 4.61, no further steps should be
  necessary.  Otherwise, do the following to verify that RSU is enabled:

  1. Start Netscape.

  2. For Netscape Navigator 2.02, select the menu item 'Options/General
     Preferences', choose 'Helpers', and select the 'application/rsu' entry.
     Make sure it has the following:

       File Extension:  rsu
       Action:          Launch the Application
       Application:     (Set to the fully qualified path to RSUINST.EXE,
                        e.g. C:\TCPIP\BIN\RSUINST.EXE)

     If there is no type 'application/rsu', select 'Create New Type' and add
     one with the above settings.

     (Note: if you had previously configured Netscape to invoke RSUINST.EXE
     when a mime type of 'www/unknown' is encountered, you should disable that
     behaviour.)

     For Netscape Navigator 4.04, select the menu item 'Edit/Preferences',
     choose 'Applications', and select the 'Software Updates' or 'Remote
     Software Updates' entry, then click the 'Edit' button.  Make sure it
     has the following:

       Extension:   RSU
       MIME Type:   application/rsu
       Handled By:  Application (and set to fully qualified path to
                    RSUINST.EXE, e.g. C:\TCPIP\BIN\RSUINST.EXE)
       Uncheck 'Ask me before opening download files of this type'

     If 'Software Updates' or 'Remote Software Updates' does not exist, click
     on the 'New Type' button and add one with the above settings.

  3. Select 'OK' to apply the settings.

RSU using Mozilla:

  1. Start the browser.

  2. Select the menu item 'Edit/Preferences', choose 'Navigator/Applications',
     and look for the file type 'application/rsu'.  If there is none, choose
     'New Type' and add a new file type with the following information:

       MIME Type:                application/rsu
       Description:              Remote Software Updates
       Extension(s):             RSU
       When a file of this
           type is encountered:  Open it with (and set to fully qualified path
                                 to RSUINST.EXE, e.g. C:\TCPIP\BIN\RSUINST.EXE)
       Uncheck 'Always ask me before handling files of this type'

  3. Select 'OK' to apply the settings.

RSU using Firefox:

  1. Start the browser.

  2. Go to the Remote Software Updates web site, and click on the link to the
     FixPak you wish to install.

  3. If Firefox is not configured for RSU, you will receive a prompt dialog
     asking "What should Firefox do with this file?".  Select "Open with",
     and use the Browser button to select the fully qualified path to
     RSUINST.EXE (e.g. C:\TCPIP\BIN\RSUINST.EXE).

     Check "Do this automatically for files like this from now on", and then
     select "OK".


Using RSU

  Once you have installed RSU and configured your web browser as described
  above, RSU should launch automatically whenever you click on a '.RSU' file
  within your browser.

  Simply follow the instructions as presented to you.



Trouble-Shooting RSU Problems

  If you have a problem getting RSU to work properly, be sure to gather any
  error messages you see, and also look at the RSU log file
  (c:\os2\install\rsuinst.log).


  Problem: RSUINST ends but FTPINSTL does not start

  You have Verbose Mode checked and you see the following sequence in the
  Status window of RSUINST.EXE but nothing else happens (check
  \os2\install\rsuinst.log):

     Setting BINARY transfer mode
     Issuing DIR command to get existing file information.
     Skipping csf144.zip, already available and valid.
     Unzipping CSF144.ZIP

  Solution: You have a downlevel version of RSUINST.EXE.  Make sure you have
  correctly installed the latest RSUINST (1.99 or later).  You can determine
  the version of RSUINST.EXE by selecting 'About' from the menu bar when
  RSUINST.EXE is running.  (If there is no menu bar at all, you are using an
  outdated version of RSUINST.EXE and must upgrade.)


  Problem: Unable to connect to service.boulder.ibm.com

  Solution: If you are trying to download a Software Choice Fixpak like XR_C001
  from IBM's Software Choice servers, you need to have RSUINST.EXE version 1.98
  or later.


  Problem: FTPINSTL ends with no error indication, or complains that FTPAPI.DLL
  does not contain the FtpSetActiveMode function.

  Solution: You may be using an outdated version of RSUINST.EXE.  Make sure you
  are using the latest version (1.99).

  Alternatively, this error can also occur if there is a disconnect between
  RXFTP.DLL and FTPAPI.DLL, specifically if RXFTP supports the FtpSetActiveMode
  API but FTPAPI does not.

  To see if this is what is occuring in your case, do the following:

  1. Change to the $rsutmp$ directory on the drive you told RSU to download to.
  2. Enter SET FTPINSTL_DEBUG=MAIN1
  3. Enter FTPINSTL

  FTPINSTL.EXE will start and you will see a "STDIO" window with following in
  it:

  rc = RxFuncAdd('FtpLoadFuncs', 'rxFtp', 'FtpLoadFuncs');
         >>>           "1"
  +++   Interactive trace. "Trace Off" to end debug, ENTER to Continue.

  Press the enter key. If the window disappears then you have this problem. If,
  instead, you see:

  rc = FtpLoadFuncs();
       >>>           "-1"

  then there is something else causing the failure and further work will have
  to be done to determine what it is. Type 'trace' and press the enter key to
  continue.

  To resolve the disconnect between RXFTP.DLL and FTPAPI.DLL, you need to get
  matching levels of these programs. TCP/IP 4.3 from IBM Software Choice is one
  way to accomplish this. Another is to upgrade to the Merlin Convenience Pack
  or Aurora Convenience Package, also available via Software Choice.


  Problem: RC 81 from UNZIP

  Solution: RC 81 from UNZIP means testing or extraction of one or more files
  failed due to unsupported compression methods or unsupported decryption.
  This happens if you are using the 5.40 version of UNZIP which stopped
  supporting the "shrinking" compression method earlier versions like 5.32
  used for some files.

  Revert to the older 5.32 version of UNZIP that is in the latest RSUINSTN.EXE
  self-extracting zip file, or obtain a newer version which has been recompiled
  to include "shrink" support.


  Problem: RC 50 from UNZIP

  Solution: RC 50 from UNZIP means you ran out of space during the extraction
  process. You need to make more room on the drive or select another drive to
  download to.

  It can also be caused by the unzip of the CSF zip file trying to overlay the
  currently inuse UNZIP.EXE in the $rsutmp$ directory. This has been fixed by
  removing UNZIP.EXE (RXFTP.DLL and REPMOD.EXE as well) from the CSF zip files
  as of October 15, 1998. If you get RC 50 and are not short on disk space,
  delete the $rsutmp$ directory and start over. That should resolve the
  problem.


  Problem: RSUINST Automatic Update fails

  Solution: Check your Web browser setup. Make sure you have specified the
  fully qualified path to RSUINST.EXE, not just RSUINST.EXE. Also make sure you
  have the latest RSUINST.


  Problem: RSU hangs when FTPINSTL.EXE is started

  Solution: You need RSUINST.EXE v1.78 or later. Download the latest version and
  follow the installation instructions.


  Problem: Command failed DIR rsucsf.zip zp.

  You are getting a "500 Illegal Port command" when the DIR command is issued.
  To verify, do a manual FTP to the target site, login and try DIR. See if you
  get the 500 error.

  If you do then the problem is probably caused by the socks server you are
  using. It has disabled active FTP (only supports passive FTP) while RSU was
  unable to set passive FTP mode.

  Solution: Try a different socks server.


  Problem: Log file shows: Error: Failed to connect to FTP host

  Solution: You were unable to make a successful connection to the FTP server.
  The FTP server could be down or unusually busy. Wait awhile and try again
  later.


  Problem: Log file shows: Error: Unable to load UNZIP.DLL (rc = -3)

  Solution: Get the latest RSU code (RSUINST.EXE, RXFTP.DLL, UNZIP.EXE).

  Also fully qualify the path to RSUINST.EXE in your Netscape Helper
  Application for mime type application/rsu.


  Problem: Log file shows: Error: FTPGET returned rc = -1

  Solution: If you are attempting to connect from a proxy server, this will not
  work. If you can, try changing your connection to use a socks server instead.


  Problem: Cannot open temporary file

  Solution: The files must be copied to your local hard drive. Be sure you have
  enough disk space on your TCPIP drive (x:\TCPIP\TMP). Also ensure you have
  SET TMP = x:\TCPIP\TMP in your CONFIG.SYS file.



Credits

  Much of this file is based on the IBM Software Updates web document, dated
  April 3 2002.  The latest version of this file can be found here, although
  most of this information is no longer included:
  http://ps.software.ibm.com/os2fixp/softupd.html

  Editing and additional information is (C) 2005 Alex Taylor.