Innovative File Transfer and Management

Gigabyte Express™ T1 & DSL for Mac OS X & Linux

 
  Click here for Linux manual
 

USER MANUAL
FOR


Gigabyte Express™ 7 for Mac OS X
with RELIA™ Technology


Internet Protocol File Transfer
for Mac OS X



N I W O T    N E T W O R K S,    I N C.



721 9th Avenue
Longmont, CO 80501
(303) 772-8664 / (800) 657-3278

© Copyright 2000-2010 Niwot Networks, Inc.

0.1542 February 2010

February 2010 GBX MAC 7.213
November 2006 GBX MAC 7.211
July 2006 GBX MAC 7.210
March 2006 GBX MAC 7.209
September 2005 GBX MAC/LIN 7.200
July 2005 GBX MAC/LIN 7.119



Table Of Contents



1. Gigabyte Express 7 for Mac OS X

1.1. Gigabyte Express Introduction

1.2. System Requirements

2. RELIA™ Technology

2.1. RELIA™ Technology Summary (Patent Nos. US 6,445,717, US 6,895,019)

2.2. RELIA™ Technology Reports

3. Gigabyte Express Installation

3.1. Software Installation from Scratch

3.2. Firewall Notes

3.3. Software Upgrade

3.4. Uninstall

4. Gigabyte Express

4.1. Start Up

4.2. Menu Commands

4.3. Stopping the Program

5. Configuring Gigabyte Express

A Minimal Example GBXMAC.INI file

5.1 Answer session settings

5.2 Dial session settings

5.3 Global settings

5.3.1 Adding entries to the GBXMAC.INI file

5.4 Alphabetic list of configuration entries

5.5 The Gigabyte Express PhoneBook file GBXPHONEBOOK.INI

5.5.1 Sections within the PhoneBook file

5.5.2 Format of PHONEBOOK entries

5.5.3 A Minimal Example PhoneBook file

5.5.4 Adding entries to the PhoneBook file

5.6 Configuring Gigabyte Express for Encryption

5.6.1 Creating Encryption passwords

5.6.2 Example of Encryption password creation on local and remote Gigabyte Express machines

6. Autosend

A Minimal Example Auto Send List file

6.1. Overview

6.2. Sent Files Handling

6.3. AutoSendList format

6.3.1. WAIT and WHEN in NiwotAutoSendList

6.3.2. GET in NiwotAutoSendList (Autoget)

6.3.3. [NoFolder] in NiwotAutoSendList

6.3.4. Source folder

6.3.5. Destination folder

6.3.6. Working with remote volumes

6.3.7. Gigabyte Express phonebook name

6.3.8. Options

6.3.9. Example

7. Configuration Setting Definitions

8. ERRORS

8.1. Error Messages Reported by Gigabyte Express

8.2. Gigabyte Express Transport Layer Messages

8.3. NiwotTemp_Do Not Use

9. Release Notes

9.1. Release Notes 7.2.1.1

9.2. Release Notes 7.2.1.0

9.3. Release Notes 7.2.0.9

9.4. Release Notes 7.2.0.0

9.5. Initial Release Notes 7.1.1.9

10. Index and License

1. Gigabyte Express 7 for Mac OS X Back to Table of Contents



1.1. Gigabyte Express Introduction Back to Table of Contents

Gigabyte Express 7 for Mac OS X provides the highest performance file transfer solution when you need to move large files by way of Internet Protocol (IP) backbones.
Two transport types are supported, TCP and RELIA.
RELIA™ technology (Patent Nos. US 6,445,717, US 6,895,019) Enhances TCP (Transmission Control Protocol) to handle packet loss (also called congestion) and long delay (also called ping time or latency) - your information gets through under harsh network conditions. Niwot's RELIA Technology is an extension to TCP which adds redundant information that enables the receiver to reconstruct lost information without requiring the time delay of retransmission. RELIA™ Technology also adds support of 32 bit window size.

The first application to support RELIA was Niwot's Gigabyte Express for Windows 5.0. RELIA Technology uses Large Window and Packet Recovery™ techniques to optimize throughput over the congested international and satellite Internet or intranets. With 4 percent packet loss, RELIA Technology is 2.9 times as fast as naked TCP on the national Internet, 8.8 times as fast on the international Internet, and 15.8 times as fast on the satellite Internet.

Gigabyte Express 7 also includes the File Pipeline - Improves multi-file transfers by filling the data pipe, 5 times as fast for large numbers of small files when compared to a protocol such as FTP which requires the first file transfer be complete before the second file transfer is begun.

1.2. System Requirements Back to Table of Contents

1) Mac OS X
2) 20 Megabytes of disk storage.
3) A minimum of 256 Megabytes of RAM, 512 Megabytes or greater is preferred.
4) Gigabyte Express 7 uses up to 5 megabytes of RAM per session, and can run up to 16 simultaneous answer sessions and 8 simultaneous dial sessions.

2. RELIA™ Technology Back to Table of Contents

2.1. RELIA™ Technology Summary (Patent Nos. US 6,445,717; US 6,895,019) Back to Table of Contents

RELIA™ Technology is an extension to TCP that uses redundant UDP packets to allow the receiving side to recover from lost packets without requiring the sender to retransmit them. The more redundant packets which are sent, the more severe the congestion can be without degrading performance. The DEMO provides redundancy levels to recover from packets being lost 1 or 2 packets at a time (RED1, RED2 redundancies).

RELIA™ Technology also supports a 32 bit window size, allowing full throughput even when faced with the typical 300 millisecond international Internet and 600 millisecond satellite Internet delays.

RED1 is default, can recover without retransmission from single lost packets. Use this for optimum throughput on satellite and international IP connections experiencing low congestion. (the sending side is reporting less than 1 chunk resent per 1000 chunks sent).

RED2 can recover without retransmission from pairs of lost packets. This is a robust level, capable of recovering from most cases of satellite and international congestion.

2.2. RELIA™ Technology Reports Back to Table of Contents

GBXWin.log entries made by a session using RELIA Technology:

Common information:

Date > Time > Session ID RELIA

Dial Session Connection start:

REDx Connecting on 206.124.12.218 to 185.135.4.151:168
x is 1,2,4, or 8
Connecting on Source IP address to
Destination IP address:Destination port

Answer session Connection start:

Answering on 185.135.4.151:168 from 206.124.12.218
Answering on Destination IP address:Destination port from
Source IP address.

Dial or answer session Connection finish:

REDx: TargetRate=1600 Kbps
x is 1,2,4, or 8
TargetRate= the kilobits/sec link rate requested by PhoneBook entry on the Dialing side

chunks rcvd=40, rercvd=0, sent=2362, chunks resent=4
chunks rcvd=xx, the total number of chunks(multi-packet blocks) received.
rerecvd =xx, the number of extra chunks received(retransmitted by other side)
chunks resent= xx, the number of chunks retransmitted by this station

outgoing lost =305 sent = 16683 rcvd =16378
outgoing lost = xxx is the difference between the number of packets this station sent(given in sent=) and the number of packets the far side received(given in rcvd=).

incoming lost =0 sent= 3745 rcvd =3745
incoming lost=xxx is the difference between the number of packets this station received(given in rcvd=) and the number of packets the far side sent(given in sent=).

3. Gigabyte Express Installation Back to Table of Contents

3.1. Software Installation from Scratch Back to Table of Contents

Gigabyte Express for Mac OS X is distributed as a gzipped(compressed) disk image file like "GigabyteExpressDSL.PPC.7210.dmg.gz" or "GigabyteExpressT1.INTEL.7210.dmg.gz".

