Installation and Configuration Guide

First Edition (March 2001)

This edition applies to IBM Web Browser for OS/2 V 1.1 (Web Browser) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2001. All rights reserved.
U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

About this book

Components and requirements

Installing Web Browser in an OS/2 Warp environment

Installing and configuring Web Browser to run in a WorkSpace On-Demand 2.0 environment

Installing Web Browser in a WorkSpace On-Demand 3.0 environment

Installing Web Browser in a CID environment

Migrating from Netscape Communicator 4.x to Web Browser

Installing additional components

Uninstalling Web Browser

Appendix A. Notices

Index

About this book

This Installation and Configuration Guide provides instructions to install and configure IBM Web Browser for OS/2 V 1.1.

Components and requirements

The following sections list the components of Web Browser and the hardware and software requirements that you need to run Web Browser.

Web Browser components

Web Browser includes the following components:

• Mozilla browser
• Mail/News
• SpellChecker
• Macromedia(R) Flash

Hardware requirements

The following lists minimum hardware requirements to run Web Browser:

• A Pentium^(R) or compatible microprocessor at 90 MHz or higher will provide the best results.
• 64 MB of RAM.
• 30 MB free hard disk space.
• 38 MB of temporary hard disk space (for installation).
• 256 color display or greater.

  Note:

  Web Browser will run on systems with 16 color display; however, the quality of the display becomes significantly lower.

• A connection to the Internet.

Note:

For Japanese and Korean users only, if you use PS/55 Display Adapter II, apply program temporary fix (PTF) JR12322 before you run Web Browser.

Software requirements

Web Browser supports the following:

• OS/2 Warp 4.0 with the latest FixPak

  Use the following instructions to determine the latest FixPak for OS/2 Warp 4.0:

  1. Go to the FixPak Database located at http://service5.boulder.ibm.com/pspfixpk.nsf.
  2. Click Software Updates.
  3. Click OS/2 Warp 3.x and 4.0 FixPaks by Country.
• OS/2 Warp Server for e-business with the latest FixPak

  Use the following instructions to determine the latest FixPak for OS/2 Warp Server for e-business:

  1. Go to the FixPak Database located at http://service5.boulder.ibm.com/pspfixpk.nsf.
  2. Click Software Updates.
  3. Click OS/2 Warp Server for e-Business FixPak's.
• WorkSpace On-Demand 2.0
• WorkSpace On-Demand 3.0

Required FixPaks for Double Byte Character Set (DBCS) versions of OS/2 Warp

The following DBCS versions of OS/2 Warp 4.0 require FixPak FX00505 or higher:

• OS/2 Warp 4 Japanese version (without VoiceType)
• OS/2 Warp 4 Korean version
• OS/2 Warp 4 Traditional Chinese version
• OS/2 Warp 4 Simplified Chinese (GB) version
• OS/2 Warp 4 Simplified Chinese (GBK) version

Installing Web Browser in an OS/2 Warp environment

After you download Web Browser, complete the following instructions to extract Web Browser, then install Web Browser in an OS/2 Warp Server for e-business or an OS/2 Warp 4.0 environment. You can extract the installation files with the OS/2 GUI or the command line.

Extracting the installation files

To extract the installation files using the OS/2 GUI:

1. Open the folder where you downloaded browser.exe.
2. Double-click browser.exe to unpack the installation files.
3. Double-click install.exe to start the installation.

To extract the installation files using the command line:

1. At a command prompt, change to the directory where you downloaded browser.exe.
2. Type browser to unpack the installation files.
3. Type INSTALL to start the installation program.

Installing in an OS/2 Warp environment

To install Web Browser in an OS/2 Warp Server for e-business or an OS/2 Warp 4.0 environment:

1. Read the license agreement and click Continue to accept the agreement.
2. Click OK to install Web Browser.
3. Select the components you want to install or select Select all to install all of the components.

   Note:

   To install Mail/News, SpellChecker, or Macromedia Flash you must install the browser component.

4. Click Install.

   Note:

   Web Browser installs in the OS2WEB directory automatically. To change the installation directory, type the directory where you want to install Web Browser in the Installation Directory field. The Installation Directory cannot exceed 32 characters.

