Category : BBS Programs+Doors
Archive   : 1EDRA201.ZIP
Filename : 1EDIT-RA.DOC

Output of file : 1EDIT-RA.DOC contained in archive : 1EDRA201.ZIP

³ ³ -*- 1-EDIT-RA -*- ³ ³

Version: 2.01




Bob Ransom

Copyright (c) 1990
All Rights Reserved


What Is 1-EDIT-RA? .............................. 2
Acknowledgements ................................ 3
Shareware & Warranty ............................ 4
FOSSILS, ANSI.SYS & Other Requirements .......... 5
LOCAL.DEF File .............................. 5
Locked COM Ports ............................ 7
Command Line Syntax ............................. 8
Colors ...................................... 8
Drop To DOS Security ........................ 8
Getting Started ................................. 9
Setting Up 1-EDIT-RA Within RemoteAccess .... 9
The MENU Editor ................................. 12
The USER Editor ................................. 13
Mass User Updates ........................... 13
Drop To DOS ..................................... 15
Local Drop To DOS ........................... 15
Remote Drop To DOS .......................... 15
Using 1-Edit-RA On Multi-Node Setups ............ 17
The "-N" Parameter .......................... 17
The "-U" Parameter .......................... 18
Registering 1-EDIT-RA ........................... 19
Keys ........................................ 19
Installing Keys ............................. 19
Final Notes ..................................... 21

1-EDIT v2.01 Page 1


1-EDIT-RA is a combined User Editor and Menu Editor for
RemoteAccess systems designed to work reliably from
remote. Features include:

- Built-in FOSSIL routines for guaranteed remote

- Full carrier detection which returns to
RemoteAccess when carrier is dropped.

