Running WordPerfect 5.1/5.2 for Windows Under OS/2

Running WPWIN under OS/2 requires some special setup.  Much of the
information presented here is specific to OS/2 and is not found in the
reference manual.


Installing WordPerfect 5.2 from a WIN-OS/2 Full Screen Session

Double click on the 'OS/2 System' icon.  Find the 'Command Prompts' icon in
the 'OS/2 System - Icon View' and double click on it.  Double click on
'WIN-OS/2 Full Screen'.  Click on 'File' in the 'Program Manager'.  Click
on 'Run'.  Insert the installation disk for WordPerfect in drive A.  Type
A:INSTALL and click on 'OK'.  Follow the instructions on the screen.

At the end of the installation this error may occur: WPINST.EXE has caused
an error in WIN-OS/2, GP Fault in module OS2K286.  This error happens
almost every time WordPerfect for Windows 5.2 is installed under OS/2 2.0.
Make sure that OS/2 has fully recovered from the error by closing all
applications and rebooting.

Start up WordPerfect.  If it has problems coming up see Common startup
problems.  If WordPerfect starts error free then close the application and
see WIN-OS/2 Settings for the next step.


For those using Dual Boot or Boot Manager, Installing WordPerfect 5.2 with
Microsoft Windows and then running it from OS/2

WordPerfect can be run from OS/2 after being installed under Microsoft
Windows, but some files need to be copied from Microsoft Windows to
WIN-OS/2:

OLECLI.DLL  DDEML.DLL  SHELL.DLL WINHELP.EXE WINHELP.HLP

In this example OS/2 and Microsoft Windows are both located on the C drive.
 The user has already booted with Microsoft DOS, installed WordPerfect
under Microsoft Windows, and booted up to OS/2.  After creating an icon,
the user tried to start WordPerfect but an error appeared saying OLECLI.DLL
could not be found.  To avoid this and future problems the user needs to
perform the following commands from an OS/2 prompt:

COPY C:\WINDOWS\SYSTEM\OLECLI.DLL C:\OS2\MDOS\WINOS2\SYSTEM
COPY C:\WINDOWS\SYSTEM\DDEML.DLL C:\OS2\MDOS\WINOS2\SYSTEM
COPY C:\WINDOWS\SYSTEM\SHELL.DLL C:\OS2\MDOS\WINOS2\SYSTEM
COPY C:\WINDOWS\WINHELP.EXE C:\OS2\MDOS\WINOS2
COPY C:\WINDOWS\WINHELP.HLP C:\OS2\MDOS\WINOS2

Start up WordPerfect.  If it has problems coming up see Common startup
problems.  If WordPerfect starts error free then close the application and
see WIN-OS/2 Settings for the next step.


Common startup problems

The problems listed below are solved with startup options.  See Appendix O
of the reference manual for further details on all the startup options that
work with WPWIN.EXE.

Problem:  Upon starting WordPerfect a message says, "Cannot initialize -
The most probable reason is insufficient memory."  After clicking on 'OK'
the user is taken back to the desktop.


Solution:  This is a common problem when trying to run WordPerfect on a
network station.  WordPerfect creates temporary files when it starts up
that are then deleted when the program is terminated.  If for some reason
the temporary files cannot be created then WordPerfect will not run.  Use
the startup option '/d' to tell WordPerfect where to create the temporary
files.  The best place to put temporary files is on the local hard drive.
Example:

     /d-C:\TEMP

Problem:  Upon starting WordPerfect a message says, "Network not loaded."
The message flashes briefly and WordPerfect starts up successfully.

Solution:  This problem usually happens on a Novell network.  Under OS/2
2.0 WordPerfect does not recognize that Novell is running.  Tell
WordPerfect to look for generic network protocol with the following startup
option:

     /nt-0

Problem:  Upon starting WordPerfect a message says, "Directory path for the
shared code is invalid" or "Cannot find WPCSHAR1.DLL.".  Startup fails
after either of these error messages.

Solution:  The '/wpc' startup option tells WordPerfect where to look for
the shared code files.  Shared code files have a 'DLL' extension.  The
WordPerfect installation places shared code files in a separate directory.
The first error message indicates that '/wpc' was used to specify a
directory that does not exist (or in a network environment a directory that
the user does not have sufficient rights).  The second message means that
the directory exists but that a necessary shared code file was not found in
the directory.  If the shared code files are located at N:\APPS\WPC include
the following startup option:

     /wpc-N:\APPS\WPC


WIN-OS/2 Settings

Setting Name Default Setting Minimum Setting Suggested Setting


DOS_FILES 20 40 100


DPMI_MEMORY_LIMIT 2 or 3 6 8


EMS_MEMORY_LIMIT 2048 0 0


IDLE_SECONDS 0 5 5


IDLE_SENSITIVITY 75 95 95


XMS_MEMORY_LIMIT 2048 4096 6144


The Minimum or Suggested Settings can prevent several serious problems that
can occur when running WordPerfect under OS/2.  Customers who run with the
Default Settings have experienced frequent General Protection Faults (GPFs)
and Out Of Memory Errors.  It is common for problems to happen while trying
to print, while using Grammatik, while editing larger documents, or while
doing anything that makes heavy use of memory.  Giving WordPerfect more
memory to run in usually solves these problems.

Even if you have not had any problems with WordPerfect in a WIN-OS/2
session it would be a good idea to use the Minimum or Suggested Settings
for faster performance.

Every icon that starts up a Windows program from the OS/2 desktop has its
own WIN-OS/2 settings.  So to change the settings the first step is to
create an icon that starts up WordPerfect.  Create an icon by Migration or
by dragging out a Template.  'Migrate Applications' is located in 'System
Setup', and 'System Setup' is located in 'OS/2 System'.  See the OS/2
documentation for further information on Migration or Templates.

