CHEFDOOR
++++++++

version 3.14 by Michael Conley
released 04/20/93 from the Charlatan's Cabin BBS, Los Angeles, CA.

CHEFDOOR is designed to be run as a live DOOR program on Wildcat! 3.x and 2.x
systems. It allows your users to search through any recipe files you provide.
For each file, they can get a LIST of the recipes by name, or they may search
through the file, looking for a particular recipe by name, keyword, matching
ingredient, etc.

Sample recipe files are included, thanks to SysOp Richard Hoover, who spent
many hours editing them for this release.

SETTING UP A DOOR:
==================
The Wildcat! manual and other tutorials have done a fine job of explaining
how to set up a door on your BBS. Therefore I won't re-invent the wheel by
going through all of the directory naming and batch file creating necessary
to execute CHEFDOOR.

It's important to note that CHEFDOOR will check the CURRENT directory (where
your DOOR program is started) for either DOOR.SYS or CALLINFO.BBS. Wildcat!
version 3.x creates DOOR.SYS; earlier versions created CALLINFO.BBS. On my
system, I have a directory called DOORS, and my batch file copies DOOR.SYS
into that directory, then change to that directory, then start CHEFDOOR.

ChefDoor also needs ENVIRONMENT VARIABLES: These are used by Wildcat! 3.x
and will be ignored by Wildcat! 2.x, but they MUST be present for each node
of your Wildcat! system in order for ChefDoor to function properly:

SET WCPORTID=2 < put these lines in your Wildcat! startup batch file and
SET WCIRQID=3 < check to be sure they are added to your environment.

If you have a non-standard port address, you'll need to provide an additional
environment variable with the DECIMAL port address:

SET COMBASE=1016 << substitute your correct decimal port address here.

That will override the default address of the port number specified in
WCPORTID. WCIRQID will still need to be set to the correct interrupt
value. ChefDoor supports IRQs in the range 2-15.

If you're running the Wildcat! IM version, I strongly recommend Scott
Brynen's DIGIFOSSIL, a shareware fossil driver available on the MSI
bulletin board, or on the Charlatan's Cabin BBS, and many other places.

A sample batch file for Wildcat! version 3.x would look something like this:

REM this is a sample batch file for CHEFDOOR with Wildcat! 3.x
REM this assumes you SHELL to your doors. If you TERMINATE, you
REM need to add a change-directory back to your startup directory
REM and then run your startup batch file.
ECHO OFF
COPY C:\WC30\WCWORK\NODE%WCNODEID%\DOOR.SYS C:\WC30\DOORS\DOOR.SYS
CD C:\WC30\DOORS
CHEFDOOR
EXIT

A sample batch file for Wildcat! version 2.x would look something like this:

REM this is a sample batch file for CHEFDOOR with Wildcat! 2.x
ECHO OFF
CD \DOORS
COPY C:\CAT\NODE1\CALLINFO.BBS C:\DOORS\CALLINFO.BBS
CHEFDOOR
CD \CAT\NODE1
NODE1.BAT

Note that CHEFDOOR monitors time online and Carrier Detect, and will close
and exit gracefully back to the node if the caller drops offline while in
the door.

PREPARING A RECIPE FILE:
========================
ChefDoor will operate with up to 18 separate recipe files ... see the
configuration file for an example of how to set up multiple files.

The format of the recipe file is quite simple, but very specific. You may
need to edit any existing recipe files to conform to this format before they
can be used with ChefDoor:

The first several lines of the file are the "HEADER" and may include any
descriptive information you like, such as the date the file was compiled,
the name of the chef who authored the recipes, etc. We suggest that you
keep the header SHORT, as it will be seen at the beginning of each search.

Before the first recipe, and between each recipe after that, place a "divider
bar" of equal signs, beginning in column 1 and at least 10 columns wide. The
recipe name is next, in all UPPER CASE, on the first line after the divider
bar. After that, the format of the recipe and ingredient list is free form
and may be mixed upper and lower case as desired.

Distributed with this ZIP file is a sample recipe file which shows the
required format in detail.


PREPARING CHEFDOOR:
===================
It's necessary to create a configuration file for CHEFDOOR, named CHEFDOOR.CFG,
which must reside in the directory where you'll start CHEFDOOR. Here is a
sample configuration file:

BBSNAME=The Charlatan's Cabin BBS
CTSCHECK=YES
FOSSIL=NO
LISTPATH=C:\WC30\doors

LISTNAME=Cakes/Cookies/Pies/Candy
LISTFILE=RECIPE1.TXT
HEADERLINES=3

