			Saber LAN Workstation 1.0d
			Release Notes - July 1993
				(continued)

_________________
MENU FOR DOS 4.1a

This section covers the following topics:

     - Memory Requirements
     - Note to previous Menu for DOS users
     - Reviewing Novell system login options (for Novell users)
     - Setting up the SABER.SRV file
     - Session Startup Processor requirement
     - Login preprocessors
     - SABER.USR file
     - LINK menu command requirement
     - Multiple line messages in SMESSAGE utility
     - Program enhancements and corrections to reported problems
     - Errata 


Memory Requirements
-------------------

To run Menu for DOS successfully, you should have at least
495K of free memory. The memory requirement to run the system
has increased due to additional network libraries. However,
you can still use the -S switch to reduce the memory requirement
by up to 100K. You can use the following commands to reduce the
memory requirement.

	MENU menufile -Sn
	SABER menufile -Sn

where: menufile is the name of the file containing the menus
and 'n' is a number that is 1K larger than your largest
menu definition file.

See page 207 in the Saber LAN Workstation "Menu Reference"
for a list of settings.

Note to Previous Menu for DOS Users
-----------------------------------

NAVIGATING MENUS
You can still use the UP and DOWN arrows to advance to the next
item or return to the previous item. However, there are two changes
in how the cursor moves on the menu:

    -  If the first item is highlighted, the UP arrow does not move
       the cursor to the last item. Use the END key to move to the
       last item.

    -  If the last item is highlighted, the DOWN arrow does not move
       the cursor to the first item. Use the HOME key to move to
       the first item.


MENU CONVERSION FOR NOVELL USERS
Previously, a menu source file (.SRC) was created when you
converted Novell menus to Saber format. Now when you
convert, a menu data file (.DAT) is created. If you want to
edit this file, you can run the menu decompiler utility
(CREATSCR.EXE) after you perform the conversion.

Use the following command to convert your Novell menus
to Saber menus.

	NVL2SABR.EXE menufile

where, menufile is the name of the Novell menu file you want
to convert.

When you convert, a new file is created and stored in the current
directory. It has the same name as the Novell menu file, except
with the .DAT file extension.


During installation, the Saber utility for converting Novell
menus (NVL2SABR.EXE) and the utility you use to decompile
Saber menus (CREATSCR.EXE) are stored in the directory
\SABERWKS\USER, or the installation directory you specify.


SCREEN BLANKER FOR NOVELL USERS
By default, the menu screen is blanked after a period of inactivity 
and users are required to enter the Novell password to continue 
processing.  To bypass use of the Novell password and allow the user 
to press any key to continue processing, use one of the following 
syntax examples to add the -N switch to your SABER.SRV file:

	*default,servername,menu -n
	*userid,servername,saber -n


Reviewing Novell System Login Options
-------------------------------------
One of the configuration tasks you should perform after using the 
Saber LAN Workstation installation program is to review the Novell 
system login options, as follows:

1.    IN SYSCON, under Supervisor Options, is the option Default 
      Account Balance/Restrictions. If you plan to limit the number
      of grace logins for a user ID, the number of grace logins must 
      be set to an even number. Multiply the number of Grace Logins 
      by two to ensure you are using an even number.  For example, 
      if you want two Grace Logins, set the option to four; if you 
      want three, set it to six.

2.    Also under Supervisor Options is the option for system login 
      script. If the user starts his or her session with NLOGIN, the 
      last line in this system login script MUST be EXIT in all caps. 
      Note: exiting to a batch file within the script will result in
      errors. 

3.    Add S_FILEDIR and S_FILE environment variable definitions to the 
      system login script. 

4.    Do not "MAP ROOT" the login directory; you'll get a "Batch file 
      missing" error if you do; you may perform normal mapping for the 
      login directory.

      Note: If you wish to require the user to log on to the network,
      you can add the NLOGIN command to each workstation's AUTOEXEC.BAT
      file; it must be the last item in the batch file. (For more 
      details, see "Getting Started.")


Setting Up the SABER.SRV File
-----------------------------
Be sure the SABER.SRV file is located in the system login directory 
of each server listed in SABER.SRV.  Here are three variations for 
defining servers in the SABER.SRV file:

One Server:    

     *default,fileservername,batchfilename

