             SoftSolutions(R) 4.1 for Windows Update

                     DOCUMENTATION REVISIONS
                               for
             SoftSolutions Administrator's Reference

        (C) 1995 Novell, Inc.  All Rights Reserved.  5/95
_________________________________________________________________

This file was created as an ASCII text file.  Any portion of this
file may be reproduced for use by licensed users of SoftSolutions
4.1 for Windows.
_________________________________________________________________

This document provides revisions to the SoftSolutions 4.0 for
Windows Administrator's Reference, dated 4-5-94, for updating to
SoftSolutions 4.1.

>> Windows and Memory Requirements  p. 6

Replace the paragraph under this heading with:

     SoftSolutions for Windows is designed to run on any machine
     set up to run Microsoft Windows 3.1 or higher in standard or
     enhanced mode.  SoftSolutions will run on a 386sx PC with
     4.0mb of RAM.  But, Novell recommends at minimum a 486 PC
     with 8mb of RAM.  Additional RAM may be required, depending
     on the number of applications opened simultaneously in
     Windows.

>> Network Support Issues  p. 6

Replace the first paragraph under this heading with:

     SoftSolutions can be implemented under a true client/server
     architecture.  The server side of SoftSolutions is available
     under NetWare, as well as SunOS, LAN WorkPlace, NCR SVR4,
     IBM AIX, SCO Unix, and Hewlett-Packard HP/UX.  (Contact
     Novell, Inc. for current availability.)

>> SEMs & Multiple Protocol Support  pp. 6-7

Replace the first two paragraphs under this heading with:

     The server software of SoftSolutions is called a "Server
     Enhancement Module" (SEM).  The SoftSolutions SEM runs as a
     NetWare 3.x/4.x NLM.  SoftSolutions SEMs are network-
     specific.  It is not possible to move a SoftSolutions SEM
     NLM and place it under an IBM Unix server.  Each SEM has its
     own model number for ordering.  SoftSolutions' SEMs are NOT
     interchangeable.

     Being a client/server model, SoftSolutions also has a client
     side.  The client software is the portion of SoftSolutions
     that runs on the workstations.  Under DOS (including
     Windows), the SoftSolutions client software is fully
     interchangeable.  This is true because support for NetWare
     and TCP/IP has been placed in the SoftSolutions DOS client. 
     This feature is called "Multiple Protocol Support."

>> File Services  p. 7

Replace the first paragraph under this heading with:

     The SoftSolutions client-side software supports the
     protocol, File Services.  This is intended to provide
     workstations with the ability to gain access to a dataset
     located on a server for which a SEM has not been
     specifically developed.  With this feature, SoftSolutions
     client software can have access to a dataset on a server
     from either Banyan Vines, LAN Manager, LANtastic, NetWare
     Lite, OS/2 LAN Server, and most other implementations of PC
     networks.

>> File Services  p. 7

Replace the third paragraph under this heading with:

     The previous paragraphs describe SoftSolutions running under
     a single dataset serviced by Banyan Vines, LAN Manager,
     LANtastic, NetWare Lite, OS/2 LAN Server, etc.  What happens
     if a configuration has MULTIPLE datasets under these network
     operating systems?  SoftSolutions without SEMs can, under
     certain circumstances, have access to multiple datasets
     located on different servers---assuming that the
     workstations are attached to the desired multiple dataset
     servers on a permanent basis with uniquely-mapped drive
     letters.

>> File Services & SEMs  p. 9

Replace all of the text under this heading with only the
following:

     File services can be mixed with SEMs.  SoftSolutions can
     exist in a network with multiple servers, with some servers
     running SEMs, and with other servers running file services. 
     A workstation connected to a mixed network can perform a
     global search and gain access to datasets via the
     SoftSolutions SEM NLM, SoftSolutions SEM for Unix, and file
     services---all because of the Multiple Protocol Support.

>> Server Enhancement Module (SEM)  p. 10

Replace the paragraph under this heading with:

     A SEM is a separate software module from Novell, Inc. that
     allows SoftSolutions to have access to data using the
     client/server technology.  The SEMs are loaded on the server
     and are executed and run from the server with communication
     to and from workstations.  Currently, a SEM is now available
     under NetWare 4.x.  SEMs are available for SunOS, LAN
     WorkPlace, NCR SVR4, IBM AIX, SCO Unix, Hewlett-Packard
     HP/UX.  SEMs allow the network to split up the work between
     the Server and the Client, and therefore will generally give
     better performance and a more seamless method of searching
     across datasets.

>> Multiple Protocol Support  p. 11

Replace the first sentence in this paragraph with:

     This is SoftSolutions' capability of accessing datasets via
     IPX/SPX, TCP/IP, or file services without the need for a
     different set of programs.

