EzyExit V1.01u
Ezycom V1.01 to
Remote Access V1.11 EXITINFO.BBS Creator
Copyright Michael Denton 1992.
All Rights Reserved.
Disclaimer
----------
You use EzyExit totally at your own risk. In no event
shall I (Michael Denton), be liable for any damages,
or money. In using this product, you take full
responisibility for the damages it may/may not do.
Use
---
You are not allowed to tamper with, reverse engineer,
alter or anything else to any part of this
product including the EXECUTABLES AND THE DOCUMENTATION.
You are NOT allowed to make this file available for
DOWNLOAD on ANY PAY systems. Although, the file is allowed
to PASS THRU your system, such as in SDS (using TICK for
example). You are not allowed to modify the archive,
or add comment files/headers to the archive. You are NOT
allowed to re-archive this file into a different format.
EzyExit?
--------
EzyExit basically takes Ezycom's Exitinfo.<node> and
Sysinfo.BBS to create Remote Access's Exitinfo.BBS
EzyExit can also convert an EXITINFO.BBS back to
EXITINFO.1, for call back verifiers, gambling doors,
etc.
Basically, this enables some door programs like
MTS and Tetra to work under Ezycom.
Multinode
---------
Since EXITINFO.BBS can ONLY be created in one directory
per node, you must run EZYEXIT in the path where you
want EXITINFO.BBS created. Thus enabling different door
programs to read different EXITINFO.BBS. If this isn't
done for multinode BBS's, then the results are
unpredictable.
Usage
-----
Simply run EZYEXIT -N<node> to run ezyexit, where <node> is
the node number of the current node. EzyExit DOES support
the TASK environment variable, but -N overrides it.
To convert an EXITINFO.BBS (created with EZYEXIT), back to
EXITINFO.<node>, use "EZYEXIT -N<node> TOEZYCOM". Do not
include the quotes. EXITINFO.BBS must be in the current
directory.
Support
-------
Michael Denton
you can reach me in the EC_SUPPORT conferences.