Two Servers:   

     *default,fileservername1,batchfilename
     $fileservername2,batchfilename

Three Servers (using the NLOGIN switches -s and -h):

     *default, fileservername1,batchfilename
     $fileservername2,batchfilename
     $fileservername3.batchfilename

To specify a different condition for a particular user,
enter the following: 

     *username,fileserver1,batchfilename

You can identify the user through the Novell bindery or by 
setting the S_USER DOS environment variable.  Groups are not
supported in SABER.SRV.


Session Startup Processor Requirement
-------------------------------------

If you wish to use the Session Startup Processor as part
of the Menu for DOS startup, you must use either LOADMENU.BAT
or SABER.BAT for startup.  MENU.BAT does not call the files 
necessary for using the Session Startup processor.  For more 
information on the Session Startup Processor, see 
"Saber Menu Reference," Part 2: Menu for DOS User's Guide. 


Login Preprocessors
-------------------

NEW NLOGIN HIGHLIGHT SWITCH
NLOGIN now has a switch, -h, designed to be used in conjunction 
with the -s switch (-s prompts the user for a server name by 
displaying a scrolling list of available servers).  The -h 
switch will place the highlight bar on the default server name 
for that particular user ID. Default server name is determined 
from the SABER.SRV file.

When using NLOGIN, if you plan to limit the number of grace logins 
for a user ID, the number of grace logins must be set to an 
even number.

NEW SLOGIN AVAILABILITY
You can use the SLOGIN processor on LAN Manager 2.x networks.


SABER.USR File
--------------
There is no default user in the SABER.USR file (i.e. *default 
will be ignored unless the user name is actually DEFAULT).

If you use group name the file SABER.USR, enter it
like this: [GROUP].


LINK Menu Command Requirement
-----------------------------
When using the menu command, LINK, you must specify the BATCH option 
on the item line.

If you wish, you can use the {-s} switch to make the link a search 
drive.  Enter the command in all upper case letters except for the 
-s switch. For example, for Novell networks you'd enter the internal 
LINK command as shown below.

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

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

The example above illustrates that you can use DOS environment
variables within the internal LINK command. 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.


Multiple Line Messages in SMESSAGE Utility
-------------------------------------------

The SMESSAGE utility, which allows you to display a brief message, 
has two undocumented functions:

     - Multiple lines of text 
     - Timed display of message (no user response required)

