                  Saber LAN Workstation 1.0d
                    Release Notes - July 1993
                       
Thank you for your purchase of Saber LAN Workstation. As with all 
Saber products, we would like to have your comments. If you have 
not already done so, please complete and return the
registration card and include your suggestions or comments.

Information in addition to the documentation provided with the 
product is contained on these two files, as follows:

README1.TXT
	Getting Started
	Quick Tutor
	Menu for Windows
	INI Manager
	Print Manager for Windows
	Saber Console and Agents
	

README2.TXT
	Menu for DOS
	Print Manager for DOS
	Secure
	Saber Editor
	Report Generator
	Notes for NetWare 4.0 Users


___________
GETTING STARTED

Saber LAN Workstation 1.0d includes a new
"Getting Started" manual. The material now includes
instructions for configuring your network for the various
LAN Workstation components.

___________
QUICK TUTOR

Saber LAN Workstation 1.0d contains the Quick Tutors, an additional
online Help feature available in the Windows environment. The files
required to run Quick Tutors are stored in the directory
\SABERWKS\QTUTOR or the directory specified during installation.
In order for users to have access to the tutorials, the LAN administrator
must make the file QT.INI available in the users' Windows startup directory.

Two types of tutorials are available:

     -  Menu for Windows
     -  Console

To run the Quick Tutor, select Help from the SMENU or Console
menu bar. Then click on Quick Tutor.

The first time users run the Quick Tutor feature, the file QT.INI is added
to the user's Windows startup directory, and instructions for using the tutorial
are displayed.


________________
MENU FOR WINDOWS
                              
This section covers the following topics:

     - Temporary files
     - Additional SMENU.INI settings
     - Creating custom help files
     - Desk accessory keys
     - Additional icon information
     - Menu style
     - Network messaging
     - A note about Userlist
     - Using the Run option
     - Setting Run Options for DOS applications
     - DOS environment variables in Windows
     - LINK Commands
     - Security
     - Additional features 
     - Corrections to reported problems
     - Known program anomalies
     - Documentation errata


Temporary Files
---------------

When performing some functions, SMENU creates temporary .PIF and
.BAT files. These temporary files are automatically deleted if 
the path and file \USER\SMENU_X.BAT are in the default installation 
directory SABERWKS or in the installation directory you specified.


Additional SMENU.INI Settings
-----------------------------

In addition to the SMENU.INI settings described in "Saber Menu
Reference," Part 3: Menu for Windows User's Guide, the following
options may also be set:

MailProgram=             References a mail program that is to be
                         executed if the user double clicks on
                         the mail waiting icon.  If this option
                         is not set, a message box is displayed
                         indicating that new mail is waiting.
                         This option is only available using an
                         MHS- or Higgins-based mail program.

MailRefresh=             Indicates the time, in seconds, between
                         checks for new mail. The default is 60
                         seconds. Zero (0) disables mail
                         checking.

StatusRefresh=           Indicates the time, in seconds, between
                         checks for updates to the status window
                         directory and disk space display.  The
                         recommended time for most installations
                         is 20 seconds.  The default is 0 (checking
                         is turned off).

TimeRefresh=             Indicates the time, in seconds, between
                         updates to the displayed system time.
                         The default is 1.
            
MessageRefresh=          Indicates the time, in seconds, between
                         checks for updates to the message
                         window.  The recommended amount of time
                         for most installations is 600 seconds
                         (10 minutes).  The default is 0 (checking
                         is turned off).
            
BlankActiveDOSWin=       When set to 'yes', blanks the screen
                         for an active DOS session running
                         in a window (not valid with DOS full-
                         screen mode).  This feature blanks the
                         screen after the amount of time specified
                         elapses, whether or not there's keystroke
                         activity.
                         Values are 'yes' and 'no'.
            
NetworkMessageRefresh=   Indicates the time, in seconds, between
                         checks for a Network message. The default
                         is 60 seconds. The 0 setting turns off
                         message checking.


Note: In versions 1.0 and 1.1 of the Saber Menu for Windows, the 
[Saber Menu System] section in WIN.INI was used to record menu 
settings.  Later versions record menu settings in SMENU.INI, and 
corresponding settings in WIN.INI are ignored.


Creating Custom Help Files
--------------------------

You can create custom menu and item Help that is available
when the user presses the F1 key using any ASCII text
editor, such as Notepad.  For SMENU to locate the
appropriate Help text, you reference menu numbers and item
descriptions in your customized Help files.  Help files must
have exactly the same 8-character file name as the menu data
file (.DAT), with a .HLP extension.  Also, help files must be
located in the same directory as the menu data file.
            
