- Refer to README or UPGRADE in root dd dir and skip the rest :)
- type "make" in root dir.
- Create user "bbs". (shell = compiled daydream executable).
- Set environment variable DAYDREAM to point to bbs'es home dir.
(eg. export DAYDREAM=/home/bbs or setenv DAYDREAM /home/bbs)
- Copy dirs questionnaiore, display and data to $DAYDREAM. Make sure
dirs+files belong to user "bbs".
- edit daydream.cfg and compile it with utils/ddcfg. Most of the stuff
in daydream.cfg are introduced in the daydream.cfg and doesn't require
additional help if you own brains :)
- Install protocols. Create $DAYDREAM/utils and copy ddrz, ddsz and
hydracom to it.
- Try logging in as bbs.
- First created user will get full sysop access, so you can use sysop
commands like usered :)
- Includes all the configuration and datafiles (like UserBase etc)
- Includes logoff-batch files.
- Includes DayDream BBS utilities.
- Required for uploads.
- Contains most of the textfiles that are showed to the
user when he's cruising in the BBS.
- Contains external program modules, commands,
games etc. that can be executed from the BBS.
- Private uploads to the SysOp are placed in
- Contains your logfiles.
This directory includes some conference-specific data, such as File
catalogs, list of free downloads, list of paths that are used to access
downloadable files etc.
- File-catalog of XXX - filearea.
- This file is used to define directories that are
used for searching files. First line=Area 1 etc.
Amount of lines can be unlimited. If there are more
lines in this file than filedirectories in the
conference, rest of the lines are extra dl-paths.
- Contains list of Free downloads. Wildcards allowed.
NOTE! Global freedownloads can be specified in
- Contains list of doors to be launched in upload-
checking after user has verified that upload is ok.
It can be used for conf top utils, if someone codes
Here's an example of examine.dat:
This directory includes bulletins, such as top uploader list or otherwise
useful information. Add .gfx or .txt suffix.
- List of available bulletins
- Should be selfexplaining.
This directory contains the conference-specific textfiles displayed to the
user. If file is not found, it is searched from
$DAYDREAM/display/[Displaymode]/. Add .gfx or .txt suffix.
- List of commands.
- List of file-areas in the current conference.
- List of messagebases in the current conference.
- Showed to the user before uploading. Useful if you
want to show some upload-rules etc.
- Showed to the user before downloading.
- Showed to the user when he/she joins the
- Showed to the user before asking conference
- Showed to the user after JoinConference.TXT in login..
Contains messages and their headers.
- Headers of the messages in the current base.
- Autoscan and lastread pointers.
- Standard messagefile.
Contains most of the textfiles that are showed to the user when he's
cruising in the BBS.
- Shown when user launches autosig door, typically from
the "A"lter user info main menu command.
- Shown when user whose account has been frozen
tries to login.
- Shown before the login prompt.
- Shown to the user when he/she enters G-command.
- List of available commands
- List of available conferences
- Shown to the user before download
- Shown to the user when he/she's modifying account
- Shown to the user when he/she's listing files.
- Logoff screen
- Shown to the user when sysop enters chat mode.
- Shown to the user when sysop exits chat mode.
- List of available commands in message-editor.
- Shown when user requests help in more-prompt.
- Shown before asking files to move.
- List of available commands when reading messages.
- Displayed to the user when he/she decides to create
a new account. Useful for rules etc.
- Shown to the user if he/she decides to create
new account and the system requires a New User
- Displayed to the user if he fails 3 times in
the password checking.
- List of available protocols.
- Shown to the user before asking his/her real name
during the registration.
- Shown to the user before asking his/her handle
during the registration.
- Shown to the user before asking his/her Zipcode
during the registration.
- Shown to the user before asking his/her Voice
phone number during the registration.
- Shown to the user before asking his/her password
during the registration.
- Shown to the user before asking his/her computer-
model during the registration.
- Shown to the user before asking his/her Screen
length during the registration.
- Shown to the user when he requests help during
new file scan.
- Shown to the user before asking for the System
Password (if SystemPassword is enabled)
- Shown to the user before uploading.
- Commandlist on prompt requesting save etc.
- Displayed to the user after logon.
- Showed to the user if he/she didn't enter any
parameters for Z-command.
NOTE! Some of these files can be different for every security level. Eg.
Commands.255.GFX will be showed to the user if his/her access level is
- List of available display modes.
- Contains nearly all strings and prompts in BBS.
One string per line. It's possible to replace a
string with textfile by changing it to
"\a[textfile]". DD will look for [textfile].gfx/txt
from conference and global display dirs.
- If exists, DayDream will display this and
disconnect the user before logon.
- If exists, will be displayed to the user when
he/she requests chatting. Useful if you are ie. on
This directory contains some binary files which are generated by
ddcfg or DayDream itself. There's also some textfiles that can be
edited using Texteditor and they are:
- List of names that are not allowed in the system.
- List of free downloads (all conferences).
- Contains list of doors to be launched before asking
displaymode from user.
Note that doors listed in here MUST be DDDP-doors.
If door uses changes displaymode using
intcommand "mode ??" or similar command, DD doesn't
ask for display mode.
- Contains list of doors to be launched after showing
Welcome.TXT. Useful if you want to force a door to be
run on startup. (One can abort welcome.txt with
- Optional file for running doors at logoff which
don't seem to get along with the batchX.logoff files.
This directory contains batch files. You must chmod +x them, so
daydream can execute then. Currently supported files are:
- This will be executed everytime user leaves a BBS.
Useful, if you want to have up-to-date top users
list etc in your board etc.
X stands for node.
You can have the following control codes in your text files:
- Pause (No text)
- Any key to resume (Pause)
- Turn more-prompts off
- Menu command
- Remove linefeed/carriage return.
- Disable codes for the rest of text (For security)
- Show textfile
- Show a random text file. [FILE] is the
prefix for the filename. After the prefix a random number between 1 and [max]
(inclusive) is appended. Note that the filenames cannot contain any suffix,
for example, the .gfx extension. The [max] parameter must be between 1
and 16777216 (inclusive).
- Real name
- Voice Phone
- Screen length
- Protocol ID
User Id Number
First Date On
Last Date On
Sysop Pages Remaining
Max lines in file descriptions
DayDream main prompt has special control codes too. Main prompt is located
at the line 296 of strings.XXX. Codes are:
Last read pointer
Message base number
Message base name
Time left in minutes
Doors that are declared in "daydream.cfg", can be given a number of
optional parameters. Some special tokens are interpreted as follows:
The number of the current node
User's real name
User's current security level