AUTOPRCM.BAS (or .EXE) Version 1.0 - March 1986 J. L. O'Boyle A routine to generate DOWNLOAD scripts (.CMD files) for ProComm* version 2.2 and greater. (It WILL work with version 2.1, but only with those file transfer protocols supported by that version.) This program was developed after seeing a version originally writ- ten by Keith Peterson. The one I saw had been modified for use with PIBTERM and RBBS systems only. While RBBS is nice, it's not the ONLY Host System in the world! I've included File Transfer Protocol and Host options for several popular systems. If the routine is well-received, I'll continue to update it as hosts systems (or ProComm) change. Forward: One of the nicest features of ProComm (this authors opinion only) is it's CMD processor! CMD files contain, among other things, the keystrokes you would normally have to enter manually for a given task. The ProComm documentation covers this subject much more completely and elegantly, but the "biggies" are the %I statement and the %T statement. The %I statement says.."wait until these characters are received from the host". The %T statement says.."send these characters to the host." You can see where, with a little expirementation, you could build a file to do just about anything you wanted, provided you KNEW what to expect from the host. CMD files can be built with any editor or word-processor. Many BBS systems offer ProComm CMD file examples that will completely auto- mate the logon sequence for their particular system. These need only be downloaded and modified for your individual use, ie; change the sample- name to YOUR name, etc. CMD files can be executed directly from the DOS command line when you execute ProComm. (Again, please refer to the documentation that Tom and Bruce provide.) Using this feature, it's possible to execute ONE DOS command which will invoke ProComm, execute a CMD file which will logon to a given host, go directly to the iles section, download a list of the most recent file additions, logoff the host system, discon- nect the phone line, print the downloaded list, and exit ProComm. (I do it all the time...and by using the TEF program, I do it in the middle of the night when the rates are lower!) If you haven't yet discovered the CMD feature of ProComm, maybe AUTOPRCM will help you get started! Operational Considerations: This program may be run from WITHIN ProComm, to produce an imme- diate .CMD file for file transfers. The BASIC version can be run via the DOS Shell option (ALT-F4). I've substituted the compiled version 1 name for the Editor option in my PROCOMM.PRM. While on-line to a sys- tem, the ALT-A key sequence initiates the program. Of course it can be run stand-alone anytime! I suggest that users run the program a few times to become familiar with the files produced. (AUTOPRCM produces ONE output file per run, called "DOWNLOAD.CMD") The .CMD will be activated at different prompts depending on the host system. Once you know what the FIRST command in the file does, you'll only have to get to the requisite prompt on the host system and trigger the .CMD file via ProComms' ALT-F5 key sequence. It's recommended that .CMD files, created via AUTOPRCM, NOT be run in an unattended mode! A misspelling of a file name and/or changes in host prompts may cause the .CMD to WAIT on an unexpected prompt. With that in mind, it also might be a good idea to set your "%P" parameter to a low value. The .CMD may recover and continue. If a .CMD file hangs, the ESC key will return you to manual control. It's also recommended that you have a copy of the host download directory handy when you create your .CMD file, or at least good clear notes if you're running the program dynamically. Scan the host directo- ries for the files you want, make a list of those files, and USE the list when you are running AUTOPRCM. Protocols which provide FILESPEC data, such as Kermit and Ymodem Batch, don't lend themselves to sub-directory specification. The Pro- Comm commands for these protocols have no provision for the addition of a sub-directory string. Unless otherwise specified, files downloaded using these protocols will be written to your default directory. A work-around is to have the DOWNLOAD.CMD file itself in a sub-directory, log to that sub-directory via the ProComm ALT-B command, and run the DOWNLOAD.CMD from there. This applies to Kermit, Ymodem Batch, Telink and Modem7. Minimal notes on supported hosts. RBBS - Currently only provides Xmodem protocol. (ASCII was not included in AUTOPRCM since most useful files are not stored in that form.) Since RBBS allows the download command, the file name, and the protocol option to be specified via a single string, (ie; "D;ANYFILE.BAS;X") the "DOWNLOAD.CMD" file begins with this command. IBBS - The above notes from RBBS apply here also. Exec-PC - See RBBS or IBBS. Source IBMSIG - The only protocol currently available is Sliding Windows Kermit. This .CMD starts from the "Enter File Name" prompt. PC-Board 2 - The transfer protocol you use from a PC-Board system is contained in your PC-Board user profile. Be certain that the one you choose for AUTOPRCM matches that used in the PC-Board system you contact. This .CMD starts from the "Enter File Name" prompt. FIDO - Prompts and protocols for FIDO systems are in a state of flux. AUTOPRCM supports Xmodem, Kermit, Telink, and Modem7. It has been tested successfully with the PIL Software Systems FIDO node. This .CMD starts from the "Enter File Name" prompt. PC-HOST - These systems do not use filenames for security reasons. Files are selected via number from a directory list. AUTOPRCM will BEGIN with a directory change command, and continue from there. For Kermit and Ymodem Batch, only the Dir # and File # must be specified. For Xmodem amd Ymodem, the addition of a file name is required. CRC-16 verification will be always be utilized where available. Some Variable Names.......(if you want to make modifications.) Q$ - Really a double quote, but no other way to get it into a string. RD$ - Contains "Ready for Download" string for a given host. RT$ - Contains "Ready to Transmit" string for a given host. RP$ - Contains ProComm Xfer protocol trigger string. DF$ - Contains a DEFAULT "DRV:SUBDIR" for captured files. SD$ - A settle-delay value. Needed for some systems. It's the %W"n"! PR$ - Contains the Protocol Request Message for the a given host. RPR$ - Contains the Protocol Request Response for the appropriate host. RFN$ - Contains the "Request for Filename" string for the a given host. DR$ - Contains your SELECTED "DRV:SUBDIR" string. If you find that this program is useful to you, a contribution (coupla bucks) would be appreciated, and can be mailed to: John L .O'Boyle PO Box 10596 West Hartford, CT 06110 Since this code is useless without PROCOMM, please be certain that you've also supported THAT product via contribution! If it gets to a choice between me and them, please send THEM your money! The usual disclaimer applies to AUTOPRCM. NO WARRANTIES EXPRESSED OR IMPLIED! 3 * PROCOMM V2.3 Copyright 1985, 1986 PIL Software Systems, Bruce Barkelew & Tom Smith PIL Software Systems P.O. Box 1471 Columbia, MO 65205 ProComm support BBS (314) 449-9401 23 hrs per day, 4 00 - 3 00 am CST. 4 e .CMD may recover and continue. If a .CMD file hangs, the ESC key will return you to