>> Item 7.  p. 12

Replace the text in parentheses with:

     (e.g., BW/NFS & NetWare; NetWare & Banyan Vines; Pathworks;
     LAN WorkPlace; and LAN Manager)

>> Configuration Examples  pp. 14-20

Delete the configuration examples and their accompanying text on
pages 14, 15, 17, 18, 19 and 20 (keeping the examples on pages 13
and 16).  Replace the text under the "NetWare/RS6000"
illustration with:

     This configuration has the data placed on a RISC-based
     system running Unix.  The data is to be accessed via a
     client/server connection using the SoftSolutions SEM for
     Unix.  Since the RS6000 and NetWare systems both store
     documents, the workstation must have access to each system
     using file services.  This is why LAN WorkPlace and the
     NetWare shell are loaded on the workstation.  The Indexer is
     running as a daemon process on the Unix machine to take
     advantage of the fast processing capabilities of the RISC
     system.  To give the Indexer access to the documents on
     NetWare, an NFS (Network File Services) connection must be
     made between the RS6000 and the NetWare server.

>> NetWare Transaction Tracking System (TTS)  p. 21

Include "and 4.x" in the reference to "NetWare 3.11" in the first
sentence.

>> Optimizing a Dedicated Indexer's Performance  p. 23

Remove "386" from the PCs listed in the fourth bullet.

>> Optimizing a Dedicated Indexer's Performance  p. 23

Remove the bullet at the bottom of the page (concerning using a
RAM disk).

>> Optimizing a Dedicated Indexer's Performance  p. 24

Replace the last bullet (concerning DOS-based indexers) with the
following:

   * The DOS-based Indexer is faster than the Windows-based
     Indexer.  Therefore, SoftSolutions for Windows includes a
     DOS-based Indexer program.  Both SoftSolutions 4.1 for DOS
     and SoftSolutions 4.1 for Windows use the same database, so
     the DOS-based Indexer should be used.

>> Configuring the File Server to Optimize an Indexer  p. 25

Change the reference to "NetWare 386" to read "NetWare."

>> Importance of a Balanced Configuration  p. 25

Change the reference to "486 EISA" to read "Pentium."

>> Considerations  p. 30

Add the following to the NOTE:

     Each user also requires the operating system's "sharable"
     rights to the data directory.  If the SoftSolutions SEM
     (Server Enhancement Module) is in use, ALL rights to the
     data directory can be removed for users.

>> Drive Letters vs. "Logical" Paths  p. 31

Replace the first two sentences of the first paragraph with:

     Novell, Inc. recommends using logical paths versus drive
     letters for defining document locations.  For example, using
     FS1/VOL1:\JAC\CORR instead of F:\JAC\CORR.

>> Universal Filing System  pp. 39-40

Replace the first paragraph with:

     This feature enables SoftSolutions to manage documents
     stored on other computer platforms and operating systems,
     such as Unix, OS/2, or IBM AS/400.  This requires disk or
     file services to already exist between the different
     operating systems and DOS or Unix.  The Universal Filing
     System feature gives SoftSolutions the ability to manage
     mixed document storage on DOS networks, Unix systems,
     mainframes, minicomputers, etc.