- Automatic high speed performance with locked
ports at up to 38,400 baud (and possibly

- Ability to work in multi-node setups.

- Status line showing user name, baud and modem
settings, and time remaining (registered

- User-definable colors.

- Full editing capabilities of nearly all fields
in the USERS.BBS file.

- Mass flag updating of user records.

- Mass "High Message Read" updating of all user

- Full menu editing capabilities including
adding, deleting, renaming, and copying menus,
plus direct editing of each line of the menu
record. Direct editing allows you to insert,
delete, change, and list the lines of the edited
menu, plus full menu simulation.

- Small file size: the program is only around
75K and will run in about 93K of memory. This
allows 1-EDIT-RA to run easily from a Type 7

1-EDIT v2.01 Page 2


A big "Thank You" goes to all those trusting souls who
beta tested this version of 1-Edit-RA, risking life and
limb (not to mention their BBS's) to see if this thing
actually worked. Thanks to Mark Oberg, Mark Martin, Mehdi
Attaran, Rod Hancock, and Lee Anderson. These folks not
only tested the software but made many suggestions for
improvement in it.

Thanks also to John Parlin for his JPDOOR Turbo Pascal
FOSSIL and door interface. Working with JPDOOR makes door
writing a breeze if you're working in TP. Some background
on this: When I began work on this program quite some
time back, I wrote my own set of low-rent FOSSIL routines.
They worked but, well, elegant they weren't. Then I found
JPDOOR. I took a look at it, shouted "Eureka!" loudly,
and promptly trashed all my own stuff and replaced it with
his. If you're interested in writing doors with Turbo
Pascal, take a look at John's package. Registration is
only (or was when I registered anyway) $15 and it is
*very* complete. The current version as I write this is
JPDOOR27.ZIP. This includes the needed .TPU's for Turbo
Pascal v5.5. Units for other versions of TP are probably
still available from John. This software was developed
and compiled using older units for TP 5.0.

Special thanks also go to Mike Janke for his original help
in converting the data structures used by this program
from QuickBBS to RemoteAccess, and also for his
suggestions on making 1-Edit-RA finally multi-node

1-EDIT v2.01 Page 3


Here comes the dull but necessary stuff:


This program is released to the public as shareware. This
means try it and if you like it you must register it
within a reasonable amount of time. The program is not
freeware nor public domain; it is copyrighted material
with all rights reserved. You are granted only a limited
license to test this software. No changes whatsoever may
be made.

You may copy 1-EDIT-RA and transfer it to others provided
you follow these brief rules:

1- You may not change the program, its archive, or its
documentation in anyway without express written consent
from me, the author.

2- You may not sell the program. This program may be
distributed on pay systems, but not on a
"fee-per-download" basis.

3- You may not distribute this product with other products
without express written consent from me.

Registration of 1-EDIT-RA is a cheap $10 and covers you
for all future releases of the program. More information
on registering is included later in this document.


No warranty of any kind, covering either hardware or
software damage, is expressed nor implied. Use this
program at your own risk.

1-EDIT v2.01 Page 4


There are a few things you should know before attempting
to boot 1-EDIT-RA for the first time:


1-EDIT-RA requires a FOSSIL driver to be installed and
active at all times. This shouldn't prove to be much of a
hindrance since 1-EDIT-RA was designed for remote use. If
you are editing strictly from the local console, RACE and
RAMenu do the same job faster and nicer, and they *don't*
require a FOSSIL. (However, they're not meant for remote
use, either.) 1-Edit-RA has been tested with both the X00
driver and the BNU driver; both work fine. One note to
BNU users who use the TSR version of the program: Be sure
that you're not having BNU remove itself from memory when
you exit your BBS and/or mailer.

ANSI Graphics

1-EDIT-RA requires all users of the program to have the
ANSI.SYS driver installed - both on the BBS and remote
caller's systems. 99.9% of sysops do have it installed so
this shouldn't be a problem. If you're unfamiliar with
ANSI.SYS, see your DOS manual. ANSI.SYS is included with
all versions of DOS.

I've received a few messages from sysops who would prefer
that the program *not* use ANSI as they do their remote
work from non-ANSI machines (like VT-220 terms on a VAX).
I'll be addressing those needs in a future version (as
soon as I figure out a clean way to do all the screen
manipulations that 1-Edit-RA does without ANSI). I'm not
using ANSI so much for color changes as I am for cursor
placement, etc.


1-EDIT-RA requires a DORINFO1.DEF file to be present when
starting. First, some background on this file and how to

1-EDIT v2.01 Page 5

get around the necessity of having it: When RemoteAccess
shells to another program, either through a menu Type 7
exit or a menu Type 15 exit, it creates two files in your
system directory (or LINEx directory on multi-nodes):
DORINFO1.DEF and EXITINFO.BBS. Both contain information
for the child program to use in determining the user's
name, baud rate and modem settings, graphic settings, etc.
When you return to RemoteAccess from the shell,
RemoteAccess deletes both of these files. That's why you
can never find them on your disk -- they're already gone.

Because 1-EDIT-RA requires DORINFO1.DEF and because a copy
won't always be available, I've made the program search
for a second file called LOCAL.DEF. LOCAL.DEF is nothing
but a copy of DORINFO1.DEF which should stay in your main
RA system directory (usually "C:\RA"). When run,
1-EDIT-RA will first search for the DORINFO1.DEF file. If
it's not found, it will then try to find the LOCAL.DEF
file. If that's not found, the program aborts. If it
*is* found (remember, you're supposed to leave it on your
disk so it should be there), 1-EDIT-RA will copy it over
to DORINFO1.DEF. When you quit 1-EDIT-RA, the
DORINFO1.DEF file will be deleted.

A copy of LOCAL.DEF is included in the 1-EDIT-RA archive
which you may edit to reflect your name and system name.
Here's what it looks like with my comments in braces { }:

BOB {Sysop first name}
RANSOM {Sysop last name}
COM0 {Don't edit this!}
0 Baud,N,8,1 {No need to edit this}
0 {This does nothing - just a zero}
BOB {User first name}
RANSOM {User last name}
LATHRUP VILLAGE, MI {No need to edit; not used}
1 {Graphics. Unused by 1-Edit-RA}
32000 {User security level}
235 {User time remaining}

Feel free to edit your copy of LOCAL.DEF to reflect the
proper sysop names and user names. The COM port setting
MUST remain as COM0 -- this indicates a local connect.
Changing the security and time remaining is up to you.
Time remaining is not counted while in local. After
editing, place the LOCAL.DEF in your RA system directory
and leave it there.

1-EDIT v2.01 Page 6

Locked COM Ports

Locked COM ports are supported automatically by 1-EDIT-RA.
There is no need to use DorSpeed, SetSpeed, etc.
1-EDIT-RA has been successfully tested at speeds up to
38,400 baud.


1-Edit-RA may be run from any directory you choose. When
first started, it searches your DOS environment for "SET
RA=", then uses that path to find the CONFIG.RA,
DORINFO1.DEF, and LOCAL.DEF files. (Note to multi-line
sysops: See the special section below on modifications
you can make to force 1-Edit-RA to search elsewhere for
these files.) If you don't have the RA environment
variable set (you should already), please set it. See
your RA docs for more info.

Also, 1-Edit-RA expects to find your USERS.BBS in the path
defined in CONFIG.RA as "Message base directory." Your
CONFIG.RA should already be pointing to the proper
directory. (This may also be changed with command line
parameters. See the "Multi-Node" section of these docs.)

Okay, that takes care of the requirements. Now, you've
unZIPped the 1-EDIT-RA file and put it somewhere on your
hard drive, and put the edited LOCAL.DEF into your RA
system directory. Now you're almost ready to get started.

1-EDIT v2.01 Page 7


1-EDIT-RA allows you to customize it somewhat via the
command line. Five parameters may be included if you wish
(they're optional):

-Nxxxxx Tells 1-Edit-RA to look in path xxxxx for the
DORINFO1.DEF and/or CONFIG.RA files. See
"Multi-Node" section for more info. Example:
"-Nc:\ra\line1" A trailing backslash is

-Uxxxxx Tells 1-Edit-RA to look in path xxxxx for the
USERS.BBS file. Example: "-Uc:\ra\users"
A trailing backslash is optional.

-Fxx Sets foreground color to xx. xx must be 0-7.
Default color is cyan (#3).

-Hxx Sets the highlight color to xx. xx must be 0-15.
Default highlight color is bright yellow (#14).

-Sxxxxx Sets the minimum security level for the Drop to
DOS feature to xxxxx. xxxxx must be 0-64000.
Default is 32000. More on this feature later.

? Brings up very short help screen describing
command line parameters.

None of these parameters are required; use any, all, or
none of them as you choose. The command line may be in
upper case or lower; it doesn't matter.

1-EDIT v2.01 Page 8


With that boring stuff out of the way, we'll get on to the
meat of the program. I'm not going to bother taking you
through each and every option in the editors -- most
commands are pretty self-explanatory, so I'll just touch
on most of it and highlight oddities, etc. Any sysop that
has gotten a RemoteAccess system up and running shouldn't
have any problems.

Setting Up 1-EDIT-RA Within RemoteAccess

1-EDIT-RA has been tested under both a RemoteAccess Type 7
exit and a Type 15 exit; either setup will work just fine.
However, because of its small size, 1-EDIT-RA is probably
best run as a Type 7 except on systems with very tight
memory constraints (i.e. some Desqview and DoubleDOS
systems). For Desqview/DoubleDOS users: As best as I can
tell, 1-EDIT-RA runs in about 84K of memory.

Here's a sample of how a Type 7 setup would look from
within RAMENU:
Edit Menu Item

1 2 3 4 5
<^1^> ............ Run 1-EDIT-RA Editor

Optional Data:
1EDIT-RA.EXE -F7 -H15 -S100

User Display
Action Execute sub-program (Type 7)
Optional data
Hot-Key 1
Automatic No
Colour Colour example
Security 32000
Flags-A --------
Flags-B --------
Flags-C --------
Flags-D --------


1-EDIT v2.01 Page 9

As mentioned earlier, the -F, -H, and -S command line
parameters are completely optional; leave them off if
you're happy with the defaults.

Here's an example of the RAMENU setup for a multi-node
Edit Menu Item

1 2 3 4 5
<^1^> ............ Run 1-EDIT-RA Editor

Optional Data:
1EDIT-RA.EXE -Nc:\ra\line*N -Uc:\ra\users -F7 -H15 -S100

User Display
Action Execute sub-program (Type 7)
Optional data
Hot-Key 1
Automatic No
Colour Colour example
Security 32000
Flags-A --------
Flags-B --------
Flags-C --------
Flags-D --------

See the section on multi-node setups for more information
on the -N and -U parameters.

Actual Startup

When you first start 1-EDIT-RA, it will check to see that
a FOSSIL is present. If not, the program aborts. From
there it begins its search for CONFIG.RA and DORINFO1.DEF,
using LOCAL.DEF if necessary. Some values are
initialized, then an opening screen pops up. If you
haven't registered your program yet, the program will ring
the bell a few times, then pause for 4 seconds to
encourage registration. After the pause you'll be
prompted to "Press [ENTER] to continue:". Press enter and
you'll get the main menu.

From the main menu you may choose to edit user files, menu
files or drop to DOS. At this point, registered versions
of 1-EDIT-RA will show a status line on the local console

1-EDIT v2.01 Page 10

detailing who's online, baud and modem settings, and time
remaining. Unregistered versions show only the line
"Unregistered Evaluation Copy."

A side note that applies here and throughout most of the
program: Pressing [ENTER] or entering a question mark will
redraw the screen. This is really only useful in times of
high line noise, but it's nice to have available when you
need it.

1-EDIT v2.01 Page 11


Those of you familiar with Adam Hudson's original Menuedit
will feel right at home here. When you first choose the
menu editor from the main menu, you'll be presented with a
directory of the menus in your RemoteAccess menu area.
1-EDIT-RA uses the CONFIG.RA file to determine the path to
this area. After displaying all of the menus you'll have
the option of editing/adding a menu, renaming a menu,
copying a menu, deleting a menu, or relisting the files.

There's no need to explain most of these functions. One
thing you might like to know is that any rename, delete,
or copy operation can be stopped by pressing [ENTER] on a
blank input field.

Choose the option and you'll be prompted for the menu
filename to edit. Input the name. If the menu isn't
found, you'll be asked if you wish to create it. After
entering the menu name, you'll be dropped onto the main
menu editor menu. From here you can do a variety of
things, all very similar to the same functions in

Rather than beat a dead horse trying to detail each
section of this menu, you should just play with it a bit.
It's pretty easy. Start by copying a menu, any menu, to
another menu file called, maybe, TEST or FRED or
something. Then hack on that copied menu. You'll get the
hang of it pretty quickly (like instantly, I hope).

1-EDIT v2.01 Page 12


Most all of this section should be pretty easy to figure
also. For the most part, everything is self-explanatory.
Press the plus key (+) for the next user or the minus key
(-) for the previous user. When moving from user to user,
if you hit the beginning or end of the USERS.BBS file, the
program will "wrap around" for the next user. Example:
You come to the last user in the file, say user #100, then
press the plus key (+). 1-EDIT-RA will "wrap around" to
user #0.

Pick and choose the fields you need to edit, press the
bracketed key <>, and you edit to your heart's content.
One note of interest: Should you go to edit a field and
then decide not to change anything, just press [ENTER]
over a blank field and that field will remain unchanged.

At the bottom of the screen, you'll see a small window
with choices to add a user, delete a user, toggle NO-KILL
and other flags, etc. uit takes you back to the main
menu. ther clears this small window and replaces it
with a different set of options that allow you to make
mass updates to flags or high message read numbers (see
below), and to edit some of the other user fields that
aren't often edited. To return to the first set of
options, press again.


From the ther window, you have the ability to do mass
updates to flags and high message read numbers. What's
this good for? Well, a couple of things:

Some of you use a combination auto-executed menu options
and flags to show your BBS users a news file. After they
read the file, you set that flag to OFF. When you create
a new news file, you must go back and turned everyone's
flag back on again. Mass Flag Upd. allows you to do that.
You're asked for the flag you wish to set (A, B, C, or D),
the flag position to set (1-8), and whether you want it on
or off. After entering the information, 1-EDIT-RA will go
through and reset that flag bit for each user in the

1-EDIT v2.01 Page 13

Mass updating of high message read is usually good after
you either bomb your message base, or do a slightly messed
up message renumber. I've had a few occasions where my
message base has gotten destroyed and I've had to delete
all the files. After doing so, all the user records still
contain the old high message read numbers, so the users
all get the "No new messages" line when they attempt to
read new messages. Using this mass update option lets you
reset everybody's high read number back to 0 (or whatever
number you want).

1-EDIT v2.01 Page 14


This feature can be both very useful and very dangerous,
to use the Drop to DOS feature, be sure your CONFIG.SYS
file sets COMSPEC=. 1-EDIT-RA uses
that DOS environment variable to tell it where to find
COMMAND.COM. For more info on CONFIG.SYS files and
setting COMSPEC, see your DOS manual. If you wish to test
whether COMSPEC= is set or not, type SET at any DOS
prompt. This will cause DOS to display your environment

When displaying the main menu, 1-EDIT-RA checks the users
security level (set in DORINFO1.DEF) against the security
level set on the command line (or the default, 32000). If
the user's level equals or exceeds that level, the Drop to
DOS function appears on the main menu. If the user's
security level is *less* than the specified level, the
option doesn't even show up on the menu. This allows you
to have co-sysops be able to edit your BBS files without
actually cutting them loose in DOS.

Drop to DOS works in two different ways, depending on if
you're online locally or from remote:


When in local mode, the drop to DOS is just a very simple
shell. You hit "D" and you get the familiar flashing
cursor. (What actually happens is a second copy of
COMMAND.COM is loaded.) You may run whatever files you
need to run from here. When ready to return to 1-EDIT-RA,
simply type EXIT.


Things become a bit more complicated when dropping to DOS
remotely because 1-EDIT-RA goes on hold during the shell.
This is similar to Type 7 and Type 15 exits out of
RemoteAccess -- when you shell out, you loose RA's ability
to send things through the modem, watch carrier and time
remaining, etc. The same happens when you shell out of

1-EDIT v2.01 Page 15

1-EDIT-RA -- whatever you shell to *must* take over all
modem functions including FOSSIL interface, carrier
detect, etc. Because of this, a warning pops up when
executing the shell reminding you not to go and try to
load WordPerfect or some other program that has no modem

To make this perfectly clear, I'll repeat this in shouting
OWN. 1-Edit-RA WILL NOT DO IT! Okay, enough shouting.

When you do execute the shell, you're prompted to enter a
filename to execute. Leave this field blank and 1-EDIT-RA
will return to the main menu. If you do execute a program
THE FILENAME (i.e. ".EXE", ".COM", ".BAT"). You may also
include as many command line parameters as you can fit
into the field. These parameters will be passed on to the
child program. When you exit the child program, you'll be
returned automatically to 1-EDIT's main menu.

A sample batch file called DOSSHELL.BAT is included in the
archive for you to look over. It details how you can set
up a true drop to DOS from 1-EDIT-RA using CTTY COMx or (a
better method using Gateway) CTTY GATEx. THIS IS NOT
guide. If you try this out, be sure to pass your baud
rate to the batch file on the command line as:
DOSSHELL.BAT 2400 (or whatever rate you're using). This
batch file should be looked at and tested CAREFULLY before
relying on it!!!! Also, I'd suggest that you make sure
you run WATCHCD or some other carrier detection TSR before
anything else. WATCHCD (and the related BOOT.COM) is
available inside the archive of any version of X00.

Better yet, get a copy of DOORWAY, a wonderful program
that lets you run almost anything through the shell with
complete carrier detection. It's shareware and
registration is pretty inexpensive.

1-EDIT v2.01 Page 16


The first versions of 1-Edit-RA (v1.0, 1.0a, and 1.01)
didn't work too well with multi-node RemoteAccess setups.
Okay, let's be honest: They didn't work at all. With
v2.00 that's been changed.

First things first: You need to do nothing at all to get
1-Edit-RA to share files with RemoteAccess. That is
automatic and has been tested on both Desqview setups and
various LAN setups. You will, however, probably want to
take advantage of the two command line parameters designed
specifically for multi-node setups.

But, first: When running a multi-node RA system, you will
typically have your directories set up similar to this:

C:\RA = Main System Directory. RA environment
variable points here.

C:\RA\LINEx = Separate directories for each node that
you operate, where "x" equals the line

Your actual directory names may be different though most
people seem to follow this example (as outlined in the RA

Under single line setups, your CONFIG.RA file lives in the
System directory. This is also where RA puts the
DORINFO1.DEF file when executing a Type 7 or Type 15 menu
option. Under multi-node setups, the DORINFO1.DEF file is
placed in the line directories (C:\RA\LINEx). Also, many
sysops have two or more different kinds of modems,
requiring CONFIG files for each modem (for different
initialization strings, etc.) In these cases the sysop
places the extra CONFIG files in the line directories so
that RA will use the proper CONFIG setup with the proper


When 1-Edit-RA detects the -N parameter on the command
line, it will search the directory specified after the -N
for both the DORINFO1.DEF and the CONFIG.RA files. If the
files are found, they will be used rather than whatever

1-EDIT v2.01 Page 17

may be in the System directory. If either file is not
found in the specified directory, 1-Edit-RA will then
search for it in the System directory. In the case of the
CONFIG.RA file, if it's missing from the specified line
directory and missing from the System directory (almost
impossible if your system actually works), 1-Edit-RA will
abort. In the case of the DORINFO1.DEF file, 1-Edit-RA
will first search the specified line directory, then the
System directory. If the file isn't found in either
place, 1-Edit-RA will search the System directory for the
LOCAL.DEF file (see above). There's no need to put a copy
of LOCAL.DEF into each of your line directories; 1-Edit-RA
won't find them there. One copy of LOCAL.DEF in the
System directory is all that's required.

Here's an example of the -N command line parameter in use:

1EDIT-RA.EXE -Nc:\ra\line1


1EDIT-RA.EXE -Nc:\ra\line*N

A trailing backslash is optional. Note the "*N" in the
second example. This utilizes a feature of RA in which RA
will substitute the current line number for the "*N" when
executing a Type 7 or Type 15 exit. More information on
this and other RA exit parameters is available in your RA


This parameter tells 1-Edit-RA to use the USERS.BBS file
in the directory specified after the -U. Example:


As before, the trailing backslash is optional. This is
probably not going to be the most used parameter of the
bunch. As far as I can tell, most folks maintain a single
USERS.BBS file for all lines of their system. However,
there may be (and probably are) some sysops who maintain
separate user bases for each of their nodes. Maybe one
for business and the other for the general public. Anyway,
you have the option should you wish to use it. One thing
to note about this parameter: If 1-Edit-RA can't find the
USERS.BBS in the directory you specify, it will NOT look
anywhere else for it. It will simply abort with an error

1-EDIT v2.01 Page 18



1-EDIT-RA uses a "keyed" registration system. The
information used to create your key is your system name
and sysop name as contained in your CONFIG.RA file.
Unregistered versions of the program (programs running
without the key) ring the bell and have a 4 second pause
built in at the beginning of the program, plus the status
line is disabled. Registered versions will also show the
registered system name and sysop name during the opening
screen (i.e. "Registered to: Creative Connection Bob
Ransom"). These are the only differences between
registered and unregistered copies. 1-EDIT-RA has no
built in self-destruct mechanisms or other disgusting

When you register 1-EDIT-RA, you'll receive a small key
file that will disable the bell ringing and pause, and
enable the status line. If you hold a valid Fidonet node
number, your key file will be sent to you through netmail
file attach. Sysops who aren't a part of Fidonet or who
are outside of the continental U.S. and Canada will
receive their key files on a disk through the mail.


When you receive your key file, it will be named something
like LASTNAME.KEY (where LASTNAME is your last name).
Place this key file into the directory where 1-EDIT-RA
will be running from and rename it 1EDIT-RA.KEY. Repeat:
It must be in the same directory as 1-Edit-RA! Be sure to
check your spelling here: "1-EDIT-RA.KEY" won't work; only
"1EDIT-RA.KEY" will.

Leave this key in place for as long as you use 1-EDIT-RA.
It will be good for all future releases of the program.
If for some reason I should need to make a change in the
key encryption routines (which would invalidate your key),
a new key will be sent to you immediately. Also, there is
no difference between a key for the QuickBBS version of
1-Edit and the RA version, 1-Edit-RA, except for the
filename. The RA version looks for 1EDIT-RA.KEY while the

1-EDIT v2.01 Page 19

QuickBBS version looks for 1-EDIT.KEY. Just rename the


A registration form called REGISTER.DOC is included in the
1-EDIT-RA archive. Please complete this form and mail it
with your check or money order for $10 (U.S. funds) to the
address on that form. You key will be sent to you within
a few days of receipt of your check.


These pop up every once in a while and they usually stem
from the information in the key file not matching that in
your CONFIG file. Most often the mismatch is in the BBS
name. The key routines don't care about case but they do
care about wording and spacing. Be sure that the
information you provide on the registration form exactly
matches that in your CONFIG file.

1-EDIT v2.01 Page 20


Okay, I guess that wraps it up. Hopefully this document
is complete enough that you can set up and run 1-EDIT-RA
without problems. Should you encounter a problem of some
kind or an unfound bug, please be sure to let me know.
Suggestions for enhancements are always welcomed, too.
You can contact me through the RemoteAccess Utility
Support echo (RA_UTIL), the QuickBBS Support echo, the
QuickPro echo, or by netmail.

The current version of this program is available for file
request from my system under the magic name of 1EDIT-RA.
First time callers can also download the program from the
RA/QuickBBS Files section.

-Bob Ransom
27840 Lathrup Blvd.
Lathrup Village, MI 48076

The Creative Connection BBS
24 hours / 7 days
300-1200-2400 Baud / 8-N-1

1-EDIT v2.01 Page 21

  3 Responses to “Category : BBS Programs+Doors
Archive   : 1EDRA201.ZIP
Filename : 1EDIT-RA.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: