home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
ra
/
ma10.zip
/
MOVEAREA.DOC
< prev
next >
Wrap
Text File
|
1993-07-08
|
6KB
|
151 lines
────────────────────────────────────────
MoveArea v1.0
(C)opyright 1993, Bill Dykstra
A RemoteAccess 2.00 Message Area Utility
────────────────────────────────────────
What is it?
MoveArea is a utility that will move a message area from one area number
to another. MoveArea will ONLY work with RemoteAccess 2.00, on HUDSON
message bases. JAM bases are not supported by this program. Once the JAM
format is implemented there may be a version available for moving JAM areas.
Usage: MOVEAREA [source] [target]
[source] = Area number of the message area to move
[target] = New number of the message area being moved
Use MOVEAREA /C to configure the paths.
Three paths are stored:
(1) The path to MESSAGES.RA. This is usually your RemoteAccess
main program directory.
(2) The path to the message base files. (Usually \RA\MSG or
similar). The MSG*.BBS files and LASTREAD.BBS are stored
in this directory.
(3) The path to the RA text files. This is where your *.ASC/.ANS
files area stored, such as NEWS.A?? and NEWUSER.A??.
Examples:
MOVEAREA 1 22 will move message area #1 to 22.
All messages in area #1 will be changed to area #22.
MOVEAREA /C will run the configuration section of this program.
MOVEAREA 25 323 will do NOTHING, because area #323 is out of the range
of 1-200.
MoveArea will NOT let you overwrite an already existent message area.
For example, if you have messages areas #1 through 10, and you try to
move Area #2 to area #8, the program will not allow this, because
message area #8 is already being used.
MoveArea will not allow you to move a message area that does not exist.
You can't move it if it isn't there.
MoveArea will only move message areas in the range of #1 - #200.
When a message area is moved, the following things are done to your
files:
■ MESSAGES.RA is updated. This changes the message area information
as defined in RACONFIG (the source area becomes [unused] and the
source area data is written to the target area record).
■ MSGHDR.BBS is updated. All message headers are scanned, and all messages
found to be in the original (source) area are updated to the new (target)
area number.
■ MSGINFO.BBS is updated. This updates some data about the number of
messages in each message area.
■ MSGIDX.BBS is updated. This updates the index file, which simply contains
the message area number of each message.
■ LASTREAD.BBS is updated. This moves the lastread pointers from the
original message area to the new message area.
■ Any MGAxxx.A?? files will be renamed. For example, if you have:
MGA1.ANS, MGA1.ASC, and MGA1.AVT files for message area #1, and
you are moving area 1 to area 110, the files will be renamed to
MGA110.ANS, MGA110.ASC, and MGA110.AVT. NOTE: Any old MGAxxx files
will be deleted! If you had an old MGA110.ASC file in the text
files directory, it would be erased before the files are renamed.
This should not be a problem, since this will only happen if the
message area in question is no longer in use. (There just might
be old ASC/ANS/AVT files sitting around.)
That's it!
I have tested this program on my system quite a bit, but I cannot guarantee
ANYTHING! USE THIS PROGRAM AT YOUR OWN RISK. I do my best to be sure the
programs that I write will do exactly what they claim to do, and nothing
more. Sometimes, however, things get overlooked. I assume NO responsibility
for any damages that may occur because of your use of this program. If you
do have any problems PLEASE let me know, and I'll do my very best to fix
things for you.
Do NOT use this program while a user is online! All nodes should be shut
down, to be sure that no share violations occur. This program does not
check for shared files, so you could (and probably will) trash your message
base if you use it while a user is online.
This program is freeware. I hope you like it!
Bill Dykstra
The BillBoard BBS
Newmarket, Ontario Canada
(416) 898-2443
14.4k v.32b
Fidonet 1:250/932
FileRequest MOVEAREA for the latest version.
MoveArea is written using standard Borland Pascal 7.0. No extra units or
libraries were used.
DO NOT COMPRESS MOVEAREA.EXE with PKlite or any other such program! MoveArea
will update the actual .EXE file when you configure it! It can NOT do this
properly if the file is compressed.
R E M I N D E R:
───────────────
If you move an Echomail area or Netmail area, be SURE to update you mail
packer (Gecho, FastEcho, Imail, or whatever you use) to reflect this change!
You want to make sure new incoming messages get dumped into the new area
number! If you have a QWK door that does not automatically update the message
areas from MESSAGES.RA, you'll have to update the area numbers in the doors
as well.
Doors like Bluewave will automatically read the new areas from MESSAGES.RA,
BUT please note that the users will have to reconfigure their message area
selections. All the area NUMBERS that they have tagged for downloading will
still be tagged, BUT, these area numbers may no longer be the areas that they
wanted to download! The areas change, the numbers don't! Post an
announcement to your users reminding them to setup the message areas that
they want to download.
PS: You just might want to backup your message files and MESSAGES.RA before
using this program. I have not had any problems, but I would hate to be
resposible for the loss of your message base. Until you're satisfied that
the program does what it should, MAKE A BACKUP!
I admit, I did NOT make a backup of my message base files... I had a tiny
test base I used for the original testing, but most of my testing was done
with my regular message base. I didn't have enough HD space to make a copy
of it to work with... What's my point? Well, first, don't do what I did.
Second, my message base is still there!!! (Whew..)