## Logging in the First Time, and Setting Up your BBS.

While the Installer does what it can to set up your system for you, there are still some things you need to do in the capacity of Sysop in order to make it useable to other users. DLG's primary means of configuration is carried out online by the sysop. Therefore, the first thing you must do is log in. One of the standard batch files that DLG installs is in the S: directory and called `Local`. This batch file will log you in on the local port, TL0.

If you have not done so, run `S:DLG-Startup` from a different shell now.

### Logging In

When installing DLG, you were prompted for a user name and password to use for your sysop account. You will need that now. From a shell, type

        s:Local

and you will see something like this.

NOTE: the exact contents of your screens will differ from what's shown, most likely, so use common sense and simply use what you see as a guide.

Until you have done some more configuration work, you will go through this process each time you wish to log in. Once you have the hang of using the various programs, you will be able to alter your batch files and configurations to streamline the local login process.

Once you have logged in, you will see a menu like this:
This is the Main Menu and is more or less the nexus for the entire BBS for online users. From here, you will want to go to the Sysop Menu

### The Sysop Menu

The Sysop Menu is so important that we should take a moment to summarize what it does. The following menu entries are available by default, though you can change it as needed.

Key | Function | Description
D | Define / Edit Message Areas | This takes you to the message area editor, where you add, edit, and remove message areas on the BBS. There is also a message area template editor attached to it that performs more or less the same functions on message area templates.
F | Define / Edit File Areas | This takes you to the file area editor, where you add, edit, and remove file areas on the BBS. There is also a file area template editor attached to it that performs more or less the same functions on file area templates.
E | Edit Message Area Access | From here you can edit special access flags for users. For example, you can give a user Sysop access to a specific message area without changing the default settings for a message area in general. You could also, for example, remove a user's write access if that user was not observing the posting rules for a specific area.
R | Revise File Area Access | From here you can edit special access flags for users with regard to file areas. This works exactly as the "E" option above works.
U | User Account Edit | The User Editor allows you to directly edit user accounts (including your own). Besides individual accounts, you may also batch edit them. User templates can be used to create and alter user accounts, as well. This function also offers the all-important validation function, in which you validate new user accounts and give them proper access to the BBS.
A | Group Account Edit | The Group Account Editor allows you to create, edit, and delete Group accounts. Group accounts are used to access many users as if they were one, such as for message routing.
P | Port Configure | The Port Editor contains a number of other editors: modem configs, port configs, global settings, and so on. You will see this editor shortly.
N | Network Mail Configure | This editor facilitates the creation of default FidoNet mail settings.
C | Configure Menus | This editor allows you to edit, create, and delete Menus and Menusets. Besides the visual appearance of a menu, you can create menu-sets that area attached to specific languages, which is very important for internationally-flavored BBSs.
T | Transfer Area Maintenance | This module contains file area maintance functions. Using it, for example, you can import entire directories of files from CD or network directories. There are also some "fix-it" functions for those times that your file areas might possibly become corrupted.
G | General Configuration | This menu contains a number of editors for such diverse things as archivers, editors, modem protocols, and so on.
S | SIG Creation/Edit | This editor allows you to create and edit both file and message area SIGs.
L | List Users | A quick listing of all users on your BBS.
M | Main Menu | Returns you to the previous menu (this is a DLG convention that you may alter if you wish).
H | Help | Brings up a help menu selection screen. From there, the user can select what command he or she wishes help with. Another DLG convention that you may change, though we recommend against it -- "H" for "Help" makes a lot of sense, after all.
? | Display Menu | Another DLG convention. Often this is a hidden menu selection. It is most useful if line noise "corrupts" the menu, or if the user is using Intermediate or Expert menu mode.

From here, select the [P] Port Menu editor.

### The Port Editor Menu

This menu offers you everything you need to configure and edit ports on DLG. Here's a brief description.

Key | Function | Description
P | Port Configuration | Port settings. This is a top-level configuration editor that depends on other settings being created first.
D | Configure Displays | Display settings. This defines the screen and window sizes that DLG uses in opening windows and screens, such as the one you are using now to configure the port.
G | Global Set Config | Global Port settings. Global settings define a lot about how a port is presented to the user when the user logs on. Using global settings, you can virtually make one BBS appear to be two BBSs, depending on the port you log in to.
O | Modem Configure | Modem settings. Global settings define how the handler "talks" to the modem attached to the port. A number of defaults have been provided with the software. If one corresponds to the modem you use, your job will be simple.
C | Computer Types | While it has no impact on operation of the BBS, you can define a set of computer types that your users can "register" with, allowing you to tell at a glance what sort of terminal the user is using to log in to the BBS.

The first order of business will be to define your modem type. Select [O].

### Modem Configuration Editor