Once the compressed disk image file is downloaded, it should automatically be decompressed and the Installer will start. Follow the prompts as displayed to install Gigabyte Express at the default location in Applications/GigabyteExpress.

You may start Gigabyte Express immediately with the Finder, by navigating into the Applications folder, then into the GigabyteExpress folder and double-clicking on the GigabyteExpress icon.

After installation, you will find a file like "GigabyteExpressDSL.PPC.7210.dmg" on the Desktop. This is the Installer disk image file which you may save to a different location or simply move to the Trash. If you double-click on the "dmg" file, the disk image will be "mounted" and you may then click on the mounted disk in the upper-left area of the Finder window. You will see the Installer package(pkg) file within the disk image. You may Eject the mounted disk image (using Apple/cloverleaf ⌘E) when you are finished.

3.2. Firewall Notes Back to Table of Contents

TCP connections start on port 32779 (default for Mac OS X). Thereafter communications move to default ports with port values of:

Gigabyte Express DSL Answer sessions needs to allow incoming TCP connections to port 32779 and ports 32780 through the maximum number of answer sessions.
  DSL (4+4) we recommend allowing incoming TCP connections to ports 32780 through 32783.
  For DSL (16) we recommend allowing incoming TCP connections to ports 32780 through 32795.
  For DSL (32) we recommend allowing incoming TCP connections to ports 32780 through 32810.
Gigabyte Express DSL Dial sessions initiate outgoing TCP connections from ephemeral ports and most firewalls do not block outgoing TCP connections.

In summary, for Windows, the default for DSL (4+4) products is to allow incoming TCP connections to ports 32779 and 32780 through 32783.

Gigabyte Express T1 and T2 TCP Answer sessions needs to allow incoming TCP connections to port 32779 and ports 32780 through the maximum number of answer sessions.
  For T1 and T2 (4+4) we recommend allowing incoming TCP connections to port 32779 and ports 32780 through 32783. Gigabyte Express T1 and T2 TCP Dial sessions initiate outgoing TCP connections from ephemeral ports and most firewalls do not block outgoing TCP connections.

RELIA connections start with both TCP connections and UDP packets in to port 32778 (default for Mac OS X). Thereafter communications move to default ports with port values of:

Gigabyte Express T1 and T2 RELIA Answer sessions needs to allow incoming TCP connections to port 32778 and ports 32780 through the maximum number of answer sessions.
Gigabyte Express T1 and T2 RELIA Answer sessions needs to allow incoming UDP packets to port 32778 and ports 32780 through the maximum number of answer sessions.
Gigabyte Express T1 and T2 RELIA Dial sessions initiate outgoing TCP connections from pairs of ports counting down from the 32777,32776 pair, with 2 ports consumed per additional Dial session.
Gigabyte Express T1 and T2 RELIA Dial sessions initiate outgoing UDP packets from pairs of ports counting down from the 32777,32776 pair, with 2 ports consumed per additional Dial session.
Gigabyte Express T1 and T2 RELIA Dial sessions also receive incoming UDP packets from pairs of ports counting down from the 32777,32776 pair, with 2 ports consumed per additional Dial session.
  T1 and T2 (4+4) we recommend allowing incoming TCP connections to port 168 and ports from 32780 through 32783.
  T1 and T2 (4+4) we recommend allowing incoming UDP packets to port 168 and ports from 32770 through 32783.

In summary, for Windows, the default for T1 and T2 products is to allow incoming TCP connections to ports 32779, 327788, and ports 32780 through 32783.
  UDP packets should be allowed in to ports 32778 and the ports from 32770 through 32783.

Within the GBXMAX.INI file, the ANSWSECOND= parameter is by default set to 32780 and the above notes apply.

The customer may specify different starting ports and ANSWSECOND value (global) if desired:

ANSPORTXX
ANSWSECOND


3.3. Software Upgrade Back to Table of Contents

The GBXMAC.INI file has the serial number/validation code, and settings. The GBXPHONEBOOK.INI has the PhoneBook information.

Installation of newer versions may overwrite these files, so you may wish to save these INI files before upgrades so that your settings are preserved.

3.4. Uninstall Back to Table of Contents

There is no set procedure when uninstalling Gigabyte Express for Mac OS X. You may simply delete all contents of the Applications/GigabyteExpress folder, though you may wish to save the INI files for later testing.

4. Gigabyte Express Back to Table of Contents

4.1. Start Up Back to Table of Contents

Double-click on the GigabyteExpress icon in the GigabyteExpress folder, within the Applications folder. The Gigabyte Express application will start, with Dial sessions scanning their Autosend lists, and Answer sessions waiting for incoming connections.

4.2. Menu Commands Back to Table of Contents

There are a limited number of menu commands at this time:

 File menu --> Send Files/Folders: Use this command to initiate a Manual Send of files and/or folders. First click on a particular Dial Session to select it, then select this File menu command. Use the dialog box to select files/folders from the table on the left, adding them to the table on the right, and then click on the Send button.
 
 
 File menu --> Get Files/Folders: Use this command to initiate a Manual Get of files and/or folders. First click on a particular Dial Session to select it, then select this File menu command. Use the dialog box to select files/folders from the table on the left, adding them to the table on the right, and then click on the Get button.
 
 
 Edit menu --> Options: Use this command to configure a Dial Session to operate in either Manual or Autosend mode. First click on a particular Dial Session to select it, then select this Edit menu command.
 
 
 Views menu --> Log Window: Use this command to open/close the Log Window. Note: information will only be written to the Log Window if you have enabled the Log File with LOGFILE=1 in GBXMAC.INI.
When using the Log Window, you may select text in the Log Window and copy it using using Apple/cloverleaf ⌘C (to paste into another document).
   
 Views menu --> Tile: Use this command to automatically arrange all of your windows on-screen.
   
 Help menu --> User Manual: Use this command to read the User Manual. Note: The User Manual will come up in a separate window of the Safari browser.

4.3. Stopping the Program Back to Table of Contents

To stop Gigabyte Express, select "Quit GigabyteExpress" from the GigabyteExpress menu.

5. Configuring Gigabyte Express Back to Table of Contents


For Gigabyte Express on Mac OS X, configuration is done by editing the GBXMAC.INI and GBXPHONEBOOK.INI files.

A Minimal Example GBXMAC.INI file
This example file is configured to provide 2 Dial sessions and 2 Answer sessions (one for TCP and one for RELIA).

[PREFERENCES]

; Global settings for both Dial and Answer sessions
DISPENNAME=0
LOGFILE=1
LOGACCT=0
LOGACCTFOLDER=
MACSUPPORT=0
PENNAME=macdemo
SERIALNUM=niwotdemo1
VALIDATIONCODE=
SORTTYPE=1
WATCHDOG=3
; BothMaster/BothSessionSpecific
ANSWSECOND=32780

; Global settings for Dial sessions
AUTOEXAMTICK=10
AUTOSENDTICK=10
LRCVERIFY=0

; Global settings for Answer sessions
ALLOWASPATHING=0
ANSWERENCRYPTION=1
AUTOGETSENTHANDLING=USESENT
AUTOGETLEAVEFOLDERS=0
AUTOGETMOVESELECTEDPATH=
INBASKET=
OUTBASKET=

; Number of Dial sessions
; (Serial number may enable more or less)
SESSIONSDIAL=2

