Dec 112017
DBASE BBS List Maintenance Program.
File DBASEBBS.ZIP from The Programmer’s Corner in
Category Dbase Source Code
DBASE BBS List Maintenance Program.
File Name File Size Zip Size Zip Type
COM.BAT 134 91 deflated
COMMENT.DBF 20451 874 deflated
COMMENT.PRG 2052 499 deflated
DBBS.DOC 4530 1733 deflated
DBBS.PRG 6986 1698 deflated
FILES.DBF 5281 2023 deflated
FILES.PRG 3157 847 deflated
LOADER.PRG 373 200 deflated
MESSAGES.DBF 17433 1690 deflated
MESSAGES.PRG 9240 1499 deflated
TEMP.DBF 66 33 deflated
TONE.ASM 3840 1325 deflated
TONE.OBJ 119 101 deflated
TUNE.OBJ 921 483 deflated
USER.DBF 2818 906 deflated

Download File DBASEBBS.ZIP Here

Contents of the DBBS.DOC file

TurnKey Technologies
6302 Riverdale Street
San Diego, CA 92120
Data 202/102 (619)563-6688
Voice (619)563-8416
Jay Kenney

- Redirects all output to the remote and local monitors. -

This program is far from complete. It must be compiled with Clipper
and have the ANSI.OBJ added at link time like this:


It reads your existing FILES.BBS (Opus or QuickBBS format) with the
LOADER.PRG. Right now the only way to get that to happen is to copy
FILE.DBF, TEMP.DBF and LOADER.PRG to each file area you have, then
run DBASE LOADER which will create a FILES.DBF for that area.

Uses DSZ.COM for Zmodem and Xmodem file downloads. You must have
DSZ.COM available and MUST edit FILES.PRG to point it to your
available files directories. With a little tinkering, you should be
able to implement uploads in the FILES.PRG. I just haven't taken the
time to do this yet.

Binkley on the front end with an exit on errorlevel called like below
calls MODE to handle 300,1200 and 2400 baud connects:

mode COM1:24,N,8,1,
echo off
mode COM1:24,N,8,1,
bt unattended
if ERRORLEVEL 100 goto local
if ERRORLEVEL 90 goto renum
if ERRORLEVEL 80 goto xlatlist
if ERRORLEVEL 70 goto renum
if ERRORLEVEL 40 goto postexit
if ERRORLEVEL 30 goto postarc
if ERRORLEVEL 24 goto opus2400
if ERRORLEVEL 20 goto postrecv
if ERRORLEVEL 15 goto cycle
if ERRORLEVEL 12 goto opus1200
if ERRORLEVEL 10 goto start
if ERRORLEVEL 6 goto mort
if ERRORLEVEL 5 goto start
if ERRORLEVEL 3 goto opus300
if ERRORLEVEL 1 goto end

goto start

dbbs /ansi >COM1 goto after

mode COM1:12,N,8,1,
dbbs /ansi >COM1 mode COM1:24,N,8,1,
goto after

mode COM1:3,N,8,1,
dbbs /ansi >COM1 mode COM1:24,N,8,1,
goto after

if ERRORLEVEL 255 goto start
if ERRORLEVEL 70 goto renum
if ERRORLEVEL 60 goto mort
if ERRORLEVEL 30 goto postarc
if ERRORLEVEL 20 goto postrecv
if ERRORLEVEL 12 goto start
if ERRORLEVEL 7 goto postexit
if ERRORLEVEL 6 goto mort
if ERRORLEVEL 5 goto qmail
if ERRORLEVEL 4 goto qmail
if ERRORLEVEL 3 goto qmail
if ERRORLEVEL 2 goto start
if ERRORLEVEL 1 goto start
if ERRORLEVEL 0 goto start

THIS DOES NOT WORK! You'll need to compile a version without
the calls to WATCHDG and setting the printer to COM1.
goto after


Things it needs:

1) Word-wrap in messages and comments.

2) Modem control to watch carrier detect so WATCHCD is not necessary.
If a caller exit with G)oodbye, it will return to Binkley without
rebooting...BUT...if they drop carrier anywhere inside DBBS,
WATCHDG will reboot the machine.
Maybe just drop it back to Binkley after a lost carrier?
Current Bonzai-modem control is primitive yet works...

3) Interface to Fidonet Mail via Sirius or Overdrive?
* If this is possible it could eliminate the need for the current
messy messages and comments program.

4) Can user color preferences be stored in USER.DBF?
Would color redirect? I haven't tried this.

5) Chat or local sysop intervention.
* I can't get anything to work from the local keyboard with everything
redirected to the COM port.

6) Sysop utilities, log reporting, and a method to control user time on
system. (These should be pretty easy.)

7) Last, but far from least, it needs your input. I write dBase applications
for clients and don't care to have to learn C to play with a BBS program.
If you find a way to make it work better, I'd appreciate hearing from you.

Long live Ashton-Tate!

Jay Kenney

 December 11, 2017  Add comments

Leave a Reply