GammaLink System Startup & Configuration
Before using the GammaLink software, the Streams Environment must be installed in 
the system.  GammaLink installation will exit if the streams network component is not 
present.

Streams can be installed with the following actions:  

	1. In the Control Panel window, start the Network application
	2. Select the Add Software button...
	3. Choose the Streams Environment module
	4. Update the Network Settings by choosing Bindings ...

Login using a system administrator’s account to start installation.  After the installation 
completes, select the appropriate configuration utility to configure an analog, PEB, or 
SCbus system.  Hit “y” in the utility’s console window to continue with fax channel 
detection and automatic configuration file generation.  Hitting any other key than "y", 
including [Enter], will cause the utility to exit.  

If the utility reports zero channels found, see the Trouble Shooting, gfdBoardDetect 
section below for additional information.

The system must be REBOOTED before attempting to start the GammaFax system 
service.  The system reboot is necessary to update the system with the new registry 
and environment variable information.  The reboot dependency will be removed in a 
future version.


Verifying Correct Configuration
Send a fax using the command line sample GFQ queue-based application, 
FAXLIST.EXE, or the GRT run-time application, SEND_FAX.EXE, both located in the 
%GFAX% subdirectory.  

If using the FAXLIST.EXE program, or any other GFQ-based application, edit the 
GFAX.$DC configuration file to make sure the GFXSHUTDOWN command parameter 
is set to 0 (zero).  By default, the auto-configuration utilities create the file with the 
GFXSHUTDOWN command parameter set to 3, the state needed for GRT-based 
applications.  For more information on GFXSHUTDOWN, see the Reference Manual.

The programs are used in the following manner:

		FAXLIST <filename> <phonenumber>
	or
		SEND_FAX <phone number to call> <file to send>

Once the applications have completed, the queue record can be viewed by using 
GFQDECOD.EXE, also located in the %GFAX% subdirectory.  See the Programmer’s 
Reference Manual for more information on the GFQ-based and GRT-based 
Programming Models.


New Features
GammaFax system service
Starting the GammaLink system is a two step process.  The first is downloading the 
firmware, GFXCX.BIN, to each fax channel.  The second is starting the GammaFax 
system service, the operating system dependent front-end to the fax channels and the 
application interface to the fax system.  

The GammaFax system service can be started manually or automatically.  The startup 
type can be configured using the Windows control panel.  

The following console commands will start an analog GammaLink system:

		net start gammafax

To stop the GammaFax system service interface to the fax channels, type the following 
command in a console window:

		net stop gammafax

To restart the GammaFax device driver (reload the firmware to each fax channel), type 
the following commands in a console window:

		net stop dialogic (must stop gammafax first)
		net start gammafax

The GammaFax service is dependent on the Dialogic service, so if the Dialogic service 
is stopped, the GammaFax service must also be stopped.

The dispatcher service outputs information to the following files:

		%SystemDrive%\gfdNT.Log
			- dispatcher service startup and shutdown status information

		%GFAX%\gfax.$co
			- dispatcher “stdout” output.  This file is kept open until the 
			dispatcher exits

See the GammaLink Reference Manual for Windows NT version 2.0 for more 
information on the GammaLink system.

New board support
	CPD/220 		- 4 port fax card, 2 analog and 2 DID fax channels
	CP-4/LSI series 2 	- 4 port analog fax card
	XPi/200 		- 2 port fax card
	CPi/200 		- 2 port fax card

See the relevant Hardware Reference Manual for more information on the boards and 
their capabilities.

Autoconfiguration
The GDK provides two new API calls

		gfdBoardDetect()
		gfdGenerateConfig()

The functions, respectively, return the number of fax channels installed in the system, 
and generate the appropriate configuration files based on specified system 
configuration parameter.  See the Programmer’s Reference Manual for more 
information on the functions.

SCbus and PEB APIs
Support for SCbus and PEB has been added. See the Programmer’s Reference 
Manual for more information on the functions. 


Compatibility Issues
Voice/Fax Systems
If Dialogic software is needed, it must be installed previous to GammaLink installation.  
All Dialogic software must be located in the following subdirectory.  Note that the 
Dialogic software MUST be installed on the System Drive (where the \WINNT35 
directory is located):

		%SystemDrive%\dlgcdev\dialogic

Systems with existing Dialogic software installed elsewhere must re-install to the above 
mentioned location and subdirectory.

Existing GRT Applications
The mneumonic GRT_ABORT has been replaced with GRT_END_CALL as a 
parameter for grtRespond().  See the Programmer’s Reference Manual for more 
information on the functions.

Specifying The File Path
Any file submitted to be sent must specify a full path.  The GammaFax system service 
does not assume that %GFAX% is the working directory and since the dispatcher 
binary is located in %SystemRoot%, it does not have a “current directory”.

Long File Names
Long file names are not guaranteed to work.  Use the NT 8.3 short-name equivalent.

DLLS
GammaLink applications need both NTGDK.DLL and MSVCRT20.DLL to be present in 
%SystemRoot%\system32 to execute properly.  Both of the DLLs are installed by the 
GDK software, if not present.  The MSVCRT20.DLL is also installed by the Microsoft 
Visual C++ 2.0 development system.