; Dial session specific settings
;
; Dial session #1
AUTOLIST1=NiwotAutoSendList.txt
SENTHANDLING1=USESENT
LEAVEFOLDERS1=0
AUTOSENDMOVESELECTEDPATH1=
OPTIONSDIAL1=MANUAL
PHONEBOOK1=niwothTCP
;
; Dial session #2
AUTOLIST2=NiwotAutoSendList2.txt
SENTHANDLING2=USESENT
LEAVEFOLDERS2=0
AUTOSENDMOVESELECTEDPATH2=
OPTIONSDIAL2=AUTOSEND
PHONEBOOK2=niwothqWin

; AnswMasterOnly
; Number of Answer sessions that the server can serve at once
; (Serial number may enable more or less)
SESSIONSANSWER=2

; AnswMaster/AnswSession Specific settings
; TCP HANDSHAKE LISTENS ON PORT 32779
; RELIA HANDSHAKE LISTENS ON PORT 32778
;
; Answer session #1, listening for TCP connections on port 32779
ANSADDR1=0.0.0.0
TRANSPORT1=TCP
ANSPORT1=32779
;
; Answer session #2, listening for RELIA connections on port 32778
ANSADDR2=0.0.0.0
TRANSPORT2=RELIA
ANSPORT2=32778


5.1 Global Answer session settings in GBXMAC.INI:

ALLOWASPATHING=0  (Allow Autosend Pathing)
ANSWERENCRYPTION=1  (Answer session encryption setting)
AUTOGETSENTHANDLING=USESENT  (File Handling After Autoget)
AUTOGETLEAVEFOLDERS=0  (Leave Folder Structure in Place)
AUTOGETMOVESELECTEDPATH=  (Files Moved Here After Autoget)
INBASKET=/Test/inbasket  (The InBasket)
OUTBASKET=/Test/outbasket  (The OutBasket)

Specific Answer session settings in GBXMAC.INI:

; AnswMasterOnly
; Number of Answer sessions that the server can serve at once
; (Serial number may enable more or less)
SESSIONSANSWER=2  (Number of Answer sessions)

; AnswMaster/AnswSession Specific settings
; TCP HANDSHAKE LISTENS ON PORT 32779
ANSADDR1=0.0.0.0  (Answer IP Address)
TRANSPORT1=TCP  (TCP Transport Type)
ANSPORT1=32779  (Answer Port, for TCP)
;
; RELIA HANDSHAKE LISTENS ON PORT 32778
ANSADDR2=0.0.0.0  (Answer IP Address)
TRANSPORT2=RELIA  (RELIA Transport Type)
ANSPORT2=32778  (Answer Port, for RELIA)


5.2 Global Dial session settings in GBXMAC.INI:

AUTOEXAMTICK=10  (Poll Folders Every xxx Seconds)
AUTOSENDTICK=10  (Examine Files Every yyy Seconds)
LRCVERIFY=1  (Read After Write Integrity Check)

Specific Dial session settings in GBXMAC.INI:

; Number of Dial sessions
; (Serial number may enable more or less)
SESSIONSDIAL=2  (Number of Dial sessions)

; Dial session specific settings
AUTOLIST1=NiwotAutoSendList.txt  (The Autosend List file)
SENTHANDLING1=DELETE  (File Handling After Autosend)
LEAVEFOLDERS1=0  (Leave Folder Structure in Place)
AUTOSENDMOVESELECTEDPATH1=  (Move Files Here After Autosend)
OPTIONSDIAL1=MANUAL  (This Dialer is Manual Send)
PHONEBOOK1=niwothTCP  (Using PhoneBook entry "niwothTCP")
;
AUTOLIST2=NiwotAutoSendList2.txt  (The Autosend List file)
SENTHANDLING2=USESENT  (File Handling After Autosend)
LEAVEFOLDERS2=0  (Leave Folder Structure in Place)
AUTOSENDMOVESELECTEDPATH2=  (Move Files Here After Autosend)
OPTIONSDIAL2=AUTOSEND  (This Dialer is Autosend)
PHONEBOOK2=niwothqWin  (Using PhoneBook entry "niwothqWin")


5.3 Global settings for both Answer and Dial sessions in GBXMAC.INI:

; BothMaster/BothSessionSpecific
ANSWSECOND=32780  (The Answer session Data Transfer Port)
;
DISPENNAME=0  (Allow PenName Disabling)
LOGACCT=0  (The gbxacct.log Accounting Log File)
LOGACCTFOLDER=  (Folder to write Accounting Log File)
LOGFILE=1  (The gbxmac.log Log File)
MACSUPPORT=0  (Provide Macintosh file support for LINUX ONLY)
PENNAME=niwot1demo  (Your PenName)
SERIALNUM=niwotdemo1  (The Serial Number)
VALIDATIONCODE=  (The Validation Code)
SORTTYPE=1  (The File Sorting algorithm used)
WATCHDOG=3  (The Watchdog Timeout value, in minutes)


5.3.1 Adding entries to the GBXMAC.INI file

Adding more Dial and/or Answer sessions is done by editing the GBXMAC.INI file (assuming that your serial number/validation code pair allow more Dial/Answer sessions).

• To add another Dial session, you must increase the value of SESSIONSDIAL and then add the specific numbered entries like so:

SESSIONSDIAL=3    (used to be only 2 Dial sessions)

;Here are the new entries for the 3rd Dial session
AUTOLIST3=NiwotAutoSendList3.txt
SENTHANDLING3=USESENT
LEAVEFOLDERS3=0
AUTOSENDMOVESELECTEDPATH3=

Note that you would need to create the "NiwotAutoSendList3.txt" file and
define the Autosend/Autoget entries within.

• To add another Answer session, you must increase the value of SESSIONSANSWER and then add the specific numbered entries like so:

SESSIONSANSWER=3    (used to be only 2 Answer sessions)

;Here are the new entries for the 3rd Answer session
ANSADDR3=0.0.0.0
TRANSPORT3=TCP
ANSPORT3=32779



5.4 Alphabetic list of configuration entries:

ENTRY (case sensitive)   DEFAULT  
ALLOWASPATHING=  Default is 0 (Answer session Global) 
ANSADDRXX=  Default is 0.0.0.0 (Answer session Specific) 
ANSPORTXX=  Default is 32779 for TCP, 32778 for RELIA (Answer session Specific) 
ANSWERENCRYPTION=  Default is 1, (Answer session Global) 
ANSWSECOND=  Default is 32780 (Answer/Dial session Global) 
AUTOEXAMTICK=  Default is 30 seconds (Dial session Global) 
AUTOGETSENTHANDLING=  Default is USESENT (Answer session Global) 
AUTOGETLEAVEFOLDERS=0  Default is 0 (Answer session Global) 
AUTOGETMOVESELECTEDPATH=  Default is blank (Answer session Global) 
AUTOLISTXX=  Default is NiwotAutoSendList.txt (Dial session Specific) 
AUTOSENDMOVESELECTEDPATHXX=  Default is blank (Dial session Specific) 
AUTOSENDTICK=  Default is 30 seconds (Dial session Global) 
DISPENNAME=  Default is 0 (Answer session Global) 
INBASKET=  Default is blank (Answer session Global) 
LEAVEFOLDERSXX=  Default is 0 (Dial session Specific) 
LOGACCT=  Default is 0 (Answer/Dial session Global) 
LOGACCTFOLDER=  Default is blank (Answer/Dial session Global) 
LOGFILE=  Default is 1 (Answer/Dial session Global) 
LRCVERIFY=  Default is 0 (Dial session Global) 
MACSUPPORT=  Default is 0 (Answer/Dial session Global) 
OPTIONSDIALXX=  Default is blank, interpreted as Manual Send (Dial session Specific) 
OUTBASKET=  Default is blank (Answer session Global) 
PENNAME=  Default is niwot1demo (Answer/Dial session Global) 
PHONEBOOKXX=  Default is blank (Dial session Specific) 
SENTHANDLINGXX=  Default is USESENT (Dial session Specific) 
SERIALNUM=  Default niwotdemo1 expires. (Answer/Dial session Global) 
SESSIONSANSWER=  Default is 1 so Demo users will have 1 TCP Answer session.(Answer session Specific) 
SESSIONSDIAL=  Default is 2. (Dial session Specific) 
SORTTYPE=  Default is 1. (Answer/Dial session Global) 
TRANSPORTXX=  Set to TCP or RELIA (Answer session Specific) 
VALIDATIONCODE=  Default is blank for expiring Demo. (Answer/Dial session Global) 
WATCHDOG=  Default is 3 minutes (Answer/Dial session Global) 


