FACSys Version 3.40

Additional Information To Assist With Your Implementation Of FACSys. Please
Read Before Running FACSys In The Event Any Of The Following Pertain To You.
Some items address installation, use of the DOS TSR under Windows for those
who run DOS applications under Windows, modifications, and new utilities:

1.	If you have already installed FACSys on your network and then decide to
	use a different fax device, you have to reinstall FACSys from floppy.
	Based on the board, the install.exe copies different files onto your
	network. This applies to the different Intel SatisFAXtion boards too.
2.	If you run into any problems, the first step you should take is to have
	a clean CONFIG.SYS and AUTOEXEC.BAT at the fax server. Your CONFIG.SYS
	should have
	FILES = 40
	BUFFERS=40
	and your AUTOEXEC.BAT should have only your network drivers. If you are
	using HIMEM.SYS, QEMM, SMARTDRV, etc. They should all be removed for
	testing purposes.
3.	Your Novell network shells should be the latest. IPX should be ver 3.10
	or greater and your NETX.COM should be 3.26 or greater.
4.	The INSTALL.EXE creates a print queue on the network called PRINTQ_FAX.
	This should not be removed. NO PRINT SERVERS OTHER THEN THE FAX SERVER
	CAN BE ATTACHED TO THIS QUEUE.
	For auto-printing, you MUST NOT use this queue. This queue is for out-
	going faxes only. If you have deleted this queue by accident,
	you should reinstall FACSys from floppy and let the INSTALL recreate
	it for you.
        Or you can make the queue manually in PCONSOLE, then run QRIGHTS.EXE on
        that queue (QRIGHTS is found in the FACSys directory).
5.	The INSTALL.EXE creates two Novell Netware groups, FAX_ADMIN and 
	FAX_ROUTER. Make sure these groups are not deleted. The user name which
	will be user logged in at the fax server has to belong to the group
	FAX_ADMIN. All users that you add to this group will have access to the
	supervisor options under the user interfaces.
6.	Some Expanded memory drivers may not be compatible with FACSys. If you
	get "PCL Memory initialization errors", please disable the use of your
	expanded memory through your INSTALL.EXE, "Server Environment" Option,
	and bring up your fax server. Or, you may edit the FAXLINK.INI file and
	set expandedmemory=NO.
7.	If you are using external fax devices that use your serial ports or non-
	coprocessed fax devices, you CANNOT HAVE MORE THAN 2 FAX DEVICES ON
	YOUR FAX SERVER. COM ports 1 & 3 share the same IRQ and ports 2 & 4
	share the same IRQ.
8.	If you have a Demo package, you should assign yourself a temporary 
	registration. To do that, you should be logged in as a SUPERVISOR
	equivalent and run INSTALL.EXE, "Product licensing" Option, Select your
	file server by pressing the <SPACE> bar, press <ENTER>, say <NO> a
	temporary registration will be given.

Please follow the steps outlined below based on the board you are using:

Gammalink CP, CPi XPi, and CPD fax boards:
1.	We do not work with any other Gammalink boards as of the release of
	this software. Please check with Optus as Optus is developing drivers
	for the newest Gamma boards and they may be available.
2.	Make sure the Gamma software you have is version 4.5 or above. If not,
	you should contact Gamma and get a new set of diskettes.
3.	Make sure the user logging in as the fax server does NOT have any MAP 
	ROOTS command in its login script. If the user does, YOU MUST REMOVE
	them before you proceed.
4.	Install the Gammalink software on the network on the same SERVER/VOLUME
	as the \FAXLINK directory. If it is already installed and you had MAP
	ROOTS, you must reinstall FACSys and the Gammalink software.
5.	Update your GFAX.$DC file with the lines GFXFORM # 3, where the # is
	for 1 through 8 for the number of fax boards you have. If you have
	three Gammalink fax boards your GFAX.$DC should	read
	GFXFORM 1 3
	GFXFORM 2 3
	GFXFORM 3 3 
6.	Create a TIF file as your logo file and copy that into your \FAXLINK 
	directory. If you do not have one, Gamma provides you with a TIF file
	you could use. It is called HEADER.TIF.
7.	Run our INSTALL.EXE program and under "Configure Devices" -> "Setup"
	make sure you point to the right network drive where you have your
	\GAMMALINK software installed.
8.	In the FACSys INSTALL.EXE program, under "Driver Environment" ->
	"Layout" make sure you have the name of your logo file. Extension
	should be included. (i.e. HEADER.TIF).
9.	Now you should run 
	GFQM.BAT    from your \GAMMA directory
	CASDRV.EXE  from your \FAXLINK directory
	FAXLINK.EXE from your \FAXLINK directory

