                     WordPerfect Corporation
                InfoShare Information Fax Service
                         (800) 228-9960

Title:   Running WordPerfect 6.0 for Windows Under OS/2 
Product: WordPerfect 6.0 for Windows 
Number:  1116-1/94 


Running WordPerfect 6.0 for Windows under OS.2
Running WPWin 6.0 under OS/2 2.x requires a special setup.  Most
of the information presented here is specific to OS/2 and is not
found in the reference manual.

What's in this document?

    Installing WordPerfect 6.0 from an OS/2 Full Screen Session
    WIN-OS/2 Settings
    Additional Settings for WPCorp DOS Products


Installing WordPerfect 6.0 from an OS/2 Full Screen Session

1    Double-click the OS/2 System icon.

2    Double-click the Command Prompts icon in the OS/2 System -
     Icon View window.

3    Double-click on OS/2 Full Screen

4    Insert the installation disk for WordPerfect in drive A:.

5    Type WIN/3 a:install at the OS/2 command line.

6    Follow the instructions on-screen.


WIN-OS/2 Settings


Setting Name        Default   Minimum   Suggested
                    Setting   Setting   Setting

WIN_RUN_MODE        Standard  Enhanced  Enhanced
DOS_FILES           20        70        100
DOS HIGH            OFF       ON        ON
DOB UMB             OFF       ON        ON
DPMI_MEMORY_LIMIT   4         6         8
EMS_MEMORY_LIMIT    2048      0         0
IDLE_SECONDS        0         5         5
IDLE_SENSITIVITY    75/95     95        95
XMS_MEMORY_LIMIT    2048      6144      6144+

The minimum or suggested settings can prevent several serious
problems that may occur when running WPWin 6.0 under OS/2. 
Customers who run WPWin 6.0 with the default WIN-OS/2 settings
have experienced frequent General Protection Faults (GPFs) and
"out of memory" errors.  These problems commonly happen while
trying to print, using Grammatik, editing large documents, or
doing anything that makes heavy use of memory.  Giving WPWin 6.0 
more memory usually solves these problems.

Even if you have not had any problems with WPWin 6.0 in a WIN-
OS/2 session, it would be a good idea to use the minimum or
suggested settings for more efficient performance.

Every icon that starts a Windows program from the OS/2 desktop
has its own WIN-OS/2 settings.  To change the settings for WPWin
6.0, the first step is to create an icon that starts WordPerfect. 

Create an icon by migration or by dragging out a template.  To
migrate WPWin 6.0 to the OS/2 desktop, click on the following
nested icons in the listed order:  OS/2 System, System Setup, ane
then Migrate Applications.  Refer to your OS/2 documentation for
further information on migration and templates.

Next, you will need to change the WIN-OS/2 settings that apply to
WPWin 6.0.

1    Click the WordPerfect for Windows program icon once with the
     right mouse button.  A pop-up menu will appear next to the
     WordPerfect for Windows icon.  You will see an arrow next to
     the Open selection.

2    Click once directly on the arrow to bring up a submenu.

3    Click the Settings option in the submenu, and a settings
     notebook will appear.  Clicking the tabs will turn the pages
     of the notebook.

4    Click the Session tab.

At this point, you can select which screen mode you would like to
operate under.  The options for WPWin 6.0 are either WIN-OS2
Window or WIN-OS/2 Full Screen.

5    Select WIN-OS/2 Full Screen.

