UU2FLO v1.0 =-=-=-=-=-= Written by Ray Akey (aka Heavy Metal) From an idea proposed and started by Dave Vandermeer (aka Night Stalker) PLEASE READ THESE DOCS IN FULL. I know the joys of receiving a new toy and how docs are very easy to overlook but if you wish your system to receive and process news 100%, please take the few minutes to read this doc. It's not really that long, nor is it technically worded. First of all, this program assumes the following: - that you already have Matt Dillon's UUCP (or some compatible setup for UseNet traffic) up and running. - that you have a fidonet compatible address and a fidonet compatible mailer up and running. History: ======== UU2FLO was written mainly because of the UUCICO program's limitations and it's slow transfer speed. UU2FLO simply does the job of converting batched UUCP files to a format that allows them to be transferred to a UUCP node using any FidoNet-compatible mailer. This allows for MUCH MUCH faster transfer by using your ZEDZAP/ZMODEM mailer (ie. Trapdoor or the soon to be EMSI-ready MetalSoft mailer "Flood") to achieve maximum transfer. The only stipulation is that the receiving node must have some sort of FidoNet-type address. For example, The Metal Shoppe offers a network called AFidNet which is a STRICTLY AMIGA network. We use AfidNet addresses to transfer UseNet news (UUCP news files) to nodes that are in the AFidNet network and we use FidoNet addresses to transfer UUCP messages to nodes that have a FidoNet address. To get a template of the arguments UU2FLO supports. enter "UU2FLO" in your CLI/Shell. An example follows: SYNTAX: UU2FLO LOCAL REMOTE FQFA where, is your system's UUCP nodename. is the receiving system's UUCP nodename. is the remote system's fully qualified fidonet address. You may omit the "point" portion of the fidonet address if your mailer supports 3D addressing. examples: UU2FLO LOCAL metshop REMOTE ntrnl FQFA 1000:6820/0 UU2FLO LOCAL metshop REMOTE mythago FQFA 1000:6800/6 "metshop" is my UUCP node name "ntrnl" and "mythago" are remote UUCP nodes that poll my system "1000:6820/0" and "1000:6800/6" are the AfidNet fido compatible addresses of ntrnl and mythago, respectively. FLO2UU.EXE ========== This AmigaDOS script is included to allow the fidonet system to restore the UUCP files, that he received through his fidonet mailer, back to his UUSPOOL: directory. For example, each node runs UU2FLO to convert the remote system's waiting UseNet News/Mail to the fidonet transferrable format. Once those files are transferred by your perspective front-doors, they arrive in your "inbound" directory. They must then be moved to the UUSPOOL: directory so that UUCP can find and process them. SYNTAX: EXECUTE FLO2UU.EXE where, is the receiving system's inbound mail directory. is the receiving system's UUCP sitename. Please note that the required UUXQT command is not present in the FLO2UU.EXE script because I realize that not all systems unpack mail/news the moment they receive it. If you DO wish your news to be unbatched the moment it is received, load UU2FLO.EXE into any text editor and add the following command to the end of it: UUXQT where is the path where your UUXQT command is located. if you do not add the UUXQT command to the FLO2UU.EXE script, you must at it to your CRON or event scheduler. Future Plans: ------------- XenoLink compatible file renaming & extensions. ...no others at the moment - any suggestions? =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Bug reports: FIDO: Ray Akey@1:246/74 CLINK: Ray Akey@911:8000/2 AfidNET: Ray Akey@1000:6800/0 INTERNET: rakey@metshop.jammys.net The Metal Shoppe BBS -> (519) 256-0278 (519) 255-7378 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=