The following information documents known problems with the
current release of SoftSolutions 4.0 for Windows integrations.

Ŀ
            WordPerfect 6.0 for Windows BIF Files              


A NOTICE TO:

  1. Users that have WordPerfect 6.0 for Windows and
     SoftSolutions 3.1 and are upgrading to SoftSolutions 4.0, or

  2. SoftSolutions 4.0 Prerelease Testing sites using prerelease
     versions of the WordPerfect 6.0 integration with
     SoftSolutions.

With previous versions of the WordPerfect 6.0 for Windows
integration, the following files were placed in each user's
Windows SYSTEM directory:

     SHWIN20.DLL    SHWINB20.DLL    SHWINC20.DLL

These files must be deleted before installing the released
version of this integration.

Also, a change must be made to the public and private BIF files. 
Following is an explanation of WordPerfect for Windows BIF files
and the changes that must be made:

EXPLANATION:

     WordPerfect for Windows uses BIF files.  There are two types
     of WordPerfect BIF files:  a private BIF that holds a user's
     custom settings to WordPerfect for Windows, and a public BIF
     that has network settings for all WordPerfect for Windows
     users.

     There is only a public BIF if you are running WordPerfect
     from the network.  It is called WPCNET.BIF and is usually
     located in the WPCNET subdirectory (a brother directory to
     WPWIN60).

     The private BIF, in the case that you are running on the
     network, is a specialized name made up of your network name
     and some other numbers and letters.  For example, a private
     BIF might be ROBE44U2.BIF where ROBE is the first four
     characters of a user's login name.  This is usually located
     in the user's WINDOWS directory (c:\windows), but is
     actually configurable with the WordPerfect Install.

     If WordPerfect 6.0 for Windows has been installed locally
     only, the private BIF is called: WPCSET.BIF and is located
     in the Windows directory (c:\windows).

     The SoftSolutions 4.0 for Windows installation program will
     search for the WPCSET.BIF file or the WPCNET.BIF to add a
     reference to our DLL integration.  It will NOT look for the
     network private BIF files (ROBE44U2.BIF, in our example).

     In earlier versions of the WordPerfect 6.0 for Windows
     integration with SoftSolutions, you were instructed to
     modify your network private BIF files (ROBE44U2.BIF).  Now
     the SoftSolutions 4.0 installation process adds it
     automatically to the WPCNET.BIF files.  Having references to
     our integration DLL in both of these BIF files seems to
     cause GPFs, STACK FAULT errors, and other problems when
     starting up WordPerfect 6.0 for Windows.

     Also note, these same GPF problems can occur if a user has
     more than one reference to a SIWP6.DLL within the same BIF
     file.  For example, if items DLL1 and DLL2 in the "Third
     Party" section both point to C:\WPWIN60\SIWP6.DLL, then GPFs
     could occur when starting WordPerfect 6.0 for Windows.

RESOLUTION:

     One way to avoid these problems is to remove the reference
     to SIWP6.DLL in your private network BIFs (i.e.,
     ROBE44U2.BIF).

     To do this, run WordPerfect's BIFED20.EXE.  Select File|Open
     Private BIF.  Find the WordPerfect area and double-click on
     it to get a list of available sections.  Find the "Third
     Party" section and double-click on it to get a list of
     available items.  Find the DLL item that points to SIWP6.DLL
     and highlight it.  Then select the DELETE button from the
     right side of the BIF Editor dialog box.

     Another way is to tell users to delete their network private
     BIFs (ROBE44U2.BIF) if they do not or cannot use the BIF
     editor.  In this case, WordPerfect 6.0 for Windows would
     create a new private network BIF the next time the user ran
     WordPerfect 6.0 for Windows.  However, All private settings
     (button bar, WordPerfect File Preference items, etc.) are
     lost when the network private BIF is deleted and they would
     have to be re-done.  This method is probably not recommended
     for that reason.  The best answer is to use the BIFED20.EXE
     tool as provided by WordPerfect.

Ŀ
                           General                             