From here, you can create, delete, and edit modem files. You should be aware that you only need one modem file for each type of modem you use. If you have multiple lines, all with the same type of modem, each port can use the same modem file -- quite a time saver. Hit [L] to see what modems you may select from. If you see the type of modem you use listed, you can simply use it instead of creating one. You should edit it to ensure that its settings are agreeable. If you do not see the modem type you wish to use listed, you will need to create one using the [A] Add Modem function. Either way, the following settings are relevant.

Select | Function | Description
1 | Init String | This string is sent to your modem to initialize it. It can be as complex or as simple as you desire. Our preference is to pre-save all the correct settings in the modem's NVRAM and then simply use ATZ (ATZ0 for multi-profile modems) to recall it.
2 | Hang Up String | This string is sent to your modem to cause it to hang up (go on-hook). Generally this is ATH0 for Hayes-compatable modems.
3 | Return to Command Mode | This string is sent to the modem to get it to go into command mode, a state in which it will accept commands rather than sending data through to the remote. For Hayes compatable modems, this is generally "+++".
4 | Reset String | This string is sent to your modem to reset it to a default state. This is generally ATZ for most hayes-compatable modems.
5 | Answer String | This string is sent to your modem to cause it to pick up the line ("answer"). For Hayes- compatable modems, this is generally "ATA". If you have your modem set to auto-answer the line, this command is ignored.
6 | Ring String | This tells DLG what string the modem will send when the phone line rings. Generally, this is RING.
7 | Lock Mode | If you are using a high-speed modem (greater than 4800 baud), you must lock the modem to computer data rate at a high rate of speed, or there will be much dropping out of data.
8 | Hang Up with DTR | If your modem supports it, DLG can toggle DTR (Data Terminal Ready) to indicate that the user has logged off and that the modem should hang up. The alternative is much slower, in that DLG will have to send the return-to-command-mode string and then issue the hangup string.
9 | BBS Answer Mode | If set to yes, DLG will answer incoming calls directly. This is the default setting you should use for a normal BBS line. However, if you are using an external program such as TrapDoor to answer the line, set this to NO.
10 | Maximum Baud Rate | This is the data rate that DLG will use to communicate with your modem. If you have the line locked (see above), this should generally be higher than the modem's rated speed. A good rule of thumb is to set it at a data rate that is (a) a multiple of 2400 and (b) at least twice as fast as your modem. Don't get carried away! Some modems do not react well to ludicrously high speeds.

You will note that there is a DIRECTCONNECT Modem file. This is used for all local logins, such as the one you are on now.

Now, let's set up the global settings for your ports. Select M and then G to go to the Global Settings menu.

### Global Settings

Global settings affect how your BBS looks and operates for a particular port or ports. Like modem files, you can define one global and use it wherever you need to. Two configurations are provided as starters, DEFAULT and LOCAL. You are, of course, using the LOCAL setting for this login. The DEFAULT setting is configured for your remote port. If you wish to create a new one, you may. At any rate, you should edit all globals that you intend to use at this point, even if it's only the DEFAULT and LOCAL globals.

Select | Function | Description
1 | BBS Name | The name of your BBS. If you have more than one global and wish to have different "looks" for them, this may be an imporant visual cue.
2 | Auto Screen Open | If set to yes, any time a user logs in on this port, a screen or window will open and you will be able to watch what the user is doing. If set to no, the user's activities will be carried out in the background. The latter setting is more effiecient. Even if you set this to "No", you can always pop open a screen to snoop on your users (see the more advanced topics as to how this works).
3 | Screen Type | Controls how the "snoop" window opens. If set to CUSTOM, a new screen will open and you will view the user's activities pretty much as they see it on thier terminal. If set to WORKBENCH, a window will open on your Workbench screen. The latter is more memory conservative.
4 | Verbose Pausing | A user can pause the stream of data displayed by selecting CNTL-S and CNTL-Q to restart the flow, which is more or less normal for any ANSI terminal. In verbose pause mode, DLG will display a prompt ("[PAUSED]") whenever a pause occurs. If verbose mode is turned off, there will be no visual indication that the BBS is paused.
5 | Public Accessability | A port can be limited to ONLY people within a given group (see group accounts). If this is set to YES, such limiting occurs. By default it is set to NO, allowing anyone to log in.
6 | Group Name for Private Port | If you answer PRIVATE for (5), you will need to specify a group name that actually has access to this port.
7 | Idle Timeout (Seconds) | DLG will log out a user if more than a certain amount of time has elapsed with no activity on the line. This parameter sets how long that will be for the port in question. You might consider a lower number for a port that gets more traffic, for example.
8 | Connect Delay | This tells DLG how long to wait after a connection before it starts interacting with the user. This allows time for the connection to stabilize. If you do not have connection problems with your users, you might consider lowering this number.
9 | Minimum Baud Rate | You can limit connections to the port in question to higher speeds through this parameter. Setting it to 300 effecively allows any connection through (unless somebody knows of a modem that runs lower than 300 baud!)
10 | Default Menu | This indicates which menu the user will see upon logging in. Right now, this should be set to MAIN since you don't have any other general purpose menus defined. This is one of the more powerful settings of the globals, as it can direct users to entirely different setups, virtually a different BBS if you so wish it.
11 | Default Login Command Stack | DLG will allow you to "stack" a series of keystrokes together and execute them sequentially without actually displaying the menus along the way; this can get you from one place to another very quickly. You have the option of defining a default stack that will execute whenever a user logs in. Very handy for landing users where you want them. This command stack is copied to each user's data when that user is validated. The user can then change it if they don't agree with your choices.
12 | Forced Login Command Stack | This is the same as (11) above, except that the user does NOT have the option of changing it.
13 | Private Message Reroute Area | If this is set to a non-zero value, all private messages written by users will be copied into a message area where you can monitor them. We do not advocate nosiness for its own sake, but as a sysop you may be legally liable for illegal activities taking place through your BBS. As such, you are given the ability to spot problems and head them off quickly. As you currently do not have any message areas created, leave this at 0 for now.
14 | Character Set | You can define a translation character set for each port global, thus allowing for special national characters in countries that use other than ISO Latin-1. If you have no desire to change this, leave it at 0.
15 | Default Language | Each port global may be attached to a specific language. By default this is English. You should set it at your native language and then create menu-sets for the other languages, thus giving the users the ability to choose for themselves.
16 | Auto ANSI Detect | If this is set to YES, the handler will attempt to detect if the user uses ANSI before the user logs in. If the user does support ANSI, you can use colors in your login screens and so on without fear of the user seeing garbage.

