Monster Media 1994 #1

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

/ Monster Media 1994 #1 / monster.zip / monster / BBS_UTIL / RBTCH242.ZIP / EXTRA.ZIP / FAKEXFER.ZIP / FAKEXFER.DOC next >

Wrap

Text File | 1992-12-15 | 17KB | 410 lines

----------------- F A K E - X F E R ----------------- A File Posting Utility for SysOp's Running RBBS-PC and RBatch FAKEXFER.EXE - Version 1.05 Dan Shore - SysOp December 18, 1992 THE SHORELINE BBS 301-946-2771 (v.32bis) DGS Systems Group (Wonder) A. What is FAKEXFER? ----------------- Have you ever called another BBS to "suck files" and then have to go through the hassel of posting them manually to your FMS/.DIR file system? Well this program was written to try to ease that burden of a SysOp's Life. By using this program along with RBatch, you can now get assistance with your file posting. Once you have created your "FakeXfer" file (see Section C - Running FakeXfer), you then run RBatch (see Section D - Using RBatch with your FakeXfer) and start to categorize your uploads. If the file has a FILE_ID.DIZ or a DESC.SDI inside of it, then that description will be used for the file currently being processed. See the .doc file in CAP2DOZ.ZIP for an easy way to prepare .DOZ files from captured file lists. If the file does not have an internal description file, and if you have created a .DOZ (Description Outside of Zip - (C) 1992 Dan Shore) file, this description from the .DOZ will be used. Also, if the .DOZ file contains a category code, then this category code is used and no intervention is needed by the SysOp when RBatch is processing files. In other words, AUTOMATIC FILE POSTING WITH MINIMAL WORK BY THE SYSOP!!! RBatch will always try to process a FILE_ID.DIZ or DESC.SDI file before using a .DOZ file, unless the configuration file is setup to have .DOZ's take priority. ******************* AUTOMATED UPLOADS ********************** If a file has a FILE_ID.DIZ or a DESC.SDI and a .DOZ file is also present, RBatch will use the description from the FILE_ID.DIZ or DESC.SDI and then use the category code from the .DOZ file. This means that once a SysOp/user starts an upload from RBBS with this scenario, no intervention is needed as RBatch takes care of everything!! If there is no FILE_ID.DIZ, DESC.SDI or .DOZ file, then RBatch will prompt you for the file description, and category code. B. What is a .DOZ file? -------------------- The .DOZ file was created for the type of files that cannot accept a FILE_ID.DIZ or a DESC.SDI. What types of files are these do you ask? Well, any file that cannot accept another file "inside" of a file (.GIF's are an excellent example). Remember that the .DIZ or .SDI are just text files that are added into compressed files. Also, .DOZ files are very useful when you are posting files locally to your BBS with RBatch & FakeXfer. As you decompress a file to read the doc's to figure out what you have just "sucked" for your BBS, you can cut and paste a section of the documentation that describes the file and put that in the .DOZ The best way to create a .DOZ is to screen capture the file listing on the BBS that you are downloading the files from. Then run the CAP2DOZ program which will read the captured file listing, prompt you for a filename to process and ask you what category that file should have. It then makes the .DOZ file for you with out having to re-type the file description or do any editing of the captured file list. ************************************************************************** * REMEMBER THAT THE .DOZ FILE CONTAINS "ALL" THE FILENAMES THAT YOUR ARE * * UPLOADING OR POSTING LOCALLY. DO NOT USE MORE THAN ONE (1) .DOZ FILE * * WITH RBATCH OR IT WILL NOT WORK. * ************************************************************************** B-1. The .DOZ File Structure ----------------------- The .DOZ filename can be anything as long as it is a legal DOS filename. The internal structure of a .DOZ is as follows: {FI dflat8.zip window x Description of file goes here with a maximum line length of 75 characters and a maximum of 10 lines {FI jiklan.zip window Description of file goes here with a maximum line length of 75 characters and a maximum of 10 lines {FI ved201.zip utils n dan shore Description of file goes here with a maximum line length of 75 characters and a maximum of 10 lines Line 1 : ALWAYS STARTS WITH A {FI and then the filename. Note that there is a space between the {FI, filename, & the category code. Do not use a path for the file. (The {FI is the Smart Text variable for FileName in RBBS, hence it seemed logical to use this as part of the structure) ##### The text MUST START AT THE LEFT MARGIN. (The example above starts in the middle of the screen for ease of reading). The category code is the code that a user would normally type when prompted to categorize a file. This is NOT THE THREE DIGIT CODE in your FMS. For example if your DIR.CAT had this entry: "GAMES","GAM","All Games" The .DOZ entry would look like this: {FI WARRIORS.ZIP GAMES This is a great graphical warrior game The next field is if you are going to be uploading a personal file to the BBS. If you use a "X", this tells RBatch to not prompt the user to see if the file is a personal upload or not. If you use the following codes: N = UserName for personal file S = Personal Upload to SysOp (No additional field needed) L = Personal Upload to security level D = Personal Upload to a distribution list If you use one of these codes, the RBatch EXPECTS to see a value in the next field after this letter (except for the SysOp personal upload). Line 2 thru 11 : The description of the file to be posted, with a maximum line length of 80 chars and a maximum of 10 lines. --------------------------- IMPORTANT ------------------------------------ The .DOZ file is uploaded to a BBS as part of the Uploading process and can be sent first, in the middle, or last, it does not matter. REMEMBER THAT THE .DOZ FILE CONTAINS "ALL" THE FILENAMES THAT YOUR ARE UPLOADING OR POSTING LOCALLY. DO NOT USE MORE THAN ONE (1) .DOZ FILE WITH RBATCH OR IT WILL NOT WORK. When using .DOZ files for local posting by the SysOp, you want your .DOZ file TO BE IN THE SAME DIRECTORY as the files that FAKEXFER is processing. After the fakexfer file is generated, the .DOZ file will be copied to the upload directory with all the other files. If the .DOZ file is not in the upload directory, RBatch will not recognize the it, hence you will be prompted for descriptions/categories. -------------------------------------------------------------------------- C. Running FAKEXFER ---------------- You can run FAKEXFER two ways. First just type the program name and the opening menu will appear as shown below. Or type the program name with the five command line parameters needed as follows: FAKEXFER FAKEXFER.DEF C:\JUNK C:\DAN D:\NEW Y X ^ ^ ^ ^ ^ ^ 1 2 3 4 5 6 Note that these numbers correspond with the descriptions following the example below. Parameter #5 is optional. If ommited or if the letter "X" (no quotes) is used, the program deafults to "N" for this parameter. Parameter #6 is if you wish the progrm prompt you to " Strike any key to exit program" or not. If you put the letter "X" (no quotes) here, you will not be prompted. NOTE: If you do not use parameter #5, you can put "X" (no quotes) as parameter #5 and FAKEXFER will then: 1. NOT PROMPT YOU TO HIT ANY KEY 2. NOT CHECK FOR DUPLICATE FILES If you just type the program name itself a color menu will appear just like the example below: F A K E - X F E R By Dan Shore -- SysOp THE SHORELINE BBS (301)946-2771 DGS Systems Group - (Wonder) Enter Name of the XFER-?.DEF File to create (Filename Only, No Path) : xferup.def Enter Path/Directory where XFER File should be created : c:\junk Enter the Full Path to the directory of the files to be processed : c:\files Enter Path/Directory where Processed Files are copied to : d:\uploads Copy files if they exist in Destination Directory (Y/N/X) : Note that your repsonses are at the ":" prompt. I will cover each item now. 1. This is the name of the Xfer file that you wish to create. Do not create a Xfer file that might conflict with your BBS, if you are doing this while the BBS is up. (Example: XFER-1.DEF - Don't use) 2. The program will create the xfer file that you specified in line 1 in this directory. Do not use the same directory that you specify in the 3rd or 4th response! 3. This is the directory that contains the files that you wish to post to your BBS. The only files in this specified directory should be the ones that are to be posted!! The program will search this directory to get the file size and the filename of EACH FILE for preparation of the "FakeXfer" file. Note that your .DOZ file should also reside in this directory if you are using one. 4. This is where the processed files will be COPIED to, once the program has generated the "FakeXfer" file. 5. If the files exist in the destination directory, should FAKEXFER still copy/process the file. If you put the letter "X" here, this parameter defaults to "N" and FAKEXFER will not prompt you to "Strike any key to exit program". NOTE: This parameter is optional and if omitted, the program will DEFAULT to "N". Notes: Make sure that the path given for the "Fake" Xfer file is the same as the one in your special RBatch Configuration File. (Line 11 of your RBatch Configuration File) Make sure that the path to copy the processed files to, is the same as your Upload Path in your special RBatch Configuration File. (This is the first line in your RBatch Configuration File) D. Using RBatch with the "Fake" Xfer File -------------------------------------- I recommend that you copy one of your RBatch Configuration files to make a specific file for the "FakeXfer" program to work with. Make sure that you have the correct "FakeXfer" filename listed in this new configuration file. Now to be able to use the "Fake" Xfer with RBatch type the following command, which will allow RBatch to run in "Local" Mode. RBatch C:\Fake\Batchup.Cfg 0 Z 2 ^ ^ ^ ^ ^ 1 2 3 4 5 1. RBatch program name 2. Name of configuration file with path to it, if in a directory other than the current directory. 3. Port Number (0 = Local) 4. Protocol Letter (Your Choice) 5. Node Number (A "Local Node" Number is highly recommended) Notes: - If you use a Node Number other than a local one, the last person who was on that node will be given upload file credits, so using a local node will prevent this. This way you the SysOp who uses the local node will get the file credits! This makes you look very good in your BBS Statistics if you keep them for the SysOp! - Why if you don't use a local node number will someone else get file credits? Good Question....10 Points for you! What happens is that RBatch reads the Node Record for the username and then gives that use the file credits. - In your RBatch Configuration file, for this "Fake" Xfer posting, the callers file that you list will be the one that RBatch also posts information to. If you wish, you can create your own callers file just for this program or again use the callers file for the Local Node. **** - If you are running RBBS 17.3C or below, RBatch will have to make its own DORINFO?.DEF file. To be able to tell who the user is, RBatch reads the NODE RECORD of the message base (1st field - this file format is described in Appendix A of the RBBS manual). Why is this important? Well, if you are posting files locally and you only have a single node system (no local node), the username that was last on the BBS, (name in node record) will be used in the dorinfo?.def file. So, this means that user will get the file credits for the files that you are posting. How do you get around this? There are three ways: 1. Make a local node on your BBS, and sign on at least once. Since the SysOp is the only one with access to the local node, the SysOp name will always be used as the name in the dorinfo?.def file. 2. Log onto your Node1 as the SysOp before posting files using RBatch to your BBS. #### 3. Get a copy of a dorinfo?.def file and rename it DORINFO0.DEF Then in your configuration file, specify "NO" to have RBatch make a configuration file and list DORINFO0.DEF as the file for RBatch to use. Make sure that you edit the dorinfo file so that it has COM0 as the port number, and SYSOP as the first name and a blank line as the second name. I RECOMMEND THIS METHOD IF YOU DO NOT USE A LOCAL NODE ON YOUR BBS!! E. FILE_ID.DIZ, DESC.SDI, or FILENAME.DOZ ? ---------------------------------------- If the file that your are posting has a .DIZ or .SDI, that file will be used for the description. If it does not and a .DOZ file exists in the upload directory, then the description will be used from the .DOZ file. If none of these files exists, RBatch will prompt you for a description. .DOZ files can take precedence over .DIZ/.SDI files by turning on this option in the configuration file. (See Sample.Cfg) F. Upload Categorization --------------------- If you specify a category code in the .DOZ file, RBatch will compare this code to your DIR.CAT file, and if there is a match, you will not have to categorize the file. If the file contains a .DIZ or .SDI and you also have a .DOZ file, the file description will be used from the .DIZ/.SDI file, and the category will be used from the .DOZ file. This makes the local file posting totaly automated once you start RBatch. G. Screen Capture from another BBS System and posting the files to your BBS with Minimal Editing! - Use the Progrm CAP2DOZ ------------------------------------------------------------ ** READ THE .DOC FILE IN CAP2DOZ.ZIP for more information ** on using CAP2DOZ with captured file listings Here is what a file listing might look like before editing: FILENAME.ZIP 234556 08-18-92 Here is a file that you all should have in your file library. It is slick, fast and the best thing since sliced bread. Download today and try it out for yourself. - or - FILENAME.ZIP 234556 08-18-92 Here is a file that you all should have in your file library. It is slick, fast and the best thing since sliced \ bread. Download today and try it out for yourself. Now here is the same file after editing it for a .DOZ file either editing by hand or using CAP2DOZ: {FI FILENAME.ZIP MISC Here is a file that you all should have in your file library. It is slick, fast and the best thing since sliced bread. Download today and try it out for yourself. Note that the size and date are edited out which brings the first line to the left margin, but the rest of the text need not be touched at all!! RBatch will read this file and "strip" out all the extra spaces and post this file to your FMS or .DIR system properly.