RSDS Logo R.S. Digital Solutions
Stony Plain, Alberta, Canada
 

BBS Utilities

The following are some Bulletin Board System (BBS) utilities developed for use on the Power Station BBS. This BBS operates in the FidoNet network of bulletin board systems. Most are written to operate under DOS and/or OS/2. Many have the source code included in the archive. If you find any of them useful, or have any comments, please

300.000 vista icons

For a great selection of icons (many sets are available for free), be sure to check out IconShock. While you're there you should check out our Icons community.


BBS2OEC (v1.01 - 1988-01-01)

This program is designed to read an input file in oANSI format and output a file in OEC source code. The file can then be edited and recompiled as necessary (or desired).

OEC stands for the Opus Embedded Command language as developed by George A. Stanislav and, when compiled with his OECC program, provides a simple method of developing oANSI .BBS files for use with Opus. BBS2OEC has been designed to be used in conjunction with the OECL/OECC package to return the OECL source code from a file that has been compiled using OECC.

BBBS Password Updater (v1.01 - 2003-03-10)

Allows a BBBS sysop to change user passwords from the command line. Full source code is included. Also includes sample scripts to implement a forgotten password "challenge response" system to automatically verify a user's identity and generate a new temporary password without the need for sysop intervention.

BT_Calls (v1.10 - 1997-03-09)

Analyzes a BinkleyTerm log file and generates an output file showing the percentage of outgoing connections for each node called. The program will optionally maintain a BT_CALLS.TRK file which will list the earliest report period that a node has been unreachable. as soon as a successful connection has been found in the log, the node is removed from the tracking file.

CallerEd (v1.00 - 1994-02-26)

This program is designed to provide a method for the operator of a Fido v12 system to edit their caller records. The program uses the FIDO.SYS file to locate the CALLER.SYS file used by Fido v12, as well as the default currency settings.

Extr_Net (v2.30 - 2003-03-07)

This program is designed to read an input fidonet nodelist file and extract selected Networks, Regions and/or Zones. The extracted portions of the nodelist are stored in a file specified on the command line. Includes a pre-compiled Linux binary along will complete 'C' source code for compiling on other platforms.

FD_Calls (v1.03 - 1997-08-10)

This program is used to read the FrontDoor log file and produce a summary report (FD_CALLS.RPT) of all outgoing calls by: number of calls; no answers; busy; interrupted by incoming call; and connections. It also includes a percentage connection rate. The program is based on FDLA.

Fido-Top (v1.02 - 1991-10-29)

This program is used to read the Fido 12 CALLER.SYS files and generate a file listing the top users (upload, download, calls) for the BBS. The CALLER.SYS file must be in the current directory.

FilesBBS (v1.40 - 1995-08-20)

This program is designed to read a file area description file such as the FILES.BBS file used by the Fido BBS software, and re-format all file identification lines. The program creates a backup file prior to beginning the re-formatting operation.

Last2Dor (v1.01 - 1993-10-17)

This program is used to read the LASTUSER.BBS file generated by Fido 12 and extract the user's information into a DORINFOx.DEF file. The LASTUSER.BBS file must be in the current directory. LAST2DOR requires a configuration file called LAST2DOR.CFG in the current directory.

Last2Sys (v1.11 - 1993-10-17)

This program is used to read the LASTUSER.BBS file generated by Fido 12 and extract the user's information into a DOOR.SYS file. The LASTUSER.BBS file must be in the current directory.

LookNode (v1.11 - 1993-11-14)

This program is designed to provide nodelist information for operator selected Nodes. The program uses the Fido v12 FIDO.SYS file to locate the NODELIST.BBS, NODELIST.IDX and NODELIST.NDX files used by Fido v12, as well as the default zone and currency settings.

Max2AL (v1.10 - 1994-06-04)

This program is designed to read a Maximus file area control file and write an areas list file to include in a AvaiList configuration file.

MBPurge (v1.00 - 1995-08-29)

This program is used to read the MEXBANK.DAT file generated by MexBank and remove any users not found in the Maximus USER.BBS file. Both files must be in the current directory.

Max-Top (v1.30 - 1995-11-25)

This program is used to read the Max 3.00 USER.BBS file and generate a file listing the top users (upload, download, calls) for the BBS. The first record in USER.BBS (usually the sysop) is ignored.

The program is based on an example program included with the Maximus User Language (MUL) package for use with Maximus 2.x, which is Copyright (c) by CodeLand Australia.

MUPurge (v1.20 - 1995-11-23)

This program is used to read the Max 3.00 USER.BBS file in the current directory and purge users based on a combination of access, number of calls, and days since the last call. Purge criteria are determined by the Sysop in a control file. The first record in USER.BBS (usually the sysop) is ignored, as are any records marked as "Permanent". Records marked as "Deleted" are purged.

NL-CRC (v1.00 - 1994-05-29)

This program is designed to read an input nodelist file and return the correct CRC value which should be displayed in the first line.

NLReport (v1.00 - 1994-10-22)

This program is designed to read a nodelist file and report on the contents of that file.

Triggers (v1.11 - 1993-10-17)

This program is used to set/reset the Fido 12 event triggers in the FIDO.SYS file for the BBS. The FIDO.SYS file must be in the current directory.

Un-Flags (v1.01 - 1994-07-03)

This program is designed to read a nodelist file and report on the nodes that are marked with a phone number of -Unpublished-.

This program is my way of making a statement regarding the controversy surrounding nodelist flags. There are many points of view on this issue, but I believe that they all come down to two. Those who want more flags, and those who want less. Those who are promoting the reduction in the number of nodelist flags generally use the massive size of the nodelist as their argument. Those calling for more flags counter with the argument that the various mailers available use this information for dynamically setting session data. Both are correct, in their own way. I tend to believe that many of those calling for new flags are really looking for more to fly as a status thing.

If we really want to reduce the nodelist, why not eliminate the flags from systems that do not have a published telephone number. What use are these flags to a mailer when the node can't be called anyway. I believe that these serve no useful purpose, and are vanity at its finest. In order to illustrate the uselessness of these flags, this program was developed.