Dec 252017
Documentation for BBSEE version 2.4.

Full Description of File

BBSee file catalog system documentation file.
Also BBSee's IMPORT PCBoard BBS conversion
file program. [2 of 2]

File BBSEE24B.ZIP from The Programmer’s Corner in
Category BBS Files
Documentation for BBSEE version 2.4.
File Name File Size Zip Size Zip Type
2ROBO.EXE 35130 34074 deflated
BBSEE.DOC 140822 38319 deflated
BBSEE0.ICO 766 198 deflated
BBSEE1.ICO 766 212 deflated
BBSEE2.ICO 766 274 deflated
FILE_ID.DIZ 116 105 deflated
GO.BAT 862 424 deflated
HISTORY 7960 3055 deflated
IMPORT.EXE 28810 27850 deflated
REGISTER.FRM 2279 905 deflated
SAMPLE 12776 4078 deflated

Download File BBSEE24B.ZIP Here

Contents of the BBSEE.DOC file

BBSee User's Manual And Reference

Copyright (C) 1991,1992 Martin Vallevand

Table of Contents

Chapter 1 General Information . . . . . . . . . . . . . . . . . . 1
1.1 What does BBSee do? . . . . . . . . . . . . . . . . . . 1
1.2 License . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 BBSee Files. . . . . . . . . . . . . . . . . . . . . . 3
1.4 On-Line Help . . . . . . . . . . . . . . . . . . . . . 4

1.5 System requirements . . . . . . . . . . . . . . . . . . . . 4
1.6 Background . . . . . . . . . . . . . . . . . . . . . . 5
1.7 Credits . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 Configuration . . . . . . . . . . . . . . . . . . . . . 7
2.1 BBSEE.CFG . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Database Filenames . . . . . . . . . . . . . . . . . . 8
2.3 General directory and files . . . . . . . . . . . . . . 9
2.4 Tag Files Facility. . . . . . . . . . . . . . . . . . . 10
2.5 Output Directory files . . . . . . . . . . . . . . . . 11
2.6 Single word exclusions, . . . . . . . . . . . . . . . . 12
2.7 Source / BBS Board Selection . . . . . . . . . . . . . 12
2.8 Area/Conference Support. . . . . . . . . . . . . . . 13
2.9 Catalog Configuration . . . . . . . . . . . . . . . . . 13
2.10 Fill Configuration . . . . . . . . . . . . . . . . . . 14
2.11 Function Keys . . . . . . . . . . . . . . . . . . . . . 15
2.12 Volume Templates . . . . . . . . . . . . . . . . . . . 15
2.13 Analyze Directory . . . . . . . . . . . . . . . . . . . 15
2.14 Hardware Installation . . . . . . . . . . . . . . . . . 16
2.14.1 Video Installation . . . . . . . . . . . . . . . 16
2.14.2 EMS Support. . . . . . . . . . . . . . . . . . . 17
2.14.3 Mouse Support. . . . . . . . . . . . . . . . . . 17
2.14.4 Sound . . . . . . . . . . . . . . . . . . . . . 17
2.14.5 Clock . . . . . . . . . . . . . . . . . . . . . 17
2.15 Miscellaneous . . . . . . . . . . . . . . . . . . . . . 17
2.16 Print Order Form. . . . . . . . . . . . . . . . . . . . 18

Chapter 3 File Function . . . . . . . . . . . . . . . . . . . . . 19
3.1 File importation . . . . . . . . . . . . . . . . . . . 19
3.2 File Duplication . . . . . . . . . . . . . . . . . . . 21
3.3 Uncompress and Import NEWFILES.DAT . . . . . . . . . . 21
3.4 Modify Import Options . . . . . . . . . . . . . . . . . 22
3.5 Create Record . . . . . . . . . . . . . . . . . . . . . 22
3.6 File Manager . . . . . . . . . . . . . . . . . . . . . 22
3.6.1 List file . . . . . . . . . . . . . . . . . . . . 23
3.7 Floppy Directory . . . . . . . . . . . . . . . . . . . 24
3.8 BBSee Shell . . . . . . . . . . . . . . . . . . . . . . 24
3.9 DOS Shell . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 4 Search Function . . . . . . . . . . . . . . . . . . . . 25
4.1 Word Search . . . . . . . . . . . . . . . . . . . . . . 25
4.2 Filename Search . . . . . . . . . . . . . . . . . . . . 25
4.3 Output Search List . . . . . . . . . . . . . . . . . . 26
4.4 Show All/Show Catalog/Show Uncat'd . . . . . . . . . . 26
4.5 Local BBS Searching . . . . . . . . . . . . . . . . . . 26
4.6 Catalog File Searching . . . . . . . . . . . . . . . . 26

Chapter 5 Catalog Function . . . . . . . . . . . . . . . . . . . 27
5.1 Catalog . . . . . . . . . . . . . . . . . . . . . . . 27
5.2 Uncatalog . . . . . . . . . . . . . . . . . . . . . . 27
5.3 Pseudonym Cataloging . . . . . . . . . . . . . . . . . 28
5.4 Label floppy . . . . . . . . . . . . . . . . . . . . . 28
5.4.1 Label Templates . . . . . . . . . . . . . . . . . 29
5.5 Make Catalog Report . . . . . . . . . . . . . . . . . . 29
5.6 Fill . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.7 View Catalog . . . . . . . . . . . . . . . . . . . . . 31
5.7.1 Volume Categories. . . . . . . . . . . . . . . . 32
5.8 Show Catalog/Archive Files . . . . . . . . . . . . . . 32
5.8.1 Find Files . . . . . . . . . . . . . . . . . . . 32
5.8.2 Scan Files . . . . . . . . . . . . . . . . . . . 32
5.9 Modify Options . . . . . . . . . . . . . . . . . . . . 33
5.10 Catalog eXtract, Copy and View. . . . . . . . . . . . . 33
5.10.1 eXtract . . . . . . . . . . . . . . . . . . . . 33
5.10.2 Copy File . . . . . . . . . . . . . . . . . . . 34
5.10.3 View File . . . . . . . . . . . . . . . . . . . 34

Chapter 6 Tag Function . . . . . . . . . . . . . . . . . . . . . 35
6.1 Delete tagged file . . . . . . . . . . . . . . . . . . 35
6.2 Create download file . . . . . . . . . . . . . . . . . 35
6.3 Remove tags . . . . . . . . . . . . . . . . . . . . . . 35
6.4 Create upload files . . . . . . . . . . . . . . . . . . 35
6.5 Output tags to disk . . . . . . . . . . . . . . . . . . 36
6.6 View tags . . . . . . . . . . . . . . . . . . . . . . . 36
6.7 Edit Tags . . . . . . . . . . . . . . . . . . . . . . . 36
6.8 Load Tags . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 7 Describe Function . . . . . . . . . . . . . . . . . . . 37
7.1 Input File List . . . . . . . . . . . . . . . . . . . . 37
7.2 4DOS Description. . . . . . . . . . . . . . . . . . . . 37
7.3 Describe Floppy . . . . . . . . . . . . . . . . . . . . 37
7.4 Cross Reference . . . . . . . . . . . . . . . . . . . . 37
7.5 Report Options . . . . . . . . . . . . . . . . . . . . 38
7.6 Analyze directory . . . . . . . . . . . . . . . . . . . 38

Chapter 8 Using the program . . . . . . . . . . . . . . . . . . . 39

Chapter 9 Command line arguments . . . . . . . . . . . . . . . . 40


Appendix A Registration Information . . . . . . . . . . . . . 42

Appendix B Where to find BBSee. . . . . . . . . . . . . . . . 44

Appendix C Program Return Codes . . . . . . . . . . . . . . . 45

Appendix D Cursor Movement and Editing Keys . . . . . . . . . 46

Appendix E Mouse Support. . . . . . . . . . . . . . . . . . . 47

Appendix F Import Usage . . . . . . . . . . . . . . . . . . . 49

Appendix G Database Packing . . . . . . . . . . . . . . . . . 51

Appendix H Deleted File List Maintenance . . . . . . . . . . 52

Appendix I Robocomm download support. . . . . . . . . . . . . 54

BBSee Version 2.4

Chapter 1 General Information

1.1 What does BBSee do?

BBSee is a program designed to help people who accumulate lots of
files, easily find the files they have access to, in their catalogs or
on BBS's or other source. The heart of the program are two databases,
the database of the filelists obtained from the BBS's and online
services you use, and the database of your cataloged floppies. Using
these databases, BBSee will provides various advanced options to help
manage these files.

The principle functions in BBSee are;

The file import function which allows you to bring file list and
description files into the database from most popular BBS'es.
This database file will normally be smaller than your original
BBS list and can be configured to meet personal database

The fast and powerful search function which enables you to locate
files from up to 16 BBS lists, and your own floppies in one
search. This search can be an instantaneous filename search, or
a complex but quick multi-word search.

The sophisticated disk catalog system with capabilities designed
to help manage your files, with a minimum amount of time and

The fill floppy function which provides a method of optimizing
floppy disk use.

An interface to many automated BBS programs and scripts, allowing
you to tag files for up/and download, and create the files
required by these useful programs.

1.2 License

BBSee is a commercial package, that is being distributed as
shareware for evaluation purposes only. This is not public
domain, or free software. After a reasonable period of
evaluation, (one month), if you decide not to purchase a
registered version of BBSee, you must delete all copies of BBSee,
in uncompressed form, that you have in your possession. If you
feel that you require a longer period of evaluation, provide the
author, Martin Vallevand, with an explanation of why more time is
required, and a one-time extension of sixty days will be

Page 1

BBSee Version 2.4

Everyone is permitted, and encouraged, to distribute the
shareware package freely to potential users and on-line BBS's, as
long as there is no charge or profit motive for providing this
service, beyond the material cost of distribution, and that a
complete set of programs (A and B) as specified in section 1.3 of
this document is distributed. Profit-oriented BBSs and other on-
line service operators are fully authorized to have BBSee archive
files for download, provided the files are available to all users
of the service at no additional charge.

Anyone wishing to distribute BBSee archive files on a CD ROM must
provide Martin Vallevand with the name, price, and source of the
CD, the file names of the BBSee archives files contained on the
CD, and the scheduled production date of the CD. If the release
date of BBSee, as indicated in the HISTORY file, is not within
three months of the production date of the disk Martin
Vallevand's written consent is required. In addition, the CD ROM
packaging must clearly identify that most shareware programs
require PAID registration before they can be used beyond a
limited evaluation period.

BBSee has been subject to thorough testing, and every reasonable
effort has been made to make BBSee a safe, fast, and easy to use
package. However the databases that BBSee makes, can easily be
the largest databases that many people will ever see on their
computers. With such large systems, there are many ways to
corrupt the database, including rebooting the computer or
powering down during use of BBSee, so care is advised.

