Possibilities - Realities 2/92

Contact:   eSoft, Inc. (Makers of TBBS)
           15200 E. Girard Ave., Suite 3000
           Aurora, CO  80014
           (303) 699-6565      Voice
           (303) 699-6872      Fax
           (303) 699-8222      BBS
           support@esoft.com   E-Mail

REALITIES 2/92
--------------

*** From February 1992 Possibilities Newsletter ***
*** Copyright 1992 by eSoft, Inc.  All Rights Reserved ***

REALITIES...how to make it work
by eSoft Technical Support Staff

From the moment you first install TBBS, it's easy to see the possibilities are 
almost endless.  Turning those possibilities into realities can bring up 
questions.  For this reason, quality customer support is at least half the 
overall value of any software package. 

We recommend you call the eSoft Support BBS (303-699-8222) and read through 
the messages in each of the various support areas.  You could find answers to 
your questions, even before you've asked them!  You'll definitely get some 
useful tips and ideas for bringing possibilities to life with TBBS.  In this 
section of the newsletter, we will answer some of the more commonly asked 
questions we receive. 

Manually Invoking External Events...

Q. I'd like to force an external event to occur before it's really time for it 
to happen.  Preferably, I'd like to do this remotely.  Can I? 

A. Yes you can do this if you are using TBBS 2.2. TBBS 2.2 has a new feature 
for use with the Type 21 remote Sysop console -- the ability to exit with an 
errorlevel other than 1 (which is still the default) which is right up your 
alley for this function. 

This is accomplished by adding an errorlevel in the Opt Data field of the Type 
21 menu entry.  When you activate that menu entry, then select to shutdown the 
system TBBS will exit with that specified errorlevel (instead of the normal 
errorlevel=1).  If you place the errorlevel from the desired external event in 
the Opt Data of the Type 21 command then, when you shutdown, TBBS will start 
that event just as though it had exited at its scheduled time.  

Once you invoke the shutdown, nothing will be displayed to your screen because 
the MLHOST remote host module will never be loaded.  After the shutdown is 
initiated, simply disconnect (drop carrier).  Assuming that the event was 
properly configured to restart TBBS after it's done, the system will come back 
online for callers after completion of the event. 

For more information about external events and how they work, refer to Chapter 
9 of the TBBS manual. 

Logon Options Not Working...

Q. I just received TBBS 2.2  It's terrific, but I made some changes to the 
Logon Options screen in CEDIT, and the changes didn't take effect!  I see them 
in CEDIT, but they definitely don't work.  Is TBBS broken? 

A. No, it's not broken.  A new TBBS 2.2 feature (which allows you to customize 
different lines for different logon formats) is getting in your way! 

To correct this problem run CEDIT.  From the menu bar, select Com Ports, then 
Port Definitions from the pull-down menu.  Select one of the lines on which 
the Logon Option doesn't work. 

On the second line of the screen (right under where it says "CEDIT 2.2" in red 
and white) does it say "Custom Logon"?  Chances are it does.  At that point, 
press F4 to access the Custom Logon screen.  Now hit F2 to Clear the Custom 
Logon settings.  A window will pop-up and ask if you want to save your changes 
- select Yes. 

Repeat this procedure on any and all lines where your Logon Options have not 
taken effect.  Finally, exit CEDIT, making sure you save your changes on the 
way out.  Your problem should be fixed! 

The Custom Logon feature allows you to customize a set of Logon Options that 
work only on a particular line.  In this fashion, different lines can behave 
differently if you wish.  Unless you fully understand the new TBBS 2.2 CEDIT, 
you can inadvertently setup Custom Logon Options for a line and not realize 
you've done it, which is probably what caused your problem. 

Note: Custom Logon is how you make your TBBS appear to be completely separate 
systems on different telephone lines.  It also allows you to have custom 
SIGNON or SIGNOFF files for different groups of lines. 

How Do I Logon as SYSOP Remotely? 

Q. I called my system remotely to logon as Sysop, and I can't figure out how 
to do it!  When the system asks for my First Name, I type in "SYSOP" and then 
press Enter.  But then it asks me for my Last Name!  What do I do? 

A. The first name/last name logon ID format (format 1, set in CEDIT on the 
Logon Format Options screen) requires a special logon procedure if your name 
is "SYSOP".  There are three ways to handle this: 

1)  Using ULEDIT change the name of the user in record 0 (the Sysop record) to 
your own name (instead of "SYSOP").  If you do this, you will be able to logon 
normally ... just enter your first name and last name in the usual manner when 
prompted. 

2)  Some people prefer to use "SYSOP" for the Sysop's name, instead of their 
own name.  In this case, you must use the special Sysop ID at First Name 
setting.  This is configured in CEDIT on the Logon Format Options screen.  
When you logon you enter this special ID at the First Name prompt.  TBBS will 
then skip the Last Name prompt, and move directly to the Password prompt.  You 
then enter the password (as stored in ULEDIT in record 0) in the normal 
manner, and you have successfully logged on.  Note: While if you set this ID 
to SYSOP you can type SYSOP as you expected, it is better to choose an 
alternate ID so that hackers cannot easily locate your SYSOP ID and begin 
trying to find the password. 

3)  Use logon ID format 2, full name.  You can then simply enter "SYSOP" when 
prompted and logon normally. 

- END -
PS0292-2
Rev. 2/92

Copyright (C) 1994 eSoft, Inc., All Rights Reserved.  Permission granted
to distribute this file in its entirety, without modification, to any
interested party.  Any other use requires the written permission of
eSoft, Inc.

IMPORTANT:  The information herein is subject to change without notice.
Please call or write to confirm factual information of importance to you
or your organization.

