I think there is a small issue you might want to review for the next release...

Message areas are auto created in the \mystic\msgs\ directory. If I want to
move the message files to a subdirectory like all the fido to
\mystic\msgs\fido\ or \mystic\msgs\usenet\ ... Here is goes... if I move /
target the message ares one at a time it'll move the files over ... If I try to
move several over at a time with the Global command menu.... It seems to leave
some files behind in the \mystic\msgs\ directory and they appear to be links to
the files that were moved.

It only does this when I try to bulk move the areas to a new subdirectory

:)

IB Joe
AKA Joe Schweier
SysOp of Joe's BBS
-=JoesBBS.com=-

.... Shortcut: longest distance between two points

IJ> I think there is a small issue you might want to review for the next
IJ> release...
IJ>
IJ> Message areas are auto created in the \mystic\msgs\ directory. If I
IJ> want to move the message files to a subdirectory like all the fido to
IJ> \mystic\msgs\fido\ or \mystic\msgs\usenet\ ... Here is goes... if I move
IJ> / target the message ares one at a time it'll move the files over ... If
IJ> I try to move several over at a time with the Global command menu.... It
IJ> seems to leave some files behind in the \mystic\msgs\ directory and they
IJ> appear to be links to the files that were moved.

A couple of notes here because I think a lot of this might just be confusion on
how things work:

If you are seeing .lnk files those are not any type of links to files, those
are part of the message base itself. Mystic message bases each have 7 data
files with the following extensions: lnk, scn, xlr, jhr, jlr, jdt, and jdx. If
you remove any of those you could cause some problems down the line.

When using the global editor it does not rename or move files for you, you are
only updating the path. If you want to try to relocate your files into those
directories you have to manually copy them and then use the global editor to
update the path. It will only update that value not move files.

The reason the auto create in the import doesn't allow you to set the path for
each network is because I have been over the years trying to get people to stop
moving the message base data files all over the place because it makes it
harder to do upgrades or to change the root Mystic install directory, or move
between Windows and Linux (for examples). This is something I could add though
but I haven't because my goal was to remove the configurable message path per
message base.

.... I'm not a complete idiot... Several parts are missing!