home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
SUTIL044.ZIP
/
SUTIL.H02
< prev
next >
Wrap
Text File
|
1993-03-02
|
36KB
|
1,135 lines
*default*
Oops! No help is available for this topic. Please check the manual if
you are unsure of something. You can always call for help on the Fidonet
SUPERBBS International echo.
*end*
─────────────────────────────────────────────────────────────────────────
*main menu*
Welcome to SUtil, the most complete set of utilities available for Super
BBS. Help is available at nearly any point in this program by pressing
F1. To navigate the help text, use your cursor up/down keys, your page
up/down keys and your home/end keys. Press Escape to exit back to the
menu.
The menus are roughly laid out by the various major areas of your bbs.
You will find all the functions related to the user base are under the
User Base menu, files base functions are under the Files Base menu etc.
To select an option use your up & down cursor keys to move the highlight
to the correct option, then press Enter to select it. You may then be
presented with a further menu or prompted for parameters if required or
the selection will be executed.
To return to a previous menu you can either select Quit, which is always
the last option on a menu, or press Escape.
Sometimes there may be too many menu options to display all at once. In
this case you can scroll the options by pressing the down cursor until you
see the option you want. If you don't see the Quit option then you know
there are more options to be found.
You can quickly exit the program from any menu using Alt-Q and shell to
DOS using Alt-Z.
*end*
─────────────────────────────────────────────────────────────────────────
*user base menu*
AVAILABLE FUNCTIONS
───────────────────
KILL USERS Mark old users as 'deleted'
PACK USER BASE Pack user base, removing 'deleted' users
SORT USER BASE Sort user base according to selected criteria
ANSWER FILE PACK Remove old users from answer files
ASW -> SYSOP COMMENT Update SysOp comments from ASW file
GLOBAL ATTR RESET Global attribute reset by security level
GLOBAL ATTR SET Global attribute set by security level
GLOBAL FLAG RESET Global flag reset by security level
GLOBAL FLAG SET Global flag set by security level
GLOBAL HIGH MSG RESET Reset 'highest message read' to specified number
UPGRADE SECURITY Upgrade security based on selected criteria
USER LIST User list with selected data
FIND USERS Find users with security and/or flag
SEARCH USERS Search users for selected string
ALIAS ONLY LIST Create ANS/ASC user list with aliases only
LIMITS REPORT Create comparative user limits report
LOST CARRIER REPORT Report lost carrier counters
LOST CARRIER RESET Reset lost carrier counters
KILL OLD MSG COMMENTS Delete old msg comment files
RECOVER USER BASE Recover corrupted user base files
*end*
*kill users*
Parameters
──────────
Low Security: 0 - 32767
High Security: 0 - 32767
Days: 0 - 999
Marks as deleted any users within the security range specified *inclusive*
that have not called in <days> number of days. This allows a range of
securities or a single security level to be deleted. For example if you
want to kill all users from level 20 to level 40 who are older than 120
days then type:
KILL 20 40 120
If you want to kill all users at security level 10 who are older than 60
days then type
KILL 10 10 60
Further, you can delete all users within a range or single security level
immediately. For example to delete all users from level 0 to level 4,
type:
KILL 0 4 0
Or only level 0 immediately:
KILL 0 0 0
This allows flexibility for keeping different level users for differing
lengths of time. For instance, your new users at level 5 who never do
much and probably won't call back can be deleted quickly whilst you can
allow those who have been upgraded time to get back from their vacation.
*end*
*sort user base*
Parameters
──────────
Mode: F = First Name
L = Last Name
A = Ascending Security
D = Descending Security
G = Ascending Age
E = Descending Age
T = Ascending Calls
I = Descending Calls
M = Ascending Msgs Posted
S = Descending Msgs Posted
Sorts the user base according to the mode on the command line. The mode
can be stacked. For example SORT LD will sort by last name and then by
descending security. Think in reverse when stacking the sort mode. For
example if the first priority is security, it should be the last entry in
the sort mode. Before Sutil starts the sort it will attempt to clean up
the users entries. It will remove any commas and compress any multiple
spaces.
*end*
*answer file pack*
Parameters
──────────
Answer File: Any questionnaire answer file found in the SBBS system
directory, no extension.
This will remove any entries from your questionnaire answer files from
users who no longer exist in the user base.
*end*
*asw -> sysop comment*
Parameters
──────────
Keyword: Keyword to search for in answer file.
Answer File: Answer file to read, no extension (default=NEWUSER).
Scans the given questionnaire answer file looking for the given keyword.
Any text on the same line immediately following the keyword will be
written into the SysOp Comment field in the user base for that user. The
most recent entry in the answer file will always be used.
*end*
*global attr reset*
Parameters
──────────
Security: 0 - 32767 or ALL
Attribute: 0 - 17
Switches off the user attribute you specify for every user at the
specified security. If security is ALL then the attribute is switched off
for all security levels.
Valid User Attributes:
0. Deleted 9. Log On New Files Check
1. Screen Clear Codes 10. No D/l Ratio
2. Page Pause 11. Female
3. Graphics 12. Delete File After Viewing
4. No Kill 13. Display File Once
5. Ignore D/l Hours 14. File Viewed
6. ANSI Editor 15. Full Screen Viewer
7. Do Not Disturb 16. Combined Mail Check
8. Log On Mail Check 17. No Hotkeys
*end*
*global attr set*
Parameters
──────────
Security: 0 - 32767 or ALL
Attribute: 0 - 17
Switches on the user attribute you specify for every user at the specified
security. If security is ALL then the attribute is switched on for all
security levels.
Valid User Attributes:
0. Deleted 9. Log On New Files Check
1. Screen Clear Codes 10. No D/l Ratio
2. Page Pause 11. Female
3. Graphics 12. Delete File After Viewing
4. No Kill 13. Display File Once
5. Ignore D/l Hours 14. File Viewed
6. ANSI Editor 15. Full Screen Viewer
7. Do Not Disturb 16. Combined Mail Check
8. Log On Mail Check 17. No Hotkeys
*end*
*global flag reset*
Parameters
──────────
Security: 0 - 32767 or ALL
Flag: A1 - D8
Switches off the user flag you specify for every user at the specified
security level. If the security is ALL then the flag will be reset for
all security levels.
*end*
*global flag set*
Parameters
──────────
Security: 0 - 32767 or ALL
Flag: A1 - D8
Switches on the user flag you specify for every user at the specified
security level. If the security is ALL then the flag will be set for all
security levels.
*end*
*global high msg reset*
Parameters
──────────
Message Number: 0 - 32767
Resets 'highest message read' counter for all users to the number
specified on the command line.
*end*
Resets all users colors to the default specified in the SBBS config.
*upgrade security*
Parameters
──────────
Control File: Any file found in the SUtil home directory.
Scans the user base and upgrades any users that meet the criteria as
listed in the specified control file. The control file is a text file
with one spec per line as follows:
<current security> <new security> <msgs> <upk> <calls>
Each line contains old and new security specs and the criteria that must
be matched in order to be upgraded to the new security, each number is
seperated by a space. Any missing numbers will cause SUtil to barf in a
big way.
Each user must be at the 'current security' and have at least the number
of messages, uploads in KB's and calls specified in order to be upgraded
to the 'new security'. If you are not concerned what the current security
is, so long as they meet the other qualifications, then put '-1' as the
current security. If you are not concerned about any of the
qualifications (msgs,upk,calls) then put '0' for that parameter. Any line
beginning with a semi-colon (;) is treated as a remark and is ignored.
For example:
;sample upgrade security control file
5 10 20 100 20
10 20 0 0 20
-1 30 100 400 50
For the first line, any users currently at level 5 will be upgraded to
level 10 if they have entered 20 or more messages AND uploaded 100KB or
more AND called 20 or more times. For the second line, any users
currently at level 10 will be upgraded to level 20 if they have called 20
or more times (because the other parameters are 0 they are effectively not
used). For the third line, any users, regardless of their current level,
will be upgraded to level 30 if they have written 100 or more messages AND
uploaded 400 KB or more AND have called 50 or more times.
*end*
*user list*
Parameters
──────────
Options: CITY|SECURITY|ALIAS|DOB|AGE|HOMEPHONE|DATAPHONE
FIRSTCALL|UPS|UPK|DOWNS|DOWNK|RATIOK|MSGS|CALLS
MINUTES|COMMENT
FORM (output format - defaults to list format)
Makes a list of all users including the information specified on the
command line. Any combination of options is allowed. For example:
USERLIST ALIAS SECURITY
will produce a list of users' names and their aliases and security. If you
include FORM on the command line the output will be formatted one field
per line, otherwise it is in list format.
*end*
*find users*
Parameters
──────────
Security: 0 - 32767 or none
Attribute: 0 - 15 or none
Options: NOT or none
Will list any users it finds that matches the criteria on the command
line. You can use either security or flags or both. If you use only one
criteria, it will list all users that match it. If you use both criteria,
it will list all users that match both. The /S and /F switches are not
required when running in the environment. Options for other keywords
include NOT, which will report all users not matching the given criteria.
At the DOS prompt:
FINDUSERS /S20
Finds all users with security level 20.
FINDUSERS NOT /S20
Finds all users not at security level 20.
FINDUSERS /Fa1
Finds all users with flag A1 set.
FINDUSERS /S20 /Fa1
Finds all users with security level 20 AND flag A1 set.
*end*
*search users*
Parameters
──────────
Search String: Any string to look for.
Searches user records and reports any occurrances of the specified string.
This is useful for finding users in the same town or area code or users
that have suspiciously similar passwords or maybe a number of users have
the same phone number.
*end*
*lost carrier report*
Parameters
──────────
Entries: Number of entries to include
Displays a sorted list of users who have dropped carrier. 'Entries' is
the maximum number of entries to include. If omitted, all users who have
dropped carrier are included.
*end*
*lost carrier reset*
Parameters
──────────
User Name: User's name to reset or ALL
Resets the lost carrier counter for the specified user. If the user name
is ALL then all users are reset.
*end*
─────────────────────────────────────────────────────────────────────────
*files menu*
AVAILABLE FUNCTIONS
───────────────────
VIEW FILES LISTS View a selected FILES.BBS file
SBBS DOWNLOAD COUNTER Update download counters from SBBS log
BIMODEM DOWNLOAD COUNTER Update download counters from Bimodem log
FRONT DOOR D/LOAD COUNTER Update download counters from Front Door log
DBRIDGE DOWNLOAD COUNTER Update download counters from DBridge log
POP DOWNLOAD COUNTER Update download counters from Portal log
MAKE MASTER FILES LISTS Create master files list and newfiles list
SORT FILES Sort selected FILES.BBS
ADD UNLISTED FILES Add unlisted files to FILES.BBS
PACK FILES LISTS Pack selected FILES.BBS
HURL FILES Hurl selected files to a new area
LOCAL FILE ATTACH Create a local file attach
ANNOUNCE NEW FILES Create new files announcement in message base
CREATE FREQ DIR LIST Create text file list of freq directories
SEARCH FILES LISTS Search files lists for given string
SORT FLSEARCH Sort files config
FILES BASE INFORMATION Files base information
*end*
*Super BBS download counter*
Parameters
──────────
Log File: Full path and file name of log file.
Updates the download counters in your FILES.BBS files according to entries
in the Super BBS log file. Specify the complete path, file name and
extension of the log on the command line. This function may barf the
first time you use it on a log file greater than around 1 MB. You will
need to trim the log until scount works. After that the size is not
important.
*end*
*bimodem download counter*
Parameters
──────────
Log File: Full path and file name of log file.
Updates the download counters in your FILES.BBS files according to entries
in the BiModem log file. Specify the complete path, file name and
extension of the BiModem log on the command line. This function may barf
the first time you use it on a log file greater than around 1 MB. You
will need to trim the log until bimcount works. After that the size is not
important.
*end*
*front door download counter*
Parameters
──────────
Log File: Full path and file name of log file.
Updates the download counters in your FILES.BBS files according to entries
in the Front Door log file. Specify the complete path, file name and
extension of the FD log on the command line. This function may barf the
first time you use it on a log file greater than around 1 MB. You will
need to trim the log until fdcount works. After that the size is not
important.
*end*
*dbridge download counter*
Parameters
──────────
Log File: Full path and file name of log file.
Updates the download counters in your FILES.BBS files according to entries
in the DBridge log file. Specify the complete path, file name and
extension of the DB log on the command line. This function may barf the
first time you use it on a log file greater than around 1 MB. You will
need to trim the log until dbcount works. After that the size is not
important.
*end*
*portal download counter*
Parameters
──────────
Log File: Full path and file name of log file.
Updates the download counters in your FILES.BBS files according to entries
in the Portal Of Power log file. Specify the complete path, file name and
extension of the log on the command line. This function may barf the
first time you use it on a log file greater than around 1 MB. You will
need to trim the log until popcount works. After that the size is not
important.
*end*
*master files lists*
Parameters
──────────
List File Name: Name of list file to create.
New List File Name: Name of new files list to create.
Security: Highest security to include.
Days: Days to include in new files list.
Creates a files list of all the files areas listed in the FLSEARCH.BBS
file including only those areas with security equal to or less than that
specified. Will include at the top of the list the contents of a file
BANNER.TXT if found. SUtil reads the default.lng file or any language
file found in the system directory to get the string for files not found.
Also creates the new files list as set on the command line. This list
includes files in the security allowed areas that are equal to or younger
than that specified.
*end*
*hurl file*
Parameters
──────────
Source: Directory and file names of files to hurl.
Destination: Destination directory for files.
Hurls one or more files and descriptions anywhere within your defined
files base. No need to type in the whole path, just the file's own
directory and file name and the destination directory. For example if a
user has just uploaded HOST44.ZIP and you want to put it in the TELIX
directory, type the following:
Source: UPLOADS\HOST44.ZIP
Destination: TELIX
This might translate to:
From: C:\SUPERBBS\FILES\UPLOADS\HOST44.ZIP
To: C:\SUPERBBS\FILES\TELIX\HOST44.ZIP
or whatever is configured in your flsearch.bbs file. If a file can't be
found then just the description will be hurled. If neither a file or it's
description can be found then no action will be taken.
You can specify multiple source files to hurl. For example, a user has
just uploaded the Telix package in three files which you want to hurl to
the Telix area.
Source: UPLOADS\TLX315-1.ZIP TLX315-2.ZIP TLX315-3.ZIP
Destination: TELIX
This will hurl all three files from the Uploads area to the Telix area.
Or alternatively, you can use wildcards such as the following:
Source: UPLOADS\TLX315*.*
Destination: TELIX
or even:
Source: UPLOADS\TLX315-?.ZIP
Destination: TELIX
*end*
*local file attach*
Parameters
──────────
User: User to receive file.
File: File to attach.
Description: Optional description to appear in files.bbs.
This function allows you to do a local file attach to a user at the dos
prompt or maybe do daily file attaches to co-sysops from the daily
maintenance. Gets the file attach directory from the SCONFIG.BBS file and
checks that the user exists in the user base. The description is optional.
If running from the command line you must use underscores in place of
spaces when typing the user name and description, if running from the
environment it is not necessary.
*end*
*announce new files*
Parameters
──────────
Message Board: Board number of Hudson message to post announcement.
Exclude File: Optional exclude file found, in SUtil home directory,
listing files/paths to exclude.
Creates a message describing new files on the system. Initially, this
function will create a zero length file called "announce" in the 'home'
directory of SUtil. This is used to remember the last date that this
function was run, so that the next time it is run it will compare file
dates against this date to decide which is new. Each successive time it
is run it will update the date on this file. This way you can run it
daily, weekly or whenever you like and it will catch all the new files
since the last time it was run. To alter the last date simply alter the
date on this file or delete it altogether to start again from today.
The optional exclude file is a text file listing paths and/or files you
wish to exclude from the new files announcement. The paths must have a
trailing backslash. Comments must start with a semi-colon (;). For
example:
;exclude file for announce function
c:\superbbs\files\uploads\
c:\superbbs\files\private\
c:\superbbs\files\rough\rough.zip
*end*
*create d/l dir list file*
Parameters
──────────
File Name: Full path and file name of text file to create.
Security: Security to include in file.
Creates a text file containing full paths to your files area including
areas of specified security or lower. This file is used, for example, by
Front Door to search for file requested files. For example:
SUTIL FRDIRS C:\FD\DIRS.FRQ 5
*end*
*search files*
Parameters
──────────
Search String: Any combination of characters to look for.
Searches all files.bbs files for the given search string and reports any
areas it was found in. Case not sensitive.
*end*
*sort flsearch*
Parameters
──────────
Mode: N = Area Name
A = Ascending security
D = Descending security
Sorts the files area config file according to the mode specified. The mode
can be stacked. For example SORTFLSEARCH NA will sort by area name and
then by ascending security. Think in reverse when stacking the sort mode.
For example if the first priority is security, it should be the last entry
in the sort mode.
*end*
─────────────────────────────────────────────────────────────────────────
*message base menu*
AVAILABLE FUNCTIONS
───────────────────
POST FILE TO MESSAGE Post text file to message base
TWIT FILTER Delete any message with selected subject/author
CLEAN MESSAGE HEADERS Remove 're:' from message headers
MESSAGE BASE REPORT Message base report
*end*
*post file to message base*
Parameters
──────────
Board Number: Hudson message base board number.
File Name: Name of text file to post.
To: Person to receive message.
From: Who is message from.
Subject: Message subject.
Works similar to many mail tossing programs. Allows you to post a text
file as a message to the hudson message base. If running from the command
line, each parameter must have underscores in place of spaces. If running
from the environment this is not necessary. If you include the /D
parameter after the subject parameter the file will be deleted after
posting.
*end*
*twit filter*
Parameters
──────────
Options: /F<name> = delete messages from a person
/S<subject> = delete message with a subject
Marks as deleted any messages written by a particular person or any
messages with the given text included in the subject. Use only one of
either the person, subject or specification file on the command line. For
example:
TWIT /FGlenn Delahoy
Will delete any messages from Glenn Delahoy.
TWIT /Stest
Will delete any messages that have 'test' included in the subject line.
TWIT @sutil.twt
Will read the text file 'sutil.twt' to get the specifications. The spec
file has one spec per line, each starting with either /F or /S for the
From field or the Subject field. It is not case sensitive and does not
need underscores.
*end*
─────────────────────────────────────────────────────────────────────────
*system files menu*
AVAILABLE FUNCTIONS
───────────────────
PLAY YELL FILE Play a yell control file
PAMS2BBS Create bbs list from Pams list
NODE2BBS Create bbs list from nodelist
TRIM SYSTEM LOG Trim system log file
POST NODE NEWS Extract news from nodelist and post to msg base
UPDATE FD INBOUND Add SBBS last caller to FD inbound
UPDATE SBBS INBOUND Add FD last caller to SBBS inbound
HIDE LOCAL CALLS Convert local calls to new baud
VIEW BBS LIST View any BBSLIST file
*end*
*play yell file*
Parameters
──────────
Yell File: Full path and name of yell file.
Plays the yell control file approximately how it would be heard from the
bbs. The speed seems to be machine dependant, otherwise it's pretty
accurate.
*end*
*pams to bbs list*
Parameters
──────────
File: Full path and name of Pams 'all' file.
State: Which state to include.
Creates a BBSLIST.BBS file from the Australian BBS directory 'all' file
that can be used with the SBBS bbs list functions. As of the last release
of the Aust BBS directory, the file required for this function is called
BBSAALL.DAT. As this may change in the future I have made this file a
command line option. The second option is the state you want listed.
{state = VIC, NSW, QLD, ACT, NT, SA, TAS, WA}
*end*
*nodelist to bbs list*
Parameters
──────────
Zone:Net: Which zone and net to include.
Creates a BBSLIST.BBS file from a fido compatible nodelist. It searches
the SBBS config file to find the nodelist directory, then looks for the
first nodelist in that directory. Note that this is not necessarily the
latest one. You must specify zone and net numbers. For example, 3:635,
is zone 3, net 635. To specify all nets in a zone type, 3:0. If the zone
isn't found you get a nice zero length bbslist file.
*end*
*trim system log file*
Parameters
──────────
File: Full path and name of system log file.
Days: Number of days to keep.
Scans specified system log file and removes entries older than specified
number of days. Before it starts it makes a copy of the log file to *.BAK
so in case it dies half way you can recover the log. If a *.BAK file
already exists it is deleted.
*end*
*post node news*
Parameters
──────────
Msg Board: Hudson message base board to post to.
Extracts any news bulletins in the current nodelist and writes it to a
message area specified on the command line. Put this after your nodediff
update.
*end*
*sbbs last call to fd*
Parameters
──────────
Front Door Directory: Full path to FD directory
Examines the SCALLER.BBS file to get the last caller online. Inserts this
info into the Front Door INBOUND.HIS and LASTCALL.FD files. You can then
use the FD inbound history to see what bbs callers you've had and the last
caller shows up on the FD main screen. Note that SBBS doesn't put the
SysOp into the SCALLER.BBS file. The last caller will be the last caller
that isn't the SysOp. In the FD inbound history the received bytes will
be the caller's total uploads, the sent bytes will be the caller's
downloads for today and the cost will be the caller's age.
If you run FD 2.02 then you do not need the dir parameter. If you are
running the commercial version (2.10) then the dir parameter should point
to the Front Door system directory where all inbound and lastcall files
are stored. If this parameter is used SUtil will look for the TASK
environment variable used by FD to construct the file names INBx.HIS and
LASTCx.FD where 'x' is the TASK number.
In summary:
If you have FD 2.02 then
SUTIL CALLERS
will update INBOUND.HIS and LASTCALL.FD files.
If you have FD 2.10 then
SUTIL CALLERS [dir]
will update INBx.HIS and LASTCx.FD files in the 'dir' directory using the
TASK environment variable for 'x'.
This has only been tested with FD 2.02 and 2.10.
*end*
*fd last call to sbbs*
Parameters
──────────
Front Door Directory: Full path to FD directory.
Examines the Front Door LASTCALL file to get the last mail call. Inserts
this info into the SBBS SCALLERS file. You can then use the SBBS 'view
today's callers' or 'view last 15 callers' to see what mail calls you've
had. Because FD doesn't store the log on and log off time seperately
these will be the same in the scallers file. Also the baud and age are not
known.
If you run FD 2.02 then you do not need the dir parameter. If you are
running the commercial version (2.10) then the dir parameter should point
to the Front Door system directory where all inbound and lastcall files
are stored. If this parameter is used SUtil will look for the TASK
environment variable used by FD to construct the file names INBx.HIS and
LASTCx.FD where 'x' is the TASK number.
In summary:
If you have FD 2.02 then
SUTIL FDCALLERS
will read INBOUND.HIS and LASTCALL.FD files.
If you have FD 2.10 then
SUTIL FDCALLERS [dir]
will read INBx.HIS and LASTCx.FD files in the 'dir' directory using the
TASK environment variable for 'x'.
This has only been tested with FD 2.02 and 2.10.
*end*
*hide local calls*
Parameters
──────────
New Baud: New baud to replace 0 baud entries.
Scans SCALLER.BBS and converts any baud settings of 0 to new setting
specified. This has the effect of making local log-ons look like remote
calls when viewing Today's Calls and Last 15 Callers.
*end*
*view bbs list*
Parameters
──────────
File: Any bbslist file (default=BBSLIST.BBS)
Displays the given bbslist file. If no file is given, the default
BBSLIST.BBS will be displayed. Any valid file name is allowed.
*end*
─────────────────────────────────────────────────────────────────────────
*doors menu*
This set of functions maintains and reports door usage. Useful for
determining the popularity, or lack of, of your on-line doors. This has
only been tested with SBBS 1.16b. In this version there is a little spare
room in the door templates which may be used by Aki in later versions.
AVAILABLE FUNCTIONS
───────────────────
UPDATE DOOR COUNTER Update a selected door counter
RESET DOOR COUNTER Reset a seleced door counter to 0
CREATE GRAPHS Create ANS/ASC graph of door counters
DOORS REPORT Report config for all active doors
*end*
*update door counter*
Parameters
──────────
Door Number: Which door to update.
Updates the door counter for the given door template number. Insert this
into your doors batch file after each door exits and before the bbs
restarts. Eg:
SUTIL DOORUPDATE 14
This adds one to the counter for door number 14 in the template.
*end*
*reset door counter*
Parameters
──────────
Door Number: Which door to reset.
Resets the door counter for the given door template number to 0. If you
remove a door from the bbs or replace it with a new one you will want to
reset it's template counter to get an accurate picture of it's popularity.
Eg:
SUTIL DOORRESET 14
To reset all doors to 0 type:
SUTIL DOORRESET ALL
*end*
─────────────────────────────────────────────────────────────────────────
*miscellaneous menu*
AVAILABLE FUNCTIONS
───────────────────
SYSTEM INFORMATION Useful overall information on your bbs
RENAME FILE TO DATE Rename a file using today's date
MESSAGE LOST CARRIER Post a message to callers who drop carrier
CREATE FILE REQUEST Create file request in netmail directory
CREATE FILE ATTACH Create file attach in netmail directory
RUN SCRIPT FILE Run selected script file
*end*
*rename file with today's date*
Parameters
──────────
File: Full path and name of file to rename.
Renames the specified file using today's date in the format yy-mm-dd.ext.
For example to rename the system log type:
SUTIL DATEFILE \SUPERBBS\SYSTEM.LOG
The resulting file would be:
\SUPERBBS\92-05-30.LOG
... or whatever the date happens to be. The reason for the particular
format for the date is when Xtree or other such program lists the files in
alphabetical order these files will show up in the correct chronological
order. Here's a little segment of my daily maintenance batch file that
makes a daily backup of the user base.
cd \superbbs
pkzip \superbbs\backup\userbak lastread.bbs nameidx.bbs users.bbs
susers.bbs
sutil datefile \superbbs\backup\userbak.zip
If the file name it wants to use to rename the file already exists it will
attempt to rename the extension until it finds an unused file name.
*end*
*post msg to lost carrier*
Parameters
──────────
Log File: Full path and name of system log file.
Text File: Text file to post.
Board: Hudson message base board to post to.
Scans the system log and looks for callers who have dropped carrier. It
then reads the text file replacing any parameters and posts it to the
caller in the specified board number.
Replacable parameters are:
^D (ASCII 4) Date caller dropped carrier
^T (ASCII 20) Time caller dropped carrier.
*end*
*matrix file request*
Parameters
──────────
Attrib: Netmail attributes.
Address: Fido compatible address.
Files: List of files to request.
Creates a file request MSG in your netmail directory as specified in your
SBBS config. Each file should be separated by a space. The msg packet
attributes are set as specified by the 'attrib' parameter.
Valid netmail attributes:
P = private C = crash
K = kill H = hold
D = direct I = immediate
N = none
*end*
*matrix file attach*
Parameters
──────────
Attrib: Netmail attributes.
Address: Fido compatible address.
File: File to attach.
Creates a file attach MSG in your netmail directory as specified in your
SBBS config. The msg packet attributes are set as specified by the
'attrib' parameter.
Valid netmail attributes:
P = private C = crash
K = kill H = hold
D = direct I = immediate
*end*
*run script file*
Parameters
──────────
Script File: Name of script file to run from the 'home' directory.
Performs the commands contained in the specified script file. Each line of
the file should have one command typed exactly how you would normally type
it on the DOS command line, minus the SUTIL bit of course. Any line
beginning with a semi-colon (;) is treated as a remark and is ignored.
From within a script file you can call another script file much the same
way that DOS can call a batch file from within a batch file. When it has
finished the embedded script file, it returns and continues on the first
one.
*end*
─────────────────────────────────────────────────────────────────────────
*external menu*
This menu allows you to add any external utilities to the SUtil
environment. For example, you might want to add the user editor, menu
editor, ansi editor and the snet manager programs. Create a text file in
the SUtil 'home' directory called EXTERNAL.MNU with one entry per line.
Each line consists of the name as it will appear on the menu, then the
directory SUtil will change to, then the program to run. Each parameter
is separated by the '|' character. For example, you might have something
like this:
EXTERNAL.MNU
SNet Manager|c:\superbbs\node1|snetmgr.exe
User Editor|c:\superbbs|sbbsuser.exe
Menu Editor|c:\superbbs|sbbsmenu.exe
Ansi Editor|c:\superbbs\text|d:\thedraw\thedraw.exe
Text Editor|c:\superbbs\text|q.exe
Config Line 1|c:\superbbs\node1|c:\superbbs\config.exe
Config Line 2|c:\superbbs\node2|c:\superbbs\config.exe
Edit SUtil Files|c:\superbbs\sutil|q
*end*
─────────────────────────────────────────────────────────────────────────
*select files area*
Highlight the files area you want to work on and press Enter.
*end*
*save report*
Parameters
──────────
File Name: Full path and name to save report to.
Reports are normally deleted when you are finished but you can save them
for later perusal. Type the full path and name for any valid DOS file
name and the current report will be saved to that file.
*end*
*report*
Valid keys for navigating the report screen:
Cursor Left: Move one column to the left.
Cursor Right: Move one column to the right.
Page Up: Move one page backwards.
Page Down: Move one page forwards.
Home: Move to first column on current line.
End: Move to last column on current line.
Cntl-Home: Move to first line on current column.
Cntl-End: Move to last line on current column.
Esc: Return to previous menu.
F1: This help screen.
F2: Save report to text file.
F3: Edit report.
F4: Search for given string.
F10: Save report to printer.
To edit a report or files list from the report viewer, you need to create
a batch file called EDIT.BAT which can reside in the current directory or
anywhere in the DOS path. This batch file will call your favorite text
editor.
*end*
*search*
Enter the string you want to search for. Case is not sensitive. Starts
search from the current position in the file. To start the search from
the beginning of the file press Ctl-Home then F4.
*end*