Intel SatisFAXtion Classic, 200 and 400:
1.	Currently we do not work with Intel SatisFAXtion 300 boards. Please
	check with Optus to see if testing has been completed.
2.	Users with brand new boards have to first use Intel's own software to
        set the EPROM and IO address on the board.
        PLEASE NOTE THIS ONLY HAS TO BE DONE ONCE FOR EACH NEW CARD ONCE IT IS
        DONE OUR INSTALL CAN CHANGE THE CARD OR CARDS.
	If you change the IO address of a board, you must COLD boot the machine 
        for the changes to take effect in the address.
	DO NOT use the IO address 310. Our INSTALL.EXE will not see that
	particular IO address.
	Once the the new boards are serialized, please clean up your CONFIG.SYS 
	and AUTOEXEC.BAT files. Intel's setup program would/could have changed
        these files to load it's own drivers. FACSys does not require these
	drivers and FACSys will not work with them.
3.	If you have a NE2000 as your NIC and if your machine hangs, when you
	try to "Configure Devices" through our install.exe program, please run
	the INSTALL.EXE with the following parameter.
	INSTALL.EXE -x I/O address of your NIC.
	This should fix your problem.
4.	REMEMBER! - based on the board you select we copy different files into
	your \FAXLINK directory. When you installed the product if you had
	selected Intel SatisFAXtion 200 and then realize you have a Intel
	SatisFAXtion 400, you must reinstall FACSys from the Floppy.
5.	If you plan on having multiple fax devices, the device have be the same
	model.
	You cannot mix different models of SatisFAXtion boards.

Generic Class I & II devices:
OPTUS DOES NOT RECOMMEND USING THIS TYPE OF FAX DEVICE IN A MULTIBOARD
CONFIGURATIONS. WE RECOMMEND A BUS TYPE CARD FOR THIS CONFIGURATION!!!
1.	If you have a device that is listed on the INSTALL.EXE program, please
        select that device. It would give you the default values for that
	particular board, and you should use those values. These devices have
	been tested in house.
2.	To get the default values for a device, you should make a backup of
	your existing CASDRV.CFG file and run INSTALL.EXE, select the device
	and then go on to "Configure Devices". The default values will then be
	there.
3.	If the device you have is not displayed in the INSTALL.EXE program,
	the device has not been tested by Optus. It may work with our Generic
	drivers. You should try installing as a generic driver as it may work.
	You can check with Optus for support of this device.
4.	You should make sure there are no IRQ conflicts between your COM ports
	and other devices on your PC.
5.	Make sure you have a clean CONFIG.SYS and AUTOEXEC.BAT.

It is very important that you DO NOT use the Novell MAP ROOT command anywhere
in the login script for the user that is logging in as the fax server. It is
alright to have this command used by a user but NOT by the fax server.
===========================================================================
FAXLINK.INI

There are a couple of new entries to the FAXLINK.INI file, below is a list of
them and their functions.
===========================================================================
[SETTINGS]
This field is used to set the mode of your fax boards. We recommend that
during the INSTALL you set all the boards to ONLINE, SEND, RECEIVE and control
their operation from the .INI file. 

Note: GAMMA CPD boards for DID routing can only receive faxes.

The options are:
SO  send only
SR  send receive
RO  receive only
off disable

EXAMPLE:
If you have four boards and want to have two set to Send Receive, one Send
Only, and one Receive Only, the settings should be:

[settings]
default=SR
line0=SO
line1=RO

This would make boards (lines) 2 and 3 your Send Only and Receive Only,
respectively.
============================================================================
[Routing]

The routing option is used to set your fax boards up for independent inbound
distribution. The options you set here will control Autoprint and its
associated options along with Receive notification.
The options selected in this section, when enabled will over ride the options
for Autoprint in the [facsys] section of the FAXLINK.INI. If the [routing]
section/ statement is removed or left blank the [facsys] section will be valid.

Example:

[Routing]
Default=1,HPPCL,OPTUS/PRINTQ_1,AUTO,1,1,EVERYONE
line0=0,HPPCL,OPTUS/PRINTQ_1,AUTO,1,1,EVERYONE
line1=1,EPSON,OPTUS/PRINTQ_0,LETTER,0,1,DAN

Options:
1 Enable                 0=off, 1=on          Enables or disable the line entery.
2 Print driver name      HPPCL,EPSON,PSCRIPT 
3 Print Path             Server/Print queue   Location you wish to Autoprint to.
4 Form                   Letter,Legal,A4,Auto Paper tray type
5 Quality                0=Draft, 1=Quality   HPPCL only
6 Time Stamp             0=OFF, 1=ON          HPPCL only
7 Receive Notify         0=OFF, 1=ON          HPPCL only