6    Click the rectangular WIN-OS/2 settings... button.  A long
     alphabetical list of settings appears.  The following list 
     details the WIN-OS/2 settings that should be changed for the
     optimal performance of WPWin 6.0:


     DOS_FILES
          70 DOS_FILES are usually sufficient.  Setting it higher
          will not increase performance.  However, in some
          circumstances, OS/2 will not give the WIN-OS/2 session
          all of the requested files.  To compensate for this, we
          recommend setting DOS_FILES to 100.  If any of the
          following error messages still occur, set DOS_FILES to
          255 (the highest value allowed).

              ...insufficient file handles... 
              Cannot initialize, most probable cause...
              Not enough local/global memory... 

     DPMI_MEMORY_LIMIT   DPMI_MEMORY_LIMIT is the total amount of
                         memory (measured in megabytes) available
                         to the WIN-OS/2 session.  With many
                         systems WPWin can get by with 6, but
                         setting this number to 8 will further
                         improve performance without inhibiting
                         other programs.  Set DPMI_MEMORY_LIMIT
                         to 8 even if the machine only has 6M of
                         RAM.  OS/2 will create virtual memory on
                         the hard drive to make up the
                         difference.

          Even more DPMI memory will be needed if other Windows
          programs will be running in the same WIN-OS/2 session.
          DPMI rule of thumb: DPMI_MEMORY_LIMIT should be at
          least 2M higher than the sum of XMS_MEMORY_LIMIT and
          EMS_MEMORY_LIMIT.  Note that XMS and EMS memory limits
          are measured in kilobytes: 1024 kilobytes = 1 megabyte.

     EMS_MEMORY_LIMIT    EMS stands for expanded memory.  WPWin
                         6.0 does not use expanded memory.  Most
                         users should set this to zero.  

          NOTE: Running any Windows program that uses EMS memory
          in the same WIN-OS/2 Full Screen session with WPWin 6.0
          would be the only reason for setting EMS higher.  2048K
          (i.e., 2 megabytes) is usually sufficient.  After you
          raise the EMS_MEMORY_LIMIT, review the DPMI rule of
          thumb: DPMI_MEMORY_LIMIT may need to be raised as well.

     IDLE_SECONDS   IDLE_SECONDS is the number of seconds that
                    must pass before OS/2 begins monitoring the
                    application for idle detection.  An
                    application is considered idle when it is
                    repeatedly polling the keyboard for user
                    input.  Constant keyboard polling can bog
                    down the performance of concurrent
                    applications.  When OS/2 determines that an
                    application is polling too much, it lowers
                    the application's priority in order to give
                    other applications better performance.

          With the default settings in effect, OS/2 mistakenly
          thinks that WordPerfect is idle when it is performing
          such functions as text conversion or merging.  This can
          turn what should be a 4-second operation into a 1-
          minute operation!  Setting IDLE_SECONDS to 5 means that
          OS/2 will wait at least 5 seconds before lowering
          WordPerfect's priority.

     IDLE_SENSITIVITY    The value entered for IDLE_SENSITIVITY
                         represents a percentage of the total
                         amount of CPU time given to an
                         application.  A value of 95 means that
                         WordPerfect can spend up to 95% of its
                         allotted time polling the keyboard
                         before OS/2 lowers its priority. 
                         Setting IDLE_SENSITIVITY to 100 disables
                         idle detection since no application can
                         spend more than 100% of its allotted
                         time polling.

     XMS_MEMORY_LIMIT    WordPerfect uses XMS memory.  Most
                         customers have been able to eliminate
                         out-of-memory errors with
                         XMS_MEMORY_LIMIT set to 4096.

          Nearly all Windows applications use XMS memory.  If
          WPWin 6.0 is running at the same time as other
          applications, then set XMS_MEMORY_LIMIT higherwe
          suggest anywhere between 6144 and 16384.  You may have
          to raise DPMI_MEMORY_LIMIT to make sure that the DPMI
          rule of thumb is not violated.

If, after making these changes, you are still having problems,
you need to make sure that the new settings are in effect.  The
following conditions may cause problems:

         The settings you changed are saved with the WordPerfect
          for Windows icon, not with WPWin 6.0.  Should you need
          to create another icon that starts WPWin 6.0, be sure
          to change the settings for the new icon.  If WPWin 6.0
          is started from the WIN-OS/2 Program Manager, or from
          an OS/2 prompt, the desired settings will not be in
          effect.

         Starting WPWin 6.0 with the WordPerfect for Windows
          icon does not guarantee that the WIN-OS/2 session will
          use the new settings.  Before you start WordPerfect,
          make sure that a WIN-OS/2 session is not running. 
          Also, verify that no other Windows software (even the
          Windows Clock) is running.  Then start WPWin 6.0 by
          double clicking on the WordPerfect for Windows icon. 
          The new settings should be in effect.

There is a way to make sure that the WordPerfect for Windows icon
will always start WPWin 6.0 with the desired settings, even if a
WIN-OS/2 session is already running:  

1    Open the settings notebook for the WordPerfect for Windows
     icon.

2    Click the Session tab.

3    Click the box next to Separate session.



WordPerfect Corporation 1994

WordPerfect Corporation
1555 N. Technology Way
Orem, UT 84057-2399

WordPerfect is a registered trademark of WordPerfect Corporation
within the United States and other countries.  WordPerfect
Office, WordPerfect Presentations, WordPerfect Rhymer, and
WordPerfect Works are trademarks of WordPerfect Corporation
worldwide.