5.5 The Gigabyte Express PhoneBook file GBXPHONEBOOK.INI

The Gigabyte Express PhoneBook file GBXPHONEBOOK.INI contains the PhoneBook entries used by the program. These are the entries that outgoing Dial sessions use to connect to remote hosts. A typical entry in the PhoneBook file might look something like this:

LondonTCP=[][TCP/IP][188.164.16.122][0.0.0.0][NoPenName][TargetRate=0][Port=167]

Also contained in the PhoneBook file are usernames and encrypted passwords in the [USERS] section, which define the users that are allowed incoming encrypted connections.

5.5.1 Sections within the PhoneBook file

There are 3 sections within the PhoneBook file:

[PREFERENCES] Contains the [PREFERENCES] PHONELIST and the [PREFERENCES] USERLIST
[PHONEBOOK] Contains the actual PHONEBOOK entries
[USERS] Contains any User entries and their encrypted passwords, defined for incoming encrypted connections

The [PREFERENCES] PHONELIST:
This is a list of the names of all PHONEBOOK entries. In a one-to-one relationship with the PHONEBOOK section entries, i.e. if there are two PHONEBOOK entries named LondonTCP and ParisRELIA, then the PHONELIST would look like:

PHONELIST=LondonTCP;ParisRELIA;    (entries are separated by semicolons)

The [PREFERENCES] USERLIST:
This is a list of the names of all USERS entries (used only for incoming encrypted connections). In a one-to-one relationship with the USERS section entries, i.e. if there are three USERS entries named niwotdemo, Gerald, and Samantha, then the USERLIST would look like:

USERLIST=niwotdemo;Gerald;Samantha;    (entries are separated by semicolons)

The PHONEBOOK section:
These are the actual PHONEBOOK entries. Using the examples above of LondonTCP and ParisRELIA, the PHONEBOOK entries might look like:

LondonTCP=[][TCP/IP][188.164.16.122][0.0.0.0][NoPenName][TargetRate=0][Port=167]
ParisRELIA=[][RELIA RED1][188.177.43.98][0.0.0.0][NoPenName][TargetRate=0][Port=168]

The USERS section:
These are the actual USERS entries, used only with encryption. These entries define the USERS that are allowed incoming encrypted connections. Using the examples above of niwotdemo, Gerald, and Samantha, the USERS entries might look like:

niwotdemo=[niwotdemo]
Gerald=[ENC!29CCDFC711B16DD8]            (Click here for an explanation of these encrypted passwords)
Samantha=[ENC!33AD619C72914B4D]

Note that the User "niwotdemo" has the password displayed "in the clear", as this User should be used for encryption demonstration purposes only.

5.5.2 Format of PHONEBOOK entries

Using the example PhoneBook entry of LondonTCP, we will define all fields:

LondonTCP=[][TCP/IP][188.164.16.122][0.0.0.0][NoPenName][TargetRate=0][Port=167]

After the "Name=" field at the start of the entry, there are 4 positional parameters (these are ALWAYS in the same order):

Field #1  Dial string  []  Leave this field blank
Field #2  Transport type  [TCP/IP] or [RELIA RED1] or [RELIA RED2]  The transport type to use
(Note the space character between RELIA and RED1/RED2)
Field #3  Remote Hostname/IP Address  [www.yourname.com] or [188.164.16.122]  The Hostname/IP Address of the Remote machine
Field #4  Local IP Address  [0.0.0.0]  The IP Address of the Local machine

Regarding the Remote Hostname/IP Address: This field specifies the Hostname/IP address of the remote workstation with which a Dial session will communicate. This can be entered as a host name (e.g., win.gigabytex.com) or as a dotted IP address (e.g., 64.32.164.216).

Regarding the Local IP Address: This field specifies the local IP address used during communication. A local address of 0.0.0.0 is recommended if you are on a machine where your IP address changes, this may happen if you are using DHCP or a dial-up connection. Note that if your machine is multi-homed (having more than one IP address) then you may wish to put in a particular IP address to force it to be used. You may enter 127.0.0.1 in both the local and remote IP addresses to test on a single machine. In this case the answer session should be set to answer on 0.0.0.0.

The remaining parameters that you may use in a PhoneBook entry are non-positional parameters (they may be in any order, and they may or may not even exist).

[NoPenName]  Do not use Penname
[NoComp]  Do not use Compression
[Port=167]  Define the Port to use, normally 167 for TCP/IP, 168 for RELIA
[TargetRate=0]  The kilobits/sec link rate, 0 means unlimited (full bandwidth of link). If a non-zero number is specified then the connection will be throttled or governed to not exceed the specified number of kilobits per second. This link rate governor feature allows you to put an upper limit on the amount of bandwidth Gigabyte Express consumes.

If you wish to use Encryption for outgoing connections, then add the following parameters:

[Encryption=1]  0 = No Encryption, 1 = Support/Use Encryption, 2 = Require Encryption (mandatory)
[Username=Joe]  The Username for Encryption sessions
[Password=ENC!29CCDFC711B16DD8]  The Password associated with this Username

(Click here for an explanation of the above encrypted password)

5.5.3 A Minimal Example PhoneBook file

Contents of an example GBXPHONEBOOK.INI:

[PREFERENCES]
PHONELIST=niwothqWin;niwothqWincrypt;niwothqRED1;
USERLIST=niwotdemo;tester;
[PHONEBOOK]
niwothqWin=[][TCP/IP][win.gigabytex.com][0.0.0.0][NoPenName][TargetRate=0][Port=167][Encryption=0]
niwothqWincrypt=[][TCP/IP][win.gigabytex.com][0.0.0.0][NoPenName][TargetRate=0][Port=167][Encryption=1][Username=niwotdemo][Password=niwotdemo]
niwothqRED1=[][RELIA RED1][win.gigabytex.com][0.0.0.0][NoPenName][TargetRate=0][Port=168]
[USERS]
niwotdemo=[niwotdemo]
tester=[ENC!90DE78102AA39FFC]            (Click here for an explanation of this encrypted password)

The example file above defines three PhoneBook entries named "niwothqWin", "niwothqWincrypt", and "niwothqRED1", and also defines two user/password entries named "niwotdemo" and "tester".

5.5.4 Adding entries to the PhoneBook file

• When adding a new PhoneBook entry to the GBXPHONEBOOK.INI file, be sure to edit both of the [PREFERENCES] PHONELIST and [PHONEBOOK] sections. For example, a new PhoneBook entry named "SeattleTCP" would require changes like the following:

[PREFERENCES]
PHONELIST=niwothqWin;niwothqWincrypt;niwothqRED1;SeattleTCP;
[PHONEBOOK]
SeattleTCP=[][TCP/IP][184.160.4.108][0.0.0.0][TargetRate=0][Port=167]