Description:
The default entry will control boards 2 and 3. Line 0 was set in the [Settings]
section to Send Only so its [Routing] option is disabled. Line 0 could have
been left out of the [Routing] and the Default would apply, but you may elect
to set it now for any possible furture changes.
Line 1 has its options enabled with a printer type of HPPCL, the print path is
OPTUS/PRINTQ_1, the paper tray is Auto, print quality is set to Quality, time
stamp in on, and network user Dan will get receive notify messages.  
=============================================================================
[QUEUES]

The queue section is were you will tell the FACSys server what Print queues
it will be attaching to as a print server.
Only one fax server per queue. No other print servers should be servicing
this queue.

Options:
File_Server_Name/Print_queue_name

Example:

OPTUS/PRINTQ_FAX
=============================================================================
GAMMA ONLY

The DosIdle command has been provided to give network administrators the
ability to grant more CPU time to the underlying fax drivers for
implementations which require more use of the processor to maintain
multiple fax devices and/or serial fax modems (i.e. Class 1/2).

To enable the DosIdle feature, add the DosIdle= line within the [facsys]
section of the FAXLINK.INI file. The granularity can be controlled by the
value passed as the parameter. On average, start by utilizing values
ranging from 400-500 and work your way down slowly until acceptable
modem performance is achieved. The parameter will accept any value from
0 through 1000. The parameter of 0 will disable any DosIdle operations.
Provision of a number too small (i.e. < 100) may cuase the fax drivers to
take too much time from the other fax server processes (i.e. queue searches,
PCL processing, auto-printing, OCR, MHS, etc.).

Example:

[facsys]
DosIdle=500

=============================================================================
Class 1 and Class 2 MODEMS

Class1 and Class 2 modems should have the Dosidle option in the FAXLINK.INI
file set to 1.

The device drivers for Class 1, Class 2, and Intel have been modified CAS
drivers to work with a \TEMP directory on a local hard drive or with a RAM
disk. It will require the 1.05.17a CAS driver and a modification to your
AUTOEXEC.BAT. For example, you can set execute 

set CASTMP=C:\TEMP

in your AUTOEXEC.BAT of the fax server. This allows for faster and better
performance in certain situations, generally associated with slower personal
computers or slower LAN topologies.
=============================================================================
DID and DTMF

When using fax boards that support DID or DTMF please remember to set the OCR 
option in the FAXLINK.INI file to equal YES. This is the option that turns
the auto routing function on. Also set-up the user Router table via Fax.exe or
Facsys.exe before attempting in bound routing. 
=============================================================================
Windows Users Who Require DOS TSR For DOS Applications Running In DOS Sessions

If you need to fax from a DOS application and you are running Windows, you will
have to load the DOS TSR. The TSR MUST ONLY be loaded when you go to the DOS
shell from within Windows. DO NOT load the TSR before loading Windows.

You will have to select a DOS TSR HOT KEY which is different from the default
ALT-ESC as ALT (and CTRL) are reserved by Windows for Windows. We also
recommend that you load the TSR with the /C option to force the TSR into
conventional memory; this will eliminate any higher memory conflicts. When you
close the DOS shell, the TSR will be unloaded automatically from memory. So,
the next time you go to a DOS shell from Windows you will have to reload the
TSR.
=============================================================================
Managing Router Tables

FACSys provides the ability to route received faxes many different ways. Each
user can have their own routing code and routing options. Until now, admin-
istrators were not able to determine if any users were accidentally assigned
the same routing number which thus caused some problems. Also, as the router
table (ROUTER.TBL) is a flat file, indexing is not as robust as with other
database/ index oriented files. So, deleting of users from the routing table
added to the issues of multiple routing numbers being assigned to multiple
users.

On your Windows diskette, you will find an executable file, ROUTE.EXE. You will
want to run this utility on the ROUTER.TBL file found in the \FAXLINK directory
(or other directory that you have chosen other than the default at install-
ation).

When you run ROUTE, you will be able to open any ROUTER.TBL file. Once open,
you can run Close or Information from the File pull-down menu.

From the Edit pull-down menu, you can run Maintenance, which will allow you
to delete any blank records which may be left from having deleted users. You
can also Export the file to an ASCII file. With a text editor, you can print
the file to check for duplicates, and edit any records you deem appropriate.
You can then Import the file back into ROUTER.TBL. With Import, you can also
bring in a router table from another source; users have suggested that this
would be easier in setting up a router table than having to manipulate each
entry through the front-end one at a time.

Please note: when running ROUTE.EXE, make sure that no other users are
managing or editing the router table through the front-ends or through
ROUTE.EXE. It is recommended that this be run in slow or off periods to better
ensure this.