When creating help text, you indicate which menu the text
pertains to by typing an asterisk (*) immediately followed
by the menu number.  After the menu number, enter a space
and then the title to appear on the help panel.  For
example:
            
     *46 Utilities Menu Help
            
On the following line, indicate to which item help text
pertains by typing a caret (^) followed by the item
description.  On the next line, enter the help text.  In
order for SMENU to locate item help text, you must enter the
item description in the help file exactly as it appears in
the menu data file, including case and punctuation.  For
example:
            
     ^Setup Menu...
            
If you want a default Help message to be displayed for items
without customized Help, enter the text to be displayed
after the menu reference and before the first item reference.
            
Example:
            
     *1 Main Menu
     This item displays a submenu of related items.
     ^Word Processing
            
If you don't specify customized help for an item, the text
you enter after the menu reference is displayed when users
press F1.
            
Remember, follow the menu (*number) or item (^description)
Help reference with the text needed for your Help panel.
Help text is displayed exactly as you enter it, without
wrapping.
            
Here is an example of a customized Help file:
            
     *1 Main Menu
     This item displays a submenu of related items.
     ^Setup...
     Sample help text for sub menu Setup.
     *2 Setup
     ^Windows Setup
     Use Windows Setup to change your default display driver for
     either higher or lower resolution depending on your
     monitor's capability.
     ^PIF Editor
     Use PIF Editor to specify additional Windows information
     about DOS programs, such as memory required, use of EMS and
     XMS memory, etc.
     ^DOS
     Run DOS to access the DOS command line.
     ^Microsoft Systems Diagnostics
     Use MSD to help debug problems with Windows and your
     systems.
     *3 Games
     ^Solitaire
     Solitaire is the Windows variation of the popular single-
     player card game.
     ^Minesweeper
     Minesweeper tests your ability to locate mines using simple
     reasoning.
     *4 Accessories
     Windows utility.
            
Note:  As shown under Accessories, the simplest form of Help
is text which applies to all items on the menu.  This text is
displayed on one help panel--separate panels are not defined
for each menu item.

            
Desk Accessory Keys
-------------------

Desk accessory keys (D/A Keys) were first provided in the Saber
Menu for DOS and are available in SMENU primarily for compatibility
between the two systems.  DA/Keys may be used any time the menu
system is the active application and is receiving keyboard input.
For example, D/A Keys are not available if Windows File Manager
is the active application.  You define DA keys in the file SABER.KEY.
            
A sample D/A Key file (SABER.KEY) is shown below.
            
     *File Manager { SURFACE=WINDOWS }
           WINFILE.EXE
     *Calc { SURFACE=WINDOWS }
           CALC.EXE
     *Calc { SURFACE=DOS }
           ACALC
            
     [ALT]
     *Print Manager { SURFACE=DOS }
            PRTMGR.EXE
            
     *User Listing { SURFACE=DOS NOECHO SHOW }
            USERLIST > $USERLST.DAT
            README $USERLST.DAT
            DEL $USERLST.DAT >> NUL:
            
     [SHIFT]
     *DOS { PIF=DOSPRMT.PIF }
            DOS
     *Exit { PSWD=EXIT }
            EXIT
     *Logout { }
            LOGOUT
     *PIF Editor { SURFACE=WINDOWS }
            PIFEDIT.EXE
            
     [CTRL]
     *Drives { SURFACE=WINDOWS }
            DLINK.EXE
     *Wait { SURFACE=WINDOWS }
            WINWAIT.EXE
     *Station Info { SURFACE=WINDOWS }
            STATION.EXE
            
To disable D/A Keys, add the following line to SMENU.INI:
            
            DAKeyAvail=NO

            
Additional Icon Information
---------------------------

In addition to the icons provided in SAPPS.SIL, icons are
available from a variety of other sources, including many
forums on CompuServe.  When retrieving icons for your menus,
we recommend that you create several icon librarian files
(filename.SIL) to help organize icons.  Although there's no
limit to the number of icons you can store in a .SIL file,
to create and organize several .SIL files makes locating
and retrieving icons faster and easier.
            
            
Menu Style
----------

The default system style is Desktop. The default menu style is Icon List
(icon with a text label beside it).

When you use Menu for Windows in Palette style, set up your 
menus and arrange the desktop before you turn the caption off. 
Once the caption is turned off, you cannot resize or move the 
menu. If you want to add items or make changes, turn the 
caption on again (see "Saber LAN Workstation: Menu Reference" 
for more information on menu style).
            

Network Messaging
-----------------
To use the network messaging feature in SMENU, replace
the current setting or if none exists, add this
setting under [windows] in WIN.INI:

     Load=SPOPUP.EXE