Likewise, when removing a PhoneBook entry from the GBXPHONEBOOK.INI file, be sure to remove the entry from both the [PREFERENCES] PHONELIST and [PHONEBOOK] sections.

• When adding a new user/password entry to the GBXPHONEBOOK.INI file, be sure to edit both of the [PREFERENCES] USERLIST and [USERS] sections. For example, a new User named "Tom" would require changes like the following:

[PREFERENCES]
USERLIST=niwotdemo;tester;Tom;
[USERS]
Tom=[ENC!2AA39FFC90DE7810]            (Click here for an explanation of this encrypted password)

Likewise, when removing a user/password entry from the GBXPHONEBOOK.INI file, be sure to remove the entry from both the [PREFERENCES] USERLIST and [USERS] sections.

5.6 Configuring Gigabyte Express for Encryption

Gigabyte Express encryption uses a Diffie-Hellman key exchange, encryption is 128 bit Rijndael. Each new session/connection establishes a different encryption key than the last session/connection.

In order for a local Gigabyte Express machine to communicate in encrypted fashion with a remote Gigabyte Express machine, the following parameters must be in order:

1. The local Gigabyte Express machine must Support/Use or Require Encryption in its configuration of the Dialer's PhoneBook entry in GBXPHONEBOOK.INI.

2. The remote Gigabyte Express machine must Support/Use or Require Encryption in the ANSWERENCRYPTION setting in GBXMAC.INI.

3. The local and remote Gigabyte Express machines must agree on an identical user/password pair to use:

• the local Gigabyte Express must define the Username and Password in its configuration of the Dialer's PhoneBook entry in GBXPHONEBOOK.INI.

• the remote Gigabyte Express must define the Username and Password in its configuration of the [PREFERENCES] USERLIST and [USERS] sections in GBXPHONEBOOK.INI.

5.6.1 Creating Encryption passwords

The Encryption passwords for Gigabyte Express have the following format:

ENC!2AA39FFC90DE7810

Where the first 4 characters ENC! indicate that this is an encrypted password string.

To have Gigabyte Express generate an encrypted password string, use the "-p password" option while running Terminal in the GigabyteExpress folder, like so:

prompt: username$ ./gbx -p password <press return key>

Note that the string password is case-sensitive!

Gigabyte Express will not start up the full application when you use this option, it will only generate an encrypted password string and then the program will return to the command line immediately. Suppose you wished to use the password "f4Cko5b9" for encrypted transactions. Usage might look like so:

prompt: username$ ./gbx -p f4Cko5b9 <press return key>
=*=*=*=> PASSWORD [ENC!792ABC9D918C35EB]
prompt: username$

Now simply copy and paste the above ENC! string into the appropriate place in your configuration file. See example immediately below.

IMPORTANT NOTE: It is strongly recommended that you execute the "history -c" and "clear" commands immediately after copying your encrypted password string, so that no record of your original password exists within this Terminal window.

5.6.2 Example of Encryption password creation on local and remote Gigabyte Express machines

Let us suppose that we wished to have an encrypted connection, Dialing from the local machine, Answering on the remote machine, with the username of "Joe" and the password of "word4you".

On the local machine we would run Gigabyte Express with the "-p password" option like so:

root# ./gbx -p word4you
=*=*=*=> PASSWORD [ENC!792ABC9D918C35EB]

On the local machine copy and paste this encrypted password string while creating an entry like this in GBXPHONEBOOK.INI:

[PREFERENCES]
PHONELIST=SomeOtherEntry1;SomeOtherEntry2;JoesEncryptedTCP;
[PHONEBOOK]
JoesEncryptedTCP=[][TCP/IP][184.160.4.108][0.0.0.0][Port=167][NoPenName][Encryption=1][Username=Joe][Password=ENC!792ABC9D918C35EB]

On the remote machine we would similarly run Gigabyte Express with the "-p password" option like so:

root# ./gbx -p word4you
=*=*=*=> PASSWORD [ENC!46944370F39253D6]

On the remote machine copy and paste this encrypted password string while creating an entry like this in GBXPHONEBOOK.INI:

[PREFERENCES]
USERLIST=SomeOtherUser1;SomeOtherUser2;Joe;
[USERS]
Joe=[ENC!46944370F39253D6]

Note that the same password "word4you" created different encrypted password strings on the local and remote machines. This is done by design, so that each encrypted password string is unique to the machine where it was created.

This new PhoneBook entry JoesEncryptedTCP can now be used in a NiwotAutoSendList file with an description like:

"Niwot_outBasket" "Niwot_inBasket" JoesEncryptedTCP        (Please see Autosend immediately below)

6. Autosend Back to Table of Contents

A Minimal Example Auto Send List file

"Niwot_outBasket" "from7demo" niwothqWin
"Niwot_out2Basket" "from7demo" selfTCP
"Niwot_out3Basket" "from7demo" niwothqRED1
"Niwot_out4Basket" "from7demo" selfRED1
END

6.1.   Overview Back to Table of Contents

Autosend is a Gigabyte Express feature which supports ongoing, unattended transmission of files from one or more Dial sessions. The sources and destinations for file transfer are supplied by text-based Autosend List files in the Gigabyte Express folder. Filenames for the list files begin with NiwotAutoSendList. Every file whose first seventeen letters are NiwotAutoSendList and which resides in the same directory from which Gigabyte Express was started is available for use. These list files can contain multiple lines, each of which defines the source folder, destination folder, and Phonebook name used during connection.

Autosend supports a [NoFolder] option, which prevents Autosend from expanding or sending any folders within the source folder. To ignore folders within the source folder put [NoFolder] after the Phonebook name.

The frequency that Autosend polls folders is defined with AUTOEXAMTICK. The frequency that Autosend examines files is defined with AUTOSENDTICK.

6.2. Sent Files Handling Back to Table of Contents

SENTHANDLINGXX options allow you to specify what action to take after files and folders are sucessfully transferred, either USESENT, DELETE, or MOVESELECTED. The default USESENT is to create a source folder_sent at the same level as the source folder, and to move files and folders into it. With DELETE, sent files can simply be deleted. With MOVESELECTED, sent files will be moved to the path specified in AUTOSENDMOVESELECTEDPATHXX, like "AUTOSENDMOVESELECTEDPATH1=/Test/autosent". The LEAVEFOLDERSXX option allows folder structures to remain in place after these various file moves or deletions.

The default USESENT will move files to an _sent folder. If you select this option, Gigabyte Express will, after successfully transferring files from the folder specified in the NiwotAutoSendList (Niwot_outBasket in our example), move those files to another folder on the sending computer. That folder will be at the same level as the source folder, and the name will be generated by appending _sent to the source folder name. PenName folders may be created within that folder, depending on whether Disable PenName was requested by the sender. These folders are created if necessary.

For example, you use Autosend to transfer a file from Niwot_outBasket to a remote computer, your PenName is faststuff, and Disable PenName was not selected. After successful transfer of the file, Gigabyte Express will move the file on your computer from Niwot_outBasket to a folder named faststuff1 within the Niwot_outBasket_sent folder.

6.3. AutoSendList format Back to Table of Contents

[waitspec optional]

[whenspec optional] [GET optional]source folder-1 destination folder-1 phonebook-name-1 [NoFolder optional]

[whenspec optional] [GET optional]source folder-2 destination folder-2 phonebook-name-2 [NoFolder optional]

:

:

[whenspec optional] [GET optional]source folder-n destination folder-n phonebook-name-n [NoFolder optional]

END

