synchro.net

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

/ synchro.net / synchro.net.tar / synchro.net / modem.madness / SMMNETML / FIDOHELP.ZIP / FIDOHELP.DOC next >

Wrap

Text File | 1992-06-18 | 32.2 KB | 799 lines

Installing FIDO-Net on your PCBoard By Tom Carroll June 18th, 1992 Why am I doing this? I began searching for a suitable information packet that would assist me in the installation of FIDO on my PCBoard system. I never found one. What did I do? I decided to drudge my way through the 148 page FrontDoor manual and see if I could install this monster on my own. Well, I did it with the help of some great friends. This document is being released because of all the troubles I had getting my system to run somewhat smoothly. I had a lot of unanswered questions, and I still do, but the majority of them have been answered by other Sysops. The files and programs I recommend in here are only my recommendations and not being advertised as superior or otherwise. I recommend these because this is what I'm using, all the required programs are FREE to non-commercial BBS'es except for FIDOPCB, and PKX35A35 these two are shareware. Here is a step by step guide for you to follow: 1. The first thing you will need to do, is set aside about a weeks worth of time, because this is no small task to set up, but then again, maybe with this it will be. <grin> I read all my documentation for about two weeks before I decided to jump into this and I feel I still wasn't well prepared. Do you remember your first door that you installed? I do, and I would say this was 1000 times harder, and I lost a lot of hair over this. But now that it's up and running, I feel great! 2. Download some files or get these from some local boards. (I will make sure all these files are available on SALTAIR when I upload this help file) REQUIRED FILES FD202.ARJ ----- FrontDoor v2.02 (Front end mailer) BNU170.ARJ ---- BNU v1.7 (Fossil driver) FP12S.ZIP ----- FIDOPCB v1.2 (Mail tosser/scanner) NODELIST.XXX -- A Node list (current preferably) XLAX_253.ZIP -- XLAXDIFF v2.53 (Used to apply nodediffs) PKX35A35.EXE -- PKXARC PKARC v3.5 (Used to uncompress ARC'ed mail) TTP100B.ZIP --- Tic-2-PCB v1.0ß (Used to import new files from the SDN) POLICY4.ZIP --- FIDO policy document for all FIDO sysops. Recommended files: PKZ110.EXE ---- PKZIP & PKUNZIP v1.10 ARJ230.EXE ---- ARJ v2.30 PK361.EXE ----- PKPAK & PKUNPAK v3.61 LHA213.EXE ---- LHA v2.133. Now create some directories to hold your Frontend mailer and associated files. I set my system up like this: C:\───┐ ┌─────────┐ ┌───────┐ ├─┤ PCB\ ├──────────────────────────┤ FD\ │ │ └─────────┘ └───┬───┘ │ ┌──────────┴──────────┐ │ │ All your Frontdoor │ │ │ files go into this │ │ ┌─────────┐ │ directory. I would │ ├─┤FD_NODE\ ├────┐ │ place this dir. in │ │ └─────────┘ │ │ your path. │ │ ┌──────────┴──────────┐ │ │ │ │ This is the dir. I │ │ You will also keep │ │ │ keep my NODELIST in │ │ your RUN.BAT file │ │ │ which you may put │ │ in this directory. │ │ │ as a sub-dir. of FD │ │ │ │ └─────────────────────┘ └─────────────────────┘ │ ┌─────────┐ ├─┤FD_MAIL\ ├────┐ NOTE: I placed all these │ └─────────┘ │ directories off of the ROOT │ ┌──────────┴──────────┐ because I was running with │ │ This is where my │ a partitioned disk and my C: │ │ incoming net-mail │ drive was too small to allow │ │ waits to be read. │ all the mail bundles and node │ └─────────────────────┘ files, so I placed them on │ ┌─────────┐ my D: drive. If you have ├─┤FD_FILES\├────┐ a single partition drive I │ └─────────┘ │ recommend making all these │ ┌──────────┴──────────┐ directories sub-directories │ │ All incoming files │ of your C:\PCB\FD directory. │ │ and mail bundles │ │ │ are stored in this │ │ │ directory. │ │ └─────────────────────┘ │ ┌─────────┐ ├─┤FD_PACKE\├────┐ │ └─────────┘ │ │ ┌──────────┴──────────┐ │ │ Location of all out │ │ │ -bound mail packets │ │ └─────────────────────┘ │ ┌─────────┐ └─┤ F_ECHO\ ├────┐ └─────────┘ │ ┌──────────┴──────────┐ │ This is where all │ │ my FIDO conference │ │ message bases are. │ └─────────────────────┘4. Next, unarj the FD202 file into your C:\PCB\FD directory. You will have quite a few files in this directory. One thing that I recommend is printing of the manual, there's a lot of helpful information that you'll need, but some that you won't. It's 148 pages long, plus whatever the updates are. This manual is not written by people that know how to explain things very easily. There's a lot of technical jargon that I considered needless for my information at this point. After unarjing the files, run the program called FDSETUP.EXE. Go through your menus and put in your info. Before you're issued a node number, you'll need to enter a fake address until you receive a number from your NET COORDINATOR (NC). He will issue a node number and then you will be added to the nodelist on the following Saturday. For now enter 1:1/1 if you're in North America. Be sure to enter the following error levels to your modem configuration screen: 1200 - 100 2400 - 100 9600 - 100 I wouldn't worry too much about the events scheduler right now. Lets just get you up and running so it'll answer the phone and let your callers on the BBS. 5. After setting up your config in FDSETUP, you will need to unarchive your nodelist and XLAX_253 into your FD_NODE directory. Once you have done that, you'll need to edit your FDNODE.CTL file, which is also located in the FD_NODE directory, to account for all of the local exchanges, in-state long distant numbers and so on. Here is an example of my FDNODE.CTL file: PHONE 1:347/9 375-0507 <<< Number to my hub. This number was wrong in my DIAL <<<<<<<<<<--- last nodelist. 1-509-222 222 | 1-509-372 372 | 1-509-373 373 -------<<< This begins my dial translation table which 1-509-375 375 tells Frontdoor's Node compiler to strip all 1-509-376 376 the 1-509-XXX from the numbers that match XXX. 1-509-377 377 1-509-545 545 The node compiler will look for each occurrence 1-509-546 546 of 1-509-XXX and replace it with XXX. All of 1-509-547 547 these number are considered a local call from 1-509-582 582 my dialing prefix. 1-509-586 586 1-509-588 588 1-509-627 627 1-509-735 735 You will also need to change any numbers that 1-509-736 736 are located in your area code, but are not a 1-509-783 783 local call from your prefix. I have this set 1-509-943 943 as my last line in the dial translation. 1-509-946 946 1-509-967 967 1-509 1 <<<<<<<<---------<<< Then after it's done with all the local numbers, END it removes the -509 from the rest of them. 6. Now change back to the C:\PCB\FD directory and type FDNC. This should compile your nodelist. After this is done, you only need to do one more thing before you're able to run the mailer. (The hard part is over, I THINK!)7. Unarj the BNU170 file into your UTILS directory. The only file I kept was the BNU.COM file. If you want the BNU.SYS file, then delete the BNU.COM file. I run the .COM file, so I can unload it when I chain to my BBS. I've heard of people having problems with a Fossil driver, and others say they don't effect anything. It's your call. If you use the .COM file, just type BNU /Pa /Lb:ccccc,8n1 /F /Pa = Number of ports active /Lb = Comm port number (L0=COM1, L1=COM2 etc.) ccccc = Comm port baud rate (i.e. 38400) 8n1 = Data bits-Parity-Stop bits /F = Fast ANSI screen writes My AUTOEXEC.BAT entry looks like this: BNU /P1 /L1:38400,8n1 /F 8. Guess what? You're now ready to fire off the FrontDoor mailer. Path to your C:\PCB\FD directory and type FD <enter>. You should see the mailer come up and try to initialize the modem. If it's successful, it'll say "Waiting for call or event" If it doesn't, then something must be wrong in you modem config. By now, you should've gotten your NC's FIDO address. If not, call a local FIDO BBS and ask that Sysop what the NC's address is. 9. Press ALT-E and enter the NC's address, then press enter. Next enter a subject, such as NEW NODE and press enter. Now enter your information, most NC's like the following info: Request to have a node number assigned to my system: BBS NAME BBS SOFTWARE BBS NUMBER BBS FLAGS (get them from the FD Manual) FRONT END MAILER SOFTWARE SYSOP NAME PASSWORD (for AreaFix and Raid) HOME PHONE TYPE OF COMPUTER COMPRESSION METHOD (ZIP, LZH, ARJ, ARC, PAK) Now press CTRL-Z to save the message. Once you're finished in the editor, press ALT-Q to return to the mailer. Your mail should go out to him within 5 minutes. 10. If you want to run events on your system, which almost every Sysop does, you'll need to forget about PCBoard's internal event system. FrontDoor has a very extensive events manager. You can have as many events a day that you wish. I didn't like this at first because it was separate from PCBoard, but now I don't see how I was doing everything in one event. You will have one event as a minimum. The Zone Mail Hour (ZMH), which is at 0800 Greenwich mean time (GMT) for Zone 1 (North America). You can then schedule other events to do you BBS maintenance, or you can just set everything up to run consecutively. This is a very powerful tool.11. Now that your mailer is up and running, you need to know how to get your callers to your BBS from the "Press Escape twice to enter PCBoard" prompt when the mailer answers the phone. There are four batch files I use, plus several environment variables. I will start with the RUN.BAT file. @ECHO OFF BNU /C REM --------- DELETE THE BBS CHAIN FILE --------- IF EXIST C:\PCB\FD\DOBBS.BAT DEL C:\PCB\FD\DOBBS.BAT IF %LASTON%==LOCAL GOTO SWAPFILE <<< I use this to control the local mode GOTO CONTINUE in my BOARD.BAT file which ensures :SWAPFILE that any callers don't get messed up CD \PCB from when I use the BBS in local mode. COPY BOARDC.BAT BOARD.BAT /V SET LASTON=CALLER I do this so I can use my doors in :CONTINUE local mode without causing conflicts CD \PCB\FD with my mailer. FD REM --------- CHECK ERROR LEVELS RETURNED BY MAILER --------- IF ERRORLEVEL 125 GOTO LOCAL <<<< These error levels are setup in the IF ERRORLEVEL 100 GOTO BOARD FDSETUP program. Use the Modem error IF ERRORLEVEL 10 GOTO QUIT levels menu to setup your connection IF ERRORLEVEL 8 GOTO ERROR speeds, and what error levels FD will IF ERRORLEVEL 7 GOTO ERROR exit with when it receives a human IF ERRORLEVEL 6 GOTO ERROR caller. IF ERRORLEVEL 5 GOTO ERROR IF ERRORLEVEL 4 GOTO ERROR This will also test for exit errors by IF ERRORLEVEL 3 GOTO ERROR FD and echo them to the screen. IF ERRORLEVEL 2 GOTO ERROR IF ERRORLEVEL 1 GOTO ERROR REM --------- SEND CALLER TO THE BBS --------- :BOARD BNU /Q /M- <<<<<<<<<<< - I disable my fossil driver SET LASTON=CALLER <<<< - SET the LASTON environment variable DOBBS <<<<<<<<<<<<<<<< - Call the batch file FD creates which calls EXEBBS REM --------- LOG ON TO THE BBS IN LOCAL MODE --------- :LOCAL BNU /Q /M- <<<<<<<<<<< - I disable my fossil driver SET LASTON=LOCAL <<<< - SET the LASTON environment variable CD \PCB COPY BOARDL.BAT BOARD.BAT /V << - COPY my local board.bat file BOARD <<<<<<<<<<<<<<<<<<<<<<<<< - CALL my BOARD.BAT REM --------- PROCESS FRONT DOOR ERROR --------- :ERROR CLS IF ERRORLEVEL==8 ECHO ERROR: FRONT DOOR ALREADY LOADED! USE EXIT TO RETURN IF ERRORLEVEL==7 ECHO ERROR: FOSSIL DRIVER NOT LOADED OR DETECTED! IF ERRORLEVEL==6 ECHO ERROR: INCORRECT FOSSIL VERSION FOR FRONT DOOR! IF ERRORLEVEL==5 ECHO ERROR: CANNOT INITIALIZE THE MODEM! IF ERRORLEVEL==3 ECHO ERROR: LESS THAN 32KB OF DISK SPACE AVAILABLE! IF ERRORLEVEL==2 ECHO ERROR: EXTERNAL ERROR - MISSING PATH, FILES, ETC. IF ERRORLEVEL==1 ECHO ERROR: INTERNAL ERROR BNU /C <<<<<< - This recaptures int 14 so you don't get any fossil errors GOTO DONE REM --------- EXIT FRONT DOOR NORMALLY --------- :QUIT ECHO Normal Exit! :DONE BNU /Q /M- <<<<<<<<<<< - I disable my fossil driver Whew! That's a bare bones batch file for the mailer. This should at least get you from the mailer halfway to your BBS. The next file is called EXEBBS.BAT which looks like this: @ECHO OFF SET CONTYPE= I set my 9600 to 5 which is interpreted IF "%1"=="9600" SET SPED=5 by PCBoard as connect speed of 38400. IF "%1"=="2400" SET SPED=3 The reason I do that is because I have IF "%1"=="1200" SET SPED=2 a USR/HST which if I connect at 9600, it IF "%4"=="/REL" SET CONTYPE=/ERR must be another HST, which can connect IF "%4"=="/ARQ" SET CONTYPE=/ERR at 38400. Any other calls will be either BOARD %1 %2 %3 2400 or 1200. I don't allow 300 callers. Your EXEBBS.BAT file is called by a batch file that you must tell FrontDoor to create when it exits after a modem connect. This file is called DOBBS.BAT and it will contain the connect speed (passed as %1), the comm port (as %2), minutes until the next event (as %3), and the connection type (as %4). i.e. EXEBBS 9600 2 159 /ARQ Notice that I pass %2 to my BOARD.BAT file. This is only used as a filler, and is not needed by the batch file. Now for the final batch file. Your BOARD.BAT. @ECHO OFF C: CD \PCB SET PCB=/BYTECRED:1.5 /CONNECT:%1 /MAIN /NOPROMOTE /SWAP /UPCRED:1 IF EXIST REMOTE.BAT RENAME REMOTE.BAT REMOTE.SYS IF EXIST EVENT.BAT RENAME EVENT.BAT EVENT.SYS IF EXIST DOOR.BAT DEL DOOR.BAT IF EXIST ENDPCB DEL ENDPCB PCB145 /C:%SPED% %CONTYPE% /EVENT:%3 IF EXIST REMOTE.BAT REMOTE IF EXIST DOOR.BAT DOOR IF EXIST EVENT.BAT EVENT IF EXIST ENDPCB GOTO END BOARD :END RUN NOTE: I have my C:\PCB directory in my path Your callers should now be able to connect to your BBS now. 12. Be sure to go into PCBSetup and select OPTIONS #1. For the Drop to DOS entry, be sure to enter "Y" in this field. No exit and save the file. 13. This has pretty much gotten the FrontDoor mailer up and working. I'm sure you're probably getting tired, but if you're like me, you just want to keep going. Now we need to get you setup with a mail tosser scanner. But before we do this, we need to determine how and what messages we will be getting from the NC. The reason for the password that you sent for areafix, and raid, is because you can automatically pickup and drop conferences, and file distribution networks. All you need to do is get the USEFIX.ZIP file that I uploaded to SALTAIR. It will explain how to use the AreaFix features on the NC's server. Once you have your message areas picked out, and you know the EXACT conference names, you can then setup your echo conferences, and your FIDOPCB to import/export your FIDO messages. 14. You will first need to setup your echo areas in PCBoard, just like any other network, or local conferences. If you've never setup an echo conference, be sure to set the echo flags to yes. As an example, I set all my conference names with a network identifier, such as F_PCBNet for the FIDO conference PCBNet. I also set my message base names to the same names as the conference or as close as possible. Such as MSGS: C:\F_ECHO\PCBNet, which makes for much easier backups when you just want to do a backup of the entire FIDO message base. Some like this, some don't, it's up to you. 15. Now, you should have time to go grab a beer, or pop, whatever you fancy, because you're going to have to print (yes PRINT) the FIDOPCB manual. The FIDOPCB.CFG file is pretty strait forward until you get down to the bottom area where you set up your conference areas. I have included my config file for your convenience to assist you in completing this last step. INTERFACE frontdoor NET_TOSS pcboard NETWORK off NO_BELL off IGNORE_ECHO on MAX_MSGS 9999 DUPE_CHECK 200 MAIL c:\fd_mail PACKET c:\fd_packe FILE c:\fd_files BAD c:\fd_bad WORK c:\fd_work LOST_MAIL c:\f_echo NET_MAIL c:\f_echo PCBOARD c:\pcb FRONTDOOR c:\pcb\fd ZIP UNZIP ARC UNARC ARJ UNARJ LZH UNLZH ORIGIN 1:347/10 DOMAIN fidonet.org SYSOP Tom Carroll TAG The Data Shop, Kennewick WA (509)582-9493 (HST) AREA 1 Apple C:\F_ECHO DUPE AREA_MSGS Apple AREA 2 Pascal C:\F_ECHO DUPE AREA_MSGS Pascal AREA 3 Trek C:\F_ECHO DUPE AREA_MSGS Trek AREA 4 Windows.Prog C:\F_ECHO DUPE AREA_MSGS Win-Pgm AREA 5 Humor C:\F_ECHO DUPE AREA_MSGS Humor AREA 6 Quik_Bas C:\F_ECHO DUPE AREA_MSGS QuickBas AREA 7 Ham_Tech C:\F_ECHO DUPE AREA_MSGS Ham_Tech AREA 8 Windows C:\F_ECHO DUPE AREA_MSGS Windows AREA 9 CNW_Net C:\F_ECHO DUPE AREA_MSGS CNW_Net AREA 10 For-Sale C:\F_ECHO DUPE AREA_MSGS ForSale AREA 11 TC_Net C:\F_ECHO DUPE AREA_MSGS TC_Net AREA 12 ASP C:\F_ECHO DUPE AREA_MSGS ASP AREA 13 Military_People C:\F_ECHO DUPE AREA_MSGS Military AREA 14 PCBNet C:\F_ECHO DUPE AREA_MSGS PCBNet AREA 15 Teen C:\F_ECHO DUPE AREA_MSGS Teen AREA 16 OS2 C:\F_ECHO DUPE AREA_MSGS OS2 NODE 1:347/9 1-10,12-16 SYSOP Vic Parrish COMPRESS ARC FLOW_TYPE NORMAL NODE 1:347/6 11 SYSOP Rodney Barnes COMPRESS ARJ FLOW_TYPE NORMAL Once you have your config file completed, and a packet in your files directory, FIDOPCB will import that packet into your PCBoard message bases. One problem that I ran into, was that I didn't do a pack on the message bases after creating them. You MUST do this so FIDOPCB will see both the XXXXX and XXXXX.NDX message files. Also, as the FIDOPCB docs state, you must create two other echo areas, one is called MATRIX (message base name. I Called that conference F_NetMail) and LOST (which no one but myself has access to). These files must exist also (in the FIDOPCB directory), or FIDOPCB will not work. I believe the docs say that these are included in the archive, but they are NOT! You must create them by entering in their names (WHICH MUST BE MATRIX & LOST, i.e. Messages: C:\PCB\FP\MATRIX) and then exit from the PCBSetup and run PCBPack to create the files and indexes. 16. The last order of business is to explain the .TIC files you will receive. These files are received whenever you get a file from the FIDO file distribution network. (i.e. FIDONEWS, NODELIST, NODEDIFF etc.) This .TIC file will contain the AREA name the file is from, who originated it, what the file name is, a description (1 line right now) and a CRC-32 of the file. When I started using FIDO, there really wasn't a simple means of importing these files to your upload directory for new files. So, I developed Tic-2-PCB which will move these files to your upload directory when they are received. 17. Well, that pretty much wraps it up for a bare bones, basic installation. I have included my batch files at the end of this document for you to use, or review to get your own ideas. If you have any problems, once you get your mailer up and running, you can net-mail me at 1:347/10. I will do whatever I can to help you along. Please remember that I have a different system than you do, so some of this may not work for you. Good luck!DEFINITIONS: (file sizes are for uncompressed files) NODELIST - This is a list of all FIDO mail systems for the world. This list has phone numbers, system names, sysop names, and system FLAGS for all nodes listed. This file is very large. Mine is over 1.5 megs in size. NODEDIFF - This is a file that is distributed every week (I get mine Saturday) and it is used with the XLAXDIFF program to update your NODELIST file to either add, remove, or make some other changes for any system. This ensures you have current info on any system that you may want to call. This file is usually under 100k. FNEWSnnn - FIDONEWS is distributed every week in compressed format. You can place it in a directory for your callers to download, or you my place it in an on-line bulletin for reading. Normally around 20k xxxxxx.TIC - These are file area descriptions that are distributed with any files you receive over the file distribution networks. xxxxxx.MO0 - These files will be named using a checksum of your address and your NC's address. The suffix will be the fist 2 letters of the day and the Nth number of the mail bundle. xxxxxx.PKT - These are conference packets that are either being sent, or received. nnnnnn.MSG - Individual messages created within each packet. ROUTE.FD - This file determines how all mail from your system is routed. NAMES.FD - This is another config file for FD. It acts as a name directory for any systems that you call frequently. You can enter the Name and Node number of a system, and then have a single letter or key sequence to call it up like a macro within the FrontDoor Message editor. FDNODE.CTL - This is the control file that tells the FrontDoor Node Compiler how to compile the node list. There are a number of different items that you can place in this file.RUN.BAT @ECHO OFF REM --------- RETURNED TO HERE AFTER EACH EXIT --------- :START BNU /C :RESUME REM --------- DELETE THE BBS CHAIN FILE --------- IF EXIST C:\PCB\FD\DOBBS.BAT DEL C:\PCB\FD\DOBBS.BAT IF %LASTON%==LOCAL GOTO SWAPFILE GOTO CONTINUE :SWAPFILE CD \PCB COPY BOARDC.BAT BOARD.BAT /V SET LASTON=CALLER :CONTINUE CD \PCB\FD REM --------- CHECK FOR NEW NODE & FIDO NEWS FILES --------- IF EXIST C:\FD_FILES\NODEDIFF.* GOTO NODEDIFF IF EXIST C:\FD_FILES\NODELIST.* GOTO NODELIST IF EXIST C:\FD_FILES\FNEWS*.* GOTO FIDONEWS IF EXIST C:\FD_FILES\*.TIC GOTO TICK FD REM --------- CHECK ERROR LEVELS RETURNED BY MAILER --------- IF ERRORLEVEL 240 GOTO BOARD IF ERRORLEVEL 125 GOTO LOCAL IF ERRORLEVEL 120 GOTO BOARD IF ERRORLEVEL 96 GOTO BOARD IF ERRORLEVEL 76 GOTO EVENT2 IF ERRORLEVEL 75 GOTO EVENT1 IF ERRORLEVEL 65 GOTO EXPORT IF ERRORLEVEL 55 GOTO GETMAIL IF ERRORLEVEL 45 GOTO NETMAIL IF ERRORLEVEL 35 GOTO HOME IF ERRORLEVEL 31 GOTO IMPORT IF ERRORLEVEL 10 GOTO QUIT IF ERRORLEVEL 8 GOTO ERROR IF ERRORLEVEL 7 GOTO ERROR IF ERRORLEVEL 6 GOTO ERROR IF ERRORLEVEL 5 GOTO ERROR IF ERRORLEVEL 3 GOTO ERROR IF ERRORLEVEL 2 GOTO ERROR IF ERRORLEVEL 1 GOTO ERROR REM --------- CALL THE HOME NUMBER AND WAKE ME UP --------- :HOME BNU /Q /M CD \PCB\ROBO ROBOCOMM /AHOME /R GOTO START REM --------- IMPORT ANY NEW FIDO MAIL FOR READING --------- :IMPORT CD \PCB\FP FIDOPCB IMPORT FIDOPCB Stat > ..\GEN\BLT16 GOTO RESUME REM --------- EXPORT ANY NEW FIDO MAIL FOR DELIVERY --------- :EXPORT CD \PCB\FP FIDOPCB EXPORT /Strip FIDOPCB Stat > ..\GEN\BLT16 GOTO RESUME REM --------- SEND CALLER TO THE BBS --------- :BOARD BNU /Q /M SET LASTON=CALLER DOBBS REM --------- LOG ON TO THE BBS IN LOCAL MODE --------- :LOCAL BNU /Q /M SET LASTON=LOCAL CD \PCB COPY BOARDL.BAT BOARD.BAT /V BOARD REM --------- BEGIN THE FIRST NIGHTLY EVENT --------- :EVENT1 BNU /Q /M CD \PCB\FP REM --------- EXPORT ANY NEW FIDO MAIL FOR DELIVERY --------- FIDOPCB Export /Strip FIDOPCB Stat > ..\GEN\BLT16 CD \PCB REM --------- RUN PCBOARDS EVENT --------- REN EVENT.SYS EVENT.BAT EVENT REM --------- BEGIN THE SECOND NIGHTLY EVENT --------- :EVENT2 BNU /Q /M CD\PCB\ROBO REM --------- CALL LOCAL BBS AND TRADE FILES/MAIL --------- ROBOCOMM /ASECOND /R CD \PCB\FP REM --------- IMPORT ANY FIDO MAIL NOT IMPORTED --------- FIDOPCB IMPORT FIDOPCB Stat > ..\GEN\BLT16 CD \PCB REM --------- PACK THE FIDO MAIL MESSAGE BASES --------- PCBPACK /Area:16-40 /Fast /KillBak /KillDups /MaxMsgs:500 /NoCaller /UpCase REM --------- CREATE THE BBS CATALOG OF FILES --------- PCBFILER /SORT PCBLOF 0 15 REN PCBLOF.LST DATASHOP.CAT ARJ A -m1 !CATALOG DATASHOP.CAT COPY !CATALOG.ARJ \FREE /V DEL !CATALOG.ARJ DEL DATASHOP.CAT GOTO START REM --------- APPLY THE NEW NODEDIFF TO THE NODELIST --------- :NODEDIFF CLS ECHO ********* PROCESSING NODELIST FILE ********* CD \FD_NODE PKUNPAK -E \FD_FILES\NODEDIFF.* DEL \FD_FILES\NODEDIFF.* XLAXDIFF /C CD \PCB\FD FDNC /F GOTO RESUME REM --------- COMPILE THE NEW NODELIST --------- :NODELIST CLS ECHO ********* PROCESSING NODELIST FILE ********* CD \FD_NODE PKUNZIP -E \FD_FILES\NODELIST.* DEL \FD_FILES\NODELIST.* CD \PCB\FD FDNC /F GOTO RESUME :FIDONEWS REM --------- PROCESS THE LATEST FIDO NEWS INTO BLT --------- CLS ECHO ********* PROCESSING FIDO NEWS FILE ********* CD \PCB\GEN LHA E \FD_FILES\FNEWS* DEL \FD_FILES\FNEWS*.* COPY *.NWS BLT15 CD \PCB\FD GOTO RESUME :TICK REM --------- APPLY THE LATEST TIC FILE AND FILES --------- CLS ECHO ********* PROCESSING .TIC FILE ********* CD \FD_FILES TIC2PCB GOTO RESUME :GETMAIL REM --------- GET LOCAL BBS MAIL & DL'ED MAIL PKTS --------- CD \CAM-MAIL IF EXIST A:\DATASHOP.REP GOTO REP LOCALCAM PCB:C:\PCB FName:Tom LName:Carroll Pwrd:XXXXXXX QWK GOTO END :REP COPY A:\DATASHOP.REP NETS /V DEL A:\DATASHOP.REP LOCALCAM PCB:C:\PCB FName:Tom LName:Carroll Pwrd:XXXXXXX REP :END IF EXIST NETS\DATASHOP.QWK COPY NETS\DATASHOP.QWK A: /V IF EXIST NETS\DATASHOP.QWK DEL NETS\DATASHOP.QWK CD\PCB\MAIL1 IF EXIST *.QW? COPY *.QW? A: /V IF EXIST *.QW? DEL *.QW? GOTO RESUME :NETMAIL REM --------- GET NETMAIL FROM HOST BBS --------- BNU /Q /M CD \CAM-MAIL\NETS IF EXIST ONESTOP.QW1 DEL ONESTOP.QW1 IF EXIST ONESTOP.QWK REN ONESTOP.QWK ONESTOP.QW1 CD \CAM-MAIL EXPORT ONESTOP CD \PCB\ROBO ROBOCOMM /ANETMAIL /R CD \CAM-MAIL\NETS IF EXIST ONESTOP.QWK GOTO NUKEIN GOTO NONUKE :NUKEIN CD \CAM-MAIL IMPORT ONESTOP /DUPS /MAILFLAGS :NONUKE CD \PCB\FD GOTO START REM --------- PROCESS FRONT DOOR ERROR --------- :ERROR CLS IF ERRORLEVEL== 8 ECHO ERROR: FRONT DOOR ALREADY LOADED! USE EXIT TO RETURN IF ERRORLEVEL== 7 ECHO ERROR: FOSSIL DRIVER NOT LOADED OR DETECTED! IF ERRORLEVEL== 6 ECHO ERROR: INCORRECT FOSSIL VERSION FOR FRONT DOOR! IF ERRORLEVEL== 5 ECHO ERROR: CANNOT INITIALIZE THE MODEM! IF ERRORLEVEL== 3 ECHO ERROR: LESS THAN 32KB OF DISK SPACE AVAILABLE! IF ERRORLEVEL== 2 ECHO ERROR: EXTERNAL ERROR - MISSING PATH, FILES, ETC. IF ERRORLEVEL== 1 ECHO ERROR: INTERNAL ERROR BNU /C GOTO DONE REM --------- EXIT FRONT DOOR NORMALLY --------- :QUIT ECHO Normal Exit! :DONE BNU /Q /MEXEBBS.BAT @ECHO OFF SET CONTYPE= IF "%1"=="9600" SET SPED=5 IF "%1"=="2400" SET SPED=3 IF "%1"=="1200" SET SPED=2 IF "%4"=="/REL" SET CONTYPE=/ERR IF "%4"=="/ARQ" SET CONTYPE=/ERR BOARD %1 %2 %3BOARDC.BAT @ECHO OFF C: CD \PCB SET PCB=/BYTECRED:1.5 /CONNECT:%1 /MAIN /NOPROMOTE /SWAP /UPCRED:1 IF EXIST REMOTE.BAT RENAME REMOTE.BAT REMOTE.SYS IF EXIST EVENT.BAT RENAME EVENT.BAT EVENT.SYS IF EXIST DOOR.BAT DEL DOOR.BAT IF EXIST ENDPCB DEL ENDPCB PCB145 /C:%SPED% %CONTYPE% /EVENT:%3 IF EXIST REMOTE.BAT REMOTE IF EXIST DOOR.BAT DOOR IF EXIST EVENT.BAT EVENT IF EXIST ENDPCB GOTO END BOARD :END RUNBOARDL.BAT @ECHO OFF C: CD \PCB SET PCB=/MAIN /SWAP SET LASTON=LOCAL IF EXIST REMOTE.BAT REN REMOTE.BAT REMOTE.SYS IF EXIST EVENT.BAT REN EVENT.BAT EVENT.SYS IF EXIST DOOR.BAT DEL DOOR.BAT IF EXIST ENDPCB DEL ENDPCB PCB145 /LOCALON IF EXIST REMOTE.BAT REMOTE IF EXIST DOOR.BAT DOOR IF EXIST EVENT.BAT EVENT IF EXIST ENDPCB GOTO END BOARD :END RUNEVENT.SYS @ECHO OFF C: CD\PCB DEL EVENT.LOG CLS ECHO Conducting Tradewars Maintenance... C: CD\DOORS\TWARS EXTERN -DOOR CLS ECHO Tradewars Maintenance Finished >> C:\pcb\event.log ECHO Extracting Echo Mail... C: CD\CAM-MAIL\NETS IF EXIST DATASHOP.RE1 DEL DATASHOP.RE1 IF EXIST DATASHOP.REP REN DATASHOP.REP DATASHOP.RE1 IF EXIST ONESTOP.QW1 DEL ONESTOP.QW1 IF EXIST ONESTOP.QWK REN ONESTOP.QWK ONESTOP.QW1 IF EXIST ONESTOP.RE1 DEL ONESTOP.RE1 IF EXIST ONESTOP.REP REN ONESTOP.REP ONESTOP.RE1 CD\CAM-MAIL EXPORT ONESTOP CD\PCB CLS ECHO Net-Mail Extracted >> C:\pcb\event.log ECHO Packing Message Bases... PCBPACK /area:0-15 /fast /killbak /killdups /purge /upcase PCBPACK /area:16-39 /fast /killbak /killdups /maxmsgs:1500 /purge /upcase CLS ECHO Message Bases Packed >> C:\pcb\event.log ECHO Packing Users File... PCBSM /pack;remove;days:60;keep:70 CLS ECHO Users File Packed >> C:\pcb\event.log ECHO Sorting Users File... PCBSM /sort;security;prireverse CLS ECHO Users File Sorted >> C:\pcb\event.log ECHO Loading Robocomm (First Agenda)... C: CD\PCB\ROBO DEL ROBOCOMM.LOG Robocomm /AFIRST /R /P CLS ECHO Robocomm (First Agenda) completed >> C:\pcb\event.log ECHO Importing Echo Mail... CD\CAM-MAIL IF EXIST NETS\ONESTOP.QWK GOTO IMPORT GOTO SORT :IMPORT IMPORT ONESTOP /DUPS /MAILFLAGS rem CRCSM CLS ECHO Net-Mail Imported >> C:\pcb\event.log CD\PCB PCBPACK /area:40-81 /fast /killbak /killdups /maxmsgs:500 /purge /upcase :SORT PCBFILER /SORT ECHO Directory sort completed >> C:\pcb\event.log CLS ECHO Creating BBS catalog of files... PCBLOF 0 15 REN PCBLOF.LST DATASHOP.CAT ARJ A -m1 !CATALOG DATASHOP.CAT COPY !CATALOG.ARJ C:\FREE /V DEL DATASHOP.CAT DEL !CATALOG.ARJ ECHO BBS catalog of files updated >> C:\PCB\EVENT.LOG ECHO Returning to Front Door C: CD\PCB\FD RUN