home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
FDREQ116.ZIP
/
FDREQ.ARJ
/
FDREQ.DOC
< prev
next >
Wrap
Text File
|
1995-07-02
|
29KB
|
925 lines
_____________________________________________________________________________
_ _
_ _
_ F D R E Q v 1.16 _
_ _
_ _
_ Copyright 1993-1995 Manfred Schramm _
_ _
_ _
_ Manfred Schramm _
_ Esplanade 2 _
_ D-46483 Wesel _
_ Telefon : +49-281-340193 _
_ Mailbox : +49-281-340191 V32B, ZyX _
_ +49-281-340192 X75, V110 _
_ Fido : 2:2446/501 + 502 _
_ _
_ _
_____________________________________________________________________________
F D R E Q : free configurable Filerequest-processor for systems running
FrontDoor > 2.10, 2.11, 2.20mL, InterMail >=2.26, McMail
and any mailer, which supports SRIF
FDREQ - Manual
Contents
1. Introduction
1.1 - 7 How to use FDREQ
2. Trademarks
3. Installation
3.1 What else do you need
3.2 Setup FDREQ
3.2.1 Setup FD / IM
3.2.1 Setup McMail
3.3 FDRSETUP
FDRINDEX
3.31 Outputs
3.4 FDRAMIS
3.5 FDRUser
3.6 FDRStat
4. Credits
5. Appendix A - Registration
1. Introduction
FDREQ has been written, because the author was bored by filerequests
overriding mailer-events and sending silly answermessages. Later,
there have been added nice fatures.
In the meantime FDREQ became a full requestprocessor,
which enables the user to highly configure his system for
requests from most different adresses with different baudrates.
More than this, FDREQ offers Offline-requests for actually not
inserted CD-ROMs and Netmail-request.
A statistiktool works on all request-results on a weekly, monthly
and/or overall base.
The fast indexer and the fast binary search splitted into local
and mapped (CD-ROM-drives) drives allows fastest answertimes even
on huge filebases, several CD-ROM-drives and/or shared data-bases
in networks.
! There is an echo named FDREQ available at Manfred Schramm's.
! There is a fileecho named FDREQ available at Manfred Schramm's.
1.1 How to use FDREQ ?
FDREQ is copyrighted by Manfred Schramm and may only be used under
the following circumstances:
FDREQ may be tested for 3 weeks.
FDREQ may be used permanently after registration.
A registration costs. See registration-docs in this packet.
1.2. In no case, Manfred Schramm is dutied to accomplish further
versions or to support actual versions of FDREQ.
1.3. FDREQ may not be changed or recompiled.
1.4 FDREQ may only be distributed in the complete package
"FDREQ116.ARJ".
1.5 FDREQ may only be distributed free of duty.
Pay-Bulletin-Board-Systems may take their normal copy-fee, but no
special fee for FDREQ.
Shareware-vendors may take their normal copy-fee, but no special
fee for FDREQ.
1.6 FDREQ may not be distributed as part of a commercial product or
gift to a commercial product without M.Schramm's written permittance.
1.7 M.Schramm does not grant any suitable results for the use of FDREQ.
M.Schramm is not responsible in any way for defects, which result by
using FDREQ, neither directly nor indirectly resulting. What I do
grant is the take of memory FDREQ, will execute.
2 Trademarks
FidoNet Tom Jennings
IBM International Business Machines
OS/2 International Business Machines
MS-DOS Microsoft Corporation
NovellDOS Novell inc.
Netware Lite Novell inc.
Personal Netware Novell inc.
Lantastic Artisoft inc.
Lantastic/2 Artisoft inc.
DR-DOS Novell inc., Digital Research
DesqView Quarterdeck Systems
FrontDoor Joaquim Homrighausen
InterMail InterMail Sales Inc.
McMail Albert Freriks, Gordian Schuermann
Stomper Pflug Datentechnik
FDREQ Manfred Schramm
3 Installation
3.1 What else do you need
FDREQ should work with any IBM-compatible 80286-PC or higher with
MS-DOS 3.2 or younger. It works with monochrome- as well as with
colorsystems.
FDREQ needs at least 270 KB free RAM and 580 KB free HD-space.
Besides FDREQ of course you need a mailer eg. FrontDoor (2.10, 2.12 or
2.20), InterMail >= 2.26 or McMail.
FDREQ has been tested successfully in DOS-tasks of OS/2.
FDREQ has been tested successfully in peer-to-peer-networks.
(Netware lite, Lantastic, Personal Netware, (Invisible Net)).
FDREQ has been tested successfully with FrontDoor 2.12 & 2.20_mL.
FDREQ has been tested successfully with InterMail 2.26(Jan.) to 2.29b
FDREQ has been tested successfully with McMail >= 1.03g.
FDREQ has been tested successfully with several CD-ROM-Drives.
FDREQ has been tested in MultiLine-conditions simultanously under
the above multitakers and networks.
FDREQ has been tested successfully with STOMPER.
3.2 Setup
Set the variable for FrontDoor, InterMail or McMail,
if you run one of these frontends, eg.:
SET FD=C:\FD
or
SET IM=C:\IM
or
SET MCM=C:\MCM
Set the taskvariable, if you are running a multiline-system, eg.:
SET TASK=x
Decide where you want to run FDREQ (whether in the mailer directory or
in it's own), copy all files there (please extract the files in
FDRS_HLP.ARJ to a directory named HELP under FDREQs directory) and
change to FDREQs directory:
Copy 'TEMPATES.xxx' and 'MESSAGES.xxx' (xxx=your desired countrycode)
to '*.FDR'.
Set a variable FDREQ for FDREQ, than it will look for it's workfiles
in the pointed directory, it will write it's logmessages and
errormessages (hopefully never) there.
3.21 Setup FD / IM
Type in FDSETUP.EXE / IMSETUP.EXE and goto the "MAILER/FILE_REQUESTS"
section.
In the "Program"-field enter:
> FrontDoor
FDREQ.EXE A=A B=B H=H F=F O=O R=R T=T X=X W=W
invokes FDREQ like this:
fdreq.exe A2:2446/502.99 B14400 H76 FC:\FD\0107A7F4.FD$
OManfred_Schramm RC:\FD\FDREQTMP.01 TC:\FD\FDREQLST.01
XUNSECURE WLISTED
or
FDREQ.EXE A=A B=B H=H M=M O=O Q=Q E=E X=X W=W
invokes FDREQ like this:
fdreq.exe A2:2446/502.99 B14400 H76 M0107A7F4.FD$
OManfred_Schramm QFDREQTMP.01 EFDREQLST.01
XUNSECURE WLISTED
This second form always assumes the files *.FD$, FDREQTMP.* and
FDREQLST.* in FD's system-directory.
As you can see, this results in a shorter commandline, which may
help you, if you have long paths.
<
This means:
A2:2446/502.99 : remote's matching AKA
B14400 : remote's baudrate
FC:\FD\0107A7F4.FD$ : Session-Infofile
or M0107A7F4.FD$ : Session-Infofile
H76 : time left in minutes
OManfred_Schramm : remote's sysop's name
RC:\FD\FDREQTMP.01 : list of desired files
or QFDREQTMP.01 : list of desired files
TC:\FD\FDREQLST.01 : list of files to transmit (found files)
or EFDREQLST.01 : list of files to transmit (found files)
XUNSECURE : (un-)secured inbound
WLISTED : (un)-listed requester
> InterMail
FDREQ.EXE A%A B%B F%F M%M N%N X%X O%O
invokes FDREQ like this:
fdreq.exe A=2:2446/502.99 B=14400 F=C:\FD\IN\IMFILREQ.001 M122
N=Weseler_Info_Service XUNSECURE O=Manfdred_Schramm
<
(should be ONE line, I wrapped for documentation)
This means:
A2:2446/502.99 : remote's matching AKA
B14400 : remote's baudrate
FC:\FD\IN\IMFILREQ.001: Requestlist
M122 : time left in minutes
OManfred_Schramm : remote's sysop's name
NWIS : requester's system name
XUNSECURE : (un-)secured or listed inbound
3.2.2 Setup McMail
>
In MCMAILx.CFG (x=Task) there must be the following entries:
Sysop
System
SECUREINBOUND or at least INBOUND
SEMAPHOR
LOCATION
ComPort
You can let McMail call FDREQ in two ways, first the
conventionally way by:
FDREQ.EXE A=PA B=BR H=MR F=IF O=RS R=FL T=XL X=SU W=LS N=RN
invokes FDREQ like this:
fdreq.exe A2:2446/502.99 B14400 H76 FC:\MC\0107A7F4.FD$
OManfred_Schramm RC:\FD\FDREQTMP.01 TC:\FD\FDREQLST.01 XUNSECURE D
This means:
A2:2446/502.99 : remotes main-AKA
B14400 : session-baudrate
FC:\MC\0107A7F4.FD$ : session-infofile
H76 : remaining time in minutes
OManfred Schramm : remote sysops name
RC:\MC\FDREQTMP.01 : List of desired files
TC:\MC\FDREQLST.01 : list of files to transmit
XUNSECURE : (un-)secured inbound
WUNLISTED : unlisted requester
The second way to let McMail call FDREQ is:
FDREQ.EXE SRIF
FDREQ then will read SRIF.$xx (xx=tasknumber)
<
FDREQ can maintain a nonlimited number of directories listed in the
file, pointed to in (Un-)secured dirs, plus all password-, zone-,
sec_zone- ... directories.
FDREQ will read the system-files for password-handling.
FDREQ will NOT do service-requests, it will strip out these magics.
Your service-requests will be handled as ever.
3.3 FDRSetup
Copy or rename MESSAGES.xxx (xxx= your country-code) to MESSAGES.FDR
Copy or rename TEMPLATE.xxx (xxx= your country-code) to TEMPLATE.FDR
Unarchive FDRS_HLP.ARx (x depends on the desired language)
Check and fill in all points of the setup.
You may store inbetween or when finishing.
If you want to use the values of one task for another one, you simply
may copy them inside FDRSETUP.
If you want to use the values of another task, change inside FDRSETUP
to the desired existing task and copy the values to the new task.
There are some values, which are globally valid, they will work in
every task. If you change their value for one task, this will effect
all tasks.
(They are: unsecured-dirs, secured-Dirs, zone-check-dirs,
secured-zone-check-dirs, hitlist (y/n), hitlistfilename)
(+) means: registered version
=Others=
Environment
Shows your environmentvariables
Shell to system
DOS-Shell
Your name
here you enter your name
BBS-Name
here you enter the name of your mailer
Task
shows the active task and allows to change task
Copy
copies the values of the actual task to another desired one
Delete
deletes the values of the named task
=FILES=
Secured:
Name of the file including the directories
for secured inbound requests.
UnSecured:
Name of the file including the directories
for unsecured inbound requests.
Zone-CHECKDIR:
Name of the file, including the commands for
Zone-CHECKDIR.
You my name up to 50(+)/20 ZONE_Check_DIRs.
Only requests, containing the named
address-frame (AKA 0-9, FD), are serviced.
example for this file:
g:\fd\aktlist.2 2:2446/
g:\fd\aktlist.16 16:
g:\fd\aktlist.16 17:
g:\fd\aktlist.21 21:
Zone_SEC_CHECKDIR:
Name of the file, including the commands for
Zone-SEC-CHECKDIR.
You may name up to 50(+)/20 ZONE_SEC_Check_DIRs.
Only Requests, containing the named
address-frame (AKA 0-9, FD) in secured
sessions, are serviced.
example for this file:
d:\zyxadmin 16:
d:\zyxadmin 17:
g:\fd\aktlist.2 2:2446/
i:\james 2:2446/502.88
ALIAS:
Name of the file including the Magis for unsecured
inbounds requests.
In the ALIASfiles you enter line by line the
ALIASnames.
You name the ALIASName followed by up to
5 filenames, all with full paths.
All named files (up to 5) will be sent on
request of the magic.
The filenames may include '*' and/or '?'.
FDREQ then looks for the youngest file.
SECALIAS:
Name of the file including the Magis for secured
inbounds requests
DenyFREQS:
Name of the file, including the times, FDREQ shall service
requests with others than the normal values.
(if you want to do a smart request-servicing, please look onto
the possibility to setup deny-times and request-ratios for each
connectspeed).
example:
00:00-00:10 0
03:30-04:00 0
07:00-07:35 50
06:30-07:10 80
18:30-19:40 40
XX:XX-YY:YY ZZ
XX:XX -> start time
YY:YY -> end time
ZZ -> percentage of the main value in FDRSETUP/values
this means, if you allow an amount of 400kB in FDRSETUP/values,
a request at 18:45 will receive max. 160kB.
If you generally allow 20 files, this requester will receive
max. 8 files.
This is activ for all request-values.
You are able to install a smart, speedmatching request-value-system.
You may edit a denyfile for each baudrate possible
(300,1200,2400,4800,9600,12000,14400,16800,19200,21200,24000,28800,
31200,34000,57600,64000 and 38400(DTE)).
example: FREQS with 2400 baud:
2400.DF1
Name of the file, including the times, where FDREQ on task 1 shall
service a request with 2400 baud with special values.
example:
00:00-00:10 0
03:30-04:00 0
07:00-07:35 20
06:30-07:10 10
18:30-19:50 40
If there are any times, not included in a *.DFR-file, the
requester will receive the normal rates (as in FDRSETUP).
LogFile:
Name of the file, FDREQ shall logg into.
HelpFile:
Name of the helpfile
(the requester get's it, when requesting the macro "%HELP")
Footer:
Here you enter the name (full path) of the file,
including the footerinfo (your requesttimes, ALIAS-Names etc.).
=TEMPLATES=
Global for all templates:
If you mark a line with <F2>, this line will be suppresed by
FDREQ.
Header:
In the header you can include the Meta-commands @DSYSOP@ for
the requester's name, @DLOC@ for the requester's Systemname and
@DAKA@ for his (matching, if) AKA.
Footer:
In the footer you can include the Meta-commands @LSYSOP@ for
your name, @LSYS@ for your BBS-name and @LAKA@ for your
(matching, if) AKA.
Call:
Here you enter template for the call-statistics.
ex.:
@NUM@ File(s) with @KBYTES@kb in @TIME@ minutes this request
Day:
Here you enter the template for the day-statistics.
ex.:
@NUM@ File(s) with @KBYTES@kb in @TIME@ minutes today
All:
Here you enter the template for the overall-statistics.
ex.:
@NUM@ File(s) with @KBYTES@kb in @TIME@ minutes in all since @FIRSTTIME@.
Remain:
Here you enter the template for the remain-statistics.
ex.:
There are @KBYTES@kb, @CALLS@ call(s) and @FILES@ File(s)
in@MINUTES@ minutes left for today.
NotExistFile
Here you enter the text to be sent, if a file could not be found.
(This text only appears, if a file wasn't found neither on HD nor
in any CD-ROM-volume. If you do not enable offline-support, it
won't appear.)
FILES.BBS_template
Here you enter the text to be shown, if a FILES.BBS is sent.
TIC-FILE_template
Here you enter the text to be shown, if a TIC-file is sent.
Values / call:
Here you enter the template for the valid values/call for the
requester (depending on global values or special uservalues
or *.DF?-values)
=VALUES=
-LIMITS-
HEARTBEAT
Here you enter the time in seconds, after which your mailer shall
send a heartbeat. (11 sec. recommended)
COM-Port
Here you enter the COM-Port.
If your modem is on COM1, enter 0.
(0=COM1, 1=COM2, 2=COM3, 3=COM4 ...)
-max.values-
Min/CALL:
max. time each call
Min/Day:
max. time daily
kB/CALL:
max. size each call
kB/Day:
max. size daily
Files/CALL:
max. number of files each call
Files/Day:
max. number of files daily
Calls/Day:
max. number of calls daily
min. baudrate
Here you enter the minimum baudrate,
for which you accept requests.
(this min. baudrate will be read from your
mailersetup, but you maybe like different
values on different tasks.)
Max.Aka to match:
Here you enter the number of AKAs, FDREQs matching-table shall use.
=Switches=
Sysopmail (CarbonCopy)
Here you enter, whether FDREQ shall send you a carboncopy-message
of the message, it sent to the requester.
0 -> no carboncopy
1 -> carboncopy
FILES.BBS
You can switch on (1) or off (0) the sending of FILES.BBS.
(The requester can switch himself by requesting the
MACRO "%BBS" / "-%BBS")
TIC-FILES
You can switch on (1) or off (0) the sending of TIC-FILES.
(The requester can switch himself by requesting the
MACRO "%TIC" / "-%TIC)
CRC32-checksum
You can switch on (1) or off (0) the sending of TIC-FILES.
(The requester can switch himself by requesting the
MACRO "%CRC32" / "-%CRC32)
Mail on 1st Request
Here you enter, whether FDREQ shall send a Helpfile (1st_HLP.FDR)
to requesters, requesting the first time at your mailer.
Of course this helpfile must exist in FDREQs directory.
Loglevel
Here you enter, how fine FDREQ shall logg.
Level 0 -> only activity
Level 1 -> activity, requester, amount
Level 2 -> activity, requester, amount, files
Hitlist
Here you enter, whether FDREQ shall send the hitlist on request of
%HIT
temp. Copy
Here you tell FDREQ, whether to temp. copy files from CD-ROM
or not.
If yes, FDRSETUP asks for the destination directory and creates
it, if necessary.
CD-ROM-drives in the PC will be recognized by FDRSETUP.
Although you have to name each CD-ROM-drive, FDREQ shall support,
in the setup.
Before temp. copying, FDREQ checks the free space on the
destination directory. In case, there is not enough free
space, FDREQ sends the file directly from CD-ROM.
temp. copying makes sense on systems, where many Nodes share
CD-ROM-drives, otherwise there would be long periods of
waiting.
In systems with one or few nodes this copying makes few sense,
because the doing of the copying also needs some time.
show all descriptions
Here you tell FDREQ, whether to show the descriptions of all
requested files or to only show the descriptions of effectively
send files in case, the user exceeded his limits.
Offline requests
Here you enter whether FDREQ shall support Offline-requests or not.
(0 = no / 1 = Yes / 2 = Yes, search online)
If NO, FDRINDEX doesn't support CDIMPORT (look description FDRINDEX)
(Doing Offline-Request-Support, FDREQ scans the volume-files for the
filename and writes the request to the file used later Offline.
During the actual request FDREQ notifies the Offline-Support by :
a) case Offline-RQ = 0 not at all
b) case Offline-RQ = 1 by a simple notification
c) case Offline-RQ = 2 by a simple notification and if found offline
in a volume by notifying 'found'.
When working on offline-requests later, the requester will get a
netmail in case the file is found and placed on hold for xx days
and the file is copied to the temp. folder.
The FileAttach-MSG and the file in the temp.-folder will be deleted
after xx days.
paysystem
Here you tell FDREQ, whether it shall work as paysystem and if,
what is counted and how much free download you allow.
(registered only)
autoindex
Here you tell FDREQ, whether it shall invoke any of your mailertasks
to start a reindex with FDRINDEX. FDREQ writes a semaphore
'FDXITx.y' or 'IMEXITxx.y' (where x is the task and y the errorlevel),
when it notices differences between its index and the filebase.
The batch off the task, doing the index, must have a label to jump
to on the shown errorlevel. At this label FDRINDEX is called (see
TASK2.BAT).
=Exit=
Edit friends
Here care for friends/twits
Sort friends
Sorts friends/twits
Edit users
Here you care for the users
Sort users
Sorts users
Exit with Save
exit FDRSETUP and save the changes of active Task
Exit w/o Save
exit FDRSETUP without saving the changes of active Task
Store SETUP
save the changes of active Task
3.3 FDRINDEX.EXE
Before using FDREQ on your mailer(s), run FDRINDEX once.
Remember to run FDRINDEX at least once a day in your daily event to
freshen up FDREQ's index files.
The sort will take place on your Ramdisk, if available, or in your
TEMP-Dir as set by TEMP-variable.
Please take care, that your RAM-disk (if any) has enough free space.
commandlineparameters:
/MONO
FDRINDEX on monochrome-systems
/CDIMPORT
FDRINDEX imports the files of the CD-rom in all
CD-ROM-drives and creates volume-files, then FDRINDEX
runs normally.
/MORE
only in conjunction with /CDIMPORT
FDRINDEX imports all files of the CD-ROM(s) and
creates volume-files and asks, whether to import
more CD-ROMS.
/ROM=X:\PATH\
only in conjunction with /CDIMPORT
FDRINDEX imports all files down from X:\PATH\
/OFFLINE (only available, if Offline request is activated)
FDRINDEX will first run a complete index and then
FDRINDEX reads the desired requests not yet fullfilled
since the matching CD-ROM wasn't in the drive.
FDRINDEX checks, if the matching volume is in the CD-ROM-drive
and copies the desired file(s) to the temp. outbound, writes
an info-MSG to the requester, notifying the file(s) on HOLD
and writes a fileattachMSG to the requester.
The fileattachMSG normally gets the flags HOLD DIR.
You may name special requesters in friends/twits-base,
who will get sent the files CRASH DIR.
/OFFLINEONLY
(only available, if Offline request is activated)
FDRINDEX reads the desired requests not yet fullfilled
since the matching CD-ROM wasn't in the drive.
FDRINDEX checks, if the matching volume is in the CD-ROM-drive
and copies the desired file(s) to the temp. outbound, writes
an info-MSG to the requester, notifying the file(s) on HOLD
and writes a fileattachMSG to the requester.
The fileattachMSG normally gets the flags HOLD DIR.
You may name special requesters in friends/twits-base,
who will get sent the files CRASH DIR.
/DELREQ (only available, if Offline request is activated)
allows you to delete entries in the list of requests
not yet fullfilled.
All parameters may be combined.
FDRINDEX looks for requestmails in your netmaildirectory.
If it finds requests, it appends the requests to the list
of requests to be fullfilled offline.
Format of a REQUEST-Mail:
From: Firstname Name, address (z.B. 2:2446/509.20)
To: FDREQ, targetaddress
Re: REQUEST
Attr: PVT
-----------------------------------------------------------
FILENAME.SUF
ANOTHER.FIL
ANDATHIR.D
This means, the requester writes a mail to FDREQ with the subject
REQUEST. In the textbody he names the desired files line by line.
3.31 Outputs
FDREQ will work on filerequests and let's your mailer send the
following files:
XXXXXXXX.pkt containing all send files and found descriptions of
them. (XXXXXXXX will be build of the actual date and time)
FILES.BBx (x task-dependant)
(must be switched ON in SETUP.FDR or by the requester)
A file containing all filedescriptions found, so the requester can
simply add them to his files.bbs.
FDREQ works on your filebases FILES.BBS like this:
descriptions with one long line will be wrapped,
LDESCs with '>' will be taken 'as is' (leading blanks are stripped).
RQxxxxxx.TIC
(must be switched ON in SETUP.FDR or by the requester)
A file containing the information needed for automatical processing
of the requested file by fileprocessors (AREA=REQUEST)
FDREQ will write a logfile named FDREQ.REQ which contains all
requested files.
FDREQ will write an "ALLNODES.FDR", containing all requesters.
FDREQ will write a "YYYYMMDD.FDR", containing the today-requsters.
FDREQ will match requests with asterisks up to 10 times (evaluation)
and up to 20 times (registered).
FDREQ will write a file named FDREQ.ERR (or whatever you tell FDREQ to
name the LOGFILE) in case of errors, containing the corresponding
errortag and code.
3.4 Friends (in FDRSETUP)
You can create a file containing name, address, and
maximum-values of your special friends (and also TWITS).
FDREQ will, in case one of your friends requests, override the general
values of time, matches, calls, and size and follow the values of
MESAMIS.FDR.
Just try it, it's easy to understand.
Calls/Day -> calls per day
kB/Day -> kbytes per day
min/Day -> time per day in minutes
files/Day -> filematches per day
kB/call -> kbytes per call
min/call -> time per call in minutes
files/call -> filematches per call
Place the resulting file named MESAMIS.FDR into FDREQ's directory.
3.5 Users (in FDRSETUP)
This is a simple viewer for all requesters, who ever requested at
your mailer.
3.6 FDRSTAT
This is a first statistic-tool
FDRSTAT will write ansi- and ascii-files for the use in your BBS.
It may write you a msg.
It may update your download-counters
To have FDRSTAT count the overall best requesters, call
FDRSTAT TU
To have FDRSTAT count the best requesters yesterday, call
FDRSTAT YD
To have FDRSTAT count the best requested files yesterday, call
FDRSTAT YF
To have FDRSTAT write a mail on each topic, call
FDRSTAT TU SM
FDRSTAT YD SM
FDRSTAT YF SM
To have FDRSTAT update your download-counters, call
FDRSTAT DL
To have FDRSTAT purge your users based on their last request, call
FDRSTAT KILLxxx
(where xxx is the number of days, after which the user did not
request)(only in combination with TU)
To have FDRSTAT count the overall statistics on a monthly base, call
FDRSTAT TU MONTHLY
You may combine all of the parameters in one call, eg:
FDRSTAT YD YF TU SM DL MONTHLY KILL100
4. special credits to:
Joerg Arlandt, Ralf Moeller, Wolfgang Schantz, Joerg Kaiser,
Daniel Zeilmann, John Tetreault, Tomasz Kepinski and
Bernfried Grosse-Venhaus
Tchibo, departement Wesel, Hohe Strasse (former in Bismarkstrasse),
for coffee brand 'Bonjour'.
U2, Berlin & Dublin, Tangerine Dream, Berlin
and Nigel Kennedy, Middlesex for their aid by good sound.
Marienhospital Wesel for its hostability.
5. Appendix A - Registration
If you're a non-commercial user send 30.- DM or $US 20 with a letter
including your full legal address and/or your Fido-,ZyXEL-, GerNet- or
OtherNet-Address (in case of othernet please note your mailers
phonenumber).
If you are a commercial user send me 60.- DM or $US 40 with a letter
including your full legal address and/or your Fido-,ZyXEL-, GerNet or
OtherNet-Address (in case of othernet please note your mailers
phonenumber).
For more info, see REGISTER.FRM (you can print it from inside FDRSETUP)