The source folders and destination folders are enclosed in double-quotes. These can supply a full drive and path specification, or a simple folder name. If a full path is not specified, the folders are treated as relative to the Gigabyte Express folder. Full paths can be entered as:

/directory1/directory2 (and for Windows destinations: drive-letter:\path\folder \\computer\share\path\folder \\server\volume\path\folder)

Source folders must exist to the folder level (\folder in the examples). Wildcards are supported. The question mark (?) wildcard can be used to represent any single character, and the asterisk (*) wildcard can be used to represent any character or group of characters that might match that position in other filenames.

Destination folders must exist to the path level (\path in the examples). The specified folder, and possibly a Penname folder within it, will be created if necessary at the destination side. The destination string is limited to 60 characters.

The Autosend List must end with END.

6.3.1. WAIT and WHEN in NiwotAutoSendList Back to Table of Contents


Autosend now has a WAIT/WHEN feature for the NiwotAutoSendList script.These features are used to schedule the starting of a NiwotAutoSendList script file (the WAIT command) or the sending of files in a specific "hot-folder" (the WHEN command). Both commands have the same format, but each is used in a different way. WAIT is placed at the top of the NiwotAutoSendFile (the first line of script), and is used to schedule when Autosend can access the "hot-folder" script lines below. The WHEN command is used at the beginning of a "hot-folder" script line,and is used to schedule when files in the specified "hot-folder" can be sent.

Format:
This is StartTime
This is either Duration or EndTime
WAIT hh:mmx yhh:mmx
hh - is hours (24hr time if no x)
mm - is minutes
x - is 'A'(am), 'P'(pm), or not used
Note: If x is not used, hh becomes 24hr time.
y - is either 'd' or 'D'(duration), or not used
Note: If y is not used, the hh:mmx that follows is then considered an EndTime.

Examples:
WAIT 2:00a 6:00p
WHEN 2:01a d0:45 "toCustomerOne" "fromNiwot" "PhoneBookEntry1"
WHEN 3:00 13:45 "toCustomerTwo" "fromNiwot" "PhoneBookEntry2"
WHEN 14:00 d2:00 "toCustomerThree" "fromNiwot" "PhoneBookEntry3"

Explanation of examples:
Line 1 - WAIT until 2:00am to start Autosend and stop at 6:00pm.
Line 2 - WHEN it is 2:01am, send all items in the "toCustomerOne"
hot-folder to the phonebook entry "PhoneBookEntry1", and place these items into a folder at the destination called "fromNiwot".
Stop sending newly placed items from "toCustomerOne" hot-folder after 45 minutes.
Line 3 - WHEN it is 3:00 (24hr time), send all items in the "toCustomerTwo" hot-folder to the phonebook entry
"PhoneBookEntry2", and place these items into a folder at the destination called "fromNiwot".
Stop sending newly placed items from "toCustomerTwo" hot-folder at 13:45 (24hr time).
Line 4 - WHEN it is 14:00 (24hr time), send all items in the "toCustomerThree" hot-folder to the phonebook entry "PhoneBookEntry3", and place these items into a folder at the destination called "fromNiwot".
Stop sending newly placed items from "toCustomerThree" hot-folder after 2 hours.

NOTE: WHEN commands will not execute if the AutoSendList is disabled by a WAIT command.

6.3.2. GET in NiwotAutoSendList (Autoget) Back to Table of Contents

The Autoget feature includes support of an optional GET in each line of the AutoSendList and Answer session control of the Handling of files that have been retrieved using Autoget. Each line in the NiwotAutoSendList may have GET after the whenspec(if it exists) and the before the source folder specification. If GET is used, the source folder spec is as it appears to the remote ends Gigabyte Express answer session, and destination folder spec is as it appears to the local Gigabyte Express.


6.3.3. [NoFolder] in NiwotAutoSendList Back to Table of Contents


Each line in the NiwotAutoSendList may have the [NoFolder] option after the Phonebook name. Folders within the source folder will be ignored with this option. See above example. Only files will be sent, not folders.

6.3.4. Source folder Back to Table of Contents


The source folder is enclosed in double-quotes. The contents can be a full path specification, or a simple folder name. If a full path is not specified, the folders are treated as relative to the Gigabyte Express folder. Full paths can be entered as:

/directory1/directory2

