File Send and Request for OPUS + Compatible Bulletin Board Systems Version 2.0 Written by:

File Send and Request for OPUS & Compatible Bulletin Board Systems Version 2.0 Written by: Dionis A. Smith Copyright 1987, by Dionis A. Smith The Trading Post (305) 834-6690 Casselberry, Fl M-F: 5p-6a S-S: 24hours 1 File Send and Request --Version 2.0-- Table of Contents: 1.0 Introduction: 1.1 Purpose of FSR.................................... 3 1.2 Updations since version 1.0....................... 3 1.3 Disclaimer........................................ 4 1.4 Copyright notice.................................. 4 1.5 Credits........................................... 4 1.6 Description of files.............................. 4 2.0 Usage of FSR: 2.1 How to use FSR .................................... 5 2.2 How to use FSR (Continued)........................ 5 3.0 Conclusion: 3.0 Future Releases.................................... 5 2 File Send and Request --Version 2.0-- PURPOSE (1.1): File Send and Request is an easy to use utility that helps out when doing file sends and file requests. This program is strictly called by parameters. With some given information that you will specify through parameters FSR will make all the necessary files for your system to make a file send or a file request. UPDATIONS SINCE VERSION 0.0 (1.2): --Version 1.0 This is really the first official release. Version 0.0 was the beta test version of FSR. Any changes and errors, along with needed modifications, that was founded while testing version 0.0 were made in this official release of FSR (Version 1.0). --Version 2.0 The Code was shorten, it's now a .EXE file and about 8k less than the old FSR.COM . Also in Version 1.0 for some unknown reason (at least to me), it bombed out when trying to convert any number between 260-271 to hex (those are the only #'s that I found)..Version 2.0 now as a more stable conversion method. 3 File Send and Request --Version 2.0-- DISCLAIMER (1.3): Dionis Smith shall not be held responsible for any damage or problems that occurs to hardware, software, or peripheral devices while running FSR. All responsibility lies upon the user of the program. COPYRIGHT NOTICE (1.4): File Send and Request (C) 1988 by Dionis Smith. File Send and Requestis distributed under the "Userware" concept. You are encouraged to distribute this software to others as long as you do not charge in any way for this program. CREDITS (1.5): Bulletin board File Director was programmed by Dionis A. Smith in Turbo Pascal. Thanks to Rafael Smith for helping in the developement of FSR. Thanks to William Beebe (363/1) for helping me test FSR Version 0.0 and for his helpful suggestions and comments. DESCRIPTION OF FILES (1.6): **Note:** You should have all of the following files included in FSR.ARC [1] FSR20.EXE ---> Main FSR programs [2] FSR.DOC ---> The documentation that your reading. 4 File Send and Request --Version 1.0-- USING FSR (2.1): This program is strictly called by parameters. The first parameter instructs FSR it you would like to do a file send or a file request. It can either be -S to do file sending or -R to do file requesting. If you just type FSR without any parameters you will get a mini help screen. I will now explain the parameters. Mode: Sending FSR -S -[Type][Dest. Net/Node] [Filename] -P[Outbound] The first thing that needs to be specified is the destination net/node numbers, the matrix addresses of were you want to send the files to. You may send to as many net/node numbers as you wish. You must also specify the way in which you want it sent, such as -C363/4 for crash send to 363/4. The types are 'C' for crash, 'H' for hold, and 'N' for normal. If you care to send the same files to more than one board you would just list one after the other, such as FSR -S -C363/1 -C363/2 -C363/3 etc.. The next thing that needs to be specified is name of the files that you wish to send. This can be entered in any of the following way; SAMPLE.TXT , D:\OPUS\SAMPLE.TXT, or \OPUS\SAMPLE.TXT. If you just enter the filename, such as SAMPLE.TXT, FSR will check if that file exists in the current directory that your running FSR from and if it does FSR will read in the current path and append the whole path and name to the send file. Inorder for your system to make a file send it needs the full path. You may also have as many filenames as you wish and wildcards are also allowed, so you could do FSR -S -C363/1 -C363/2 -C363/3 D:\OPUS\*.TXT FSR.ARC etc..The last thing that needs to be specified is the outgoing path, this can be specified as -P\OPUS\OUT or -PC:\OPUS\OUT. If you do not specify a path FSR will use the opus default, \OPUS\OUTBOUND . So to summerize it all, I have listed an example below. FSR -S -C1/1 -N3/3 FSR.ARC D:\OPUS\*.TXT This example would first check if FSR.ARC exists in the current path. If it does it will proceed to append it to the send files for 1/1 and 3/3, which will be 00010001.CLO and 00030003.FLO . It will then check if any files with the .TXT extension exists in D:\OPUS . If it does it will proceed to append all the .TXT files to the send files for 1/1 and 3/3 . 5 File Send and Request --Version 1.0-- USING FSR -CONTINUED- 2.2 Mode: Request FSR -R [Type][Dest Net/Node] -O[Net/Node] [Filename] -P[Outbound] The Request mode is somewhat similar to the send. You specify the net/node numbers of the systems that you want to request from the same way you do the systems that you wish to send to. When doing a file request FSR makes a .REQ file and a .OUT , .HUT , or .CUT file(depending on what type you specify). Not specifying a type will instruct FSR to only make the .REQ file, -C363/1 will make 016B0001.REQ AND 016B0001.CLO but -363/1 will only make 016B0001.REQ. You may also specify more than one Net/Node to request from. The next thing is your net/node #, this is done as -O363/4 . The filenames of course can not have a path, just type the filename that you wish to request. If you have a file that you are requesting that requires a password you would do it as SAMPLE.TXT/PASSWORD . You may also request more thatn one file and the outbound parameter is specifed the same way as I stated above. To summerize the Request mode I have listed an example below. FSR -R -C363/1 -363/2 -O363/4 NEWS.TXT/OPUS FILES This example would create 016B0001.REQ & 016B0001.CLO for 363/1 and 016B0002.REQ for 363/2. The two .REQ files would look like this: NEWS.TXT !OPUS FILES FUTURE RELEASES (3.0) If you have any suggestions or comments pertaining to FSR please send mail to 363/4 or call: The Trading Post [305] 834-6690 Weekdays: 5p-6a Weekends: 24hours Baud: 300/1200 Software: Opus Version 1.03a 6