# Installing DLG

Every effort has gone into making first-time installation of DLG as easy as possible. However, a great many things must be done and there is of course a possiblity that the installer will not operate properly under your unique set of circumstances. While this chapter does not cover all the bases, it will perhaps give you the means to overcome the occasional problem that you might encounter. If not, you will need to contact Digerati Dreams directly to rectify the problem. We will do all we can to help satisfy your needs in this regard.

## System Requirements

DLG's requirements are modest but absolute - if your system does not at least match this profile, you will not be able to run DLG at all.

- AmigaDOS release 2.04 or later
- At least 512 kB of RAM. More is recommended. Fast RAM will give best results. Additional lines will incur roughly 100 kB per line additional overhead (peak usage).
- A hard drive with at least 5 MB of free space. You will need a minumum of 3 MB of space to store the software and additional space for file and message areas. While in theory you can operate entirely off of floppies, it is strongly recommended against.
- At least one modem.

While DLG works with OS 2.04, future releases will require at least V3.0.

Users of the ARP shell will find that it will cause crashes with DLG. Under OS 2.04 there should be no good reason to use the ARP shell, anyway.

## Register your software!

Included with your software is a registration card. We encourage you to register your software as soon as you purchase it. Your registration card contains a serial number. Always refer to that serial number when initiating a support request with Digerati Dreams.

## Before you install DLG

Before you install your software, we suggest the following:

- Ensure your installation disks are write protected before you insert them into your disk drive. This not only guards against viruses, but also against accidental erasure.
- Make backup copies of your disks and use those backups to install the software. Be sure that the disks are named the same as the original disks.
- If you have the means to do so, make a full backup of your system "just in case".

## Installing DLG

Installing DLG is a simple matter using the Amiga Installer. Simply click on the INSTALL_DLG icon on Disk 1 and it will begin. You will be asked if you wish to log the installation process; we suggest that you either log to a log file or to your printer. This will give you a solid record of events that transpired if the software installer somehow does things wrong.

Throughout the installation process, you will be given a number of choices to make. Before the installer actually starts copying files, you can abort the process with no permenant effects. After files begin to be copied, your recovery path is less straightforward.

With this in mind, we have constructed the installer so that it asks you about the specifies of file and directory locations FIRST, then actually implements your instructions.

## Installed Directory Structure

DLG's installer will create a variety of directories and make a number of logical assignments in the process of installing your software.

Directory | Assign | Purpose
DLG | DLG: | Location for most of DLG's executables
DLGConfig | DLGConfig: | Location for most of DLG's configuration files.
MSG | MSG: | This is where DLG will by default store its messages and bulletins
FILE | FILE: | This is where DLG will by default store its file archives for downloading
Fido | Fido: | This is where DLGMail and its config files are kept. Not installed unless you tell it to.
FIDO:Trap | - | This is where the executables for TrapDoor are kept. Only installed with DLGMail.
FILE:Tick/ | TICK: | This is where DLGTick will store files that are not kept on the BBS itself. Only installed if you install DLGMail.
MSG:Pass/ | PASS: | This is where DLGMail will store messages for echos that you are not importing to your BBS, or Passthrough areas. Only installed if you install DLGMail.
Msg:Inbound/ | INBOUND: | This is where incoming FidoNet mail will be found and processed by DLGMail.
Msg:Outbound | OUTBOUND: | This is where outgoing messages will be stored by DLGMail before they're sent.
Msg:NodeList | NODELIST: | This is where the FidoNet nodelist is kept. Only installed if you install DLGMail.
User | User: | This is where each user's configuration files are kept, as well as thier private messages and files

## Contents of DLGConfig

DLGConfig: contains a number of nested directories, each serving a purpose.

Directory | Purpose
CharSets | This is where translation character sets are kept. These are used to remap messages so that they display properly in all countries.
Fido | This contains files specifically for use with FidoNet-enabled software. Eventually, all FidoNet configuration files will be stored here.
Group | This is where group definitions are kept.
Languages | DLG can use different language files (localization) depending on how the sysop and user sets up the system (sysops control what's available, and users choose from that). This is where the language files are kept.
Menu | This is where menu definitions, display files, help files, and function templates are kept.
Menu/<Menu_Name>/ | Each menu's help files are kept in a seperate directory.
Menu/Funcs/ | The files in this directory define what built-in functions each online module posesses. Do not edit these without explicit instructions!
Misc | A number of miscellaneous configuration files are kept here. In general, third-party utilities likewise keep thier config files here.
Notes | You may keep private notes for each user on your BBS. This is where the notes will be stored.
Port | Port, modem, and local display files are kept here.
Rexx | DLG Arexx files are kept here, as well as any other Arexx files you wish to use with the BBS. DLG Arexx files use the extension .DLX.
SIGS | The configuration files for Special Interest Groups (SIGs) are kept here.
Template | You may use templates for validation of new user accounts and creation of file and message areas. This is where they are stored.
Text | A number of different text files are kept here, from special text files used internally to those that you wish to include as part of the BBS.

## If You Lose Your Password

It's a bit difficult to maintain your system without having a password. If you do forget it, follow these instructions:

1. Open a shell.
2. In the shell, type

   `CD User:<Your_Name>`

3. Type

   `Type User.Data OPT H`

The first 12 characters will be your password.

## Recovering a Corrupted Account

If you accidentally corrupt your account data, you will have to create a new account. For this reason, we encourage you to investigate a good backup utility and hardware, and use them. Another possibility is to maintain a fallback account that you can use to enter the BBS with if your main account gets corrupted. Finally, you can use the MakeSysop program that is shipped as part of the installer disk. This program is what is used to create your initial account data when you install the BBS, and can be used in an emergency to give you an account again. Usage is:
`MakeSysop "Your Name" "Password"`