Wildcards are supported such as:
/directory1/directory2/*.ZIP

The total number of characters should not exceed 55.

6.3.5. Destination folder Back to Table of Contents


The destination folder is enclosed in double-quotes. The contents can be a full drive and path specification, or a simple folder name. If a full path is not specified, the folders are treated as relative to the Gigabyte Express folder. Full paths can be entered as:

/directory1/directory2

Windows full paths can be entered as:

drive-letter:\path\folder
\\computer\share\path\folder
\\server\volume\path\folder


These can supply a full drive and path specification, or a simple folder name. If a full path is not specified, the folders are treated as relative to the Gigabyte Express folder.

Destination folders must exist to the path level (\path in the examples). The specified folder, and possibly a Penname folder within it, will be created if necessary at the destination side. The destination string is limited to 55 characters.

6.3.6. Working with remote volumes Back to Table of Contents

Gigabyte Express supports remote(non-local) mounted volumes, either found through browsing with the Finder -> Network icon or Go menu -> Connect to Server.

Once a remote volume is mounted, you may define an Autosend entry in one of your NiwotAutoSendList files to send from your mounted volume:

"/Volumes/VOLUMENAME/folder1" "C:\incoming\client1" server1TCP

where VOLUMENAME is the name that you see in the Finder for the mounted volume. For example, if the mounted volume's name was "Jeffrey", then the above Autosend specification would look like so:

"/Volumes/Jeffrey/folder1" "C:\incoming\client1" server1TCP

A retrieve into a mounted volume may be performed with an Autoget:

GET "C:\incoming\client1" "/Volumes/Jeffrey/folder1" server1TCP


6.3.7. Gigabyte Express phonebook name Back to Table of Contents


The Gigabyte Express phonebook name is used for the selection of transport, IP address, and such as controlled by the Gigabyte Express phonebook file GBXPHONEBOOK.INI.

6.3.8. Options Back to Table of Contents


The only option currently supported is [NoFolder].

Our customers use [NoFolder] to keep Autosend from sending folders found within the source folder.

NOTE: This option is case-sensitive

6.3.9. Example Back to Table of Contents


The sample file we include with the installer is NiwotAutoSendList.txt:

"Niwot_outBasket" "from7demo" niwothqWin
"Niwot_out2Basket" "from7demo" selfTCP
"Niwot_out3Basket" "from7demo" niwothqRED1
"Niwot_out4Basket" "from7demo" selfRED1
END

The first line will cause all files and folders in the folder Niwot_outBasket to be sent using the phone book entry with the name niwothqWin. The files will be placed in a pen name folder in the folder from7demo in the GBXWin folder at the destination.

The second line will cause all files and folders in the folder Niwot_out2Basket to be sent using the phone book entry selfTCP.

The third line will cause all files and folders in the folder Niwot_out3Basket to be sent to niwothqRED1 using RELIA.

The fourth line will cause all files and folders in the folder Niwot_out4Basket to be sent to the same machine using RELIA.


7. Configuration Setting Definitions


Global Answer session settings

• ALLOWASPATHING -- Allow Autosend Pathing (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI applies to all Answer sessions. The default is ALLOWASPATHING=0, to not allow Autosend Pathing. If this setting is ALLOWASPATHING=1, and a remote sender is running Autosend with destination folders specified, files and folders are placed into the specifed destination if it can be found. If it cannot be found the actual destination is reported in the gbxmac.log Log File.

• ANSWERENCRYPTION -- Encryption setting (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI applies to all Answer sessions. The default of ANSWERENCRYPTION=1 is to support encryption. If this setting is ANSWERENCRYPTION=0, meaning "Disable Encryption", then Dial sessions requiring encryption will not be able to connect to this Gigabyte Express machine.

If this setting is ANSWERENCRYPTION=1, meaning, "Support Encryption", Dial sessions requiring or using encryption will be able to connect to this Gigabyte Express machine (assuming their username and password match an authorized username and password) and use encryption. Dial sessions with encryption disabled or dial sessions from versions of Gigabyte Express not supporting encryption will still be able to connect.

If this setting is ANSWERENCRYPTION=2, meaning Require Encryption, Dial sessions requiring encryption will be able to connect to this Gigabyte Express machine. Dial sessions using encryption will connect (assuming their username and password match an authorized username and password) and use encryption. Dial sessions with encryption disabled or dial sessions from versions of Gigabyte Express not supporting encryption will not be able to connect.

• AUTOGETSENTHANDLING -- Handling of Files After Autoget (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI allows you to define the manner in which files sent via incoming Autoget are handled for all Answer sessions. Currently the options for this setting are:
USESENT    Move files to an "_sent" folder after incoming Autoget (default behavior)
DELETE    Delete files after incoming Autoget
MOVESELECTED    Move files to AUTOGETMOVESELECTEDPATH (see below) after incoming Autoget

• AUTOGETLEAVEFOLDERS -- Leave Folder Structure in Place (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI allows folder structures to remain in place after files sent via incoming Autoget have been moved or deleted, for all Answer sessions:
0    Delete folder structure after sending files (default behavior)
1    Do not delete folder structure

• AUTOGETMOVESELECTEDPATH -- Files Moved Here After Autoget (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI allows you to choose the folder into which files are transferred after incoming Autoget, if AUTOGETSENTHANDLING=MOVESELECTED (see above). Example: "AUTOGETMOVESELECTEDPATH=/SentFiles/autoget" ... for all Answer sessions, this would move all files sent via incoming Autoget to "/SentFiles/autoget".

• INBASKET -- The InBasket (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI allows you to choose the folder into which files are transferred from a remote user. The default InBasket for all sessions is Niwot_inBasket in the same folder as Gigabyte Express. All Answer windows share a common InBasket. Example: INBASKET=/MyGBXInBasket

• OUTBASKET -- The OutBasket (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI allows you to choose what folder a remote user can access to get files. The OutBasket does not need to be in the Gigabyte Express folder. Some users have their OutBasket on their server. The default OutBasket is Niwot_outBasket in the same folder as Gigabyte Express. The remote user will also be able to get files/folders from an OutBasket which matches their PenName. PenName OutBaskets must be in the same folder as Gigabyte Express. Example: OUTBASKET=/MyGBXOutBasket

Specific Answer session settings

• SESSIONSANSWER -- Number of Answer sessions (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows you to define the number of Answer sessions. Your serial number may enable more or less TCP Answer sessions. Example: SESSIONSANSWER=2

• ANSADDRXX -- Answer IP Address (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows you to define the Answer session IP Address, where XX is a specific numbered Answer session. The default Answer IP Address setting is ANSADDR1=0.0.0.0 (for Answer session #1). Note that if your machine is multi-homed (having more than one IP address) then you may wish to put in a particular IP address to force it to be used.

• TRANSPORTXX -- Transport Type (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows you to define the Answer session Transport type, where XX is a specific numbered Answer session. The default settings could be something like TRANSPORT1=TCP and TRANSPORT2=RELIA (Answer session #1 listening for incoming TCP connections, Answer session #2 listening for incoming RELIA connections)

• ANSPORTXX -- Answer Port (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows you to define the Answer Port for an Answer session, where XX is a specific numbered Answer session. The default settings could be something like ANSPORT1=32779 and ANSPORT2=32778 (Answer session #1 listening for incoming TCP connections on Port 32779, Answer session #2 listening for incoming RELIA connections on Port 32778)

Global Dial session settings

• AUTOEXAMTICK -- Poll Folders Every xxx Seconds (Dial session Global) Back to Table of Contents
This setting is defined in the GBXMAC.INI file. The Autosend function will continue to check the specified folders, moving from line to line at the interval specified in seconds. If there are files in the folders, they will be transferred to the destination corresponding to the IP address. The default setting is AUTOEXAMTICK=30 (seconds). Minimum is 1 second.

• AUTOSENDTICK -- Examine Files Every yyy Seconds (Dial session Global) Back to Table of Contents
This setting is defined in the GBXMAC.INI file. Specifies how long Autosend will wait between successive file examinations. The default is AUTOSENDTICK=30 (seconds). Minimum is 1 second.

• LRCVERIFY -- Read After Write Integrity Check (Dial session Global)
This setting is defined in the GBXMAC.INI file. Enabling this with LRCVERIFY=1 adds an extra read after write longitudinal redundancy file integrity check at the destination. The default setting LRCVERIFY=0 will not perform the check.

Specific Dial session settings

• SESSIONSDIAL -- Number of Dial sessions (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows you to define the number of Dial sessions. Your serial number may enable more or less Dial sessions. Example: SESSIONSDIAL=1

• AUTOLISTXX -- The Autosend List file (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows you to define the Autosend List file for a specific numbered Dial session. Filenames for the list files begin with NiwotAutoSendList. For example, with Dial session #1 you could define AUTOLIST1=NiwotAutoSendList1.txt and with Dial session #2 you could define AUTOLIST2=NiwotAutoSendList2.txt

• SENTHANDLINGXX -- Handling of Files After Autosend (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows you to define the manner in which Sent Files are handled for a specific numbered Dial session. Currently the options for this setting are:
USESENT    Move files to an "_sent" folder after send (default behavior)
DELETE    Delete files after send
MOVESELECTED    Move files to AUTOSENDMOVESELECTEDPATHXX (see below) after send
For example, with Dial session #1 you could define SENTHANDLING1=USESENT and with Dial session #2 you could define SENTHANDLING2=DELETE
Click here for examples of Sent File Handling in the larger context of Autosend.

• LEAVEFOLDERSXX -- Leave Folder Structure in Place (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows folder structures to remain in place after the Sent files have been moved or deleted, for a specific numbered Dial session:
0    Delete folder structure after sending files (default behavior)
1    Do not delete folder structure
For example, with Dial session #1 you could define LEAVEFOLDERS1=0 and with Dial session #2 you could define LEAVEFOLDERS2=1

• AUTOSENDMOVESELECTEDPATHXX -- Files Moved Here After Autosend (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows you to choose the folder into which files are transferred after Autosend, if SENTHANDLINGXX=MOVESELECTED (see above). Example: "AUTOSENDMOVESELECTEDPATH1=/SentFiles/autosend" ... for Dial session #1 only, this would move all files sent via Autosend to "/SentFiles/autosend".

• OPTIONSDIALXX -- Operational Mode (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows you to choose the operational mode in which a Dial session runs, either Manual Send or Autosend.
Examples:
OPTIONSDIAL1=MANUAL  Dial session #1 runs as Manual Send
OPTIONSDIAL2=AUTOSEND  Dial session #2 runs as Autosend
Note: This setting is normally configured via the UI here.

• PHONEBOOKXX -- PhoneBook entry (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI allows you to choose the PhoneBook entry that will be used by a Dial session when running in Manual Send mode.
Example:
PHONEBOOK1=niwothqWin    (Use the "niwothqWin" PhoneBook entry when Sending/Getting files with Dial session #1)

Global settings for both Answer and Dial sessions

• ANSWSECOND -- The Answer session Data Transfer Port (Answer session Specific)
Defined in GBXMAC.INI, the default Answer session Data Transfer Port setting is ANSWSECOND=32780, so Answer session #1 will use port 32780, Answer session #2 will use 32781, and so on. User may specify the secondary port numbers by modifying this value. A value of 0 or deleting this parameter will cause the ephemeral ports to be used.


• DISPENNAME -- Allow PenName Disabling (Answer session Global) Back to Table of Contents
This setting is defined in the GBXMAC.INI file. The default setting is DISPENNAME=0 to not allow PenName disabling. Set this value to DISPENNAME=1 to allow PenName disabling. If you select this option, and if the sender has chosen to disable the PenName, files and folders will be placed directly in your InBasket without a PenName. Both the sender and receiver must request the no pen name in their respective ways for this to occur. CAUTION: With this option, over-writing of a duplicate file can occur. If the Sender does not disable the PenName, or if the Receiver does not choose the Allow PenName Disabling option, all incoming files will be put into correct PenName folders.

• LOGACCT -- The gbxacct.log Accounting Log File Back to Table of Contents
This setting is defined in the GBXMAC.INI file. The default is LOGACCT=0 to not write the gbxacct.log Accounting Log File. This file maintains a record of the files transferred for accounting purposes. Enable the writing of this file by using LOGACCT=1 for this setting. When you choose to generate a gbxacct.log, it contains one line for every file successfully transferred. The file is organized to allow importing by spreadsheet programs to capture file transfer information for billing purposes. When the file is approximately 5 megabytes, it is copied to gbxacct1.log (after gbxacct1.log is copied to gbxacct2.log). Also see the LOGACCTFOLDER setting immediately below.

Each line of the gbxacct.Accounting Log File has the format:

Date>StartTime>FinishTime>Session ID>FileName>Size>OtherSide ID

The Session ID gives the session number and the direction of the transfer. A Dial session may receive R(Get) or send S. An Answer session may receive R or send S(in response to a Get))

The OtherSide for an Answer Session has the format PenName: xxxx where xxxx is the Other sides PenName. For a Dial session, the OtherSide has the format PhoneBook: xxxx where xxxx is the name of the PhoneBook entry.

• LOGACCTFOLDER -- Folder to write Accounting Log File Back to Table of Contents
This setting is defined in the GBXMAC.INI file. The default is to leave this field blank. If the setting LOGACCT=1 is defined, the gbxacct.log Accounting Log File will be written to the folder where Gigabyte Express is installed. If the LOGACCTFOLDER setting is also defined it will be used, i.e. LOGACCTFOLDER=/Test then the Accounting Log File will be written to /Test/gbxacct.log

• LOGFILE -- The gbxmac.log Log File Back to Table of Contents
This setting is defined in the GBXMAC.INI file. The default setting of LOGFILE=1 is recommended so that a record is kept of the operation of the program, start-up, sending/receiving files, etc. This file will always be written to the folder where Gigabyte Express is installed. Gigabyte Express operations from ALL sessions will be logged here. When the file is approximately 5 megabytes, it is copied to gbxmac1.log (after gbxmac1.log is copied to gbxmac2.log). If desired you may disable writing of the Log File with LOGFILE=0

• MACSUPPORT -- Macintosh file support for LINUX ONLY Back to Table of Contents
Gigabyte Express for Linux may gracefully send and receive Macintosh files when communicating with Gigabyte Express for Mac OS X or Gigabyte Express for Windows (if MACSUPPORT is also enabled on the Windows machine). Users desiring this functionality should set MACSUPPORT=1 in the GBXLIN.INI file. This option should be disabled with MACSUPPORT=0 for non Macintosh-only file operation as it slows down the cataloging of files to be sent.

• PENNAME -- The PenName
Back to Table of Contents
This setting is defined in the GBXMAC.INI file. The PenName is used to name the folder on the receiving computer which will contain the files and folders you have sent. For example, lets use the setting PENNAME=Jack ... The first batch of files/folders you send will be placed in the folder Jack1. The second batch of files/folders you send will be placed in the folder Jack2, and so forth. The PenName number will increment unless you delete a pen name folder, then it will replace the deleted folder so the numbers remain consecutive.

• SERIALNUM -- The Serial Number Back to Table of Contents
This setting in GBXMAC.INI is where you may view or change your serial number. Gigabyte Express will not execute without a correct serial number / validation code pair.
Demo serial numbers are: SERIALNUM=niwotdemo1 or SERIALNUM=niwotdemo2 or SERIALNUM=niwotdemo3

• SORTTYPE -- The File Sorting algorithm used (Answer/Dial session Global)
If SORTTYPE=1 or if SORTTYPE is not found in the GBXMAC.INI file then oldest files will be sent first. If SORTTYPE=0 then files will be sent in the order they are found.

• VALIDATIONCODE -- The Validation Code Back to Table of Contents
This setting in GBXMAC.INI is where you may view or change your validation code. Gigabyte Express will not execute without a correct serial number / validation code pair.
Demo validation code should be left blank: VALIDATIONCODE=

• WATCHDOG -- The Watchdog Timeout, in minutes Back to Table of Contents
The WatchDog timer is used to monitor file transfer action between connected computers. If there is no file transfer action within the set WatchDog time, the link between computers will be terminated. The default WatchDog time setting is WATCHDOG=3 (minutes). Edit the GBXMAC.INI file to define the WatchDog time you would like in minutes. WATCHDOG=0 (zero) indicates unlimited time. With WATCHDOG=0, the link may stay up indefinitely creating high long distance bills.

8. ERRORS Back to Table of Contents


8.1. Error Messages Reported by Gigabyte Express Back to Table of Contents

The error code can be either a general system or socket error code.

Autosend Folder Does Not Exist

Auto-Send not supported by remote

Bad connection state=

Bad file send list format

Command confirm failed with

Connect confirm send failed with

connect request failed with

Connect request fail code =

Connect retry in x secs

Compress Block Error =

Compressor Initialize error =

Connection error waiting for ack

Connection request timed out

Decompress Block Error =

Decompressor Initialize error =

Disconnect confirm failed with

Disconnect listen failed with

Disconnect request failed with

Disk file write error =

Duplicate Serial# detected

Error Creating File (RC=)

Error Creating File on Remote

File command not sent in entirety

File command send failed

File confirm failed with

File Not Found

File Open, Not Sent

File Open Failure =

File read error: OS error:

Get File not supported by remote

Get Folder not supported by remote

Incoming connect request failed with

Incoming connection request timed out

init command read error:

Link has failed unexpectedly!

Link Watchdog has expired

Listen failed with

Local Hard Drive Full

No Dial String is Specified

No File Opened on Remote

No Filename chosen

No valid wait time defined in auto-send file

Non-printable character detected in list file

Not enough receive side disk space

Read After Write Fail, Terminating connection

Read data failed with

Receive Side Setup Err = cmdRes

Received data larger than expected

Received data length greater than expected

Sorry, Autosending on Remote

System Error

Transfer File Not Selected

writeNet failed with

8.2. Gigabyte Express Transport Layer Messages Back to Table of Contents

The error code will be a socket error code.

closesocket failed:

Connect: socket failed:

Connect: setsockopt(

Copyright 1995-2009, Niwot Networks, Inc. All Rights Reserved
Gigabyte Express, You've Got Files!, and RELIA are trademarks of Niwot Networks, Inc.