The Send Network Message function of SMENU displays a list 
of users logged into the network; the list includes users, 
but doesn't include all bindery objects, such as printers 
and servers. The Send Network Message function filters out 
nonuser objects; therefore, the list displayed is different 
from the list you get using Novell's userlist command.


Using the Run option
--------------------

The Run option is now listed on the File menu when
the following SMENU.INI settings are specified:

     PersonalMenus=1 (users can edit personal menus)
     RunOption=1 (Run option is active)

The Run option is still listed on the Control menu when
the following SMENU.INI setting are specified:

     PersonalMenus=0 (users cannot edit menus; therefore,
		     the File menu does not appear)
     RunOption=1 (Run option is active)


Setting Run Options for DOS Applications
----------------------------------------

If you wish to run a DOS Application from Menu for Windows 
in maximized or minimized mode, two conditions must exist:

     -	In your default PIF file for the DOS application, you 
	must use the WINDOWED setting rather than FULL SCREEN.

     -	There must be NO setting for SURFACE= in your menu 
	definition file for the item loading the application.

Use one of the following procedures to set up your DOS 
application to run maximized from within Windows.

USING MENU FOR WINDOWS:

STEP			ACTION
----			------

1.   In Menu for Windows, use one of the following methods:

     - 	Use the Run box to run the PIFEDIT program.  Open your 
	default PIF file and change the Display Usage field 
	to Windowed. (DO NOT use the Full Screen option.) 
	Save your default PIF file.

     or

     -	Proceed to Step 2 to edit the item properties for the 
	DOS application menu item. 

2.   Open the menu file containing the DOS application menu item, 
     and highlight the item you wish to edit.

3.   Choose the Item Properties option from the Edit menu.

4.   Click on the "Advanced" button, and then on the "Assign To" 
     button to display the dialog for setting the Menu Surface.

5.   Make sure Menu Surface is set to "All Menus" in order to 
     include the DOS application on the Windows menu; then 
     click OK.

6.   Set your Run Options as desired to run the DOS application.

7.   Click on OK to complete the process until you have returned 
     to the Menu for Windows desktop.


USING THE MENU SOURCE FILE:
In your menu source file containing the definition for the DOS 
application, follow these steps:

STEP		ACTION
----		------

1.   Include an option in your ITEM statement, as follows:

	ITEM  DOS_application {PIF=WINDOWED}

2.   Make sure there is no SURFACE= option set for the item.  

3.   Set your Run Options as desired for the DOS application.


DOS Environment Variables in Windows
------------------------------------

This section describes how to reference DOS environment 
variables in SMENU and how to use the SETENV utility for 
setting environment variables in the master DOS environment.

REFERENCING DOS ENVIRONMENT VARIABLES:
DOS environment variables may be referenced within many
areas of the Saber Menu System by enclosing the environment
variable within percent symbols (%) as in standard DOS batch
files. For example:
            
     My current COMMAND.COM setting is %COMSPEC%
            
Places where environment variables may be referenced include:
            
     Header file (SABER.HDR)
     Message file (SABER.MSG)
     Item titles
     Menu titles
     Menu control statements (EXEC, GETx, TEXT, LOAD, etc.)
            
Use DOS environment variables to customize menu options and
text based on information unique to individual user environments.
            

SETTING DOS ENVIRONMENT VARIABLES WITHIN WINDOWS:
The SETENV utility for setting DOS environment variables is now 
included on the installation diskettes (SETENV.EXE). See the 
section below, "Setting DOS Environment Variable in Windows" 
for a description of this utility. 

SETENV has two functions:

-  Displays, in Windows, the current settings for environment 
   variables in the master DOS environment 

-  Sets environment variables in the master DOS environment from
   within Windows.

How SETENV Works:
When Windows is started, current DOS environment settings are 
copied to Windows' own environment buffer. Then, when a Windows
application or task is started, it receives a copy of this buffer 
for its own use; when the application is closed, the application's 
copy of the buffer is deleted, leaving the Windows copy. 

However, master DOS environment variables cannot be set normally 
(for example, with the DOS SET command) during a DOS process from 
within Windows. If the SET command is used within Windows, it only 
sets the variable for individual application environments; once 
the window for the application is closed, the setting is lost. Use 
SETENV in place of the SET command to change the master DOS 
environment variable setting. The following procedures 
explain how to display or set the environment variables with SETENV:

Displaying Master DOS Environment Settings:
To display the master DOS environment settings from within Windows
use the Run option from the Windows or SMENU Control menu and enter 
the following:

	SETENV

