Skip to content
Snippets Groups Projects
Commit 6c3385b6 authored by rswindell's avatar rswindell
Browse files

These are obsolete docs (mostly DOS-specific).

parent 2c1a4fc0
No related branches found
No related tags found
No related merge requests found
SYSOP Your Name
SYSTEM Your BBS (XXX) XXX-XXXX
ADDRESS 1:123/456
INBOUND C:\IM\INBOUND
OUTBOUND C:\IM\OUTBOUND
ARCDEF ZIP 0 504B
ADD PkZip %A %F
EXTRACT PkUnzip %A
END
ARCDEF ARC 0 1A
ADD Arca %A %F
EXTRACT Arce %A
END
ARCDEF LZH 2 2D6C68
ADD Lha a %A %F
EXTRACT Lha e %A
END
ARCDEF ARJ 0 60EA
ADD Arj a %A %F
EXTRACT Arj e %A
END
NOFLO
FORCEKILLSENT
SIGDIR C:\IM
SIGKEEP 2000
CHECKPATH
DUMPUNKNOWN
AREAFILE C:\IM\SYSTEM\AREAS.BBS
NOWARN CIRCULAR DUPES ORIGIN
SCANALL
RETEAR ADD
Synchronet Version 2.2 Documentation Directory
Table of Contents
The following files should be located in the DOCS directory off of your main
BBS directory (example: C:\SBBS\DOCS).
CONTENTS TXT This file
SBBS LST List of public access Synchronet BBSs sorted by phone number
ORDER TXT Purchase order form for Synchronet v2.2
VERSIONS HST History of Synchronet package versions and release dates
VERSIONS TXT Versions of utilities included with this Synchronet package
USER DOC Synchronet User Manual (exported to ASCII)
SYSOP DOC Synchronet Sysop Manual
BAJA DOC Baja compiler/langauge documentation
BAJA_200 NEW Changes made in Baja version 2 (and incompatibility reference)
FILES REF Reference for all Synchronet data/config files
SBBSECHO DOC FidoNet EchoMail import/export (toss/scan) documentation
MAILER BAT Batch file for using Synchronet with FrontDoor/InterMail
EXEBBS BAT Batch file for using Synchronet with FrontDoor/InterMail
QEMM DOC Tips on keeping QEMM from using memory it shouldn't (crashing)
SVDMANSI DOC Documentation for OS/2 ANSI replacement
USERCOM DOC Documentation for USER.COM log search utility
TEXT210A DIF TEXT.DAT changes from v2.00 to v2.1x
TEXT220A DIF TEXT.DAT changes from v2.1x to v2.20a
TEXT220B DIF TEXT.DAT changes from v2.20a to v2.20b
V200A NEW New features introduced in v2.00a
V210A NEW New features introduced in v2.10a
V211A NEW New features introduced in v2.11a
V220A NEW New features introduced in v2.20a
SBBS HST Development history of Synchronet version 2
Third Party:
SYNCEDIT DOC Documentation for SyncEdit external editor
REGISTER FRM Registration (order) form for SyncEdit
CVT2SBBS TXT Information on how to convert previous BBS user data to SBBS
@echo off
rem ***************************************************************************
rem EXEBBS.BAT for use with FrontDoor and Synchronet BBS v1c
rem if using with InterMail, change all "FD"s to "IM"s
rem ***************************************************************************
rem ***************************************************************************
rem Drive where this Synchronet node is installed
rem ***************************************************************************
c:
rem ***************************************************************************
rem Directory for this node
rem ***************************************************************************
cd \sbbs\node1
rem ***************************************************************************
rem You probably don't want to mess with this line
rem ***************************************************************************
call sbbs qc%1 e%3
rem ***************************************************************************
rem Drive where FrontDoor is installed
rem ***************************************************************************
c:
rem ***************************************************************************
rem Change directory to FrontDoor system directory
rem ***************************************************************************
cd \fd
rem ***************************************************************************
rem Call MAILER.BAT so we go full-circle
rem ***************************************************************************
mailer
@echo off
rem ***************************************************************************
rem MAILER.BAT (AKA IMRUN.BAT or FDRUN.BAT) file for use with FrontDoor or
rem InterMail and Synchronet BBS Version 2
rem
rem If you get OUT OF ENVIRONMENT SPACE messages when using this batch file,
rem increase your DOS environment by adding the following to your CONFIG.SYS:
rem SHELL=C:\COMMAND.COM /E:1024 /P
rem ***************************************************************************
rem ***************************************************************************
rem Set this to IM for InterMail or FD for FrontDoor
rem ************************************************
set fd=FD
rem ***************************************************************************
rem Node Number - needed for NODE utility
rem *************************************
set nodenum=1
rem ***************************************************************************
rem SBBS Directory
rem **************
set sbbs=c:\sbbs
rem ***************************************************************************
rem SBBS CTRL Dir - needed for NODE utility
rem ***************************************
set sbbsctrl=%sbbs%\ctrl
rem ***************************************************************************
rem SBBS NODE Dir - needed for SBBSECHO (use NODE1 directory)
rem *********************************************************
set sbbsnode=%sbbs%\node1
:top
rem ***************************************************************************
rem Set Node status to WAITING FOR CALL
rem ***********************************
%sbbs%\exec\node status=0 %nodenum% rerun off %nodenum% event off %nodenum%
rem ***************************************************************************
rem Drive letter and directory where Mailer is installed
rem ****************************************************
c:
cd \%fd%
%fd%
rem ***************************************************************************
rem These error levels must be set in FDSETUP or IMSETUP!
rem *****************************************************
if errorlevel 200 goto fax
if errorlevel 100 goto bbs
if errorlevel 75 goto event
if errorlevel 50 goto inmail
if errorlevel 25 goto outmail
if errorlevel 10 goto userbreak
if errorlevel 1 goto error
goto end
rem ***************************************************************************
rem Mailer received in-bound mail from another system
rem *************************************************
:inmail
echo Importing in-bound mail!!!
rem ***************************************************************************
rem Set node status to NETWORKING
rem *****************************
%sbbs%\exec\node status=6 %nodenum%
%sbbs%\exec\sbbsecho /les!
goto top
rem ***************************************************************************
rem Semaphore file (xxEXIT.025) was signaled by the BBS - new outbound messages
rem ***************************************************************************
:outmail
echo Exporting out-bound mail!!!
rem ***************************************************************************
rem Set node status to NETWORKING
rem *****************************
%sbbs%\exec\node status=6 %nodenum%
%sbbs%\exec\sbbsecho /lin
rem ***************************************************************************
rem Signal the rescan semaphore so that FD will rescan the netmail folder
rem *********************************************************************
rem > fdrescan.now
goto top
rem ***************************************************************************
rem Received a call from a user wanting access to the BBS - how dare they!
rem This actually executes EXEBBS.BAT with the proper switches for SBBS
rem You will probably also need to edit EXEBBS.BAT for your configuration
rem *********************************************************************
:bbs
dobbs
rem ***************************************************************************
rem Run any pending events (Remove the 'o' if running SBBS v2.1 or earlier)
rem ***********************************************************************
:event
cd %sbbsnode%
call sbbs o
goto top
rem ***************************************************************************
rem Received a fax call
rem *******************
:fax
cd \zfax
rcvfax 2 /p:1
if errorlevel 0 echo riIncoming FAX Notification! >> \bbs\data\msgs\0001.msg
goto top
rem ***************************************************************************
rem Quit FD
rem *******
:userbreak
echo User Break.
goto end
rem ***************************************************************************
rem Mailer error of some kind
rem *************************
:error
echo %fd% ERROR (1-9)
goto end
rem ***************************************************************************
rem End of the batch file, so display a blank line for prettiness
rem *************************************************************
:end
rem ***************************************************************************
rem Make node status OFFLINE
rem ************************
%sbbs%\exec\node status=5 %nodenum%
echo.
Experience has shown that problems with DESQview usually have nothing to do
with DESQview and everything to do with QEMM.
The default QEMM config.sys line is "DEVICE=QEMM386.SYS RAM". If you are using
this config.sys line, you are playing with fire. On every system configuration
tested at Digital Dynamics, DESQview (or even just plain DOS) will eventually
crash using this config.sys line.
The problem is that QEMM is using memory regions that other components of your
systems are also trying to use. This is bad. QEMM may also not be using memory
regions that are not in use and therefore you may not be getting all the
available upper memory possible. This is important if you need to load TSRs,
device drivers, or network drivers into high memory to leave as much DOS base
memory as possible.
An example config.sys:
1: shell=c:\dos\command.com /e:1024 /p
2: stacks=0,0
3: buffers=5
4: files=50
5: lastdrive=m
6: device=c:\dev\qemm386.sys ram x=b800-c7ff i=f000-f7ff i=fd00-fdff
7: device=c:\dev\loadhi.sys c:\dev\smartdrv.sys 1024
8: device=c:\dev\loadhi.sys c:\dev\ramdrive.sys 4096 256 512 /e
9: device=c:\dev\loadhi.sys c:\dev\ansi.sys
Remember, this example config.sys will probably NOT work in your system. It
does however work in one specific system. The right config.sys line for your
system will need to be determined by you. Keep reading to find out how to make
that determination.
Note line 6, where QEMM386.SYS is loaded. The extra parameters after "ram"
are specifying that QEMM exclude (not use) the memory region B800h through
C7FFh and that QEMM should include (use) the memory regions F200h through F2FFh
and F400h through F6FFh.
The "x=b800-c7ff" part of the line is VERY IMPORTANT. Without this parameter,
this particular system will eventually crash under DESQview or even DOS alone
under some circumstances. The crash will manifest itself differently with
different system configurations. It may give you a "QEMM protection violation"
or "Invalid instruction", or "NO ROM BASIC - SYSTEM HALTED", or it just may
suddenly freeze.
The "i=nnnn-nnnn" parameters in the line tell QEMM to include (use) these
memory regions for more available high memory. You should NOT use the inclusion
parameter unless you are positive that no component of your system will try
to use that memory region (including your system BIOS).
So how do you figure what to include and exclude? By using the QEMM.COM utility
with the "analysis" parameter. The first time you run "qemm analysis", you'll
see something like this:
ͻ
Area Size Status
0000 - C2FF 780K OK
C300 - C7FF 20K Include
C800 - EFFF 160K OK
F000 - F1FF 8K Include
F200 - F2FF 4K OK
F300 - F3FF 4K Include
F400 - F6FF 12K OK
F700 - F8FF 8K Include
F900 - FAFF 8K OK
FB00 - FBFF 4K Include
FC00 - FCFF 4K OK
FD00 - FDFF 4K Include
FE00 - FFFF 8K OK
ͼ
The regions with the status "OK" mean that QEMM is dealing with it correctly.
It is either NOT using the region because another resource is using it or it
is using the region and no other resource has tried to use it since you booted.
The regions with the status of "Include" mean that QEMM is not using the region
and no other resource has tried to use it since you booted.
The regions with the status of "Exclude" (none listed above) mean that QEMM is
using the region and another resource has tried to use that region at the same
time. This region must be manually excluded with the "x=nnnn-nnnn" parameter
on your config.sys line.
Now don't be fooled by all the "Include" regions above in that box. As you use
the system, those regions will shrink, split, or disappear altogether. After
executing "qemm analysis" (producing the above output) and then accessing a
floppy drive, the "Include" regions already begin to disappear:
ͻ
Area Size Status
0000 - C2FF 780K OK
C300 - C7FF 20K Include
C800 - EFFF 160K OK
F000 - F1FF 8K Include
F200 - F2FF 4K OK
F300 - F3FF 4K Include
F400 - F6FF 12K OK
F700 - F8FF 8K Include
F900 - FCFF 16K OK
FD00 - FDFF 4K Include
FE00 - FFFF 8K OK
ͼ
After switching into every available video mode and running "qemm analysis"
again:
ͻ
Area Size Status
0000 - C5FF 792K OK
C600 - C6FF 4K Include
C700 - EFFF 164K OK
F000 - F1FF 8K Include
F200 - F2FF 4K OK
F300 - F3FF 4K Include
F400 - F6FF 12K OK
F700 - F8FF 8K Include
F900 - FCFF 16K OK
FD00 - FDFF 4K Include
FE00 - FFFF 8K OK
ͼ
After typing "echo ^g" at the DOS prompt (^g stands for Ctrl-G) and then
running "qemm analysis" again:
ͻ
Area Size Status
0000 - C5FF 792K OK
C600 - C6FF 4K Include
C700 - EFFF 164K OK
F000 - F1FF 8K Include
F200 - F2FF 4K OK
F300 - F3FF 4K Include
F400 - F6FF 12K OK
F700 - F7FF 4K Include
F800 - FCFF 20K OK
FD00 - FDFF 4K Include
FE00 - FFFF 8K OK
ͼ
As you can see, just about every system function will effect the regions that
QEMM thinks you can safely include. It is a good idea to run just above every
application you can and access every device on your system before deciding
that the information provided by "qemm analysis" may be accurate and usable.
If "qemm analysis" every reports a region with the status of "Exclude", do not
question it. Immediately edit your config.sys excluding that region and reboot.
If, for example, "qemm analysis" reports:
ͻ
Area Size Status
0000 - C5FF 792K OK
C600 - C6FF 4K Include
C700 - EFFF 164K OK
F000 - F1FF 8K Exclude
F200 - F2FF 4K OK
F300 - F3FF 4K Include
F400 - F6FF 12K OK
F700 - F7FF 4K Include
F800 - FCFF 20K OK
FD00 - FDFF 4K Include
FE00 - FFFF 8K OK
ͼ
Edit your config.sys file addding "x=f000-f1ff" at the end of your
"device=qemm386.sys" line. Then reboot your system.
USER.COM Documentation
----------------------
This utility will extract the activity and statistics of a particular user from
the Synchronet detailed log files.
usage: user <username> <logfiles>
'username' is the name or number of the user whose doings should be extracted.
It should be placed in double quotes if the name is more than one
word, and is case sensitive.
'logfiles' is a log filename or list of log files to search (wildcards are ok)
It is useful to redirect the output of USER.COM into a text file for viewing.
Examples: user "Bill Wagstaff" c:\sbbs\data\logs\07*.log > bwag.txt
user 0155 ..\maylogs\*.log ..\junlogs\*.log >rbar.txt
Versions of Utilities Included with this Synchronet Package
===========================================================
The "Filename" column specifies the program filename or sub-directory.
The "Vers" column indicates the version number of the program.
The "SBBS" column indicates the SBBS package when the program was last updated.
The "Description" column is a description of the program.
Filename Vers SBBS Description
-------- ---- ---- -------------------------------------------------------
UTI* 2.23 220A UTI driver set for PostLink v1.05+
ADDFILES 2.22 220B Add files to database from DOS prompt or BAT file
DELFILES 1.01 220B Delete files from database or disk from DOS prompt
FILELIST 2.10 220A Generate ASCII file listings of file directories
DUPEFIND 1.01 210A Finds duplciate file names in file directories
AUTONODE 2.00 200A Find first available node for local logon
BAJA 2.01 220B Command shell/module (EXEC\*.SRC) compiler
NODE 1.03 1B03 Node display/control utility
SLOG 1.01 210A System/node statistics log viewer
DSTSEDIT 1.01 200A System/node daily statistics editor
ANS2MSG 1.06 220A ANSI to Ctrl-A conversion utility (for ASC/MSG files)
MSG2ANS 1.03 200A Ctrl-A to ANSI conversion utility
MLABELS 2.11 220A Generate mailing labels from Synchronet user data
TONE 1.01 200A Tone generation utility (external chat pager)
DBCS 1.00 1C01 DigiBoard channel status utility
USER 1.00 1A12 Pull specific user logons out of DATA\LOGS\*.LOG files
ALLUSERS 2.11 220A Bulk command line user editor
QWKNODES 1.20 220A QWKnet Node/Route/User list generator
CHKSMB 1.24 220A Checks Synchronet message base(s) for corruption
FIXSMB 1.22 220A Rebuilds Synchronet message base index and alloc files
SMBUTIL 1.24 220A Message base utility for maintaining and packing
SMBACTIV 1.00 210A Displays message base activity (users reading subs)
SYNCEDIT 2.05 220B SyncEdit external message editor (Unregistered)
SBBSECHO 1.12 220B FidoNet EchoMail import/export program (Unregistered)
XTRN\SDK 2.34 220B External program software developer's kit (Freeware)
XTRN\SBJ 2.31 220A Synchronet Blackjack Game with C source code (Freeware)
XTRN\SBL 1.36 220A Synchronet BBS List Door with C source code (Freeware)
XTRN\SCB 1.32 220A Synchronet Callback Verifier (Unregistered)
XTRN\SMM 1.31 220B Synchronet Match Maker (Unregistered)
XTRN\SCP 2.30 200A Supernet Centipede (Freeware)
XTRN\DPOKER 1.40 200G Domain Poker Multi-Player Online Game (Unregistered)
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment