Questions and Answers About Running WordPerfect 5.1 for Windows under OS/2 2.0


 * May 1992

Question: What should be done if the message "Error DDEML.DLL Not Found. Insert In Drive A: And Press Any Key" appears when a user tried to start WordPerfect for Windows under OS/2 2.0?

Answer: WPWin installs this file into the C:\OS2\MDOS\WINOS2\SYSTEM directory. The file was not in this directory. The user can correct the error by running the WPWin install from a DOS full screen. Select a Custom installation and answer Yes to "Install Shared Product Files." The DOS full screen prompt is found by selecting OS/2 System, then Command Prompts. One user received this message because the OS/2 files were located on the C: drive and WPWin was installed to the D: drive. Copying the DDEML.DLL file to the C: drive corrected the error.

Another user not running under OS/2 corrected this error by copying the DDEML.DLL shared code file into the WPWIN directory or any other directory in the path.

Question: What directory should the DDEML.DLL file be stored?

Answer: If you install WordPerfect for Windows to a different drive from the drive containing Windows, the DDEML.DLL file will be placed in a \WINDOWS\SYSTEM directory on the same drive as where WPWin was installed. For example, if you have Windows on the C: drive, but are installing WPWin to a D: drive, the D:\WINDOWS\SYSTEM directory will be created. Since the DDEML.DLL needs to be in the same directory as Windows, you will need to copy the DDEML.DLL file from D:\WINDOWS\SYSTEM to C:\WINDOWS\SYSTEM. You can then delete the DDEML.DLL file and the \WINDOWS\SYSTEM directory from the D: drive.

Question: What should be done if under the OS/2 2.0 Windows portion, the screen fonts for the 8514 monitor do not show up in WordPerfect for Windows? Answer: The customer can use four Windows 3.0 for DOS font files to replace the font files OS/2 is using for the 8514 monitor. They are COUREF.FON, HELVF.FON, SYMBOLF.FON, and TMSRF.FON. These files can be found in the WINDOWS\SYSTEM directory and should be copied to the WINOS2\SYSTEM directory.

Question: A user has the initial 11/4/91 release of WPWin and wants to make it work through OS/2 2.0. How can this be done?

Answer: The interim release of WPWin (04/30/92) corrects the problem of users not being able to execute WPWin under OS/2 2.0. In the mean time you can use the FIXWP.EXE and UNFIXWP.EXE files to run the 11/04/91 release of WordPerfect for Windows on OS/2 2.0. These files are located in the C:\OS2\MDOS\WINOS2\SYSTEM\ subdirectory in the 6.177 revision of OS/2 2.0 and in the C:\OS2\MDOS\WINOS2\ subdirectory in the 6.304 revision. This fix from IBM modifies the WPWINFIL.EXE file. To use the fix type FIXWP \WPWINFIL.EXE at the SYSTEM subdirectory. After FIXWP.EXE is executed you will get a message telling you that WPWin will no longer run under DOS and to use UNFIXWP.EXE in order to execute WPWin under DOS. When the process is finished, a message will appear notifying the user that WPWin will no longer run under DOS unless they reverse the process by using UNFIXWP.EXE. However, one user was able to run WPWin under DOS without using UNFIX.EXE. This information can also be found in the readme file from OS2.

Note: Users who encounter this problem should be sent the interim release dated 04/30/92.

Question: Will WordPerfect for Windows run on any 1.x version of OS/2?

Answer: No. WordPerfect for Windows will run on OS/2 2.0 in the release of WPWin after 11/04/91.

Question: Can the customers in Canada who are still using the beta version of OS/2 2.0 be able to use the FIXWP command to run WordPerfect for Windows?

Answer: No. They will need to use the interim of WPWin after 11/4/91 or get the shipping version of OS/2 2.0.

Question: A user running OS/2 2.0 on a Novell network was unable to print from WordPerfect for Windows with WP printer drivers (11/04/91 program and 04/15/92 printer drivers). The user could print a file to disk and copy the print-to-disk file at DOS to the redirected port. How can the user print directly from WordPerfect for Windows?