Setting a DOS Environment Variable with SETENV:
To add an environment variable to the master DOS environment from 
within Windows, use the Run option from the Windows or SMENU Control 
menu and enter the following:

	SETENV keyword=value

where  keyword  is the environment variable keyword, and  value  is the 
value to be assigned to the environment variable.

	Example:
	-------
	In this example, S_MONITOR is set in the master DOS environment 
	from within Windows within the following SETENV command:

		SETENV S_MONITOR=VGA

Note: Since SETENV is a DOS utility, it opens its own DOS window 
to run. If you run SETENV outside Windows, it functions just like 
the DOS SET command.

            
LINK Commands
-------------

Enter the LINK command in all uppercase letters.

If you wish, you can use the {-s} switch to make the link a
search drive for DOS applications only (not available for Windows
applications).  Enter the internal and external link commands in 
all upper case letters except for the -s switch, as shown below.

INTERNAL LINK
You use the internal link command only within the Saber Menus.
This command is the first command executed for the menu 
definition. When using the internal command, you don't need the
LINK DEL commands. You don't need to enter the EXEC command to 
use an internal link.

   Syntax
     LINK [drive]: SERVER\VOLUME:DIRECTORY\SUBDIR {-s}

   Example 
     LINK F: FS2/SYS:PROGRAMS\WP51\%WPFILE% -s


EXTERNAL LINK
You can use the external link command whether or not you're working
within the Saber Menus. This is helpful if you use DOS programs.
The external link command can be executed in any order in the menu
definition by using the EXEC command. The EXEC command must be used
with the external link command. Also, you must use the
LINK DEL command to delete the link.

   Syntax
     EXEC LINK INS [drive]: SERVER\VOLUME:DIRECTORY\SUBDIR {-s}

   Example 
     EXEC LINK INS F: FS2/SYS:PROGRAMS\WP51\%WPFILE% -s



Security - [Ctrl]+[Alt]+[Del] with Screen Blankers
--------------------------------------------------

Windows 3.1 has the keyword LocalReboot= in the SYSTEM.INI
file under the [386enh] section.  This keyword specifies
whether users can press CTRL+ALT+DEL to quit individual
applications without restarting Windows. If the setting is
On, users can quit individual applications. If the setting is
Off, pressing CTRL+ALT+DEL restarts the entire system
(as it usually does). We suggest that you use the Off setting
for this keyword to prevent users from being able to terminate
Screen Blankers with the key combination CTRL+ALT+DEL.            


Additional Features
-------------------

     - These two Windows 3.1 compatible screen blankers are 
       provided in the product and are installed automatically 
       in the Windows directory during SMENU installation: Company
       News (CNEWS.SCR) and Screen Saber (SSABER.SCR).  Company
       News presents company information by reading and displaying
       bitmap files from the specified directory.  Screen Saber is
       a Saber logo which you can set up to move across the screen.
            
     - SMENU emulates standard Program Manager DDE commands for
       creating new menus and items.  Most applications which use
       a Windows based install program that automatically creates
       an application group are compatible with Saber's Program
       Manager emulation.  However, this emulation may not be
       compatible with installation programs which require
       Program Manager as the shell exclusively (such as by
       checking the shell= statement in the SYSTEM.INI file).
            
     - In the status bar for Application and Desktop system 
       styles, the network user name from a Novell, Banyan or 
       LAN Manager network is now displayed in the "user ID" area.

     - The Menu for Windows Advanced Properties dialog allows you
        to select menu foreground and background colors; you don't
        have to remember the numeric value associated with the color.

     -  Items can now be arranged on the menu using the mouse or keyboard.
        Follow the procedure below to use the keyboard. See
         "Saber Menu Reference," Part 3: Menu for Windows User's Guide
         for the procedure for using the mouse.

	Step	Action
	1.	Select Edit/Arrange to display the Arrange Menu dialog.
		This dialog displays a text list of the items contained on
		the menu.

	2.	Use the up or down arrow keys to select the item.
		Hold down [Shift] and press the up or down arrow keys to
		move the selected item.

	3.	Do one of the following: 

		- To save your changes and close the dialog, press [Enter].
		or
		- To move the item again, repeat steps 2 and 3 until the item
		   list is in the order you want. 


Known Program Anomalies
-----------------------

     - If file reading problems occur during installation
       with DOS File Sharing Support (SHARE.EXE) loaded,
       try installing without DOS Share loaded.
            
     - When using AfterDark or other third-party screen blankers
       with SMENU, disable the UseNovellPassword SMENU.INI
       setting.  The UseNovellPassword setting only works with
       Windows 3.1 standard screen blankers.
            
       UseNovellPassword=No
             
     - If problems occur when using the PIF= item option, make 
       sure you've specified the full path for the default PIF 
       file in SMENU.INI in order for the file to be located by 
       Saber Menu for Windows.  Also, use the _default.pif file 
       copied during installation for running DOS applications, 
       or create a _default.pif file using the PIF Editor 
       (PIFEDIT.EXE).

       DefaultPIF=c:\windows\_default.pif
            
     - If you receive the message "Bad command or file name" when
       executing a DOS menu command, be sure that the directory
       where Saber Menu for Windows is installed is on the path.