Once you have set this up as you desire, save it off and go back to the previous menu (M), then select the Display editor (D).

### Display Configuration

The Display Configuration settings determine how DLG's interactive windows and screens will open. This includes the window for Chat and the screen for PeopleTalk.

Window Settings |
Select | Function | Description
1 | X Position | The horizontal position of the upper left corner of any opened window. 0 is all the way to the left.
2 | Y Position | The vertical position of the upper left corner of any opened window. 0 is all the way to the top. A value of 11 is usually sufficient to leave the screen's title bar clear.
3 | Width | The horizontal size of any opened window. Can not be larger than your screen's width plus the X position.
4 | Height | The vertical size of any opened window. Can not be larger than your screen's height plus the Y position.
5 | Activate | If set to yes, this window will be activated as soon as it is opened, thus moving your keyboard focus to it. If you are busy typing at the time, this can prove annoying, so use it with caution
6 | Font | The font to use with any opened window. Defaults to topaz.font. Note that font names are case-sensitive.
7 | Size | The size of the font you wish to use with this window.
Screen Settings |
Select | Function | Description
8 | Width | The horizontal size of any opened screen.
9 | Height | The vertical size of any opened screen.
10 | Bit Planes | How many bit planes defines how many colors are used with your screen. 1 bitplane is two colors, 2 bitplanes is 4 colors, 3 is 8, and 4 is 16. DLG only currently supports 3 bitplanes, though you can set it to 4 if you wish.
11 | HiRes | If set to yes, the screen will open in high-resolution mode. If not, it will nopen in low- resolution mode. This can be pretty ugly if you set the screen resolution to 640 pixels...
12 | Interlace | If set to yes, the screen will open in interlace mode. This should likewise be set with your screen resolution in mind.
13 | Open Behind | If set to YES, then the screen will open BEHIND all others, thus not disturbing what you are doing at the time. Otherwise, it will pop open as the front most screen.
14 | Font | The font to use with any opened screen. Defaults to topaz.font. Note that font names are case-sensitive.
15 | Size | The size of the font you wish to use with this screen.
16 | Edit Colors | This brings up a palette requester that will allow you to change the colors used for the screen.

Once this is complete, you are ready to tie it all together using the Port Configuration editor. Select [M] to return to the previous menu, then [P] for the Port Configuration Editor.

### Port Configuration

The port config editor ties all the previous work together for a particular port, plus a few other parameters. You should have two ports to configure -- TR0 (remote) and TL0 (local). You can create as many other ports as desired once you have everything set up to your satisfaction.

Select | Function | Description
1 | Serial Device | This is the hardware device to which the port is attached. The default Amiga serial port is `serial.device`. If you are using a different serial card for your remote port, you will need to set that name here. Note that device names are often case-sensitive. For the local port TL0, this will be `console.device`.
2 | Unit Number | This is the unit number of the serial device in use. For `serial.device` and `console.device`, there is but one choice -- 0. For other serial ports, it will depend on how you connected your modem. Most serial cards start at 0 and go up as far as 7.
3 | Modem File | Here you select the modem file(s) you configured earlier. For TL0, you must select DIRECTCONNECT.
4 | Global Set | Here you select the global set(s) that you configured earlier.
5 | Display File | Here you select the display file(s) you configured earlier.

That's it! You have now set up your basic connectivity and should be ready to accept callers. From here, you will need to set up areas, user templates, and so on, but these are discussed in the Sysop Operations section.