┌────────────────────────────────────────────────────────────────┐
│▒▒▒ Addendum ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│
└────────────────────────────────────────────────────────────────┘
Copyright (c) 1993, 1994, Hamilton TeleGraphics Inc.
────────────
Version 1.04
────────────
■ MAIL
- Missing message problems caused by RoboBOARD have been solved.
Old message areas should be deleted to avoid future problems
with corruption (FASTECHO PACK will usually fix message bases
also).
- Lastread pointers now work correctly
- ROBOPACK.EXE has been added. This utility will pack your message
areas according the value you define in the ROBOCFG message
editor. A value of 0 will turn off packing for any particular
area.
- Private mail is now readable by anyone havine SysOp access to
a message area.
- ERRORLEVEL 2 for echo mail now works.
- ERRORLEVEL 3 for Internet/Usenet mail has been added.
- One line messages fixed.
- PID field in RoboML has been corrected.
- Tearline bug has been fixed.
- Access checking on new mail has been revised so inocent people
won't be shocked by messages they shouldn't see.
- Message REPLIES now correctly place the originating users
name in the destination field of the message writer.
■ FILES
- Number of files marked is now correct when Good-bye option
is selected.
■ DOORS
- One name users will now have a last name of NLM rather than LAST
when DORINFO#.DEF files are used.
- DOOR.SYS locked rate is now correct for people using high locked
baud rates.
- DOOR.SYS node number is now correct.
- Door Entry is now properly documented in the Log File.
■ MISC
- Bugs having to do with user time limits and accesses not being
revised after downloading files, using doors or losing carrier
have been corrected.
- UFNAME variable had an extra space appended to it. This extra
space has been removed.
- Log File now reports NO CARRIER.
- Event enforcing has been slightly relaxed for systems that pass
RoboBOARD the number of minutes till event on the command line.
This allows the time bank to be used within a 120 minute window.
─────────────
Version 1.02a
─────────────
■ Fixed Small bugs:
- "Download A File" command didn't work anymore.
- LAN will not allows user edit in ansi mode now.
- Event handling now properly restores time removed after a
user logs off.
- User's Last Called info is now set to the correct date if
a user starts the call before midnight.
- Small security bug in messages and file resolved.
- Baud rate no longer show up at the port locked rate.
■ DOOR.SYS is now added to a special work directory under
RoboBOARD/FX. The DOOR.SYS file for node one would be found in the
C:\ROBOFX\TEMP_1\ directory.
────────────
Version 1.02
────────────
■ DOS SHARE MUST BE LOADED. The new JAM message bases require SHARE.
OS/2 has automatic file sharing.
■ FXterm 1.02 has been included. For those upgrading from 1.00x to
1.02 you may have to update the TERMINAL NAME field in ROBOCFG.
■ New -FAST command line option allows users like SysOp having an
access of 999 to bypass all NEWS and LOGON screens.
■ Users are now asked if they would like to Log Off after Download.
■ Added ONCE,ONCE1,ONCE2,ONCE3.TFX/ANS/ASC before news screens are
shown. If a picture is newer than the users last called date,
then the user will be displayed the ONCE screen. Handy for READ
ONCE NEWS announcements.
■ New Double Buffered Ansi to enchance DOS/DV/OS2 speed.
■ SysOp Editor in TEXT and ANSI modes. Just hit F10 and it will
pop up.
■ Enforced events have been added. Event management is done
on "by minute basis". Support for the -EVENT # has been
added for event passing. The Time bank is also event friendly.
■ Added support for DOOR.SYS (now we support DORINFO#.DEF and
DOOR.SYS). The Door file format is specified in the menu
editor.
■ Revised ROBOCFG. Fixed several strange happenings. Added 50 line
support. ROBOCFG can be started with a -25 option to force it
into 25 line mode for doorway compatibility.
■ Greatly enhanced ANSI interface.
■ FILE and MESSAGE area selection windows now stay up for user
convenience.
■ ****** 100TO102.EXE ****** If you are converting from version
1.00x to 1.02 then you MUST run 100TO102.EXE. This will add
proper paths to existing MESSAGE and FILE areas.
■ Changed file system over to new FF (FASTFILE) format. A utility
called FBS2FAST has been provided to convert the 1.00-1.00e FBS
file format to the new xDB format. All your NEW XDB databases
should now be found in ROBOFX\FILES directory. The utility
named 100TO102.EXE will adjust the new DATABASE FILE field
to point to the ROBOFX\FILES directory. After you are certian
the conversion was successful you may remove the xDB files from
your ROBOFX\ROBODATA directory.
Why is there a path to the file database now? The reason is
fairly simple. On a system with 200 file areas, there will be
800 xDB files (4 files per DataBase). Due to a DOS limit this
will cause a file access slow down (dos seems to REALLY slow
down after 512 files). Our suggestion for BBS's using many
CD-ROMS is to seperate your file databases into seperate
directories named after the CD-ROMS they represent.
The FF format can have up to 10 lines of description and a
classification icon. Benchmark searches on 500 file databases
with a total number of 240,000+ files have resulted in search
times of 15-25 seconds depending on the query type.
Here is an example of how to set up a FASTFILE area:
╔═ File Area ═══════════════════════════════════════════════════════╗
║ ║
║ Area Name [New Files_________________________] ║
║ Path To Files C:\ROBOFX\FILES\NEWFILES\_________ ║
║ DataBase File C:\ROBOFX\FILES\NEW_______________________ .xDB ║
║ ║
║ Storage Type HARD DRIVE ║
║ Sort Method ALPHA (Z-A) ║
║ ║
║ Forum 1__ (0=ALL) ║
║ ║
║ View Access 4__ tags __________________________ ║
║ Download Access 5__ tags __________________________ ║
║ SysOp Access 999 ║
║ ║
║ DONE ║
╚═══════════════════════════════════════════════════════════════════╝
■ This version uses a JAM message base. So far GECHO, FASTECHO and
XMAIL are the only tosser/scanners who actually shipping with JAM
support. FMAIL, IMAIL, TOSSCAN, INTERECHO and RAECHO are supposed
to be coming out with it any time. Unlike HUDSON where message
bases had a AREA #, Jam has a PATH and BASE NAME. For those of
you updating from 1.00x to 1.02 you should run the utility named
100TO102.EXE, this will add a path to your existing message base
definitions.
Message areas each have there own unique database name and may be
stored in a single directory or multiple directories. The old
AREA # field has been changed to BASE PATH & NAME. Here is an
example of the new MESSSAGE AREA naming convention:
<PATH>\<NAME>
or
C:\JAMMAIL\ROBONET\ROBONEWS
In the prior example ROBONEWS is the JAM message base name, and
C:\JAMMAIL\ROBONET is the MAIL directory where this mail will be
stored.
Here is an example of how to set up a JAM message area:
╔═ Message Area Settings ══════════════════════════════════════════════╗
║ ║
║ Name [General Mail______________________] ║
║ Base Path & Name C:\ROBOFX\MAIL\GENERAL____________ ║
║ ║
║ Area Type LOCAL ║
║ Msg Settings PRI/PUB ║
║ File Attaches YES ║
║ Name Style REAL NAME ║
║ ║
║ Forum 1__ (0=ALL) ║
║ Read Access 0__ Tags __________________________ ║
║ Write Access 0__ Tags __________________________ ║
║ SysOp Access 999 ║
║ ║
║ Msg Tag Line RoboBOARD/FX 1.00 | Number One by Default!________ ║
║ System Addr ____________________ ║
║ ║
║ DONE ║
╚══════════════════════════════════════════════════════════════════════╝
■ Added support for NETMAIL, USENET, INTERNET mail addressing and
reading. ROBOUUCP will provide gateways to USENET and INTERNET,
NETMAIL must be gated with some sort of gateway utility provided
with your tosser or scanner.
■ Added flow control options.
■ Added LAN IO device for local lan logins, also added -LAN option.
LAN mode removes the SysOp interface from the bottom of the screen.
■ File attaching to messages added.
────────────-
Version 1.00e
─────────────
■ Overlays will now use XMS or EMS. XMS is faster so RoboBOARD/FX
will attempt to use it first. For those of you using DOS 5 or
DOS 6 and without QEMM386 or 386MAX, you may be interested in
removing EMM386 from you CONFIG.SYS. This will free up 64K of
high memory that can be used for the high loading of TSR's and
Device Drivers. (Other programs may require EMM386). Under OS/2
EMS support will slow down your Virtual DOS sessions.
■ Uploads no longer debit time from your users.
■ Revised LastRead tracking in message areas.
────────────-
Version 1.00d
─────────────
■ Uses new memory manager. Stops lost clusters, and as is more
robust.
■ New overlay buffering system. Allows RoboBOARD/FX to run in less
memory. For systems with ample conventional memory, performance
will be higher.
■ Better support for multi-taskers. Particularly DESQview and OS/2
virtual dos machines.
■ Flow control correction
■ JPEG quality and speed improved.
■ Messages to "SYSOP" are redirected to the SysOps name.
■ Sysop may delete public messages that are not addressed to them.
■ Pointer errors corrected. This should solve a few lockups.
■ The occasional loss of user password and phone number data has
been solved.
──────────────────────────────-
Version 1.00a/1.00b/1.00c/1.00d
───────────────────────────────
■ RunTime 204 error on logon timout fixed. (1.00c)
■ Added note to ADDENDUM (below) about EMS.
■ Changed exit ERRORLEVEL to 5 in RUN-ROBO.BAT... this doesn't
affect anything if it is left at 1 in your old BATCH file but
should be changed to 5.
RUN-ROBO.BAT
------------
@ECHO OFF
CLS
:TOP
ROBOFX
if ERRORLEVEL 5 goto DONE
goto TOP
:DONE
echo RoboBOARD exited!
echo.
■ Call Back problem resolved (v1.00a).
■ Fixed some DORINFO#.DEF problems (v1.00b).
■ Added CDROM importer into the ROBOCFG FILE MANAGER (v1.00b).
Now supports more formats of FILES.BBS directly.
From the file manager you may now import both FILES.BBS and
SFFILES.BBS listings from your CDROM directory listing
directly.
A new command is also available from the sidebar. It is called
IMPORT. If you press "I" or select the IMPORT button, a window
prompting you for the PATH & NAME of a description file will
be displayed.
■ Trident/Oak problem resolved (v1.00b).
This bug fix resolves problems where RoboBOARD/FX locks up in
ANSI/ASCII mode.
■ Fixed Ellipsoid in FXDRAW.
■ Fixed JPEG deletion in FXDRAW.
■ Lock up on NEW USER template fixed/realised. This problem has
to do with memory allocation. We were able to greatly reduce
the amount of memory required for the new user process, however
one still has to meet the minimum memory requirements.
■ Adjusted Overlay buffers. Overlay buffers now have a sliding
size based on the amount of free memory.
For speed purposes, certain code was shifted in or out of the
overlay. This will greatly increase system response (especially
under DESQview), and will resolve the "SysOp to User Chat Problem".
The side effect is that RoboBOARD/FX requires the following:
- 480-500K under DV (No Graphics)
- 550K under DOS (With Graphics)
- 512K EMS (for Overlay management under or DOS & DV)
* Use the MEM command (in DOS) to see your systems memory usage.
■ Revised & improved templates. The following statements may be
added to any RoboBOARD/FX template:
*SET,<#>,<VALUE> - Any number of *SET commands may be added to
a template. The *SET command can only be
issued after the *VAR section and before the
*PLATE command. The <#> parameter should be
filled with a valid input variable register
number. The <VALUE> parameter should be
filled with the text string you would like
the register filled with. This text string
may contain DISPLAY TOKENS.
eg: *SET,1,{UNAME}
*PREPIC,<PICNAME> - The *PREPIC command must be placed before
the *PLATE command. If a *PREPIC is defined
RoboBOARD/FX will display the desired image
before the user enters the template. You may
put a button on the picture to stop it. The
<PICNAME> field should contain a file name
without extension.
*DONEPIC,<PICNAME> - The *DONEPIC command must be placed before
the *PLATE command. If a *DONEPIC is defined
RoboBOARD/FX will display the desired image
if the user clicks [DONE] on the template.
You may put a button on the picture to stop
display. The <PICNAME> field should contain a
file name without extension.
*EXITPIC,<PICNAME> - The *EXITPIC command must be placed before
the *PLATE command. If a *EXITPIC is defined
RoboBOARD/FX will display the desired image
if the user clicks [EXIT] on the template.
You may put a button on the picture to stop it.
The <PICNAME> field should contain a file name
without extension.
───────────────────────────────────────────
Documentation Revisions for v1.00 --> 1.00d
───────────────────────────────────────────
NOTE ABOUT EMS and XMS:
RoboBOARD/FX requires 512K of XMS. This memory is used for Overlay
management. EMS will also work and may also exist in your system.
Without the 512K buffer, your disk will be used as the paging area. The
following are ways to get 512K (or more) XMS or EMS for RoboBOARD/FX.
XMS UNDER DOS (Recommended over EMS)
Use the HIMEM.SYS driver supplied with DOS 5 or 6. This is preferred
over EMM386 and EMS, as it is faster, and does not require the
64K page frame area (which can be better used for the High Loading
of TSR programmers). QEMM386 and 386MAX provide XMS and EMS, however
XMS will be used over EMS always.
EMS UNDER DOS 5 (Without 386MAX or QEMM)
Install HIMEM.SYS and EMM386.SYS in your CONFIG.SYS. Consult your
DOS manuals for examples. EMM386.SYS will provide EMS services but
will also use 64K of upper memory for paging. Make sure you also
have the lines DOS=UMB and DOS=HMA in you CONFIG.SYS.
EMS UNDER DOS 6 (Without 386MAX or QEMM)
Install HIMEM.SYS and EMM386.SYS in your CONFIG.SYS, or run
MEMMAKER which will do this for you. It is important to answer
"Y"es when asked if you run programs which use EMS. MEMMAKER
will also load additional device drivers and TSR programs into
high memory freeing up conventional memory for RoboBOARD/FX.
EMS/XMS UNDER DOS # WITH QEMM386
Qemm 7.01 by Quarterdeck will allow you to operate with the
required EMS. QEMM allows your memory to be both EMS or XMS
for applications which like either. QEMM386 will also move
your TSR and device drivers into high memory. If you run
DOS 6 DOUBLESPACE then you may want to check out QEMM386 as
it will eliminate the 44K used by the disk drivers.
EMS/XMS UNDER DV WITH QEMM386
Under program setup on the "Advanced Options" menu be sure to
specify 512K EMS/XMS/VCPI/DPMI. It is also suggested that you
set "Maximum Program Size (in K)" to 640, and "Memory Size" (on
the "Standard Options" menu) to 128K. XMS will be used over
EMS always.
1) CORRECTION: On page 133 of the printed manual (Page 105 Digital
DOCs) the Transmit and Receive buffers are set incorrectly.
The X00 CONFIG.SYS Fossil settings should read:
DEVICE=C:\FOSSIL\X00.SYS E 2 T=4096 R=4096 B,1,19200 F=8
Note: Even if you have a 16550 UART it is necessary to turn
the Fifos on by setting F=8
2) ADDED. Alt C will activate Sysop/User chat from any menu.
3) ADDED. RoboBOARD/FX keeps a log file of every users activity on
your system. This Log file will continue to grow until it uses
up your hard drive unless you maintain it. It is named:
ROBO_1.LOG (Note: that the _1 refers to the Node that is being
logged so every node has its own log file.)
If you do not want logging to take place on your system then
create an event that deletes it weekly, or daily. You can also
include a line in the BATCH file that drives RoboBOARD to delete
ROBO_1.LOG after each caller.
4) ADDED. RoboBOARD/FX maintains a daily log file that contains the
names of everyone that calls during the 24 hour day. This file is
called DAY_CALL.LOG and it is a self maintained file. It is
automatically deleted when the first caller after midnight logs
on to your system and is replaced with a new DAY_CALL.LOG.
5) ADDED. Two new Inline Text Token have been added:
{LCALLER} - Displays the Last User who called.
{UEXP} - Displays the users Expiry date on your system.
9) NOTE: If you are using nonstandard Interrupts or Serial Port
Addresses use the Fossil Driver, X00 by Ray Gwinn.
10) SUGGESTION: Typically for most users the default UART support we
provide will be faster then using a Fossil.
11) ADDED: There are 12 allowable template string variables now
instead of 8. They are named:
STRING9
STRING10
STRING11
STRING12 (refer to page 118 of the printed manual
page 92 of the Digital Docs)
12) ADDED: A new Menu Command has been added called:
[ (Window) Close Window on Exit ]
This menu command will close a window completely when a user
exits the menu. When this Menu Command is chosen in the Menu
Editor a notice will pop up saying:
" This Command will cause the Current Window to close upon Exit
for graphical users. "
In text mode windows are always cleared.
13) WARNING!: There is a practical limitation to the number of menus
that can be displayed at one time. We suggest that no more than
five (5) menus be displayed at one time for reasons of temporary
storage on the users end. Refer to point 12 for an explanation
of how to limit the number of windows that are displayed at one
time.
14) WARNING!: On multiline systems don't operate ROBOCFG and change
user settings while users are on line.
15) WARNING!: Just another reminder to back up your configuration,
userbase, drawings etc. It is a very good idea when using
computers to back up any data that is of value to you.
16) CLARIFICATION: Page 34 manual, and Page 26 DOCs. If an Access
Level is set in the User Editor for a user and no Access Profile
exists for that Access Level, RoboBOARD will automatically assign
the next LOWER valid Access Profile to that user.
ie1: - USER Name - Bill Smith - Access 17 is set in User Editor.
- No Access Profile has been created for Access Level 17.
- Access Level 5 is the next lower Access Level that has a
valid Access Profile created for it.
- Bill Smith gets the Access Profile for Access Level 5 but
he is evaluated for Menu Command Access based on Access
Level 17 set in the User Editor.
ie2: - USER Name - Bill Smith - Access 17 is set in User Editor.
- No Access Profile has been created for Access Level 17.
- Access Level 5 is the next lower Access Level that has a
valid Access Profile created for it.
- The required file ratio, kilobyte ratio, daily files
allowed, and daily time fields have been filled in, in
the User Editor specifically for Bill Smith.
- Bill Smith gets the required file ratio, kilobyte ratio,
daily files allowed, and daily time fields from the
User Editor and he is evaluated for Menu Command Access
based on Access Level 17 set in the User Editor.
- Bill Smith does NOT get Access Profile 5.
17) OBSOLETED: Global Change command in user editor. Page 38 - 39
in the Printed Manual and page 31 in the Digital Docs. This
command was no longer required after we changed the logic
involving User Profiles and Access Levels during beta testing.
18) NOTE: ANSI screens created in ANSI drawing packages like TheDraw
must be 20 lines or less.
19) REQUIREMENT: RoboBOARD/FX and FXdraw requires 512k of EMS for its
Overlays. It will not run without it.