Possibilities - Realities 7/90

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 7/90
--------------

*** From July 1990 Possibilities Newsletter ***
*** Copyright 1990 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. 

User-to-User File Exchange Made Easy...

Q. I need a way to send a file to a user privately.  Preferably, users would 
be able to send files privately to each other as well. Private Pseudo-
Directories can't help here -- Is there a way to do this in TBBS? 

A. You're looking for the enclosed file function, which allows you to upload a 
file and associate it with a message entered into the system.  When the 
message recipient reads the message, they can then download the associated 
file during message read operation. 

As a system designer, you can allow or disallow enclosed files on any TBBS 
message board.  In CEDIT MESSAGE BOARD DEFINITIONS, you can enable enclosed 
files for any area by placing a "Y" under the "EF" column for the desired 
message board.  For private user to user file exchange, make certain that 
enclosed files are enabled in conjunction with an E-MAIL message board type.  
If you enable enclosed files in a STANDARD type message board, then any user 
who has sufficient access to read the message will be able to download the 
file enclosed with it.  You can enable enclosed files on any number of message 
boards you wish. 

In CEDIT under MESSAGE BOARD OPTIONS, you set the minimum privilege level 
required to enclose a file in the message (the recipient of the message 
doesn't have any minimum level required to download the enclosed file).  Also 
with this CEDIT screen you designate a special sub-directory on your disk 
which will hold all enclosed files.  The size of an enclosed file is limited 
only by the space available in this directory. 

Enclosed files are maintained by MFSQZ along with the message base.  If a 
message is deleted, the enclosed file remains.  Thus if you un-delete the 
message the file will return with it.  When MFSQZ purges the deleted message 
it will also delete the associated file. 

If a multi-copy message is sent with an enclosed file, only one copy of the 
file is placed on disk.  Each copy of the message will "point" to this file. 
As copies are deleted, the file will not be deleted.  If the message is a CC: 
copy set, then the file is actually attached to the original message.  When 
that message is deleted the file will be deleted as well.  If a distribution 
list is used, then TBBS will generate a special "control" message to which the 
true file is attached.  Only when that message is deleted will the enclosed 
file be removed by MFSQZ. 

Forbidden Fruit?

Q. We're getting an increasing number of users who are calling our TBBS with a 
Macintosh computer.  Can they really transfer files to and from our system 
without losing information?  They've tried to download some MacPaint format 
files from our system and the downloads keep failing. 

A. Both the concerns and troubles you're having center around a single issue -
- the Macintosh file format.  In order to perform some of the unique 
operations possible on a Macintosh, each data file has a "header" that is 
composed of a "resource fork" and a "data fork".  The "forks" allow the Mac to 
know which application is responsible for a particular file's creation and 
maintenance. 

Mac users most definitely CAN successfully transfer files back and forth 
between their Macs and TBBS.  Mac-based telecomm programs usually support a 
feature known as "MacBinary".  Sometimes MacBinary is automatic -- as a user 
you are not aware that it is being added to your transfer protocol.  Other 
times it is a configurable option which you must turn on in your Mac terminal 
software.  In still other cases, MacBinary is identified as a file transfer 
protocol which is really a combination of MacBinary operation with XMODEM 
protocol. 

In any case, MacBinary should be used when transferring files to and from TBBS 
with a Macintosh.  Using MacBinary assures that the file integrity will be 
maintained when uploaded files are later downloaded for use by another 
Macintosh.  When using MacBinary as a protocol selection, Mac users should 
select XMODEM from the TBBS protocol menu. 

You need to be careful when adding Mac format files to your TBBS system 
through any other means than a protocol upload from a Mac.  Some utilities 
designed to share files between Macs and PCs don't transfer the file header 
correctly, and such files may not be downloadable (or usable after download) 
by a Mac user. 

Six Fingers on One Hand...

Q. I wish TBBS had a function whereby a user could press a single key to 
select a single menu entry but execute several TBBS menu functions at once?  
Will a feature like that be in TBBS 2.2? 

A. We're not sure if that specific feature will be in TBBS 2.2 or not, but you 
can perform that function right now in TBBS 2.1! 

The trick is as follows:  Have the desired single key menu selection call 
another menu (using a TYPE=5 command).  On that secondary menu, have all of 
the desired functions appear in order as auto-execute commands (KEY=^@). See 
page 9-6 of your TBBS manual for details.  Make sure the LAST item on this 
menu is a menu return (TYPE=12, Opt Data=1) to go back to the calling menu. 

When a user presses the assigned hot key, all of the auto-executing commands 
on the secondary menu are executed in order, and when finished, the original 
menu is again displayed.  Using this technique, a single hot key can appear to 
execute a number of functions automatically in "batch" mode. 

Eking out More Performance... 

Q. Do you have any tips for squeezing out just a little more performance 
from my TBBS installation?  I just want to make sure I'm getting the best 
speed and response I possibly can. 

A. As you already know, TBBS is one of the most responsive multiuser software 
packages available.  Its intelligent design makes "performance squeezing" 
relatively unimportant.  On slower CPUs, however, at least one tip could help 
performance if you have a RAM disk large enough to handle the job.  Copy all 
of your menu control files (MENU*.CTL) to your RAM disk every time before TBBS 
loads.  Then reference your RAM disk at the beginning of your SET TBBSPATH= 
list in your RUNBBS.BAT (or AUTOEXEC.BAT) file. 

Keep in mind that RAM disk contents are lost when power is lost to the 
computer or the computer is rebooted.  So keep original copies of your menu 
files on conventional disk and copy them to RAM disk each time your computer 
restarts.  No file which changes while TBBS is running should ever be placed 
in a RAM disk. 

You should store those files in a directory other than the default directory 
from which you run your RUNBBS.BAT file.  And be sure you place the RAM disk 
first in your SET TBBSPATH= command as follows: 

SET TBBSPATH=E:\;C:\TBBS

RAM disks are handy, but be very careful not to use extended memory for them 
if you are using an 80286 computer and modem or line speeds faster than 
2400bps.  Extended memory on an 80286 machine causes the CPU to be disabled 
for a fraction of a second, and this can be long enough to cause a loss of 
data on higher speed data lines.  EMS RAM disks are preferable, but some EMS 
RAM disk software cannot handle disk I/O into another EMS buffer (as TBBS 2.1M 
requires if it is also using EMS pages). 

- END -
PS0790-2
Rev. 7/90

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.