5. Click YES to use Web Browser as the default program for opening URL objects on the desktop.

   Note:

   Clicking YES does not affect URL objects that are set to open with a specific browser.

6. Click YES to enable Web Browser as a browser that you can select when you open HTML files.
7. Click YES to read the README file. The README file contains updated information about Web Browser.
8. Close the ASCII editor when you finish reading the README.
9. Click OK at the reminder window to shut down your computer.
10. Restart your computer.

    The installation program creates a shadow of the browser and a Web Browser folder on your desktop. The Web Browser folder includes the Browser object, User Profile Manager object, README file, and an installation utility.

11. Double-click the Web Browser icon on your desktop to start Web Browser.

    If no profiles are found for migration, Web Browser creates a default profile. If more than one profile exists, the User Profile Manager opens automatically when you start Web Browser. You can use the User Profile Manager to select the profile that Web Browser will use. The User Profile Manager also enables you to add or delete profiles.

    Note:

    A network or TCP error might occur when you use Web Browser behind a firewall. To resolve the error, set up a socks server or proxy gateway. See the online help for more information.

Installing and configuring Web Browser to run in a WorkSpace On-Demand 2.0 environment

This chapter explains how to install Web Browser in a WorkSpace On-Demand 2.0 environment. After you install Web Browser, complete the instructions in Configuring Web Browser for WorkSpace On-Demand 2.0 to configure it to run as a client network application.

Installation Tips

• You must have System Administrator authority to install Web Browser in a WorkSpace On-Demand 2.0 environment.
• If your client machines use a drive letter other than Z, modify the BRCOMM.PKG file. To modify this file:
  1. Open BRCOMM.PKG in an ASCII editor.
  2. Search for Z:.
  3. Replace Z with the drive letter that your client machines use.
  4. Save and close BRCOMM.PKG.
• After you install Web Browser, run the GETRPL utility. The GETRPL utility sets access rights for the new subdirectory.

Installing Web Browser in a WorkSpace On-Demand 2.0 environment

After you download Web Browser, complete the following instructions to install Web Browser in a WorkSpace On-Demand 2.0 environment.

1. Log on to a WorkSpace On-Demand 2.0 server as a system administrator.
2. Extract the installation files.
   1. At a command prompt, change to the directory where you downloaded browser.exe.
   2. Type browser to unpack the installation files.
   3. Type INSTBRWS to start the installation program.

      Note:

      Valid parameters for the INSTALL command are also valid for the INSTBRWS command.

3. Read the license agreement and click Continue to accept the agreement.
4. Click OK to install Web Browser.
5. Select the components you want to install or select Select all to install all of the components.

   Note:

   To install Mail/News, SpellChecker, or Macromedia Flash you must install the browser component.

6. Click Install.

   Note:

   To avoid modifying client FIT files, install Web Browser in the OS2 directory or in a subdirectory of the OS2 directory. The default directory is IBMLAN\RPL\BB20.cc\OS2\OS2WEB. Where cc represents the two character country code.

   To install to a directory other than IBMLAN\RPL\BB20.cc\OS2\OS2WEB, type the directory where you want to install Web Browser in the Installation Directory field; then, modify the APPPOST.FIT file. The Installation Directory cannot exceed 32 characters. See Configuring Web Browser after you install it in another directory for instructions to modify the APPPOST.FIT file.

7. Click YES to read the README file. The README file contains updated information about Web Browser.
8. Close the ASCII editor when you finish reading the README file.

   The installation program creates a Web Browser--IBM WorkSpace On-Demand folder on your desktop. The folder contains the README file and an installation utility.

   The installation program also creates an application, named BRCOMM, for the browser and an application, named BRPRF, for the User Profile Manager.

