home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
BTMTEXE3.ZIP
/
BTP-MT.DOC
< prev
next >
Wrap
Text File
|
1992-04-26
|
7KB
|
176 lines
BinkleyTerm/2-Multi Thread 2.40.03
----------------------------------
1. Copyright Information and Acknowlegements:
-----------------------------------------
(C) Copyright 1987-90 Bit Bucket Software Co., a Delaware Corporation.
ALL RIGHTS RESERVED. COMMERCIAL DISTRIBUTION AND/OR USE PROHIBITED
WITHOUT WRITTEN PERMISSION FROM BIT BUCKET SOFTWARE CO.
Original port to OS/2 of BTP 2.40 by Bill Andrus at 1:109/301.10.
BT/2-MT enhancements by Chris Laforet Software at 1:3644/1 and
1:3644/2. Enhancements are released henceforth into the public
domain.
2. Source Code Availablity:
-----------------------
The original releases of BinkleyTerm for DOS and for OS/2 are available
at either node of Chris Laforet Software (1:3644/1 or 2). Source
code is also available.
The code for BT/2-MT as well as the executable are also available from
the same sources.
3. BinkleyTerm MultiThread:
-----------------------
Currently BT/2-MT uses 4 threads of execution. Two of these handle the
com port. One is in charge of the receive ring buffer and the other is
in charge of the send ring buffer. Another thread is used to handle
timer information. This thread is not doing much at present, but I
have plans for it (such as monitoring of CD and preventing continual
calls to the CD checking function from the main thread). The last
thread is the main program itself.
4. Changes between BT/2-MT and Regular BTP:
---------------------------------------
a. Execution is a lot faster.
b. The ESC key no longer shells. Only Alt-J will do that. The ESC
had the potential for causing problems with the Ctrl-ESC and
Alt-ESC used by OS/2 (i.e. if you were sloppy while hitting one
of these kb combinations, you would take the board offline!).
c. The Snoop-pipe stuff is history.
d. Lockbaud now works correctly. Just say:
Baud max_baud
Lockbaud
and the lockbaud will keep the port "locked" at the max_baud.
However, internally BT/2-MT keeps track of the REAL baud rate
and all xfer times and % efficiency reports are based on that
baud.
c. Connect strings that return a baud > 9600 and < 19200 will map to
19200 baud.
d. BT/2-MT sets up the com port correctly with handshaking on. It
should not touch the buffering question for folks who run
16550's, so you can keep using the mode statement if you desire.
There is an untested keyword "LeavePort" for the command line
which "should" allow BT/2-MT to behave like Andrus' BTP and not
set up handshaking. *Warning* To disable CTS-RTS handshaking is
equivalent to playing Russian Roulette. You might get by with
it, but on the other hand, you might not!
e. If Lockbaud is in action, SPAWNBBS is called with an extra
parameter:
SPAWNBBS actual_baud port_handle time_to_next_event
modem_reliable locked_baudrate
This way, if your BBS (like Simplex/2 BBS) doesn't change the
baud rate, you can pass it the correct baud of the connect so
that xfer rates are correctly calculated. Otherwise you can
snag the locked_rate so that your BBS can set it correctly.
f. Handshaking timing restrictions have been "bent" slightly to take
into consideration that OS/2 is a multitasking system. Actually,
the BT/2-MT is so fast, it's handshaking leaves the older BTP in
the dust.
g. I have attempted to clean up some of the code. This is a large
project codewise, so I am by no means near completion. I do hope
to move BT/2-MT over to complete ANSI-C since the OS/2 version
would not be compiled under anything less.
5. Warranties and Disclaimers:
--------------------------
Here is Bit-Bucket Software's regular statement:
NO WARRANTY
BECAUSE BINKLEYTERM IS LICENSED FREE OF CHARGE, WE PROVIDE ABSOLUTELY NO
WARRANTY. EXCEPT WHEN OTHERWISE STATED IN WRITING, BIT BUCKET SOFTWARE
CO. AND/OR OTHER PARTIES PROVIDE BINKLEYTERM "AS IS" WITHOUT WARRANTY OF
ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF
BINKLEYTERM, AND THE ACCURACY OF ITS ASSOCIATED DOCUMENTATION, IS WITH
YOU. SHOULD BINKLEYTERM OR ITS ASSOCIATED DOCUMENTATION PROVE
DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
CORRECTION.
IN NO EVENT WILL BIT BUCKET SOFTWARE CO. BE RESPONSIBLE IN ANY WAY FOR
THE BEHAVIOR OF MODIFIED VERSIONS OF BINKLEYTERM. IN NO EVENT WILL
BIT BUCKET SOFTWARE CO. AND/OR ANY OTHER PARTY WHO MAY MODIFY AND
REDISTRIBUTE BINKLEYTERM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
DAMAGES, INCLUDING ANY LOST PROFITS, LOST MONIES, OR OTHER SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY
TO USE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
INACCURATE OR LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE
PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS) BINKLEYTERM, EVEN IF YOU
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM
BY ANY OTHER PARTY.
To the above, I add my own for this release:
There are no warranties of any kind, explicit or implied, on the
BT/2-MT software. The executables and code are provided on an "AS
IS" basis. What this means is that if you decide to use BT/2-MT,
it is at your own risk. In plain English, this means that if you
use Simplex and your machine blows up, the developers and
distributors of Simplex are not responsible in any fashion. If
you use Simplex and it loses all of the files on your disk, once
again the developers and distributors of Simplex are not to be
held accountable. While these scenarios are rather extreme in
nature, they serve to indicate that Chris Laforet Software and/or
Christopher Laforet do not warrant, guarantee, or make any
other representations regarding the use, or results of use, of
BT/2-MT or its documentation in terms of accuracy, reliability,
correctness, currentness, or otherwise.
6. Contacting Me:
-------------
You may send me mail through any of the following:
Programmer's Oasis BBS, USA .... 919/226-6984
Programmer's Oasis 2 BBS, USA .. 919/226-7136
Fidonet Email .................. Chris Laforet @ 1:3644/1 or 1:3644/2
Compuserve Email ............... User ID: 76120,110
US Mail ........................ Chris Laforet Software
511-D Poplar St
Graham, NC 27253
These I check occassionally:
BIX Email....................... User ID: laforet
7. What's New?
----------
Changes made on Binkley for 2.40.03:
- Added LimitBaud command. This sets a limiting baudrate below which NOT to
send files if we are the caller (Not on my NICKEL, chump!!!).
- Cleaned up code to send Janus flag.
- Cleaned up problem with Get and Send file.
- Activated Janus correctly. Code was slightly incorrect and didn't support
locked baudrate connections.
- Cleaned up nodelist handling. Made new nodelist searching use file rather
than allocating memory to hold index (64K problem).