Answer: The user can correct the problem by changing the printer port in WordPerfect to C:\OS2\SPOOL\LPTx.OS2. With this method, the print job is spooled to the directory then sent to the printer. Users must log on to the network with the Netware drivers first.

Question: The error "Sharing Violation" appeared when a user running under OS/2 2.0 tried to enter WordPerfect for Windows (11/04/91) using WPWIN.EXE instead of FIXWP.EXE. Now when the user reboots OS/2 2.0, the computer tries to load WPWin again and gives a sharing violation. What can the user do to correct this problem?

Answer: This is working as designed. OS/2 2.0 will try to activate the program that had the sharing violation when it is rebooted. To fix this, you will need to press Ctrl-Esc once it tries to start WPWin. This will take you to the Windows (task) list. You then need to open a DOS BOX and run the FIXWP.EXE \WPWINFIL.EXE to get into WPWin correctly. You can then make the change to the WPWin execution so that it will load with FIXWP.EXE instead of WPWIN.EXE.

Question: Do you need Microsoft Windows to run Windows programs (i.e., WordPerfect for Windows) in OS/2 2.0?

Answer: No. OS/2 2.0 can run Windows applications without having Microsoft Windows installed.

Question: Does WordPerfect for Windows support DDE links between OS/2 products and WPWin when WPWin is run in the OS2/WIN full screen of OS/2 version 2.0?

Answer: DDE text links only are supported currently. DDE Graphics links are not currently supported. The reason is that the link is using the Clipboard as an intermediary buffer.

Question: How can a user of OS/2 2.0 and WPWin set up WP Icons on the OS/2 Desktop?

Answer: The 11/04/91 release of WordPerfect 5.1 for Windows does not set up the WordPerfect icons on the OS/2 Desktop after it has been installed on OS/2 2.0. The steps below will allow users to set up the WordPerfect icons on the OS/2 Desktop:
 * 1) Double-click on the OS/2 System folder.
 * 2) Double-click on the System Setup folder.
 * 3) Double-click on Migrate Applications. The "Find Programs" window should appear.
 * 4) Remove the highlight by clicking once on the drives you do not want to search.
 * 5) Make sure there is a check mark next to "Windows Programs." To find programs faster and for easy identification remove the check marks left of the OS/2 and DOS application boxes.
 * 6) Click on Find to display the Migrate Programs window with a message "Searching For Programs Please Wait..." After a few minutes WordPerfect for Windows should be listed under applications.
 * 7) Remove the highlighting from the applications you do not want to migrate.
 * 8) Select Migrate! A folder, Additional Windows Programs, is created on the Desktop with the WordPerfect Icon.

Question: A user running WordPerfect for Windows under OS/2 2.0 on an OS2 Lan Server network would receive the error message "Unable To Print" and could not print with a WP printer driver. How can this problem be resolved?

Answer: The user can correct the problem by making sure the network was loaded in OS/2 Setup and by selecting LPT1.OS2 as the port.

Question: A customer was getting the error message "Cannot Find WPCSHAR1.DLL. How can this be resolved?

Answer: The following items are several things that should be checked: Possible workarounds would be as follows:
 * 1) The *.DLL files are found in WPC subdirectory.
 * 2) The WPWIN.EXE and WPWINFIL.EXE are found in the WPWIN subdirectory.
 * 3) Check for the WP{WP}.ENV file in the WPWIN directory and make sure that it contains the /WPC pointing to the shared directory and the /NI, /PS, and /NT switches.
 * 4) Check the order of entries in the CONFIG.SYS file. Any extended memory manager (e.g., QEMM, HIMEM, etc.) should be on the first line before everything else.
 * 5) Check the date on the disks. One user received this error when trying to install the 09/25/91 beta release of WPWin.
 * 1) Make sure that the path in the autoexec.bat file includes the WPWIN and WPC directories.
 * 2) Try copying the *.DLL files into the WPWIN directory.
 * 3) Try reinstalling after deleting all WPWIN files, including the *.INI files that are loaded right into the Windows subdirectory.
 * 4) Make sure the user has not changed the properties for the WPWin icon (File|Properties) from WPWIN.EXE to another filename such as WPWINFIL.EXE.