home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
bbsdoor
/
library.zip
/
EXITINFO.ARJ
/
EXITINFO.DOC
next >
Wrap
Text File
|
1993-03-05
|
10KB
|
216 lines
****************************
Lee Lefler
Infinity Software
7211 E 108th Street
Kansas City, Mo 64134
or
Lee Lefler
Infinity BBS
(816) 761-0860
FidoNet (1:280/5)
****************************
Standard Disclaimer:
This program is provided AS IS and as such the only
guarantee I will make is that it will take up space. I fully
intend to support this product and make updates when I feel
they are necessary but I will make no commitments to do so.
Please take any precautions that you feel are necessary to
protect your files.
Purpose of this program:
With the release of Remote Access 2.0/gamma came
many changes. The addition of quite a few new features
made it necessary to modify many of the support file
structures. While I'm sure many utility writers are cussing
RA's author about now, I personally see the long overdue new
structures as a fresh start and a step forward by doing away
with all the update kludges. But of course this means that
virtually all of the Remote Access specific utilities are
currently broken. Well that's what this program is here for.
MKQwk (by Mark May) is one of my main utilities and my system
just felt crippled without it's QWK mail door. With a little
help from Mark I was able to work around almost all the
incompatabilities with a couple minor DOS fixes. The main
problem was that ExitInfo.BBS was one of the files that had
changed. So this program was born. This program will create
a RA 1.11 ExitInfo.BBS file so that many of the older
utilities will run again. Then, since RA re-reads this file
when it reloads, you can use this program again to recreate
the original 2.0/g version of ExitInfo.BBS. One problem that
I ran into is that there is information in the new ExitInfo
that didn't exist in the old one. So before I create the old
format I copy the new one to Exit.BBS. This file will be
deleted as soon as I'm through with it and it allows me to
re-read the original information and put things back to
normal for RA. Well, now that my speech is out of the way,
on to how you can use it.
Warning ***** Well, just one more thing before we go on. The
purpose of this program is to give utility programmers
a little breathing room to get their programs updated.
Most are programming for us for free, or close to it,
and have a real life besides. But kludging the system
this way opens things up to some real hazards. RA
expects all the data in ExitInfo.BBS to be correct and
uses it accordingly. If you trash your exitinfo I can
almost guarantee you will trash your Users.BBS. So at
least keep current backups until you get the hang of
this program. Better yet, keep current backups all
the time. You are strongly encouraged again to take
any and all precautions you feel are necessary to
protect your data.
Operation:
Basically this program will run 3 ways and all three
start with different command line parameters. The first is
'Help' (or '/?'). This is just a simple help screen. The
second is with no command line parameters at all. This will
create the 1.11 format ExitInfo.BBS. And finally, '/NEW'
will convert the 1.11 format back to the 2.0/g format. To
create a 2.0/g file you must have previously run ExitInfo in
the 'old' mode so that there is a 1.11 format ExitInfo.BBS
and a Exit.BBS available for processing.
ExitInfo /? { Help Screen }
ExitInfo Help { Help Screen }
ExitInfo { Create 1.11 format }
ExitInfo /NEW { Create 2.0/g format }
And here's the batch file that I use here to call MKQwk:
Qwk.Bat @Echo Off
Set Hold=
Set Ra=C:\Ra\Node1\OldCfg
ExitInfo /Old
MkQwk
ExitInfo /New
OK, some explanations are probably in order... MkQwk
also reads Messages.Ra and Config.Ra in addition to ExitInfo.
Since both of these files have changed I needed to work out a
way to have multiple copies (new and old) of these two files
without killing my system. Well, being a programmer I have a
tendancy to use a sledgehammer to drive a thumb tack and went
to great means to work around this problem. I fired off some
netmail to Mark and he offered me the above, simple solution.
Just change RA's environment variable in a batch file in a
shell. Exit the shell and it's all back to normal. So that's
the reason for Set RA=... I put my old .RA files in the
OldCfg directory and I'm a step closer. But when I shell I
get an 'out of environment space' error. So I went in with
my BBS batch file and defined a new variable, Hold, and set
it to Hold=12345678901234567890. Just saving space that I
can make available with a Set Hold=. The rest is pretty much
self explanitary, I convert ExitInfo to 1.11 format, load
MKQwk, and then convert back to 2.0/g format.
Well, that's it. You can see how I use it. I use
this method daily on my BBS so that my users can still read
their mail. I'm sure there are many other uses, but it's up
to you to find them.
The rest is just some more of my ramblings. If
you're not interested in the technical issues, then you're
probably not going to be interested in my following
observations. It isn't necessary for you to read them to use
this program, but they might give you a little insight on how
it works.
{ Information that is not passed from new style ExitInfo }
{ to old style ExitInfo. }
{ }
{ ExitInfoRec.LogonPassword }
{ ExitInfoRec.UserInfo.Password }
{ ExitInfoRec.UserXIInfo.CombinedInfo }
{ }
{ ExitInfoRec.UserInfo.DataPhone }
{ and }
{ ExitInfoRec.UserInfo.HomePhone }
{ are smaller by 3 bytes and could truncate numbers }
Password information is no longer available. RA
doesn't store passwords anywhere any more. Instead it stores
a 32-bit CRC of the password. It's easy to CRC input and
compare it to this stored number, but considerably harder to
generate the original password from only the CRC. It's a
security feature folks. Just try to figure out someone's
password by looking at your Users.BBS.
CombinedInfo has gone from an Array of 25 bytes to
an Array of 100 words. I suspect that Andrew is just
expanding it to handle up to 64k message areas, but I didn't
want to get into disecting it to find out. I doubt that
there are very many doors that use the information anyway.
Home Phone and Data Phone have both been extended to
15 characters each from 12. This could cause some trouble
with programs that use this information, like CBVs. I would
suggest using caution if you use these fields.
{ Information that is not passed from old style ExitInfo }
{ to new style ExitInfo and must be recovered from saved }
{ Exit.BBS. }
{ }
{ ExitInfo.LogonPasswordCRC }
{ ExitInfo.PageReason }
{ ExitInfo.StatusLine }
{ ExitInfo.UserXIInfo }
{ ExitInfo.UserInfo.DefaultProtocol }
{ ExitInfo.UserInfo.FileGroup }
{ ExitInfo.UserInfo.LastDOBCheck }
{ ExitInfo.UserInfo.Sex }
{ ExitInfo.UserInfo.MsgGroup }
{ ExitInfo.UserInfo.PasswordCRC }
{ ExitInfo.UserInfo.Organisation }
{ ExitInfo.UserInfo.Address1 }
{ ExitInfo.UserInfo.Address2 }
{ ExitInfo.UserInfo.Address3 }
{ ExitInfo.UserInfo.CombinedInfo }
And now back the other way. All of this information
is new in RA 2.0/gamma. This information, as well as the
phone numbers, is what I use the old copy of ExitInfo.BBS
(stored in Exit.BBS) for. This information has to be in the
file when RA reads it back in or it will definately blank the
fields in the user record. Saving the information in a
temporary file was the easiest way to do it.
Registration:
This part is really simple. I don't require any
registration. The only thing that I ask is that the program
is distributed in the original archive with all the files
intact. Changing the archive format, from ARJ to ZIP for
instance, is permissable. Editing or reverse engineering any
of the files contained in the original archive is strictly
prohibited. Other than that, you are free to use this
program in any environment necessary, whether commercial or
non-commercial. But if you get the chance, I'd appreciate
it if you could drop me a note, (either US Mail or at my Fido
address) and let me know how far this program has travelled
and what you think of it. Lee Lefler and Infinity Software
retain all rights. This program absolutely is NOT Public
Domain.
CopyRight 1993, Infinity Software, All Rights Reserved