Be aware of the following issues that exist in the initial
release of SoftSolutions 4.0 for Windows integrations:

  1. When Microsoft Word for Windows is already open and you open
     a Microsoft Word document from within SoftSolutions, the
     document will be opened in the version of Microsoft Word
     already running regardless of the version of Microsoft Word
     indicated in the document's Profile.  For example:

          Microsoft Word for Windows 2.0 is running.  A Microsoft
          Word 6.0 document is opened through SoftSolutions.  The
          document is actually opened in Microsoft Word 2.0.

     This also occurs using Microsoft Excel 4.0 and 5.0.

  2. Currently, WordPerfect for Windows integrations is not able
     to detect when a figure box is selected at the time
     File|Exit or File|Close is chosen.  If a figure is selected
     when choosing one of these options, a Macro Facility error
     is reported.  After receiving the error, if the figure is
     deselected and File|Exit is chosen, a General Protection
     Fault error is encountered.  An error is also encountered
     when choosing File|Close after deselecting the figure.

     When using WordPerfect for Windows without integrations,
     WordPerfect detects if a figure is selected and will
     deselect it automatically when closing the file.

  3. WordPerfect 6.0 for Windows and MS Word 2.0 are both
     running.  Select Insert|Object in Word 2.0 and select
     "WordPerfect 6.0 Document" option.  Instead of WordPerfect
     6.0 coming up, the SSAPPINT FileNew dialog box is displayed. 
     A bug in WordPerfect concerning the token handler and
     recognizing whether WordPerfect is already in an OLE mode.

     A work-around for now is for the user to modify the
     SSWMAIN.WCM macro so that when the "New" macro is called, it
     only calls FileNew().

  4. For Lotus 1-2-3, Release 4, the combining function is not
     working correctly.  In combining a password-protected
     worksheet into the current worksheet, and entering the wrong
     password, 1-2-3 displayed COMBINE dialog box anyway (though
     nothing was combined).  The Lotus 1-2-3 "LciUtYield"
     function loop (specified by Lotus) is not working correctly. 
     This is also causing problems with combining text files, and
     opening/closing files.

     The "Combine" check box option has been disabled, for now.

  5. Microsoft Excel 5.0 integrations not available for the
     initial release of SoftSolutions 4.0 for Windows---WAITING
     FOR FINAL RELEASE by Microsoft of Excel 5.0 for Windows.

  6. Select a line in the SEARCH RESULTS window, then drag it
     down (hoping to scroll down) and it seems to corrurpt
     memory, causing a General Protection Fault error.  This has
     occurred with integrated applications that made
     "valid_option" calls through integrations as the document
     was being closed.  It causes scrolling to react improperly
     and locks SoftSolutions if a DOS window is open or
     minimized.

  7. The memory manager, 386MAX version 7, does not work with
     SoftSolutions.  When trying to log into SoftSolutions while
     using this product, memory errors are given.

  8. The SoftSolutions billing utility (SIWINBIL) is running. 
     Open a WordPerfect 6.0 for Windows document containing
     multiple pages and print a range of pages.  Close the
     document.  When the BILLING INFORMATION window is displayed.
     the Pages Printed field still shows 0 and no billing for
     pages can take place.

  9. WordPerfect 6.0 for Windows merge does not work with the
     SoftSolutions Document & Security Server (DSS).  If DSS is
     set up to use the Temp location, the merge will fill in the
     path and filename of where the DSS should have put the
     files, but the files never get there.

 10. Microsot Excel 4.0 charts are not being properly saved. 
     Using data from an Excel worksheet, create a chart,
     double-click on the chart to go into the chart-editing mode,
     do File|Save to save just the chart, and you are correctly
     prompted to fill in a new Profile for the chart.  But, after
     doing this, the chart title bar is messed up (just displays
     "-30"), and if you make any changes to the chart and then
     save it again, you are again prompted to fill out a new
     Profile.  

 11. If you do a File|New or a File|Open in an integration (such
     as MS Word 2.0) and change the dataset (into a dataset with
     a different password), Windows hangs.

 12. When you change the search scope, it is sometimes not
     properly executing the search to the new search scope.  The
     following steps illustrate:

       a. Start SoftSolutions.
       b. Change the current dataset to a second dataset.
       c. Do a search and change the search scope to search the
          original dataset ONLY.
       d. The search only searches the current (2nd) dataset that
          SoftSolutions was attached to (disregarding of the
          changes to the search scope).

 13. In Ami Pro, if you perform a merge using the DSS and choose
     to "merge, view and print," then after pressing OK on the
     MERGE dialog box, a sharing violation occurs.

 14. Using %I on a Launch command line, where the command line is
     using a batch file, results in a runtime overlay error 100%
     of the time.  Some PCs are using QEMM, VLMs and other
     miscellaneous configuration combinations, and some are using
     an EZLaunch calling a batch file that passes %I.  The
     problems are more sporadic when using the VLMs.  The batch
     file contains four lines:

          @ECHO OFF
          I:
          CL
          K:

     The error occurs after exiting the calendar program.
