home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 3 Comm
/
03-Comm.zip
/
hab4_d1.zip
/
HAOS2D.Z
/
README.TXT
< prev
next >
Wrap
Text File
|
1995-09-08
|
32KB
|
849 lines
---------------------------------------------------------------------
HyperACCESS for OS/2 Version 6.0 Final Beta README File
---------------------------------------------------------------------
README.TXT Contents
===================
o Disclaimer
o Installation
o Reporting Bugs
o Contacting Hilgraeve
o Ray Gwinn's SIO Drivers
What is SIO?
Distribution, Ordering and Support
Installing SIO/VSIO
o Using VMODEM
o HyperACCESS Host Commands
o On-line API Documentation
o Queued Calling
o Setting Up HyperACCESS for OS/2 on a Network
o Upgrading From Other Communications Products
o Lists, Upload and Download Directories
o List Contents
o Running Non-API Programs from HyperACCESS
o Weather Report and Split-Second Utilities
o Uninstalling HyperACCESS
o Manual Errata
o Installed Files
----------
Disclaimer
----------
This free trial copy of HyperACCESS for OS/2 will stop working
on:
November 1, 1995.
Feel free to use and distribute this fully functional, free beta
copy of HyperACCESS for OS/2. HyperACCESS for OS/2 is an
exciting new program from the makers of the top-selling OS/2
communications program HyperACCESS/5, and HyperACCESS Lite in the
BonusPak bundled with OS/2 Warp. We want you to see what's
coming from us, and welcome your feedback!
Though nearly complete, this beta still has some bugs. You can
help us by reporting any problems you encounter that are not
already listed later in this file. We will only respond if we
need more information. As with any beta software, Hilgraeve
assumes no risk of potential loss or damage to data arising from
use of this beta software.
------------
Installation
------------
Follow these steps to install HyperACCESS for OS/2:
If you received HyperACCESS v6.0 as zipped files:
HyperACCESS v6.0 Beta #3 is provided as two zipped, named
HAB4_D1.ZIP and HAB4_D2.ZIP, which are files containing the
HyperACCESS installation files in a compressed format. You must
have both files in order to install Hyper- ACCESS. You will need
to uncompress these files to generate the files necessary to
install and run HyperACCESS. Here's the procedure:
NOTE: You will need the uncompression utility PKUNZIP.EXE
version 1.01 or later to unzip these files. This utility
is available on nearly all on-line services.
1. Open an OS/2 window, and change to the drive and/or directory
containing the downloaded files.
2. Type PKUNZIP HAB4_D1 <destination>, and then press ENTER.
Replace <destination> with the drive and/or directory where
you want the HyperACCESS files to be copied. We recommend
that the destination be a floppy drive containing a blank,
formatted 1.2M or 1.44M diskette. That way, you can use this
diskette to install HyperACCESS on each of the PCs that you
use for testing HyperACCESS.
Example: PKUNZIP HAB4_D1 A:
3. Repeat step 2 for the file HAB4_D2.ZIP. If uncompressing
these files to floppy disks, make sure that you label them as
DISK1 and DISK2.
4. Once the installation files have been created continue with
the steps below.
HyperACCESS Installation PHASE I
================================
1. Change to the drive/directory containing the HyperACCESS
installation files.
2. Type SETUP.
3. Specify the directories for the Program and Data files. These
may be the same location or different location depending on
your preferences. Click OK to continue.
NOTE: Program files may be installed to a directory that is
set to read-only after installation and may be shared
with other users. Data files must be in a writable
directory and should not be shared.
4. Click Continue after reading the next status message.
HyperACCESS's files will be copied to the specified
directories.
5. Change the floppy disk to disk #2 or specify the directory in
which the disk2 files are located when prompted. Click OK to
continue.
6. Click Continue after reading the next status message to begin
Phase II of the installation.
PHASE II
========
1. Enter all user information. Click Continue when finished.
2. Select the type of connection you will most often use. Click
OK to continue.
3. If you chose "Modem or Modem Pool" as your connection type,
select an appropriate modem from the selection list. Click OK
to continue.
4. Select the interface to connect through. Then select the COM
port you will use most often. Click OK to continue.
5. If you chose "Modem or Modem Pool" as your connection type,
select the dialing method your phone system uses. Click OK to
continue.
6. If you chose "Modem or Modem Pool" as your connection type,
enter a dialing prefix if your phone system requires one
(such as '9' to get an outside line). Otherwise, leave this
field blank. Click OK to continue.
7. Specify your default download and upload directories. If
you leave these field blank, whichever directory is
currently selected at the time of the transfer will be used.
Click OK to continue.
8. Click OK after reading final status message.
9. Reboot machine so that changes made may take effect.
You are now ready to run HyperACCESS for OS/2.
--------------
Reporting Bugs
--------------
Please include the build number in all bug reports. The build
number may be found by selecting Help, then Product Information
from any HyperACCESS panel. This will help us to identify which
bugs are associated with a particular build. It will also allow
you to identify if you have the most recent version of the
software.
When you report bugs, please try to provide enough detail so that
Hilgraeve will be able to reproduce the problem. It is much more
useful to hear "when I do this, then this, then this, the program
misbehaves in this way," than to hear that something "doesn't
work right." Keep in mind that too much information is much
better than not enough.
We will not guarantee a respond. However, if more information is
needed to reproduce or resolve a problem with the software we
will contact you. Please do not report bugs by phone.
Remember that we're looking for more than just bug reports; we
also want to know what you think. So please give us your
comments and opinions, and let us know what additional features
you would like to see in future versions. We would also love to
receive a detailed account of how you use HyperACCESS in your
particular field of business. We might even want to share your
experiences in articles, reviews, or advertisements (with your
prior approval, of course).
--------------------
Contacting Hilgraeve
--------------------
Hilgraeve may be contacted through the following means:
Hilgraeve Inc.
111 Conant Ave.
Suite A
Monroe, MI 48161
Customer Support: 313-243-0576
FAX: 313-243-0645
BBS: 313-243-5915
Sales: 800-826-2760 or 313-243-0576
Compuserve: Go Hilgraeve
Internet: support@hilgraeve.com
sales@hilgraeve.com
http://www.hilgraeve.com
gopher.hilgraeve.com:9005
ftp.hilgraeve.com
America On-line: Hilgraeve at America On-line
--------------
Queued Calling
--------------
HyperACCESS has a feature called queued dialing, which dials
multiple phonebook entries, one after the other. When it
connects with any entry, it drops that entry from the queue.
After it has tried all entries once, it tries those again which
it was unable to connect with on the first attempt. It continues
cycling through the queue until it connects with every entry, or
exhausts the number of dialing attempts specified in that entry's
Dialing Details dialog.
To use queued dialing, simply mark multiple entries in the
phonebook, and then instruct the program to connect (select
Connect from the File or context menu; hit the dial button; or
drag the highlighted entries to the Terminal tab). A dialog
confirms that queued calling is beginning, then proceeds with the
first call after 5 seconds.
NOTE: Double-clicking on a group of selected entries deselects
the group and dials the entry which you double-clicked.
Each time a call connects, you are free to interact with that
system as you would during any other call to that system. Upon
concluding the call (when you disconnect), a dialog pops up for 5
seconds, summarizing the number of queued calls completed and
remaining. Select Cancel in this dialog if you wish to cancel
the remaining queued calls.
NOTE: If you select Cancel from the Connect dialog that appears
during dialing, only the call to that entry is canceled;
queued calling to the remaining entries continues.
Because most users prefer to complete all queued calls prior to
calling other phonebook entries, the dialog that appears between
queued calls is modal, and prevents placing other calls.
However, if you want to place other calls during queued calling,
you can. Simply return to the phonebook and initiate the call
while you are still connected with one of the queued entries.
When asked "Do you want to disconnect?" answer Yes; the call
will then be placed. Queued calls resume when you disconnect
from that entry.
-------------------------
HyperACCESS Host Commands
-------------------------
HyperACCESS contains a powerful Host mode--a miniature BBS--
which you can use to let other PC users connect with your PC.
While connected, callers can type a variety of commands to
interact with or control your PC's Host mode. For information on
those commands, and on Host customization options available to
you as the Host operator, please see the file HOSTHELP.TXT,
located in your DATA directory.
------------------------
On-line API Documentation
------------------------
HyperACCESS provides many API functions that you may use to
automate your favorite on-line activities. While REXX is
HyperACCESS's main scripting language, you may access these API
functions through C, C++, or any other language that can make
external API calls. For more information and examples of the API
functions, please see the file APIHELP.TXT, located in your DATA
directory.
-----------------------
Ray Gwinn's SIO Drivers
-----------------------
HyperACCESS for OS/2 comes with a copy of Ray Gwinn's renowned
SIO shareware communications drivers. Ray's drivers have become
extremely popular among OS/2 users, because they support speeds
up to 115,200bps (standard OS/2 Warp drivers limit you to
57,600bps) and generally deliver better performance at lower
speeds, as well.
Please note that the enclosed copy of the SIO drivers is
UNREGISTERED. If you decide to keep using SIO, you should
register (pay the nominal registration fee) as described below,
so Ray can continue to develop and support these outstanding OS/2
comm drivers.
Also note that Ray is solely responsible for the support of the
SIO drivers. If you have questions relating to SIO or encounter
difficulties with this shareware product, you will need to
contact Ray (not Hilgraeve) for assistance, as described below.
The following documentation has been provided by Ray Gwinn,the
author of the SIO drivers:
What is SIO?
SIO is a Serial Input/Output (SIO) communications character
device driver. It provides an interface between application
programs and the serial communications hardware.
SIO had been designed as a high performance replacement for the
OS/2 device driver COM.SYS. This manual documents the known
differences between COM.SYS and SIO.SYS.
SIO only works with 8250 (type) serial I/O devices. Such devices
include, but are not limited to the 8250A, 16450, 16550, 16550A
and the 82510. If you have a PC that is an IBM or
near-compatible which has a serial communication port, it is
likely that it contains one of these devices. SIO will identify
the type of serial devices that it finds at load time.
Like other Device Drivers, SIO will do very little standing
alone. There must be an application(s) program that makes use of
SIO's functions before one will benefit from the use of SIO.
Distribution, Ordering and Support
Distribution and Ordering
The entire package collectively known as SIO is ShareWare. It is
not free software or freeware. See LICENSE.TXT and ORDER.TXT for
additional information. The ShareWare version of SIO is
distributed electronically. One may check their favorite
electronic hangout for the latest version of SIO. The latest
copy of the ShareWare version is always posted for downloading
from the BBS at 1-304-255-7903 or 199.248.240.2.
Registered versions of SIO are distributed by US Mail and
electronically from the SIO Distribution and Support BBS. Users
desiring to register electronically, may call the BBS and
register on line (1-304-255-7903 or 199.248.240.2) and
immediately download their registered version of SIO. Use the
ORDER command at the main BBS prompt.
Registrations/Orders can also be placed by phone, mail, FAX, and
email. See the front cover of this manual for the phone numbers
and addresses. Also see ORDER.TXT for and order form that may be
used.
Support
Extensive testing has been done to insure that this product works
on the widest possible range of OS/2 V2 (and up) systems. In
most cases, problems can be resolved by reading this manual
carefully.
Support is provided in section 4 of the OS/2 Vendor Forum on
CompuServe (GO OS2BVEN). Section 4 of the OS2BVEN Forum is
dedicated to the support of SIO.
In addition, support is provided by BBS, Email and FAX. Voice
support would overwhelm the author and is not available. If,
after reading the manual carefully, you are unable to resolve a
problem, you may submit a problem report to one of the following:
Email CompuServe: 71154,575
Internet: ray@gwinn.com
FAX 1-304-255-7902
BBS 1-304-255-7903 or 199.248.240.2
Users should note that Support does not always result in a
correction of a problem. In addition, the support provided is
support of SIO, and not the applications that use SIO. Questions
and/or problems about applications programs (such as terminal or
FAX programs) should be directed to the available support for the
application.
Installing SIO/VSIO
SIO is distributed as a ZIP file. To extract the individual
files from the distribution file you need the program PKUNZIP or
an equivalent. PKUNZIP is a product of PKWARE and can be
downloaded from almost any bulletin board system (BBS). You
probably already have PKUNZIP and know how to use it, otherwise I
doubt that you would be reading this. When PKUNZIP is used to
extract the various files, -AV should appear after each file name
as it is extracted. In addition, the message:
Authentic files Verified!
should appear after the extraction process. If this message does
not appear, or appears with a name other than Raymond L. Gwinn,
the file is not an original SIO distribution file.
The only file that the basic user actually needs is SIO.SYS.
Virtual DOS machine (VDM) users will also want VSIO.SYS. Copy
one or both of these files to a convenient directory or
subdirectory on your system. An installation program
(INSTALL.EXE) is provided to install the SIO files and modify
your CONFIG.SYS.
Quick Start
Create a temporary directory, change into that directory and
unzip the SIO distribution zip there. Type INSTALL followed by
the enter key. For a basic setup, that is all that is needed.
If you choose to install SIO manually, the following should be
done.
BE SURE THAT ANY SERIAL MOUSE DRIVER APPEARS IN THE CONFIG.SYS
BEFORE SIO.SYS.
If you are going to use standard communications ports, either
COM1 or COM2 on an ISA bus (AT or clone), or COM1 through COM4 on
a PS/2, then add the following line to your CONFIG.SYS file:
DEVICE=SIO.SYS DEVICE=VSIO.SYS
Be sure to REMark out the COM.SYS and VCOM.SYS device drivers if
they exist in your CONFIG.SYS.
With the above statements you will be able to use standard COM1
and/or COM2 (if they exist) on any PC system known to the author.
The above, indented documentation was provided by Ray Gwinn, the
author of the SIO drivers. If you have questions about the SIO
drivers or encounter difficulties with this shareware product,
please contact Ray as described above.
------------
Using VMODEM
------------
VMODEM is a virtual COM port driver that allows communications
programs to use TCP/IP. Since HyperACCESS directly supports
TCP/IP, using this driver is not needed. However, if you wish to
use this driver, you may do so by setting up a new connection
with 'Vmodem (Ray Gwinn's SIO)' as the modem name and whichever
COM port you are using Vmodem on as the COM port. It's as easy as
that. HyperACCESS will function as though it is talking to a
modem even though it will actually be using Vmodem and TCP/IP.
--------------------------------------------
Setting Up HyperACCESS for OS/2 on a Network
--------------------------------------------
If you are setting up HyperACCESS for OS/2 for use on a network,
you should install the HyperACCESS PROGRAM files into a network
directory which is accessible to all users who you want to be
able to use HyperACCESS. You may prevent users from changing or
deleting files in this directory by making this a read-only
directory. Each user's HyperACCESS DATA files, on the other
hand, should be installed into a separate directory, which is
accessible to that user. You may prevent other users from
changing or deleting files is this directory by giving write
access to that directory only to the authorized user of that set
of data files.
NOTE: You must possess a quantity of HyperACCESS licenses equal
to the number of potential users; see License Agreement.
--------------------------------------------
Upgrading From Other Communications Products
--------------------------------------------
If you want to import phonebook entries from HyperACCESS Lite
(included in the OS/2 WARP BonusPak), HyperACCESS/5, HyperACCESS
for Windows, or Procomm, use the HyperACCESS Conversion Program
found in the HyperACCESS for OS/2 folder.
Users of HyperACCESS Lite who have customized their USERMDM.TXT
file with additional modems may use that file with HyperACCESS
for OS/2. Simply copy the file to the location where your data
files are located and those modem definitions will automatically
show up in HyperACCESS's modem list.
--------------------------------------
Lists, Upload and Download Directories
--------------------------------------
HyperACCESS Setup creates a number of directories in addition to
the HyperACCESS program and/or data directory. It creates a
LISTS subdirectory in its data directory, where it stores list
files that contain libraries of on-line systems that you can call
from the Lists panel. It also prompts you to specify upload and
download directories, which typically are located in the
HyperACCESS data directory.
HyperACCESS Setup also places folder objects representing these
directories in the HyperACCESS desktop folder, so you can easily
browse their contents, or copy files to and from these
directories later. For example, if you collect additional list
files in the future, you can copy them to the LISTS directory.
If you change the upload and download directories from within
HyperACCESS later, you may also want to create new folder objects
in your HyperACCESS desktop folder, to represent the new
directories. You may create them using Workplace Shell, or by
rerunning the HyperACCESS Setup program.
NOTE: If you run the Uninstall program to remove HyperACCESS
from your PC, it leaves this directory structure intact,
so that files you may have put in these directories remain
accessible.
------------------------
List Contents Disclaimer
------------------------
HyperACCESS comes with libraries of 1000s of on-line systems that
you can call. These libraries are actually ASCII files containing
lists of BBSs and other on-line services compiled by independent,
3rd-party authors. You can download newer versions of these
lists, plus a huge variety of similar lists, from BBSs and on-line
services all over the world.
Authors of such lists consider them to be copyrighted material.
Therefore, we include lists only with the author's consent and in
original, unaltered form. The authors maintain the copyright and
the sole right to revise and update these lists.
NOTE: If you find anything in these lists that you feel needs to
be updated or revised, please notify the independent,
3rd-party author of the list, not Hilgraeve. These lists
are copyrighted material of their authors, who retain the
sole right update and revise them.
Certain lists may include BBSs that provide access to explicit
materials--materials you may find offensive or unsuitable for
minors. Hilgraeve in no way condones electronic distribution of
such materials. If you find materials on a BBS offensive, please
be aware that the List panel DOES enable you to delete that entry
from your copy of the list.
-----------------------------------------
Running Non-API Programs from HyperACCESS
-----------------------------------------
The HyperACCESS manual incorrect states that only programs that
make HyperACCESS API calls may be assigned to keys or buttons for
use from within HyperACCESS. If you enclose the program name
within double-quotes when you assign it to a key or button, you
can run programs of any kind. If you omit the double-quotes,
HyperACCESS attempts to open a pipe to the program, for execution
API functions, as illustrated in this example:
Entering the program name c:\os2\apps\epm.exe readme.txt (without
double-quotes) would cause HyperACCESS to attempt to start epm
(the OS/2 Enhanced Editor) with a command line including a pipe
argument that would be nonsense to epm:
c:\os2\apps\epm.exe readme.txt /HAPIPE:<pipename>
Entering the program name "c:\os2\apps\epm.exe readme.txt" would
successfully start epm using the command line:
c:\os2\apps\epm.exe readme.txt
-----------------------------------------
Weather Report and Split-Second Utilities
-----------------------------------------
Weather Report
Weather Report is a cool utility that keep you abreast of
up-to-the-minute changes in the weather around the country. It
does this by calling up the FedWorld government BBS and
selectively downloading various weather map and satellite images
for you to view. To use Weather Report, simply double-click on
the Weather Report icon in your phonebook. You will be prompted
to select from a list of available weather images. Once you have
selected the images to download, it will call the BBS and take
you through logging in and downloading the images. You will see
the images appear as they are being downloaded, allowing you to
view the latest hurricane or weather front moving through the
area.
NOTE: Since this particular BBS periodically changes login
prompts for a new user, the logon script may get stuck
waiting for a prompt that never appears. If this happens,
simple hang up and call again. The script should then run
to completion.
Split-Second
Split-Second is a neat little atomic clock icon in HyperACCESS
Phonebook that performs a special function. When you double-click
it, it calls a US Government BBS, picks up the precise time and
date from the National Bureau of Standards' atomic clock, then
sets your PC's time and date accordingly.
In the case you inadvertently set the incorrect time zone the
first time you run the Split-Second session, don't panic -- you
may correct this by opening the Split-Second session and
following these simple steps:
1. From the Terminal menu, click on Properties and choose Runtime
Values from the list.
2. From the String #0: drop-down list find the 14th and 15th
entries and delete them.
3. Click OK.
4. Connect to the Split-Second session again to set the correct
time zone.
If you experience difficulty in connecting to this BBS and are
using a high-speed modem, you may find that turning off your
modem's error correction feature will correct this. You may do
this by experimenting with your modem's initialization string.
Usually adding a \N0 or a &Q0 to the session's additional modem
commands will accomplish this. Refer to the documentation that
came with your modem for further information.
------------------------
Uninstalling HyperACCESS
------------------------
The Uninstall program performs the following operations:
1. Removes HyperACCESS's changes from the CONFIG.SYS and OS2.INI
files on the PC where Uninstall is being run.
2. Deletes contents of the program directory associated with this
installed copy of HyperACCESS, unless the files were placed
there by another installation of HyperACCESS (or the directory
is write-protected).
3. Deletes contents of the data directory associated with this
installed copy of HyperACCESS. If you want to keep phonebook
entry files, make backup copies before running Uninstall.
4. Deletes all desktop objects associated with this installation
of HyperACCESS.
5. Leaves any files that you have placed in the Upload, Download,
and Lists directories, and leaves the HyperACCESS directory
structure intact, so you can still reach those files.
-------------
Manual Errata
-------------
1. In the Stop Recording dialog, "Run this script upon
connection" has replaced "Install as current logon task."
2. Changes to the modem definition file are saved in a file
called USERMDM.MOD in the data directory.
3. The Sound dialog has been rearranged. The "Sound event" and
"Associated file" controls are disabled unless the "Multimedia
sound" radio button is selected. If no multimedia support is
installed, this radio button is disabled.
4. The "Display graphics files while receiving" checkbox is in
the Transfer/Receive dialog, not the File Transfer Properties
Sheet.
5. The Fonts Properties Sheet has been rearranged, and the "Size"
entry field is disabled if the "Automatically adjust font size
to terminal window size" checkbox is selected.
6. A "Retry automatically if no dial tone" check box has been
added to the Dialing Details dialog.
7. If HyperACCESS detects an abnormal event during modem setup or
dialing, a message summarizes the problem and offers help,
which explains possible causes and remedies.
8. The Receive dialog includes no "Use receive filenames"
checkbox. All protocols except Xmodem use received filenames,
or follow overwrite options selected in this dialog. With
protocols other than Xmodem, the entry field at the top of the
dialog is labeled "Directory to receive files into."
9. On the ASCII Receiving Properties Sheet, selections for the
"After sending each line, wait for character" are made with a
drop-down list, not a spin button.
---------------
Installed Files
---------------
Other than placing these files in the directories specified
during installation, HyperACCESS makes one or two additional
changes to your system. It places an entry in your OS2.INI to
specify the program and user directories, and if you elected to
have Setup modify your CONFIG.SYS file, the HyperACCESS program
directory is added to the LIBPATH and HELP statements within that
file.
Contents of <DATA_DIRECTORY>
============================
REXX Scripts
============
GENIE.CMD Logon for Genie
DELPHI.CMD Logon for Delphi
MCI.CMD Logon for MCI Mail
DOWJONES.CMD Logon for Dow Jones
CIS.CMD Logon for Compuserve
BIX.CMD Logon for BIX
SIO.CMD Logon for SIO Support BBS
IBM.CMD Logon for IBM National Support BBS
ATTMAIL.CMD Logon for AT&T Mail
NEWSNET.CMD Logon for NewsNet
OS2SHARE.CMD Logon for OS2 Shareware BBS
WEATHER.CMD Logon for FedWorld BBS
Phonebook Entries
=================
COMPUSER.HAO Compuserve phonebook entry
ATTMAIL.HAO AT&T Mail phonebook entry
GENERIC.HAO Generic BBS phonebook entry
DELPHI.HAO Delphi phonebook entry
HAINET.HAO Generic internet phonebook entry
DOWJONES.HAO Dow Jones phonebook entry
GENIE.HAO Genie phonebook entry
HILGRAEV.HAO Hilgraeve BBS phonebook entry
BIX.HAO Bix phonebook entry
MCIMAIL.HAO MCI Mail phonebook entry
NEWSNET.HAO NewsNet phonebook entry
IBM.HAO IBM Support BBS phonebook entry
SIO.HAO SIO Support BBS phonebook entry
OS2SHARE.HAO OS/2 Shareware BBS phonebook entry
SPLIT.HAO National Time Server phonebook entry
WEATHER.HAO FedWorld BBS phonebook entry
HAHOST.HAO HyperACCESS Host phonebook entry
DEFAULT.HAO New phonebook entry template
Icons
=====
HAREADME.ICO Readme icon
HAUNINST.ICO Uninstall icon
Uninstall Files
===============
SETUP.INS Setup utility script
~INS0762.LIB Setup support library
SETUP.EXE Setup utility
INSTALL.CFG Installation config file
HAUNINST.CMD Uninstall script
Miscellaneous
=============
HA.INI HyperACCESS settings
HAHOST.PWD HyperACCESS Host password list
PCWEXP.WAS Procomm/Win export script
PCW2EXP.WAS Procomm/Win v2 export script
DEFAULT.LOG Default call log file
INSTALL.LOG Installation log file
USERMDM.MOD User modified modem definitions
Sounds
======
HARP.WAV Harp sound
DOORCLS.WAV Door closing sound
BABY1.WAV Baby crying sound
HORN.WAV Horn sound
PARTHORN.WAV Horn sound
PHONERNG.WAV Phone ringing sound
HALLELUJ.WAV Singing hallejulah sound
DOOR.WAV Door opening sound
DRUMROLL.WAV Drum roll sound
BUZZER.WAV Buzzer sound
CUCKOO.WAV Cuckoo sound
Text Files
==========
README.TXT File you are reading now
WELCOME.TXT Host welcome banner
HOSTHELP.TXT Text file explaining Host commands
APIHELP.TXT Text file giving API examples
API_REF.TXT Text file documenting API calls
SIO Communications Drivers
==========================
SIO153.ZIP Ray Gwinn's OS/2 comm drivers
Contents of <DATA_DIRECTORY>\LISTS
==================================
List Files
==========
OS2.BBS A list of OS2 BBS's (International)
SBIQ.LST A list of BBS's on the Internet (TCP/IP)
USBBS136.LST A list of BBS's (US only)
Contents of <EXE_DIRECTORY>
===========================
Icons
=====
HOST.ICO HyperACCESS Host icon
NPFOLD1.ICO HyperACCESS folder icon
NPFOLD2.ICO HyperACCESS open folder icon
Dynamic Link Libraries
======================
HAHELP.DLL HyperACCESS help DLL
HA2C_SHR.DLL OS/2 shared port comm. driver
HA2C_STD.DLL Standard comm. driver
HA2C_TCP.DLL TCP/IP comm. driver
HA2X_DIR.DLL Direct connection driver
HA2X_STD.DLL Standard connection driver
HA2X_TCP.DLL TCP/IP connection driver
TDLL.DLL HyperACCESS support DLL
Executables
===========
CONVERT.EXE HyperACCESS Conversion program
HALOGON.EXE Logon for Hilgraeve BBS
HAOS2.EXE HyperACCESS for OS/2 program
HAVIEW.EXE HyperViewer program
RESETINI.EXE Resets HA.INI
(WARNING: All user settings will be lost)
SET_TIME.EXE Logon for National Time Server
Help Files
==========
HACCESS.HLP HyperACCESS help
HAVIEW1.HLP HyperViewer help
HAVIEW2.HLP HyperViewer help
API Support Files
=================
HA_AUTO.H API include header file
HA_AUTO.LIB API library file
HA_AUTO.DLL API support DLL
Miscellaneous
=============
MODEMS.BIN Modem definition file