LISTNAME=Main Course for meal
LISTFILE=RECIPE2.TXT
HEADERLINES=3

LISTNAME=Salads & Dressings
LISTFILE=RECIPE3.TXT
HEADERLINES=3

LISTNAME=Muffins & Buns & Bread
LISTFILE=RECIPE4.TXT
HEADERLINES=3

LISTNAME=Drinks of all kinds
LISTFILE=RECIPE5.TXT
HEADERLINES=3

LISTNAME=Seafood Courses
LISTFILE=RECIPE6.TXT
HEADERLINES=3

LISTNAME=Side dishes for meals
LISTFILE=RECIPE7.TXT
HEADERLINES=3

LISTNAME=Sauces/Dips/Solutions
LISTFILE=RECIPE8.TXT
HEADERLINES=3


You may edit this file as desired, following these guidelines:

BBSNAME= The name of your BBS as you want it to appear in
the program's displays.

CTSCHECK= Indicate YES or NO ... do you want the program to
check for Clear to Send? Default is YES if this
line isn't found.

FOSSIL= Indicate YES or NO ... do you want the program to
redirect all COM calls using the INT 14h FOSSIL
convention. If you're NOT running a FOSSIL driver,
set this to NO.

LISTPATH= The complete Path to your recipe text files.

Next, you'll need to set up configuration information for each recipe file
you want to support in ChefDoor. NOTE: You'll need to place ALL of the
files in the directory defined in LISTPATH.

A maximum of 18 Recipe files may be included ... any beyond that will be
ignored.

For each Recipe file, create a block of entries with these three lines:

LISTNAME= The name of the file as you want it displayed on the
menu screen.

LISTFILE= The name of the Recipe file file itself. Reasonable
wildcards are acceptable, such as "PASTRY??.LST" The
program's search routine will display the first
matching file, so be sure to delete old ones when you
create a new file.

HEADERLINES= Indicates how many lines from the very top of the
text file you want to display. This might include
the name of the list, the compilation date, and
perhaps the name of the chef who created the
recipes. I suggest you keep this to a fairly small
number because this info will be displayed each
time a search is initiated on a particular file.

It's important to note that the block of options for each list must be filled
out completely, or ChefDoor may produce unpredictable results! Also, be sure
to keep them in the order shown above. Do NOT omit any lines or ChefDoor
will reject the configuration file.

------------------------------------------------------------------
PROBLEMS, SUGGESTIONS:

This program is public domain. I don't seek or accept any donations for
this or any of my other Wildcat! utility programs, including TODAYBBS,
FLOP, MSTAT, USTAT, and others.

I welcome suggestions, and will try to help (no guarantees) if there are
problems.

You may contact me at The Charlatan's Cabin BBS (213) 654-7337. Mention
your Wildcat! registration number in the comment and you'll be upgraded to
visiting sysop level without the usually required registration by mail.

You may also leave a message via CompuServe EMail. My CompuServe account
number is 70250,220. I also regularly check the Mustang Software head-
quarters BBS, especially the "3rd Party Utilities Help" conference.

Please, NO VOICE CALLS. This isn't meant to be unfriendly, but with the
price of public domain software these days ... I just can't afford to be
"on call." I WILL respond to your questions via my BBS or CompuServe,
or via the Mustang Software registered SysOp BBS.

Version history:

3.00 01/03/92 First (private) release of ChefDoor.
3.01 01/11/92 First public release of ChefDoor. (no recipes)
3.02 01/18/92 Feature added: [L]ist recipes in a file.
3.03 01/19/92 Fixed local display erase line function, enabled
total of 18 available list files. Enclosed sample
recipe files.
3.04 01/19/92 Fixed CTS checking bug.
3.05 02/07/92 Recompiled with QBSerial 2.1 by Jeff Sumberg. More
reliable on a multi-tasking machine.
3.06 07/05/92 Recompiled with QBSerial 2.25 by Jeff Sumberg.
3.07 08/07/92 Fixed bug which caused error if user name was a
one-word name.
3.10 12/19/92 Added FOSSIL support using QBSerial 3.0. Requires
configuration file change.
3.11 01/23/93 Enhanced FOSSIL support, better checking for init
problems, etc.
3.12 01/29/93 Bug fix in FOSSIL flow control.
3.13 04/02/93 Added routine to clear input before before asking
for first input.
3.14 04/20/93 Added recognition of RIPmode, outputting in ANSI
if "RIP" or "GR" present in DOOR.SYS