PC Online 1997 August

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

/ PC Online 1997 August / PCO0897.ISO / filesbbs / dos / fdt.arj / FDT.ENG < prev next >

Wrap

Text File | 1996-03-17 | 56.8 KB | 1,403 lines

FrontDoorTool V1.5 _ by Heiko Stoevesandt 1 ╔═════════════════════════════════════════════════════════════╗ ║ Frontdoor-Tool ║ ╚═════════════════════════════════════════════════════════════╝ ╒══════════════════════════════════════════════════════════════╕ │ -= Inhaltsverzeichnis =- │ ╘══════════════════════════════════════════════════════════════╛ ╒══════════════════════════════════════════════════════════════╕ │ -= Table of Contens =- │ ╘══════════════════════════════════════════════════════════════╛ Frontdoor-Tool..............................................1 Table of Contens............................................1 The world before...........................................2 What's going on here?......................................2 Guarantee:.................................................2 Requirements:..............................................2 Installation:..............................................3 GLOBAL Parameters...........................................3 Batch-Tools.................................................4 We use the FDT-FaxGateWay...................................4 Whats On Hold...............................................8 Mail Historys...............................................9 Updating LastCaller........................................10 Shorten LogFiles...........................................11 Sorting LogFiles...........................................13 Local Poll via FDT.........................................14 FILES.BBS-Funktions........................................16 ROBOTER-Mails..............................................18 OUTBOUND / FileAttaches "on the Fly".......................19 MGR-Find SCAN..............................................20 Generate Pointlists in the "Boss"-Format...................21 5D-List...................................................21 NodeDiff's workage.........................................22 Writing a protocol into FD-LOG.............................22 Show PKT...................................................23 InfoScreen.................................................24 Foreword to InfoScreen.....................................24 The Multi(Single)-Line-InfoScreen..........................25 Potential parameters:.....................................25 Keyboard commands.........................................26 The following keyboard commands are similar, resp. call Frontdoor.................................................26 Altered functions for Frontdoor...........................26 FileInfo-Viewer...........................................27 Special 2 Inbound & Outbound-View.........................27 Browsing Nodelists........................................28 Line-Controlling..........................................29 Interactive controlling at the InfoScreen.................29 AT THE END.................................................30 Planned Features:.........................................30 Address of the Autor......................................30 FDT Beta tester:..........................................30 Translation...............................................30 COPYRIGHT.................................................31 Exclusion of liability and warranty:......................31 FrontDoorTool V1.5 _ by Heiko Stoevesandt 2 ╒══════════════════════════════════════════════════════════════╕ │ -= The world before =- │ ╘══════════════════════════════════════════════════════════════╛ What exactly is FDT? I often used fragmentary utilities to write a function which was moreover insufficient. Above all I found it rather unneccessary to write all parameters in CTL files again and again which must be updated after every change of the programme. So I wanted a tool which sizes hold of other configs, fits to other tools or is very easy to convert. In some cases I needed the help of batch files, but I think I found a bearable ratio of mixture. As I wanted FDT to do far-reachingly without other configs from time to time the parameter lines are very long! FDT offers a wide range of possibilities and I permanently make improvements and flaw corrections. The Program is fully in english language. The documentations comes in dual versions. One is english the other is in german language. ╒══════════════════════════════════════════════════════════════╕ │ -= What's going on here? =- │ ╘══════════════════════════════════════════════════════════════╛ Guarantee: Sounds good, doesn't it... But all I can guarantee is that the program needs some space on your hard disc. And even in that case I only takeover for a partial guarantee. :-) Requirements: At least: - 386SX-16 - 480 KB free RAM - 512 KB free XMS or EMS - MS-DOS 3.3 - Frontdoor 2.02nc ( recommended FD 2.20c mL or the 2.12 SW ) FrontDoorTool V1.5 _ by Heiko Stoevesandt 3 ╒══════════════════════════════════════════════════════════════╕ │ -= Installation: =- │ ╘══════════════════════════════════════════════════════════════╛ You can copy FDT on every place of your hard disc. It would be the best if you establish a partition of 20 MB and name it FDT. That means you would also have enough space for the OS/4 version. But still it is convenient to copy FDT somewhere into the path Either into the frontdoor directory or -to the place where the compression programmes are. All parameters are read out of the Frontdoor files. You should set the DOS variable FD. -But you can also start FDT always with the parameter /S=C:\FD, then FDT is accepting the given path to SETUP.FD. Furthermore, SETUP.FDT is needed for the InfoScreen This is a feature of my FDT packet and you shall adjust it to you own system. All you need is a simple text editor. ╒══════════════════════════════════════════════════════════════╕ │GLOBAL Parameters -= =- │ ╘══════════════════════════════════════════════════════════════╛ /S=[path to Setup.FD] has been dokumented, The setup that FDT shoud use it. /L=LogFile path&name Herewith the LogModus is simultaneous activated. A LogFile is written in Frontdoor format In this file only unimportant things are recorded, just as every good Logfile does. If you just use the parameter /L, the Logfile is written out of the TASK variable and SETUP.FD. /T=Tasknumber Tasknumber you want to work with. Is mostly interesting when working with semaphore files. @FILE-CMD Working with several commands in a file. FrontDoorTool V1.5 _ by Heiko Stoevesandt 4 ╔══════════════════════════════════════════════════════════════╗ ║ Batch-Tools ║ ╚══════════════════════════════════════════════════════════════╝ ╒══════════════════════════════════════════════════════════════╕ │ -= We use the FDT-FaxGateWay =- │ ╘══════════════════════════════════════════════════════════════╛ To use this function, some preparations are neccessary! Just start with the simple idea. I wanted to sent a fax via NetMail by using a modem. As you know, Frontdoor can receive faxes anyway, at least after the shareware testing phase. In order to not wanting to blow out the programming part, FDT uses ZFAX.COM which is included in every Frontdoor version that exists Only some little changes are neccessary in a helping batch. What makes FDT being effective? In principle, it makes a NetMail to a text file, together with a starting batch and a little text data bank. After this, the mail is sent and is either deleted according to the flag or marked as SENT/RCVD. During rescanning the data bank is being updated and faxes which were not received are deleted or sent again. For FaxGateWay-Function start FDT with the following parameters: /A=n in which n is the amount of hours FDT tries to sent the fax again. Default is 999 hours, 1 hour is minimum. /B=File File is a batch file which should be generated. Default is FDTFAX.BAT in the actual directory. /C=File File ist a PCX file which is sent along with CoverPage. Default is NO Cover. /D=TaskNum Tasknumber for the errorlevel definition above /E=Errorlevel The errorlevel that has to be created for TaskNum. /H=HeaderASC An ASC (!) - header which is sent after the CoverPage and before the actual fax. /O=Directory Here resides the outgoing faxes. FrontDoorTool V1.5 _ by Heiko Stoevesandt 5 /P=Passwort If a mail comes from outside, that means the sender is not an aka from Frontdoor, you can handle them only with the passwort. All you have to do is to add a spaceand an exclamation mark. But then there is a limitation that ZFAX commandos cannot be in the text which start with tilde ('~'). If there's no passwort given, no one from "outside" can send a mail. /R=Level There are 3 different Scan levels for FDT: 0 = Scan NetMail only. 1 = Reorg and ResendFax only 2 = 0 + 1 /Z=ZFaxDir The list which contents ZFAX.COM. Structure of a NetMail: To: FDTFAX Re: FaxNumber (!PW) ------------- FaxText Parameters of the author. FDT /L FAX /O=Z:\ZYXEL\FAXOUT /B=Z:\ZYXEL\FDTFAX.BAT /Z=Z:\ZYXEL /E=90 /D=1 /R=2 List in detail: FDT /L FAX Calling modul FAX, starting LogFile! /O=Z:\ZYXEL\FAXOUT List of the text fax files /B=Z:\ZYXEL\FDTFAX.BAT The generated Fax-BatchJob /Z=Z:\ZYXEL List of ZFAX /E=90 /D=1 As ZFAX is not on the same line as FDT an exit level for task 1 is generated which then calls FDTFAX.BAT . /R=2 NetMail-Scan and Rescan. FrontDoorTool V1.5 _ by Heiko Stoevesandt 6 FDT is going to call a batch file (ZFAXSEND.BAT) which has to be left in the ZFAX list!! It should look like this: For ZFAX 2.xx zfax.com 1 %1 %2 if errorlevel 1 goto nosend echo %1>>zfax.snd :nosend For ZFAX 3.xx zfax.com sf %1 %2 if errorlevel 1 goto nosend echo %1>>zfax.snd :nosend FrontDoorTool V1.5 _ by Heiko Stoevesandt 7 In ZFAX.SND all files are put down which has been sent. In ZFAX.FDT different details of every fax are noticed which FDT needs again for the reorg. During Reorg/Rescan every line in ZFAX.FDT is compared with ZFAX.SND. That could result in the following: 1 Fax has been sent * Text file is deleted * NetMail goes to the sender 2. Fax has not yet been sent. 3. Fax has not been sent because of a timeout. * TextDatei is deleted. * Error report goes to the sender. After passing through FDTFAX.BAT should be deleted to make sure you don't call it once again. It is then going to be renewed by FDT. Batch for Line 1 looks like: CD\ZYXEL IF NOT EXIST FDTFAX.BAT goto NoFaxe CALL FDTFAX.BAT DEL FDTFAX.BAT :NoFaxe By the way, my fax number is +49-421-3722174 ;-) FrontDoorTool V1.5 _ by Heiko Stoevesandt 8 ╒══════════════════════════════════════════════════════════════╕ │ -= Whats On Hold =- │ ╘══════════════════════════════════════════════════════════════╛ /O=OutFile /U={FileName} Take a different file as USER2AKA.FDT in the Frontdoor -System directory. ** Please read the describtion in the MAILHIST A little ASC statistics is generated which shows whats on hold. It is the same as the one you can see at the InfoScreen by using ALT-B, but it is written into a file so you can see it every time you want. FDT looks for a file named NAMES.WOH. This file has the following contents: [NodeNumber] [Changed text] Sample: 2:2426/3035 Heiko Stoevesandt Sample: FDT WOH /O=WOH.TXT The file can automaticely generatet with the programm PMGR ( The PowerManager ) or manual with a ASCI-Editor. FrontDoorTool V1.5 _ by Heiko Stoevesandt 9 ╒══════════════════════════════════════════════════════════════╕ │ -= Mail Historys =- │ ╘══════════════════════════════════════════════════════════════╛ Summarize Mailhistory and generating a survey Parameters: /I Summarize Inbound History + Sorts the History /O Summarize Outbound History + Sorts the History /W Writing Summary + Sorts the History /Z TestMode /A=MaxRecord Max. Amount of Records in INBOUND.HIS /B=MaxRecord Max. Amount of Records in OUTBOUND.HIS /U={FileName} Use a different file as USER2AKA.FDT in the Frontdoor System directory - /R Reverse sorting order. /F=FidoAka It_s a Filter. Shows only the node with_FidoAka_ Warning: INB?.HIS OUT?.HIS are being deleted without a test running through. 4 ASC Files are generated which are called TRAFFIC.1 - 4. 1+2 are Inbound; 3 + 4 are Outbound tables. 1+3 are summaries about single sessions. 2+4 are summaries of one single node. ** This part is also guilty for the WOH- and InfoScreen parameters- Since the Beta 1.34B04.07.95 nodes can be combined. It happened that you sent a crash mail to someone under 2 different addresses but it was one and the same person. To let FDT take note of this, you have do define a file in the FD systempath The following rules are valid: - Every line starting with a valid nodenumber is a main-AKA - Every line with an indented nodenumber is a sub-AKA For example: 2:2426/3000 2:2426/3035 2:2426/3036 37:1/315 144:4902/0 144:4902/1 No matter to what address your mail has been crashed to, FDT is always going to register the Fido 3000 AKA on the traffic statistics!! FrontDoorTool V1.5 _ by Heiko Stoevesandt 10 ╒══════════════════════════════════════════════════════════════╕ │ -= Updating LastCaller =- │ ╘══════════════════════════════════════════════════════════════╛ FDT can also change the LASTC*.FD file. Herewith as the last call any name can be entered as OutCall or InCall. The following parameters are possible: /F=FromUser Name, otherwise FDT /N=Nodenummer The entered Fidaddress, otherwise 2:2426/3999 /W=Wohnort Residence which shall be entered. /R Entering OutCall instead of InCall. /O=Task Which task has to be changed, otherwise the actual task Example: FDT /L LCALL "/F=Heiko Stoevesandt" /W=At_Home /N=2:2426/9999 /R FrontDoorTool V1.5 _ by Heiko Stoevesandt 11 ╒══════════════════════════════════════════════════════════════╕ │ -= Shorten LogFiles =- │ ╘══════════════════════════════════════════════════════════════╛ LOGSHORT I had the idea when I let Frontdoor running with RDEBUG for some weeks. Hereby 5 lines came up 20 MB (!) the week only with LogFiles from FD. That couldn't be right I said to myself and so I tried to find a LogShortener who could delete fixed lines. Some tools I found were good enough for the functions, but the only program I could have used in my case was Clear. The problem was that it always changed the complete logfile into CAPITALS. Unfortunately I wasn't able to reach the writer by Fido. Well, to make it short: FDT had to be enlarged ;-). There are the following parameters: /A Append Modus ( not ready yet). The output file is lengthened by the input file after the shortening. . /J Permit Overwrite. Especially if input and output files are matching. /Z TestModus; After shortening the file FDT.$$$ is left. /I=Filename Input-file; the file who has to get shortened. /O=Filename OutPut-Datei; the file that has to be written. /R=Rules-Datei Contents the rules after which one or more lines are being deleted. FrontDoorTool V1.5 _ by Heiko Stoevesandt 12 Here comes a file as example: E.G. Call: FDT /L LOGSHORT /J /I=FDTASK.LOG /O=FDSHORT.LOG /R=P:\FDT\LOGSHORT.FDT E.G. file: ; LogShort - Example ; ; created : 21.04.95 By Heiko Stoevesandt ; ;------------------------------------------------------------- ; ; ; General Rules ; ; Possible Keywords ; ; Double = Deleting the same, following up files Double ;------------------------------------------------------------- ; ; After the following statement, files are totally removed if ; they fulfil one of the following rules. ; DELLINES ; ; FOL The following words have to appear, but they have to ; start with $1-$9 (first to ninth word). If there's a ; different word, the line won't be deleted. ; ; TRI Leave trivialities out of consideration. The follow up ; line has to start the same way, otherwise the line won't be ; deleted. ; ; KOM Leave a complete line out of consideration if it's named ; as follows FOL $1=Msg $3=from ;z.B. Msg 1023 from 2:2426/3011 to 2:2426/3140 via 2:2426/3140 FOL $1=Destination $2=System $4=doesn't $5=exist, $6=Msg TRI Bundle not sent to TRI NoTouch: KOM Rescan requested KOM Preparing outbound mail ;RING without telefonnumber not in protocol KOM RING ;------------------------------------------------------------- ; EOF FrontDoorTool V1.5 _ by Heiko Stoevesandt 13 ╒══════════════════════════════════════════════════════════════╕ │ -= Sorting LogFiles =- │ ╘══════════════════════════════════════════════════════════════╛ Parameters: /A=Logfilename The LogFile which has to be sorted /Z TestMode By using LOGSORT, Log files are sorted. The begin of a block will be established if it starts with 10 minus signs (Frontdoor-Style-Logformat). Out of this and the follow up line the date and time is going to be established. If a space follows, 00:00:00 h is assumed. If there are mistakes, the function is continued as good as possible, but the temporary file won't be renamed, respectively the original won't be deleted. It'll stay with the filename of the original file and the extension.$$$. That also counts for the test mode. This function can manage 6000 blocks, that's a LogFile size of about 8 MB. If this function is used, possible connected logical blocks can get apart if a caller goes over the 00:00 - limit. FrontDoorTool V1.5 _ by Heiko Stoevesandt 14 ╒══════════════════════════════════════════════════════════════╕ │ -= Local Poll via FDT =- │ ╘══════════════════════════════════════════════════════════════╛ Parameters: /O=OutboundPath /A=Address /P=SessionPassword /U=UserName_to_write_to_Protokoll /Z TestModus /I INBOUND.HIS to write /F FD.LOG to write LOCPOLL does a _real_ local poll, that means it looks into the netmail inbound to find out which files (+Attach) are for the given node and copies them into a named outbound. There are some things that deviate a little bit from Frontdoor, but normally are insignificant. LocPoll only functions in the way out. If you want to have packets or files from the inbound of another program, you should buy a corresponding program. The most simple application are Sysop Points. To make sure you don't wrote anything wrong, a SessionPW is neccessary. Otherwise you could get or delete anything from an address which you actually didn't want to. A simple example: FDT /T=20 /L=LOGPoll.LOG LOCPOLL /A37:1/317 /P=THERE /O=C:\FD\IN Herewith all NetMail and fileattaches are copied. In the outbound exist one PKT foer each mail. FileAttaches are also copied to the outbound. Is the mailflag KILL the mail will killed after proceed. Normaly the mail will flagged as SENT. The behavior is identical to these from FrontDoor. If you don't want your own netmail outbound to be edited because you probably want to test the routing or anything else, you can set the parameter /Z which copies everything but doesn't touch the outbound. Instead of this, every operation will be shown on the screen. Routing is supported for only a minimum. Also, only the verb ROUTE-TO is taken into consideration. The only permitted macro is *. Besides, the routing has to be in the global part of the Route.FD. FrontDoorTool V1.5 _ by Heiko Stoevesandt 15 If it's neccessary to need a certain ROUTE.FD, you can set FDT on a TASK which is free. FDT also pays attention to the Task if it runs under FD2.11 or 2.02.. For Task 20 the Route.FD must be a ROUTE20.FD. Possible ROUTE-TO are for example: ROUTE-TO 37:1/317 37:1/317.* 144:4902/44 144:2002/* Of course you can handle several lines ROUTO-TO at the same time. Notice: FrontDoor distinguishes ROUTE-TO, but ROUTE-FILES. FDT doesn't!! Messages or files with a HOLD-Flag can't be routed, you always have to call if you want your packet. FrontDoorTool V1.5 _ by Heiko Stoevesandt 16 ╒══════════════════════════════════════════════════════════════╕ │ -= FILES.BBS-Funktions =- │ ╘══════════════════════════════════════════════════════════════╛ This function won't be developed any more. Oliver Weindl's Wizard works much better than FDT. Description: This is one of the functions that took most of my time. At first, here's a brief survey: /I=IncludeDir Multiple calls are possible /A=FLSEARCH.CTL Text file that contents file directories. /V No search in subdirectories. /O=OutputFile /H=HeaderFile /F=FooterFile /Q QBBS / RA(?)-Format /R SortFlag /C=CounterFile Path and Filename to FD - Logfile /P=PathExclude Don_t save this path in Counter-Helpfile /D=[0,1,2] Check Directory for orphaned files and so on. Default = 0 0 = No Check 1 = Check and write to LOGFILE 2 = Check, and when file orphaned, kill it. /E=EntryLevel Create FLSEARCH.CTL with Accountlevel. 0-65534 ( 65535 for internal use ) The idea of these functions is very simple. It should have been possible to manage files without using an additional program and to keep them sorted. So I did it without an automatically header. Herewith, fileboxes can be summed up by their content and also labled with only one big headline but are still schematically subdivided and sorted. The switches in particular: /I=PATH is a path which is examinated together with all available subdirectories for the file FILES.BBS. All entries are checked of their existance. If a file won't be found, it shows an error report but continues obviously. /A=FILE is a macro file which contents paths which should be examined to avoid that you haven't to type /l every time. Unfortunately, DOS doesn't allow to give parameters with more than 128 characters. The filename could be FLSEARCH.CTL which is used by many mailbox programs. /O=Datei is a total file which has to be used for the output. If you don't want a total file to be generated, you can give /O=NUL. /H=Headerfile that should be clear. You have to write the Header in front of the total file. As a standard parameter you have to use HEADER.FDT. FrontDoorTool V1.5 _ by Heiko Stoevesandt 17 /F=Footer that should be also clear. You have to write the Footer on the back. As a standard parameter you have to use FOOTER.FDT. /Q forces FDT to consider all data entries as QBBS compatible. By outputting a total filelist, too long describtions are avoided. If it's not possible to tear a describtion with words because the line has more than 40 characters, it cuts of right across the word. Besides, in this mode time and length of the file are taken out of the DOS dates. If the switch /Q is missing, the outputting file is filled with what is written in the file FILES.BBS. /R With this switch, the file FILES.BBS will be sorted. As a help file FILES.BAK is generated in the directory and after the sorting it will be deleted, so that BAK's disappear after the sorting in every case. /C=FD.LOG let the counter of the Files counting up by using the FD.LOG. It always has to be a Frontdoor-LOG-file. Everything standing between "Sent" and the ending ";" is considered as a filesend. If the file (including the path but excluding the drive) is found, the counter between "[" and "]" increases about one. /P=[Path] doesn't save this path in the file amongst. Herewith, the performance can be accelerated considerably. Path is WITHOUT Drive! Here, the file FILES.BAK will be also used as a help file. Of course you can use the switches /R und /C during a run through. /E=EntryLevel If a file path is missing in the FLSEARCH.CTL, a new line will be generated. But it doesn't touch the FLSEARCH.CTL, merely a file FLSEARCH.NEW will be written. EntryLevel describes the level which entries the line. /V No search of subdirectories except the given path. Example: FDT FILES /T=255 /L=SORT.LOG /I=T:\FILEBOX /O=NUL /Q /R /C=FD.LOG All directories in T:\FILEBOX which contains a file FILES.BBS will be counter updated with FD.LOG and arranged alphabetically. FrontDoorTool V1.5 _ by Heiko Stoevesandt 18 FDT FILES /O=24263036.LST /A=FREE.ARS /H=HEADER.FDT ..... /F=FOOTER.FDT /T=255 /L=Q:\BOX\LOG\FDT$TASK$.LOG /Q A total file will be generated which searches for all directories in FREE.ARS and arranges them to 24263036.LST. FrontDoorTool V1.5 _ by Heiko Stoevesandt 19 ╒══════════════════════════════════════════════════════════════╕ │ -= ROBOTER-Mails =- │ ╘══════════════════════════════════════════════════════════════╛ This function is very simple. If you want to outpoll someone, by using the command FDT POLL /R2:2426/3000 a corresponding address can be outpolled. For this, an empty Poll-Msg will be generated. At the moment it is implemented that you can send any text message to someone. Commands: POLL Generating Poll-Msg TEXT Send text as MSG RPOLL Delete Poll-Msg /F<Text im Re: Field> /R<receiver-adresse> /T<Txtfile, as messagel> /M<MsgBits> MsgBits could be: P = MSGPRIVATE C = MSGCRASH Y = MSGREAD S = MSGSENT K = MSGKILL L = MSGLOCAL H = MSGHOLD Followed by a '+' or '-' , the single flags can be switched ON or OFF. Example: FDT /L ROBO POLL /R2:2426/99 FDT /L ROBO RPOLL /R2:2426/99 FDT /L ROBO TEXT /R2:2426/6000 /TMAIL.TXT "/F Compiling New Version" FrontDoorTool V1.5 _ by Heiko Stoevesandt 20 ╒══════════════════════════════════════════════════════════════╕ │ -= OUTBOUND / FileAttaches "on the Fly" =- │ ╘══════════════════════════════════════════════════════════════╛ Since the 0.21g you may write OutFile attaches. This function is so extensive in his possible parameters that it needed his own config file. The idea of this function was that you can simply put files into a directory and then send it via FDT with a netmail to a certain person. Every addressee has his own subdirectory. If files have been sent, they will be deleted by Frontdoor. (Del/Sent). By using the parameter /I you state which config file FDT has to use. In the config file all lines with a semicolon at the beginning and with spaces will be ignored. Bspl: ; OUTDIR.CTL-File ; ; DIR FROMAKA TOAKA FLAGS [@MESSAGE] P:\PRV\KLAUS 2:2426/3035 2:2426/6002 Hold Direct @SendKlau P:\PRV\KLAUS2 2:2426/3035 2:2426/6002 Crash Direct @SendKlau P:\PRV\GEROLD 2:2426/3035 2:2426/3121 Hold Direct @SendGero P:\PRV\TORSTEN 2:2426/3035 2:2426/3131 Direct ; ;-eof- DIR is a valid directory. FROMAKA has to be an aka known by Frontdoor. TOAKA could be any Fido address. FLAGS only CRASH HOLD DIRECT are possible. MESSAGE is an optional parameter which sends along a netmail to the file attach. The mail HAS to have the ending FDT and stands in the same directory as in which FDT has been started. Example for OutFiles: FDT OutFiles /I=OUTDIR.CTL /T=11 FrontDoorTool V1.5 _ by Heiko Stoevesandt 21 ╒══════════════════════════════════════════════════════════════╕ │ -= MGR-Find SCAN =- │ ╘══════════════════════════════════════════════════════════════╛ /U=user /U=. tells which MGR's has to be found' Here, a file called MGROPT.BAT will be generated which appears as follows: Set MGROPT=GECHO FILEMGR It is merely ascertained which MGR's have to get called and these are utilized as SET-variables. With this, only aimed MGR's can be called who have NetMails left. The often unneccessary run through of all MGR's can be dropped. GECHO TOSS -NoMgr IF EXIST MGROPT.BAT DEL MGROPT.BAT FDT SCAN /T=255 /L /U=GECHO /U=ALLFIX /U=VOTEMGR IF NOT EXIST MGROPT.BAT Goto NoMgr CALL MGROPT.BAT DEL MGROPT.BAT :NextMgr ECHO @echo off >tmp.bat ECHO SET U=%%1>>tmp.bat ECHO SET MGROPT=>>tmp.bat ECHO IF NOT %%2/==/ SET MGROPT=%%2 %%3 %%4 %%5 %%6 %%7 %%8 %%9>>tmp.bat CALL TMP.BAT %MGROPT% DEL TMP.BAT IF %U%/==GECHO/ CALL GECHO MGR IF %U%/==VOTEMGR/ CALL VOTERUN.BAT IF %U%/==ALLFIX/ CALL AF\ALLFIX MGR IF NOT %MGROPT%/==/ goto NextMgr :NoMgr GECHO SCAN IMPORT Pack -Hold [usw.] Example: FDT SCAN /L /U=GECHO /U=ALLFIX FrontDoorTool V1.5 _ by Heiko Stoevesandt 22 ╒══════════════════════════════════════════════════════════════╕ │ -= Generate Pointlists in the "Boss"-Format =- │ ╘══════════════════════════════════════════════════════════════╛ FDT PL /I=FileName Otherwise, POINTS24.* is assumed O=FileName Otherwise, FDPOINT.PVT is assumed /Z=ZONE new Zone Number /5[=Filename] 3D-Poinlist with convertion of the towns into "normal" 3D format (as above) /4 Convert 4D-Pointlist /X Convert Pointlist in Boss format /A Adding to an existing file /B Boss telephone number and flags, instead of 9,9600 As Frontdoor can only use lists in the "BOSS" format, FDT stands in and works for Fido. You should always generate a POINTS.PVT. Frontdoor then can work properly with it. ╒══════════════════════════════════════════════════════════════╕ │ -= 5D-List =- │ ╘══════════════════════════════════════════════════════════════╛ In this time, it is attached a great importance to a short PL. But unfortunately, the clearance and exact determining of residence of a point suffers on it (e.g. DD instead of Dresden is registered). FDT expands this motor vehicle numbers by using a mot.veh. translation table, which either has FIDO-5D.LST in the directory where FDT has been called, or responds over /5={Path}[Filename]. FDT changes DD back to Dresden. Besides the BossFlags are taken with it, too. So you get back the overall view and don't have to remember all motor vehicle numbers. (this was just for example) Example: FDT PL /5=CIA5D.LST FDT PL /A /I=..\3035LIST FDT PL /A /I=..\TREKNET\TREKPNT /4 /Z=37 FrontDoorTool V1.5 _ by Heiko Stoevesandt 23 ╒══════════════════════════════════════════════════════════════╕ │ -= NodeDiff's workage =- │ ╘══════════════════════════════════════════════════════════════╛ ND /D=DiffFile otherwise NODEDIFF /I=Nodeliste otherwise NODELIST /R after successful assimilation, deleting old NODELIST & DIFF /C CRC-check out of function F10 breaks off FDT is very exact in the default attidude to make sure that a diff has enough functions to work successfully. FDT grows 100% together to the FTS. Which means that that diffs with a wrong checksum or other changes won't be inbounded at all. They just stay where they are. Example: FDT ND /D=PR24DIFF /I=POINTS24 ╒══════════════════════════════════════════════════════════════╕ │ -= Writing a protocol into FD-LOG =- │ ╘══════════════════════════════════════════════════════════════╛ PRO Is writing a string into the actual Frontdoor protocol /H Oppress header /A AutoAdd Header when neccessary if you already have a header for today's date. If there's already a header for today's date, no new header will be written. /F=filename use other filename, otherwise use what's written in SETUP.FD. Most of the multiline systems use FD%TASK%.LOG. e.g. FDT /A PRO I switch the light off now. FrontDoorTool V1.5 _ by Heiko Stoevesandt 24 ╒══════════════════════════════════════════════════════════════╕ │ -= Show PKT =- │ ╘══════════════════════════════════════════════════════════════╛ PKTVIEW or PK Show details of PKT's /D shows not only the MSG header but also the MSG itself /Z test modus ( FDT.PKT will be generated ) filename Filename ( with or without path ), even with Wildcards The output can be stopped with ESC. e.g. FDT /T3 /L PKTView /Z O:\OPKT\37*.PKT Notice: FDT stopps searching after finding the first successful PKT. If you want more PKT of the same matching to be shown, you could use the following batch: ;-Example batch for FDT-PKT-Viewer ; IF %1/==/ goto Syntax FOR %%I in (%1) DO FDT /L PKTVIEW /D %%I goto ende :Syntax ECHO Appeal to %0 [PKTNAME-Matching] goto ende :ende ;-EOF- FrontDoorTool V1.5 _ by Heiko Stoevesandt 25 ╔══════════════════════════════════════════════════════════════╗ ║ InfoScreen ║ ╚══════════════════════════════════════════════════════════════╝ ╒══════════════════════════════════════════════════════════════╕ │ -= Foreword to InfoScreen =- │ ╘══════════════════════════════════════════════════════════════╛ The first version of InfoScreen wasn't surely too bad. Nervertheless it wasn't originally thought as Info, but rather as an indication with an EventManager. The available version of InfoScreen is a global information- and overall viewtool for Frontdoor. No other utility I know has this powerful access to internal Frontdoor structures and files. FDT has surely become such a tremendous instrument for Frontdoor user because of the InfoScreen. But of course I also have to say thanks to all the beta testers who called me constantly with improvements and who tested tireless and gave me the ideas to write new functions for this tool. So the InfoScreen is also a development of the beta testers, whose names are written in the appendix. I think that with the Info Screen I wrote a function that speaks for a product offering an open programming interface. FrontDoorTool V1.5 _ by Heiko Stoevesandt 26 ╒══════════════════════════════════════════════════════════════╕ │ -= The Multi(Single)-Line-InfoScreen =- │ ╘══════════════════════════════════════════════════════════════╛ The main parameter is INFO Potential parameters: /C=0 Used for programming. The screen won't be deleted after ending. /E=0 Not fetching forced events /F=0/1 Color (default-FD-results) instead of Mono 0=Mono 1=Color /K=Passwort Placing a Password.. (ATTENTION, you find it in the LOGFile) /M=0/1/2 0 No mover above left 1 Pulsating point above left 2 Shows routines (Program developing) /U={FileName} Take a different file as USER2AKA.FDT in the Frontdoor system directory. ** Read the describtion in MAILHIST /R Reverse order by overview of inbound and outbound flow e.g.: FDT INFO /T=255 /L /M=1 !!! NEW !!! Since 1.42 The main routine of the Info Screen is written completely new, that means it corresponds mostly with Frontdoor and his keyboard verification. There are 3 fields in InfoScreen: 1. Top Show information for SiteInfo, number of drives, over the top FDT will show time and date. 2. Middle Shows the task, configured in file SETUP.FDT, the lastcaller information also on the right side the resend activity in minimal form 3. Bottom Shows lastcaller info from FDT-Line. On the right side the Eventinfo. Above, in the bottom line from right window we see the same informations also in FrontDoor _. FDT shows not the word _mail_. But he will show _lock_ when keyboard is locked. FrontDoorTool V1.5 _ by Heiko Stoevesandt 27 ╒══════════════════════════════════════════════════════════════╕ │ -= Keyboard commands =- │ ╘══════════════════════════════════════════════════════════════╛ The following keyboard commands are similar, resp. call Frontdoor. Alt-E FM (Message Editor) will be started. Alt-J FD /TERM will be started. (Fossil is needed) Alt-C FDSETUP Alt-K Showing all F-Keys - User keys Alt-Z Call Dos-Shell ( Attention, I still didn't find a way to restore the video mode properly) Alt-L Lock/DeLock Keyboard Alt-H Help Screen Alt-V Undial-Manager Alt-Q, ALT-X, X End FDT CTRL-A Copyright notice (always shown by starting the shareware version Altered functions for Frontdoor Alt-A Activate event - show all events Alt-I Inbound History of ALL lines Alt-O Outbound History of ALL Lines Alt-R Recent activity - the activity of ALL lines Alt-B Mail Bundle - What's on WOH for whom Alt-F Forced call to a node. In contrast to FD a poll msg will be generated Alt-G Carries out a filerequest. In contrast to FD a request msg will be generated 1-9 (Only in the topical BETA) Look into a bundle of a line. Not only the mails are going t to get analysed, but also the FDC to a line. ALT-N Show NodeInfo Inbound- & Outbound- activyties and Nodelist- LookUp. Here works the detailinfo described later. Besides, it is paid attention to the existing user keys for the mailer. That counts for the keys which produce the error level and also for the keys which calls the programs! If a break has been set, after EVERY program seperated by a semicolon it'll make a break. FrontDoorTool V1.5 _ by Heiko Stoevesandt 28 ╒══════════════════════════════════════════════════════════════╕ │ -= FileInfo-Viewer =- │ ╘══════════════════════════════════════════════════════════════╛ In FDT I have installed a "little" Fileviewer which should be good enough for the needed requirements. Apart from the common cursor key functions (up/down, picture up.., etc.) the following things are added: F Find Text - search a certain text, F3 goes on with the search. D Detailinfo S Save-File ╒══════════════════════════════════════════════════════════════╕ │ -= Special 2 Inbound & Outbound-View =- │ ╘══════════════════════════════════════════════════════════════╛ If you type "D" in a line with a valid node entry, a highlighted line appears on the screen with which you can chose one of the entries. After selecting an entry by typing "Enter" FDT tries to read the information out of the LOGFILE . That works of course only if it is available. Many systems proved that oversized logfiles doesn't make sense and only lower the performance. Therefore, FDT first searches the pointed LOGFILE in the setup and then changes the extension into .OLD. But if that isn't entirely successful, FDT replaces the complete filename with FDTASK.LOG and last with FDTASK.OLD. If all of this doesn't lead to the wanted success, FDT stops the search. After being successful in having a result of the search the part of the logfile which fits to the entry in LastCaller is presented. FrontDoorTool V1.5 _ by Heiko Stoevesandt 29 ╒══════════════════════════════════════════════════════════════╕ │ -= Browsing Nodelists =- │ ╘══════════════════════════════════════════════════════════════╛ is called by Force-Poll Get Files NodeInfo Remark: I racked my brain over the nodelist browser of FDT. The nodelist is generated by TACCESS. I programmed the complete browsing and the internal structure with LOW-Level. All index trees and contexts had to be investigated very exactly. Originally, I didn't want to write a browser, but please consider the FDT browser only as a help to the nodenumber input!!! Nothing more or less. After typing an address or a name you'll find yourself in a FD-like nodelist-browser. Essentially it does the same as FD, but there are some differences: All nets of one zone are shown correctly. That means that even on zone level the 37:* lists the host address 1. It's easy to describe the reason why Frontdoor isn't able to do the same: FD uses ZONE.ZONE/0 as start address. If you change from an underlevel to a toplevel (cursor on the left), FDT will search the underlevel until it finds the chosen boss of the node. For e.g., from 2:2426/3000 to the host level it'll reel to the screen where the host 2:2426 is situated. More deviations: FDT always lists the complete address. Not only a node/point etc. will be shown, but also, if available, the responsible HUB/Host. It is also recorded with the node number whether the session was protected or not. In some cases the telephone number will be changed in FDNODE.CTL (or via FDNC). In that case, it writes down the complete entry into the FDNODE.FDA. The disadvantage of this is that not all FLAGS can be registered. Just a little warning: FDT sets an !FDA! in front of such flags. After selecting with ENTER FDT will ALWAYS ask you if you want to go on. (Force poll) If you have request files, you can state any file you want, just as with FD. Attention! FDT is generating mails! The advantage is that they don't disappear after a rescan, but that's also the disadvantage of it! FrontDoorTool V1.5 _ by Heiko Stoevesandt 30 ╒══════════════════════════════════════════════════════════════╕ │ -= Line-Controlling =- │ ╘══════════════════════════════════════════════════════════════╛ ALT-F(1-9) De-/Freeze LINE Num ALT-F10 De-/Freeze ALL CTRL-F(1-9) View LogFile to line (F9 oder F) can search a text or mark the place of the logfile. CTRL-L or F3 goes on with the search. CTRL-F10 Browsing FDT-LOGfile ALT-(1-9) Semaphoren - Controlling ! Flags shall/may only be used by an FD-experienced user. FDT marks these points specially. ALT-0 Set global semaphores or remove them. ╒══════════════════════════════════════════════════════════════╕ │ -= Interactive controlling at the InfoScreen =- │ ╘══════════════════════════════════════════════════════════════╛ At the InfoScreen modus you have to notice the following: The SETUP.FDT file in the Frontdoor system directory. Please read the details about parametric programming in the enclosed SETUP.FDT. The responsible event file for the task. But only eXternal events, as FDT normally doesn't need a routing. The File FDXITxxx.yyy And of course the Freeze-Flag. In particular: FREEZE for the FDT-LINE doesn't open any files no more. FDXIT*.* is not considered and events will be frozen. ALL keyboard functions are still carried out!! If another LINE as the FDT-Line is frozen, its files won't be touched any more. A typical entry is then: "LC not found or untouched" This message comes also when no lastcaller is there for this task. FrontDoorTool V1.5 _ by Heiko Stoevesandt 31 AT THE END ╒══════════════════════════════════════════════════════════════╕ │ -= Planned Features: =- │ ╘══════════════════════════════════════════════════════════════╛ FDT with FD 2.30 mL Address of the Autor Error - Bug- Proposal report to: Heiko Stoevesandt 2:2426/3000 (Fido) 37:1/300 (TrekNet) 85:220/100 (InfoNet) 144:4902/0 (GamesNet) or SnailMail to Heiko Stoevesandt Siedenburgskamp 4 28219 Bremen Germany ╒══════════════════════════════════════════════════════════════╕ │ -= FDT Beta tester: =- │ ╘══════════════════════════════════════════════════════════════╛ Robert Bergermann (2:2426/3002) Torsten Mausolf (2:2426/3130) Klaus Winckler (2:2426/6000) ╒══════════════════════════════════════════════════════════════╕ │ -= Translation =- │ ╘══════════════════════════════════════════════════════════════╛ English: Angela Klugius (2:2426/3035.12) Orig. Translation of 1.50 Klaus Winckler (2:2426/6000) Continuation FrontDoorTool V1.5 _ by Heiko Stoevesandt ╒══════════════════════════════════════════════════════════════╕ │ -= COPYRIGHT =- │ ╘══════════════════════════════════════════════════════════════╛ This program is subject to the German and International copyright as to the contractual right. . FDT is NO Public-Domain or Freeware, it is released as Shareware. Everybody who wants to use it until after 30 days of testing will have to register or to delete the program. Passing on the program to everyone is really wanted, as long as the content of the original archives is not changed in any way. The distribution of a modified program archives is prohibited. There may not come any expenses into the program being distributed to the purchaser. Professional shareware distributors who break on of the limitations stated above need the particular, written authorization of the author. Exclusion of liability and warranty: This program is given to you in particular without any liability and warranty. It fulfils a certain purpose, nothing more. There's no possibilty to let the author be responsible for any direct or indirect damage on your computer. The user carries the risk, especially for the safety of his datas. If local laws should break one of the rules stated above, the usage of the program is forbidden. . The following modules NOT written by the author are used and therefore are not copyrighted by me: EXC33 Public domain software by Thomas Wagner Ferrari electronic GmbH Beusselstrasse 27 D-1000 Berlin 21 Germany GETKEY by courtesy of KWS-Enterprises Copyright by Klaus Winckler ( Fido 2:2426/6000 )