; File: FDUSER.CFG ----- Master control file for FDUSER.
;
; FDUSER is Copyright(c) 1991 by: Gordon E. Rasnick
; Arctic Computer Services
; 2530 Sebring Circle
; Anchorage, AK 99516
; FIDONET (1:17/59)
; AKA (1:355/59) (1:355/500)
; CompuServe ID: 72007,417
;
;
; PLEASE, read this CAREFULLY. One mistake setting this up and the
; whole thing will probably crash. I suspect that most of the
; requests for support that I will receive will be a result of not
; having this file set up properly. If you netmail me with a problem,
; be sure to include a copy of your CFG file, and an excerpt of the
; FrontDoor log file showing the problem, in the request.
;
; *****************************
;
; This is the master control file for FrontDoor User. It also serves
; as much of the documentation for the program. (Don't let that
; keep you from reading the DOC file though.) You may insert or
; delete comments in it as you wish, but, each comment line must
; begin with a semi-colon! Removing the comments may speed it up a
; bit, but I doubt you'd notice the difference. It's fast!!!
;
; DO NOT delete any of the control statements in this file. Control
; statements are any line not beginning with a semi-colon. They
; tell FDUSER what you wish to include in your reports. If you
; wish to remove a feature from the generated reports, change that
; statements toggle to a 'N' instead of a 'Y' in this file. Obviously,
; 'Y' means you wish to have the feature ENABLED or 'Turned ON' in your
; reports. 'N' will DISABLE or 'Turn OFF' a particular feature.
;
; ALSO! Leave in all the equal signs (=) for each of the statements.
;
; ******************************
;
; The 'KEY' statement is required as is! Do not modify this line in
; any way until you have registered your copy and received your
; registration KEY code. See REGISTER.DOC included. It must also
; be the first non-comment line in the control file, as it is here.
;
KEY=000000000
;
; FD LOGPATH tells FDUSER where to find your FrontDoor log file, and
; the name of the file itself. You provided this to FrontDoor during
; installation with FDSETUP. Include your own path and filename.
;
FD LOGPATH=C:\FD\LOG.FD
;
; ADDRESS is your complete netmail address. You should include the
; zone also.
;
ADDRESS=1:355/500
;
;
; I didn't see a need for your AKA's anywhere. Enlighten me if you
; think they are really necessary. They don't show up in the
; log file anywhere.
;
;
; ANSI is for creation of ansi color style output files. You may
; wish to make FDUSERS reports displayable on your system. Setting
; ANSI to Y will generate a colorful report.
;
; ASCII is for plain text style output files.
;
; You can produce both if desired. ANSI files have a file extension
; of .ANS, while the ASCII text file will be .ASC.
;
ANSI=Y
ASCII=Y
;
; MAIL FILE tells FDUSER the path and name of the file you wish
; to use for the report of incoming and outgoing mail and files.
; Its file extension will be added based on your settings for ANSI
; and ASCII.
;
; It produces a report of all mail traffic to and from your system
; and is called via the -R switch. (FDUSER -R)
;
; If you do not want a mail report generated, leave the path and
; filename blank. (Can't see why you would want to do that though.)
;
MAIL FILE=MAILRPT
;
; *****************************
;
; The following should be the same as the settings you have saved
; under FDSETUP in the Mailer/Log options. Check your FD setup
; and toggle the ones here (Y or N) to match those in FD.
;
; NOTE: FATAL ERRORS is something I have not been able, or care to
; reproduce. (Knock on wood.) Anyone having an example of one or more
; of these types of errors, could you please send it to me netmail. As
; it is, FDUSER will duplicate the exact line produced by FD and place it
; in the FDUSER.ERR file on your disk, if toggled to Y here.
;
FATAL ERRORS=Y
OTHER ERRORS=Y
ACCOUNTING INFO=Y ; <-- This must be toggled to YES. Here, and in FD.!
;
; Sent/Rcvd files is omitted here since the primary purpose of this
; program is to report on this type of activity. Sent/Rcvd Files should
; be toggled YES in your FDSETUP.
;
BRIEF MESSAGES=Y ; <-- This must be toggled to YES. Here, and in FD.!
TRANSFER MESSAGES=Y
UNEXPECTED PASSWORDS=Y
MODEM RESPONSES=Y ; <-- This must be toggled to YES. Here, and in FD.!
;
; All the other options available in the FD log file are a bit trivial
; for system reporting and have been omitted here. Let me know if you
; would like to see any of the others included.
;
;
; Here is an example of FD's Setup Screen for the Log File.
;
; NOTE: Be sure to toggle YES for "= Modem Responses", "$ Accounting
; info", and also "+ Brief Messages."! FDUSER uses these messages to
; pick out your calls.
;
; NOTE: If you have not been using these flags in FrontDoor, do not try to
; process your current FD log file. It will probably produce garbage, or
; worse yet, hang up your computer. Delete or rename your log file and
; start a new one with the required toggles set in FDSETUP.
;
; File Global Mailer Editor Terminal Modem Printer
; ════════════╒══════════════════╕════════════════════════════════════
; ▒▒▒▒▒▒▒▒▒▒▒▒│╒════════════════════════════ Log ╕▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒││ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒││ ! Fatal errors Yes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒││ ? Other errors Yes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒││ $ Accounting info Yes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒││ * Sent/Rcvd files Yes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒││ + Brief messages Yes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒││ - Trivial messages No │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒││ : Transaction info No │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒ F││ % Transfer messages No │version ▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒││ # Unexpected passwords Yes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; Copyright 19││ ~ Session information No │ll rights reserved
; ▒▒▒▒▒▒▒▒▒▒▒▒││ ~ ├─Remote system's AKAs No │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒╘│ ~ └─Remote system's info No │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒▒│ = Modem responses Yes │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒▒│ DEBUG: All of the above No │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
; ▒▒▒▒▒▒▒▒▒▒▒▒▒╘═════════════════════════════════╛▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
;
; If you have toggled ON any of the control statements and do not have
; a matching toggle in FDSETUP, FDUSER will not complain but your reports
; will look a bit odd with all these statments turned on and nothing
; printed out on the report for the option except the heading itself.
;
;
; The ENDCFG statement must be included and nothing should be
; written below it.
;
ENDCFG