Monster Media 1994 #1

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

/ Monster Media 1994 #1 / monster.zip / monster / HAM / PCFU199H.ZIP / PCFU.DOC < prev next >

Wrap

Text File | 1994-01-23 | 69KB | 1,430 lines

┌──────────┐ ┌─────────┐ ┌─────────┐ ┌────┐ ┌────┐ └┐ ┌───┐ │ │ ┌────┐ │ └┐ ┌───┐ │ └┐ ┌┘ └┐ ┌┘ │ │ │ │ │ │ └─┘ │ │ └─┘ │ │ │ │ │ └───┘ │ │ │ │ └──┐ │ │ │ │ │ ┌──────┘ │ │ │ ┌──┘ │ │ │ │ │ │ │ │ ┌─┐ │ │ │ │ │ │ ┌┘ └┐ │ └────┘ │ ┌┘ └┐ │ └───┘ │ └────┘ └─────────┘ └────┘ └─────────┘ The Planet Connect File Utility Version 2.00 (rough draft) Copyright (c) 1994 by Genesis Information Service Written by: John Morano Documentation by: Adam Morano 1:391/1180 @ FidoNet 8:391/1180 @ FamilyNet adam@cybernet.cse.fau.edu john.morano@f1180.n391.z1.fidonet.org Page 1 1 Introduction . . . . . . . . . . . . . . . . . . . . . . 3 1.1 What is PCFU . . . . . . . . . . . . . . . . . . 3 1.2 Features . . . . . . . . . . . . . . . . . . . . 3 1.3 System Hardware and Software . . . . . . . . . . 3 1.4 License and Disclaimer . . . . . . . . . . . . . 4 1.5 My ramblings . . . . . . . . . . . . . . . . . . 4 2 Planet Connect Technology . . . . . . . . . . . . . . . 5 2.1 Network structure . . . . . . . . . . . . . . . 5 2.2 File transfer and recieve structure. . . . . . . 6 2.3 A word about ACONFIG.SKY . . . . . . . . . . . . 7 3 Program Setup and Overview . . . . . . . . . . . . . . . 8 3.1 How PCFU works . . . . . . . . . . . . . . . . . 9 3.2 Setting the PCFU enviroment. . . . . . . . . . . 10 3.2.1 PCFU=. . . . . . . . . . . . . . . . . . 10 3.2.2 DIRCMD=. . . . . . . . . . . . . . . . . 11 3.3 PCFU <> Dos relationship . . . . . . . . . . . . 11 3.4 Easy Setup . . . . . . . . . . . . . . . . . . . 11 3.5 PCFU.CFG . . . . . . . . . . . . . . . . . . . . 12 3.6 The PCFU Files . . . . . . . . . . . . . . . . . 14 3.6.1 README.1ST . . . . . . . . . . . . . . . 14 3.6.2 PCFU.DOC . . . . . . . . . . . . . . . . 14 3.6.3 PCFU.NEW . . . . . . . . . . . . . . . . 14 3.6.4 PCFU.EXE . . . . . . . . . . . . . . . . 14 3.6.5 PCFU.CFG . . . . . . . . . . . . . . . . 14 3.6.6 PCFU.IDX . . . . . . . . . . . . . . . . 14 3.6.7 PCFU.LOG . . . . . . . . . . . . . . . . 14 3.6.8 PMOV.LOG . . . . . . . . . . . . . . . . 14 3.6.9 UPLDMSTR.LOG . . . . . . . . . . . . . . 14 3.6.10 PTIC.MSG . . . . . . . . . . . . . . . . 14 3.6.11 RECEIVED.NOT . . . . . . . . . . . . . . 14 3.6.12 FREQTHEM.NOW . . . . . . . . . . . . . . 14 3.6.13 RUNBBS.NOW . . . . . . . . . . . . . . . 14 4 Program Commands an Switches . . . . . . . . . . . . . . 15 4.1 Command Line Structure . . . . . . . . . . . . . 15 4.2 DUP command. . . . . . . . . . . . . . . . . . . 15 4.2.1 X option for DUP . . . . . . . . . . . . 16 4.3 MOV command. . . . . . . . . . . . . . . . . . . 16 4.3.1 X option for MOV . . . . . . . . . . . . 17 4.4 -c switch. . (config). . . . . . . . . . . . . . 17 4.5 -o switch. . (originate) . . . . . . . . . . . . 18 4.6 -t switch. . (terminate) . . . . . . . . . . . . 18 4.7 -s switch. . (safe). . . . . . . . . . . . . . . 19 4.8 -x switch. . (index) . . . . . . . . . . . . . . 19 4.9 -f switch. . (filespec). . . . . . . . . . . . . 20 4.9.1 -fTIC switch (special filespec). . . . . 20 4.10 -l switch. . (log) . . . . . . . . . . . . . . . 21 4.11 -m switch. . (movlog). . . . . . . . . . . . . . 21 4.12 -p switch. . (post). . . . . . . . . . . . . . . 21 4.13 -k switch. . (keep). . . . . . . . . . . . . . . 22 4.14 -r switch. . (reprocess) . . . . . . . . . . . . 22 4.14 -v switch. . (verify). . . . . . . . . . . . . . 22 Page 2 5 Networking and Multitasking. . . . . . . . . . . . . . . 23 5.1 Running PCFU in a network. . . . . . . . . . . . 23 5.2 Running PCFU under Desqview. . . . . . . . . . . 23 5.3 Running PCFU with other multitaskers . . . . . . 23 5.4 File sharing . . . . . . . . . . . . . . . . . . 23 5.5 Moving vs Copying Files. . . . . . . . . . . . . 23 6 Epilog . . . . . . . . . . . . . . . . . . . . . . . . . 23 6.1 Credits. . . . . . . . . . . . . . . . . . . . . 23 6.2 Thanks to. . . . . . . . . . . . . . . . . . . . 23 6.3 Technical notes. . . . . . . . . . . . . . . . . 23 6.4 Technical support. . . . . . . . . . . . . . . . 24 6.5 Suggesting option for future versions. . . . . . 24 Note !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PCFU is "NOT" an upgrade tp PCUTILS, there is no conversion program to run, and it won't self install. You are going to have to take the time to sit down and read the documentation, install the EXE files, set up a new config file, and also make a few changes to your existing batch files to get it to work properly. My appoligies in advance for this inconvienence but I could not do what I wanted with PCFU and make it 100% compatable with the older PCUTILS. Page 3 1. Introduction: If you are reading this file I hope you are a memeber of the Planet Connect Satellite Data Service. Why? Because this file was written for that service, and will most likely be of very limited value to you if you are not part of PC. So don't waste your time by reading any more of this boring doc file and go do something constructive like playing Mortal Combat. :-) 1.1 What is PCFU: Planet Connect File Utility, PCFU for short, is an automated batch type file generator,driver and shell that has options to keep logs of what it has done so you can verify that the operation went the way you wanted it to go. In a single command line you will be able to automate file manipulation processes that would take hundreds of lines in a batch file to duplicate, saving you time and effort maintaining your BBS. 1.2 Features: The following are the primary features built into PSCU, that will help you do file manipulations under the PC enviroment. I think you will find that with a little bit of experimenting that you will be able to do exactly what you want to do with any files now and in the future that could be sent over the satellite system. 1. Delete duplicate files in the inbound satellite directory or any directory of your choice. 2. Move inbound files to the holding directory and/or tossing directory or any other directory of your choice. 3. Move any files in any directory to any other directory in date and time order so as to proccess them in and orderly and less congested enviroment. 4. Keep detailed logs of everything that PCFU has done so that acutate tracking and debuging of the system can be accomplished. 5. Pre-proccess TIC type files in matched pairs and optionally create a message suitable for posting on your BBS with the file information and file disription. 6. Self maintaining logs and indexes to keep then at a resonable size, you no longer need to manually delete oversized logs by hand. 7. Keep track of all files that were not received,isolate files that are received but do not show up on the listing of files that should have been received on that day. 8. Create a a flag file to let your BBS software know that all files on the files of the day list have been received. 1.3 System Hardware and Software: Any 8088,286,386,486 type machine with 256K of free memory, and having a minimum of 10 file handlers available for PCFU. The system needs to be working within a DOS 'based' enviroment, this includes MS DOS 3.3 or greater, PC DOS 3.0 or greater, 4DOS, a DOS window within WINDOWS, or a Desqview window set to the above memory requirments. And of course it would help if you were running the Planet Connects Satellite equipment. :-) Page 4 1.4 License and Disclaimer You are granted a limited license to use and copy this software within the terms and in accordance with that license as follows. The software enclosed in this archive is copyrighted meterial, you may use this software for as long as you like provided you do not violate the copyright. You may not make any changes or modifications to the software including but not limited to decompiling, disassembling, or otherwise reverse engineer the software. You may not rent or lease it to others. You may not modify the documentation in any way except for the addition of personal notes within said documentation as long as those notes do not become a part of the documentation distibuted with this software. Information within this documentation is subject to change without notice as is the content and funtionality of the program PCFU. Genesis Information Services and the authors of PCFU and the documentation make no warranty of any kind,expressed or implied, with regard to the funtionality of the software or documentation, and shall not be liable in any event for incidental or consequential damages in connection with, or arising from, the use or inability to use said material. Your use of this software and documentation beyond the casual reading of the documentation for informational purposes will constitute a legal and binding contract provisioned by the above License and Disclaimer wording. PCFU and it's documentation can be freely distributed under the SHAREWARE concept with a registration fee of $1.00 (one dollar) 1.5 My ramblings: Well you just went through the legal crud, sorry about but my legal beagle said it had to be there. Now a few of you are going to ask why the stupid $1 registration charge, well here's the method to that madness. With PCUTILS I asked for a netmail message if you used the program. Well I got two (2) I'm using it messages and five (5) gripe messages that it didn't work. (4 of the 5 sent another message saying it wasn't PCUTILS that was causing the problem) Well anyway I guess only 7 systems on the PC network are using it :-). I've got about 1000 hours of coding time in PCFU and I sure would like to hear from you guys and gals, so legally your obligated to put a buck in an envelope and send it to me if your using PCFU. I got a buck in my pocket that says I won't be flooded with bucks in the mail. < big grin > Well enough of me, lets get on with the show, and have fun. John..... Page 5 2. Planet Connect Technology What can I say besides, 'Sliced Bread' and 'Up Yours Ma Bell.' With the addition of a relitively inexpensive modem like receiver and satelite dish to your BBS, you will connect your system to a file distribution system that is on the threshold of todays ever expanding personal information distribution network. Planet Connect is a data delivery service capable of sending you very large amounts of information in a relitively short time frame, Although the PTCCMAIN program supplied by PC does a perfect job of receiving those files and storing them on your disk drive, you still have a very large task at hand in trying to sort out that information and put it into a form that your normal mail tossers and file handlers can work with, without choking on the massive volume that is recieved and without getting the FidoGods and InternetGods mad at you for sending massive duplicate message into the system due to the multipal repeat tranmissions PC does each day to guarentee the receipt of those file. That is where PCFU steps in and does a lot of that grunt work for you. 2.1 Network structure The basic configuration of information flow within the Planet Connect network can be seen in a simple form as follows: Inbound: Land Line > Planet Connect Mail System > Satellite Uplink > Satellite > Satellite Downlink (your receiver) > PCFU > Your Tosser > Your BBS Outbound: Your BBS > Your Scanner > Land Line > Planet Connect Mail System So as you can see it is not much different then the normal land line base information transfer system of: Inbound: Land Line > Modem (your receiver) > Your Tosser > Your BBS Outbound: Your BBS > Your Scanner > Land Line > Hub Mail System Just a few more piece of equipment to pass through and a few extra programs to handle the information flow, and get it to the point where your normal BBS software thinks it has just come in over a land line based modem instead of a satellite receiver. PCFU was designed to be that middle man that takes the work out of the conversion. Page 6 2.2 File transfer and recieve structure We will go into more detail later but for now in it's most simple form this is what your system will have to do to get all those files that Planet Connect is sending your way. When PTCCMAIN exits on a signal from the satellite link receiver it sets an errorlevel of 100. It also sets an errorlevel of 0 if you manually exit the program using the exit function. What the error level of 100 means to you and PCFU is that the satellite data delivery system has come to the end of a cycle of files it is sending out. By using an errorlevel traping line in the batch file your running PTCCMAIN from it is a simple matter to detect this exit and redirect your batch file execution to any point in the batch sequence you would like. The following is a simple example of a batch file showing what I mean. Note: The commands used for PCFU in the following batch file force a dup check & pre tic proccess to be done creating a message for posting, and moves all 0000FFFF.* files to the default tossing directory. :START PTCCMAIN IF ERRORLEVEL 100 GOTO CYCLE IF ERRORLEVEL 0 GOTO END :CYCLE PCFU DUP PCFU MOV PCFU MOV -fTIC -p GECHO TOSS IF EXIST RUNBBS.NOW GOTO BBS GOTO START :BBS IF EXIST RUNBBS.NOW DEL RUNBBS.NOW RA -mC:\FD\FD.EXE*M -E20 -N%1 -A0 IF ERRORLEVEL 190 GOTO START IF ERRORLEVEL 150 GOTO MAILIN IF ERRORLEVEL 20 GOTO BBS IF ERRORLEVEL 3 GOTO MAILOUT GOTO BBS :END In the batch file PTCCMAIN is run and when the program exits at errorlevel 100 (end of cycle) an errorlevel trapping line redirects the execution of the batch sequence to a tag called CYCLE. At this point PCFU is run and if configured properly, makes some sense out of the 20 meg of files you got in the last 2-3 hours. Then PCFU exits the batch file runs a tosser (GEcho). The RUNBBS.NOW file is created by PCFU if the BBS_START option set in PCFU.CFG is within the window you select to NOT cycle back to the PTCCMAIN program loop and forces your bbs package to take control of the computer until an event occurs that sets an errorlevel of 190, at which point the batch file recycles to run PTCCMAIN again. So as you can see with a few simple batch file commands and the use of PCFU your system, even running on a single non-multitasking computer can receive the days mail from Planet Connect and also be available for users to call during curtain hours of the day. Or you can have a Desqview window doing that double duty. Page 7 2.3 A word about ACONFIG.SKY Just the same way that your front end mailer uses a configuration program to tell it where to deposit files received over the modem. PTCCMAIN uses a configuration to tell it where to shove files received over the satellite. And that config file is called ACONFIG.SKY Here is the ACONFIG.SKY file that is currently being used on my system. # net grp usr maj min top type destination limit :rulebase, *, 1, *, *, *, *, disk, C:\STATLITE\SKYINFO/, * :rulebase, *, 2, *, *, *, *, disk, C:\SKYDATA/, * :rulebase, *, 3, *, *, *, *, disk, C:\SATELITE/UPDATES/, * :rulebase, *, 4, _SKYID, *, *, *, disk, C:\SATELITE\PERSONAL/, * :rulebase, *, 5, *, *, *, *, disk, C:\SATELITE\FIDO/, * :rulebase, *, 6, *, *, *, *, disk, C:\SATELITE\WEATHER/, * :rulebase, *, 7, *, *, *, *, disk, C:\SATELITE\TV/, * :rulebase, *, 8, *, *, *, *, disk, C:\SATELITE\DIR08/, * :rulebase, *, 9, *, *, *, *, disk, C:\SATELITE\DIR09/, * :rulebase, *, 10, *, *, *, *, disk, C:\SATELITE\DIR10/, * :rulebase, *, 11, *, *, *, *, disk, C:\SATELITE\DIR11/, * :rulebase, *, 12, *, *, *, *, disk, C:\SATELITE\DIR12/, * :rulebase, *, 13, *, *, *, *, disk, C:\SATELITE\DIR13/, * :rulebase, *, 14, *, *, *, *, disk, C:\SATELITE\DIR14/, * :rulebase, *, 15, *, *, *, *, disk, C:\SATELITE\DIR15/, * :rulebase, *, 16, *, *, *, *, disk, C:\SATELITE\DIR16/, * :rulebase, *, 17, *, *, *, *, disk, C:\SATELITE\DIR17/, * :rulebase, *, 18, *, *, *, *, disk, C:\SATELITE\DIR18/, * :rulebase, *, 19, *, *, *, *, disk, C:\SATELITE\DIR19/, * :rulebase, *, 20, *, *, *, *, disk, C:\SATELITE\DIR20/, * Now while I don't profess to be 100% knowlegable about all the ins and outs of how and why this file works with the main PTCCMAIN programs, I do know this, If a program that comes over the satellite has a marker on it that matches the line in this config file that says rulebase, *, 5, it is going to end up on my system in the directory C:\SATELITE\FIDO and is it is marked for rulebase 15 it will end up in the directory C:\SATELITE\DIR15 The second thing that I am aware of is that if a file comes into the system that PTCCMAIN cannot find a match for it will be placed on the C:\SKYDATA directory of the receiving system. From this you can see that a properly set ACONFIG.SKY is of the upmost importance and you will need this information when you setup the PCFU.CFG file. Note: Any changes you make to the ACONFIG.SKY file will not take effect until you run the MAKECFG.EXE program that come with PTCCMAIN. Page 8 3. Program Overview Here is what PCFU will and won't do. PCFU will MOVE/COPY (Move files across the same drive or Copy file from one drive to another in a multidisk and/or multinode enviroment. Check for duplicate files coming into the system over the satellite using the filename, filesize, archive date and archive time to do the match and delete files that have an exact match within a certain number of days (configurable).It will NOT delete files with the same name that are received in the alloted time frame if the filename matches but the filesize, date or time has changed from the last time a file of that name arrived on your system, instead it will move/copy this CHANGED files to a SAFE directory. Move/copy all inbound files to a holding directory and/or a tossing directory or just leave them where they are if you would like to toss directly from where PTCCMAIN deposited them. Pre-process *.TIC type files in a orderly paired match of the *.TIC and the file that is associated with it, and will optionally generate an ascii text message of the files that arrived along with thier discriptions. Keep track of the Files_To_Be_Sent files list (UPLD.LST or date.LST) sent to it and if a change in the list is detected it will add the new list to a master log with a date and time stamp of when the file was first detected. Keep a log of the files received between the detection of the UPLD.LST or date.LST changes and maintain a log called RECEIVED.NOT of the files that were on the list but have not been received, and build a file called FREQTHEM.NOW that can be used to file request any files that were missed so you can automaticly file request them. Maintain system logs to a reasonable size so manually log deletes will not be needed. Copy ANY file to ANY directory using ANY filespec and log it to ANY log file you want. Work under any version of DOS and all dos based LAN systems or multitaskers. Manage the use of your computer to allow it to be a part time satellite receive system and also be used as a computer for your BBS. An easy way to get both satellite use and BBS use from a single machine without the need for a multitasker. As for what PCFU WON'T do, it won't toss mail or post directly to your message base, and it has nothing at all to do with the actual downlink operation of the satellite files. And it isn't crippled in any way, shape or form, registered or not. Page 9 Things 'I' won't do: Release the next version before it's ready to be released. I'm sure that we will find a few bugs in this version of PCFU and I will attempt to correct them as quickly as I can. But just as I did with the conversion of PCUTILS to PCFU, if I'm not satisfied with it,it stays right here getting the acid test till I am. :-) 3.1 How PCFU Works Note: The following discription assumes DEFAULT setting, the highly configurable options in PCFU will be explained later. Here's where we take the mystery out of how PCFU does it stuff. If you understand this 'COPY TEST.TXT ..\HOLD >> COPY.LOG' you are well on your way to understanding how this program works, nothing up my sleeve, no mirrors, and it didn't take a Phd in programing to do it, just some simple logic and the fact that nobody told me it couldn't be done the way I wanted to do it. Here we go....... When you first fire up PCFU it read the command line to see if there is enough info in it to do something it knows how to do. Next it reads the configuration file to gain the knowledge of the defaults and options that YOU decided YOU wanted it to know about. If all goes well to this point it looks for a file called PCFU.BSY and if found will assume it is running under a multitasking system and that another copy of PCFU is running on another node/task and will abort exacution of the program. You have 60 sec. to override the abort sequence, if you DO override it the PCFU.BSY file will be deleted automaticly so the program won't hang each time it fires up like PCUTILS use to, forcing you to go in and delete the file by hand. If you force an override and PCFU is actully running on another node, you can take it to the bank that you are going to have a big mess on you hands.... ;-) If the DUPx function is called: Next it looks for a new UPLD.LST (I hope Boyd doesn't change this on me I worked long and hard on this little routine) If it finds the file it will trigger the appending of this file to a master log, creates of a file with file names in it that were on the last upload list but did not get detected by the program as received, FREQTHEM.NOW, the creation of a new file to track files as they are received from the new UPLD.LST called RECEIVED.NOT and the optional reprocessing of files that were received but were unknown at the time. At this point the program processes the duplicate index file PCFU.IDX removing all lines in it (this is a plan ascii file) that are older then the number of days you have defined with the x option when you call it. Note: x defaults to 5 days if the x option is left blank. Now is when it gets to have fun, it runs through your inbound file directory and deletes anything that is in there that has an exact match in the PCFU.IDX, renames the PCFU.IDX to OLD.IDX and then in a single operation move the NEW and CHANGED files to HOLDING and/or SAFE directories and rebuids a new index files with the new files in it, the OLD.IDX is appended to the end of the new one. The last things PCFU does is looks into your config file to verify if the timing window for your BBS is set and if so creates a file called RUNBBS.NOW (just a semaphore) that you can use to redirect your batch file after exiting PCFU and purges the log files by the option set in your config file.. Page 10 If the MOVx function is called: The program defaults to move x number of 0000FFFF.??? files from your holding directory to the tossing directory. This function is used mainly in a lan or multitask enviroment where you have another node or task call for a file transfer on the fly. Here is a section of my batch file that tosses only one mail bundle at a time, so the node isn't rapped up for hours tossing an endless supply of mail. Note: Please let me explain something here, before you get a big chuckle out of it like a friend of mine did. My A: drive is a 1 Gig drive that is remaped on a Lantastic network. I was running out of drive letters, so everyboby send in your buck so I can afford NetWare. :-) ...clip... :MOREMAIL ALLFIX MGR GECHO TOSS GSTATS 3 GECHO IMPORT RAMSG LINK :MAILOOP IF EXIST A:\SIM\SOMENODE.BUSY GOTO STARTBBS PCFU MOV 1 IF EXIST A:\FDPRO\INMAIL\0000FFFF.??? GOTO MOREMAIL ...clip... What this does is allows me to toss the inbound mail during the early afternoon hours when the bbs is not as busy, but if a node becomes busy during the mail tossing process the file SOMENODE.BSY is detected and the toss loop is aborted until any node cycles through again and starts the mail toss cycle up. It just keeps the tossing node from slowing down the whole system when it's banging the poo-poo out of the hard drive. So as you can see if you are running under a lan or multitasking system you can use the MOV function of PCFU to more or less manage some system resources. 3.2 Setting the PCFU enviroment As mentioned in the previous description of how PCFU works, PCFU first searches out a config file, and a PCFU environment variable can be set to have PCFU look for that config file in a certain directory on your system. 3.2.1 PCFU Enviroment Variable (optional) If you set a enviroment veriable of something like: SET PCFU=C:\PCFU in your batch file that you fire the system up on then the program will look for a file C:\PCFU\PCFU.CFG first and then look in the current directory that you call PCFU from for the default config file named PCFU.CFG We will go into detail later in how to override the config file from the command line. Page 11 3.2.2 DIRCMD Enviroment Veriable PCFU will attempt to detect a DIRCMD environment variable that is set, reset it to NUL on the fly and restore it back to the original way it was on exiting. But if you have trouble with PCFU wiping your DIRCMD variable out (I guarantee I can do that) then reset it in your batch file when you exit a PCFU call. I.E. DIRCMD=/p 3.3 PCFU <> Dos relationship Yes I will admit that PCFU still uses one DOS call to do its dirty work 'DIR' it is a quick and dirty way to get all the information I need as fast as possible without having to reinvent the wheel and until I come up with a routine that does a better job, faster, than DIR can we're both stuck with it, and I'll just put some chrome hubcaps on the wheel. 3.4 Easy Setup PCFU should not be hard to set up on your system, If I where setting it up as someone that was not the author I think I would use the following steps: 1. Unzip the archive to a directory of it's own called PCFU 2. Read the docs 3. Set may enviroment variables 4. Read the docs! 5. Build a PCFU.CFG file 6. Read the docs!! 7. Modify the batch files to reflect the new commands 8. Read the docs!!! 9. Cross my fingers and fire this baby up........ By the way, if all else fails READ THE DOCS !!!!! I spent more time writing them then the program. Note: PCFU will not create directories or sub-directories that are listed in your config file, but you can verify all paths and files, if the -v switch is set on the command line, The -v switch will verify the config file ONLY and force the program to exit. So when you think you have the config file correct just run this from the command line: PCFU DUP -v before using the program for the first time. Page 12 3.5 PCFU.CFG Enclosed in this archive is a file called A_PCFU.CFG, it is a sample config file that you can modify for your own use on your system. The default name of the config file that PCFU looks for is PCFU.CFG so it would be best to copy the sample file to a file by that name and then go ahead and modify the PCFU.CFG to your needs. The search that PCFU uses for its config file is: 1. -cpath\file switch 2. PCFU= path using the file name PCFU.CFG 3. Current directory using the file name PCFU.CFG The following are options that can be used within the config file with an explanation of each one. Note: PCFU will attempt to make some sense out of all lines in the config by using some string concatination routines so you can get a little sloppy when working with the file but don't go overboard. SATELITE_IN=C:\SATELITE\NEW\ and satelite_In = c:\ SATElITE \ nEW Would all mean the exact same thing to PCFU. BBS_NAME= The Name of your BBS, at present this is only used as a header in the PTIC.MSG file. SATELITE_IN= The directory that PCFU will default to when doing the dup check of new and changed inbound files. Note: When using the DUP command the -o switch will override the SATELITE_IN directory. HOLD_DIR= The directory that new files will be moved to after the duplicate check is made. By leaving this entry out of the config file NO intermediate holding area will be used. HOLD_DIR will default to the same directory as TOSS_DIR and the DUP command will move files directly to the TOSS_DIR from the SATELITE_IN directory. Note: When using the DUP command the -t switch will override the HOLD_DIR directory. When using the MOV command the -o switch will override the HOLD_DIR directory. TOSS_DIR= The directory your MAILER exspects to find inbound mail and files in, Under lan and multitask systems the default MOV command will move 0000FFFF.??? files from the HOLD_DIR to the TOSS_DIR. And the MOV -fTIC command will move paired TIC files here. Note: When using the MOV command the -t switch will override the TOSS_DIR directory. Page 13 SAFE_DIR= The safe directory is used when a file is received before the x days defined in the DUPx command and is found to have the same name as a file in the dup index but the file size,date or time has changed. These may be good files or badly recieved files so they are quaretined until you can take a look at them. I use a line in my batch file that makes MBUTIL post a private message to me if anything ends up in this directory. Note: If an attempt is made to move a new file to the hold or toss directory and a file is found in that directory with the same name then the new file will also be moved to the safe directory. THIS DIRECTORY MUST BE DEFINED !!!!!!!!!!!!!! INDEX_DIR= PCFU builds indexes, some permanent and a whole lot of temporary ones, so that it doesn't frag your disk by just dumping them all over the place I would suggest that you set this to something like C:\PCFU\INDEX\ The following default index's are are created here. PCFU.IDX, RECEIVED.NOT,FREQTHEM.NOW and PTIC.MSG Note: The -x switch will overrride the PCFU.IDX only. LOG_DIR= Where the logs that PCFU creates should be stored only the following default logs are created here. PCFU.LOG, PMOV.LOG and UPLDMSTR.LOG Note: The -l switch will override the PCFU.LOG The -m switch will override the PMOV.LOG The last thing that PCFU does before exiting the program is to attempt to cull logs that are over the size set in LOG_SIZE. The -l and -m switches will reset the path for that cull of the logs. Just the same as they reset the path/filename. SEM_DIR= This points to a semaphore directory where you would like the files RUNBBS.NOW and PCFU.BSY created. UPLD_FILE= This is a full path and file to the UPLD.LST that is sent out each day, and was included in the event that PC decides to change the file name in the future. An -subdate switch can also be used with this option and can be pointed at the dated upload list that PC has been sending out as of late. I.E. UPLD_FILE= C:\SATELITE\FIDO\-subdate.LST and the file that will be searched for would be something like 01-16-94.LST in the FIDO directory. Note: Make sure this points to the UNLOCKED file, if you run PCFU from another node/task and PCTTMAIN is running somewhere else. (it is in two places on the disk) START_BBS= The start time (24 hour clock 00:00 = midnite) that if PCFU exits and finds the time to match the window set by this start time and within the BBS_RUN= hours length set. PCFU will create a file called RUNBBS.NOW in the INDEX_DIR BBS_RUN= A intiger number from 0 to 23, setting the number of hour from the START_BBS time to create the RUNBBS.NOW file on an exit from PCFU. ( Continued on next page ) Page 14 REC_ALL If this option is set in the config file and the RECIEVED.NOT file is empty (all files on the UPLD.LST have been received) the the timing window set by the START_BBS and BBS_RUN will be overriden and the RUNBBS.NOW file will be created when PCFU exits. LOG_SIZE= Number of maximum lines to keep in your log files. 0 or not defined = No automated log culling. SEARCH_IN= This is a multiline config option where you can define all of the paths that you want PCFU to search when it if looking for files that have been received, it uses these paths to cull the RECEIVED.NOT file. 3.6 The PCFU Files 3.6.1 README.1ST Do I need to explain this one? 3.6.2 PCFU.DOC This is a full documentation file on how to use and abuse PCFU. 3.6.3 PCFU.NEW Any updates and fixes to PCFU will be listed in this file. 3.6.4 PCFU.EXE Planet Connect File Utility executible. 3.6.5 PCFU.CFG Default PCFU configuration file (sample: A_PCFU.CFG) 3.6.6 PCFU.IDX Default PCFU index file (created by PCFU.EXE {DUP}) 3.6.7 PCFU.LOG Default PCFU log file (created by PCFU.EXE) 3.6.8 PMOV.LOG Default PCFU move log (created by PCFU.EXE {MOV}) 3.6.9 UPLDMSTR.LOG Default PCFU UPLD.LST master log 3.6.10 PTIC.MSG Ascii message for posting (created by {MOV -fTIC}) 3.6.11 RECEIVED.NOT Files in the UPLD.LST that have not been received 3.6.12 FREQTHEM.NOW File created from RECEIVED.NOT with a list of files that you may want to file request via land line. 3.6.13 RUNBBS.NOW File created by PCFU that can be used to flag your batch file to restart the BBS instead of cycling back to PCTTMAIN. Page 15 4 Program Commands and Switches PCFU [with no options] Quick Help screen will be displayed to you for instant online help. PCFU DUP? or PCFU DUP ? Quick Help screen for the syntax of the DUP(x) command with all options and switches. PCFU MOV? or PCFU MOV ? Quick Help screen for the syntax of the MOV(x) command with all options and switches. Command Syntax: PCFU DUP x -cPATH\FILE -oPATH -tPATH -sPATH -xPATH\FILE -lPATH\FILE -k -r -v PCFU MOV x -cPATH\FILE -fFILE -fTIC -oPATH -tPATH -sPATH -lPATH\FILE -mPATH\FILE -k -p 4.2 DUP command: DUPx (Note: Do not put a space between DUP and x) DUP is a prime command with defaults and is used to: 1. Purge duplicate files in the directory of your choice. Default: SATELITE_IN= pointed to in PCFU.CFG Options: SATELITE_IN= pointed to in config file set by -c switch or any directory pointed to by the -o switch (see below) 2. Move/Copy NEW or CHANGED files in the directory that was checked to another directory of your choice, or just leave them where they are and exit PCFU so that you can do what you like with the files after they have been dup checked. Default: HOLD_DIR= pointed to in PCFU.CFG or TOSS_DIR= pointed to in PCFU.CFG if a holding directory is not defined. Options: HOLD_DIR= pointed to in config file set by -c switch or TOSS_DIR= pointed to in config file if a holding directory is not defined. or any directory pointed to by the -t switch 3. Use and purge the index of your choice when duplicates are checked, with the -o and -x switches (see below) multiple index files can be created for the many different directories defined in the A_CONFIG file and all be managed with one simple to use program. Default: INDEX_DIR= pointed to in PCFU.CFG Options: INDEX_DIR= pointed to in config file set by -c switch or any index pointed to by the -x switch Page 16 4. Maintain the PCFU.LOG to include culling that log to a set size each time you run PCFU so you don't have to manually delete or edit it to keep it from taking over your hard drive. Default: LOG_DIR= pointed to in PCFU.CFG Options: LOG_DIR= pointed to in config file set by -c switch or any log pointed to by the -l (L) switch 5. Maintain a running log of the 'files of the day' list sent out to each system stamped with the date and time received for each file. Default: UPLD_LIST= pointed to in PCFU.CFG Options: UPLD_LIST= pointed to in config file set by -c switch 6. Maintain a RECEIVED.NOT (got it from my son) list that originally starts with the UPLD.LST and as files are received off the satellite the file names a checked against the remaining files in the RECEIVED.NOT and deleted from that list. At the time that a new UPLD.LST is received thet list is checked to see if any files remain unreceived. If found the file is renamed to FREQTHEM.LST and a new RECEIVED.NOT is created from the new UPLD.LST Default: INDEX_DIR= pointed to in PCFU.CFG Options: INDEX_DIR= pointed to in config file set by -c switch the -x switch will NOT override this path so a good index directory path has to be defined in the config file. 4.2.1 X option for DUP x can be any number from 0 to 365 or can be left blank and is used by PCFU to manage the size of the index file by removing any entries in the index file that are older then x days prior to doing the duplicate check of a directory. If x is set to zero (0) then no purging of the index is done on the execution of the DUP command and if left BLANK A DEFAULT VALUE OF FIVE (5) is assummed. FIVE (5) is the recommended value and has proved to work well on my system when tossing Fido mail and files. Examples: PCFU DUP 3 (dup check, purge index older then 3 days) PCFU DUP0 (dup check do not purge index) PCFU DUP (dup check purge index with default of 5 days) 4.3 MOV command: MOV is a root prime command with defaults and is used to: 1. MOVE/COPY x number of files in the directory of your choice to any other directory in date and time order and to log each file in a log file of your choice as they are moved. Default: From: HOLD_DIR= pointed to in PCFU.CFG To: TOSS_DIR= pointed to in PCFU.CFG Using: FILESPEC= 0000FFFF.* Page 17 Options: From: HOLD_DIR= pointed to in config file set by -c switch or any directory pointed to by the -o switch To: TOSS_DIR= pointed to in config file set by -c switch or any directory pointed to by the -o switch Using: FILESPEC= defined by using the -f switch or the special FileSpec -fTIC 2. If used with the -fTIC FileSpec and -POST switch PCFU will create an ascii output message of the received tic files in a format suitable for posting in a Netmail or EchoMail area or adding to a log. 4.3.1 X option for MOV x can be any number or can be left blank and is used by PCFU to control the maximun number of file that the MOV command attempts to MOVE/COPY from the ORIGITATION directory of your choice to the TERMINATION directory of your choice. If x is set to zero (0) NO files will be moved and if left BLANK, ALL files will be MOVED/COPIED from the originating directory to the destination directory. Examples: PCFU MOV 5 Move 5 0000FFFF.xxx mail bundles from the HOLD_DIR directory to the TOSS_DIR directory. PCFU MOV Move ALL 0000FFFF.xxx mail bundles from the HOLD_DIR directory to the TOSS_DIR directory. PCFU MOV0 -fTIC -p Create the PTIC.MSG file using the *.TIC files in the HOLD_DIR directory, but don't move any files. PCFU MOV3 -fPCUSENET.* -oC:\SATELITE\NEWSGRP -tC:\FRED\BAG Move 3 PCUSENET mail bundles from the directory called NEWSGRP in date and time order to a directory called BAG. 4.4 -c switch Syntax: -cPATH/FILE The -c switch is used to override the default PCFU.CFG file information and can be used to point the program to a different configuration for the execution of the command at run time. PCFU uses the following search path when looking for the configuration file. 1. Look for file pointed to by -cPATH\FILE switch 2. Look for the file PCFU.CFG in the path of the enviroment veriable set by using SET PCFU=path 3. Look for file PCFU.CFG in the current directory that PCFU is called from. 4. Aborts execution of the program and notify you of failure to locate a suitable configuration file. Page 18 Example: PCFU DUP5 -cC:\PCFU\NEW.CFG Notes: If using the -c switch a FULL path MUST be defined and is checked for validity, if the file CAN NOT be found the program will try to work its way down through the search sequence and if another PCFU.CFG file is found the program will use the first one it finds and notify you on the SCREEN of which config file is being used. 4.5 -o switch Syntax: -oPATH The -o switch stands for ORIGINATE PATH and is used in a case where you would need to override the SATELITE_IN or HOLD_DIR path that is defined in the PCFU.CFG or the configuration file pointed to by the -c switch, since PCFU was designed to delete duplicate file in the inbound satellite directory and move files from the holding directory to the toss directory, It will work great in default mode for that, but what about all the files in the Internet newsgroups you would not want to toss them over and over again. So you have a few choices here. 1. Rework the Planet Connect config file to dump all files to one directory and then use the DUP command to delete the dups. 2. Build another PCFU.CFG file to reflect the directory that the news groups are in and call it with the -c switch. 3. Call PCFU more then once with the following lines in your batch file. PCFU DUP4 (normal dup check) PCFU DUP4 -oC:\SATELITE\NEWSGRP (dup check of NEWSGRP directory) I think you can see that you could get pretty creative here and take care of ANYTHING that Planet Connect could send to you in the future. Example: PCFU MOV5 -oC:\SATELITE\RIME\ Notes: Only one (1) -o switch can be used on a command line Trailing (\) is optional The -o switch will override the -c switch if called together 4.6 -t switch Syntax: -tPATH The -t switch stands for TERMINATE PATH and is used in a case where you would need to override the HOLD_DIR and/or TOSS_DIR path that is defined in the PCFU.CFG or the configuration file pointed to by the -c switch, since PCFU was designed to move NEW and CHANGED files in the inbound satellite files directory to an intermediate HOLDING directory or directly to the TOSSING directory or to move files from the holding directory to the tossing directory it works great for that purpose. But what what about all the files in the ROSENET area that you would like to check for dups and then move to the C:\QWK\TOSSTHEM\ directory of proccessing ? You quest it, and I think you are starting to catch on to just how flexible PCFU can be. Page 19 Example: PCFU DUP1 -oC:\SATELITE\ROSE\ -tC:\QWK\TOSSTHEM\ Notes: Only one (1) -t switch can be used on a command line at a time Trailing (\) is optional The -t switch will override the -c switch if called together 4.7 -s switch Syntax: -sPATH The -s switch stands for SAFE PATH and is used in a case where you would need to override the SAFE_DIR= path that is defined in the PCFU.CFG or the configuration file pointed to by the -c switch, since PCFU was designed to move NEW and CHANGED files in the inbound satellite files directory to an intermediate HOLDING directory or directly to the TOSSING directory or from the HOLDING directory to the TOSSING directory it is possible that a CHANGED or duplicate file (same file name but different file size or date/time stamp) could be found in the inbound directory that if moved to the HOLDING or TOSSING directory could overwrite and existing file there that has not been proccesed yet so if the program detects a filename match it will move the file to the directory pointed to by the SAFE_DIR= path pointed to in PCFU.CFG or the configuration file pointed to by the -c switch, or it will override that path by using the -s switch if defined on the command line. PCFU DUP -sC:\SATELITE\SAFE\ Notes: Only one (1) -s switch can be used on a command line at a time, trailing (\) is optional The -s switch will override the -c switch if called together NO double filename check is done when moving files to the SAFE directory, if a duplicate filename exists in the safe directory it will be overwriten with the new file. ( it's on the things to do list ) 4.8 -x switch Syntax: -xPATH\FILE The -x switch stands for INDEX and is used in a case where you would need to override the INDEX_DIR= path that is defined in the PCFU.CFG or the configuration file pointed to by the -c switch, Lets suppose you want to dup check and index the INTELEC Qwk files, well since the extension on the file is always QWx, if you had those files being loged to the default PCFU.IDX, you would most likely have those files dumped to the SAFE directory every day because the file name would be the same but the file size, date and time would change from day to day. So how about if we use a different index and set the x setting in DUP to only one day and when your sure that the files have changed delete that index and be ready to go for it again the next day. Page 20 Example: PCFU DUP3 -oC:\SATELITE\INTEL\ -tC:\INTELTOS\ -xC:\INDEX\INTEL.IDX Notes: Only one (1) -x switch can be used on a command line at a time, trailing (\) is optional The -x switch will override the -c switch if called together Hint: PC changes the files that it uplinks around 7:30 AM EST so if you would delete the INTEL.IDX at 7:30AM each day the index would be ready to take that days mail with no false dup problem. 4.9 -f switch Syntax: -fFILE The -f switch stands for FILESPEC and is what makes the move command so much fun to experiment with. A FILESPEC of 0000FFFF.* can be set on the PCFU.CFG file as a default, or any other for that matter. But you can override that filespec using the -f switch so that any wildcard file search can be done, and the files that match that search can be moved/copied in a date and time order from any directory of your choice using the -o switch to any directory of your choice using the -t switch, or from the default HOLD_DIR to the default TOSS_DIR if ether the -o or -t switch are not used. The moved files are also logged to the PMOV.LOG in the default LOG_DIR or in a log file of your choice by using the -lPATH\FILE switch. Note: See -fTIC switch for examples 4.9.1 -f switch Syntax: -fTIC PCFU also uses a special -fTIC filespec to tell it to do a special move function on *.TIC type files and it's attached file using the following logic in it's search. First PCFU catalogs al the *.TIC files in the HOLD_DIR or the directory of your choice using the -o switch, next it reads a *.TIC file to find out some information about its file attach. I then attemps to move the attached file to the TOSS_DIR or any directory of your choice using the -t switch and then moves the *.TIC file that matches it also. It will continue to move matched pairs of files until it has move all the file that are associated with the *.TIC's that it cataloged. The only log that is kept of the moved TIC's is the file called PTIC.MSG that will be created if the -POST switch is set when you call -fTIC.It will also have other information stored in it about the files,such as Filename, Date, Time, discription all in a neat little message for those diehards that still use the old TICK file proccessor and wish that they could make a message to post on the BBS's. The -fTIC switch WILL post failed move attempts to the PCFU.LOG or any log of your choice using the -lPATH\FILE option Page 21 Examples: PCFU MOV5 -fCRS.* -oC:\SATELITE\CRS Move 5 CRS.xxx mail bundles from the CRS directory to the TOSS_DIR directory. PCFU MOV -f*.* -tC:\FD\MAIL Move ALL files from the HOLD_DIR directory to the C:\FD\MAIL directory. About the same as doing a: XCOPY C:\SATELITE\INBOUND\*.* C:\FD\MAIL But keep in mind you now have a record of what was moved a 3 AM while you are counting sheep. PCFU MOV7 -fTIC -lC:\LOGS\BADTIC.LOG -p Move 7 TIC's and the files attached to them in the HOLD_DIR directory to the TOSS_DIR and log the files moved to a pretty little message in PTIC.MSG, and log the unmatched TIC's to a file called BADTIC.LOG in the C:\LOGS directory. 4.10 -l switch Syntax: -lPATH\FILE The -l (L) switch stands for LOG and is used in a case where you would need to override the LOG_DIR= path and default PCFU.LOG filename that is defined in the PCFU.CFG or the file pointed to by the -c switch. Example: PCFU DUP -lC:\SATELITE\LOGS\OTHER.LOG Notes: If using the -l (L) switch a PATH and FILE MUST be defined and is checked for validity, if the program can not find the log file defined, information is is dumped to PCFU.LOG. 4.11 -m switch Syntax: -mPATH\FILE The -m switch stands for MOV and is used in a case where you would need to override the LOG_DIR= path and default PMOV.LOG filename that is defined in the PCFU.CFG or the file pointed to by the -c switch. Example: PCFU MOV -mC:\SATELITE\LOGS\OTHERMOV.LOG Notes: If using the -m switch a PATH and FILE MUST be defined and is checked for validity, if the program can not find the log file defined, information is is dumped to PMOV.LOG. Page 22 4.12 -p switch Syntax: -p The -p (post) switch is used for in conjunction with the -fTIC switch, It notifies PCFU to create a PTIC.MSG file file in the index directory of the files that were proscessed by the PCFU MOVx -fTIC function. Note: This file is overwriten each time the function is called. 4.13 -k switch Syntax: -k The -k (Keep) switch is used for testing or when you would like to run PCFU to see that it will do what you want it to do without doing any of the deleting of files,indexes,logs or any other thing that it normally wipes out on it's marry way through your directories when it runs. Basiclly it should be used for debuging you config files and command line options as you are setting up PCFU and for nothing else. 4.14 -r switch Syntax: -r The -k (Reprocess) switch is used for force the moving of unknown file back into the SATELITE_DIR when a new UPLD.LST is received. PCFU will look at the new list and transfer all files that match back into the inbound SATELITE_DIR from the UNK_DIR. Note: Please keep in mind that the -o switch will override the SATELITE_DIR so using the -o and -r switch together will move the unknown files to the directory defined by the -o switch. 4.15 -v[w] switch Syntax: -v or -vw The -v (verify) switch will cause config and command line verification on the fly with or without the VERIFY option being set in the PCFU.CFG If there is a configutation error PCFU will abort execution. The -vw (verify with wait) switch verifies and then waits 10 seconds to give you time to read the screen before continuing execution. Page 23 5. Networking and Multitasking Here is where PCFU shines, it was made for it. I run a 8 node system under a Lantastic net, with one node doing double duty as both the satellite downlink and a BBS port from 4PM till midnite. 5.1 Running PCFU in a network I call the PCFU DUPx command from every other node on the BBS each time the node cycles through. (FD/RA does a complete exit and restart each time a user or inbound mail bundle comes in) This keeps my inbound satellite directory clear, and with a little batch file trick.... :CHECKSAT PCFU DUP IF EXIST K:\SATELITE\FIDO\*.* GOTO NOPACK RD K:\SATELITE\FIDO MD K:\SATELITE\FIDO :NOPACK ... I keep the fragmentation on the drive down to a minimum. PCFU was designed to shove files all over my network with the idea in mind that I didn't want to be bothered with anything unless a problem should come up that I had to look into. (SAFE directory message post and auto file request... remember) Although file sharing was not implimented, with a few steps on your part and the help of the PCFU.BSY flag, you should be able to run PCFU on a lan with no possibility of it bumping into itself. 5.2 Running PCFU under Desqview I can only say this about Desqview, I had PCFU running under it using the exact same configuration and I use with Lantastic, gave it a 512K big dos window to run in, and it was fat,dump and happy. You can most likely cut that down to 256k and not have a bit of trouble at all. 5.3 Running PCFU with other multitaskers Hmmmmm.... I don't know, try it you may like it, It's plan vanella makes no funky bios calls, and needs to get at DOS's DIR function. If your multitasker can supply this go for it... :-) 5.4 File sharing IT DON'T DO THAT STUFF. If set up properly keeping an eye on the PCFU.BSY flag it shouldn't need to. I have been running it for 3 months and have never had a file sharing violation. 5.5 Moving vs Copying Files Or should I say Speed vs Flexibility, PCFU has enough smarts to try to MOVE a file first (Speed) and if it falls on its face it will revert to copying file (Flexibility in a lan situation) so you have the best of both worlds. Now it's up to you to get your network engineers so that all the grunt stuff that PCFU has to do, it can do without jumping drives. 6 Epilog 6.1 Credits: It all goes to the guys at Planet Connect Data Services... Without the satellite system what would be the sense of this program. 6.2 Thanks to: Boyd,Joe,Todd,Tim,Dennis,John,Doug,Robert and all the rest of you guys that made suggestions about how to improve PCUTIL. Special thanks to my wife Eileen and son Adam for putting up with me over the last few months. 6.3 Technical notes: PCFU is compiled using pure Quick Basic 4.5, uses no direct disk access, low level dos calls or screen writes. All indexes are in plain ascii format for easy editing. Page 24 6.4 Technical support John Morano The Genesis Project BBS 501-267-9600 1:391/1180 @ FidoNet john.morano@f1180.n391.z1.fidonet.org 6.5 Suggesting option for future versions Pleeeeeeez.................. :-)