To get to the WIN-OS/2 settings that apply to WordPerfect you need to click
on the 'WP' icon a single time with the right mouse button.  This brings up
a menu next to the 'WP' icon.  Notice the arrow next to the 'Open'
selection.  Single click on this arrow to bring up a sub-menu.  Click on
'Settings' in the sub-menu.  A settings notebook appears.  Pages of the
notebook can be turned by clicking on the tabs.  Click on the 'Session'
tab.  Click on the rectangular button that reads 'WIN-OS/2 settings...'.  A
long alphabetical list of settings appears, six of which need to be
changed.

Usually it is not necessary to understand what the settings do.  But if the
Minimum or Suggested Settings do not help, or if you are simply curious see
the next section for a better understanding.

Guidelines for customizing WIN-OS/2 Settings

DOS_FILES          DOS_FILES is the total number of files a program can have 
open at any given time.  40 files is 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.  In order to compensate
we recommend setting DOS_FILES to 100.  If the error message, Insufficient 
File Handles, still happens set DOS_FILES all the way to 255.

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
WordPerfect can get by with 6, but to be on the safe side set it to 8.  Set
DPMI_MEMORY_LIMIT to 8 even if the machine only has 6 meg 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.  Set DPMI_MEMORY_LIMIT to 12
or higher.  Some customers have had good success running as high as 64.

DPMI rule of thumb: DPMI_MEMORY_LIMIT should be at least 2 meg
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.  WordPerfect for
Windows does not use expanded memory.  Most users should set this to zero.

Running a Windows program that uses EMS memory in the same session with
WordPerfect would be the only reason for setting EMS higher. 2048 (ie. 2      
megabytes) is usually sufficient.  After raising EMS_MEMORY_LIMIT review
the DPMI rule of thumb.  DPMI_MEMORY_LIMIT may need to raised as well.

IDLE_SECONDS             IDLE_SECONDS is the number of seconds before OS/2
begins monitoring the application for idle detection.  An application is 
idle when it is repeatedly polling the keyboard for user input.  Constant 
keyboard polling can bog down the performance of other 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 prematurely puts WordPerfect "on the
back burner."  OS/2 mistakenly thinks that WordPerfect is idle
when it is doing something like 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 makes heavy use of XMS memory.  Most
customers have been able to eliminate out of memory errors with 
XMS_MEMORY_LIMIT set to 4096.

Almost all Windows applications use XMS memory.  If WordPerfect is running
along side other applications then set XMS_MEMORY_LIMIT higher, from 6144
to 16384.  You may have to raise DPMI_MEMORY_LIMIT to make sure that the
DPMI rule of thumb is not violated.



Still having problems?  Make sure that the new WIN-OS/2 Settings are in
effect

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

But even starting WordPerfect with the 'WP' icon is no guarantee that the
settings will be in effect.  Before starting WordPerfect make sure that no
WIN-OS/2 session is running.  Make sure that no other Windows software
(even the Windows clock) is running.  Start WordPerfect by double clicking
on the 'WP' icon and the new settings will be in effect.

There is a way to make sure that the 'WP' icon will always start
WordPerfect with the desired settings, even if a WIN-OS/2 session is
already running.  Open the settings notebook for the 'WP' icon and click on
the 'Session' tab.  Mark an X in the box next to 'Separate session'.


Trouble shooting for hardware compatibility

If you are certain that the new settings are in effect and WordPerfect is
still having problems then try these five startup options:

     /nc /nd /ne /nk /nh

Click on the 'WP' icon with the right mouse button.   Click on the arrow
next to 'Open'  and then click on 'Settings'.  Type the above startup
options in the text area titled 'Parameters:'.  Include a space between
each setting.  Close the settings notebook by double clicking in the upper
lefthand corner.  Start WordPerfect by double clicking on the 'WP' icon.
Test WordPerfect to see if the problem is solved.

If the problem was solved it is a good idea to narrow down which option
made the difference.  Any one of these five startup options could have
solved the problem.  Remove them one by one, testing WordPerfect each time.
 See Appendix O of the WordPerfect reference manual for details on what
each startup option does.


Installing Grammatik for use with WordPerfect

Grammatik has its own installation.  Start up a WIN-OS/2 Full Screen
session.  Click on 'File' in the 'Program Manager'.  Click on 'Run', type
A:INSTALL, and click on 'OK'.  Follow the instructions on the screen.

During the installation an error may pop up twice:

     Error calling BITMAPS.DLL, ...

Each time the error occurs click on 'OK' to continue with the installation.
 Because of the error the AUTOEXEC.BAT file needs to be modified.  The path
where Grammatik was installed to needs to be added to the PATH statement.
Also, a statement that reads SET GMKW5=(the path where Grammatik was
installed) needs to be included.  For example, if Grammatik was installed
to C:\GMKW then your AUTOEXEC.BAT file should look something like this:

@ECHO OFF ECHO. PROMPT $i$p$g REM SET
DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512; PATH
D:\SO:\OS2\MDOS;D:\OS2\MDOS\WINOS2;D:\;C:\GMKW; SET GMKW5=C:\GMKW LOADHIGH
APPEND D:\SO:\OS2\SYSTEM SET TMP=D:\ REM LOADHIGH DOSKEY FINDFILE=DIR /A /S
/B $* REM DOSKEY EDIT=QBASIC/EDITOR $* REM SET DIRCMD=/A SET
TEMP=D:\OS2\MDOS\WINOS2\TEMP


Installing Adobe Type Manager 2.5

The ATM diskette has its own installation program.  Before installing it
however, the SYSTEM.INI needs to be changed.  The changes are documented in
paragraph 13 of the README.TXT file located on your ATM diskette.

