Short:        Send alpha-numeric pages to beepers
Architecture: m68k-amigaos

WHAT IT DOES
============

The CyberPager software allows one to send alpha-numeric pages from one's
Amiga.  This is accomplished by dialing into an IXO protocol compliant
pager central and uploading messages.

FEATURES
========

o   Aliases file allows for commonly paged people to be refered to by
    name rather than having to remember cryptic PIN numbers.

o   Groups file allows one to create "groups" allowing messages to
    be easily sent to many people working on the same project, in the
    same department, etc.

o   Supports multiple pager centrals through a Services configuration
    file.

o   Any number of messages can be spooled to disk to be uploaded in
    a single call to a service.

o   Automatically breaks long messages up into seperate pages.  Individual
    preferences for maximum message length can be set for each account
    listed in the aliases file.

o   Dialer supports multiple modems and knows how to hunt down a free
    modem in priority order.

o   Full logging of messages spooled, dialout attempts, etc.

o   Supports the OwnDevUnit.library method of locking serial devices,
    making the dialer compatible with mith Amiga UUCP, Welmat, and
    many major Amiga terminal programs.

SYSTEM REQUIREMENTS
===================

Any Amiga running AmigaDOS 2.0 or higher.
A Hayes compatible modem.
OwnDevUnit.library v2.1 or higher must be installed (v3.3 is included
    with this distribution for those that don't already have ODU)

Highly recommended:
	A hard drive
	A cron program (job scheduler) of some sort, such as CyberCron.

HISTORY
=======

1.0
	Initial release

1.1	(7/10/93, SpoolPage v0.136, DialIXO v0.219, library v1.23)
	A bug in the checksum generator manifested itself when talking
	to services which are more strict about the IXO protocol.
	Many IXO services accept a space instead of a zero in the checksum.
	Some, like SkyTell, appear not to.  DialIXO now uses zeros per
	the IXO spec as written by Motorolla.

	Added a loglevel 4 entry to DialIXO that causes it to log the
	exact packet being sent to the service when uploading each
	page.

	Added a routine to intelligently add characters to the safe
	buffer (i.e., non-printable characters converted to escaped
	hex, etc, for display purposes).  DialIXO know displays
	special characters of the IXO protocol, such as ACK, NAK, STX,
	etc., as text rather than hex escape sequences to make
	tracing loglevel 5 output easier.

1.2	(7/20/93, SpoolPage v0.136, DialIXO v0.220, library v1.23)
	Found a bug that affected people running KickStart V37.  The
	wildcard mask DialIXO used to look for spool files would not
	find any that had a letter in them (i.e., 00000a as opposed
	to 000009 which would work).  This was due to the mask having
	the alpha range specified in lowercase.  V37 has a bug that
	doesn't uppercase alphabetic letters when a case-insensitive
	compare is being made.  By changing the mask to specify the
	alphabetics in uppercase, things now work properly on V37
	machines.  Thanks to Nickey MacDonald <i6t4@jupiter.sun.csd.unb.ca>
	for reporting this problem.

1.3
	Greg Peck had a problem with the 1stPage service where it was
	sending out messages before ACKing the page (which the service
	is not supposed to do).  CyberPager would report an "unknown
	packet" and resend the page.  It would then see the ACK from
	the previous page.  The end result was that he was getting
	each page twice.  CyberPager no-longer resends the page on
	unknown packets, but rather continues to look for an ACK or NAK
	from the service.  Related to this, I changed the log level
	of the "unknown packet" message to 2 (which is the same level
	as the "saw NAK, retrying" message) so that people in Greg's
	position wouldn't have their logfile explode due to the
	unknown packet messages being dumped into it for every page.

1.4
	(2/7/94, SpoolPage v0.140, DialIXO v0.226, library v1.26)
	David Varley reported that his makes use of the password
	specification at login time.  This is the first time I heard
	of any system actually making use of this, rather than always
	using the default '1000000'.  I have modified the system to
	have a password field in the services file.

	For most systems, simply specifying "1000000" should suffice.

	Note:  this change requires that you modify your services file
	to include a password field for each service, even if it is
	just "1000000".

1.5
	(10/5/94, SpoolPage v0.144, DialIXO v0.230, library v1.27)
	Added Use8N1 field to services configuration file.  The IXO
	protocol specification indicates that all IXO TAPs should use
	7E1.  Some newer services are now using 8N1, however.  By
	setting this flag to "y", DialIXO will dial the service in
	8N1 mode, instead of the default 7E1 mode.

	Note:  this change requires that you modify your services file
	to include a Use8N1 field for each service.  For most services,
	you should simply specify "n" to continue to use 7E1.