OS/2(R) Plug-in Pack v. 3.0
Installation and Configuration README

This README file contains the information about installing and
configuring the feature.

Note: To help you locate information in this README, you can use
      the Find option under the Edit menu of the OS/2 System
      Editor. You can print the file by dragging it to your
      printer object or by selecting Print from the file object's
      pop-up menu. Using the right mouse button, click the object
      to display the pop-up menu.

In the following sections, "Netscape Communicator 4.61" refers to
Netscape Communicator 4.61 for OS/2 Warp and "Plug-in Pack" refers
to OS/2 Plug-in Pack v. 3.0.

All variables in path names are in lowercase.

CONTENTS
__________________________________________________________________

1.0 Installation
2.0 Plug-in Support
3.0 OS/2 MPEG Support
4.0 CID Installation Information
5.0 Notices

1.0 INSTALLATION
__________________________________________________________________

The following sections describe installing the Plug-in Pack.
Be sure that you have installed Netscape Communicator 4.61 before
installing the Plug-in Pack.

1.1 Hardware and Software Requirements
------------------------------------------------------------------

Hardware Requirements:

At least 2.5 MB of free hard disk space and 10 MB of temporary
disk space.

Note: If you plan to use IBM(R) MPEG support, see section 3.0
OS/2 MPEG Support.

Software Requirements:

Netscape Communicator 4.61 for OS/2 Warp

The OS/2 Plug-in Pack v. 3.0 is installable on the following
operating systems:

  o OS/2 Warp 4

  o OS/2 Warp Server Version 4

  o OS/2 Warp Server Advanced Version 4

  o OS/2 Warp Server Advanced SMP Feature

  o OS/2 Warp Server for e-business

1.2 Installing the Plug-in Pack
------------------------------------------------------------------

For information on CID installations, see section 4.0 CID
Installation Information.

After you have installed Netscape Communicator 4.61, you can install
the Plug-in Pack.

Note:  If you plan to use Microsoft(R) Windows(R) 3.1 Plug-ins,
       install the Plug-in Pack into a directory with a name
       no more than 8 characters long.

To install the Plug-in Pack using the graphical user
interface (GUI):

  1. Open the folder where you downloaded the os2pip30.exe file.

  2. Double-click os2pip30.exe to unpack the files for
     installing the Plug-in Pack.

  3. Double-click install.exe to start the installation.

  4. Follow the online instructions.

     Note: If you have previously installed the OS/2 Plug-in Pack
           v. 2.1, during the installation you are asked the
           following question:

           x:\pluginfile already exists on the workstation.

           Do you want to replace the file?

           (where x: is the drive where OS/2 is installed and
            pluginfile is one of several plug-in files)

           Click Yes to All when asked.

  5. Shut down and restart your operating system.


To install the Plug-in Pack from the command line:

  1. From a command line, change to the directory where you
     downloaded the os2pip30.exe file.

  2. Type os2pip30 to unpack the files for installing the Plug-in
     Pack.

  3. Type INSTALL to start the installation.

  4. Follow the online instructions.

  5. Shut down and restart your operating system.


1.3 Uninstalling a Previously Installed Version
------------------------------------------------------------------

If you have more than one version of the OS/2 Plug-in Pack
installed and you want to uninstall one or more versions but not
all versions, you must update the version of the Plug-in Pack
that remains on your system. This update is required because the
uninstall procedure deletes some of the files used by all versions
of the Plug-in Pack.

After uninstalling any version, you must update the version of
the Plug-in Pack that remains on your system.

To update the Plug-in Pack, follow the instructions in section
1.2 Installing the Plug-in Pack. Click Update the Currently
Installed Product when prompted.

2.0 PLUG-IN SUPPORT
__________________________________________________________________

The following sections describe some of the plug-ins provided in
the Plug-in Pack.

2.1 Windows(R) 3.1 Plug-ins
------------------------------------------------------------------

When you install a Windows 3.1 plug-in, change the default
directory for installation to

ATTENTION: This is not the same directory as in previous versions
           of the Plug-in Pack. It has changed from PLUGIN to
           PLUGINS.

x:\netscape\PROGRAM\WIN16\PLUGINS

where x:\netscape are the drive and directory where you installed
Netscape Communicator 4.61.

Some Windows 3.1 plug-ins require specific installation steps:

  o Shockwave: The Shockwave installer should be run from
               WIN-OS/2 File Manager or from the Program Manager
               command line. After installation is completed,
               exit Program Manager.

  o Sizzler:   Sizzler displays a test window for an extended
               period of time the first time it is used. A Timeout
               message box might display. Click Retry until the
               test window completes its test.

If you prefer not to use the Windows 3.1 Plug-ins support after
installation, delete the Windows 3.1 Plug-in Support component
using the Plug-in Pack installation utility in the directory
where you installed Netscape Communicator 4.61.

