home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
UTILITY
/
FVIEW736.ARJ
/
PENGUIN.CFG
< prev
Wrap
Text File
|
1989-08-09
|
14KB
|
368 lines
;
; Set PENGUIN= ???????
; July 26, 1989
;
;
; What is it?
;
; Set PENGUIN=somefile is a method to deal with the explosion of con-
; figuration files that programs need. I've got three programs going now
; that use configuration files, and I'm going to allow you to combine
; those configuration files into a single file. (I'd also like to invite
; the other Opus utility to join in this and use this strategy. If you'd
; like more information on how to set it up, please contact me via the
; methods listed at the end of this document.)
;
; FVIEW.EXE version 7.25+, Opus-Fam 0.56+ and MLUPD.COM dated 07/26/89
; will all search the environment for the string "PENGUIN". If they find
; that string, they'll use the file specified instead of their own
; configuration file. This means that you can combine MLUPD.CFG, OPUS-
; FAM.CFG and FVIEW.CFG into a single file, which should save you some
; disk space.
;
; Each program will go through the PENGUIN file looking for a line that
; begins "begin program_name", (FVIEW.EXE will look for "begin fview"
; for example), and read lines until it encounters a matching "end
; program_name". You can start and stop anywhere in the PENGUIN file,
; and they can be interlaced for information that could be shared by
; different programs.
;
; Here's a sample. Sorry I can't make it shorter.
;----------------------------------------------------------------------------
begin mlupd ; Since this information is shared with MLUPD and Opus-Fam
begin opus-fam ; Both programs can read it
;
scan 1 c:\files\bbstext disgrace ; Area #1 is "d:\files\bbstext"
scan 2 c:\files\text disgrace ; and requires "disgrace" privilege.
scan 3 c:\files\msdos disgrace
scan 4 c:\files\comm disgrace
scan 5 c:\files\general disgrace
scan 6 c:\files\language\ disgrace
scan 7 c:\opus1\ disgrace
scan 8 c:\node disgrace
;
end mlupd ; I don't want MLUPD to display these other areas.
;
scan 20 c:\files\uploads extra
scan 40 c:\files\sysop extra
scan 51 c:\files\email assist ;Only allow Assit here....
scan 73 c:\files\language extra
;
end opus-fam ; Done reading areas for Opus-Fam
;
;-------------------------------------------------------------------------
begin MLUPD ; This file can be plugged into or appended to another
; ; configuration file you have around. MLUPD will ignore
; ; anything up to this line. It will then read everything
; ; until you reach the 'MLUPD end' line at the end of this
; ; file.
;
; Ml-Update configuration file. This does NOT read SYSTEM*.BBS files!
;
; <-- MLUPD only accepts ';' for comments, any other character and it tries
; to process the line. Lines are terminated when a ';' is hit so comments
; after a keyword are OK, but a ';' in a board name or comment line will
; terminate the board name or comment line.
;
;
address 1:119/5.0 ; Your full address. (Zone/Point not necessary)
;
password mypass ; ML-UPD password, Don't change without warning the person
; ; who keeps track of your ML-COL!
;
phone (916) 893-9019 ; Your phone number
;
baud 9600 ; Maximum baud rate
;
name *LAZARUS* ;BBS Name
;
; Any two lines of comments/advertising/hours etc. go here, these will
; be inserted into the MegaList output files.
;
comment: Chico's oldest FidoNet board
comment: OpusInfo West
;
;
; If you are the person who runs ML-COL, comment out the next three
; keywords, PACKER, COLLECTOR, and OUTBOUND. MLUPD will try to attach the
; output file _only_ if it knows both who collects the MLA files, and where
; your outbound mail area is. If you leave out either piece of information
; MLUPD will just create the outbound file. MLUPD will tell Opus/Binkley to
; shrink the output file after it is sent if the "shrink" keyword is
; uncommented.
;
; packer arca /D ; Use arca WARNING! the /D doesn't always work, and
; ; arca does NOT produce an error code when it fails
; ; So MLUPD _might_ try to send a non-existent MLA file.
; ; The other programs produce an error code and MLUPD
; ; will send the MLU file if no MLA file was created.
; ; MLUPD will exit with the error code of the packer.
;
packer pkarc m ; What program and command line you use
; packer zoo aM ; Use ZOO
; packer pak m ; Use PAK
; packer arc a ; Use ARC
;
collector 119/4 ; Who collects the ML-UPD files.
;
outbound c:\outbound\ ; Where your outbound mail waits
;
shrink ; shrink the output file after sending (make it 0 length)
; delete ; delete after sending (only works with Binkley 2.00)
;
; hold ; send output file as a hold bundle
direct ; send output file as a direct bundle (default)
; crash ; send output as a hold bundle
;
; Which Areas to build the list from. You must have a files.bbs in each
; area. The area list MUST be at the end of this configuration file. MLUPD
; starts writing output file when you get here.
;
; The keyword is "scan", then the area number or code (letters acceptable)
; two characters are read. Then the full path to the download directory in
; question.
;
;scan 3 c:\files\msdos ; Since this information is used by
;scan 4 c:\FILES\COMM\ ; Opus-Fam, I'm reading it down there
;scan 6 c:\files\language ; Just have to edit those lines for changes
;
; Copyright 1988, Doug Boone, ChicoSoft
;
end MLUPD
;
;
; Exit error codes:
;
; 0 Everything went fine
; 1 Packer error code, no MLA created
; 2 Help was requested. (MLUPD ?)
; 3 Memory error (not enough free space)
; 4 Failed to open configuration file
; 5 Failed to open outbound attach file
;
;---------------------------------------------------------------------------
begin FVIEW
; This is a sample of what a FVIEW.CFG file should look like
; it is a special, TEMPORARY, file for Opus 1.03b Sysops if they
; need it. If you don't need it, great, if you do, here it is.
;
; Old_Opus ; Tells FVIEW that you are an Opus 1.03b
;
; task 0 ; If you're going to rely on this, insert task
; ; number here. (MUST match the one in OPUS.CTL
;
System c:\opus\ ; Path to my SYSTEM*.BBS files
;
dearc d:\temp\ ; Path to dearc files to temporarily while users
; ; are reading the text.
;
User C:\Fview ; Path to Lastuser.BBS
;
log fview ; Log of activity. DO NOT INCLUDE THE FILE EXTENSION!!!
;
online 30 ; Allow users 10 minutes use of FVIEW at a time
; ; instead of the default 5 minutes.
;
; noshow ; Uncomment this if you do NOT want users to read
; ; text files online. It will block out all the
; ; commands that would normally allow users to unarchive
; ; and read files.
;
debug ; More intense log of activity by FVIEW. Should
; ; help to find errors.
;
; watch ; Use FOSSIL watchdog while running remotely, reboots
; ; your computer on loss of carrier. Otherwise, FVIEW
; ; returns control to Opus.Exe
;
; noraw ; Don't allow users to do a R)aw listing of files
;
; nofiles ; Don't allow users to do a F)iles search
;
End FVIEW
;
;
; May the Shwartz be with you.
;---------------------------------------------------------------------------
; Configuration file for Opus-FAM beta ver 0.03
; search rules for the config file.
; 1. current directory
; 2. path in environment string "set opus-fam=d:\dir"
; 3. Optional command line switch -c d:\dir\opus-fam.cfg
;
begin opus-fam
; The very first thing we have to know here is which version of Opus
; you are running. Two version are currently supported:
;Opus 1.03
Opus 1.10
local ibm
; local bios
; local ansi
;
local color
; local mono
;
; Video Display
; ansi ; Default to ANSI standard
; bios ; Use BIOS calls, faster, machine dependent
; fossil ; Use FOSSIL, remote run through modem
;
; Next we need to know a little bit about your environment and options
; for file area management
;
priv_kill assist ; user with "assist" privilege can kill files
priv_area extra ; user with "extra" privilege can change areas
priv_adopt norm ; user with "assist" privilege can adopt orphan files
priv_rawdir priv ; "assist" user can do a Raw dir
priv_abandon assist ; "assist" user can abandon files
;
;backup ; user wants the files.bbs copied to files.bak
;
; trim ; Cut lines off at the right margin when users put in Loooonnnggg
; ; descriptions.
;
; Defaults are: kill on Assist privilege
; adopt on Assist privilege
; areas on Assist privilege
; rawdir on Assist privilege
; user_priv SYSOP
; color off
; backup on
;
; Accepted privilege levels are: Twit
; disgrace
; normal
; privil
; extra
; assist
; sysop
; hidden
;
;
;
; If you specify a log file name, then all errors encountered during
; file list processing will be entered in the log. This feature is
; highly recommended when Opus-FAM is invoked from a batch file during
; automatic processing.
;
;
;
log d:\files\error.log
; Define the headers for the list. Up to three headers may be defined.
; headers are automatically centered, and will only appear on the first
; page of the list file. Unless they are extremely long, they will work
; even for a sorted list, since the left margin where the file names
; normally appear will be spaces, and therefore sort first.
; The definitions stay intact (carry forward) for each file requested
; Colors can be configured for the folowing items:
menu-select yellow on blue ; the selection character on menus
menu-text cyan on black ; the selection text on menus
edit-line red on cyan ; the line being edited
status-bar white on green ; status line functions
; We are using the same color names and format as used by oecl, George
; Stanislav's great opus embedded command language compiler
;
; The following colors can be used for both foreground and background:
; black
; blue
; green
; cyan
; red
; magenta
; brown
; gray
;
; Now the colors that can be used for the foreground only.
; darkgray
; lightblue
; lightgreen
; lightcyan
; lightred
; lightmagenta
; yellow
; white
;
; There two more reserved words dealing with colors:
; on
; blink
;
; first we show the flexibility of generating different files lists, all
; from 1 invocation of Opus-FAM. In my nightly maintenance, I generate
; three file lists.
HDR1 *LAZARUS*
HDR2 OpusInfo Sherwood
HDR3 Master File List by Area
lpp 62 ; Lines per page (default is 62)
column 80 ; page width (max is 136, default is 80)
date ; print file dates
;nodate
;wrap ; wrap long lines
nowrap ; truncate long lines
;strip ; strip ANSI escape sequences
nostrip ; converts to printable characters
comments ; print file comments (has no affect if sort option selected)
;nocomments ; don't print any comments from the files.bbs
;priv ; list priv file areas
nopriv
level normal ; Any lines marked with the AVATAR sequence "below ... don't
; see rest of file" or "rest of line" will be skipped in the
; list file (same as Opus F)iles command).
; The above listed options carry forward for each report.
; AREA/XAREA need to be set for each report produced
; They are also mutually exclusive. Which means that you either
; specify the areas desired for the report, or you specify all areas
; EXEPT those listed for that report.
; The area numbers are decimal for Opus 1.03 and hex for Opus 1.10
;AREA 1 2 3 4 5 6 7 8
XAREA 0 20 40 51 81 80 82
file d:\files\Lazarus.lst ; produce first report
HDR3 Files Newer than 14 Days
;sorted
nosort
AREA 1 2 3 4 6 7 8
newfile d:\files\laz-new.bbs 10
;
; Set up the parameters for the second report, which is a sorted file
; list. Opus-FAM doesn't do the actual sort since there are many excellent
; file sorters available. Here's the command line from my bat file
; sortf sortin.lst c:\file\f01\sorted.lst /+3,13
;HDR3 Sorted Master File List
;sorted ; produce sorted file
;nosort ; produce file by area (default)
;XAREA 0 40 51 81 80 82
;file D:\files\sortin.lst ; produce second report
; execute a dos command - note that the entire line is passed to command.com
;exec sortf c:\temp\sortin.lst c:\file\f01\sorted.lst /+3,13
; The third report is my WOCCFILES. It contains just those file areas
; with BBS related files
; HDR3 File List of BBS software only
; area 7
; nosort
; file D:\files\wocfiles.lst ; produce third report
end opus-fam
; the end