High Voltage Shareware

home *** CD-ROM | disk | FTP | other *** search

/ High Voltage Shareware / high1.zip / high1 / DIR10 / GT1800_2.ZIP / BIMOD110.LZH / BIMODEM1.DOC < prev next >

Wrap

Text File | 1989-05-30 | 126KB | 4,340 lines

B I M O D E M Version 1.10 May 29, 1989 Program Reference Manual (C) Copyright 1989 by ERIK LABS ALL RIGHTS RESERVED Erik Labs 3431 W. Thunderbird Rd. Suite 13-311 Phoenix, AZ 85023 This Page is intentionally left blank Bimodem Copyright and License Agreement BiModem Copyright and License Agreement (C) Copyright 1989 Erik Labs. All rights reserved. No part of this manual may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language (natural or computer), in any form or by any means, except as described in the following license without the prior written permission of ERIK LABS. You are granted a limited license to use the software described in this manual. The software may be used or copied only in accordance with the terms of that license, which is described under SINGLE COPY SOFTWARE LICENSE. Information in this manual is subject to change without notice and does not represent a commitment on the part of ERIK LABS. ERIK LABS may make improvements and/or changes in this manual and/or in BiModem at any time. SINGLE COPY SOFTWARE LICENSE THIS IS A SINGLE COPY SOFTWARE LICENSE granted by ERIK LABS whose mailing address is at 3431 W. Thunderbird Rd., Suite 13-311, Phoenix Arizona 85023. BiModem is licensed to you as the end user. BiModem is copyrighted material. You may use it on a trial basis provided you do not violate the copyright and if you follow these simple rules. Use of BiModem on a regular basis requires purchase as described later. You may not make any changes or modifications to BiModem, and you may not decompile, disassemble, or otherwise reverse-engineer it. You may not rent or lease it to others. You may make copies of BiModem only under the terms of the following section entitled "Limited License to Copy". This Software is Commercial Computer Software under Federal Government Acquisition Regulations and agency supplements to them. The Software is provided to the Federal Government and its agencies only under the Restricted Rights Provisions of the Federal Acquisition Regulations applicable to commercial computer software developed at private expense and NOT in the public domain. The use, duplication, or disclosure by the Government is subject to restrictions as set forth in subdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at 252.227-7013. LIMITED WARRANTY. Erik Labs makes no warranty of any kind, either expressed or implied. This includes, but is not limited to, implied warranties of i Bimodem Copyright and License Agreement merchantability, and fitness for any particular purpose with respect to both the software and the documentation included in this package. IN NO EVENT SHALL Erik Labs OR ANY OF ITS PRINCIPLES BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, OR INCIDENTAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THIS PRODUCT EVEN IF ERIK LABS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR CLAIM. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages, so the above limitation may not apply to you. The warranties set forth above are in lieu of all other express and implied warranties, whether oral, written, or implied, and the remedies set forth above are your sole and exclusive remedies. LIMITATION OF LIABILITY. In no case shall Erik Lab's liability exceed the license fees paid for the right to use BiModem or five dollars ($5.00), whichever is greater. INTEGRATION. This License constitutes the entire agreement and understanding between the parties and supersedes any prior agreement or understanding whether oral or written, relating to the subject of this License. This Agreement may only be modified by a written agreement signed by Erik Labs. LIMITED LICENSE TO COPY You are granted a limited license to copy BiModem only for the trial use of others subject to the software license described above, and also the following: BiModem must be distributed in absolutely unmodified form, including ALL program, documentation, and other files. BiModem may not be included with any other product for any reason whatsoever without a license from ERIK LABS. BiModem may not be offered through Public Domain, Shareware, Freeware, or other offers of mass media distributions unless prior permission has been granted in writing by Erik Labs. This includes disk vendors. Operators of electronic bulletin board systems (Sysops) may post BiModem for downloading by their users without written permission only as long as the above conditions are met. A fee may be charged for access to the BBS as long as no specific fee is charged for access to the BiModem files. ii Acknowledgements Acknowledgements We would like to thank the following individuals for their continued support and assistance. Chris Hall for QKBilog, the Quick BBS Door. BBS: The PC Network 505-821-5341 Dale Fedorchik for his Wildcat interface and assistance in testing. BBS: The Cat's Castle 215-867-8761 Jimmy Pearson for the Byte Brothers PCBoard Door. Michael Phelps for use of the name BiMenu. BBS: The Keyboard BBS 602-846-2940 Michael Malone for the BiModem Echo. BBS: The Migrant BBS 602-264-2328 Mike Callahan affectionately known as Dr. File Finder for assistance in propagating our product. Nick Annis for his loan of equipment, time, and suggestions. Steve Lee for File Door, the Quick BBS/PCBoard interface. BBS: The System Three R's 503-582-4860 We would also like to thank the numerous sysop's who have unselfishly devoted there time and energy to propagating our product. We appreciate it. The following companies hold the following trademarks, or market the following products, mentioned in this manual: Adam Hudson, Arvada, CO: Quick BBS Artisoft, Inc., Tuscon, AZ: Lantastic Clark Development Company, Inc., Salt Lake City, UT: PCBoard Datastorm Technologies, Inc., Columbia, MO: ProComm Exis, Inc., West Hill, ONT: Telix Hayes Microcomputer Products, Inc., Norcross, GA: V29/V42 modems Microsoft Corporation, Bellevue, WA: MS-DOS Mustang Software, Inc., Bakersfield, CA: Wildcat Omen Technology, Inc., Portland, OR: Zmodem Quarterdeck Office Systems, Santa Monica, CA: Desqview SoftLogic Solutions, Inc., Manchester, NH: Double Dos US Robotics, Inc., Chicago, IL: Courier 9600 HST, Dual Standard Ward Christensen: Xmodem Wynn Wagner: Opus iii Acknowledgements This Page is intentionally left blank iv Table of Contents Table of Contents Copyright and License Agreement . . . . . . . . . . . . . . . . . . . . i Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . v INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Program Description . . . . . . . . . . . . . . . . . . . . . . . . 1 The future . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . 3 BiModem Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Start-Up Directory . . . . . . . . . . . . . . . . . . . . . . . . 4 BiModem Getting a Quick Start . . . . . . . . . . . . . . . . . . . 4 BiMenu - The menu for BiModem and its support programs . . . . . . . . . 7 command format . . . . . . . . . . . . . . . . . . . . . . . . . . 7 selection screen . . . . . . . . . . . . . . . . . . . . . . . . . 8 BiPath - The original transfer list maintainer . . . . . . . . . . . . . 11 command format . . . . . . . . . . . . . . . . . . . . . . . . . . 11 sample screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 acceptable keys . . . . . . . . . . . . . . . . . . . . . . . . . . 14 BiBat - The mini terminal emulator . . . . . . . . . . . . . . . . . . . 17 command format . . . . . . . . . . . . . . . . . . . . . . . . . . 17 BiModem - The file transfer program . . . . . . . . . . . . . . . . . . 19 command format . . . . . . . . . . . . . . . . . . . . . . . . . . 19 example screen . . . . . . . . . . . . . . . . . . . . . . . . . . 21 acceptable keys . . . . . . . . . . . . . . . . . . . . . . . . . . 22 BiConfig - Configuring your environment . . . . . . . . . . . . . . . . 25 command format . . . . . . . . . . . . . . . . . . . . . . . . . . 25 selection screen . . . . . . . . . . . . . . . . . . . . . . . . . 26 Screen and Colors . . . . . . . . . . . . . . . . . . . . . . . . . 27 Terminal Options . . . . . . . . . . . . . . . . . . . . . . . . . 29 General Options . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Download Defaults . . . . . . . . . . . . . . . . . . . . . . . . . 36 Upload Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Filenames and Paths . . . . . . . . . . . . . . . . . . . . . . . . 40 Comm Port Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Write Setup to Disk . . . . . . . . . . . . . . . . . . . . . . . . 45 Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Appendix A - File Formats . . . . . . . . . . . . . . . . . . . . . . . 47 Configuration File . . . . . . . . . . . . . . . . . . . . . . . . 47 Paths file layout . . . . . . . . . . . . . . . . . . . . . . . . . 48 v Table of Contents Appendix B - Sample Script Files . . . . . . . . . . . . . . . . . . . . 49 Sample Telix Script File . . . . . . . . . . . . . . . . . . . . . 49 Sample Procomm Plus Aspect File . . . . . . . . . . . . . . . . . . 49 Appendix C - Performance . . . . . . . . . . . . . . . . . . . . . . . . 51 Appendix D - Desqview Notes . . . . . . . . . . . . . . . . . . . . . . 53 Appendix E - Double Dos Notes . . . . . . . . . . . . . . . . . . . . . 55 Appendix F - Lantastic Notes . . . . . . . . . . . . . . . . . . . . . . 57 Appendix G - Modem Settings . . . . . . . . . . . . . . . . . . . . . . 59 Preferred USRobotics Courier 9600 HST Settings. . . . . . . . . . . 59 Preferred USRobotics Courier 9600 DUAL Settings. . . . . . . . . . 59 Appendix H - 16550's . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 vi Introduction INTRODUCTION Program Description BiModem is a new communications protocol which allows simultaneous bidirectional file transfers. Yes, BiModem can upload while downloading. Imagine the time savings if you could upload with Zmodem (tm) and YmodemG efficiencies while downloading at the same efficiency at the same time. The applications for such a protocol are many, and I will not try to cover them here. Everyone from occasional BBS users to fulltime network managers will appreciate the advantages of exploiting full duplex operations. Even for those with small and moderate volumes of data to transfer, the time savings can be very significant. Please do not expect a 50% decrease in your overall modem transfer time. This can only be achieved when the same amount of information is transmitted in both directions, and does not account for the overhead of specifying the lists of files to download and upload. If that feature is not enough to get you really excited, how about the ability to chat while the transfer is going on? Chatting, of course, will impact your throughput, but since most of us are slow typists, when compared to the speed of even a 1200 baud modem, the impact is usually minimal. Two methods of automatic recovery are provided. This first is the one that everyone else provides. If a file exists with the same name, date, and time, but different sizes then BiModem picks up where it left off. The second method is for boards that like to have the date and time stamp reflect the time the file was uploaded. It will rename a file into an abortion directory if the transmission is prematurely terminated. Then when the user calls back to finish the upload it will restart where it left off. A refresh mode of uploading is provided that verifies the contents of two files and only sends the data where it encounters discrepancies. The verification part takes about 20 seconds per 200k at 2400 baud. If it finds a large number of consecutive discrepancies it then switches to a normal upload. This is perfect for large transaction files where the only thing that ever changes is at the end of the file where transactions are added. Imagine refreshing a 10 meg file in a few minutes that only had 20k modified at the end. Auto Verification insures that the entire file was accurately transmitted and can be switched on at the user's discretion. While this is normally not necessary (BiModem already uses 32bit CRC's to insure accuracy), it is a nice feature to have available for those critical transmissions and is efficient enough that you may want to use it routinely. BiModem has more than just * name handling. You can create a large list of upload and download requests before you even sign on. Create an entire evening's worth of requests and let your computer do the rest. 1 Introduction Multiple directories can be searched for the file. You can provide a list of directories for BiModem to search. Imagine requesting a download of *.GIF and receiving every GIF file the board has available. Not just the ones in the area you are in. You can also supply a list of directories for it to scan for duplicates. Upon finding a duplicate in any of the directories in the list it will discontinue the transmission of that file. BiModem is both Double Dos and Desqview aware. For both of these fine multi- tasking software additions it intelligently informs them when it is idle. This allows other tasks to get more of your machine's time. It also means that the display is as fast and intelligent as it can be. All of this power is provided to you by a menu. This makes the functions easy to remember and fast to get to. BiModem is fully configurable to allow as much or as little access to your system as you desire. You can allow full path specifications on both ends. If a file already exists, you can replace the file directly, or simply run a verify to revise only the parts that have changed. You may request that the source file be deleted on a successful transmission or you can disable this feature so others cannot delete files from your system. For registered users there are even more features: Four different methods are available to maintain your file transmission requests. You can mark files to be sent by walking through your hard disks and selecting them. You can scan a previously downloaded list to select files you want to download while you are offline. There is a hot key program provided so that you can mark files that are displayed on screen. And there is the original request list maintenance program. Forget a file? No need to wait until the current transfer is done. You can add transfer requests while in the process of transferring other files. You can also kill single requests on either the send or receive side. Surely by now you are wondering if this is all BiModem does. The answer unfortunately for today is yes, but the future holds even more exciting things for BiModem. There just wasn't time to add all the features for this release. We are offering an earlybird special to the first 1000 users who have taken the time to read about BiModem. Simply write earlybird on your completed registration form. This entitles you to a free upgrade when the next version is released. The future will offer additional features such as: Sub-Directory inclusion: Tell BiModem you want sub-directories included, and it will copy all files matching the * name from the specified directory on down the tree and create a similar tree on the receiving end (if 2 Introduction allowed and the tree doesn't already exist). Dialing lists and scripts: Build a list of phone #'s to call, tell us which script to use, what transmission request file to use, and go to bed (let your computer do the walking). File Compression: for even faster transfer rates. Machine Requirements BiModem requires a PC/XT,AT,386 with at least 100k of memory available to it. It will work on MicroSoft DOS 2.0 and up. Unbuffered communications boards work best. The buffered communications boards will work, but they will have a negative impact on the BiDirectional file transmissions and when chatting. BiModem Files BiModem is comprised of the following files: BiMod110.Zip - This is the shareware version of BiModem. Registered users are sent this so they may distribute THIS FILE ONLY according to it's shareware license. All other files are governed by the license agreement included in this document. BiMenu.Com - The BiModem menu program. BiModem.Com - The File Transfer Program. BiPath.Com - The Paths File Maintenance Program. BiBat.Com - A Mini Terminal Emulator that monitors the communications port to see when BiModem is up on the other computer. BiConfig.Com - The BiModem Configuration Program. BiModem.Cfg - BiModem's configuration file. BiModem.Pth - Paths File - specifies files to be transferred. BiSetup.Com - The setup program. Prompts you for information and then runs Binstall.Bat. Binstall.Bat - This helps to install BiModem and should be run from a directory other than the one your Terminal Program (i.e. Telix or Procomm) resides in. BiModem.Cf? - A series of sample config files used to simplify the installation process. 3 Introduction BiMod.Slt - Simple script example for Telix. BiMod.Asp - Simple script example for Procomm Plus. BiMod.Scr - Simple script example for Qmodem. BiMod.Bat - Batch file for running BiModem from Dos. For registered users the following programs are also included. BiMark.Com - Program to mark uploads from your disks. BiList.Com - Program to mark downloads from a downloaded LIST of files. BiHot.Com - Hot Key program to mark downloads from what's displayed on your screen. BiSelect.Com - Program to select from multiple transfer lists. Note: The script files are renamed bimodem.??? when the install is run so that is what you will want to execute from your terminal program. BiModem will create a BiModem.Cfg file if none exists at the time it is run. BiPath.Com will likewise create a BiModem.Pth. BiModem transfers the files, and BiPath maintains the list of files to be transferred. Start-Up Directory BiModem must reside somewhere, and this directory is referred to as its startup directory. The easiest method of placing files is to simply place them all in the same directory. The default configuration specifications require this. BiModem has been designed to be flexible, so you may place them in any directory on any disk you like. To do this, install BiModem and specify the full paths to these files, or provide command line overrides to specify these paths. For more detailed information on these options, please refer to the detailed BiModem Installation section and the Command Line syntax section. BiModem Getting a Quick Start The easiest way to get BiModem up and running is to run Binstall. It will let you select the communications program that best describes your program (Other for most), and which directory it resides in. You will also be asked which communications port your modem uses. The appropriate files will then be copied to your communications directory. Before running this, you should unarc the BiMod110.Zip file into a work directory from which the files may be copied to your communications directory. 4 Introduction ****************[BiSetup (C) Copyright Erik Labs 1989]**************** * What Communications program will you be running on your computer? * * 1 - Telix * * 2 - Qmodem * * 3 - Procomm Plus * * 4 - Other * * 5 - Running a BBS * * * * What is the path to your communications directory? ie C:\TELIX * * _:________________________________________________________________ * * * * What communications port will you use from this communications * * program? 1-COM1 2-COM2 3-COM3 4-COM4 5-COM5 6-COM6 7-COM7 8-COM8 * ********************************************************************** * This batch file cannot configure bimodem for everyone nor does it * * attempt to. What it does do is give you a good place from which * * to start. It will generally set up acceptable parameter values * * for general use, however it simply installs the suggested * * configurations for BBS Sysops. Your particular software and * * hardware configurations may make it necessary to make changes to * * these settings for optimal use. See documentation for assistance. * *********************[Esc-Undo,Alt-X Exit,>,<,v,^]******************** Fill in the blanks on the screen and the batch file will do the rest. If you use Telix, and you don't have CS.EXE in your Telix directory, you should move a copy there prior to running the batch file, and you may delete it and move the bimodem.slc file into your designated script directory after the install is complete. We recommend you use this setup a few times to get familiar with Bimodem, and then change only the upload and download directories on the BiModem Installation screen. Then, try it a few more times before experimenting with the other parameters. The other method is manual, and is described below: 1. Pick a directory where BiModem and BiPath may be easily executed from your communications program. I use Telix, and simply placed BiModem and BiPath in my Telix directory. 2. Unarc the BiMod110.Zip file into a work directory. Copy Bi*.Com, BiMod.Bat, and BiModem.Cfg from the work directory to your communications directory. If you do not use Com1, you will need to run BiConfig to switch the port. See item 6 below on configuration files first. 3. Before transferring files with BiModem, you must specify the files to be transferred on one of the computers. To do this, enter BiMenu and select transfer list maintenance. This will give you a transfer specification screen. All you must specify is (U)pload or (D)ownload, and the source file (may be full pathname). Be sure the specification is entered by pressing PGDN which will display the transfer request in the scroll area above. If 5 Introduction you are uploading, most sysops prefer descriptions so you should probably give the file descriptions too. 4. If you have not already established a connection (i.e. Logging onto your favorite BBS), you should do this now. 5. Finally, start BiModem on the other computer and execute bimodem on your end. BiModem can be executed on your computer by invoking it from DOS, a script file, or selecting Host or Remote BiModem from BiMenu. Remote BiModem brings up a mini terminal emulator so that you can start BiModem on the other computer. On a terminal emulator to terminal emulator connection you would want to invoke remote BiModem on one end and Host BiModem on the other. The script files included bring up BiMenu. 6. Note, there are two BiModem configuration files included in the BiMod110.Zip file. BiModem.Cfg is set up for most people; BiModem.Cf1 is set up for most BBS's. If you are installing BiModem for use on a BBS, you should copy bimodem.cf1 to bimodem.cfg. Otherwise you should be all set. 6 BiMenu BiMenu - The menu for BiModem and its support programs BiMenu is a customized menu for BiModem and its support programs. BiMenu and all of its sub-programs can either be in your current directory or be accessible from one of the path environment variable directories. It is designed to be invoked from a terminal emulator as a hot key, or by jumping to DOS and invoking BiMenu (see appendixes for interface information). The command format is: BiMenu [/?/C/T/B/L/P/S] /? Displays the acceptable arguments. /C Config_Path Tells BiMenu what configuration path to use. The default is BiModem.cfg in your current directory. This argument, as with all BiMenu arguments is passed through to programs that it invokes. /T Time Limit Tells BiMenu what time limit in minutes to pass to BiModem. This value overrides the value specified in the configuration file. /B Baud Rate Tells BiMenu what baud rate to pass to BiModem for it to use in its time estimation. This value overrides the value specified in the configuration file. /L Comm Port Tells BiMenu what communications port to use. This value overrides the value specified in the configuration file. /P Transfer List Path Tells BiMenu what transfer list path to use. This argument overrides the path specified in the configuration file. /S Size Limit Tells BiMenu what size limit to pass to BiModem. This value overrides the value specified in the configuration file. 7 BiMenu The selection screen looks like this: ***************[BiMenu - (C) Copyright Erik Labs 1989]**************** * * * * * Remote BiModem * * * * * * Host BiModem * * * * * * Transfer List Maintenance * * * * * * Kill Transfer List * * * * * * Configure BiModem * * * * * * Exit * * * * * * * ****************************[Esc-Exit,^,v]**************************** Once this screen appears you may use the up and down arrows to position to the appropriate selection. Once the selection bar is on the appropriate selection you can then hit the enter key to invoke that function. Alternatively you can type in the first character of the selection to invoke it. Some of these functions are internal to BiMenu and some of them invoke other programs. We will now discuss the functions in detail. Remote BiModem This selection first invokes the program BiBat so that you may start BiModem on the bulletin board at the other end. BiBat is a mini terminal emulator that passes characters that you type on to the comm port and displays characters received from the comm port on your screen. It also monitors the characters received for the space/backspace character sequence that BiModem uses for its handshaking. Once BiBat recognizes a space/backspace sequence it terminates and BiMenu then invokes BiModem on your computer. Upon completion of BiModem, BiMenu also terminates. This should bring you back to your favorite terminal emulator software. Host BiModem This selection invokes BiModem on your computer. Upon completion of BiModem, BiMenu also terminates. This should bring you back to your favorite terminal emulator software. 8 BiMenu Transfer List Maintenance This selection invokes the program BiPath so that you can modify the list of files to be transferred. When BiPath terminates control will return to BiMenu. See the chapter on BiPath for information on how to use it. Kill Transfer List This selection deletes the current transfer list file. Configure BiModem This selection invokes the program BiConfig so that you can establish the operating environment for BiModem and all of its support programs. When BiConfig terminates control will return to BiMenu. See the chapter on BiConfig for information on how to use it. Exit This selection terminates BiMenu. The Escape key also terminates BiMenu. 9 BiMenu This Page is intentionally left blank 10 BiPath BiPath - The original transfer list maintainer BiPath is a program designed to let you maintain the list of files to be sent and/or received. It is designed to be invoked from BiMenu, but you can invoke it from the command line if you prefer. The command format is: BiPath [Transfer List Path] [/?/C] /? Displays the acceptable arguments. /C Config_Path Tells BiPath what configuration path to use. The default is BiModem.cfg in your current directory. Transfer List Path Tells BiPath what transfer list path to use. This argument overrides the path specified in the configuration file. 11 BiPath BiPath starts out by displaying all files currently selected to be sent/received in the top part of the screen. The cursor will then stop on the (U)pload/(D)ownload field and wait for you to enter a new file to be sent/received. If you want to modify an existing transfer request you can press PgUp and PgDn to get to the request you want to modify. Then you may use Ctrl/D to delete the request or re-type the information to change it. Here is a sample screen followed by a description of the fields, and a list of valid keys. **************[BiPath - (C) Copyright Erik Labs 1988,89]************** * * * * * * * * * * * * * * * * * * * * * * * * * * ********************************************************************** * (U)pload/(D)ownload U * * Source File> * * Dest File--> * * Description> * * Refresh Include Sub Directories * * Replace Delete SOURCE When Done * * Verify When Done * *[Esc-Undo,Alt-X Exit,Ctrl-D Delete,PgUp,PgDn,C-PgUp,C-PgDn,>,<,v,^]** (U)pload/(D)ownload This field will only accept a U for upload or a D for download. Upload means a file that is going to be sent from your computer to another computer. Download means a file that is going to be received on your computer, sent by another computer. 12 BiPath Source File This field is the path to the source file(s). It can contain star names. In the case of an upload it would point to one or more files on YOUR computer. In the case of a download it would point to one or more files on ANOTHER computer. If it is an upload the path is checked to insure at least one file exists. Some bulletin boards may not allow the use of full paths. If this is the case then the file part of the path you have entered will be used and the path part will be ignored. You can configure BiModem to search multiple directories for a file (See BiConfig). This will only work if a simple name (file name only, no path) is used or the file name has been stripped from the path due to the simple name only configuration option. Dest File This field is optional. This instructs BiModem where to put the file on the receiving computer. In the case of an upload this would be on another computer. In the case of a download this would be on your computer. If you omit this field the file will be put in either your current directory, or the receiving directory specified in BiConfig. You can point to a directory by terminating this field in a slash. This is extremely handy in the case of star names source files. Description This field is optional. It is only meaningful in the case of an upload. Some bulletin board interfaces will use this field to post the description of the file. If you omit this field on an upload some bulletin board interfaces will prompt you for them after the transfer is completed. Refresh This field is optional. You may specify a Y,N,or space. A Y indicates that you want the file verified via checksum and any discrepancies found sent. Of course this will only occur if a file is found on the receiving side. If the file can't be found then BiModem will perform a normal transfer. An N has no effect other than eliminating a default Y in BiConfig. A blank in this field indicates that BiModem will use the BiConfig default for uploads or downloads. Replace This field is optional. You may specify a Y,N,or space. A Y indicates that the file will be replaced (assuming that the receiver allows replacements). An N has no effect other than eliminating a default Y in BiConfig. A blank in this field indicates that BiModem will use the BiConfig default for uploads or downloads. 13 BiPath Verify When Done This field is optional. You may specify a Y,N,or space. A Y indicates that the file will be verified when the transfer is complete. An N has no effect other than eliminating a default Y in BiConfig. A blank in this field indicates that BiModem will use the BiConfig default for uploads or downloads. Include Sub Directories This field is not used at this time. It is planned that a Y in this field will indicate that directories subordinate to the one pointed to will also be searched for matching files to be transferred. Delete SOURCE When Done This field is optional. You may specify a Y,N,or space. A Y indicates that the source file will be deleted when a successful transfer completes. This ability can be disabled via BiConfig. An N has no effect other than eliminating a default Y in BiConfig. A blank in this field indicates that BiModem will use the BiConfig default for uploads or downloads. While using BiPath you may use the following list of acceptable keys. Right Arrow Advances the cursor 1 position to the right. Left Arrow Advances the cursor 1 position to the left. Control Right Arrow Advances the cursor 1 word to the right. Control Left Arrow Advances the cursor 1 word to the left. Home Puts the cursor at the beginning of the field. End Puts the cursor at the end of the field. 14 BiPath Alt Right Arrow Deletes the current word. Control U Converts the case of the current letter. Destructive Backspace Deletes the character behind the cursor and positions the cursor and text back 1 space. F6 Inserts 1 space at the current cursor position. Shifted F6 Deletes 1 space at the current cursor position. Control End Erases from the current cursor position to the end of the field. Control X Erases the entire field and puts the cursor in position 1 of the field. Down Arrow Advances to the next field. Up Arrow Takes you back to the prior field. Control Home Puts the cursor on the first field. Page Down Accepts the current transfer request or advances to the next transfer request. Control D Deletes the current transfer request. 15 BiPath Page Up Takes you back 1 transfer request. Control Page Down Advances you 1 page of transfer requests. Control Page Up Takes you back 1 page of transfer requests. Alt/X Exits BiPath and causes any modifications or additions you have made to be written to disk. Esc This key has many purposes. Its basic function is to undo the last thing entered. For example if you were half way through entering a description and you hit Esc, it would clear the description field and place the cursor at the beginning of the field. If you then hit Esc again it would clear the record you were working on and position the cursor on the first field. Then if you hit Esc again it would terminate BiPath and NOT write the modifications to disk. 16 BiBat BiBat - The mini terminal emulator BiBat's main purpose is to allow you to invoke BiModem on a bulletin board. Then once it sees BiModem come up it terminates so that BiModem can come up on your end. BiBat is a mini terminal emulator specially tailored for BiModem. In addition to performing ansi graphics level terminal emulation it also monitors characters received for 2 space/backspace pairs. The space/backspace pair is how BiModem handshakes to determine that there is a BiModem running on the other end. When BiBat sees 2 space/backspace pairs it terminates so that BiModem can be run either through a batch file or BiMenu. BiBat can be run on both sides of a connection, however it will never detect the 2 pairs of space/backspaces. Thus it will never continue on to BiModem. The command format is: BiBat [/C] /C Config_Path Tells BiBat what configuration path to use. The default is BiModem.cfg in your current directory. Once invoked, if Bibat does not immediately detect the 2 space/backspace pairs, it displays the following message. Dos to Comm Gateway -> Invoke BiModem on the other end or press ESC to exit (C) Copyright Erik Labs 1989 At that time you may type characters and they will be passed on the to comm port (Just like any terminal emulator). Normally you would type whatever characters the board requires to start BiModem. Characters received from the comm port are then displayed on your terminal. If it detects the 2 space/backspace pairs BiBat will terminate. You may also hit Esc to terminate BiBat. 17 BiBat This Page is intentionally left blank 18 BiModem BiModem - The file transfer program BiModem is the file transfer program. It can be run all by itself from command line, or it can be invoked from BiMenu. There are two references to BiModem in Bimenu. Remote Bimodem actually invokes BiBat first and then BiModem (see BiBat for further info). The second invokes BiModem immediately. The command format is: BiModem [/?/C/T/B/L/U/D/P/S] /? Displays the acceptable arguments. /C Config_Path Tells BiMark what configuration path to use. The default is BiModem.cfg in your current directory. /T Time_Limit Tells BiModem what time limit in minutes to use. This value overrides the value specified in the configuration file. /B Baud Rate Tells BiModem what baud rate to use in its time estimation. This value overrides the value specified in the configuration file. /L Comm Port Tells BiModem what communications port to use. This value overrides the value specified in the configuration file. /U File_List Specifies a list of files to be sent to the remote location. These may be the simple format which requires that the file be located in the current directory, or they may be full or partial paths. Due to the limited command line length, this is basically a convenient way to send a very few file specifications. Note, however, that the wildcard specifications are permitted and that depending on the situation, many files may be transferred with this option. 19 BiModem /D File_List Similar to the /U option except that this parameter specifies download requests. Again, full or partial paths may be specified, and due to limited command line, length is not practical for more than a few file specifications. Note, however, that wildcard names are permitted and that under certain circumstances many files may be transferred with this specification. /P Transfer List Path Tells BiModem what transfer list path to use. This argument overrides the path specified in the configuration file. /S Size Limit Tells BiModem what size limit to use. This value overrides the value specified in the configuration file. /I This argument is obsolete. It was used when BiConfig was part of BiModem. Currently this argument if passed is ignored. In the future it may be used for some other purpose. /O This argument is obsolete. It was used to inform BiModem that you had a composite monitor. Since the enhanced BiConfig allows you to set the colors to your personal preference, this is no longer needed. Currently this argument is ignored. In the future it may be used for some other purpose. /R This argument is obsolete. It was used to inform BiModem to use CTS/RTS handshaking. Since the enhanced BiConfig allows you to set this, it is no longer needed. Currently this argument is ignored. In the future it may be used for some other purpose. 20 BiModem Here is an example screen. *****************[BiModem - (C) Copyright Erik Labs 1988,89]****************** * (602)942-5403 ** John Erickson's Personal Copy Version 1.10 * ****************************************************************************** * Sending BIMOD110.ZIP * Receiving TLX310-1.ARC * Summary * * Bytes 98751 83572 * Bytes 87585 83572 * 167144 * * Time 6:57 5:52 * Time 6:10 5:52 * 5:54 * * Bytes/Sec 236.8 237.4 * Bytes/Sec 236.7 237.4 * 472.1 * * Err Count 0 * Err Count 0 * 0 * * Last Err * Last Err * * ************************************[Text]************************************ * Here is the new version of Telix. It is MUCH improved over the old * * version. Some of its supporters have been a bit concerned over the * * complexity of the Script language, however, I maintain that it is all for * * the better. I tried BiModem out with a Beta Version my brother gave me, * * and I must say I was Impressed. I can't wait to try the public release * * version... Thank you for allowing me to download it. Let me know if you * ****************************************************************************** * Please, let us know what you think of BiModem. It is our first Shareware * * product, and we really would like to make it the BEST PROTOCOL AVAILABLE. * * We feel that if a good percentage of people will call in with their * * comments (both good and bad), we will be able to reach this goal. Thanks * * again for your interest in our product and keep in touch. * *******[Alt/A-Add, Alt/S-Kill Send, Alt/R-Kill Receive, Esc-Terminate]******** The following text describes the information displayed on BiModem's transfer screen. While you will probably find most of the information self explanatory, you might want to read through this section to be sure you understand it. First, the top of the screen informs you who is on the other end. This option is nice for sysops as they may not have been on their system when the transfer began. The second section provides information about the file transfer such as the names of files being transferred, their length, and the rate at which the data is being transferred (Bytes Per Second). The first thing you will likely notice is that the total Bytes Per Second (Located on the far right) doesn't seem to be equal to the sum of the bytes per second on the individual files. There are several reasons for this. Since the sending file finished 2 minutes ago, its time stays constant. However, the combined rate reflects real time information. The reporting is designed to be as accurate as possible, and the total fields begin accumulation as soon as BiModem is started. If the other end waited several seconds to start up their end, it would severely reduce the overall throughput of the operation. It also includes the identification transfer which identifies the user at the other end which also reduces the overall transfer rate. The figures on each file 21 BiModem represent the total time and actual rates for transferring the files which are sent. There are 2 columns for each file being transferred. The first column represents BiModem's prediction of how long the transfer will take. The second column represents the real time transfer results. The third and perhaps one of the most noticeable features of BiModem is that you may converse with the person on the other end of the connection while transferring your files. Yes, it is just your normal chat window, but the nice part about it is that it has no effect if it is not used. It also has very little effect when very fast typists use the feature. We have tested some very fast typists, and find that even continuous chatting during the file transfer will effect the transfer throughput only 3 to 10 BPS. Only when very fast key repeating utilities are used does the effect become noticeable. As a little bonus, we have allowed the ctrl-G keystroke to cause a beep at the other end. The following lists the acceptable keys and what they do Alt/A Allows additions to the transfer list. Brings up the following screen in the bottom chat window. ****************************************************************************** * (U)pload/(D)ownload U * * Source File> * * Dest File--> * * Description> * * * *******[Alt/A-Add, Alt/S-Kill Send, Alt/R-Kill Receive, Esc-Terminate]******** While this screen is displayed you may add a request. The keys function similar to the way they do in BiPath. Esc takes you out of request add. Alt/X or PgDn completes the request. None of the options are overideable when adding a request this way. The requests that you add will use the defaults from BiConfig Upload and Download defaults. The meanings of the fields are the same as in BiPath, but we will reiterate them here. (U)pload/(D)ownload This field will only accept a U for upload or a D for download. Upload means a file that is going to be sent from your computer to another computer. Download means a file that is going to be received on your computer, sent by another computer. 22 BiModem Source File This field is the path to the source file(s). It can contain star names. In the case of an upload it would point to one or more files on YOUR computer. In the case of a download it would point to one or more files on ANOTHER computer. If it is an upload the path is checked to insure at least one file exists. Some bulletin boards may not allow the use of full paths. If this is the case then the file part of the path you have entered will be used and the path part will be ignored. You can configure BiModem to search multiple directories for a file (See BiConfig). This will only work if a simple name (file name only, no path) is used or the file name has been stripped from the path due to the simple name only configuration option. Dest File This field is optional. This instructs BiModem where to put the file on the receiving computer. In the case of an upload this would be on another computer. In the case of a download this would be on your computer. If you omit this field the file will be put in either your current directory, or the receiving directory specified in BiConfig. You can point to a directory by terminating this field in a slash. This is extremely handy in the case of star names source files. Description This field is optional. It is only meaningful in the case of an upload. Some bulletin board interfaces will use this field to post the description of the file. If you omit this field on an upload some bulletin board interfaces will prompt you for them after the transfer is completed. Alt/S This key allows you to kill the currently transferring send file. It doesn't stop transferring until all buffers are cleared. This usually means the completion of 2 more blocks of data. If you are talking to a version of BiModem prior to 1.09 it will work, but it just signals end of file. Alt/R-Kill Receive This key allows you to kill the currently transferring receive file. It will only work if you are talking to a version of BiModem 1.09 or better. It happens immediately and doesn't have to wait for buffers to clear. Control G - Operator Page This key rings the bell on the remotely connected computer. Provided of course that the remote computer allows bells during this time of day (See BiConfig General Options). 23 BiModem Esc-Terminate This key halts transmission, and terminates BiModem. 24 BiConfig BiConfig - Configuring your environment BiConfig is a program designed to let you configure BiModem and its support programs. It is designed to be invoked from BiMenu, but you can invoke it from the command line if you prefer. The command format is: BiConfig [/?/C] /? Displays the acceptable arguments. /C Config_Path Tells BiConfig what configuration path to use. The default is BiModem.cfg in your current directory. This argument, as with all BiConfig arguments is passed through to programs that it invokes. 25 BiConfig There are 7 sections to BiConfig. These sections are accessed from a selection screen similar to BiMenu. The selection screen looks like this: ***************[BiConfig - (C) Copyright Erik Labs 1989]************** * * * * * Screen and Colors * * * * Terminal Options * * * * General Options * * * * Download Defaults * * * * Upload Defaults * * * * Filenames and Paths * * * * Comm Port Setup * * * * Write Setup to Disk * * * * Exit * * * * * *********************[Esc-Exit,Tab,BTab,>,<,v,^]********************** Once this screen appears you may use the up and down arrows to position to the appropriate selection. Once the selection bar is on the appropriate selection you can then hit the enter key to invoke that function. Alternatively you can also type in the first character of the selection to invoke it. We will now discuss the functions in detail. 26 BiConfig Screen and Colors This selection is for modifying the way BiModem and its support programs converse with your display and to modify the color palette used. If you select this function it will bring up a screen that looks like this: ***************[BiConfig - (C) Copyright Erik Labs 1989]************** * * * * * Remove Snow (Y/N) N * * Use Bios for Screen Display (Y/N) N * * * * Press the arrow keys (><) to change the foreground colors. * * Press Ctrl and the arrow keys (><) for background colors. * * Sample Screen * * **[BiModem - (C) Copyright Erik Labs 1988]*** * Prompts * 000 000-0000 Remote site not Registered ** * ********************************************* * Fields * Sending * Receiving * Summary ** * * Bytes * Bytes * ** * Chat Received * Time * Time * ** * *******************[Text]******************** * Chat Keyed * Sample of Received Chat ** * * ** * Menu item current ********************************************* * * Sample of Typed Chat ** * Menu item other * ** * **************[Esc - Terminate]************** *********************[Esc-Exit,Tab,BTab,>,<,v,^]********************** Remove Snow On some of the older CGA display adapters direct screen writers will cause flicker. This field instructs BiModem and it's support programs to wait until vertical retrace happens before moving things to the screen. In layman's terms if your screen flickers say Y. 27 BiConfig Use Bios for Screen Display BiModem and its support programs display approximately 100 times faster if it can talk directly to your display hardware. So whenever possible you want this field to say N. Multi-tasking software such as Double Dos, Desqview, etc. do not like programs to do this because the display is not stoppable and will bleed through to the other task(s). Another class of programs that doesn't like direct screen writers is the ones that allow you to remotely access your PC. In order for them to see what is being displayed the programs being run must use Bios. If you are running one of these types of programs you will want to say Y to Use Bios. (Note: BiModem itself will properly handle Double Dos and is Desqview aware, so on a bulletin board where all you are running is BiModem, you can leave this set to N. The support programs are Desqview aware, but not Double Dos aware.) Changing Colors There are six different colors used in BiModem and it's support programs. One for each of the following field types: Prompts, Fields, Chat characters received, Chat characters typed, Menu item current, Menu item other. To change one of these colors you do the following. First position the cursor to the appropriate field type. Then you can use the right arrow and left arrow to change the foreground colors, and the control right arrow and control left arrow keys to change the background colors. There is a sample BiModem screen displayed which will change colors as you change the colors of the different field types. 28 BiConfig Terminal Options This selection is for modifying the way BiModem and its support programs converse with your communications port. If you select this function it will bring up a screen that looks like this: ***************[BiConfig - (C) Copyright Erik Labs 1989]************** * * * * * * * Baud rate to base estimates on (Modem Rate) 2400 * * * * Communications Port (1-8) 1 * * * * Modem Type D - USR Dual Standard F * * H - Half Duplex at high speeds * * F - Full Duplex always * * * * CTS/RTS hardware flow control (Y/N) Y * * * * Signal Loss of carrier on Carrier Detect (Y/N) Y * * * * Signal Loss of carrier on Data Set Ready (Y/N) N * * * * * * * * * * * *********************[Esc-Exit,Tab,BTab,>,<,v,^]********************** Baud rate This field identifies the normal connection default. It is used only for the purpose of computing estimated times and is overideable by the /B option of BiModem. Since BiModem relies on other software to configure the communications port and establish the modem connection, there is no way for it to know the connection rate. If you have an MNP modem there is no accurate method of predicting estimated times. Communications Port This field identifies the communications port number. It is overideable by the /L option of BiModem. It is used as an index into the table defined in the Comm Port Setup function of BiConfig. 29 BiConfig Modem Type This field identifies the type of modem being used. F indicates that the modem is full duplex all the time. This is true of all known 2400 baud or less modems, V32 modems, and V42 modems. H indicates that the modem is full duplex below 9600 baud and half duplex above. This is true of US Robotics HST modems, Hayes 9600 baud V29 modems, and most 9600 baud modems that do not state that they are V32 or V42. D indicates that the modem is full duplex if it connects to another D or F and half duplex if it connects to another H. This is true of the US Robotics Dual Mode. If it connects to another Dual Mode Modem it can transfer full duplex, but if it connects to an HST it talks half duplex. When BiModem determines that it must operate in half duplex mode it will only send files in one direction at a time. It will still allow chat. Most half duplex modems do have a slower speed back channel which allows chatting to occur, but if we attempt to transfer files bi-directionally the modems usually thrash too much trying to contend for the fast side of the transmission. CTS/RTS This field indicates whether or not you want to use CTS/RTS flow control. This is a requirement for MNP compression/bit stripping to occur. Under MNP you need to connect your PC to your modem at a faster rate than the modem is communicating over the phone line. This gives MNP time to compress the data and strip bits. Likewise on the receive side it needs to deliver more characters to your computer than it receives. Since you are talking to your modem faster than it is sending or receiving there needs to be some method of throttling the data so that you don't overrun its buffer. The most efficient method available today is CTS/RTS. It does not require any significant time. The other method commonly used is Xon/Xoff. We have elected not to use this method because it slows down transmission. The transmitting of Xon/Xoff characters takes time, not to mention the fact that Xon/Xoff characters that occur in data then have to be escaped to. In summary if your computer is talking to your modem faster than the modem is talking over the phone line than you want to say Y to CTS/RTS. Signal Loss of carrier on Carrier Detect This field indicates whether or not to base carrier loss on a drop of the carrier detect line from the modem. Y indicates that if the carrier detect line drops loss of carrier has occurred and BiModem terminates. Normally when someone hangs up their modem, the other modem will no longer hear the carrier signal and drop the carrier detect line. However, some modems have been found that do not raise the carrier detect line and causes a loss of carrier immediately. If this occurs change this value to an N. 30 BiConfig Signal Loss of carrier on Data Set Ready This field indicates whether or not to base carrier loss on a drop of the data set ready line. Y indicates that if the data set ready line drops, loss of carrier has occurred and BiModem terminates. Normally you would set this to N and data set ready will not be tested. If you can't use Carrier Detect, as mentioned in the prior field, you may want to use data set ready. 31 BiConfig General Options This selection is for modifying what will be allowed when people request files from or send files to YOUR system. If you select this function it will bring up a screen that looks like this: ***************[BiConfig - (C) Copyright Erik Labs 1989]************** * These options dictate what will be allowed when people * * request files from or send files to YOUR system * * Allow current directory access (Y/N) Y * * Allow file names only (no paths) (Y/N) Y * * Rename the file if it already exists (Y/N) N * * Always verify when done (Y/N) N * * Do NOT allow source deletion (Y/N) Y * * Retain original file date (Y/N) Y * * Do NOT allow full directory transfers (Y/N) Y * * Do NOT allow sub directory transfers (Y/N) Y * * Replace Timer Interrupt (Y/N) N * * Replace Keyboard Interrupt (Y/N) N * * Number of seconds to wait for connect 40 * * Operator Page allowed from 0: 0 till 0: 0 military time * * Phone number edit mask. All 9's will be replaced with a * * portion of the phone #. Other characters in the mask are * * placed in their display position as is. Please be sure * * to include 10 9's in the mask (999)999-9999 * * Maximum # of bytes that can be sent during 1 connection * * 0 means no limit 0 * * Maximum time allowed during 1 connection 24 hours 0 minutes * *********************[Esc-Exit,Tab,BTab,>,<,v,^]********************** Allow current directory access This field indicates whether or not remote users are allowed access to the current directory. It is applicable to files sent from your system, only if the sending directory field (see filenames and paths) points to a list of directories. Y indicates that it will first search the current directory and then the list. N indicates that it will only search the list of directories. Allow file names only This field indicates whether or not paths are allowed on file requests. Y indicates that other people can not supply path names. This is not to say that you can't supply paths. Requests that are generated locally can still supply full pathnames to files. However, if another computer supplies a full path the path part will be stripped away and just the file name will be used. N indicates that other people CAN supply full path names. 32 BiConfig Rename the file if it already exists This field determines if files that already exist at the destination location are allowed to be replaced or is the new file renamed to a unique name. Y indicates that a duplicate file name can't replace the dupe. It will be renamed to a unique name. This does not prevent file recovery. See "directory that aborted files will be renamed into" under filenames and paths. N indicates that replacement of files is allowed. Always verify when done This field determines if files are always verified when the transmission is complete or not. Y indicates that whenever a file completes it is always verified. N indicates that verification occurs only if requested by the other computer, the request, or because of a file sum error. See verification sending in the terms section for a definition. Do NOT allow source deletion This field indicates whether or not source files can be deleted when transmission is complete. Y indicates that files can never be deleted. N indicates that a file on your computer can be deleted after a successful transfer. Retain original file date This field indicates whether files you receive are to retain their original date or get current date/time stamped. Y indicates that files received are to retain their original date and time. N indicates that files received are to be date/time stamped according to the clock. Do NOT allow full directory transfers This field is not currently used. Its future intent is to disallow the transfer of a directory and all of its sub directories by pointing to the directory in question. Do NOT allow sub directory transfers This field is not currently used. Its future intent is to disallow the include all sub directories type of transfer. 33 BiConfig Replace Timer Interrupt This field indicates whether or not to replace the timer interrupt. On a few systems we have encountered problems in the timer interrupt bios. On these systems BiModem gets a large number of Naks. Generally the interrupt replacement is not necessary. When running under multi-tasking software such as Double Dos and Desqview replacement of the timer interrupt can cause problems. Local Area Networks also have problems if the timer interrupt is replaced. So we normally recommend not replacing it unless you absolutely have to. Y indicates that the timer interrupt is replaced by a small and quick version. N indicates that the timer interrupt is not replaced. Replace Keyboard Interrupt This field indicates whether or not to replace the keyboard interrupt. On a few systems we have encountered problems in the keyboard interrupt bios. On these systems BiModem gets a large number of Naks while chatting. When not chatting files transfer without errors. Generally the interrupt replacement is not necessary. When running under multi-tasking software such as Double Dos and Desqview replacement of the keyboard interrupt can cause problems. Local Area Networks also have problems if the keyboard interrupt is replaced. So we normally recommend not replacing it unless you absolutely have to. Y indicates that the timer interrupt is replaced. N indicates that the keyboard interrupt is not replaced. Number of seconds to wait for connect This field specifies the number of seconds BiModem will wait for a connection to another BiModem before displaying the error 'Connection can not be established'. Operator Page allowed from These fields indicate during what time of day operator pages (Ctrl/G) will be allowed. They must be specified in military time (no Am/Pm support). If both the start and stop time are zero then paging can be done any time. Phone number edit mask This field defines how phone numbers will be displayed. Phone numbers are always stored as 10 digit numbers. How these 10 digits are edited is up to you. This is accomplished via a mask. In the mask where ever the digit 9 occurs it will be replaced by 1 digit from the phone number. When entering a new mask make sure there are 10 9's in the mask or the results may be a program crash. The default US mask is supplied (999)999-9999. An example of one of the European masks is +999-999-9999. 34 BiConfig Maximum # of bytes that can be sent during 1 connection This field indicates the maximum number of bytes that can be sent during a single connection of BiModem. A zero in this field indicates that it is unlimited. Maximum time allowed during 1 connection This field indicates the maximum hours and minutes that a person can be connected during a single connection of BiModem. 35 BiConfig Download Defaults This selection is for modifying the default settings that will be used when you request a file to be sent TO your computer. If you select this function it will bring up a screen that looks like this: ***************[BiConfig - (C) Copyright Erik Labs 1989]************** * * * * * These are the default settings that will be used when * * you request a file to be sent TO your computer * * * * * * If file exists, use verify to upload it (Y/N) N * * * * If file exists, replace it (Y/N) N * * * * Verify files when done transferring (Y/N) N * * * * Delete source file when done (Y/N) N * * * * Include matching files in sub directories (Y/N) N * * * * * * * * * * * * * *********************[Esc-Exit,Tab,BTab,>,<,v,^]********************** All the fields on this screen determine the default action to be taken if you indicate to take the default on a download request. If File exists, use verify to upload it This field indicates whether or not verify is to be used to overlay an existing file on a download request. Y indicates that verify should be used. N indicates that BiModem should select what it thinks is the best method. If File exists, replace it This field indicates whether or not to replace an existing file. Y indicates that the file should be replaced. N indicates that it should not be replaced. 36 BiConfig Verify files when done transferring This field indicates whether or not to verify a file when done. Y indicates that the file should always be verified when the transfer is complete. N indicates that it will only be verified if the other computer requests it, or a fatal transmission error has occurred. Delete source when done This field indicates whether or not to delete the source file upon successful completion of the file transmission. Y indicates that the source file is to be deleted. Of course if the other computer does not allow his files to be deleted, then it won't happen. N indicates that the source file is to remain intact. Include matching files in sub directories This field is not currently used. Its future intent is to inform BiModem to include all sub directories of the referenced directory in the file search. 37 BiConfig Upload Defaults This selection is for modifying the default settings that will be used when you request a file to be sent FROM your computer. If you select this function it will bring up a screen that looks like this: ***************[BiConfig - (C) Copyright Erik Labs 1989]************** * * * * * These are the default settings that will be used when * * you request a file to be sent FROM your computer * * * * * * If file exists, use verify to upload it (Y/N) N * * * * If file exists, replace it (Y/N) N * * * * Verify files when done transferring (Y/N) N * * * * Delete source file when done (Y/N) N * * * * Include matching files in sub directories (Y/N) N * * * * * * * * * * * * * *********************[Esc-Exit,Tab,BTab,>,<,v,^]********************** All the fields on this screen determine the default action to be taken if you indicate to take the default on an upload request. If File exists, use verify to upload it This field indicates whether or not verify is to be used to overlay an existing file on an upload request. Y indicates that verify should be used. N indicates that BiModem should select what it thinks is the best method. If File exists, replace it This field indicates whether or not to replace an existing file. Y indicates that the file should be replaced. N indicates that it should not be replaced. 38 BiConfig Verify files when done transferring This field indicates whether or not to verify a file when done. Y indicates that the file should always be verified when the transfer is complete. N indicates that it will only be verified if the other computer request it, or a fatal transmission error has occurred. Delete source when done This field indicates whether or not to delete the source file upon successful completion of the file transmission. Y indicates that the source file is to be deleted. Of course if the other computer does not allow his files to be deleted, then it won't happen. N indicates that the source file is to remain in tact. Include matching files in sub directories This field is not currently used. It's future intent is to inform BiModem to include all sub directories of the referenced directory in the file search. 39 BiConfig Filenames and Paths This selection is for modifying the paths to directories and files used in BiModem. If you select this function it will bring up a screen that looks like this: ***************[BiConfig - (C) Copyright Erik Labs 1989]************** * * * Directory that files will be received into * * * * Directory that aborted files will be renamed into * * * * Delete aborted destination files (Y/N) N * * Path of file listing directories that determine rejections * * * * * * Directory that files will be sent from. This can point * * to a file that contains a C/R L/F delimited list of * * directories to be searched * * * * * * Path to UpLoad/Download list file * * bimodem.pth * * Path to log file * * bimodem.log * * Are connects/disconnects to be logged (Y/N) N * * Are file transfer statistics to be logged (Y/N) N * * * *********************[Esc-Exit,Tab,BTab,>,<,v,^]********************** Directory that files will be received into This field identifies the directory that files without paths are to be received into. This would include all files if you have specified that you allow simple names only (see general options). Directory that aborted files will be renamed into This field identifies the directory that files that get aborted will be renamed into. This is only pertinent to files being received. Aborted refers to any type of abortion ie. user cancel, carrier loss, user hitting the esc key. The rename will fail unless the directory is on the same drive. BiModem will not copy a file to another drive. Every time a user attempts to send you a file, this directory will be checked first to determine if the user is attempting to recover from a prior abortion. If the file he is trying to send to you exists in this directory it will be renamed back to the receiving directory and the transmission will restart where it left off. 40 BiConfig Delete aborted destination files This field indicates that an aborted file should be deleted. Aborted refers to any type of abortion ie. user cancel, carrier loss, user hitting the Esc key. Path of the file listing directories that determine rejections This field identifies a file that contains a list of directories that will be scanned to determine if you already have the file the user is trying to send you. If the file is found in any of these directories, then the transmission is discontinued. If the user has a prior version of BiModem than he will be sent a create/open error. If the user has the current version of BiModem then he will be sent a file rejected error. The directories in the list should be terminated by a \ and a carriage return and line feed. Directory that files will be sent from This field identifies where files will be sent from if the user does not supply a path. Of course if you are disallowing full paths (see general options), then it would include all file requests. This field can also point to a file containing a list of directories to be searched. The directories in the file should be terminated by a \, carriage return, and line feed. In the case of a star name request all the directories in the list will be searched. In the case of a non star name request as soon as the first match is found directory searching will terminate. If a list of directories is supplied, then the current directory is always checked first followed by the first directory in the list. Path to Upload/Download list file This field identifies the default transfer list path. The file it points to need not exist as BiModem and its support programs will create it when needed. Path to log file This field identifies the file that logging information will be written to. If the file exists the logging info will be appended to the end, otherwise a file will be created. What information is logged to this file is controlled by the following 2 fields. Are connects/disconnects to be logged This field determines if connections and disconnections are to be logged to the file identified in the path to log file field. Y indicates that connections and disconnections are to be logged. N indicates that they are not logged. 41 BiConfig Are file transfer statistics to be logged This field determines if file transfer statistics are to be logged to the file identified in the path to log file field. Y indicates that file transfer statistics are to be logged. N indicates that they are not logged. 42 BiConfig Comm Port Setup This selection is for modifying the comm port and IRQ table. If you select this function it will bring up a screen that looks like this: ***************[BiConfig - (C) Copyright Erik Labs 1989]************** * * * Base Interrupt * * Port Request * * Address Number * * * * Comm 1 03F8 4 * * * * Comm 2 02F8 3 * * * * Comm 3 03E8 4 * * * * Comm 4 02E8 3 * * * * Comm 5 03F8 4 * * * * Comm 6 02F8 3 * * * * Comm 7 03E8 4 * * * * Comm 8 02E8 3 * * * *********************[Esc-Exit,Tab,BTab,>,<,v,^]********************** Comm 1 These two fields identify the base port address and interrupt request queue that is to be used when you specify communications port 1 in the terminal options section or on the command line. Comm 2 These two fields identify the base port address and interrupt request queue that is to be used when you specify communications port 2 in the terminal options section or on the command line. Comm 3 These two fields identify the base port address and interrupt request queue that is to be used when you specify communications port 3 in the terminal options section or on the command line. 43 BiConfig Comm 4 These two fields identify the base port address and interrupt request queue that is to be used when you specify communications port 4 in the terminal options section or on the command line. Comm 5 These two fields identify the base port address and interrupt request queue that is to be used when you specify communications port 5 in the terminal options section or on the command line. Comm 6 These two fields identify the base port address and interrupt request queue that is to be used when you specify communications port 6 in the terminal options section or on the command line. Comm 7 These two fields identify the base port address and interrupt request queue that is to be used when you specify communications port 7 in the terminal options section or on the command line. Comm 8 These two fields identify the base port address and interrupt request queue that is to be used when you specify communications port 8 in the terminal options section or on the command line. 44 BiConfig Write Setup to Disk This selection will write any changes you have made to the current configuration file. It will not bring up a screen, but you should see the disk activity light flash as it writes out the file. 45 BiConfig Exit This selection is for exiting BiConfig. You may also use the Esc key to back your way out of BiConfig. 46 Appendix A Appendix A - File Formats Configuration File 1 - 1 Short Int Max Time Hundredths 2 - 2 Short Int Max Time Seconds 3 - 3 Short Int Max Time Minutes 4 - 4 Short Int Max Time Hours 5 - 8 Long Int Max Size hex Long Integer 9 - 10 Integer Baud rate of Modem Connection 11 - 11 Short Int Active Port Number 12 - 13 Integer Port Address 1 14 - 14 Short Int Interrupt Request Number 1 15 - 16 Integer Port Address 1 17 - 17 Short Int Interrupt Request Number 2 18 - 19 Integer Port Address 2 20 - 20 Short Int Interrupt Request Number 3 21 - 22 Integer Port Address 3 23 - 23 Short Int Interrupt Request Number 4 24 - 25 Integer Port Address 4 26 - 26 Short Int Interrupt Request Number 5 27 - 28 Integer Port Address 5 29 - 29 Short Int Interrupt Request Number 6 30 - 31 Integer Port Address 6 32 - 32 Short Int Interrupt Request Number 7 33 - 34 Integer Port Address 7 35 - 35 Short Int Interrupt Request Number 8 36 - 37 Integer Port Address 8 38 - 38 Bit Map 0 - Half Duplex Modem 1 - Dual Standard Modem 2-3 Reserved 4 - Maintain original date 5 - Summary Statistics 6 - Full Statistics 7 - Simple Names only 39 - 39 Bit Map 0 - Reserved 1 - Never allow sub directories 2 - Never allow directories 3 - Delete abortions 4 - Never delete source 5 - Always verify when done 6 - Always rename collisions 7 - Reserved 40 - 40 Bit Map 0-6 Default Download Options 41 - 41 Bit Map 0-6 Default Upload Options 42 - 121 Character Default Send Directory 122 - 201 Character Default Recv Directory 202 - 281 Character Default Log File Path 282 - 361 Character Default Paths File Path 362 - 362 Character Remove Snow (Y/N) 47 Appendix A 363 - 363 Character Modem Type (F-Full Duplex, D-Dual Standard, H-Half Duplex) 364 - 364 Character Use Bios Indicator (Y/N) 365 - 365 Character Test CTS Indicator (Y/N) 366 - 366 Character Test Carrier Detect (Y/N) 367 - 367 Character Test Data Set Ready (Y/N) 368 - 368 Character Replace Timer Interrupt (Y/N) 369 - 369 Character Replace Keyboard Interrupt (Y/N) 370 - 370 Short Int Prompt Color 371 - 371 Short Int Field Color 372 - 372 Short Int Chat Received Color 373 - 373 Short Int Chat Sent Color 374 - 374 Short Int Menu Item Current Color 375 - 375 Short Int Menu Item Not Current Color 376 - 377 Integer # of seconds to wait for connect 378 - 378 Short Int Start Page Minutes 379 - 379 Short Int Start Page Hours 380 - 380 Short Int End Page Minutes 381 - 381 Short Int End Page Hours 382 - 394 Character Phone Edit 395 - 474 Character Rejection List Path 475 - 554 Character Abort Directory Path Paths file layout 1 - 1 (U)pload or (D)ownload 2 - 2 (R)efresh 3 - 3 {Y| |N} Replace if existing override 4 - 4 {Y| |N} Verify when done override 5 - 5 {Y| |N} Delete source when done override 6 - 6 Unused 7 - 7 {Y| |N} Allow full directory override 8 - 8 {Y| |N} Include subdirectory override 9 - 88 Source Path 89 - 168 Destination Path 169 - 248 Description (Only used on Uploads) 48 Appendix B Appendix B - Sample Script Files Sample Telix Script File (Included as BiModem.SLT) main() { dos("BiMenu",0); } This script will, of course, have to be compiled prior to use with Telix. It is written for Telix 3.10. Therefore, it may differ with other releases of Telix. To compile the script type: CS BIMODEM from the DOS prompt. It is also suggested to assign this script to a macro key so that a single key input can be used to start up BiModem transfers. Refer to your Telix Manual for details on how this is done. Sample Procomm Plus Aspect File (Included as BiModem.ASP) DOS "BiMenu.Com" This script needs to be copied to your Procomm Plus directory. It is executed while connected to your remote site (Usually a BBS), by pressing alt F5 and entering BIMODEM in the window. These are admittedly very simple script files; however, they are intended mostly as an aid to understanding what is required. Secondly, for the novice programmer who may not know where to begin with a script file, this may lend some assistance. 49 Appendix B This Page is intentionally left blank 50 Appendix C Appendix C - Performance We wanted a fair way to compare BiModem and other protocols... so what we did was download 6 files using each of 3 transfer protocols. We chose Telink which was about as close to XMODEM as we could get and still support wildcard downloads, Zmodem which is very popular these days, and BiModem. We timed the execution from the time we pressed enter to start the transfer until the system responded ready to enter more commands. The tests were conducted using a 1200 baud modem connection from an 8mhz XT compatible to a 10mhz AT compatible which was running the BBS software (OPUS v1.03b). The XT was using Telix version 3.10. Here are our results: Downloading 6 2136 byte files: Telink - 2 minutes 45 seconds Zmodem - 2 minutes 29 seconds BiModem- 2 minutes 07 seconds Downloading 6 2136 byte files and uploading 6 2136 byte files Telink - 5 minutes 30 seconds Zmodem - 4 minutes 58 seconds BiModem- 2 minutes 07 seconds Of course, we knew it would be much faster when uploading and downloading, but we didn't know it would be so much faster when there was no data to upload. While these are not very scientific test results, they are indicative of the kinds of performance boosts you can achieve with Bimodem. Results may vary depending on the particular software and hardware used, so we encourage you to run your own timing tests. The Transmission speeds reported by most transfer protocols can be pretty misleading, some do not account for buffering (Either hardware or software). We even underestimate our rates primarily so as not to sacrifice actual performance. So use your watch and time the actual difference. 51 Appendix C This Page is intentionally left blank 52 Appendix D Appendix D - Desqview Notes BiModem can be classified as being Desqview aware. It automatically determines if it is running in a Desqview environment. It will inform Desqview when it is idle, so that other tasks can have more time on the system. BiModem and all of the support programs have there screen output re- directed to the Desqview screen buffer and Desqview periodically updates the screen from that buffer. This allows other windows to overlay the BiModem window with no bleeding of the information. We recommend that a separate window be created for either BiModem or BiMenu so that you can inform Desqview that this window is NOT swappable. THe amount of memory required for BiModem is dynamic. It depends on the number of transfer requests, upload directories, and rejection directories. We recommend that you use 100k. This should cover 99.9% of situations. In our example we use 115k because BiMenu is in memory along with BiModem. Here is an example of the required program parameters. *1**Change*a*Program************************************************************ * Change a Program * * * * Program Name............: BiMenu (BiModem Menu) * * * * Keys to Use on Open Menu: ME Memory Size (in K): 115 * ******************************************************************************** * Program...: \tlx\bimenu.com * * * * Parameters: * * * * Directory.: \tlx * ******************************************************************************** * Options: * * Writes directly to screen......: [N] * * Displays graphics information..: [N] * * Can be swapped out of memory...: [N] * * Requires floppy diskette.......: [N] * * * * Press F1 for advanced options Press <** when you are DONE * ******************************************************************************** 53 Appendix D *1**Change*a*Program************************************************************ * Change a Program Advanced Options * * * * System Memory (in K).......: 0 Maximum Program Memory Size (in K)..: 115 * * * * Script Buffer Size.......: 2000 Maximum Expanded Memory Size (in K): * * * * Text Pages: 1 Graphics Pages: 0 Initial Mode: Interrupts: 00 to FF * ******************************************************************************** * Window Position: * * Maximum Height: 25 Starting Height: 25 Starting Row...: 0 * * Maximum Width.: 80 Starting Width.: 80 Starting Column: 0 * ******************************************************************************** * Shared Program * * Pathname..: * * * * Data......: * ******************************************************************************** * Options: * * Close on exit to DOS.........: [Y] Uses its own colors.........: [Y] * * Allow Close Window command...: [Y] Runs only in foreground.....: [N] * * Uses math coprocessor........: [N] Keyboard conflict (0-4).....: [0] * * * * Press F1 for standard options Press <** when you are DONE * ******************************************************************************** 54 Appendix E Appendix E - Double Dos Notes BiModem is Double Dos aware. It automatically detects the presence of Double Dos. It changes the priority to 70/30 (70 for BiModem). Then it informs Double Dos when it is idle. This method yields excellent performance results. On my 386-25 when I run Telix in one partition and Norton SI in the other I get around a 9. When I run BiModem in one partition and Norton SI in the other I get around a 26. BiModem also switches to BIOS mode when it detects Double Dos. This allows you to normally write directly to the screen (BIOS N) and when you run Double Dos it will change for you. Switching to BIOS slows down the display, but it prevents bleeding through to the other task. 55 Appendix E This Page is intentionally left blank 56 Appendix F Appendix F - Lantastic Notes BiModem works well in a Lantastic environment provided you follow one simple rule. You must NOT replace the timer interrupt (See BiConfig General Options). Lantastic does all of it's network work during a timer interrupt. By replacing the timer interrupt you are not allowing Lantastic to do it's job. 57 Appendix F This Page is intentionally left blank 58 Appendix G Appendix G - Modem Settings For most modems no adjustments are needed in order to use BiModem. We have found some modems however that have switch settings which can affect the CTS signal handling. These settings should be made so that CTS indicates the modem's readiness to accept data. Xon/Xoff software flow control should not be used. Preferred USRobotics Courier 9600 HST Settings. C=? E=? F=? M=? Q=? V=? X=4+ B=? BAUD=19200 PARITY=N WORDLEN=8 DIAL=HUNT ON HOOK TIMER &A? &B1 &G? &H1 &I0 &K1 &M4 &N0 &P? &R2 &S? &Y? S00=??? S01=??? S02=??? S03=??? S04=??? S05=??? S06=??? S07=??? S08=??? S09=??? S10=??? S11=??? S12=??? S13=??? S14=??? S15=008 S16=??? S17=??? S18=??? S19=??? S20=??? S21=??? S22=??? S23=??? Settings marked as ? don't affect BiModem Performance. Preferred USRobotics Courier 9600 DUAL Settings. B0 C1 E? F? M? Q? V? X? BAUD=38400 PARITY=N WORDLEN=8 DIAL=HUNT ON HOOK TIMER &A? &B1 &C? &D? &G? &H1 &I0 &J? &K? &L? &M? &N0 &P? &R2 &S? &X? &Y3 S00=??? S01=??? S02=??? S03=??? S04=??? S05=??? S06=??? S07=??? S08=??? S09=??? S10=??? S11=??? S12=??? S13=??? S14=??? S15=008 S16=??? S17=??? S18=??? S19=??? S20=??? S21=??? S22=??? S23=??? Settings marked as ? don't affect BiModem Performance. 59 Appendix G This Page is intentionally left blank 60 Appendix H Appendix H - 16550's A 16550 is a chip that replaces the standard communications chip (UART) in your PC. The advantage to a 16550 is that it has a built in 6 character buffer. We have found that a large percentage of NAK's are caused by bios, and other software running concurrently with BiModem, disabling interrupt processing for too long. This causes characters to be lost. A good example of this is on AT's where the fixed disk interrupt has a higher priority than communications. Characters can not be sent or received while your machine is servicing a fixed disk interrupt. The built in buffer of the 16550 causes those characters not to be lost. Instead they are buffered until the disabling condition has passed. The buffering of the 16550 is programable. BiModem will recognize that you have a 16550 and automatically enable the buffer. When BiModem terminates it will restore the buffering state to it's pre-BiModem state. 61 Appendix H This Page is intentionally left blank 62 Index Index 16550's . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Aborted Files Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Baud Rate BiMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 BiModem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 BiBat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 8, 17, 19 BiConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 5, 9, 25 BiHot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 BiList . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 BiMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 BiMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 7 BiModem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 19 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Bios for Screen Display . . . . . . . . . . . . . . . . . . . . . . . . 28 BiPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 11 BiSelect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 BiSetup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 5 Colors Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27, 28 Comm Port BiMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 BiModem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Command format BiBat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 BiConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 BiMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 BiModem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 BiPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Configuration File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Configuration Path BiBat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 BiConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 BiMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 BiModem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 BiPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Connect Wait For . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Copyright . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i CTS/RTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 63 Index Current Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Delete Aborted Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Source File . . . . . . . . . . . . . . . . . . . . . . 14, 33, 37, 39 Transfer List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Transfer request . . . . . . . . . . . . . . . . . . . . . . . . . 15 Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13, 23 Desqview Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Program parameters . . . . . . . . . . . . . . . . . . . . . . . . 53 Destination File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13, 23 Directory Aborted Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Received Files . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Rejection List . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Sending/List of Sending . . . . . . . . . . . . . . . . . . . . . . 41 Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Double Dos Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Download Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 File List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . 12, 22 Exit BiConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 BiMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 File Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Name only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Keyboard Interrupt Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Keys Alt Right Arrow . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Alt/A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Alt/R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Alt/S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Alt/X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Control End . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Control G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Control Home . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Control Left Arrow . . . . . . . . . . . . . . . . . . . . . . . . 14 Control Page Down . . . . . . . . . . . . . . . . . . . . . . . . . 16 Control Page Up . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Control Right Arrow . . . . . . . . . . . . . . . . . . . . . . . . 14 64 Index Control U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Control X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Destructive Backspace . . . . . . . . . . . . . . . . . . . . . . . 15 Down Arrow . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Esc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16, 24 F6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Left Arrow . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Page Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Page Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Right Arrow . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Shifted F6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Up Arrow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Lantastic Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Logging Connections/Disconnections . . . . . . . . . . . . . . . . . . . . 41 File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Transfer Statistics . . . . . . . . . . . . . . . . . . . . . . . . 42 Loss of carrier Carrier Detect . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Data Set Ready . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Modem Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Operator Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Phone number edit mask . . . . . . . . . . . . . . . . . . . . . . . . . 34 Procomm Aspect File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Receive Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13, 36, 38 Rejection Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Rename the file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13, 36, 38 Screen BiConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 BiMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 BiModem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21, 22 BiPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Comm Port Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Download Defaults . . . . . . . . . . . . . . . . . . . . . . . . . 36 Filenames and Paths . . . . . . . . . . . . . . . . . . . . . . . . 40 General Options . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Screen and Colors . . . . . . . . . . . . . . . . . . . . . . . . . 27 Terminal Options . . . . . . . . . . . . . . . . . . . . . . . . . 29 65 Index Upload Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Sending Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Simple Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Size Limit BiMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 BiModem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Snow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Source File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13, 23 Sub Directories . . . . . . . . . . . . . . . . . . . . . . 14, 33, 37, 39 Telix Script FIle . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Time Limit BiMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 BiModem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Timer Interrupt Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Transfer List Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Kill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . 9, 11 Transfer List Path BiMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 BiModem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 BiPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Upload Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 File List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . 12, 22 Verify . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14, 33, 36-39 66