Then, delete the second paragraph (that begins "For example,
...").

>> Rights  p. 42

Add the following to the NOTE:

     Each user also requires the operating system's "write"
     access to at least the SOFTSOL.CTX file to prevent errors.

>> ~ (in table)  p. 76

Add the following paragraph to the explanation of the tilde (~)
character:

     Note that if two consecutive tildes are entered (~~) in the
     creation template, a single tilde (~) is placed in the
     document.  But, if a space is placed between the tildes
     (~ ~) in the template, two successive hard returns are
     placed in the document.

>> Defining Applications to be used by DOS and Windows
Users  p. 79

Replace the sentence and its example at the bottom of the page
with:

     Using ^filename, the command line for WordPerfect 5.1 may
     be:

          ^C:\WPFNAME.TXT /U=%U %WIN:INT:WPWINFIL.EXE

Note that the changes reflect the example is for WordPerfect 5.1
for DOS, and the "%P%F" parameter is removed from the command.

>> Defining Applications to be used by DOS and Windows
Users  p. 80

Remove "%P%F" from the command line example.

>> OAM Functions:  Archive  p. 85

Insert the following before the last sentence of the page:

     Be sure NOT to make any mistakes when editing an OAM command
     line.  The parameters must be correct to prevent problems in
     SoftSolutions.

>> Dataset ID  p. 93

The Dataset ID is now "SOFTSOL," not "SS."

>> Visit Pages Printed  p. 97

Replace all of the text under this heading with the following:

     Indicates whether users are to have access to the "Pages
     Printed" field in the BILLING INFORMATION dialog box.  If a
     document belonging to a billable document type and
     application is created or edited, a BILLING INFORMATION
     dialog box may display upon exiting the document.

     SoftSolutions automatically track pages printed for
     WordPerfect, Microsoft Word, and Ami Pro (all Windows
     versions of each).  SoftSolutions cannot automatically
     calculate the number of pages printed for other
     applications.  Therefore, to track their number of pages
     printed, the "Visit Pages Printed" flag must be set to Yes
     for accessing the PAGES PRINTED dialog box.  The default is
     No.

     This field may be changed at any time.  This field is not
     visited if "Bill?" is set to No.

>> Visit Location Field  p. 98

The last sentence in the first paragraph states that the default
is "Yes"---this is incorrect, it should be "No."

>> Visit File Field  p. 105

The last sentence in the first paragraph states that the default
is "Yes"---this is incorrect, it should be "No."

>> Datasets  p. 123

Add the following NOTE after the second paragraph:

     NOTE
          Datasets are NOT CREATED in this window.  Use this
          window to "point" SoftSolutions to an existing dataset. 
          Use the SoftSolutions installation CD/diskettes to
          create a dataset.

>> Field Definitions:  Code  p. 128

Add the following bolded sentence to the paragraph:

     Only alphanumeric characters should be used in the code.

>> Transferring the Data  p. 149

Replace references to "SSFORWARD" with "SSFORWRD" (eight
characters vs. nine).

>> The /ID= Switch  p. 154

The second sentence under "WorkStation ID" incorrectly states to
use the "/WID= switch," which should instead be listed as the
"/ID= switch."

>> Stop Words  p. 169

Add the following information to the discussion on Stop Words.

     The maximum Stop Word length is seventeen (17) characters. 
     Since only the first 17 characters of any word are indexed
     by SoftSolutions, a Stop Word cannot be longer than 17
     characters, else it would not be unique.

>> Users  p. 178

Replace the paragraph at the top of the page with:

     For example, "SOFTSOL" is automatically created by
     SoftSolutions and is given the status of system
     administrator.  "SOFTSOL" is also assigned the screen access
     group of "SYSM," granting access to all windows and options
     in SoftSolutions.  By default, time spent by "SOFTSOL" in
     creating or revising a document is NOT billable.  "SOFTSOL"
     is assigned the screen definition of "WINDEF."

>> Field Definitions:  Code  p. 178

Change the reference to a user code of "SS" to "SOFTSOL."

>> Doc Security Group  p. 182

Add the following NOTE after the second paragraph:

     NOTE
          If this field is used, its entry takes precedence over
          any defaults in the Screen Definition record.

>> Field Definitions:  Frequency  p. 187

Remove the @ symbols from the examples at the bottom of the page: 
"@7:4:12:00" should be "7:4:12:00" and "MON-FRI:@24:00" should be
"MON-FRI:24:00."

>> Sample Tasks  p. 188

Remove the @ symbols from the examples in the table.  They appear
under the "Frequency" heading for the first five items.

>> Maximum Size in Bytes  p. 193

Replace the first paragraph with:

     The amount of space available for echoing.  The default is 5
     megabytes.

>> Temp Loc  p. 194

Add the following NOTE after the last paragraph:

     NOTE
          If the temporary location is set to a RAM drive, ensure
          that there will be enough memory.  Too little memory in
          a RAM drive will cause problems for SoftSolutions' use
          of the temporary location.

>> Backup of the SoftSolutions Database  p. 207

Add the following paragraph to the NOTE at the top of the page:

     If TTS is in use, files in the destination directory that
     are flagged as "transactional" cannot be backed up by
     SSBACK.

>> Word Correction  p. 207

In the bolded text concerning SSBACK, the phrase "...make your
won backup..." should read "...make your own backup..."

>> Custom Fields Switch (/CUST=)  p. 212

Under "Custom Field," the last paragraph is not clear on the use
of the quotation marks.  It should be changed to read:

     Only the first word after the /CUST= switch is read by
     SoftSolutions, unless quotation marks are used.  To have
     both words in "PROJECT ALPHA" read by SoftSolutions, quote
     marks should be placed around the entire switch.  For
     example:

          "/CUST=PROJECT ALPHA"

>> Multiple Workstation Reconstruction  p. 238

The underlined "+" after "[Record Number] in the examples should
only be minus signs:

     RECONSS /RANGE=[Record Number]-[Record Number]
     RECONSS /RANGE=[Record Number]- 

>> Multiple Workstation Reconstruction  p. 239

Replace the "=" sign in the example in item "1)" with a space so
that it reads:  "RECONSS  /RANGE=0-4000."