To delete the Windows 3.1 Plug-in Support:

  1. Double-click the Installation Utility located in the
     folder where you extracted the os2pip30.exe file.

  2. Click Windows 3.1 Plug-in Support, and then click delete.

  3. Shut down and restart your operating system.

2.2 OS/2 Multimedia Plug-ins
------------------------------------------------------------------

The native OS/2 Multimedia Plug-ins in this package provide
support for multimedia MIME Types and file extensions such as
.mpg, .avi, .voc, .aif, .wav, .MID, and many others.

The OS/2 Multimedia Plug-ins provide support for streaming
multimedia. Certain files that support streaming can be played
while they are downloaded. A Multimedia Internet Manager program is
provided to access these files and it can be started from the
System setup folder after you install the plug-ins. The
Multimedia Internet Manager stores temporary files in
[X:]\MMOS2\INETTEMP (where X is the drive where multimedia
support is installed).

Note: When files are downloaded using the native OS/2 Multimedia
      Plug-ins, they are not deleted by the system even after you
      have exited Netscape Communicator 4.61. This can cause additional
      disk space to be consumed. The Multimedia Internet Manager
      in the System Setup folder allows you to remove some or
      all of these files as well as change the directory that
      contains this multimedia data.



3.0 IBM MPEG SUPPORT
__________________________________________________________________

The IBM MPEG support includes software MPEG video file playback
that does not require special MPEG hardware.

3.1 Recommended Hardware Configuration
------------------------------------------------------------------

A Pentium(R) or compatible microprocessor is required. Software
MPEG support can be used with a 486 microprocessor, but the video
quality is minimal.

Software MPEG audio support is available, but performs best on
systems with a Pentium or compatible microprocessor at 90MHz or
higher.

Hardware MPEG audio is supported with IBM Mwave(R) cards or
REALmagic cards.

MPEG hardware is used transparently, if it is available. An
updated REALmagic driver set is provided and installable if the
hardware configuration includes the REALmagic drivers. These
drivers should not be installed unless the hardware exists in
the machine where the drivers are being installed. For hardware
video support, VSDOM1.INI must be installed in the \MMOS2
directory. Using the OS/2 Multimedia MPEG Support installation,
select the MPEG card installed in the system.

A 2-speed CD-ROM drive that supports long reads is required to
play CD-i or Video CD content. Some OS/2 CD-ROM drivers do not
support the long reads that CD-i requires. CD-i content is not
readable through the file system. Playing this content requires a
dummy file named _VIDCDI.MPG. Playback quality is very choppy for
polling CD-ROMs.

3.2 Configurations with Existing MPEG Hardware Support
------------------------------------------------------------------

To configure OS/2 Multimedia MPEG Support to be used as the
default hardware MPEG device:

  1. In the Multimedia Setup, on the Association page for the
     existing MPEG hardware, select the MPEG data type and remove
     all current extensions.

  2. On the OS/2 Multimedia MPEG Support Association page, select
     the MPEG data type and add the following extensions:
     MPG, CDI, VBS, DAT, M1T, M2T, M2P.

3.3 Installing MPEG Hardware
------------------------------------------------------------------

OS/2 Multimedia MPEG Support installs hooks for the following
hardware devices:

  o  ThinkPad(R) 760CD MPEG

  o  ThinkPad 760ED MPEG

  o  Sigma Designs REALmagic

  o  Sigma Designs REALmagic Pro

  o  Visual Circuits ReelTime

If MPEG hardware is installed after the Plug-in Pack is installed,
the VSDOM1.INI file must be created by running the MKVSDINI.CMD
file in the \MMOS2 directory. For new MPEG hardware not in the
preceding list, modify the MKVSDINI.CMD file with the appropriate
PDD and VSD DLL. The PDD and VSD are defined in the MMPM2.INI file.
Do not include the $ character for the PDD.

In addition, if the DSP requires special loading, use the
appropriate numbers for the .dsp field to signify the following:

  o 1 Load DSP Only

  o 2 Load With MPEG Stream Info

3.4 Backward Compatibility for MCI applications
------------------------------------------------------------------

A video Media Control Device (MCD) is provided for backward
compatibility for existing applications that utilize the Media
Control Interface (MCI). This means the existing media player
provided with OS/2 Multimedia can be used to play MPEG content.


3.5 MPEG Limitations
------------------------------------------------------------------

  o MPEG-2 Transport streams with buffered play works only with
    188 byte size buffers. All others are rejected.

  o Playback from content on slow CD-ROMS (less than 4X) results
    in poor video playback quality.

  o If audio fails to play:

      1. Open the Multimedia Setup notebook in the System Setup
         folder.

      2. Click the OpenMPEG tab to go to the OpenMPEG page.

      3. Select Software Only.

    This change could be necessary for workstations using
    Audiovation sound cards.

  o To improve software MPEG performance, go to the OpenMPEG page
    in the Multimedia Setup notebook and change the
    synchronization factor to greater than 40 or to the maximum.
    (This slider is not proportional in changes.) Increasing the
    synchronization factor decreases the video quality but
    improves CPU performance so that software MPEG is not taking
    the maximum out of the CPU. This synchronization factor has
    no effect on hardware MPEG performance.

  o Video CD and CD-i content is supported with Software Video CD
    in the Multimedia folder. Systems with MPEG hardware, such as
    a ThinkPad 760, might have Video CD Player. This allows Video
    CD to run through the existing MPEG device. If Software Video
    CD is used on systems with MPEG hardware, OS/2 Multimedia MPEG
    Support attempts to play the content using hardware. Use the
    Software Video CD if the system has been customized with OS/2
    Multimedia MPEG Support as the default MPEG device.