The format and syntax for the command is:

     SMESSAGE "message line 1" "message line 2" ...  [-t#]

where each line of text is enclosed in double quotation marks and 
-t is followed by the number of seconds to display the message. 
If the -t switch is used, it must be the last argument on the 
command line. 

For more information about SMESSAGE, see "Saber Utilities: Workstation,"
Part 5: Other Utilities.


Program Enhancements and Corrections to Reported Problems
---------------------------------------------------------

     -	Menu for DOS is compatible with DaVinci and Castelle TSRs and 
	the Fox Pro LX program.

     -	Both Saber Menus (Menu for DOS and Menu for Windows) menu and 
	item command options are compatible.
  
     -	HERC and MONO keywords can be used as the value for the HARDWARE= 
	item option.

     -	SVGA monitors can be specified in the HARDWARE= variable using the
	value VGA (HARDWARE=VGA).

     -	DOS environments variables can be used to specify a menu of item name.

     -	Menu titles are now centered correctly above the item list.

     -	The Compiler (CREATDAT.EXE) processes menu source files (.SRC)
	when the parent or current directory name has an extension.

     -	The GETD local command in Menu for DOS lists only drive A when 
	drive B does not exist.

     -	Menu for DOS temporary files are NOT deleted when File Manager 
	is executed.

     -	Use of the GETF and GETFP command does NOT cause PC lockup.

     -	Negative Saber Simplified numbers are now recognized.

     -	The message line located at the bottom of the desktop displays up
	to 80 characters.


	
Documentation Errata
--------------------
"Saber Menu Reference," Part 2: Menu for DOS User's Guide:

     -  In the file SABER.KEY, the format for assigning a "hot key" for 
        desk accessory keys is incorrect; use the following:

         [hotkey]    

        where "hotkey" is the optional Alt, Shift or Ctrl key to be
        used in combination with the function key.  For example,
        to specify the Shift key is to be used, enclose it in square
        brackets once at the beginning of the assignments for all
        combinations which use it, as follows:

         [Shift]


_________________________________
PRINT MANAGER FOR DOS VERSION 2.0

Print Manager for DOS is designed for use with Novell networks only. 
This section covers the following topics:

     - Creating PRTMGR.DAT, the menu of printer commands
     - Errata
     - Known program anomaly

Creating PRTMGR.DAT
-------------------
The full version of the Print Manager 2.0 (PRTMGR.EXE) requires that 
you create the PRTMGR.DAT menu definition file. This file defines 
the print devices and modes contained in the Novell NET$PRN.DAT, and 
is used to display the menu of options for the main menu option 
Send Printer Commands. PRTMGR.DAT may be located anywhere in the 
search path. 

The new PRTMGR.DAT format is as follows:

    *Printer Name
    Mode 1
    ^mode string
    Mode 2
    ^mode string

Here is an example of entries in a PRTMGR.DAT file. 

    *Hewlett Packard Laser Jet I/II
    Condensed
    ^\27E\27&sOC\27&l10\27(s16.66H\27(&15.4C
    (Re-initialize)
    ^\27E
    Lotus 123 Spread Sheet
    ^\27E\27%$3g\27(s4T\27(s0P

The above "Condensed Mode" example has the string for the following:

     - Reset
     - End-of-Line Wrap - Enable
     - Orientation - Landscape
     - Pitch - 16.66
     - Vertical Motion Index - 5.4

All information in PRTMGR.DAT must begin at the left margin and 
end with a return. An asterisk (*) is used to define print devices. 
Lines without an asterisk are assumed to be print modes.  Blank lines
are ignored.  

Be sure the case and spacing in the file are the same as those in the 
PRINTDEF file. For more information on PRINTDEF, see the chapter on 
Print Manager Operation in "Saber LAN Workstation Utilities: 
Workstation."

Errata
------
"Saber Utilities: Workstation," Part 3: Print Manager Operation:

Under the main menu option Display Print Queue, you may perform 
various operations on items in the queue.  Use of the [Insert] and 
[Del] keys is explained; however, the following options are not 
described in the documentation:

[H]old:        Places a queued item on hold.  Highlight the item 
               and press [H] to put the item on hold until you 
               release it.

[R]elease:     Releases a queued item with Held status.  Highlight 
               the item and press [R] to release it.

[M]ove:        Moves the highlighted queued item to another queue. 
               A list of queues is displayed; highlight the queue 
               you wish to move the item to and press [Enter].

[C]opy:        Allows you to copy a queued item to a file you specify. 
               Enter the full path for the file and press [Enter].  
               Note: any printer setup commands for the print job are 
               copied into the file.

Known Program Anomaly
----------------------
Under the following conditions you may experience unexpected 
results in the Print Queue Display:

     - After inserting a job into an empty queue
     - After deleting the last job in a queue.

__________
SECURE 4.0

The documentation you received with the product for Secure
has been replaced by documentation in the following files:

      - SECURE1.TXT
      - SECURE2.TXT
      - SECURE3.TXT

This section covers changes to the Secure product and includes the following topics:

     - Notes for existing customers
     - New Features


Notes for Existing Customers
----------------------------

This section contains information about changes made 
from the previous version of Secure. The main changes 
are:
     -	A single executable program for all Secure 
	users
     - 	Modifications to command line switches
     - 	New command line switches.

These changes are described in detail below.

SINGLE PROGRAM FOR ALL SECURE USERS
The new release of Secure does not require use of a 
special executable program (formerly SECUREP) for 
Novell passwords.  


MODIFICATIONS TO COMMAND LINE SWITCHES
Some command line switches have been modified for this 
release. The following paragraphs describe the changes; 
however, for a complete description of how to use the 
switch, see "Securing Workstations," which follows 
these notes to existing customers. 

-Z	This compatibility switch is no longer needed. 
	Secure now provides LAN Manager compatibility 
	without the switch. 

	ACTION: Remove the -Z switch from your Secure 
	command statements.

-G	This graphics switch is no longer needed for 
	using Secure with products that have a 
	graphical interface.

	ACTION: Remove the -G switch from your Secure 
	command statements.

-P	This switch, which previously allowed you to 
	prevent processing while the workstation was 
	blanked or secured, is no longer available. The 
	new default for Secure is to prevent processing 
	while the screen is blanked unless you use the 
	new -C switch (described below). 

	ACTION: If you currently use the -P switch, you 
	need to remove this coding and add the new -C 
	switch where applicable. 

-D	In the previous version, this switch allowed 
	you to disable all local drives while Secure 
	was loaded; the drives were enabled whenever 
	Secure was unloaded. With this release, you can 
	disable all or selected local drives with this 
	switch; however, the drives will remain 
	disabled even after unloading Secure. 
	
	ACTION:  If you use this switch to disable all 
	local drives, remove these drives from the 
	search path.

	NOTE:	If you have local and network drives on 
		the search path, Secure only disables 
		local drives; no network drives are 
		disabled.

-O	This switch prevents logout and reboot if files 
	are open. However, with this release, logout 
	and reboot will occur if a file was open when 
	Secure was loaded.


New Features for Secure
-----------------------

NEW COMMAND LINE SWITCHES
The following switches are intended for use by the 
network administrator, and are described in detail 
under "Securing Workstations," which follows. 

-C	Allows the program or application which is 
	running when the screen is blanked to continue 
	processing. If you do not use this switch, the
	current processing is interrupted whenever the 
	screen is blanked.

-I	Provides a screen requiring the user to define 
	an initial password and optional message at the 
	time Secure is loaded as a memory resident 
	utility. The password is then required whenever 
	the screen is blanked. For Novell networks, 
	this switch is available in combination with 
	the -N switch, which bypasses use of the Novell 
	password.

-K	Unloads Secure as a memory-resident program 
	(same as -U switch).

-S	Provides a method for specifying the type of 
	memory swapping to use for Secure when loaded 
	as a memory-resident utility.

-F	Allows you to specify a file to use for 
	swapping memory.
	
-E	Allows you to specify a time-out (in seconds) 
	for displaying the password screen. In most 
	cases, after the time specified has elapsed 
	with no keyboard activity, the screen is 
	blanked; if Secure is being used as a DOS 
	application, inactivity at the password 
	definition screen will cause Secure to be 
	unloaded after the specified time. The effect 
	is the same if the user presses [Esc] at the 
	password screen.


A NOTE ABOUT GRAPHICS APPLICATIONS
In order for Secure to work with graphics applications, 
you should not use these two new switches:

-SO	Normally disables memory swapping; however, 
	some form of memory swapping is required for 
	using Secure in conjunction with graphics 
	applications. 

-C	Normally allows you to continue processing 
	while the screen is blanked. However, in order 
	to allow an application to continue processing, 
	Secure retains control of the screen, and this 
	doesn't work if the applications are not in the 
	same video mode.


SCREEN DISPLAY FLEXIBILITY
Secure now works with a 25-, 43- or 50-line screen 
display, and you can switch between display modes while 
Secure is loaded.


__________________________
SABER REPORT GENERATOR 1.0

You can use the Report Generator (SABER_R.EXE) to run reports
on .DAT files to get information such as, when the file
was created and a summary of the menus defined in it.

____________
SABER EDITOR

You can compile Saber menu source files (.SRC) using the [F10]
funtion key. However, an error occurs if you select the
Compile option from the Options menu.

___________________________
NOTES FOR NETWARE 4.0 USERS

Saber products are currently not compatible with NetWare 4.0.
At the time of this release, the final version of some Novell
NetWare 4.0 files were not available. Therefore,
unexpected results were experienced during testing
of some functions since Saber files work
together with files provided by Novell (for example,
.DLL files and APIs).

Saber developers are currently working on NetWare 4.0
compatibility issues. And compatibility with NetWare 4.0
will be available in a future release.


_______________________
SABER TECHNICAL SUPPORT

If you have questions on how to use the product or need any other
assistance, please contact Saber Technical Support at the
phone numbers listed in the front of the manuals you
received with the product.  Technical support is available 9
a.m.-5 p.m. CST.  If you prefer, you may also contact
technical support through our multiline BBS system at
214/361-1883.  The BBS is set up with US Robotics 9600 baud
modems and is capable of v.42 support.  Terminal support is
ANSI at 8/n/1.  The BBS operates 24 hours each day.

