@L}5 _$% l0$)$$Hȱ$ UhL" `e$$%`$%`  R@W!( L(1   Y I`  d  Ld M * @  $ % CC$$)%1 Udߥ$9%: !0 S$% DD˙`  }J)Lr d M * @  $ % CC$$)%1 Udߥ$9%: !0 S$%} DD˙`  }J)Lr J  ((  p L ()   J}L= ( L 0q A    IB JC;? D W } LL  ` W )LA!  ߰")-݆ p" } $G@LL 08`Q")<2Q0 -G$Ș݆ UL# ; p8(()(0ʥ)NQ` }$GȘ݆LU )L ݆ L GȘ ݆LL )W>Z   HH)H }p h  hyhy D L> L JJ    ! LA*` BF }7'8  M HN H` 8 Z  \LdJJ!"! GFE@F (!L }EE !E^ ^ E E7EȩEdE/EȩE  D } .L }  ;F d  ;?F7F? ( .   Z D LL d } . D  L    p  E` , d)  D L) 0BM݊L݉} ML  N݆ L NLML [ TEqEHȱEqEh 0Gȹ G} HLL GɛL  LFREE SECTORS G) *Gȩ GȽG GȌ*jj >G} C8jJ3j2CD( C202C ԠBX` N 1? l LlD:RAMDISK}.COMLu L1 L ;LHL  T`  `8  ɐ     `TU  } L ? .  t`GBJ ~DEHI B V0dV!}QDEHI VF9 ,0 ,0 s0hhL  L` H hDHEh"}DEL8HI4 0 HI,0 0  9 .G VLO#},0 L4*IJ`llD1:AUTORUN.SYSNEED MEM.SAV TO LOAD THIS FILE.D8:MEM.SAV J y08 B|DEHI$} V0 0`B;DEL`?<0LV`@ʆ v s? F0Ξ05: [ BDEHI%} VY8 B V  @  /DE `E:D8:DUP.SYSERROR-SAVING USER MEMORY ON DISKTYPE Y TO &}STILL RUN DOS B;DE J  (` 9 V⪍ ઍ  -'}LLu ÝDEHILV 9 .l 9 .l  `` s$B BH(}I|DE V BLV nB,DE JLV B V BLVDEIʩ BꭝLu } 3E:}DISK OPERATING SYSTEM II VERSION COPYRIGHT 1984 ATARI CORP.A. DISK DIRECTORY I. FORMAT DISKB. RUN CARTRIDG*}E J. DUPLICATE DISKC. COPY FILE K. BINARY SAVED. DELETE FILE(S) L. BINARY LOADE. RENAME FILE M. RUN AT ADDRES+}SF. LOCK FILE N. CREATE MEM.SAVG. UNLOCK FILE O. DUPLICATE FILEH. WRITE DOS FILES P. FORMAT SINGLEL !N',}#"&))9(&*)/h)''-&؆莟R'S  vL/ˢ L }Insert DOS 2.0s, type Y Λx -}DEfHI 1莏#q! @ y0ɛ8A0,' ȅ 1 1ild! 1L!NO SUCH ITEMSELECT.} ITEM OR FOR MENU! 0 .z:*{}.|{ 1 0 0JB 18L%|DL/}%DIRECTORY--SEARCH SPEC,LIST FILE?[# 0 0 &|D3" 1L!NOT A DISK FILEN !B 1L!E# 1 !BD0}ED:}:1BJ|DE 1DEBHI 1 h0ߢ 0.1}  0?詛 1 y0YЛ 1 ;#L" ;#L! BL1TYPE "Y" TO DELETE...DELETE FILE SPEC2}COPY--FROM, TO?OPTION NOT ALLOWED697 FREE SECTORS COPYING---D8:COPY32.COMl# 0|D .L/%#3}##JB|DE 1BHID#E 1#0: B 1L!#͑### B 1#c$0SY4}S1}:## # # .#Ƚ# # 𩛙## 1,#PD#ELJ- <.BJD#E 5}1 1HH 0hh|DL%1}:̳# L% #D#EL% 1 0 . .0O% 1L!WILD CARDS NOT A6}LLOWED IN DESTINATION 0 <.|K}N 2 FORMAT. t* 5) 1L!`) 0NΞ 0 L1) 1 L!BAD LOAD FILELOAD FROM WHAT FILE?) 0 ?}0#B 1L!WHAT FILE TO LOCK?) 0 0$B 1L!WHAT FILE TO UNLOCK?DUP DISK-SOURCE,DEST DRIVES?TYPE "Y" IF OK TO US@}E PROGRAM AREACAUTION: A "Y" INVALIDATES MEM.SAV.FE! +L1   `*  70 2 2A} 0.* 1 y0 0)INSERT BOTH DISKS, TYPE RETURN^, 1 y038逍 N, 1L! ,B}C, t*  Lx+, 0 ^, 1 y0 , ,0,0 ,L+ ,I0 ,Vǭ0C}Ξ, 0 }, 1 y0C,ШC, 0K'!" H H 'h h Lx+!EF 5L1L!D,I,HhD}` NOT ENOUGH ROOMINSERT SOURCE DISK,TYPE RETURNINSERT DESTINATION DISK,TYPE RETURNE}`  `8 rL1`-* 1P* 1 y0Y`hhL!NAME OF FILE TO MOVE?- 0 0|DL% <.F},^ 1 70 0 .@L# .BJ 1  DEHIB V L1 ,} 1 70,L.  G}JB|,#P#DE 1 HI BDEHHII 1 B 1 ,^ 1 70,0La- B V,#PH},^ 1 70 0L#L!-* 1P* 1 y0Yj383}mm ݭI}}`8}``|* ? ɛ,`|:-)| / 1L!`DESTINATION CANT BE DOJ}S.SYS0 0H{ 24Δ 28/L!/) 2 Π 2 0 ξK}hAΞB,0 J 1 BDEHI,HÝDE 1HIHIDELSAVE-GIVE L}FILE,START,END(,INIT,RUN)O S0 1`BDEPHI V` S0H 1 L!M}0 0 1L~0`PLEASE TYPE 1 LETTER,0`hhL! 70 1L0L<1 ,;ɛ7,"ɛ:ݦ1ݥN}A"D|ݤD|ȩ:|ȩ|ɛ,,(/+.ީ1 1,ɛ`轤{NAMEO} TOO LONG B VL!` L1I H1EΝDL1|mDiE` V0`8d/8 i:222 1 LP}!ERROR- 164ɛ+,' 20*.. өr2 1``2TOO MANY DIGITSINVALID HEXAQ}DECIMAL PARAMETER800 0 8 00`,0'D800 H,ɛh`2L1NEED D1 THRU D8uR} ECIMAL PARAMETER800 0 8 00`,0'D800 H,ɛh`2L1NEED D1 THRU D8u05  15 2 2151^116115ύ011$r2ԭ5 3)5)5ԭx GT}@@L00)+& 2 L0=ɛ -L!1LV1L1 /3 3ȹ441L-4 v3 25 2H 2h͔5U}L3L3 2 k3U hh`DOC`QL3P1Lk0S1H /3h0B k3@ VL0LU!#$53 1181118V}1111Ε5 1Lk0552 1Ȍ1i111i11115Lk0pppB4f5&&&&&&&&^6f^6&&&&&W}&&A1@BJ D2ELVK@BHILV^Щ6 2BD2EJ VBD5EHI0 V0%5X}5 2iХiL[2 25 25`D:*.*` i@`8 ``@i `8@`0 BLV525<4Y}5`HH i ԍΗ552 ԍhh@ Lح1Э1Ѣ 24.4 24Z}4`D4E` 2BJ k3LVRH` 2BD4EhK)I JLV333 BASIC language TUR > TURBO BASIC OBJ| f}COM > MACHINE language DOC > DOCumentation PIC|MIC|FNT|MVM > Graphics AMS|MUS|MBD > Music LST > BASIC g} LISTing -Some MACHINE language programs can only be run by loading the MENU without BASIC! ------- -For s h}ome programs, XL/XE models may require a "TRANSLATOR" program (available from BELLCOM) to be loaded first! -Most i}programs are relatively self-explanatory; however, some may have separate DOCumentation files. Some BASIC programs m j}ay contain instructions in their program listings. LIST to read. -To view DOCumentation files one page at a time, k} press [START], [Return], or the Joystick Trigger to display the highlighted DOC file. Pressing the [Esc] key cau l}ses a return to MENU. -To print out a hard-copy of any DOCumentation file, [Q]uit the MENU, boot DOS, and then from m} DOS, use the (C)Copy command: D:Filename.DOC,P: -To use this great MENU program on your own disks, simply n} copy the file "AUTORUN.SYS". D:Filename.DOC,P: -To use this great MENU program on your own disks, simply ! Welcome to BobTerm 1.10! ======================== For those of you who hate to read DOCs, go ahead and lop}ad it up. I would suggest printing out the DOCs at some point, because there are several features that may not be apq}parent. One addition to the DOCs: The term "Pathname" refers to everything BEFORE the actual 11 character filename. r} For example, in D1:BOBTERM.COM, the "D1:" is the pathname. One other addition: The wait time for the dialer has bes}en slightly shortened, to account for differences in various R: emulator handlers. This just means you may need to at}dd s second or two to the "wait for carrier" time. The program is named BOBTERM.COM, [L]oad that filename from youru} DOS menu. The main DOCumentation for the term is in the file BOBTERM.DOC. Simply (C)opy this file to your printer.v} If you are using the SpartaDOS X cartridge, then you will want to read the file SDX.DOC. The file MODULE.DOC detaiw}ls operation of the two BobTerm modules provided: XEP80.BTM and CP.BTM. Modem handlers have been provided for the Atx}ari SX-212 in direct connect, the Atari 835/1030/ XM301, and the Supra/MPP 300 baud modems. Simply rename the appropy}riate file to RS232.COM, and the term will automatically load it for you. No appending is necessary. Enjoy! And rez}member: If you really enjoy using a ShareWare program, please consider sending the author a note as well as a token o{}f your appreciation. Bob Puff Suite 222 2117 Buffalo Rd Rochester, NY 14624oken ow BOB TERM v1.1 Documentation }} A ShareWare Terminal Program by ~}Robert Puff 06/11/89 GEnie Mail Address: BOB.PUFF CIS Mail Address: 7}2377,2045 Suite 222 2117 Buffalo Road Rochester, NY 14624 } BobTerm 1.1 Docs Page 1 INTRODUCTION BobTerm i}s a fully featured Multi-Tasking terminal program for ANY Atari 8 bit machine with at least 48K of memory. BobTerm has bee}n fully tested under MYDOS, SpartaDOS, SpartaDOS X, TopDos, and Atari DOS 2, along with many others. BobTerm }supports XModem, XModem-CRC, 1K-XModem, CIS Fast XModem, YModem (batch) and FModem (batch) protocols. Also supported are f}loating buffer size (depending on your machine and DOS), chat window recall, online/real-time clock, RTime8 support, a di}aling system, the ability to load modules for additional features (such as XEP80 and SpartaDOS command line support modul}es included), both RS232 ports on the 850 and P:R:, and much more! SETTING UP BOBTERM BobTerm is compat}ible with all known RS-232 interfaces, and most direct-connect modems. If your modem is connected to a Black Box or MIO, } no set-up is necessary. If you are using an 850 interface or P:R: Connection, BobTerm will automatically load the handler} from the interface; no disk handler should be used. When using any other type of interface or direct-connect modem, a d}isk-based handler is necessary. Handlers have been provided for the Atari SX212 modem, Atari 835/1030/XM301 modem, and t}he Supra/MPP 1000x modems. Note that the SX-212 handler is only needed if you are using the modem 'direct-connect', and no}t through a RS232 interface. Either load the handler prior to running BobTerm, or rename it to "RS232.COM," and place it} in your "default directory," which is drive 1 for most DOSes. To create a BobTerm boot disk, boot up your DOS }and format a blank disk. Write DOS files. Now copy the BOBTERM.COM file to this disk, and rename it to AUTORUN.SYS. If} you need a modem handler, copy the appropriate file to this disk, and rename it to RS232.COM. Users of the Black Box, MIO, 850, or P:R: connections d}o not need and should not have a RS232.COM file, since the handlers for those interfaces are built-in. Your BobTerm boot} disk has now been created. If you want to use any of the module programs for BobTerm, they should be placed on this dis}k as well. See the section entitled MODULES for more information. BobTerm loads a default dialing list when it first boot}s , so after adding all the entries to your dialing list, save it to this disk. BobTerm looks }to the "default" drive for all support files, so MYDOS and SpartaDOS X users can place all files for the term in a separate} subdirectory for convenience. All other DOSes will look to drive 1 for these files, which is why it is} a good idea to make up a boot disk as described above. SpartaDos X users please see the file called "SDX.DOC" }for more BobTerm 1.1 Docs Page 2 information. BobTerm loads right from }DOS as a binary file. Use the [L]oad Binary File option of your DOS menu, or consult your DOS manual for the correct com}mand. Be sure to DISABLE BASIC is using SpartaDOS - use the 'X' command with SpartaDOS X. HELP MENU FUNCTIONS } Modem Parameters Note: Unless otherwise stated, the command within the [] brackets is }the toggle for the command parameters. [A] TRANSLATION Changes your translation between ASCII, ATASCII, an}d VIDTEX. ASCII is the universal text standard, and should be used on most national telecommunications networks, and non}-Atari 8 bit Bulletin Boards (When in doubt, use ASCII). ATASCII is the Atari-specific text mode only usable on boards w}hich support it (typically, only Atari 8 Bit Bulletin Boards). The VIDTEX mode is actually a combination of CompuServe's V}IDTEX mode and VT-52 emulation. The ESC I sequence is the only VT-52 command not supported (because VIDTEX uses this for} a different function), but some of the additional ST-specific VT-52 codes are supported. When logging onto CIS, it is b}est to be in VIDTEX translation. Do a "GO TERMINAL" and set your page length to 23 and your columns to 40. Then make the }settings permanent. This may also be changed while in terminal mode by pressing Shift Control F. [B] BAU}D RATE The speed at which your modem and the other system's modem can receive information. Rates supported are} from 300 baud to 19.2K BAUD, but of course you cannot go any higher than your modem is capable. Note that some modem in}terfaces (namely the 850 and P:R: Connection) will not support 19.2K BAUD. Baud rates like 9600 and 19.2K are used mostly }for "null-modem" transfers, where you hook up the output of your RS-232 interface to another computer's RS-232 port, thro}ugh a special cable or adaptor. [D] DUPLEX Duplex controls how characters appear on your screen, that is,} whether they are put on your screen by the terminal program, or echoed back from the host computer. Full Duplex means th}at the characters are echoed from the host. Half Duplex means the characters are sent from your keyboard to the screen. } Full Duplex is usually the default of most online services (except GEnie), so unless otherwise stated, try Full Duplex fir}st. If you can not see what you are typing, go into Half Duplex. If you see BobTerm 1.1 D}ocs Page 3 double of each character you type, you should use full. BobTerm also supports "Echoplex". This is ena}bled by holding [START] while pressing [D]. This will cause everything to be reflected, just as a BBS does. Echoplex is }handy for answering a call, when the other person is in full duplex. Remember to switch into echo mode ONLY after connecti}ng, and out of it after disconnecting. You may change the duplex while in term mode by pressing Shift Control} D. [I] DIALING TYPE This toggles the dialing mode of your modem. PULSE dialing is supported by all telep}hone companies, but TONE dialing is MUCH faster. If your call does not go through using tone dialing, switch to pulse. } Dialing Commands [E] DIALING MENU Provides you with various lists from wh}ich you pick the phone number(s) you wish to call. See "The Autodialer and Entries" below. [F] ORIGINATE Allows }your terminal program and modem to send a carrier to be answered by another modem. An example of this is if you originally} connected using a voice line, then wished to use your modem. Use this command to connect to a BBS if you are dialing ma}nually (with a telephone). [G] SEND CARRIER Known on other terminal programs as "ANSWER MODE," this will sen}d an answering carrier to the other computer. If connecting to another person also using a term, one should Originate, a}nd the other should "Answer," or send carrier. [H] HANG UP This will hang up your modem. BobTerm first dr}ops the DTR line; if it sees that a carrier is still present, it will send a +++, wait, then ATH. This should take care }most all modem configurations. The online timer will stop. The timer will restart when dialing manually, or if Shift Co}ntrol T is pressed. System Commands [C] CAPTURE BUFFER The "Capture B}uffer" is a feature that lets you record whatever you are receiving. If there is a special message or something you want t}o save, simply enable your capture ahead of time. When you type [C], it will BobTerm 1.1 }Docs Page 4 ask you for the destination filename. Capture will then be turned on; characterized by the screen's b}order color turning red. You may toggle the capturing by pressing [OPTION]. To close the capture (ending it), use this }same option. It will ask you "Close Capture?". Press [Y]. You will now be prompted for the filename to write the file. }If BobTerm cannot save the file correctly, it will re-prompt you for a filename. While you are capturing data, }you will see the buffer count on the top status line slowly decrease. When it gets to around 256 bytes left, it will pau}se the other end, save the buffer to disk, and resume operation. You cannot change the disk in the drive you are capturing }to, until the capture is closed. You may also start capturing by simply pressing [OPTION] (without first sett}ing it up). When the buffer fills, it will prompt you for the filename to save it as. If you want to cancel the save, sim}ply press [ESC]. If you want to erase the buffer , you can clear the buffer by selecting [C]. Now hit [ESC] at the filename prompt, then hit [ESC] again to return to } terminal mode. [Q] QUIT TO DOS This will exit to DOS WITHOUT dropping carrier, allowing you to copy files}, run other programs, such as ARC or UNARC, all without hanging up! To return to online, just reload BOBTERM (you may need }to change translation, baud rate and duplex). It is not necessary to reload your modem handler, if applicable. If captu}ring was enabled, it will be saved before exiting. BobTerm will NOT perform the BOOTUP.BTM modem initialization function} if it sees that you are re-entering BobTerm, so no junk data will be sent if you reload the term while the modem is online}. [R] RECEIVE FILE Use this when Downloading, or receiving a file or files from the host computer using a} transfer protocol of XModem, XModem-CRC, 1K-Xmodem, YModem, CIS Fast XModem, and FModem. See below for "Send and Receive f}iles explained". [S] SEND FILE This is the entry point for Uploading, or sending files TO the host compu}ter. In addition to the protocols listed above, you may also do a simple text upload (the exact opposite of capturing). S}ee below for "Send and Receive files explained." [J] SYSTEM CONFIGURATION This sets your bootup terminal }and system defaults, as well as macro editing. See "[J] System Configuration" below. [K] DOS FUNCTIONS } BobTerm 1.1 Docs Page 5 This takes you to a menu which supports the most common DOS f}unctions. Use them just as you would from your DOS menu. Note that the subdirectory commands may not be supported in your} DOS (they work under MYDOS and SpartaDOS). These are the options: [1] Rename File: Format is: OLDNAME.EXT,NEWNA}ME.EXT [2] Delete a File: Asks for a filename. [3] Lock a File: Asks for a filename. [4] Unlock a File: Ask}s for a filename. [5] Format Disk: Prompts for device number to format. It will format under the current DOS}. SpartaDos X users are taken to the SDX format menu. This will format a disk in DOS 2 format if using }SpartaDOS disk based. [6] Load a File: Use this to load the Sparta XINIT file to format disks. This may also} be used in the future to load utility programs for BobTerm. Do NOT use this function with TOPDOS. } [7] Set Directory: Used to set a working directory under a DOS that supports subdirectories. [8] Create Dire}ctory: Creates a new subdirectory under a DOS that supports them. [9] View a File: Allows you to view TEXT fi}les. Use the SpaceBar to pause, and ESC to quit. [1-9] DISK DIRECTORIES Pressing the appropriate }disk device number will prompt you for a "PATH NAME or RETURN". Simply pressing [RETURN] will display the main directory} of the drive. If your DOS supports subdirectories, you may enter the subdirectory name, followed by a [>]. If you just w}anted to look at all files ending with .BAS, you could enter "*.BAS". This function pauses at each page: pressing [RETUR}N] will continue, [ESC] will abort. [J] System Configuration This area allows t}o set such things as macros, screen colors, modem port, etc., and optionally save them so that they will be loaded each tim}e you use BobTerm. There are two sub-menus that you encounter when you select this option. The first sub-menu allows yo}u to select from: [1] EDIT MACROS, ETC.: Takes you to the second menu area. [2] RELOAD DEFAULT PARAMETERS: Lets you re}load the way BobTerm was set up by your BOBTERM.CNF file. [3] SAVE DEFAULT PARAMETERS: Saves your settings to a } file called BOBTERM.CNF on the DEFAULT drive. The second sub-menu is entered by pressing the [1] key above. T}his menu is the one that actually allows you to edit your macros, screen colors, and modem port. To modify yo}ur screen colors, use the arrow keys (CONTROL is not needed) until the screen color and intensity is pleasing to you.} BobTerm 1.1 Docs Page 6 BobTerm supports a total of 16 macros. A macro is a s}eries of keys which, when pressed, will send out a pre-defined message. The macros in BobTerm are grouped by size and ty}pe of access. [A]-[H] Allows you to set the "Large Macros" of BobTerm. These macros may be up to 31 characters} long. Large Macros are accessed by pressing the SHIFT, CONTROL, and a number key (from 1 to 8) all at the same time. (}In these docs, holding SHIFT and CONTROL while typing another character will be referred to as 'SHIFT CONTROL x', where x i}s the character.) To define a large macro, just press the letter from A-H and type in the macro that you wish to store. } Note that you can use the standard Atari editing keys; use [SHIFT] [DELETE] to clear out whatever is on the line. Press} [RETURN] when you are finished entering the macro text. One special note about Large Macros A, B, and C: These macros are }updated by the dialing list. Any macros set by your BOBTERM.CNF file will be over-written by the dialing list, if used. } You may, however, reload the defaults AFTER dialing, and restore these three macros. [I]-[P] Allows you to def}ine the "Small Macros" of BobTerm. These macros are limited to 15 characters and are accessed by pressing the CONTROL an}d a number key (from 3 to 0) at the same time. Entering these macros is the same as the Large Macros. [Q]-[U] }Allows you to define five special one character macros that are controlled by the joystick in port #1 of the computer. Typ}ical uses for this would be the CONTROL-S or CONTROL-Q character to stop and start text flow on most BBSes. To execute t}hese macros, simply move the joystick or press the fire button. SPECIAL MACRO CHARACTERS There are three "}special" characters that may be included in the Large and Small Macros. These are: CONTROL-P will cause a 3 secon}d delay in the sending of the macro, then resume. You may stack as many of these characters }as you need. CONTROL-, (little heart) will cause the macro to execute as normal, but it will N}OT send a RETURN at the end of it. (Normally a RETURN is sent at the end.) CONTROL-M will send a RE}TURN, but still continue with the rest of the macro. An example of using the special macro charac}ters might be to call a BBS, send a RETURN, wait, send your password, wait, and send your name without a RETURN at the en}d. This would be coded in a macro as: ^M^P^Ppassword^M^P^Pmy name BobTerm 1.1 D}ocs Page 7 (note that the ^P means CONTROL-P, and ^M means CONTROL-M.) If you are using an Atari 850 or }P:R: Connection, BobTerm will let you use serial port #2. This is useful when null-modeming between the Atari and other }machines, because you can leave your null-modem cable connected to port #2, and your modem to port #1. No cable swapping i}s need now! You COULD hook a modem to port #2 as well, but since the carrier detect of port 2 is always forced on, BobTe}rm's dialer will not function correctly. Pressing [V] in this config menu will alternate between ports 1 and 2. This ha}s no effect if you are not using an 850 or P:R:. [S] Send Files and [R] Receive Files Explained } The first thing you will be asked for is the protocol that you wish to use to transfer a file. This choice is based }totally on what the other computer or system supports. When in doubt, try standard XMODEM, since almost all hosts suppor}t this. The choices you have and a brief description of each are: [1] STANDARD XMODEM This is a 128 byt }e block size with a mathematical checksum for error detection and correction. It is supported by almost all BBSes and te }lecommunications networks. [2] XMODEM-CRC A 128 byte block size with a cyclic checksum for error detection a }nd correction. This protocol is supported by the vast majority of BBSes and telecommunications networks. Whenever possi }ble, you should use XModem-CRC over Standard XModem because the CRC option will catch almost all errors. [3] CIS FAST  }XMODEM This is a BobTerm exclusive: when uploading or downloading from CompuServe, use this protocol; yet tell CIS tha}t you are using XModem. I developed a modification to the XModem protocol that dramatically increases the transfer speed} for the CIS host. Its almost as fast as their own Quick B! This protocol should be used ONLY on CIS, as it will not work }correctly on any other system. [4] 1K-XMODEM This protocol is basically XModem-CRC with a 1K (1024 bytes) block s}ize. The advantage to 1K XModem is that there are fewer "header" bytes sent per file, therefore, making 1K-XModem about 1}5% faster than XModem-CRC. Note that some systems incorrectly call this "YModem"; the difference being YModem is 1k XMod}em with batch capabilities. [5] YMODEM (batch) YModem is a modified 1K-XModem that allows the transfer of multiple }files BobTerm 1.1 Docs Page 8 at one time. The file name and size are sent in a he}ader block that BobTerm decodes for you. This way, you can set up a transfer of as many files as you like, and the filen}ames will be automatically saved for you! You only set up the transfer once, and there are no limits (except your disk sp}ace) to the number of files you can receive! [6] FMODEM This protocol is used on some ST BBS programs and in the Pu}ff BBS. It is basically YModem with a 4K block size. Note that this protocol is also capable of batch file transfers, a}s is YMODEM. This is best used for null-modem transfers, because it gives the highest throughput of all protocols. }[7] SEND ASCII (XON/XOFF) This is a send ONLY protocol (use "Capture Buffer" to receive) that simply dumps ASCII text }to the other computer. Since this is not an actual protocol, there is no error checking that can be done. Use this to upl}oad messages while in the BBSes message editor, etc... You can specify a delay rate of 0 through 9; 0 is no delay, and 9} is the largest. A value of 3 should be sufficient for most purposes. XON/XOFF control is supported (^S to pause, ^Q to} resume). HOW TO SEND/RECEIVE FILES For transfers using XMODEM, XMODEM-CRC, CIS FAST XMODEM, and 1K-XMO}DEM, the following applies: RECEIVE or DOWNLOAD 1. Instruct the host to send (downloa }d) a file with the appropriate protocol. 2. Press [R] from the BobTerm main menu. 3. Select the appropriate protocol!} on BobTerm. 4. Type the entire filename for the file, as you want it to appear on your disk, and press [RETURN]. "} You will be returned then to terminal mode. 5. Press [SELECT] to begin the transfer. #}SEND or UPLOAD 1. Instruct the host to receive (upload) a file with the appropriate protocol. 2. Press [S] from t$}he BobTerm main menu. 3. Select the appropriate protocol on BobTerm. 4. Enter the source filemask and filename, if you kn%}ow what it is. If not, you can enter "*.*". Bobterm will prompt you for each file it finds. Type [Y] to send tha&}t file, [N] to keep looking, or [ESC] to re-enter the source filemask. Once you have selected a file, you will be '}returned to terminal mode. 5. Press [SELECT] to begin the transfer. BobTerm 1.1 Docs (} Page 9 For transfers using YMODEM and FMODEM protocols, the following applies: )} RECEIVE or DOWNLOAD 1. Instruct the host to send a file in the appropriate protocol. For batch transfers, see t*}he host documentation for how to specify more than one file. Most often it is done by "marking" the files you want+} to download, then issuing the command to download. 2. Press [R] from the BobTerm main menu. 3. Select the appropria,}te protocol on BobTerm. 4. Provide the device name, and path name ONLY. BobTerm will take care of the filenames. (An-} example of a pathname is "D1:" or "D2:DLS>".) You will be returned then to terminal mode. 5. Press [SELECT] to .}begin the transfer. SEND or UPLOAD 1. Instruct the host to receive a file in the ap/}propriate protocol. For batch transfers, see the host documentation for how to specify more than one file. Batch s0}ending is rarely used on a BBS; it is meant more for term-to-term communications. 2. Press [S] from the BobTerm main m1}enu. 3. Select the appropriate protocol on BobTerm. 4. Provide the pathname (and filename, if known) for the files t2}hat you wish to send, one at a time. If you used wildcards, BobTerm will display each file found and query you if 3}you wish to send it. Press [Y] to add it to the list, [N] to skip it, or [ESC] to enter a new pathname. Depending on 4} the size of your path and filenames, you may be able to mark up to 100 or more files to be sent all at once! Note 5} that the memory used to hold the dialing list is used for this list of files, so you will have to reload the dialing6} list to dial a new number. To end entering filenames, simply press [RETURN] at the "Enter filemask" prompt. You7} will be returned to terminal mode. 5. Press [SELECT] to begin the transfer. The following applies to ASCII sen8}ds: 1. Instruct the host to receive ASCII text. 2. Press [S] from the BobTerm menu. 3. Select item 7 for SEND ASCII.9} 4. Provide path and filename to send. 5. Provide a delay rate. The delay rate determines the time between each cha:}racter sent. You will need to experiment with different BBSes and telecommunications services to determine what th;}e delay rate should be. A delay of 0 is none, 9 is the greatest. A value of 3 usually words ok for most BBS messa<}ge editors. You will then be returned BobTerm 1.1 Docs Page 10 to terminal mode=}. 6. Press [SELECT] to begin the transfer. FEATURES COMMON TO ALL TRANSFERS BobTerm is the ONLY 8 bit t>}erminal to remove the excess double-padding added to files by the online services. The timing used in the protocols shou?}ld be loose enough for any system, yet tight enough to maintain fast transfers. To abort any transfer, hold dow@}n the [START] key. To retry an aborted transfer, press [SELECT]. This will try the exact same transfer again. Note: ifA} the transfer aborted because of an error on your end (like a wrong protocol, disk error, etc...) that has not been correctB}ed, the transfer will simply abort again. Once you begin a transfer, you will see the BobTerm transfer displaC}y. The top line of the file transfer window displays the file name including path, followed by the file size (for batch reD}ceives only). The line under that shows the status of the transfer, the block number being transferred, and the number oE}f tries for the current block. The only time you will not see this display is when you are doing an ASCII send (you will F} stay in term mode for ASCII sends). If the transfer is aborted because of a disk error on your end, the transfG}er will first abort, then the disk error message will be displayed. Press [RETURN] twice to return to terminal mode. If thH}e transfer was aborted from thee other side or timed out, you will be returned to term mode, and the top status line willI} display "Xfer Aborted!". Holding [SHIFT] when entering the protocol number will select the ASCII <-> ATASCII trJ}anslation mode. This is used for text files only! When sending files, ATASCII files will be converted to ASCII format (CK}R/LF). When receiving, ASCII will be converted back to ATASCII (CR, CR/LF, or just LF). This allows you to let BobTerm haL}ndle the translations so you do not have run separate translation programs! Just be sure you don't accidentally enable tM}he translation on a file that is NOT a text file, else your file will be corrupted. SetN}ting up BOOTUP.BTM Some Hayes-compatible modems default to some parameters that are not what you want for standO}ard terminal use. For this reason, BobTerm will send whatever is in a file called BOOTUP.BTM on the default drive (drive 1P} for most users) to the modem at the default baud rate, when the term first loads. It will input a linR}e, send it to the modem, wait 1 second, then input again, etc., until it reaches the end of file. A control M is not needeS}d at the end of each line. My suggestion might be to have something like this in your BOOTUP.BTM file: T} BobTerm 1.1 Docs Page 11 ATX3 V1 L2 M1 E1 S7=30 &C1 &D2 You could change S registerU}s to perhaps increase dialing speed, etc... Remember it is not necessary to have this file present; it's just there in cV}ase you have need of it. Keyboard Command Summary CONTROL 3-0: 15 byte macros. (AlW}l the rest are SHIFT CONTROL:) 1-8: 31 byte macros (1-3 are the ones the Dialer updates) SHIFT CONTROL: X}Q: Recalls last two chat buffers (alternates between the 3). W: Toggle word wrap, E: Toggle the chat window in and out. Y} R: Reset the online time counter. T: Start/stop the online time counter. Y: Swap the online counter/real time on the topZ} status line. O: Takes a snapshot of the term screen, and saves it in the buffer. P: Does a screen dump of the term mode [}screen to your printer, replacing any non-printable characters with a period. M: Toggle left margin between 0 and 2. \} 9: Toggles the key click sound. When Word wrap is enabled, words will not be split if the text you are reading]} is formatted for something over 40 columns. This has no effect on captures; it simply makes reading text a little easier,^} especially if the text is formatted for 80 columns. BobTerm also accounts for backspacing in word wrap; so if it is ena_}bled and you are typing a message, you can backspace to the previous line without fear of deleting too many characters, a`}s is the case with other term programs. Word Wrap is toggled by pressing Shift Control W, and its status is seen by the fia}rst character in the top status line. You may change the left margin to 2 (incase your TV has overscan) by prb}essing Shift Control M. Note that this does NOT affect the edit window; the edit window remains in 40 columns. c} Items Saved in BOBTERM.CNF Default Drive (for any filename input) Phone List Filename Last Numd}ber Dialed Long Distance Code Tone/Pulse Dialing Mode Term Translation Term Duplex Term Baud Rate Default File Tre}ansfer Protocol Delay Rate Used in ASCII Send Protocol BobTerm 1.1 Docs Page 12 Sf}tatus of the Keyboard (in upper case or lower) Which Type of Time is Being Displayed (On=Online, Rt=Real Time) Screen Colg}ors Key Click Flag Chat Buffer Status (on or off) Word Wrap Status Left Margin Status RS232 Modem Port Number Joyq}B%DOS SYSB*)DUP SYSB SAUTORUN SYSB_HELP DOCB oREADME DOCB=|BOBTERM DOCBUSDX DOCB,MODULE DOCstick Characters All 16 Macros [E] The Autodialer and Entries Pressing [E] from r}the BobTerm main menu will take you to the Dialing Menu. The dialing menu has a number of choices as follows: [A] ADDs} AN ENTRY This option allows you to add a telephone number to your dialing menu. You will be prompted for the t}name of the entry, the telephone number, 3 macros (See section on System Configuration), the Baud Rate, the Translation, u}the Duplex, and the wait (amount of time to wait for the other computer to answer - should be 15-20 for average local callsv}). [D] DIAL TAGGED This option will continuously scan the "tagged" entries looking for a terminal connectiw}on. To tag an entry, use the arrow keys to move to the entry, and press the SPACEBAR to tag it. You will see a ">" in frox}nt of each tagged entry. To clear the tag, press the SPACEBAR again. [K] DELETE AN ENTRY To delete an enty}ry from your phone list, use the arrow keys to move to the entry, and press [K]. [M] DIAL MANUALLY By presz}sing [M], you may enter a phone number to dial from the keyboard. Note, the current system configuration will be used for {}this number (ie: baud rate, translation), and a wait time of 30 seconds will be used. [S] SAVE LIST This|} option will save your phone list to disk. You will be prompted for a device and filename, or you may use the last name us}}ed (by simply pressing [RETURN]). [V] VIEW ENTRY This option will allow you to just look at the entry. ~} BobTerm 1.1 Docs Page 13 [X] LONG DISTANCE CODE This is the code that i}s used by long distance dialing services such as MCI, Sprint, etc... Although it is not needed much anymore because of "}equal access," some long distance telcos still have special numbers to call and require a special code. Use this feature f}or those cases. To execute the long distance code, simply insert an exclamation point (!) in the phone number at the app}ropriate place (normally in the very beginning). When you enter your long distance code from the dialing menu, it is saved} as part of your configuration file. For example: LD code: 950-1111,,,,123456781 Dial: !716-247-8355 would }do the following: Dial 950-1111, wait 4 seconds, dial 123456781 (your LD code would be here), followed by 716-247-83}55. Another use for the LD code is for those who have call waiting. Insert an [!] before every number in your l}ist, and make the LD code be the numbers you have to dial to disable the call waiting feature. If you ever want to dial }the number without disabling the call waiting, simply erase the LD code. [C] CLEAR LIST This will erase th}e current list from memory. [E] EDIT ENTRY This option allows you to make changes to any of the entries in t}he dialing menu. First, select the entry to edit (by using the arrow keys), then hit [E]. Each item will be available f}or editing; press [RETURN] when done, or [ESC] to exit. [L] LOAD LIST Use this to load a new phone list fr}om your disk. This may be used to load something other than the default (if you have more than 1 list), or if you have b}atch sent some files (since the batch send function will wipe out the list in memory). [P] PRINT LIST Send}s the current list to your printer. [ESC] Exits back to the main BobTerm menu. [RETURN] Dia}ls the entry highlighted. (Use the arrow keys to move the bar to BobTerm 1.1 Docs Page 14} the desired entry.) To interrupt the dialing process at any time, press the SPACEBAR. If y}our modem supports the BUSY string when calling a number that is busy, BobTerm will detect it and re-dial or continue the s}can. The Terminal Mode Status Line While in terminal mode, the upper line of your} screen is being used as follows: WRAP:DUPLEX:TRANSLATION:BAUD RATE:BUFFER TOTAL:ONLINE/REAL-TIME CLOCK } The second line in the header is the changing status, which tells you if there are transfers pending, errors have occurre}d, etc... Miscellaneous Notes One of the unique features of BobTerm is its m}ulti-tasking. You are ALWAYS in term mode; that is, any modem input is being printed to the term screen, even if you are} not viewing that screen. The only exceptions to this are disk I/O and file transfer. You can be capturing, go do a disk} directory, and come back to term mode all without losing any data (assuming the other end supports XON/XOFF)! } Another feature is the extremely fast text screen handler. Term mode can keep up with text at 19.2K baud, even while capt}uring! When BobTerm expects input from the user, [RETURN] will accept whatever is on the screen, and [ESC] will} abort. On any filename or other line-input needed, you can use the standard Atari cursor control to edit. To delete the} entire line, press SHIFT DELETE/BACK SPACE. The edit window is another unique feature. Used mostly for the "c}onference" section on the online services, this buffer is actually 3 buffers in one. When you press SHIFT CONTROL E, you w}ill see three lines at the bottom. You may now type away in the buffer. Nothing will be sent out until you hit [RETURN]}; then the whole buffer will be dumped. The only exception to this is control characters. CONTROL A through CONTROL Z wil}l be sent when you type them; this is to allow you to pause the sender, etc... By pressing SHIFT CONTROL Q, BobTerm will} cycle through the last two "buffers" you typed and the current one. Once you press [RETURN], the current buffer gets co}pied into buffer 2, buffer 2 into 3, and buffer 1 is cleared. Another feature that might come in handy is the b}uffer screen command. Let's say you are on a BBS, and you're viewing a file that you just decided you want to capture, y}et you don't have the capture turned on. Simply press [OPTION], then press SHIFT CONTROL O. That last keypress will take} a "snapshot" of the screen, placing it in the buffer. Pressing BobTerm 1.1 Docs Page 15} [OPTION] turned the buffer on, so now you will have saved everything that was on your screen, plus everything that w}ill be coming, till you disable the capture (by hitting [OPTION] again). When you [C]lose the capture or if the buffer f}ills, you will be prompted for the filename to save the buffer. Modules } BobTerm now allows the loading of modules, to allow for new features to be added to the program without having to come out} with special versions. Two modules have been included with this versions: a XEP-80 driver, and a SpartaDOS command proc}essor interface. I will probably be writing a module to set the time for the real time counter, and a copy file function}. When the term first loads, it looks on the default drive for MODULE1.BTM. If it finds this module, it will c}ontinue and look for MODULE2.BTM, etc., up to MODULE9.BTM. This is the only reliable way modules should be loaded into B}obTerm, although you may have limited success with the LOAD A FILE option of the DOS functions. It is not necessary to h}ave modules present, but if you do have any, they should be consecutively named (module1, 2, etc.). } Support Shareware BobTerm has taken a fair chunk of my time, but has been very rewarding. It st}arted out to be just a transfer utility for null-modeming files between an 8 bit and ST, but it kept growing! T}his updated version fixes all known bugs with the earlier versions, as well as adds a few more features, one of which is th}e ability to load modules. This is the way new patches, transfer protocols, and other things can be added to the program}. If anyone has COMPLETED programs that they wish to incorporate into the term, leave me E-Mail on GEnie, CompuServe, or } my BBS . The new version also accounts for bugs in Carina II batch transfers, and other incorrectly-writt}en BBS file transfer sections. I am releasing this program as "shareware," which means this: You are encoura}ged to pass it around to your friends. What I ask is that if you like the program, consider the time that went into such a} program, and send a donation ($15 suggested) to the address listed at the top. If you have any questions/comments, plea}se feel free to write, or leave a message on one of the support boards. Thank you! Enjoy the term. Bob Puff } Support BBSes for BobTerm BobTerm 1.1 Docs Page 16} Computer World (716) 247-8355 The Moose BBS (716) 381-5139 The Breakfast Club BBS (916) 331-4722 } Many thanks to all those who helped in getting all those nasty bugs out! Special thanks to Marty & Gayle Albert and Gle}nn Garman for the documentation & testing; the CompuServe 8 bit sysops Keith Joins, Don Lebow and Bill Aycock for their m}any hours of testing, suggestions, and downloading MANY versions of the term; Jeff "Alfred" Williams for the dialer code,} and Frank Walters for his many calls and helping to get things totally bug-free. Since the first release about} a month prior to this writing, I have received many letters and messages from helpful people, too numerous to list. A b}ig THANK YOU goes out to them! BobTerm 1.1 Docs Page} 17ANK YOU goes out to them! BobTerm 1.1 Docs Page SPARTADOS X ADDENDUM to Bob Term v1.10 Documentation June 1989 by Marty Albert First of a}ll, I would like to thank Bob Puff for all his efforts to get BobTerm to its present finished form. It is indeed one of t}he best, if not THE best, terminal programs that I have ever had the pleasure of using. Thanks also, Bob, for allowin}g me to help with the beta testing of BobTerm from the start. It has been a learning experience for us both! } Looking back through the notes and letters that Bob and I have exchanged about BobTerm, it seems that many, if not a ma}jority, of the problems were directly related to SpartaDOS X. This is not surprising when you realize that Bob did n}ot have a SpartaDOS X cartridge. In other words, he did all his programming "blind" and left it to me, a mere 3000 m}iles away, to do the testing, find the bugs, and send the reports back to him. A difficult programming project at best.} At any rate, we made it to this point. I shall cover the SDX questions and concerns in the order of: } How to make it run Known problems Possible problems At the end of this section, you }will find my own "editorial" comments about the use of SDX with BobTerm and in general. If you don't have the Sp}artaDOS X cartridge from ICD, Inc. and have no plans to get one, you need not read the rest of this section. That is, } unless you just want to know. I will not be addressing anything with any other DOS than SpartaDOS X here. } How To Make It Run Look at the line in CONFIG.SYS that should read DEVICE SPARTA. You MUST have at le}ast 4 sector buffers and 5 files open. This is the default SDX setting. More won't hurt, but less won't work. }Before you run BobTerm, as noted in the main part of the documentation, you must load a device handler. I have tested Bo}bTerm with the SDX RS232 handler, and it works just fine. The MIO handler also works well. If you have the }SDX cart and an ATR8000, you may be in for a few problems. The driver for the ATR8000 that is on the SpartaDOS 3.2d }disk works well, as does the one that is on the MyDOS 4.5 disk . The handler that cam}e with the ATR8000 won't cut it for whatever reason. With this latest version, there is one or two t}hings to remember with the use of the COMMAND.COM file. If you have COMMAND.COM LOADed into memory, then you have no} problems. If, however, you prefer to NOT have COMMAND.COM in RAM, you will be in for problems if you use an external } R: handler . If, under these conditions, you exit to DOS and come back to BobTerm, the machine will l}ock up. This is due to the handler being loaded into RAM again and sliding LOMEM about. The easiest, and best, way }to avoid this is to simply include the line: LOAD COMMAND.COM in your AUTOEXEC.}BAT file. Not only will this avoid problems with the R: handler, but it will make the new Command Processor work a bit } faster. The cost is, of course, a slightly smaller buffer space. The tests that I have done used a MIO, a P:R: C}onnection, and an Atari 850. Once you have the above all done, you are ready to load the actual BobTerm prog}ram. The correct SpartaDOS X command line input is: X BOBTERM Note that the X command is REQUIRED. If you don't use that, BobTerm simply will not run for you. } Known Problems As of this writing, there are no known problems between BobTerm and Spa}rtaDOS X. The only exception is the possible problem if you don't have COMMAND.COM LOADed into memory. (see abo}ve) Note that with ALL versions of SpartaDOS, including the X cart, you MAY NOT have the TD Line on!! This will} cause all sorts of problems that appear to be random. So, just make SURE that the TD Line is OFF before you try to }run BobTerm. You don't need it anyway since BobTerm has the online time and "real" time displayed for you at all times.} Possible Problems Due to the complexity of the interface between BobTerm and SpartaDOS X,} there may be a few problems that we have missed. See my editorial comment at the end of this section for a few reas}ons why. One problem that seemed to die a slow and hard death, and may very well still be kicking in} there someplace, is screen flickering. Normally, this takes the form of control characters being flashed rapidly on the} screen, as a whole or in just one area. I think that Bob has tracked down all of these pesky things, but is more th}at slightly possible that we have both missed one. Another problem that seems to be totally fixed is an inabilit}y to read drives that have been reassigned via the MIO. This manifests itself as a failure to read a directory or access in any other way a drive that has been reass}igned through the MIO menu and that persists after you exit to DOS until you do a cold start. Again, this proble}m appears to be gone. With the new Command Processor, there are a few things that are not REALLY problems, but y}ou should be aware of them. First off, the SDX cart's ARC programs may NOT be used from within BobTerm! If you try }it, the system WILL crash. COPY, RENAME, ERASE, UNERASE, etc. are all valid and work fine. Editor}ial Comments It should be noted that the comments that follow are my own and in no way reflect the opinion of Bo}b Puff or any other person. In other words, if you don't like what you read here, yell at me. As I said abo}ve, there were many problems along the way to BobTerm, especially when it came to making it work with SpartaDOS X. These} were compounded by the fact that Bob lives in New York and I live in California and that Bob didn't have an SDX cart}. But, these facts don't account for all the problems that we ran into. SpartaDOS X is, by far, the most co}mplex DOS ever written for the Atari 8-bit computers. Perhaps the complex DOS for ANY 8-bit machine. It has abiliti}es and versatility far beyond that of any other DOS and is rivaled in speed of operation only by MYDOS. All this power an}d ease of user interface has a price, however. The price is complexity in programming. To be able to ef}fectively access the abilities of SpartaDOS X and make it do the things that it can do, the programmer needs to be able t}o find out what is going on with the DOS. The manual that comes with SDX is not much help there, nor should it } contain volumes of technical information. The manual is for users, not programmers. The single biggest probl}em that Bob had was finding the information needed to make his program work with SpartaDOS X. S}ince the first edition of these notes for SDX and BobTerm, ICD has contacted me with a small bit of information. They ar}e indeed working on getting some tech notes (or what-ever name you wish to pin on them) out for the cart. Such thing}s as a list of more of the Kernal routines, tables of the memory use, and so on. The problem is that since SDX was w}ritten on an MS-DOS machine with a proprietary cross-assembler that was, basically at the time, experimental, the doc}umentation SDX programs themselves are the comments in the source code. For those not familiar with the use of s}ource code in this type of a situation, it is VERY difficult, at best, to pull of information that makes any reasonab}le amount of sense. At any rate, Craig Thom of ICD has assured me that this is a project that ICD is aware of an}d that ICD knows that it needs to be done. The problem is simply that ICD is still a relatively small company, and w}ith all the other projects that they are working on, something (I suspect several somethings) has to wait. For now, that} is the SDX technical data. From a business standpoint, this makes sense, and I'm sure that now, as always, }the results will be well worth the wait. Credits for this Section Again, thanks to Bob} Puff for BobTerm, as well as his other many fine programs for the Atari 8-bits. Keep on codin', Bob! All beta  }testing of BobTerm and SpartaDOS X was done on the following system: Atari 800XL with 256K via RAMBO XL upgrade } R-Time 8 clock SpartaDOS X cartridge, version 4.20 1 megabyte MIO ATR8000, 64K Atari 1050 drive with US D }oubler chips Twin DSDD drives via ATR8000 Star NX1000 printer via ATR8000 Atari SX212 modem via MIO or ATR8000  } Avatex 1200 modem via MIO or ATR8000 Atari 850 interface ICD P:R: Connection  } Magnavox Color Monitor 40 Action! cartridge for debugging Text Pro 3.2r for all letters Also I would like }to thank my wife, Gayle, for her help in testing and for her ideas and for just listening to me scream at Spa}rtaDOS X, Bob, the modem, and computing in general. Between Gayle and I, we have downloaded about 4000 files tot}alling well over 10 megabytes and uploaded about 2800 files totalling over 5 megabytes, all with BobTerm. Other than} a few problems when, due to an oversight, the protocol code was goofy, we have had NO problems. Thanks to the local }Sacramento BBSs of The Breakfast Club <(916)331-4722>, ACCESS <(916)423-2544>, and SELECT <(916)392-7279> for putting} up with all the transfers. If you have any problems with BobTerm and SpartaDOS X, please contact Bob with }a COMPLETE description of the problem. If you can't reach Bob, drop me a note and I can pass it on to him. } Marty Albert 4005 Manzanita Ave. #6-216 Carmichael, CA 95608 GEnie Mail} == MARTY.A 216 Carmichael, CA 95608 GEnie Mail8 Documentation for XEP80.BTM and CP.BTM -------------------------------------- } BobTerm version 1.10 now supports modules, so programs can be added to the main term without having to } re-write the whole thing. Two modules have been written and provided in this package; more will most likely fo}llow at later dates. Place the modules you wish to use in the same directory/}drive as BOBTERM is located, and name them MODULEx.BTM, where x is a number between 1 and 9. There is no} special order that needs to be observed when loading them; just that the first one starts with 1, etc. } XEP80.BTM --------- This is a driver for the XEP-80 80 column box from } Atari. The driver directs ONLY the term mode screen to both the XEP and the standard term screen. It takes up} 256 bytes of buffer space, so you will see your buffer size decrease when it initializes. The driver do }es not display any menus or the exit window. The XEP is just too slow to keep re-drawing the term mode s!}creen and help screens, and does not have the capability of scrolling in one window and not in another. "}This is unfortunate. In any event, you will need two monitors to see the term mode screen on the XEP, and the help/editing screens on your computer's output. Th$}e XEP driver will keep the computer's screen on at all times, and will still print to the computer's screen %} as well. The driver makes a valiant attempt at supporting VIDTEX/VT-52. All command&}s are supported, but a couple of them take a bit of time for the XEP to perform, and result in lost bytes'} if the data rate is high. A few of the special function VIDTEX/VT-52 commands will only affect the XEP'(}s screen, and will not affect the computer's screen. The XEP can handle 2400 baud and perhaps 480)}0, but no higher. The VIDTEX/VT-52 functions perfectly at 300 and 1200 baud, but two of the commands wil*}l cause lost characters at 2400 or higher. CP.BTM ------ +} This module is for SpartaDOS users only. It replaces the DOS functions with a command processor interfa,}ce, so that you have access to DOS while online. Since it replaces the old DOS functions, it takes up no-} additional memory. You can quit to DOS, do whatever is necessary, then reload the term to do the same .}thing, but this is quicker, especially if you are using floppy drives. SpartaDOS 3.2 an/}d SpartaDOS X are the only two versions supported. If you are using SpartaDOS X, please refer to "SDX.TX0}T" for more notes. When you type [K] to get to the DOS functions, you will see the fami1}liar Dx: prompt. Operation is basically the same as if you were really in the DOS's command processor, e2}xcept that after each command you have to press a key. To change drive numbers, type in the new prompt <3}"D2:"> and hit RETURN (twice). Also screen output is re-directed so that it will "page" printing - when the 4} screen fills, you are prompted for a key press; it will then clear the screen and continue. If you press ESC w5}hile at a page prompt, a break is simulated; so you will see the message "Break Abort" immediately follow6}ing. Pressing ESC at the command line prompt will return you to BobTerm. Most all func7}tions should work here, including COPY, AINIT, CWD, etc.. You may load XINIT, but do NOT select any DOSe8}s to be written to the disk. BobTerm allows the use of memory from around $51FF down to LOMEM, so as long 9} as programs don't use anything higher than $51FF, everything is safe. Commands such a:}s TIME or DATE that require input may not work; this is something I am working on. When;} using SpartaDOS X, you will notice the screen will turn itself off and on quite a bit. This is a fact of <} life with SDX due to it being on a cartridge. The main reason for the "paging" of the output was so that you can=} see what is going on before it scrolls off. It is best to LOAD COMMAND.COM prior to ru>}nning BobTerm when using SDX. This eliminates certain memory conflicts with handlers, although you can g?}et away without loading COMMAND.COM if you are using a Black Box or MIO. @} That's it for now! Remember you need to rename whichever module(s) you wish to use to MODULE1.BTM, A} MODULE2.BTM, etc., for them to be loaded into the terminal. Hopefully more modules will be on the way! B} Bob Puff 06/12/89 terminal. Hopefully more modules will be on the way! 4