Also, it is impossible to test this program on the many
combinations of computer software and hardware available in the
PC marketplace, and to anticipate all uses for software.
Therefore all copies of BBSee, and any program distributed with
the package, shareware, or registered, are purchased AS IS, and
Martin Vallevand will not be held responsible for any damage, to
your computer, programs, data, or anything else for that matter,
that may result from its use. By using BBSee you consent to do
so at your own risk. If you find that this is unsatisfactory, DO
NOT run BBSee.

See Appendix A for further information on registering BBSee, and
on contacting the author for further clarification.

Page 2

BBSee Version 2.4

1.3 BBSee Files.

Files on the 'Program' archive #1 BBSEE24A.ZIP
BBSEE.EXE Program File
README.2ND Latest file information.
QUICKST.ART Start using BBSee now.
BBSEE.HLP On-Line Help File
WHATS.NEW Information on new features in this release.
FILE_ID.DIZ Description File

Files on the 'Program' archive #2 BBSEE24B.ZIP
BBSEE.DOC Documentation
IMPORT.EXE General BBS file listing conversion utility.
2ROBO.EXE Interface to Robocomm.
SAMPLE A file for use as a test import.
REGISTER.FRM Form used to register BBSee.
GO.BAT The first thing most people do.
BBSEE1.ICO Microsoft Windows Icon
BBSEE2.ICO " " "
HISTORY Revision history for BBSee.
FILE_ID.DIZ Description File

These two archive files make up the files required for standard
distribution of the BBSee program.

Files on the 'Extras' archive BBSEE24X.ZIP

READDEL.EXE Delete file reader.
WRITEDEL.EXE Delete file writer.
PACBBSEE.EXE Database 'pack' utility.
REBOBBS.EXE Utility to re-structure the BBS information.
BBC2PCB.EXE Utility to create a PCBoard-like list of the
entire master database.
4DLS.EXE Utility to create a file which could be used by
the program DLS.EXE to print labels for cataloged
FILE_ID.DIZ Description File

The files in the extras archives are not essential to run BBSee,
but they certainly will make its use more versatile. Depending
on file import needs other utilities may be added to this list.
Check the README file for the latest information.

Page 3

BBSee Version 2.4

Files in the 'Conversion' archive BBSEE24C.ZIP

CATCON.EXE Conversion from various other program to BBSee
catalog format. These are CatDisk, CUDM,
DiskTrak, InteliCat, and Wssindex.
CATCON.DOC Documentation for above.
ASP2BBC.EXE Utility to add ASP catalog to BBSee database.
ASP2BBC.DOC Documentation for above.
FIX4DIZ.EXE Fix for non-standard .DIZ files from previous
versions of BBSee (pre 2.21).
FILE_ID.DIZ Description File

These are various files used to convert catalog databases from
other programs to BBSee format.

If you are having trouble finding these files through any of your
regular sources they (or the current versions) can be obtained as
explained in Appendix B.

1.4 On-Line Help

The file BBSEE.HLP provides on-line help for BBSee. To run
properly BBSEE.HLP should be located in the same subdirectory as
BBSEE.EXE. This will allow BBSee to run from a path and still
access the help file. BBSee will run without the help file, but
it will display an error message when the help function is

Online help is not meant as a substitute for reading this
documentation, but as a quick reference to most of BBSee's
functions. The help is available by pressing from any menu
or sub-menu option.

1.5 System requirements

100% IBM compatible computer.
MS-DOS 3.30 or higher. (lower versions were not tested)
A minimum 500K free RAM, or 440K and use of 100K of EMS.
12 file handles and open DOS files (from CONFIG.SYS).
You must have a line of FILES=20 or more in your CONFIG.SYS file.
Hard disk strongly recommended.

BBSee will use as much disk space as you would like to devote to
BBS file listings. The faster the disk transfer rate the better.
The addition of disk caching, even as small as 128K, will
significantly improve performance.

Page 4

BBSee Version 2.4

1.6 Background

This program is written in the large model of Borland C++ 3.1,
CXL 5.2 and the MIX C/database toolchest. I believe these to all
be excellent, inexpensive, packages although the database package
can be slow on adding records to a large database. A fast string
search algorithm, the Boyer-Moore algorithm, is used to find
words. To me this is to brute force searching, what qsort is to
a bubble sort. Most of the overhead is in the disk read. CXL
has been superseded by TCXL however I found too many bugs in
version 5.51 to use it, and have not yet tried the later

BBSee and BBSetup have been compressed with LZEXE, and further
processed to disable UNLZEXEing as a very limited means of
protecting the programs from alteration. The registered version
can be ordered in uncompressed format if you specify this on the
order form.

All the file writes in the BBSee program use standard Borland C
calls, with the exception of the routines that manipulate the
label on the floppy, which use extended FCBs and DOS interrupts.
Other than directly writing to the floppy disk sectors, I don't
believe there is another method to write the volume label. I
have read, that everyone should use the DOS label program to
label diskettes, for technical reasons, so I will mirror that

Regardless of whether you use BBSee or not, I strongly recommend
that all users of DOS 4.0, always run the DOS SHARE.EXE command,
to protect themselves from deficiencies in the FCB structures in
their version of DOS. As well, if your drives support disk
change indication, you will be provided with better protection
for your valuable archive floppy disks. Upgrading to DOS 5 is
highly recommended.

1.7 Credits

I would like to thank the following people for assisting me in
the development of this software. The diligent work of this team
of beta testers and proof readers has helped me so much, and I
believe their many suggestions have greatly enhanced the
functionality of BBSee.

Bernard "The Exterminator" Desruisseaux for finding bugs big and
small, and for providing many good (and sound) ideas.

Paul "The Cosmetician" Loshuk for keeping the documentation and
help clean, and for prompting me to take BBSee beyond the simple
program I first intended.

Page 5

BBSee Version 2.4

John Zaharychuk for providing good ideas, 'different' hardware
platforms and putting up with 2400 baud file transfers.

Daniel Verreault for having the knack of identifying database
problems. Also his help with help and the documentation for
version are appreciated.

Michel Tordion, Phil Lachance, Gordon Haff, Tony Dibenedetto,
John Lindeyer, Dominique Plante, Dan Wood, Serge Cote and others
for taking the time to help with the beta testing.

All the people who have registered so far, they propel me to keep

Angela Tweeddale for putting up with me through all of this

Daniel Coulombe for allowing SYNAPSE BBS to be used as the basis
for the beta testing, and the 'home' of BBSee.

Chris Grainger for allowing File Request access for BBSee on his
Exception #13 BBS.

Page 6

BBSee Version 2.4

Chapter 2 Configuration

Because of the many options available in BBSee, the most complicated
aspect of using BBSee, is in configuring it to your needs. BBSee
needs to know the location of many files and programs, if you intend
to use all its options. If you don't install BBSee correctly then
these options may not function properly, and/or BBSee may exit with an
error code. Also BBSee will overwrite certain files if they exist
(although BBSee's 'filenames' should not conflict with files you
have), so some care should be used in reviewing default filenames.

BBSee configuration is performed in a program, BBSETUP.EXE that
handles all aspects of BBSee configuration. Although this program
MUST be run initially, it also can be used to reconfigure options at
any time. As you become proficient in the use of BBSee, you will
probably go into BBSetup, many times, to change the inclusion and
exclusion word lists, and to fine-tune things to your liking.

Note as a general rule whenever user input is required in BBSEE.EXE or
BBSETUP.EXE, selecting will cancel the operation, will get
help (in BBSee), will select the option or move to the next
option and will process an entire set of choices. See
Appendix D for further information.


All configuration information is contained in the file BBSEE.CFG.
BBSee searches for the file BBSEE.CFG in the default directory,
and if not found BBSee searches in the same directory that
BBSEE.EXE was run from.

If BBSEE.CFG is not found in the above steps BBSee will abort
indicating that BBSETUP.EXE must be run first.

To create BBSEE.CFG it is necessary to run the program
BBSETUP.EXE first. Do not create this file manually. The rest
of this section deals with using this program. You can opt to
install BBSee with only default information however some more
advanced features will not be available, or work properly.


BBSetup is a DOS program that runs from the DOS prompt. It
creates the file described above, BBSEE.CFG, in the default
directory. You can create as many BBSEE.CFG files as you wish.
The main purpose for doing this would be to maintain separate
database files, exclusion lists and floppy catalogs.

Page 7

BBSee Version 2.4

The main menu for BBSETUP.EXE is as follows:

BBSee Configuration
Database Filenames
General directories and files
Output directory files

Single word exclusions
Paired word exclusions
File Extension exclusions
Required words
BBS/Source names
Local BBS's

Catalog Options
Function Keys
Volume Template
Analyze Directory
Hardware Installation
Print Order Form

The directories and filenames for all files used by BBSee are outlined
in this section. Note that the sub-directory mentioned should be of
the form drive:\subdirectory with no trailing backslash. If you must
use the root directory, which I don't recommend, DO NOT include the
backslash. These fields are checked for the existence of drives or
directories, however you should ensure that they are correct. PLEASE
BE CAREFUL. Also note that if you re-organize your hard disk, you
will have to make corresponding changes to BBSEE.CFG.

2.2 Database Filenames

The first step in configuration is to enter the name of the
master database and the catalog database. The reason that the
database filenames are not fixed is to allow multiple BBS list
databases and disk catalogs, in separate sub-directories, if

BBSee creates in total ten permanent database files,

