Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / UFOBASE7.ZIP / PHASE3.ZIP / PHASE3.DOC next >

Wrap

Text File | 1995-05-09 | 16.3 KB | 373 lines

WoodyWare's InterBBS ▄▄▄▄▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄ ▄▄▄▄▄ ▄▄▄▄▄ ▄▄▄▄▄ █ ▄▄▄ █ █ █▄█ █ █ ▄▄▄ █ █ ▄▄▄▄█ █ ▄▄▄▄█ █▄ ▄█ █▄ ▄█ █▄ ▄█ █ ▄▄▄▄█ █ ▄▄▄ █ █ ▄▄▄ █ █▄▄▄▄ █ █ ▄▄▄█▄ ▄█ █▄ ▄█ █▄ ▄█ █▄ █▄█ █▄█ █▄█ █▄█ █▄█ █▄▄▄▄▄█ █▄▄▄▄▄█ █▄▄▄█ █▄▄▄█ █▄▄▄█ Thank you for trying WoodyWare's Phase 3 InterBBS Interaction Module. In this archive, PHASE3.ZIP, you will find the following files. UECHOIN.EXE - EchoMail to Database Exec UECHOOUT.EXE - Database to EchoMail Exec SAMPLE.CFG - A sample Config file for Uechoin and Uechoout SECHO.BAT - Batch for calling up Echomail Processor of your choice. PHASE3.DOC - This Documentation PHASE3.ORD - Order Form for Phase3 Before going into detail on how to run these programs, lets discuss the concept of PHASE3 and what it can & cannot do. PHASE3 allows you to receive and send Data over a FidoNet Type echomail message area. By FidoNet type I mean if you send and receive ArcMail (*.MO?, *.TU?, etc.) and *.PKT/*.OUT files. If you're not sure if you do or not you can send me a message or maybe it will be more clear as this document progresses. In a nutshell, this is how PHASE3 works: UECHOIN.EXE will search the incoming arcmail path as defined in the configuration file for incoming arcmail. It will determine the file type compression and unarchive the incoming arcmail. UECHOIN.EXE will then search the .PKT's or .OUT's that have been archived for messages from and addressed to UFOBASE. If a message in a Packet contains a message to/from UFOBASE then it will toss it into the sysop definable freeform database (FUFO.DAT) or the Fixed form database (UFO.DAT). Afterwards the searched .PKT's/.OUT's will be deleted (HOWEVER THE ARCMAIL WILL NOT BE DELETED SO YOU CAN TOSS YOUR MESSAGES INTO YOUR BBS). UECHOOUT.EXE will search your UFOBASE directory looking for *.FRE or *.FIX files. It will put these temporary files into a Hudson Message base. Then, it will shell out to SECHO.BAT to call up an echomail processor (such as gecho.exe, fmail.exe, etc.) to pack up and arcmail the outgoing echomail data. Below is detailed information on both processes and how to make a configuration file, etc. ECHOIN.EXE: ----------- ECHOIN.EXE is the exec that will read incoming arcmail and unarchive it, then search the .PKT's/.OUT's for messages addressed to UFOBASE and add them to the appropriate database. First, let's get your configuration file fixed. Below is a sample configuration file called SAMPLE.CFG Jerry Woody 1 3607 20 c:\sbbs\xtrn 1 Y Y c:\fd\file 00000 The First Line is your First Name (NO BLANK SPACES AFTER FIRST NAME) The Second Line is your Last Name (NO BLANK SPACES AFTER LAST NAME) The Third Line is your ZONE The Fourth Line is your NET The Fifth Line is your NODE the Sixth Line is the Path to your TEMPORARY HUDSON MESSAGE BASE The Seventh Line is the BoardNumber to Post the TEMPORARY DATA in the HMB The Eighth Line is Y/N if you want to delete the TEMPORARY HUDSON MESSAGE BASE The Ninth Line is Y/N if you want to delete the TEMPORARY DATA FILE (*FRE/*FIX) The Tenth Line is the Path for INCOMING ARCMAIL (*.MO?, *.TU?, *.FR?, etc.) The Eleventh Line is your registration number if you have one from WoodyWare LINES 1 - 5 should (Hopefully) be self-explanatory LINE 6 - 9 Will be Discussed in the UECHOOUT.EXE Section LINE 10 - PATH TO INCOMING ARCMAIL This is the path where incoming arcmail from your uplinks come in. They are in the form of *.MO? *.TU? *.WE? *.TH? *.FR? *.SA? *.SU? Uechoin.exe will automatically determine the following types of archive methods: ZIP PAK ARJ LHA SQZ ARC ZOO If you find that you have arcmail in your directory but UECHOIN.EXE didn't unarchive it you can go to the UFOBASE directory and unarchive it manually and write me a note letting me know what compression type is used and I'll look into it :) UECHOIN.EXE will UNARCHIVE the incoming ARCMAIL but will NOT delete the incoming arcmail. The arcmail must still be there for your BBS Echomail tosser to toss mail into your BBS. UECHOIN.EXE takes some time to search each message in a .PKT / .OUT so it will be somewhat slow going depending on what speed machine you have. To avoid delays you may want to copy your arcmail to a special directory, toss the echomail to your BBS, then run UECHOIN.EXE at a time when the BBS is slow, etc. I've only found 1 instance where UECHOIN.EXE will "choke" on a .PKT . This was a .PKT created by AllFix. The packet/message length was over 64000 bytes long and the .PKT Header didn't conform with FTSC-0001 standards. The .PKT currently being processed will be displayed when UECHOIN.EXE is running. If no message is processed in 1-3 minutes then you will need to delete the .PKT/.OUT that is displayed. ! YOU MUST SPECIFY A CONFIGURATION FILE TO USE ON THE DOS COMMAND LINE WITH UECHOIN.EXE. FOR EXAMPLE: UECHOIN SAMPLE.CFG ! YOU MUST RUN UECHOIN.EXE BEFORE CALLING UP YOUR ECHOMAIL TOSSER; OTHERWISE YOUR ECHOMAIL TOSSER WILL DELETE THE ARCMAIL BEFORE UECHOIN.EXE HAS HAD A CHANCE TO SEARCH IT! UECHOOUT.EXE: ------------- ECHOOUT.EXE is the exec that will Take temporary files (*.FRE/*.FIX) that UFOBASE creates when data is entered and toss them into a TEMPORARY HUDSON MESSAGE BASE. Then UECHOOUT.EXE calls up SECHO.BAT to run your Echomail processor, and depending on your configuration file deletes your temporary files and HMB. Now... there are some important logic facts to remember while running UECHOOUT.EXE. The VERY important things to look for will be preceded by a !. Before going through the Configuration file... ! You can use MULTIPLE configuration files for UECHOOUT.EXE. This is in case you want to transmit data on more than one ECHOMAIL area. That is why in the configuration file you have an option to delete the temporary files and/or temporary HMB. Below is a sample configuration file called SAMPLE.CFG: Jerry Woody 1 3607 20 c:\sbbs\xtrn 1 Y Y c:\fd\file 00000 The First Line is your First Name (NO BLANK SPACES AFTER FIRST NAME) The Second Line is your Last Name (NO BLANK SPACES AFTER LAST NAME) The Third Line is your ZONE The Fourth Line is your NET The Fifth Line is your NODE the Sixth Line is the Path to your TEMPORARY HUDSON MESSAGE BASE The Seventh Line is the BoardNumber to Post the TEMPORARY DATA in the HMB The Eighth Line is Y/N if you want to delete the TEMPORARY HUDSON MESSAGE BASE The Ninth Line is Y/N if you want to delete the TEMPORARY DATA FILE (*FRE/*FIX) The Tenth Line is the Path for INCOMING ARCMAIL (*.MO?, *.TU?, *.FR?, etc.) The Eleventh Line is your registration number if you have one from WoodyWare LINES 1 - 5 should (Hopefully) be self-explanatory LINE 6 - Path to your TEMPORARY HUDSON MESSAGE BASE When processing outgoing temporary files, UECHOOUT.EXE creates an old style Hudson message base. We chose this msg base because a majority of inexpensive or freeware echomail programs processes the old style Hudson Message Base, hereafter referred to as HMB. After you run UECHOOUT.EXE there is no reason to keep the temporary HMB, so you can set line 6 to Y ; but you can keep it if you want by setting line 6 to N . ! If you are running BBS software that already uses the old style HMB and choose to use your BBS HMB then be sure to set line 6 to N otherwise you'll delete your message base! ! The path to your HMB should be the same in your HMB echomail processor as it is in the configuration file. LINE 7 - Board Number to Post the TEMPORARY DATA in the HMB This can be a number from 1 - 200. This is used when your HMB echomail processor is packing and arcmailing outgoing messages. ! If you are already using an old style HMB with your BBS software you can pick an open HMB message board number. ! If you are planning to transmit data over multiple echoes, be SURE each configuration file has a different Board Number. For example, lets say you're going to transmit data in the WOODYWARE echo (example Board Number 1) and the XUFO echo (example Board Number 2). Here's the sequence and example for running UECHOOUT.EXE when transmitting over multiple echoes: Your Echo1.cfg would be something like: Jerry Woody 1 3607 20 c:\sbbs\xtrn 1 N N c:\fd\file 00000 Notice that the board number is 1, and the delete Temporary HMB and delete Temporary data files are set to N . Then- UECHOOUT.EXE ECHO1.CFG Immediately following that: Your Echo2.cfg would be something like: Jerry Woody 1 3607 20 c:\sbbs\xtrn 2 Y Y c:\fd\file 00000 Notice that the board number is 2, and the delete Temporary HMB and delete Temporary data files are set to Y . LINE 8 - Do you want to Delete the Temporary HMB Unless you are running an old style HMB with your BBS software set this to Y. The only exception is when posting over multiple echoes, then set it to Y only for the last time you run UECHOOUT.EXE with its configuration file (see example above). LINE 9 - Do you want to Delete the Temporary Data Files Setting this to Y will delete *.FRE and *.FIX in your UFOBASE Directory. ! IT IS VERY IMPORTANT THAT YOU SET THIS LINE TO Y IN THE CONFIGURATION FILE FOR THE LAST TIME UECHOOUT.EXE RUNS. IF NOT THEN YOU WILL BE SENDING DUPE DATA RECORDS ACROSS THE ECHO AND PISSING A LOT OF PEOPLE OFF :) . See example above. After processing temporary data files and tossing them into a temporary HMB UECHOOUT.EXE will call up SECHO.BAT to run the echomail processor. ABOUT SECHO.BAT: =============== Secho.BAT calls up a HMB echomail processor of your choice. For example, with Gecho 1.0 it would look something like this: cd c:\fd\gecho gecho scan cd c:\sbbs\xtrn\ufobase exit ! You must have an echomail processor that will process the old style HMB. Gecho 1.0 is what we have tried it on here. ! VERY IMPORTANT: This can be complicated... I'll try to explain it as best as possible. Say for example you are running a BBS that has a JAM message base. Your Echomail processor can process echomail for both JAM and HMB message bases. Lets say the echomail area you're going to toss to also has "human" mail. Well, obviously in your echomail processor you CAN'T have both Jam and HMB defined. So you MUST copy your echomail processor to another directory and set it up exclusively for UECHOOUT.EXE. ! To be on the safe side, I would copy the echomail processor of your choice; Gecho, Jmail, AlexiMail, Qecho, Freemail, etc. etc., into a directory and set the copy of it up EXCLUSIVELY for use with UECHOOUT.EXE. This will save a lot of headaches and confusion. The echomail processor of your choice will scan the HMB for outgoing echomail messages. It will then bundle them up into packets and archive them into arcmail to be sent out to your echomail links. ! BE SURE TO READ THE DOCUMENTATION OF THE ECHOMAIL PROCESSOR OF YOUR CHOICE TO LEARN HOW TO SET UP A PARTICULAR ECHOMAIL PROCESSOR FOR UECHOOUT.EXE ! As mentioned before, we use gecho 1.0 as the echomail processor for UECHOOUT.EXE. Below is a capture of some of the configuration screens that may help you understand it better. Here is a picture of our Pathnames: ╒══════════════════════════════════════════════════════════════════════════════ │ GEcho SETUP 1.00 ∙ Unregistered Evaluation Version 1:3607/20 │ Copyright (C) 1992 Gerard J. van der Land. All rights reserved. ╘══════════════════════════════════════════════════════════════════════════════ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒╒══════════════════════════════════════════════════════════ Pathnames ╕▒▒▒▒ ▒▒▒▒│ │▒▒▒▒ ▒▒▒▒│ Message base C:\SBBS\XTRN\ │▒▒▒▒ ▒▒▒▒│ Netmail C:\FD\MAIL\ │▒▒▒▒ ▒▒▒▒│ Inbound mail C:\FD\FILE\ │▒▒▒▒ ▒▒▒▒│ Outbound PKTs C:\FD\PACKET\ │▒▒▒▒ ▒▒▒▒│ Outbound mail C:\FD\OUTARC\ │▒▒▒▒ ▒▒▒▒│ Bad echomail C:\FD\BADECHO\ │▒▒▒▒ ▒▒▒▒│ Secure mail C:\FD\SECURE\ │▒▒▒▒ ▒▒▒▒│ Personal mail C:\FD\MAIL\ │▒▒▒▒ ▒▒▒▒│ Rcvd netmail │▒▒▒▒ ▒▒▒▒│ Sent netmail │▒▒▒▒ ▒▒▒▒│ Nodelist C:\FD\NODELIST\ │▒▒▒▒ ▒▒▒▒│ Swapping C:\FD\ │▒▒▒▒ ▒▒▒▒│ Semaphore C:\FD\ │▒▒▒▒ ▒▒▒▒│ │▒▒▒▒ ▒▒▒▒╘═════════════════════════════════════════════════════════════════════╛▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ─────────────────────────────────────────────────────────────────────────────── Where the Hudson Message Base is located Notice the first line, where the HMB is located. Also notice where the outbound PKTs are. Here's an example of the WoodyWare echo area: ╒ View 91/93 ════════════════════════════════════════════════════ Area manager │ │ Area name WOODYWARE │ Comment │ Area type Echomail │ Format Hudson │ Board 1 │ Group A - FidoNet │ Options Security Yes Disconnected No Notified No │ Check SB Yes Import SB Yes Tiny SB No │ Mandatory No No %PASSIVE No Visible Yes │ Allow Pvt No Del future n/a Keep SysOp n/a │ Purge info Days old 0 Days rcvd 0 Max msgs 0 │ Origin line Compu<>Link Online | WoodyWare Support BBs 1(205)7391469 │ Origin AKA 1:3607/20 │ Seen-By 1:3607/20 │ Export list 1:3607/10 │ │ │ │ │ ╘══════════════════════════════════════════════════════════════════════════════ ─────────────────────────────────────────────────────────────────────────────── Enter-Edit Ins-Add Del-Delete F2-Global F4-Find F5-Browse Esc-Exit Notice the Area Tag name , the areatype as Echomail, the format as Hudson and the Board Number. This is just an example of what we have used here on occasion. PLEASE READ THE DOCUMENTATION OF THE ECHOMAIL PROCESSOR OF YOUR CHOICE TO SET UP YOUR ECHOMAIL PROCESSOR FOR UECHOOUT.EXE. GECHO 1.0 IS AVAILABLE FOR FREQ HERE AS GE_100.ZIP IF YOU WANT TO USE IT. ! Be SURE you get the permission of a moderator of a particular echo before you start transmitting data. ! You are free to use the WOODYWARE echo to send/receive Phase 3 InterBBS Echomail. Please netmail me at 1:3607/20 if you want to hook up. ! WOODYWARE currently isn't on the FidoNet Backbone at this writing. Hopefully, with your and others help we can get the WOODYWARE echo on the fidonet backbone in the near future and transmit data without incurring LD phone bills! Write me at 1:3607/20 if you're interested in helping get WOODYWARE on the Fidonet backbone.