Network Drives
The default installation for a system service provides a local system logon account and 
, hence, does not provide network access privileges.  To enable sending files located 
on a network drive or receive files to a network drive, the GammaFax system service 
must log on to an account with network access.  

The following is one method of changing the default GammaFax service logon account:

	1.  Start the Services applet in the Control Panel.
	2.  Select the GammaFax service and choose the Startup... button
	3.  In the dialog window, change the Log On As: option
		a) select "This Account" and the default LocalSystem account will appear
		b) change LocalSystem to another account with adminstrative privileges
	4.  Choose OK to have system update the changes.


System Requirements
Only Intel uniprocessor X86 architecture is currently supported.  No Symmetric 
MultiProcessor (SMP) machines have been tested.

Applications must be built with Microsoft Visual C++ 2.x (4.x will be qualified in future 
versions).


Trouble Shooting Tips
Installation
Before starting GammaLink software setup, all running Dialogic and GammaLink 
services and related software must be stopped otherwise the installation utility will fail 
to complete.


GammaFax System Service
The "boardtype" command in GFAX.$DC will always generate an error in gfax.$co, 
regardless of whether the value is correct or incorrect.  This error can be ignored.

In high density fax systems, channel 28 will fail with error 4500 while attempting to 
receive a fax.  This is because the GammaLink file naming system causes fax channel 
28 to create the receive filename with the first character as |’ (vertical bar character, 
code 124, in codepage 437), which is the pipe symbol in Windows NT.  This channel 
can send faxes without problems.

The GammaFax service will return error 3080 when it cannot find the filename specified 
in the fn_send field of the queue record.  If this error is returned, make sure the full path 
is specified in the fn_send field of the queue record.  If the path is a network drive, see 
Compatibility Issues, Network Drives for additional information.

The GammaFax service will return error 4500 when it attempts to receive a faxfile to an 
invalid directory.  This path may be specified in fn_received field of the queue record, 
GFXRECVPATH command, or defined in %GFAXR% environment variable.  Make sure 
the path specified is valid (and the directory exists) and if the path is a network drive, 
see Compatibility Issues, Network Drives for additional information.

There is no cleanup mechanism for gfdNT.Log (both in %GFAX% and in 
%SystemDrive%\).  The log files will continue to grow in size unless manually deleted.

GammaLink recommends installing and running the GammaLink GDK with the release 
version of Windows NT 3.51.  The GDK has not been qualified with Windows NT 
service packs.

GammaFax system service debugging information can be enabled with the following 
command:

		debug 0xb7b7

Place the above command near the beginning of the GFAX.$DC file.  The debug 
information is logged to %GFAX%\GFAX.$DL.  


GFSH.EXE Utility
GFSH.EXE will error when reading configuration file GFSH.CMD if the setloc command 
SC2000 I/O address parameters are not in "sequential order".  For example, if there are 
3 CP-4/SC cards in the system:

		I/O addr              1             2            3
		====================================================
		GOOD:	  setloc  3   0x358         0x158        0x168
		BAD:	  setloc  3   0x158         0x358        0x168

This is generally not an issue as the PEB and SCbus auto-configuration utilities create 
the files correctly.  


PEB
gl_pebenter is not thread-safe and should be called once per process.  If it is called a 
second time, before gl_pebexit, it returns a -1 error code.  


SCbus
The "Configure SCbus" utility creates a GFAX.$DC file with the gfxdid <c> 6 0 
command, which must be removed before starting the GammaFax service.

gl_scenter is not thread-safe and should be called once per process.  If it is called a 
second time, before gl_scexit, it returns a -1 error code.  


grtInit()
When GRT_DIAL_RESPONSE_ENABLE is specified in the grtInit() function call, the 
send fax transaction fails.  GRT_DIAL_ENABLE does function as documented.  The 
status code returned is 3933 (GX1_HIGHDRY).


gfdBoardDetect() and gfdGenerateConfig()
gfdBoardDetect will fail when detecting the new CPi/200 and XPi/200 boards.  Manual 
configuration of the necessary configuration files is needed when using the new 
boards.  The files to be modified are the following:

		%GFAX%\GFAX.$DC
		%DIALOGICDIR%\DIALOGIC\CFG\GLFXCFG

The Reference Manual contains information necessary to create or edit these files 
manually.

If you are experiencing problems with gfdBoardDetect it may fail if its threads are not 
serviced within a set time period.  To maximize CPU cycles for gfdBoardDetect, do the 
following:

		- exit all background tasks

		- convert the Configuration utility's console window to full-screen mode
		by typing <ALT><ENTER> with it in the foreground.

		- make sure Windows NT tasking is set for "Best Foreground Application 
		Response Time".  Verify the setting of this option by starting the System 
		applet in the Control Panel and choose the Tasking...  button.

gfdBoardDetect and gfdGenerateConfig errors are logged to the %GFAX%\gfdNT.Log 
file.


Contacting GammaLink
GammaLink
1314 Chesapeake Terrace
Sunnyvale, CA  94089
USA

Main voice:  +1 (408) 744-1400
Main fax:      +1 (408) 744-1900
Fax retrieval: +1 (408) 734-9906

Technical Support voice:  +1 (408) 745-2250
Technical Support fax:      +1 (408) 745-2236

Compuserve:  75300,2226
email:		techs@gammalink.com
Internet:	http://ww.gammalink.com


 