1. the master database file and index, (mastername.DB and
2. the index of deleted files, ( mastername.DEL ),
3. the catalog file and index, (catalogname.DB and .IDX),

Page 8

BBSee Version 2.4

4. the catalog volume database file and index (volumes.DB and
5. the archive content database file and index (archives.DB and

It is possible to have different combinations of catalog and
description databases. If you have multiple catalogs please note
that the volume and archive content files are related, and their
names should be changed as a pair. If you do not catalog within
archives or in only one catalog this is not a consideration.

2.3 General directory and files

The BBS description directory is the sub-directory where most of
your file description lists will be located. This can be
modified during the import function of BBSee.

The Download File directory is the sub-directory where your
telecommunication program places downloaded files. This is used
in the Analyze Directory option of Catalog. As well this
directory is searched before download files lists are created.

Archive Files directory is the sub-directory where files could be
moved after being downloaded, but before being moved to floppy
disk. This is used in the Analyze Directory option. As well
this directory is searched before download files lists are

Qmail File directory is the sub-directory where your .QWK files
are kept. NEWFILES.DAT files in the .QWK files, can be extracted
from these files and imported into the master database. Other
.QWK files in other sub-directories on the same drive can be
selected by navigating through the disk using the cursor. This
directory is used in the Unarc/Import Newfiles option.

Uncompress Program Directory is the sub-directory where your file
archivers exist. This is used in the Unarc/Import Newfiles
option, and in the eXtract function.

The BBSee Output directory is the working directory BBSee for
storing temporary files including those created by the Search
Word function, and possibly by DOS Shells. These files can be
large so the drive where this directory is located should have at
least .5MB free. Also, many BBSee output file are created in
this directory. See Section on the output directory files for
further information.

The Virus Scan Directory is the directory where the program
SCAN.EXE resides. This is used if you enable the eXtract Scan

Page 9

BBSee Version 2.4

The Upload Files Directory is the directory from where you
usually upload files.

The General Directory is any directory that you would like to pop
up in the File Manager.

The Archive Viewer Directory is the directory where your archive
viewer is located. The Viewer name is configured below this.
The Viewer could be a program like FV which writes to the screen
or it could be a stand-alone program like SHEZ, Arc Master, ZRAY,
or VPIC. If you wish to use a stand-alone program enter Y in the
Shell program field. Note the BBSee Shell programs can be
configured to act as multiple viewers for cataloged files if so
desired. See section 3.8 for further information.

2.4 Tag Files Facility.

The Tag files directory is where BBSee places the download and
upload files from the tagged file option. The extension field
should contain the extension that will be appended to the output
file that BBSee creates, depending on whether the upload or
download option was selected within BBSee. A blank is possible.
The first part of the filename will be the name of the BBS. This
feature is intended to be used with automated file/mail
management programs, and telecommunication program scripts.

Q - QMM/Access*
L - Liberator* (Telix)
W - CatCalls - Wildcat 3.0 (Telix) * marked automater types
2 - CatCalls - Wildcat (Telix) use BBSee conference
S - Telix Square (Telix)
I - Intellicomm*
B - Boyan* (Lee Breeden/R. Cronenwett scripts)
R - Robocomm
C - {COMMO} (Chuck Seyboldt's macros)
A - ASCII Filenames (generic ASCII filenames only)

Note that the Upload and Download file extensions need to match
those specified for use with your program. I will attempt to add
support for additional Upload/Download types if the appropriate
file specifications are provided to me.

R. Cronewett's WildCat! scripts for use with Boyan require that
you configure the BBS type as WC3 instead of AUT.

See Appendix I for special instruction for use with Robocomm.

Page 10

BBSee Version 2.4

2.5 Output Directory files

This screen contains the default filenames for the files, other
than the databases, created by BBSee. All of these files are
placed in the output directory. If you don't want to create a
file for any of these options, specify NULL as the filename.

The Added file is the filename used as output of all new files
added to the database. This is useful when batch updates of
files are undertaken, however for the most part I recommend NULL
as the device for this option when you are importing ALLFILES.LST
types, as it causes a lot of disk overhead. You should however
enable this option when you are adding from NEWFILES.DAT or daily
imports, and use the List/tag mode to tag new files.

The Added file will also have a list of files that are modified
for higher priority BBS. In this way you can see files that you
may have chosen to disregard on a long-distance call BBS, but
sounds more attractive, for a local call. These modifications
are indicated with the marker on the description.

You can also choose to have BBSee check your catalog before
adding files to your Added file list. This is configured using
the Search Catalog for adds option.

The Discard file is the name of the file that is to contain
information about files that were discarded during the import
process, for each of the various rules used in the import. Note
that this file is opened in append mode. I suggest that you use
the NULL device once you have a reasonable idea of how data is
imported. While learning BBSee I suggest that you create this
discard file, and examine it to see what BBSee rejects, until you
are satisfied with your exclusion words list.

The Duplicate file shows filenames and descriptions when there is
potential for a description change. A '>' indicates that a
description was replaced. This file should be watched as the
potential exists that file descriptions will not match the
filename that is duplicated. Filenames with 3 or fewer
characters in the filename should normally not have their
descriptions replaced, as the short filenames are often not
unique, especially when you access many BBS sources. It is
possible to configure the default for duplicate replacements from
0-9 (in the Misc section). The smaller the number the more there
will be a chance of duplicates occurring.

The Word Search Output file is the file which BBSee creates when
you output the results of a search or the output of tagged files
to disk. This is a PCBoard-like file with the inclusion of the

Page 11

BBSee Version 2.4

BBS and file catalog locations. Output to this file will be
added to the end of the file if the indicated file is found.

The Catalog files are the output files chosen in the output of
the floppy catalog filename and volume options. There are also
.DUP, .VER and .BBS extensions possible. See Section for
further information.

The Cross Reference extension is the extension used in making a
BBS cross reference file. See Section 7.4 for further

The floppy description file is the output from the Describe

Floppy option of catalog. See Section 7.3 for further

The usage log is a facility that allows you to log certain
activities within BBSee. The main purpose is to log errors and
additions to the database, for those people that want to monitor
database growth.

2.6 Single word exclusions,
Paired word exclusions,
File extension exclusions and
Required words.

These options allow for processing of file descriptions based on
certain words, (actually strings) so that the file can either be
included, or excluded from addition to the BBSee database. If
you include and exclude words 'smartly' the size of your database
can be greatly limited. Note, if for example, you specify to
exclude the word 'windows' (you do not want all files associated
with Windows v3.1 to be in you database); should you later start
running Windows and want files and accompanying descriptions to
be included, you must reread in the entire original file list(s).
A certain amount of thought, both about your present and future
computing needs should be done before deciding on words to
exclude and include.

Some strings may be better specified as words, ie you may wish to
exclude descriptions with the word BMP, forgetting that it is
included in some words ( IBMPC ). To include an entire word use
the leading and/or trailing spaces by enclosing the word with the
space in double quotes. ("gif ", " pcx "," bmp", etc.).

2.7 Source / BBS Board Selection

The third part of the configuration is a list of the BBS names
that you plan to include in the list. The order of these names
is important. See the section on file duplication for further

Page 12

BBSee Version 2.4

information. You can also include the name of a friend as a 'BBS'
if you intend to share file lists. The Format and Options
selections are used in processing non-PCBoard files. See Chapter
3 and Appendix F for more information.

For PCBoard systems, if you do not configure the Options (and you
shouldn't) you can select a default conference for use by a file
automation program if desired.

Note that in the unregistered shareware version of BBSee, if you
have more than 3 BBS/Source selections configured you will
experience a delay on start-up. Once you register BBSee you will
be give an activation key which provide unrestricted access.

2.8 Area/Conference Support.

This option allows you to assign BBS Conference and Area numbers
when a file is imported. The BBSee numbers (0-15) correspond to
data input in the second column which is the actual area on your
BBS. The output in BBSee and in download files will be the
entered data in column 2.

In the third column you may enter the conference name. This will
allow you to select the name from an F2 picklist in BBSee rather
than by the BBSee number.

Note that for PCBoard files the default conference number can
setup in the BBS/Source section.

2.9 Catalog Configuration

Default Drive: This is the default cataloging drive, A or B.

Default Category: This is the default category assigned when a
volume is cataloged. It can be changed using the View Catalog
D(etails) option.

Catalog within archives: BBSee can be configured to catalog
within archives if desired. Enter the Y(es) option of Catalog
Within Archives, to catalog every filename within the archive,
with the exception of READM*.* files. If you have a restricted
need type C(ustom), and if you don't want to catalog within
archives type N(o). There is also option P, which causes BBSee
to prompt you to catalog within every archive file it finds. The
various options can be changed temporarily while running BBSee.

If you use the C(ustom) option to customize cataloging within
archives, various options are available to you, in a secondary
window. This feature allows you to restrict the filenames that
are cataloged within archives by specific extension. The Archive

Page 13

BBSee Version 2.4

Extension selection allows you to choose archive cataloging of
standard extensions. The standard extensions are .ZIP, .PAK,
.ARC, .LZH, .ARJ, .COM, .EXE, .SDN, and .GIF. Filenames in
imbedded archives will not be cataloged. In addition, OR
instead, you can specify file extension(s) that you would like
cataloged by adding the specific extensions (without the dot).

Extract Descriptions: You are able to select automatic extraction
of the BBS description files FILE_ID.DIZ and DESC.SDI from your
files while cataloging. Enable this feature by entering a Y(es)
in extract descriptions. More and more authors are including
these files.

Find 4DOS Descriptions: Enabling this option will take catalog
descriptions from 4DOS/NDOS the descript.ion file.

Recatalog: There are two methods of cataloging; cataloging entire
disk contents and cataloging updates to disk contents. The major
difference between the two options is that in update mode, BBSee
will not do the normal uncatalog/catalog performed by other
programs, it only updates the database on the specific filename
changes. Minor limitations on the update exist when a cataloged
file 'changes', but its name does not change. For example, data
changes (size, dates) for a filename, will not cause the database
to be modified, nor will any changes in the contents of archives.
Manual uncataloging and then a re-catalog will correctly handle
these situations.

2.10 Fill Configuration

The Fill setup options that will require configuration are:

Default category - {99999} - This is the category used in the
Fill process as a default, and which is temporarily reset using a
Fill. A normal disk when cataloged is given a category of 99999.
If this disk is updated using a Fill category BBSee will update
the volume category.

Update BBSee Catalog - This will cause disks to be cataloged
during the Fill.

Create Volume Label - This option will cause disks with no label
to automatically be sequentially labelled using the selected
label template. See Section 5.3.1 for further information.

Perform Validity Check - This option will cause a 32bit CRC
check to be performed on all copies to the floppy disk, including
those done in the File Manager. Using this option is highly
recommended, as I have found DOS (and Verify) to be unreliable in
determining faulty diskettes.

Page 14

BBSee Version 2.4

Mark Filled Files - This option allows BBSee's Fill to use the
archive bit as an indicator that a file has been successfully
copied to disk. When this option is enabled, it is possible to
interrupt a large Fill, and come back to the same point later on.
It is a good idea to use the File Manager to ensure that the
files in the directory you wish to Fill from have their archive
bit set (Upper case) properly before starting the Fill. Note
that many programs, not only BBSee, including the DOS BACKUP and
ATTRIB commands, will modify the archive bit. After the Fill it
is possible to use the File Manager to mark and delete the Fill
'copied files' (showing in lower case) from the hard disk, if

2.11 Function Keys

To run programs using the BBSee Shell facility you need to
identify the program name (format DRIVE:\DIRECTORY\PROGRAM ie.
C:\DOS\FORMAT.COM), and optionally the DRIVE:\DIR where you would
like to run this program from.

The reset video commands, no swap, and command line parameters,
allow you to configure other shell characteristics. Reset video
returns the video back to 80x25 if it has been changed by BBSee.
Setting EMS/XMS swapping to N(o) will cause BBSee to swap to disk
rather then EMS or XMS, which will reserve EMS/XMS memory for the
shelled program. If EMS use is disabled this will have no

The Command line parameters are those commands you might have
typed if you had entered the program on the command line
ie (for the FORMAT example ) a: /n:9 /t:80

A special command line parameter {CATALOG} is available which
will allow you to pass the filename of the currently selected
catalog file to a program. If this option is used no other
parameters are possible. This advanced features allows
configuration of multiple file viewers and graphic display
utilities, in addition the to normal configured Viewer.

2.12 Volume Templates

This option allows you to create Volume templates for use in
BBSee's automatic Volume labelling. (see section on template
labelling). The first template is the default template, the
second set are for selection from a pick list.

2.13 Analyze Directory

This option provides a means to create a personalized batch file
that can process files on your computer in any manner you wish.

Page 15

BBSee Version 2.4

The ~ macro allows substitution of default directory information
into the batch file when the batch file is created. This
information comes from other options within BBSETUP.EXE. NOTE
that lines two and three of this batch file ONLY apply to files
with the .ZIP extension.

There are two files created in the Output Directory for this
option, which are set by the top two fields on this screen. See
Section 7.6 for a detailed explanation of how these files are
created and used.

2.14 Hardware Installation

2.14.1 Video Installation

Various colours, and video modes options are available to the
BBSee user. This section details these options.

BBSee is written independent of the normal 80x25 screen, and if
you start BBSee, with other configurations BBSee will use it.
Having less than 70 columns would be for the most part
unsatisfactory. BBSee should work with Ultravision extended
modes if they are enabled before BBSee is run. Note that if you
desire to use custom VGA fonts with BBSee, you should only run
BBSee in 80x25 mode, or change the video before running BBSee.
If you don't BBSee video resets could 'lose' your font when you
exit to DOS.

This Change Colours option will allow for setting up colours
within the various menus/windows in BBSee. In the shareware
version you are able to explore this feature, but it will not
save changes for any option except the Search Window. The
registered version of BBSee provides further colour configuration

If you a have a CGA that produces flicker, flicker elimination
can be obtained by instructing BBSee to wait for video retraces
before writes. Mono mode disables colour settings for use with
monochrome monitors. Enter a Y in the appropriate field to
enable these selections.

If you have a VGA monitor, BBSee can generate screen
combinations, other than 80x25. One 'interesting' mode, the 90
column mode, provides a lot more information on the screen with
very little loss of readability. Although SVGA is not required,
this mode has not worked on every VGA card/monitor combinations.

Various screen row (line) lengths are available including 21 (a
slightly bigger font), 25 (normal) and 28, 43, and 50, and 60 row
modes. Additionally the 50 row mode can be set to only function

Page 16

BBSee Version 2.4

during a word search, to allow more data on the screen at that

It is also possible to use special mode(s) available on many VGA
cards. Refer to your documentation, and if you find a mode you'd
like to try, use 0 as the number of screen lines and set the DOS
variable BBVMODE= to the desired mode. Note that most VGA card
documentation manuals specify the non-standard mode in
hexadecimal notation, and BBVMODE would be the decimal

For special environments, DesqView and Memory Commander (RSIS)
video specifications are followed to allow 'fast' video. Also,
BBSee will not attempt to switch video modes if Windows 3.X is
running, although it will accept the Windows 3.1 50 line mode.

2.14.2 EMS Support.

BBSee will use expanded memory for some functions to reduce
memory requirements. The savings are most dramatic in the word
search (although EMS memory is slightly slower than regular
memory). Use of EMS is configured on and off in BBSetup. Use of
EMS can reduce memory requirements by about 70K and speed up
certain shell related functions. For EMS to work with BBSee you
must have the full 64K EMS frame.

2.14.3 Mouse Support.

BBSee has full mouse support which can be configured off or on.
The mouse can be either an arrow with fixed colours, or a block
cursor with screen related colours. See Appendix E for
information on using the mouse in BBSee.

2.14.4 Sound

There is an option to configure 'completion' sounds on and off.
Error sounds will remain if sound is configured off

2.14.5 Clock

If you are using BBSee in a multi-tasking environment such as
Desqview, Windows, or OS2, you may wish to disable the clock to
reduce BBSee's call to the system.

2.15 Miscellaneous

Under this option there are data fields that are used in various
functions of BBSee. The file date option excludes files older
than a certain date from being added to the database. This

Page 17

BBSee Version 2.4

exclusion date default is not permanent, it can be modified in
the File menu selection of BBSee, under the "Modify Import
Options" sub option. Although you may want to specify that older
files, such as pre-1986 be excluded, you must remember that some
sources have files dated as early as 01-01-80. A suggestion is
to browse through the lists you wish to read into BBSee and
determine if any of these files exist.

The duplicate length is the minimum length of filename used by
BBSee in determining if descriptions should be replaced for
matching filenames from various BBS's. See Section 3.1

The 4DOS description length is the file of length of the output
4DOS description length.

SCAN extracts is the option to use if you plan to have BBSee
perform a McAfee SCAN.EXE of files that you 'eXtract'

The effective cps is the cps rate used to estimate the download
time for marked files. You may wish to change this to match your
effective modem speed (ie 270 for 2400 baud MNP, 1650 for a USR
HST). Of course, the BBS you are calling will have to match your
modem speed.

The two locks configure the File Detail Window in the Search Word
and List/Tag windows on and off (using Y(es) and N(o).).

2.16 Print Order Form.

I hope this is the most used option! This will create a BBSee
order form, which you could mail in for registration. You can
have as the destination any DOS device (PRN,LPT1,LPT2, COM1) if
you wish, although no checking for device availability is
performed. See Appendix A for further registration information.

Page 18

BBSee Version 2.4

Chapter 3 File Function

The heart of the BBSee program is a master database of file
descriptions that can come from many sources. File description
listings can be imported from BBS directory listings, QWK format
files, telecommunication program screen captures and log files, file
output from BBSee itself, and they can be entered manually.

3.1 File importation

Importation is the method of bringing a file list into BBSee and
processing the listing, line-by-line, into a BBSee database
record. Because of the many, many different list types, it is
impossible to guarantee that all files in a list will be

BBS file listing, are incorporated into the database using a
sequential read of a DOS text (ASCII) file, each line being one
record. The layout of a file description 'record' is one that I
have adopted based on viewing PCBoard file description listings.
Anyone having definitive specifications is encouraged to forward
them to me as described in Appendix A. The file "record' layout

that BBSee expects is:

filename position 1-12
spaces position 13-14
filesize position 15-21
spaces position 22-23
date position 24-31 ( format mm-dd-yy )
spaces position 32-33
description position 34-80

Any lines that follow this original record with blanks in columns
1-33 and text in columns 34 - 80 are treated as continuation of
the description record. The pipe character | is allowed to
indicate the start of a continuation line if it is the first
character of a line.

An asterisk in position 32 is allowed. This sometimes indicates
a new file in a BBS on-line search.

Data is incorporated into the database from the parsed text file,
using the exceptions input in BBSetup. The rules built into the
BBSee import logic function as follow:

- Filenames must be uppercase.

Page 19

BBSee Version 2.4

- The character set is limited to the extended ASCII
characters between 32 and 175. No allowance is made for
code pages.

- If the file contains one of the required words it is
considered mandatory. This file will be added in all

- Records with a description containing two paired exclusion
strings, will not be entered into the database.

- Any file description continuation lines that begin with the
words 'Uploaded by .....' or 'Last filedate in .ZIP ..' or
containing 'files - New:' will be stripped out.

- Ending punctation character . and ! are removed.

- Catalog only descriptions always replaced.

- Files descriptions beginning with (CRS) will have the (CRS)
stripped. the 'Last Revision Date...' string for CRS files
will also be stripped.

Note that if you manually create a PCBoard-like text file using a
text editor, you should ensure no tab characters are in your
output document, as they can make it appear that the file meets
specifications, when it truly does not.

Another program supplied in BBSee, IMPORT.EXE, is intended to
assist in the automatic creation of file lists, by parsing non-
standard file lists into the PCBoard 'standard' that BBSee uses.
In general, if you don't know if a BBS is a PCBoard type, run the
import file through the import program to see if it meets the
PCBoard column specs. General use of this program is outlined in
Appendix E.

If this non-standard BBS file can be converted automatically
using IMPORT, BBSee has the capability of performing this
conversion when a file is imported. (BBSee can presently import
more than 50 different BBS list formats). Specify in BBSetup,
that the file type is type AUT, (for automatic), rather than PCB,
and the appropriate option (see Appendix E). If the BBS requires
a manual use of IMPORT, specify ASK for the file type, and BBSee
will prompt you before importing the file.

Note that the nature of the database will not allow automatic
determination, and indication of various file areas and
conferences on the BBS. This is extremely difficult to detect
automatically, and so the feature is not available. You can

Page 20

BBSee Version 2.4

however, set a limited number of conference numbers prior to
doing an import.

3.2 File Duplication

There is a mechanism in place to prevent the addition of
filenames with different descriptions, sizes, times and
extensions into the master database. Filenames from description
listings ( excluding extension) are compared to those already in
the database and if the filename is found certain database
modifications may take place. PRIORITY will be given to the BBS
names higher on the configuration list of sources (the lower
number). The extension, file date, and file size stored in the
database will be that of the highest priority source.

The same is true of the description, although if the filename is
more than the configure duplicate minimum (default is three
characters long), the description having the most characters is
stored in the database, regardless of the source. No method
exists to eliminate this problem, or to prevent replacing file
descriptions, without user prompting, which is not desirable.
This number can be changed temporarily if desired, in the File -
Modify Import Options window, or permanently in BBSetup.

3.3 Uncompress and Import NEWFILES.DAT

Users of Qmail, MarkMail, Rosemail etc with offline mail readers
are probably aware that it is possible to browse all files new to
the BBS from a previous date, offline. I am not going to try to
explain how these programs work, rather I will explain how BBSee
handles the importation of the new file information contained
within them. If you plan to use a BBS regularly, and it has the
option of using an offline mail reader, usually configured as
doors, I suggest that you investigate them.

Contained in most .QWK files downloaded with the 'scan for
newfiles' option of the mail door turned on, is a file called
NEWFILES.DAT. BBSee will allow for a semi-automatic import of
this file description list into the master database. Within
BBSee, after selecting the Unzip option, use the cursor to
select the .QWK file that you wish to import into the database.
After this, select the BBS source of this file. The file
description records will then be entered into the database. This
of course assumes proper configuration of the mail and archive
file directories.

If your BBS has this capability, regular use of this feature will
keep your database up-to-date, and eliminate the need to
regularly download the entire list of files added to your BBS's.

Page 21

BBSee Version 2.4

BBSee will automatically sense if the .QWK package has been
compressed with ZIP, ARC, ARJ, or LZH formats and will extract
accordingly, if the archive utilities are configured as indicated
by BBSetup.

3.4 Modify Import Options

This option allows you to temporarily change specific options
related to file imports. The various import-output files can be
modified, and exclusion dates and duplicate lengths can be

There is also an option to configure a BBSee conference number.
Before loading a specific file which you know relates to a
specific BBS conference, enter the BBSee number 0-15 that relates
to that conference. A pick list is available using the F2 key.
At the end of your import this option will be reset to BBSee
conference 0.

A final option is available to import specific description files,
regardless of length. The purpose of this is for customized
lists containing information that you do not wish to be ignored.

3.5 Create Record

Using this option it is possible to create a master database
entry. The best use for this option is to add unknown files,
personal files, and obsolete files to the database so that the
floppy disk catalog can also be updated. This file description
is not subject to any of BBSee's import 'rules'.

3.6 File Manager

BBSee includes a simple disk management facility under the main
menu File option, the File Manager. It is also available
globally using . It is not meant to compete against
other commercial file managers, but it could assist you while
using BBSee.

Most of the functions, are self-explanatory. Some points of

- The lower case names are files that have their Archive
attribute bit set. The Catalog Fill can make use of this

- Files copied to a floppy using File manager, will have their
archive bit removed if Fill - Mark Archives is Enabled in

Page 22

BBSee Version 2.4

- All copies, and moves to a FLOPPY disk will use CRC checking
if the Perform Validity Check option is enabled in BBSetup
(under Catalog/Fill options).

- The eXtract option functions as described in Chapter 1.

- Cataloging of floppies is available in the File Manager.

- File manager will copy over existing files.

- File manager will not try to copy one file if there is no

- A Move onto another directory on the same drive is treated
as a rename, to function quickly. This is one good reason
for keeping up/down/archive directories on the same
partition when they are going to be used for cataloging.

- The V command will bring up a program viewer. This can be a
standalone program for archives (SHEZ, AM, ZRAY etc) graphic
viewers (VPIC, VUIMG, GWS etc) or it can be program like
FV.COM which displays to standard output.

3.6.1 List file

Within the File Manager there is a list command designed to
browse ASCII text files. The commands available within the
lister are:

Cursor Up/Down/Left/Right, Home, End, ,
(scrolling full left and right)

F Find text
N Next (find Next occurrence of text)
Z Zoom List to full screen.
T This is a special function, in that it allows you to enter
BBSee's List/Tag mode during a normal text file 'list'. The
primary use of this mode is to browse the PROGRAMS.NEW file
created during an import and then tag selected files for
download. This mode can be enabled on a 'Zoomed' list.

There is also a configuration option in BBSetup , as in the
Search Word option that enables a Detail Window within the
List/Tag mode to show possible BBSee information on a filename.
If no BBSee description information is found for the file, this
window is left blank.

Page 23

BBSee Version 2.4

3.7 Floppy Directory

This option allows you to see a list of all files on the selected
floppy, including all sub-directories, with one entry. The
filenames shown on the left have descriptions in your BBSee
master database, the filenames on the right would, if you
cataloged this disk, be cataloged with description 'catalog
only'. This option is available anywhere in BBSee by entering

3.8 BBSee Shell

It is now possible to shell to specific DOS programs by
function key , through a pop-up interface, under
File option BBSee Shell, or through almost anywhere
in BBSee.

If you have enable the {CATALOG} command line parameter in the
Shell setup, the current catalog filename will be passed as the
parameter to the shelled program.

Note that if you change video modes while you are in the shell
BBSee may have to exit to DOS when you return, if the previous
video state cannot be properly restored.

3.9 DOS Shell

This option allows exiting to DOS to execute many DOS programs
and commands. Do not run any TSR's, reboot, or turn off you
machine while you are in the shell. To return to BBSee you must
type the command EXIT at the DOS prompt. It is better to quit
BBSee and come back if you must leave the program for a long
period of time.

If you use BBSetup in the shell, the changes you make will not
take place, until you quit BBSee and rerun it.

Page 24

BBSee Version 2.4

Chapter 4 Search Functions.

Search for words and/or filenames. Outputs the filename if found, and
if the filename has been cataloged on disk, the label and directory of
the cataloged disk will be displayed. Graphic resolution for
cataloged GIF, and JPEG files will also be displayed.

4.1 Word Search

This option allows you to search for strings within the database.
Because of the nature of the search the most unique word should
be in the primary word field. The primary word is searched in
all filenames and description.

The search on a word continues until the entire database is read
or a complete screen of information is displayed, at which time
the filename will be highlighted with a selection bar. It is
then possible to select filenames by moving the selection bar up
and down using the cursor. Full database information on the
selected filename is available by typing the letter D (for
Detail). will abandon the search at this point. Also see
the TAG option.

Under the Search Word option BBSee saves all output for later
review, [in a file called BBSCREEN.TMP]. You can PgUp and Down
through a file as well as use ^Home and ^End to get to the top,
and last screen of the present search.

Typing will lock on the Detail Window until is pressed a
second time. The default Detail Window lock on, Y(es) or N(o),
is configured in BBSetup.

The BBSee catalog eXtract, Copy and View features are
available in this window. See Section 5.10 for further

4.2 Filename Search

Using this option will allow you to perform an indexed search on
the filename. This is by far the speediest search, if you have a
pretty good idea of the filename, or you want to look for various
versions of a particular file. This is equivalent to a PCBoard
ocate without requiring the trailing *.*.

To 'browse' the file near the search, the page/cursor up and down
keys can be used. A file also can be T(agged), and U(ntagged)
using the or keys. See tags for further information.

Page 25

BBSee Version 2.4

Typing will open up an edit window for the current

The BBSee catalog eXtract, Copy and View features are
available for retrieved files. See Section 5.10 for further

4.3 Output Search List

This option creates an ASCII listing of the files that meet the
same search criteria as an on screen search. This listing is in
PCBoard like format with the addition of the BBS source, and any
disk cataloging information that you may have. This listing can
be imported into BBSee. If this file exists it is opened in
append mode.

4.4 Show All/Show Catalog/Show Uncat'd

To toggle the search results from displaying the master database
description information, to displaying only descriptions
contained in the floppy catalog, to displaying only descriptions
of files you have not cataloged, hit enter on this option.

4.5 Local BBS Searching

Under the BBS/Source option it is possible to restrict searches
to specific BBS(es), using what I call a 'Local' search. An
asterisk will indicate that you are running a 'local' search. To
disable the 'local' search hit enter on the Show option. The
defaults for the 'Local' BBS's are established in BBSetup.

4.6 Catalog File Searching

The Main Menu Search option provides a mechanism to search for
catalog files using 'words' within descriptions as detailed
above. However there are also additional search options in the
Show Catalog/Archive file section 5.8 which provides even more
flexibility. This includes the S(can) option which provides
'normal' access to file extensions.

Page 26

BBSee Version 2.4

Chapter 5 Catalog Function

The purpose of these functions is to improve disk maintenance of
downloaded files, and other files that you accumulate and wish to
store on floppy. If you accumulate a large number of files on your
hard disk, especially from downloads, that you do not want to delete
but you wish to remove for later retrieval, using the various
cataloging features of BBSee should drastically reduce problems you
may have finding them.

Cataloging within BBSee is designed to be both powerful and simple.
After initial configuration, it can be as simple as running BBSEE /A
at the command line to catalog a disk. You can also configure BBSee
to do just about everything any other catalog system on the PC market
can do.

The cataloging system uses three database, volume (info. on the entire
disk), catalog (file data on each file on the disk) , and archives
(file data within arc, arj, lzh, and zip files). I could add other
archive types, but I will wait to see what you users demand. The
catalog structure is tied to the master file description database for
storage of the 512 character descriptions, but a BBS file list is not
required. However using BBS lists, or stealing descriptions from BBS
lists will make finding archive files that much easier.

One difference between BBSee and other catalogers is that BBSee uses
the DOS 4+ disk serial number in conjunction with the volume label to
produce a 'unique' identifier for disks. BBSee will not prompt you to
update a serialized/labelled disk, as the chance of error is reduced
to what I consider to be acceptable. If the disk does not have a
serial number, prompting will be required as with other programs.

BBSee will automatically extract GIF and JPEG resolution information
from .GIF and .JPG files. If the GIFLITE string is left in a .GIF,
BBSee will also identify it in the resolution ( 640 X 480 normal 640 x

5.1 Catalog Disk
5.2 Uncatalog Disk

Both of these functions will work by specifying the drive to be
cataloged, and inserting the disk if it is removable media.
Additionally a disk can be uncataloged by volume label name.

A disk can be cataloged, if it meets two criteria, a) the disk
has a volume label and b) a matching volume label has not already
been cataloged. (Note that in BBSee the volume label is not case
sensitive). If files exist on the disk that do not have
descriptions in the BBSee master database, you may wish to create
a 'Floppy' description file, edit it with the proper

Page 27

BBSee Version 2.4

descriptions, and import this edited file into BBSee, with an
unknown category. If no descriptions from a file exist an entry
with the 'Catalog only' description will be entered into the
master database. If you must catalog a disk without a label see
section 5.3 on Pseudonym cataloging.

If you try to catalog a disk that has already been cataloged,
BBSee will check the serial number and if they match, it will
automatically catalog the disk for you. If they don't you will
need to Uncatalog the disk manually.

If the disk you are using does not have a serial number or you
are using DOS older than version 4, BBSee will ask if you want to
replace the existing catalog entry for that label. Be careful
when you physically label your floppies, as it is easy to
overwrite your catalog database entries if you use very common
volume labels.

5.3 Pseudonym Cataloging

Pseudonym cataloging allows you to manual assign the 'label'
which will be used by BBSee to identify a disk volume. The
pseudonym is independent of the disk label, and so no volume
label is needed on the disk for this function to work.

Normally the standard method of cataloging should be used, as the
volume label is a very easy method of naming unique disks. The
naming convention for pseudonym labels should be distinct to
assist you in their identification. However there are times when
want to catalog blank disks you do not wish to label, or disks
which have the same label you do not want to change where this
feature will be of necessity.

Pseudonym cataloging can be used to catalog individual sub-
directories on a disk. Use the DOS SUBST command to identify the
sub-directory, and pseudonyms to identify the SUBST'd drives when
cataloging. This method should NOT be used when running
Microsoft Windows.

BBSee will still maintain the serial number (if found) for disk
cataloged with a pseudonym for update purposes, so a small level
of protection against incorrect pseudonym updates is available.

5.4 Label floppy

This option allows you to label floppies without exiting to DOS.
If there is no volume label on your floppy, a default unique
label assigned by BBSee will be displayed. You can edit or
change this if you desire.

Page 28

BBSee Version 2.4

If a volume label exists on a floppy that you are labelling, the
existing label will be shown in the input window. If you desire
to use the automatic template label feature described below, you
must first delete any existing label, by inserting spaces, and
then re-enter the label function again, to get the proper default

5.4.1 Label Templates

The default layout of the default label name is established in
BBSetup. There are two components, the name component and the
number component. The name component is up to seven characters,
the number component is up to 99999. They must be separated by a
space. BBSee will increment the number component automatically to
allow for the unique label, sequential. BBSee does not modify

the BBSEE.CFG file in performing this function, so holes can be
found. You cannot label a disk in BBSee with a template name
that is the same as a cataloged floppy.

If you enter a volume label manually which uses the template
formula described above, automatic increments of the number
component based on volume database, will be made, without you
specifically configuring the template. Subsequent calls to the
label function will give you the next available number of this
new template. Remember to include the number of leading zeroes
you feel will be appropriate.

A pick list of possible label templates is also available, by
hitting function key F2, if the templates have been configured in

5.5 Make Catalog Report

Filename/Volume Reports

These options create a list of files you have cataloged, sorted
by either disk volume, or filename. This list is useful as it is
output in a format that BBSee can use as input. This allows for
sharing file lists with friends and other user groups.

Volume reports for a single BBSee cataloged volume are available
in the View Catalog option.

Duplicate/New Version/BBS Version Reports

These useful reports are designed to give you a list of possible
duplicates and new versions of files that you have cataloged.
The duplicate report can either be produced by filename, or by
disk volume name, the choice being set up on the Report Options

Page 29

BBSee Version 2.4

The two version reports use logic to determine if you have
'different' versions of the same program, or that possible new
versions exist of files you have already downloaded. The logic
is not absolute, but it is still beneficial. Using the New
version report you can, much like in the duplicate report,
determine obsolete files you may have. The BBS version report
identifies files that you have, that also have newer versions in
your imported BBS lists. This helps determine two things, files
you might have missed in BBS lists and should download, or files
that probably should be deleted since you didn't like it enough
to download a newer version.

Multi-Column Report.

This catalog report is a list of filenames with their
corresponding Disk Label output in either filename or
label/filename order. The number of column and the sort order is
setup in the Report Options selection.

Extension Report.

This report is a catalog report sorted by file extension, or file
date respectively. Date order can be ascending or descending as
setup in the Report Options Selection.

Modify Report Options.

This feature allows various methods of customizing features in
BBSee's report functions. Options include the capability of
outputting BBSee information (Source, Catalog information, GIF
resolution). It is possible to output a 'Quick' catalog report
which is a fast report created with no descriptions. Also it is
possible to configure a report which will exclude all files with
a 'catalog only' description.

Page 30

BBSee Version 2.4

5.6 Fill

One very useful feature of BBSee's cataloging function is the
Fill option. What this option does is allow you to copy files to
floppy disk, in an optimum manner, much like other programs,
(FILL, ICOPY, DISKFILL), but BBSee will catalog after the Fill to
save disk swaps, and will catalog archive contents and extract
description files from the hard disk rather than the much slower
floppy disk.

When Fill is started you can enter volume and/or category
information. During a Fill, BBSee will determine if you have the
free space on existing cataloged disks with the indicated volume
template or category and provide you with name of matching volume
names so that you can optimally Fill existing disks before each
disk change.

5.7 View Catalog

This option provides a visual 'directory' of your cataloged
files. Hitting enter on a highlighted volume will provide a file
list on the item selected by the current cursor position. The
next enter will provide the description contained in the BBSee
database for the highlighted filename (All the options available
in the Search Filename option are available to you on the

To change the selected volume you can navigate in various ways.
Cursor up/down, page up/down and F(ind) and N(ext) options are
available. Find will search both the volume name and any
description that you may have provided to get to specific volume.
Next continues the search from the current location.

If you wish to view archive file contents or graphic resolution
information, the D(etails) option is available when the cursor is
on a filename.

If the cursor is on a volume, additional keyboard options are
available. These are:

- E(dit) to change the description or category for this file.
- O(rder) will output the list in various sort orders,
including, label name, space available, category and disk
number (order cataloged).
- R(eport) to create a disk report MYBBSEE.VOL for highlighted
- S(ummary) to create a summary of statistics for your
cataloged files.
- X, C and V. These are the eXtract, Copy and View functions
explained in detail in 5.10

Page 31

BBSee Version 2.4

5.7.1 Volume Categories.

Using volume categories to identify disk contents can be a useful
means of grouping disks with similar contents. The O(rder) and
D(etails) option above make use of this feature. As well, when
you are in View Catalog, function keys F2 thru F9 can be used to
set categories 20000 thru 90000 respectively. You can assign
these eight categories as you see fit. If you hit one of these
keys by accident, immediately hitting F10 will restore the
previous category.

Future releases of BBSee will make more use of the categories, to
limit catalog reports, and group items. Additionally,
categorization will be added at the file level for even more
control over your disk catalog.

5.8 Show Catalog/Archive Files

These options provide on-line browsing and searching of all
catalog and archive files respectively, using a DOS DIR-like
displays. The Show Catalog files provides have access to the
eXtract, Copy and View function explained in section 5.10.

To change the selected filename you can navigate in various ways.
Cursor up/down, page up/down and F(ind) and N(ext) options are
available. Find and Scan allow you search for the filename that
you may have provided. You also have the option to move by
Shift-Letter to go to the first file beginning with that letter.
and manoeuvre you to the top and bottom of
the catalog list.

Hitting on a file will bring up the Browse File
description for the current file. Hitting D(etail) will provide
any archive contents for the current file. Note that for the
Show Archive file option, the description and archive contents
will be for the 'parent' archive file, not the highlighted file.

5.8.1 Find Files

When you hit the letter F(ind) you are provided with direct
access to the File Index, as in the Search Filename option. The
difference is the search only displays cataloged files. Normally
you should use this option with no file extension. The search
always starts at the top of the database.

5.8.2 Scan Files

Entering a S(can) brings up an input field which leads to BBSee's
catalog regular expression search logic. Regular expressions are
special methods of searching for text regularly used in the Unix

Page 32

BBSee Version 2.4

world, but not normally implemented in DOS. However, almost all
DOS users have encountered partial regular expressions with the
use of the * and ? in DOS filespecs.

The Scan option allows you to use the * and ? as in DOS, and
provides additional flexibility in that the * can be used to
qualify search beginnings, ie. *SEE*.*

Additionally using the square brackets you can limit a search
range, ie BBSEE24[AB].* will search only for the A and B BBSee
files. You can also include all of the set or a range, ie [A-C].
The limit search can also work with a 'not' character (^ or !)
which means not in the range. For example, to search for older
BBSee files you might wish to search for BBSEE2[^4]?.*

Because the Scan uses file extensions in its search you must
remember to include it in the Scan. You can use a regular
expression in the extension separately from or in addition to the
filename. For example you may choose to use a *.ZI[^P] search to
find zipped files renamed by your telecommunication package.

The Scan will commence at the current location in the catalog
database. A Scan will be continued by using the N(ext) key. If
you have a very large database you may wish to use the Find or
Shift-Letter positioning to speed up access to files if you know
the first part of the filename.

5.9 Modify Options

This option allows you to temporarily configure various Catalog
and Fill options established in BBSetup on and off. These
options are: Catalog in Archives, Extract Descriptions, Update
Catalog, Create Volume Label, Perform Validity Check and Mark
Filled Files. See chapter 2 for further information.

5.10 Catalog eXtract, Copy and View.

These functions are designed to make it easier to manage
cataloged files. Using these options you will be able to perform
specialized functions on catalog files, without having to rekey
the catalog name. After typing the 'action' letter (X, C or V),
you will be prompted with the volume name, and when you accept
(your disk is ready), the function will be performed.

5.10.1 eXtract

The purpose of this function is to automatically extract an
archived files based on the archiver's extension (.ZIP, .ARJ,
.LZH, and .ARC extensions). To use this function type X when a
cataloged file is found in a Word of Filename Search.

Page 33

BBSee Version 2.4

The operation of this function is as follows. BBSee first
creates a directory in the BBSee output directory with the
filename of the archive, (without extension) and the files are
extracted into it. The location of the appropriate archive
utility must exist in the archive directory configured in BBSetup
for this function to perform.

Additionally, BBSee can be configured in BBSetup to automatically
run SCAN when you perform an eXtract. SCAN from BBSee uses the
/NOMEM and /REPORT option, so memory is not checked for a virus.
A file called SCANNED is created in the output directory when you
scan the file. BBSEE.USE is also updated to show the name of the
scanned directory and the return code from SCAN.

5.10.2 Copy File

This feature will copy a file from a cataloged disk to an input
disk, after you are prompted for the appropriate disk. The
destination disk must be different from the source disk.

5.10.3 View File

This feature loads the configured archive viewer using the
current cataloged file as the command line argument.

Page 34

BBSee Version 2.4

Chapter 6 Tag Function

When one of the various file searches take place, it is possible to
'tag' a file. This is done using the key. Files can be
individually untagged with the key. Additional options are
available in the Word Search Option, tags a screen of
filename 'hits', and tags all screens of filename 'hits'.
File tags are indicated with the character.
Tags can also be toggled with the or keys.

There is a limit of 300 tagged files at one time.

6.1 Delete tagged file

This option deletes all tagged files from the database. These
filenames are permanently removed from the database. You will be
provided with an option to add these files to the Deleted files
database so that they cannot be re-added (See Appendix F). This
feature is to ensure that you don't have to delete the same files
every time a complete BBS file list is subsequently imported, for
update purposes. This will also remove the tags.

6.2 Create download file

This option creates a download file in the tagged file dir. The
format of the filename is bbsname.{defaultextension} ie.
SYNAPSE.DOW. The layout of this file is based on the configure
automation program being used, and consists of a list of all
filenames that are found in the master database on the selected
BBS. This will remove all tags from the selected BBS, unless the
indicated bbsname has no tagged files.

Conference support is provided for Intellicomm, Liberator and
Access program/scripts.

6.3 Remove tags

The tag is removed from every tagged file. All file information
is left unchanged.

6.4 Create upload files

This option creates an output list of all tagged files, in a
format that can be edited to use with automatic file uploading
facilities of scripts Liberator, Access (QMM), Telix Square and
CatCalls, and Intellicomm, and macros available for Boyan and
{COMMO}. Direct area/conference support and support for Robocomm
upload agendas are not available at this time.

Page 35

BBSee Version 2.4

6.5 Output tags to disk

This option creates an output list of all tagged files in PCBoard
format. This file is opened in append mode.

6.6 View tags

This function gives you a display of all filenames you have
tagged during a search or in list/tag mode. By entering O(rder)
this list will be toggled between filename order, BBS priority
order and catalog label order. An estimate of file download time
is also presented.

Entering D(etails) allows you to enter the Search Filename
function at the current file, to assist in finding newer versions
that may exist on the database, which may not have been
identified. Because you are in Search Filename mode, access to
all of its options are available at that point.

Entering a S(ave) will allow you to save your tag list in the
current sort order to disk. Section 6.8 explains how to Load
this file.

Tagging and untagging files is also possible on this screen using
the enter or space keys. Any tags you remove will not take place
until you exit the window, or type R(edraw).

6.7 Edit Tags

This option allows you to edit the description for each file you
have tagged. Selective editing can be performed in the View tag
window, by going through the Search Word window, available as

6.8 Load Tags

Use this option to read a file of filenames, and then have them
automatically tagged by BBSee. Many uses for this exist
including, loading want lists, and special upload and delete file
lists (possibly an edited version of the Cross Reference file).

Page 36

BBSee Version 2.4

Chapter 7 Describe Function

The Describe function provides various means of using the BBSee master
database to assist you or produce speciality reports.

7.1 Input File List

This function allows you to read almost any ASCII text file which
has a filename as the starting word, and provide a PCBoard like
output-file containing the description found in your BBSee master
database for each file 'found'. The input file for this
function, can include such things as redirected DIR listings and
output from BBSee itself.

The main use of this function is to provide a means of either
giving descriptions of files you are giving 'friends', or getting
descriptions for files that you have stored as 'catalog only'.

7.2 4DOS Description.

This option creates a 4DOS/NDOS descript.ion file based on the
contents of your master description database, for the indicated
directory. This option will OVERWRITE any existing descript.ion
file so be careful, if you have entered some descriptions

7.3 Describe Floppy

This option allows for the creation of a file, in PCBoard format,
containing any file descriptions associated with files on a
floppy. If a file has no description in the master database, the
message, 'Not in BBSee catalog' is output to the file, in the
description. Since this file is in PCBoard format, if you edit
the 'not in BBSee catalog' message with a more appropriate
description and then import the file into BBSee, the master
database will have more valid data.

7.4 Cross Reference

A catalog cross reference creates a list of files you have
cataloged against a list from another source. The cross
reference output file is a list of differences. This should make
it easier to determine what to upload to other sources. Remember
to check a BBS before uploading to ensure that you don't upload
something they received since your last file import.

To make use of this file with an automated upload, edit it as
required and use the Load tags facility. This will provide a
list in Catalog label order if required, and also can output the
desired upload file for you.

Page 37

BBSee Version 2.4

7.5 Report Options

This option allows you to identify which reports you would like
to have output the BBSee Source and Catalog information. As well
a Quick Catalog Report Selection which creates catalog reports
with no descriptions, (which because of database access can be
significantly faster).

This option is available globally as .

7.6 Analyze directory

This option uses the batch file specifications created in the
configuration. Reviewing what I do, should assist you in
creating a usable analyze.bat file. These are implemented as a
batch file so that you may inspect the file prior to running it.
This sample could be further modified to meet your personal

The default configuration functions as follows. Files in the
download directory are compared with the description database.
If they are found they are added to a file, by default,
ANALYZE.BAT, that can perform the following operations when
executed. Note that in all cases batch options 2 and 3 will only
work for .ZIP files.

1. File is copied from download to archive directory.
2. README.ROS and READ_ME.TXT ( Rose Media ads ) are removed
from the ZIP file.
3. Comments are removed from the file ( This requires a
shareware package STRIPZIP).
4. Original file is deleted from the download directory.

I would recommend that if you approximate my archiving method,
that you also investigate programs such as FILL or ICOPY. These
will assist in copying files from this archive directory to
floppy disk, and they will maximize your floppy disk utilization.

A second output file from this option is a list of files that
were not found in the master database. A single file, by
default, NOTFOUND.ADD is created that meets the specification for
a BBS file listing. This file description can be edited with a
text editor (the description is initially indicated *Not Found*),
and can be imported directly into the database. BBSee does not
like the tab character so be careful when you use your text

Page 38

BBSee Version 2.4

Chapter 8 Using the program

I have included a file, SAMPLE, that is simply a small NEWFILES.DAT
file from SYNAPSE to help you test BBSee. You can later expand the
actual master database by importing your BBS's allfiles listings. I
suggest that you investigate various exclusion word combinations in
BBSETUP prior to creating your 'good' database. Once you have got the
hang of it, you can of course import files from any sources you want.

The first step, which I again emphasize as probably the most important
is to understand how to configure all the directories properly. Read
the configuration section, if you have not done so already.

It is now time to run the program, that is after all why you have read
all of this in the first place.

1. Run BBSETUP.EXE at the DOS prompt. I would recommend that you
make a temporary subdirectory for this purpose. Files can be
moved at a later date.

2. Continue through BBSetup configuration.

3. Place the desired file(s) to be imported in your description

4. Run BBSee and select the File Import Option.

5. Enter the filename (wildcards are possible).

6. When you are prompted to Select a BBS, moving the cursor, or
selecting the first character, will scroll through valid options.

7. to add files, to abort

8. When the file update is complete you are free to explore the

Enjoy, and good luck!

Page 39

BBSee Version 2.4

Chapter 9 Command line arguments

1. BBSEE [primary word [qualifier 1 [qualifier 2 [exception 1]]] ]

This will start word searches directly. Blanks are not allowed,
unless they are enclosed in quotes.

searches all filenames and descriptions with qmail in them

search all filenames and descriptions with qmail and ( read
or offline) but not containing the string cis

2. BBSEE [-u [[drive:]directory]filename[ext] ]

This option allows for automatic updates of Qmail packages, if
you have configured the Source/BBS name to be the same as that of
your mail package. The default extension is .QWK.

update the master database with files from the newfiles.dat
contained in synapse.qwk in the default mail directory.

as above but override using the default mail directory.

3. BBSEE [-i [[drive:]directory]filespec Source ]

This option allows for automatic importation of a file list using
the corresponding source.

update the master database with all files in the temporary
directory for the source SYNAPSE.

update the master database with descriptions from the file
FILES.LST contained in directory D:\MYDIR for the source

4. BBSEE -4 directory

This option creates a 4DOS/NDOS descript.ion files of
'directory'. See Section 7.2 for further information.

Page 40

BBSee Version 2.4

5. BBSEE -o source destination

This option creates a BBSee description destination file based on
the filenames listed in source. See Section 7.1 for further


These options allow you to catalog the indicated disk from the
command line. These will allow cataloging in batch files.

Page 41

BBSee Version 2.4

Appendix A Registration Information

I have tried to keep the price for the BBSee package extremely low to
encourage people to register. At these low prices, if you use BBSee
there should be no reason to NOT register. I plan to add
functionality which BBSee does not yet have, however this will only
come into being with your support. The pricing for BBSee is as

#1 $15.00 A license to use BBSee with a Registration Key for manual
#2 $20.00 #1 plus a floppy containing any new utilities and import
functions, a program to install the Registration Key,
support in use of the product and notification of upcoming
#3 $25.00 #2 plus automatic delivery of version 3, whether I decide to
release it as shareware or not.

Bank or postal money orders should be sent when possible. Please make
these out to Martin Vallevand. If you send me a cheque I will wait
for it to clear, before I mail out anything. All orders must be pre-

In Canada these prices are in Canadian dollars. Ontario residents
also must include the 8% PST.

All orders from outside of Canada must be paid in $US dollars. The
exchange difference will also be used to pay the difference in postage
and applicable taxes. Money orders are preferred. If you send a
cheque, (on American banks only), add $5 to the appropriate cost.

These prices are subject to change at any time.

If you are the author of a useful shareware package, and you send me a
copy of your product, registered and licensed in my name, I will
either return your package, or more likely, register you and send you
the activation key to for BBSee. Barterware?

I can be reached at

Martin Vallevand
Suite 100
56 Fourth Avenue
Ottawa, Ontario
K1S 2L2

for further information on obtaining this package. I am also open to
suggestions on methods of improving BBSee, by adding new functions or
by enhancing existing methods.

Page 42

BBSee Version 2.4

I will try to respond to letters or phone calls from users who have
not opted for the purchase of product support, but this is not always
possible. Also I cannot return a disk forwarded to me with a BBS
listing, or other information, unless return CANADIAN postage is also

I monitor many shareware related conferences on U'niNet, NA-net,
RelayNet (RIME), IntelecNet, FidoNet, and ILink. You may try to
contact me there. I also can be found on the Internet as
martin[email protected] , which can be access by some on-line
services such as Compuserve. Messages can also be left for me on
Synapse BBS, (see Appendix B).

Page 43

BBSee Version 2.4

Appendix B Where to find BBSee.

I will attempt to maintain the latest version of all BBSee shareware
products on SYNAPSE BBS and Exception #13 BBS as detailed below.


This BBS is an excellent IBM-only PCBoard BBS located in Gatineau,
Quebec, (very near Ottawa, the Capital of Canada). The SYNAPSE BBS
Sysop, Daniel Coulombe has graciously allowed me to use his BBS as a
'home' for BBSee. An account has been set up for BBSEE USER with a
password of VISITOR for the purpose of allowing you to download the
current BBSee files. This method is superior to logging on with your
own name, as you do not need to register and have full access to BBSee

The best numbers to use to call Synapse are listed below. These lines
are chained so that V32bis callers have access to 14 lines and 14.4K
HST callers access 10 lines. Synapse is closed for a daily event from
approx. 0230-0300 Eastern.

(819) 561-4321 14.4K V32bis/V42bis/V42 (4 lines)
(819) 561-3740 14.4K HST Dual Standard (V32bis) (3 lines)
(819) 561-0981 16.8K HST Dual Standard (V32bis) (7 lines)

Exception #13 BBS.

Anyone who would like to call for the current BBSee files can F'REQ
them from Exception #13 BBS from 0600-0400 Eastern. The current A and
B files can be accessed with the 'magic' name of BBSEE. My thanks to
the SysOp Chris Grainger for allowing this feature.

To contact Exection #13 BBS call:

Address: 1:163/518.0@FidoNet

(613) 830-2802 14.4K HST Dual Standard (V32bis)

Page 44

BBSee Version 2.4

Appendix C Program Return Codes

0 Normal exit

1 Not authorized
2-6 Error in BBSEE.CFG
7-10 Error in master database
11-12 Error in deleted file database
13-16 Error in floppy catalog database
17 Not enough memory for BBSee
18 Input file error
19 Could not open add file
20 Could not open error file
21 Could not open download file
22-23 Error on -u
24 Could not open master database file for word search
25 Could not open output catalog file
26 Could not open cross reference file
27 Index error - rebuild index
28 Could not open upload file
29 Could not open duplicate file
30 Cannot run BBSee in its Shell.
31 No NEWFILES.DAT or error in UNZIP in batch .qwk file
32 Error on batch import option
33-34 Error on -u
35 BBS name not found
36 Could not open floppy description file.
37-39 Error on -i
40 Conversion error
41 Database add error
42-43 Directory error in shell.
44 Changed video returned to BBSee from shell.
45 EMS error Search Word
46 Error in the search temporary file.
47 EMS error in Fill.
50-52 Error in floppy catalog database
53-60 Errors in volume database.
61-64 Errors in archive database.
65-66 Error in floppy catalog database
67 Catalog duplicate file error.
68 Error reading JPEG information.
70 Volume database error.
71-72 Error on -i -u
73 Error on /a /b
74-76 Error on -o -4

The remedy for many of these errors will be to increase the FILES=
statement in your CONFIG.SYS file.

Page 45

BBSee Version 2.4

Appendix D Cursor Movement and Editing Keys

Cursor Movement

Arrow keys - cursor movement
Ctrl-LeftArrow - word left
Ctrl-RightArrow - word right
Home - beginning of field
End - end of line/field
Ctrl-Home - beginning of first field
Ctrl-End - end of last field
Tab - next field
Shift-Tab - previous field

Inserting and Deleting

Ins - toggle insert mode
Del - delete character at cursor
BackSpace - delete character left
Ctrl-BackSpace - delete word left
Ctrl-T - delete word right
Ctrl-U - delete to end of field
Ctrl-Y - delete to end of form

Other Editing Keys

Enter - process current field
Ctrl-Enter - process all fields
Ctrl-R - restore field
Esc - abort data entry

Page 46

BBSee Version 2.4

Appendix E Mouse Support.

Full mouse support is available in BBSee, and it is configured ON by
default. Should you wish, it can be disabled in BBSetup in the
Hardware option. Basic operation is that the right mouse button
operates like the key and the left mouse button operates like
the key. I will refer to a left mouse hit as a 'click'. If
you don't like the fixed mouse arrow, it can be turned off (to the
standard DOS block mouse).

1.0 General Menu and option selection.

For navigation within the basic BBSee menu structure and
selection boxes, simply point the mouse block cursor at an option
and click.

The arrow up and down keys on the right hand side of a window
border can be used to scroll a window if the mouse cursor is
clicked on them.

Different options are available on the top menu bar, depending on
the current active window. Normally these options can be
selected with a mouse, however when you are in BBSee's file
viewer the mouse controls cursor movement, not menu options.

Advanced mouse use.

2.1 File Manager.

The File Manager is made up of two distinct windows for the mouse
to select from. There is the directory window of filenames, and
the command window with the possible commands.

Selecting a file within the directory window by a point-and-shoot
selection will activate the currently highlighted action in the
command window. This default action can be changed by placing
the mouse on the 'Action Command' line and clicking, and then
making the actual selection of the default command.
Alternatively you can manually hit the or
characters to open the Action window.

You can also use the mouse to select the option you want
performed by clicking on the appropriate option in the command
window. You may have to use the 'normal' cursor to highlight the
appropriate filename first.

2.2 Search Word.

Moving the filename cursor within the search window is done by
clicking the mouse on any element of a file or its description.

Page 47

BBSee Version 2.4

Clicking an already highlighted file will toggle the tag of that

2.3 Search Filename

Clicking when this window is active will toggle the tagging of a

2.4 View Catalog/List Catalog/List Archive

Clicking on a volume will bring up a list of all files on that
volume. Clicking on a filename line will bring up the
description of that file. If you click on the left border of a
line, archive contents or graphic resolution information will be
displayed if available.

2.5 View Tags.

Clicking on the filename will toggle a tag of a filename.

Page 48

BBSee Version 2.4

Appendix F Import Usage

Attempting to import file description lists into BBSee that are not in
PCBoard format, can cause a lot of problems. To overcome some of
these problems, a utility program, IMPORT.EXE is included in the BBSee
package to assist in the import process. The function of this program
is to convert files into a usable PCBoard-like data structure. All
non-PCBoard files should be converted with this program, before you
attempt to import them into BBSee.

The primary syntax to the IMPORT program is:

IMPORT {sourcename} {destname} PDM

P directs the number of passes that IMPORT makes on the file. The
choice is 1 or 2. Some BBS listings require two passes to
eliminate CR/LF, and Formfeed problems. 2 passes are required
for most Wildcat BBS lists.

A special parameter C (for Caution!) is available which can be
used for some BBS's which have the description on the line(s)
following the filename, but not directly under the initial line.
Files created with this option should be reviewed to ensure that
the descriptions created are what you expect.

D directs the date determination of the import, Y indicates to
IMPORT to swap the day and month fields (ie the format is MM-DD-
YY), N indicates not to swap the day and month, and C indicates
to check for the date format. Of course if all days are < 13 the
check will indicate not to swap the day and month.

If your BBS uses the international YY-MM-DD format, use the R
(for reverse option). The C option can identify this type as

M directs the mode of the import. IMPORT will automatically try to
(the A option) determine the appropriate columns that it uses in
the import process. You can override this if automatic mode does
not produce a workable PCBoard-like listing, by using the M
(manual) option. This mode will allow you to manually enter
column details for various fields. The filename and description
fields must be entered, if the size and/or date are missing,
indicate this by entering 0 for the start and stop column

In using manual mode, step through the file using the Get
Filename key, and then modify the various fields that you
require. If a file date or size does not exist, enter 0 for both
the start and end columns of the field. If the BBS uses a K
indicator include it within the filesize.

Page 49

BBSee Version 2.4

The default if the PDM options are omitted is 2CA

If the automatic mode of IMPORT works with your description list,
BBSee can also perform the automatic conversion. Use AUT (automatic)
in the BBSetup for the appropriate BBS, and enter the pd (pass and
date) parameters as determined above. When in doubt use IMPORT to
convert the file, and review it before importing into BBSee, to avoid
entering incorrect entries in the database. I do not recommend that
you use the Caution mode as the pass type, unless you are very sure
that it works with your BBS list regularly.

You should also attempt to use one pass mode if you find that two pass
mode is successful. For many Wildcat! types this is not possible (due
to the many differences available).

Four other import modes exist within IMPORT.

a. IMPORT {sourcename} {destname} XPC

This format is used to create a PCBoard file from the XFER5K.TXT file
available on EXEC-PC.

b. IMPORT {sourcename} {destname} MIN

This mode can be used to compress a PCBoard file if there are a lot of
spaces and carriage returns within a description. Some BBS's and
files created by IMPORT require this, if you want to capture more than
11 lines of description within BBSee.

c. IMPORT {sourcename} {destname} WC3
IMPORT {sourcename} {destname} WCF

These two options create output from specific file lists from two type
of Wildcat listings.

If you have a BBS listing from a major BBS that does not work
automatically with IMPORT I would very much appreciate it if you would
send me a disk, containing a sample, and I will attempt to incorporate
its structure into the automatic import. See Appendix A for
information on contacting me.

Other utilities for file conversion may be included on the extras
disk. See the README.2ND file.

Page 50

BBSee Version 2.4

Appendix G Database Packing

Most database packages, do not actually delete files from a database,
they simply mark the files for deletion. The BBSee database is no
exception. To reclaim this space it is necessary to 'pack' the
database. In addition to reclaiming disk space, (vis-a-vis a random
un-packed database), the packed file is maintained in alphabetical
order. Due to the nature of the BBSee database, an undelete feature,
before unpacking, is not possible.

To pack the BBSee master database, run the program PACBBSEE at the DOS
prompt, in a BBSee directory. PACBBSEE will read your BBSEE.CFG file
and automatically pack the master database. During the PACBBSee
operation, a record count will be displayed on the screen.

Note that to use this program, a new file is actually created, and
your old file is maintained, in case a problem is encountered. You
will therefore require disk space equal to that of you original
database and index to complete the database pack. Because of the
extensive hard disk activity required, this process can take a
considerable amount of time. It is not essential to the operation of
BBSee, and disk savings can usually only be achieved after a large
number of imports. I would pack the database after the all of your
bbs allfiles listings are included.

There is also a command line option (-c) to only pack files in the
floppy databases.

Page 51

BBSee Version 2.4

Appendix H Deleted File List Maintenance

Filenames that you delete from the master database are added to an
index file (the .DEL file) so that they are not added to the database
again. At times you may wish to review your deleted files, and allow
certain deleted files to be added as your computing requirements
change. To do this, the following steps should be followed.

Step 1.

The first step is to create an ASCII file of your present .DEL file.
The program READDEL.EXE will read your present .DEL file and output it
to standard output. The format to view the file on the screen is
READDEL {master delete file} To trap standard output to a file it is
necessary to use the DOS redirect command. The syntax for the
redirect of READDEL is:

READDEL {master delete file} > {filename}

Care should be taken here as DOS does not prevent you from overwriting
a file on a redirect.

This program can be used to view the deleted file list by reviewing
the above file, or omitting the > filename.

Step 2.

The second step in editing the .DEL is to use an ASCII text editor on
the filename output in the previous step. Remove all the lines
containing filenames that you no longer wish excluded. You can also
filenames to this file at this point, that will cause the entered
filenames to be removed from the master database in the next step.

Ensure that you use DOS naming rules when entering these filenames,
do not add a trailing dot. DO NOT include the following extensions if
you are manually entering filenames.


Page 52

BBSee Version 2.4

Step 3.

The third step is to write a new .DEL file using the WRITEDEL.EXE
program. This program, will read the list that you have edited above,
delete records from the master database if necessary, and create a new
.DEL file. The syntax for use of this program is:

WRITEDEL {input file} {output file}

The output file is the name of you master .DB and .DEL files without
an extension. It will not overwrite your present .DEL file. You must
first delete (or rename) the appropriate .DEL file. If you don't run
this program from your database directory, ensure that the output file
includes the proper sub-directory information.

WRITEDEL will check to see if the input file is in the appropriate
format. This checking is not all inclusive so be careful.

Page 53

BBSee Version 2.4

Appendix I Robocomm download support.

Support in BBSee for Robocomm 4.1 depends on an external program
2ROBO.EXE which directly access the Robocomm Clipper database files,
rather then intermediate files like the other supported automaters. I
would prefer that BBSee remain independent of other program files but
no other approach appears to work. To use 2ROBO


1. Copy 2ROBO.EXE to your Robocomm directory.
2. Configure the tag facility in BBSetup, to have the Tag File
Destination directory to be the Robocomm directory.
3. Use .DLR as the download file tag extension in BBSetup.
4. Configure Robocomm as the automater type.
5. Ensure that the BBS name you configure in BBSetup matches
the one you use in Robocomm.

Running the program.

The syntax to run the program is

2ROBO agenda bbsname

Program notes.

- If the agenda is not found, it will be added.
- All the files in BBSNAME.DLR will be inserted in the agenda,
after any old items.
- The file BBSNAME.DLR will be deleted.
- You should not run 2ROBO until just before running the
agenda, as BBSee will check for duplicates in the DLR file,
not the agenda.

I will try to add extra support for Robocomm based on REGISTERED users
requests. I would also ask that Robocomm users try to persuade the
Robocomm author (Dan Parsons), to allow an independent up/download
file mechanism which would provide better portability between Robocomm
and specialized programs like BBSee.

Page 54

 December 25, 2017  Add comments

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>