BeamUp V1.1.0 (R4 release)


(c) by Patrick van Beem 1997, 1998

Documentation: 1 novembre 1998


Introduction



Configuring BeamUp


Adresses The node numbers of your system, separated by spaces. The numbers are in general Fido format. For example: 2:280/464.2 This is a mandatory field.
System name The name of your system. Optional. This field will only be showed on the host system.
System city The city where your system is located. Optional. This field will only be showed on the host system.
Sysop phone Your phone-number. Enter -Unpublished- if you don't want others to know your phone-number. This field will only be showed on the host system.
Sysop name Your name. Also optional, also only showed on the remote system.
Dial numbers The phone-numbers of your boll, separated by a space. These numbers will be dialed sequentially and repeatedly until a connection is established (or one of the other conditions is met).
Dial timeout Time in secs. given to the modem to establish a connection after the dial command for that number has been sent.
Dial delay Time in secs. between two repeated sequences of dialing the phone numbers.
# retries Number of repeated dial sequences befor giving up ever establishing a connection.
Device The device to use for the connection.
Inbound The directory to use for the incomming files. The directory must exist! It's NOT being created for you. /boot/usr/mail/inbound is recommended.
Outbound The directory where the outgoing files can be found. The directory must exist! /boot/usr/mail/outbound is recommended.
Logfile The logfile to use. If not specified, no log is kept.
Log level The level of information to log. Varying from -2 (nothing) to 2 ('debug' information).
Baud rate The baud-rate at which the device is set.
Dial prefix Prefix to add before any number to dial.
Modem reset Modem command string used to initialize the modem before each dial command.
Password Optional password used on the host system. Ask your sysop.
Seven-wire If checked, a full 7-wire modem-cable is assumed and hardware handshake is enabled.
Nullmodem When checked, the normal dialler is skiped and it's options are ignored. Instead, when a poll starts, the program waits a little time, sends the string OK, waits a little time, sends the string RING, waits a little time, sends the string CONNECT 14400 and then starts the session. This ought to be enough to fool a receiving communication program in thinking it's actually talking to a modem. Works for me with TrapDoor on my Amiga computer.


Using Beam



Supported file-extensions


OUT Normal mail. Send to the host as nnnnnnnn.PKT file. Deleted after sent.
Example: 2.280.464.0.OUT
CUT Continues mail. Send to the host as nnnnnnnn.PKT file. Deleted after sent.
Example: 2.280.464.0.CUT
DUT Direct mail. Send to the host as nnnnnnnn.PKT file. Deleted after sent.
Example: 2.280.464.0.DUT
REQ Filerequest. Send to the host as nnnnnnnn.REQ file. Deleted after sent.
Example: 2.280.464.0.REQ
FLO List file. The given file is read line by line. Each line is interpreted as being a file (with an optional path). The file is being send. If the filename looks like a node number, it's converted to nnnnnnnn, with the original file-extension. For example, 2.280.464.0.SU0 will be sent as 32474DE7.SU0. The first character of each line may be a special character:
# = the file will be made empty after sent.
^ = the file will be deleted after sent, which will be recorded in the logfile.
- = the file will be deleted after sent.
~ = the file will not be processed.
The .FLO file is deleted after all of its listed files are sent.
Example: 2.280.464.0.FLO
CLO Will be treated the same as a .FLO file.
Example: 2.280.464.0.CLO
DLO Will be treated the same as a .FLO file.
Example: 2.280.464.0.DLO


Known bugs



The author and (c)



BeamUp is written by Patrick (K.P.) van Beem