4.0  CID INSTALLATION INFORMATION
__________________________________________________________________

CID installation is accomplished by using response files to install
the Plug-in Pack in a CID environment.

A response file is a flat ASCII file that consists of a series of
lines separated by newline sequences (0x0A, 0x0D, or a combination
of these two sequences).

Each line in a response file has a maximum line length of 255
bytes.

A response file has two kinds of lines:

  o Comment lines contain only white space characters or have
    either an asterisk (*) or a semicolon (;) as the first nonwhite
    space character on the line.

  o Response lines are used by Software Installer to determine
    the options and configurations to install on the target
    system.

Response lines have the following syntax:

keyword = value

  o Keywords cannot contain imbedded spaces.

  o Keywords are not case-sensitive.

You can group keywords together in value lists using the following
syntax:

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


Keyword-value pairs used in a response file can be in any order.
However, only one pair is allowed per line.

If you use any keyword names other than the supported keywords,
they are treated as installation variables. For example,
MONITOR = VGA creates a installation variable with the name of
MONITOR and a value of VGA.

Note: Do not use quotes around the component name, even when the
name is more than one word with blanks between words.

4.1 Sample Response File
------------------------------------------------------------------

The following command is an example of the command needed to start
a response file installation of the Plug-in Pack:

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

The following is an example of a response file used to install
OS/2 Plug-in Pack v. 3.0 in a US English environment:

Sample Response File

      COMP         = OS/2 Multimedia Plug-Ins for Netscape Communicator 4.61
      COMP         = 16-bit Plug-In Support for Netscape Communicator 4.61
      COMP         = OS/2 Multimedia MPEG Support
      CFGUPDATE    = AUTO
      DELETEBACKUP = NO
      OVERWRITE    = YES
      SAVEBACKUP   = NO
      NAV_PRESENT  = TRUE

4.2 OS/2 Plug-in Pack v. 3.0 keywords
------------------------------------------------------------------

The following response file keyword is required to install the
Plug-in Pack in a CID environment. The possible values for the
keyword are TRUE or FALSE:

     NAV_PRESENT - Netscape Communicator 4.61 for OS/2 Warp has
                   been already installed

Notes:

  o The FILE keyword should point to the directory where
    Netscape Communicator 4.61 was installed.

    For example:

    FILE = C:\NETSCAPE

  o The AUX1 keyword should print to the directory where OS/2
    Multimedia was installed.

    For example:

    AUX1 = C:\MMOS2

  o The value given in the COMP keyword in the response file must
    exactly match the string specified by the NAME keyword of the
    COMPONENT entry of the .PKG file. Refer to the OS2PIP30.PKG
    file at approximately line 125 for the OS/2 Multimedia
    Plug-ins, 295 for the 16-bit Plug-in Support, and 370 for the
    OS/2 Multimedia MPEG Support for the possible component names
    to specify.

5.0  NOTICES
__________________________________________________________________
This information was developed for products and services offered
in the U.S.A. IBM may 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:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1758
U.S.A.

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

IBM World Trade Asia Corporation Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or
any other country where such provisions are inconsistent with
local law:

THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY
KIND. IBM AND NETSCAPE DISCLAIMS ALL WARRANTIES, WHETHER
EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE
IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND
MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS
DOCUMENT. BY FURNISHING THIS DOCUMENT, NETSCAPE
COMMUNICATIONS GRANTS NO LICENSES TO ANY PATENTS OR
COPYRIGHTS.

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:

IBM Corporation
Department LZKS
11400 Burnet Road
Austin, TX 78758
U.S.A.

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.

5.1 Trademarks
------------------------------------------------------------------

The following terms are registered trademarks of the IBM
Corporation in the United States or other countries or both:

  o IBM

  o OS/2

  o ThinkPad

  o Mwave

The following are trademarks of other companies:

Netscape, Netscape Navigator, and the Netscape N logo are
registered trademarks of Netscape Communications Corporation in
the United States and other countries. Netscape Collabra, Netscape
Composer, Netscape Messenger, and Netscape Communicator are also
trademarks of Netscape Communications Corporation, which may be
registered in other countries.

Microsoft and Windows are registered trademarks of Microsoft
Corporation.

Pentium is a registered trademark of Intel Corporation in the US
and other countries.

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

(C) Copyright International Business Machines (IBM) Corporation
1995, 1999. All rights reserved.