Corrections to Reported Problems
--------------------------------

     -	Icons for DOS applications are now loaded properly from 
	the STARTUP.DAT menu.

     -	You can no longer use a function key combination (such as 
	[Alt]+[F4]) to bypass the password requirement for the 
	screen blanker.

     -	Function keys and control menus have been modified to adhere 
	to Windows/MDI standards in Desktop as well as Application 
	system styles. As a result, the [Ctrl]+[F4] and [Ctrl]+[F6]
	key combinations are no longer available for desk accessory 
	key assignment in SMENU (you can still assign them in Saber 
	Menu for DOS if you have this Saber component; however,
	these keys are not available for desk accessory assignment 
	in SMENU). For more information on the new functions, see 
	"About Function Keys and Control Menus," which follows.

     -	Menu items for DOS applications can be properly executed in 
	all menu styles.

     -	DOS applications defined in SABER.RUN can be executed 
	properly from the Menu for Windows Run box.

     -	If you disable the RunOption= and ShutDown= keywords in the 
	SMENU.INI file (i.e., set to a value of 0), the options are 
	omitted from the Control menu in the Object system style.  
	If you disable the Close= keyword, the option is "grayed" 
	(appears but is unavailable) in the Object system style.

     -	Other Windows applications can be properly installed when 
	SMENU is designated as the shell.

     -	The LINK command works properly when using DOS environment
	variables.

     -	Only screen blanker files (.SCR) are accepted in the Screen
	Blanker field on the Preferences dialog. If  an executable or
	.COM file name is entered in the field, an error message is
	displayed.

     -	Users cannot close the network menu (NET0). Therefore, a menu
	is always available on the desktop.

     -	Menus in SMENU can now be deleted when they're minimized.

     -	Using Icon Palette style, you now double click on items to start them.



About Function Keys and Control Menus
-------------------------------------

If you are using the Desktop system style, the following keys and 
menus have been redefined to adhere to MDI standards:

FUNCTION KEYS
The following function key combinations are available:
			
     [Alt]+[F4]		Previously, the [Alt]+[F4] key combination 
			closed the focused menu in Desktop system 
			style. This key combination is no longer 
			available for closing menus in Desktop or 
			Application system style; instead, use
			[Ctrl]+[F4] (see description below). The 
			[Alt]+[F4] key combination is available for 
			Object system style.

     [Ctrl]+[F4]	Closes the current menu for any menu 
			style when SMENU is in the Desktop or 
			Application system style; shifts focus to 
			the next opened menu (whether it is 
			currently open or minimized). Note: if the 
			menu style is Icon Palette without caption, 
			the menu is focused, but there is no visual 
			clue (for example, no highlighted border).

     [Crtl]+[Tab]	Changes the focus from the current menu to 
     [Ctrl]+[F6]	the next opened menu for any menu style 
			(whether it is currently open or minimized). 
			Note: if the menu style is Icon Palette 
			without caption, the menu is focused, but 
			there is no visual clue (for example, no 
			highlighted border). 

     [Alt]+[Spacebar]	Activates the Control menu for the main 
			SMENU window.

     [Alt]+[-]		Activates the Control menu for the active 
			menu.

Note:  	[Ctrl]+[F4] and [Ctrl]+[F6] key combinations are not 
	available for desk accessory key assignment in SMENU. For 
	more information on desk accessory keys, see the "Saber Menu 
	System for Windows: User's Guide."

CONTROL MENUS
The control menus for all menu styles except Icon Palette without 
caption now adhere to Windows/MDI standards. The menu options 
comprise: Restore, Move, Size, Minimize, Maximize, Close, and 
Next Window. The option Switch To is available only from the main 
SMENU control menu.


Documentation Errata
--------------------

Listed below are additions and corrections to the documentation
on Saber Menus you received with the product.

Online Help

    - Enter the LINK command in all uppercase letters.
            