9. Assign BRCOMM to the users that you want to have the browser.
10. Assign BRPRF to the users that you want to have the User Profile Manager.
11. Run the GETRPL utility. If the defaults are ok, the client machines can access Web Browser.

    If no profiles are found for migration, Web Browser creates a default profile. If more than one profile exists, the User Profile Manager opens automatically when you start Web Browser. You can use the User Profile Manager to select the profile that Web Browser will use. The User Profile Manager also enables you to add or delete profiles.

    Notes:

    1. The apppost.fit file provided with Web Browser contains the necessary fit entries to locate and migrate Netscape Communicator 4.61 profiles (assuming that you installed Netscape Communicator 4.61 in it's default directories). If you installed Netscape Communicator 4.61 to different directories, or if you are using Netscape Communicator 4.04, then you need to modify the Web Browser apppost.fit file entries to match the directory where you installed Netscape Communicator 4.61 or Netscape Communicator 4.04. Modify the apppost.fit file entries immediately after you install Web Browser to allow each user to migrate the first time they log on and open the browser. (If they want to migrate later, they can open the User Profile Manager on the desktop to delete all existing profiles and then open the browser. If no profile is found to migrate, a new default profile will be created.)

    2. A network or TCP error might occur when you use Web Browser behind a firewall. To resolve the error, set up a socks server or proxy gateway. See the online help for more information.

Configuring Web Browser for WorkSpace On-Demand 2.0

WorkSpace On-Demand 2.0 supports Web Browser as a client network application. During installation, Web Browser creates two network applications: the browser, named BRCOMM, and User Profile Manager, named BRPRF.

Note:

If the BRCOMM and BRPRF IDs are defined and if you install Web Browser as a new application, the installation fails. However, if you choose to update your current installation, these IDs do not affect the installation.

Web Browser uses directories (based on the directories specified in the FIT file) in each user's workarea. The installation process enables the Wrapper Utility (in the public applications) to create these directories automatically. Client machines cannot access Web Browser unless these directories have been created. Additionally, the Wrapper Utility manages some files when you install additional components, such as Mail/News.

Using the Wrapper Utility

If you installed Web Browser in the default directories, no changes to APPPOST.FIT or BRWS.DSF are necessary. However, if you changed the default directories, carefully review the following information.

The Wrapper Utility creates directories by reading an input file that contains specifications about the directories and executing the specified commands. The input file consists of keywords and their values, which describe the steps to create directories, copy files, and start Web Browser for the application.

The input file resides in the same location as the executable file. To determine the file name of the input file, replace the extension (.EXE ) of the executable file name with .DSF. For example, if a utility named BRWS.EXE resides in the Z:\OS2\OS2WEB directory, then the input file name and directory are Z:\OS2\OS2WEB\BRWS.DSF.

The input file has a line limit of 256 bytes and supports the following keywords:

EXE= program_name

program_name represents the name of the program to be executed. If you specify EXE more than once, the input file uses the value of the last occurrence.

FILE=target file source file

target file represents the name of the file you want to create. source file represents the file that you want to use as a template for the target file.

DIR=target dir

target dir represents the directory you want to create for the target file.

Create a DIR entry for every subdirectory under the USER specification in the file's FIT entry. For example, if the FIT entry is ?:\OS2WEB\MOZILLA \\<DCSERVER>\IBMLAN$\DCDB\USERS\<USER>\COMMBR\MOZILLA, create the following DIR entries after the FILE=\OS2WEB\MOZILLA\XYZ entry:

DIR=BRCPDIR1 
DIR=BRCPDIR2

After you create the DIR entries in the input file, create corresponding entries in the FIT file. The entries in the FIT file create the directories. For example, corresponding FIT file entries for the input file entries above would be:

?:\BRCPDIR1 \\<DCSERVER>\IBMLAN$\DCDB\USERS\<USER>\COMMBR
?:\BRCPDIR2 \\<DCSERVER>\IBMLAN$DCDB\USERS\<USER>\COMMBR\MOZILLA
 

Web Browser writes to several files in the X:\OS2\OS2WEB directory (where X represents the boot drive). Every client machine must have its own set of these files to read and write to. The directories for the files must exist in each client machine's write area before you open the browser for the first time. The Wrapper Utility creates these directories for the files.

Although Web Browser doesn't require any specific FILE= entries in the Wrapper Utility, Web Browser includes two mock entries in the BRWS.DSF file, which enables BRWS.EXE to function properly. If you installed Web Browser in a directory other than the default, modify the APPPOST.FIT file according to the instructions in Disabling the Wrapper Utility. You do not need to modify the BRWS.DSF file.

Disabling the Wrapper Utility

You might choose to disable the Wrapper Utility so that you can manually create the directories for each user.

Note:

If you disable the Wrapper Utility, you cannot install the Mail/News component (after the initial installation) unless you erase all .rdf files in the CHROME directory (and its subdirectories) in every user's data area.

To disable the Wrapper Utility:

1. Open the settings notebook for the BRCOMM public application definition.
2. Click the Invocation tab.
3. In the Command field, change brws.exe to os2web.exe.
4. Click Apply to save your changes.
5. Close the settings notebook.
6. Repeat steps 1 through 5 for the BRPRF public application.

Creating directories manually

If you disable the Wrapper Utility, you must create these directories manually because client machines cannot access Web Browser unless these directories have been created.

To create the directories manually:

1. At an OS/2 command prompt, change the directory to X:\IBMLAN\DCDB\USERS\user. Where X represents the drive letter for the user's workarea and user represents the name of the user.
2. Create a subdirectory named COMMBR within the user's directory. For example, type:

   MD COMMBR
   

3. Change to the COMMBR directory. For example, type:

   CD COMMBR
   

4. Create a subdirectory named MOZILLA within the COMMBR directory. For example, type:

   MD MOZILLA
   

5. Create a subdirectory named CHROME within the COMMBR directory. For example, type:

   MD CHROME
   

6. Complete steps 1 through 5 for each client machine that uses Web Browser.

Configuring Web Browser after you install it in another directory

If you installed Web Browser in a directory other than the default (OS2\OS2WEB), modify the APPPOST.FIT file to reflect the new location. The default directory location is similar to ?:\OS2\OS2WEB... For example, if you installed Web Browser in the \IBMLAN\RPL\BB20.US\NETSCAPE\M directory, change the location to ?:\NETSCAPE\M. Do not install Web Browser into any directory that is not a subdirectory of \OS2 or \NETSCAPE. If you install into a directory other than the default, the directory name cannot exceed 32 characters. If the directory name exceeds 32 characters, the installation of additional components will fail.

Installing Web Browser in a WorkSpace On-Demand 3.0 environment

Before you can begin installing Web Browser, extract the installation files using the instructions in Extracting the installation files. Then, refer to the following instructions to install Web Browser in a WorkSpace On-Demand 3.0 environment. The installation instructions make these assumptions:

• The steps in "Prerequisites for installing OS/2 applications" on page 256 of the IBM WorkSpace on-Demand 3.0 Administrator's Guide (First Edition, July 2000) have been completed.
• The application server share is \\server_name\apps and is at drive X.
• The configuration server's TDMPKGS share is at drive letter H.
• The country code (LANG) is US.
• The APPLICATION DEFINE name for Web Browser is OS2WEB.
• The browser.exe file from Software Choice has been downloaded to drive X on the application server share (\\server_name\apps) and users have access to drive X on startup.

The following instructions refer to the IBM WorkSpace On-Demand 3.0 Administrator's Guide (First Edition, July 2000). To install Web Browser in a WorkSpace On-Demand 3.0 environment:

Note:

When you define client machines that will run Web Browser, select DHCP=YES, or enable TCPIP.

1. Log on to the sandbox client machine as a user with administrative privileges.
2. Connect to the application server. For example, type:

   NET USE X: \\server_name\apps
   

3. Run the CRTPKG utility. For example, type:

   Z:\APPLCPTR\CRTPKG /START
   

4. Change to drive X where browser.exe was downloaded.
5. Type BROWSER to run the executable file that unpacks the files for installing Web Browser.
6. Type INSTWS3 to begin the installation.

   Note:

   All parameters that are valid for the INSTALL command are valid for the INSTWS3 command.

7. Read the license agreement and click Continue to accept the license agreement.
8. Click OK to install Web Browser.
9. Select the components you want to install or select Select all to install all of the components.
10. Type the drive letter and directory that you used to connect to the application server as the Installation Directory. The Installation Directory cannot exceed 32 characters. For example, type:

    X:\OS2WEB
    

11. Click Install.
12. Click YES to use Web Browser as the default program for opening URL objects on the desktop.

    Note:

    Clicking YES does not affect URL objects that are set to open with a specific browser.

13. Click YES to enable Web Browser as a browser that you can select when you open HTML files.
14. Click YES to read the README file. The README file contains updated information about Web Browser.
15. Close the ASCII editor when you finish reading the README file.
16. Restart the sandbox client machine when the installation completes.
17. After the sandbox client machine restarts, reconnect to the application and configuration servers. For example, type:

    NET USE X: \\server_name\apps
    NET USE H: \\server_name\tdmpkgs
    

18. Double-click the Web Browser icon on the desktop to open Web Browser.

    Web Browser creates a default user profile the first time you open Web Browser. If you want to customize the default profile, select Edit --> Preferences in Web Browser. For example, you might want to customize the preferences to change the appearance or proxy information.

    If you want to distribute plug-in software, install the software now.

19. Close the browser.
20. Double-click the User Profile Manager icon in the IBM Web Browser for OS/2 V 1.1 folder on the desktop.

    If you want to change the default profile name or add additional profiles, do so at this time.

21. Select the profile that you want Web Browser to use and click Start.
22. After the browser opens, close it.

    Note:

    You must have opened and closed the browser twice (as described in steps 18 through 22) before you continue with the next step.

23. Run the CRTPKG utility. For example, type:

    	Z:\APPLCPTR\CRTPKG OS2WEB /FINISH
    

    Where OS2WEB represents the APPLICATION DEFINE name for the browser application.

24. Copy the APPPOST.WS3 file (that was unpackaged in step 5) to the directory on the configuration server where you installed Web Browser and rename the file APPPOST.FIT. For example, type:

    COPY X:\APPPOST.WS3 X:\OS2WEB\APPPOST.FIT
    

    Notes:

    1. The apppost.ws3 file provided with Web Browser assumes that you installed Web Browser to X:\OS2WEB. If you install Web Browser to a different location, you must edit apppost.ws3 before you copy it so that each client machine will have its own set of profiles. To edit apppost.ws3, change all occurrences of X:\OS2WEB to point to the shared directory where you installed Web Browser.

    2. The apppost.ws3 file also contains the necessary fit entries to locate and migrate Netscape Communicator 4.61 profiles (assuming that you installed Netscape Communicator 4.61 according to the instructions in the WorkSpace On-Demand 3.0 Administrator's Guide). If you installed Netscape Communicator 4.61 to different directories, you will need to modify the last 3 entries in apppost.ws3 to match the Netscape Communicator 4.61 apppost.fit file entries.

       WorkSpace On-Demand 3.0 users can migrate at any time. To migrate, users must complete the following steps:

       1. Open the User Profile Manager on their desktop.
       2. Delete all existing profiles (including the default profile).
       3. Open the browser.

          Note:

          If no profile is found to migrate, a new default profile will be created.

25. Create a directory for user-specific files. For example, type:

    MD H:\application\OS2\lang\OS2WEB\user\profile\mozilla
    

26. XCOPY the files and directories from X:\OS2WEB\MOZILLA to H:\application\OS2\lang\OS2WEB\user\profile\mozilla with the /S /H /E /T options. For example, type:

    xcopy X:\OS2WEB\MOZILLA H:\application\OS2\lang\OS2WEB\USER\profile\mozilla 
    /S /H /E /T
    

    Note:

    This example displays on more than one line because of the width of the page.

27. Copy the following files

    X:\OS2WEB\component.reg
    X:\OS2WEB\mozregistry.dat
    X:\OS2WEB\components\xpti.dat
    X:\OS2WEB\components\xptitemp.dat
    X:\OS2WEB\chrome\user-locales.rdf
    X:\OS2WEB\chrome\user-skins.rdf
    

    to H:\application\OS2\lang\OS2WEB\user\profile.

28. Define the Web Browser application. At a command prompt, type the APPLICATION DEFINE command and specify NAME=OS2WEB, COMMAND=os2web.exe, DRIVE=X, APPPATH=\OS2WEB, and ICONTITLE=Browser. For example, type:

    APPLICATION DEFINE NAME=OS2WEB
    LANG=US OS=OS2 SHELL=PMSHELL 
    APPDRIVE=X APPPATH=\OS2WEB 
    COMMAND=os2web.exe ICONTITLE=Browser 
    

29. Create an APPPARM.INI file for the User Profile Manager application to be created in the next step. For example, type:

    cd \TDM\TDMPKGS\APPLICATION\OS2\US
    md UPM
    copy os2web\appparm.ini upm\*.*
    

30. Define the User Profile Manager application. At a command prompt, type the APPLICATION DEFINE command and specify NAME=UPM, COMMAND=os2web.exe -profilemanager, APPDRIVE=X, APPPATH=\OS2WEB, and ICONTITLE=USER PROFILE^MANAGER. For example, type:

    APPLICATION DEFINE NAME=UPM 
    LANG=US OS=OS2 SHELL=PMSHELL
    APPDRIVE=X APPPATH=\OS2WEB
    COMMAND=os2web.exe -profilemanager
    ICONTITLE=USER PROFILE^MANAGER
    ICONFILE=X:\OS2WEB\UPM.ICO
    

After you install Web Browser and define it as a WorkSpace On-Demand 3.0 application, use the following steps to verify that the installation completed successfully.

To verify that the installation completed successfully:

1. Log on to a Windows NT^(R) server or client machine as a user with administrative privileges.
2. Assign a desktop to a user. (See "Assigning desktops to user accounts" in "Chapter 15: Managing desktops" in the IBM WorkSpace On-Demand 3.0 Administrator's Guide for more information about assigning desktops to user accounts. If you don't have any desktops defined, define a desktop and then assign that desktop to a user. See "Chapter 9: Defining desktops" in the IBM WorkSpace On-Demand 3.0 Administrator's Guide for more information about defining desktops.)

   For example, to assign a desktop to a user, type:

   DESKTOP ASSIGN DESKTOP="neatdesktop" LANG=US
   OS=OS2 SHELL=PMSHELL USER="Tom"
   

3. Assign Web Browser and the User Profile Manager to a user without administrative privileges and as a user who has access to drive X on startup. (See "Assigning applications to user accounts" in "Chapter 13: Managing applications" in the IBM WorkSpace On-Demand 3.0 Administrator's Guide for more information about assigning applications to user accounts. If you don't have a user defined, define a user and then assign a desktop and the applications to that user. See "Chapter 5: Defining user accounts" in the IBM WorkSpace On-Demand 3.0 Administrator's Guide for more information about defining users.)

   For example, to assign Web Browser to a user, type:

   APPLICATION ASSIGN APPLICATION="OS2WEB" LANG=US
   OS=OS2 SHELL=PMSHELL USER="Tom"
   

   For example, to assign the User Profile Manager to a user, type:

   APPLICATION ASSIGN APPLICATION="UPM" LANG=US
   OS=OS2 SHELL=PMSHELL USER="Tom"
   

4. Log on to a client machine (other than the sandbox client machine) as a user without administrative privileges (the user whom you assigned the application to).
5. Verify that Web Browser and the User Profile Manager reside on the desktop and function properly.

Installing Web Browser in a CID environment

CID (Configuration, Installation, and Distribution) installation uses response files to install Web Browser in a CID environment. A response file is a text file that consists of keywords that direct the installation process. Response files consist of two types of lines:

• Comment lines

  Comment lines contain only spaces or an asterisk (*) or a semicolon (;) as the first space character on the line.

• Response lines

  Software Installer uses response lines to determine the options and configurations to install on the target system. Each line in the response file has a maximum length of 255 bytes. Response lines have the following syntax:

  keyword=value
  

Keywords are case-insensitive and cannot contain imbedded spaces. You can group keywords together in value lists using the following syntax:

keyword= (
         keyword1=value
         keyword2=value
         keywordn=value
         )

Keyword-value pairs can be in any order; however, response files only allow one pair per line. If you use keyword names other than the supported keywords, Software Installer treats them as installation variables. For example, if you specify MONITOR=VGA, Software Installer creates an installation variable with the name of MONITOR and a value of VGA.

Note:

Do not use quotes around the component name. Use a space to separate multiple component name entries.

Before you can begin installing Web Browser in a CID environment, complete the instructions in Extracting the installation files. Then, refer to the keyword lists and sample response file before you write a response file that installs Web Browser.

Web Browser keywords

Web Browser supports the following keywords for you to use to install Web Browser in a CID environment:

NSCONVERTBROWSER=YES|NO

Specify NSCONVERTBROWSER=YES to enable Web Browser as the default browser for all URL objects. Specify NSCONVERTBROWSER=NO to disable Web Browser as the default browser for all URL objects. Valid values for NSCONVERTBROWSER are YES or NO. NSCONVERTBROWSER is a required keyword.

NSASSOCIATEHTML=YES|NO

Specify NSASSOCIATEHTML=YES to associate Web Browser with HTML files. HTML files are files with .htm and .html extensions. Specify NSASSOCIATEHTML=NO to disable opening HTML files within Web Browser. Valid values for NSASSOCIATEHTML are YES or NO. NSASSOCIATEHTML is a required keyword.

If you specify NSASSOCIATEHTML=YES, you can open HTML files within Web Browser by right-clicking the file on your OS/2 desktop, and selecting Open As. Then, select Web Browser from the pop-up menu.

Software Installer keywords

Software Installer supports the following keywords:

AUXn

Specifies the default path for the auxiliary directory. Replace n with any number between 1 and 18 that you want to use as your auxiliary directory. AUXn replaces the AUXn keyword in the PATH entry of the package file. Web Browser uses AUXn for installation processing only. AUXn is a required keyword if you specify an AUXn keyword in the PATH entry of the package file.

CFGUPDATE=AUTO|MANUAL

Specify CFGUPDATE=AUTO to update the CONFIG.SYS file automatically. Specify CFGUPDATE=MANUAL to update the CONFIG.SYS file manually. Valid values for CFGUPDATE are AUTO or MANUAL. CFGUPDATE is a required keyword.

COMP

Specifies the unique name of a Web Browser component to apply passed information to. You can specify a maximum of 100 components. The value of COMP must exactly match the NAME keyword of the COMPONENT entry in the package file. COMP is an optional keyword.

Note:

Do not use quotation marks around the component name regardless of whether or not the component name is more than one word.

COPY=source_file target_file

Specifies the source file that you want to copy from and the target file that you want to copy to. If the target file already exists, it will be overwritten. If either file is not valid, the copy will not be made. COPY is an optional keyword.

DELETEBACKUP=YES|NO

Specify DELETEBACKUP=YES to delete the backup versions of Web Browser. Specify DELETEBACKUP=NO to delete the entire product. DELETEBACKUP is a required keyword.

Note:

If you attempt to delete Web Browser and you have not specified DELETEBACKUP in the response file, then the deletion fails.

FILE

Specifies the default path for the file directory. FILE replaces the FILE keyword in the PATH entry of the package file. Web Browser uses FILE for installation processing only. FILE is a required keyword if you specified a FILE keyword in the PATH entry.

INCLUDE=file_name

Specifies the names of response files to include with a specific response file. file_name represents the name of the response file that you want to include. If the file name contains any global characters, such as * or ?, Web Browser includes the first file that matches. If the file name is not valid, then the response file is not included.

Web Browser searches for response file names in the following order:

1. fully qualified file name
2. current directory
3. file name with the /G: invocation parameter
4. each directory in the PATH environment variable
5. each directory in the DPATH environment variable

Note:

You cannot include more than five levels of response files.

OVERWRITE=YES|NO

Specify OVERWRITE=YES to automatically overwrite files during installation. Specify OVERWRITE=NO not to overwrite files during installation. Valid values for OVERWRITE are YES or NO. OVERWRITE is a required keyword for unattended processing.

SAVEBACKUP=YES|NO

Specify SAVEBACKUP=YES to save a backup version of Web Browser when it updates. Specify SAVEBACKUP=NO not to save a backup version of IBM Web Browser for OS/2 V 1.1. Valid values are YES or NO. SAVEBACKUP is a required keyword.

USEREXIT=file_name

Specifies the name of the exit file that you want to start. file_name represents the name of a user exit. If the file name contains any global characters, such as * or ?, Web Browser includes the first file that matches. If the file name is not valid, Software Installer displays an error message.

Web Browser searches for file names in the following order:

1. fully qualified file name
2. current directory
3. each directory in the PATH environment variable
4. each directory in the DPATH environment variable

Note:

If the exit does not already exist on your system, you must package the exit in the INSTALL.IN_ file.

WORK

Specifies the default path to the data directory. WORK replaces the WORK keyword in the PATH entry of the package file. WORK is a required keyword if you specified a WORK keyword in the PATH entry.

Sample installation response files

To begin CID installation, type the installation command. For example, your installation command might look like the following:

INSTALL /X /A:I /NMSG /O:DRIVE /R:responsefile /L2:output file 

This response-file example installs the United States English version of Web Browser in the C:\OS2WEB directory:

COMP              =Browser
COMP              =Mail/News
COMP              =SpellChecker
COMP              =Macromedia Flash Player
FILE              =C:\OS2WEB
CFGUPDATE         =AUTO
DELETEBACKUP      =NO
OVERWRITE         =YES
SAVEBACKUP        =NO
NSCONVERTBROWSER  =YES
NSASSOCIATEHTML   =YES

This response-file example installs the United States English version of Web Browser to the C drive in a WorkSpace On-Demand 2.0 environment.

COMP          =Browser
COMP          =Mail/News
COMP          =SpellChecker
COMP          =Macromedia Flash Player
FILE          =C:\IBMLAN\RPL\BB20.US\OS2\OS2WEB
AUX1          =C:\IBMLAN\RPL\BB20.US
CFGUPDATE     =AUTO
DELETEBACKUP  =NO
OVERWRITE     =YES
SAVEBACKUP    =NO

Migrating from Netscape Communicator 4.x to Web Browser

To migrate your files from Netscape Communicator 4.x for OS/2 (version 4.61 or 4.04) to Web Browser, follow the installation steps for your environment. The first time you open Web Browser, a window is displayed that asks if you want to migrate. Select Yes to migrate your profile and bookmarks. If you have multiple profiles, Web Browser will ask you to select the one that you want to migrate.

Notes:

1. Web Browser is not intended to replace Netscape Communicator 4.x.

2. Because you cannot export address books from Netscape Communicator, you cannot import address books from Netscape Communicator into Web Browser.

About the MOZILLA_HOME entry in CONFIG.SYS

MOZILLA_HOME specifies where the registry and profile information is stored for Web Browser. The location that MOZILLA_HOME points to must be on a HPFS or JFS drive. Web Browser cannot store registry and profile information on a FAT drive.

Installing additional components

After you install Web Browser, you might later decide to install additional components such as SpellChecker. Use the following instructions to install additional components on your system.

To install additional components:

1. Verify that you have the executable (that you downloaded from Software Choice) on your system. If you deleted the executable, go to the Software Choice Web site at http://service.boulder.ibm.com/asd-bin/doc/en_us/home.htm and download Web Browser again.
2. Extract the installation files and start the installation according to the steps in Extracting the installation files.
3. Read the license agreement and click Continue if you accept the agreement.
4. Click OK to install Web Browser.
5. Select the components you want to install.

   Note:

   To install Mail/News, SpellChecker, or Macromedia Flash you must have the browser component installed.

6. Click Install.

   Note:

   When you install additional components, you cannot change the Installation Directory.

7. Click YES to read the README file. The README file contains updated information about Web Browser.
8. Close the ASCII editor when you finish reading the README file.
9. Click OK.
10. Double-click the Web Browser icon on your desktop to start Web Browser.

Uninstalling Web Browser

IBM Web Browser for OS/2 V 1.1 provides an installation utility that you can use to uninstall Web Browser (or one or more of its components) from an OS/2 Warp 4 server, an OS/2 Warp Server for e-business, and WorkSpace On-Demand 2.0.

To uninstall Web Browser or one or more components:

1. Open the Web Browser folder or the Web Browser--WorkSpace On-Demand folder on your desktop.
2. Double-click the Web Browser Installation Utility.
3. Select Web Browser or Web Browser_WorkSpace On-Demand.
4. Click Action --> Delete.
5. Select the components you want to uninstall.
6. Click Delete.
7. Click OK when the uninstallation completes.
8. Shut down and restart your computer.

   Note:

   You do not have to restart your computer if you uninstall WorkSpace On-Demand 2.0 client machines.

Appendix A. Notices

This information was developed for products and services offered in the U.S.A. IBM might not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written.

These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. 2001. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

The following terms are registered trademarks of International Business Machines Corporation in the United States, or other countries, or both:
IBM
OS/2

Macromedia, Flash and Macromedia Flash are trademarks or registered trademarks of Macromedia, Inc. in the United States and internationally.

Netscape is a registered trademark of Netscape Communications Corporation in the United States and other countries.

Pentium is a registered trademark of Intel.

Windows NT is a registered trademark of Microsoft Corporation.

Other company, product, and service names may be trademarks or service marks of others.

Index