"Saber Menu Reference," Part 1: Menu for DOS User's Guide

    - If you use group name the user file (SABER.USR) enter it
       like this: [GROUP].
            
 "Saber Menu Reference," Part 3: Menu for Windows User's Guide

    - Files marked as Read Only are also considered shared menus.
            
    - The directory where the LAN Workstation executable files
      are installed should be on the path or added to the path
      (default is \SABERWKS).
            
    - Changes made to SMENU.INI (using SMENUINI.EXE) take affect
      the next time the menu program is started.
            
    - The Object system style requires a mouse.

    -  When you select Shutdown from the Control menu to restart (reboot)
       the workstation, you receive a prompt to continue or
       cancel the request to reboot. If you choose yes to continue and
       there are no open files which need to be saved, the workstation
       is rebooted. If files need to be saved, you receive an additional
       prompt to save changes. If you choose to save (Yes), all open files
       are saved and the workstation is rebooted. If you choose No, open
       files are NOT saved and the workstation is rebooted. If you choose
       Cancel, the request to reboot the workstation is canceled.

       Note that the Reboot dialog (Figure 3-6) is no longer displayed.

    - The Run option is now found on the File menu.
            
    - The send network message menu option is only available for
      Novell networks.
            
    - For a list of available menu colors, please see 
      Part 1: Language Reference.
            
    - To remove a menu password after one has been set, press the
      OK button without entering any text.
            
    - The Arrange Menu requires a mouse for operation.  To move
      a menu item:
        - Select the item
        - Move the arrow pointer within the Items list until
          it changes to an insertion pointer
        - Click the left mouse button.
            
    - Desk accessory key combinations which use [Alt] cannot be 
      accessed using the keyboard; you can access them only with
      the mouse using the Desk Accessory Reference box.  [Alt] key
      combinations are provided for compatibility with Saber Menu
      for DOS only.  For a more complete discussion of desk 
      accessory keys, see the section above.
            
    - The DA/Key file referenced in Appendix D is not included.
      Use the discussion of desk accessory keys above and the
      sample SABER.KEY file provided on disk for more information.
            
    - The Help file referenced in Appendix D is not included.
      Use the discussion of custom menu help above and the sample
      WIN1.HLP file provided on disk for more information.
            
    - The search option for Link Network drive is available only for
      DOS applications; it is not available for Windows applications.
            
    - The Station Information dialog has been changed to provide
      additional information.
            
    - For sample WIN.DEF and SYSTEM.DEF files, please refer to the
      sample files copied during installation.
            
    - The Network= option is not used. Network type detection is now
      performed automatically by the menu program.
            
    - Additional files copied during installation:
        - SABERSRC.HLP Online help for the menu language
        - CNEWS.SCR    Company News Screen Blanker (copied to
                       Windows directory)
        - SSABER.SCR   Screen Saber Blanker (copied to Windows
                       directory)
            
"Saber Menu Reference," Part 1: Language Reference
            
    - If the folder or icon name contains spaces, the icon reference 
      must be surrounded by quotes.  For example:

	 ICON="SAPPS.SIL,Word processing,Microsoft Word" 

    - SMENU uses _DEFAULT.PIF file to run a DOS application if
      you do not enter PIF= settings for the application in the menu
      source file. SMENU searches for the _DEFAULT.PIF file
      in this order:
 
      1) path specified in the SMENU.INI file
      2) directory specified in the S_FILEDIR environment variable
      3) current directory
      4) path.

    - Here are two additional messages displayed by the CREATDAT
      compiler:

	038 Item title cannot be blank
		Error: You have entered the ITEM command without
		an item name. The correct syntax is: ITEM itemname.

	039 Statement cannot be longer than 255 characters
		Error: The line identified has more than the maximum
		number of characters. Each statement including continuation
		lines, can have a maximum of 255 characters.

    - The length of the GETL statement cannot exceed 255 characters.
            
    - The example given for GETD works only with Saber Menu System
      for DOS.
            
    - CREATDAT can create an encrypted file that further secures 
      network information.  When encrypted, the .DAT file becomes 
      unreadable even with programs such as Debug.  Whether a .DAT 
      file is encrypted has no effect on the menu program or CREATSRC.
      If an encrypted file is changed and then saved within the
      menu program it is written in encrypted format.

      To indicate that you wish to encrypt a menu file, do one of the 
      following:

      In SMENU:

	1.	Choose System/Run.

		Response: The Saber Menu System Compiler dialog is 
		displayed; it includes a checkbox for indicating whether 
		you wish to encrypt the menu file. The default is off.

	2.	Click on the Encrypt check box.

	3.	Proceed to Step 2 on page 86.


     At the DOS command line:
	
	The syntax for the menu compiler command which includes the 
	encryption option is as follows:

		CREATDAT srcfile -E

	Where srcfile is the name of the source file (.SRC) you wish to 
	compile, and -E is the encryption option switch.


____________
.INI MANAGER

The .INI Manager now supports 80486 processors.

For LANMAN 2.x users, you can now use the DOS environment
variable, S_GROUPS in your .DEF files.


_______________________________
SABER PRINT MANAGER FOR WINDOWS

Print Manager for Windows is designed for use with
Novell networks only.

The following is a correction to a reported problem:
     -	The print queue features now work correctly.
	You can insert, move, copy hold, release
	and delete jobs in a print queue.


________________________
SABER CONSOLE AND AGENTS
                              
This section covers the following topics:

     - Note to previous Console and Agent users
     - Refresh feature enhancement
     - Server Agent
     - Security
     - Note for Banyan users about security
     - Metering applications
     - WMONITOR command options
     - Command line options for the SMETER scan
     - Specifying which applications to monitor
     - Exporting data to database format
     - Corrections to reported problems 
     - Known Program Anomalies
     - Documentation errata


Note to previous Console and Agent users
----------------------------------------
DO NOT delete the WKS.DSD dataset created during installation.
It is stored under the subdirectory \DATASET in the installation 
directory (default installation directory is SABERWKS). If this 
dataset is deleted, the new Agent Handlers provided with the new 
product release may not be located by the Console, as well as the 
files required to run the Console. The Console searches for files 
in this order:

	1) current directory
	2) path
	3) full path specified for the dataset 
	4) agent directory (default=\SABERWKS\ADMIN).

If you want to work with the datasets you created using a previous
release of the Console and Agents, just add the datasets to the
Console. See the "Installation Supplement" and the book "Saber 
LAN Workstation: Administrator Utilities" for instructions
on adding a dataset.


Refresh Feature Enhancement
---------------------------
The Console offers the option to continuously update displayed data 
through the refresh feature. To turn refresh On or Off, 
choose Options/Refresh from the Console menu.

Please be aware that when you choose to turn refresh Off, any 
displayed views are NOT updated until you turn the option on again. 
New views are empty when they are displayed. In addition, the 
option to reset an agent handler is turned off when refresh 
is Off (see "Saber LAN Workstation: Administrator Utilities" 
for instructions on resetting an agent handler").


Server Agent
------------
The Server Agent is available for use only with Novell NetWare 3.x.
                       
If you enable the Continuous Scan options for disk information and 
trustee assignments, operations performed at the Console can take 
a significant amount of time to complete. This condition is due to 
the amount of time required to retrieve information from the 
Novell network. Therefore, we recommend leaving the Continuous 
Scan options off until you finish working with other programs and 
utilities and can leave only the Console running. You set the 
Continuous Scan options in the SCONSOLE.INI file which was copied 
into your Windows directory during installation.
                       
Security
--------
During installation, all files reserved for use by the LAN
administrator were stored under \SABERWKS\ADMIN. We suggest
you make this directory nonpublic to secure the executable
and related administrator files.


Note for Banyan Users about Security
------------------------------------
When you use WMONITOR.EXE, you must set the S_STATION 
variable because Saber doesn't detect stations identifiers
on Banyan networks.


Metering Applications
---------------------
You can use the ADMIN.DAT file to launch programs for all network
users of a particular version of Windows.  Most important, if you
want to meter applications for all users, you should define the
WMONITOR program in ADMIN.DAT. This method eliminates the need to
define metering for each workstation.

If you chose to activate metering during installation, ADMIN.DAT
was created and the WMONITOR program was defined automatically.
SMENU launches the programs defined in ADMIN.DAT when users
start the system.

To activate the metering function at a time other than at
installation, create a file called ADMIN.DAT and define the 
WMONITOR program as a menu item.  Then store the file in the
Windows system subdirectory (\SYSTEM). For DOS applications,
remove the REM command from the menu definitions in MAINMENU.DAT.

     EXAMPLE
       EXEC REM SMETER -LOGIN -T:WP -D:Z:\SABERWKS\dataset\WKS.DSD
       EXEC REM IF ERRORLEVEL == 1 GOTO exit
       CD X:\PROGRAMS\WP.51
       WP
       EXEC REM SMETER -LOGOUT -T:WP -D:Z:\SABERWKS\dataset\WKS.DSD
       :exit

     Note: 'dataset' is the name of the directory where you want 
     metering information stored.


WMONITOR Command Options
------------------------
There are two command line options for WMONITOR.

     -	Specify the -IGNORELOCAL option to ignore local 
	files when running WMONITOR in secure mode.  If this 
	option is not specified, an error occurs when users 
	attempt to run local files which are not in the file 
	database.

     -	Saber Menu for Windows (SMENU) creates temporary batch
	files to execute DOS applications.  If you run SMENU and
	run WMONITOR in secure mode, these batch files do not run
	since they are not included in the file inventory. Add the
	-IGNORETEMP option to the command line to run SMENU
	temporary batch files whether or not WMONITOR is running
	in secure mode.


Command Line options for the SMETER SCAN
----------------------------------------
Two options are available for running SMETER with the -SCAN option:

     -	You can add a list of applications found in the scan to 
	the software inventory for the Application agent. To do 
	so, specify a dataset name on the SMETER command line. 

     -	When a program file (.COM, .EXE, .BAT) not defined in the 
	SMETER template database is executed, an event is logged. 
	This type of event is referred to as level 5, and is 
	labeled "UndefinedFile." If users frequently execute files 
	which are not included the file database, the scan 
	operation performed by SMETER can be slowed significantly 
	due to the number of events written to the log. To turn 
	off logging for these files, add the -NOSCANEVENT option 
	to the SMETER command line.


Specifying which Applications to Monitor
----------------------------------------
With WMONITOR.EXE as an item on a Saber menu, you can specify
criteria for which applications are metered.  You can specify item 
properties to meter applications for certain users, groups, 
stations, hardware and networks.

You must be consistent in how you specify which application files
to meter. Specifically, you can use one of two methods for identifying
which files to meter: (1) by specifying drives mapped to a certain
volume or (2) by specifying map rooted drives. Applications are
NOT metered correctly if you use these methods interchangeably.

See Part 2, Agents Reference in "Saber LAN Workstation: Administrator
Utilities" for more information on WMONITOR.


Exporting data to database format
---------------------------------

The Console offers the option to export data to dBASE file format.
However, in some database products (for example, dBASE4) an error occurs
when you try to open the exported file. This error is caused when a field
in the data you export has multiple lines, such as the AUTOEXEC.BAT
or CONFIG.SYS fields in reports created using the Hardware agent handler.
Other products, such as Microsoft FoxBase, do not have this limitation.


Known Program Anomaly
---------------------
If you are a Novell user, specify the -f switch (what file is to be 
created and where to store it) last in the SFILETSR command.

            
Corrections to Reported Problems
--------------------------------

     -	Console and Agents are installed properly on NetWare 2.15 
	when the SERVERH.DLL is added.

     -	Information displays faster at the Console, including for
	large datasets. After information displays the first time,
	you can continue working with other applications. Data is
	still refreshed in the background, if you select
	Option/Refresh.

     -	The Event, Application and Hardware agents now handle
	larger groups on NetWare.

     -	Addition of the Server agent no longer causes a General 
	Protection Fault (GPF) error on Netware 2.15.

     -	The Disk agent (SDISKMON.EXE) now reads dataset names, drives, 
	and volume information properly from LAA.INI.

     -	The Printer agent no longer causes a GPF when the plotter driver
	(HPPLOT.DRV) is selected.

     -	Multiple charts can be opened concurrently using the Application
	agent.

     -	An application scan can be properly run with READ and EXECUTE
	rights; WRITE access is not required.

     -	For chart view, plotter fonts are displayed correctly when text
	is rotated.




Documentation ERRATA
--------------------
Here are corrections to the documentation on the Saber Console
and Agents you received with the product.
            
"Saber LAN Workstation: Administrator Utilities" page 47
    - Unless you specify otherwise, Console and Agent files
      are copied into the following subdirectories:

	\SABERWKS\ADMIN		subdirectory for files only the 
				LAN administrator should have 
				access to; these include: 
				SCONSOLE.EXE (the executable for 
				the Saber Console),and Agent 
				Handler .DLL files.

				Since only the administrator should 
				have access to View and Text files 
				created and displayed by the Console, 
				store these files in the \ADMIN 
				subdirectory. If you wish, you could 
				create a subdirectory under \ADMIN 
				in which to store these files.
					
	\SABERWKS\DATASET 	subdirectory where Console dataset 
				files (WKS*.DSD) are created. We 
				recommend you also store the dataset 
				files you create in this subdirectory 
				to make the information available to 
				all users.

	\SABERWKS\USER 		subdirectory for other files such 
				as the WPMONITOR program used to 
				meter applications:

				ADMIN.DAT -- the menu file where
				WMONITOR is defined for software 
				metering.

				Note: the installation program only 
				creates this file if you choose to 
				activate metering (see the 
				"Installation Supplement" included 
				with the product).
					 
				WBTRCALL.DLL -- Btrieve Dynamic Link
				Library.

"Saber Utilities: Administrator," Part 2: Agent Reference
	"Using the (hardware) Station Dialog" Section--duplicate
	parts are not allowed for workstations with the status
	"Spare."


