How to do a MASS File Area insertion into Mystic BBS. Then import all of the FI
LES.BBS or 00INDEX.txt files into those areas.

Here is a tutorial on how to create File Groups, then all of the File Areas unde
r those groups in Mystic BBS Software. I will note
that I am running Mystic 1.11 on a Raspberry PI 3 under Ubuntu MATE. This MAY o
r MAY NOT work with your setup. Use this
tutorial at your own risk. I would study your own MUTIL.INI file to see how thi
ngs are done.

This came about because I wanted to add several CD's contents to my BBS.
I did not feel like sitting there for Days creating Each Directory into the File
Area.
I knew there was a way to do this in EchoMail/Netmail... So I copied how they do
that in a way...
I sort of cheated by using a .NA file with the directories (Areas) to Add into t
he BBS...

Note: When I say CD, I mean a folder that has numerous Directories under it...

For Example:
SVACDROM
\
ARCHIVE
BBS
PROGRAMS
...
Under for example ARCHIVE you may have 100 files.. SCACDROM\ARCHIVE\zipmaker.zip
SCACDROM\ARCHIVE\arc.zip
SCACDROM\ARCHIVE\lzh.zip
SCACDROM\ARCHIVE\zoo.zip
SCACDROM\ARCHIVE\FILES.BBS
...

I will from now on call these CD's, but they are folder on your BBS Hard Drive u
nder for example /Mystic/Files/CDROM/SCACDROM/ etc...
I do not think you would be able to do this with Actual CD's.

So Here is what I did.

1) Copy the contents of your CD's to a Subdirectory in /mystic/files/cdrom

2) Go to the Main directory of each CD...
Lets say as an example you have placed 5 CD's under /mystic/files/CDROM like bel
ow:
c:\mystic\files\CDROM\SCACDROM\
c:\mystic\files\CDROM\WALNUT\
c:\mystic\files\CDROM\SIGMA1\
c:\mystic\files\CDROM\SIMTEL1\
c:\mystic\files\CDROM\SLACKWARE\
(For linux it may look like as an example: /home/user/mystic/files/CDROM/WALNUT
/)

I used DOSBOX (Both on Linux/Raspberry Pi or even Windows).
For Each CDROM Directory above, do this: DIR > scacdrom.txt
or DIR > walnut.txt
etc...

You can copy all of those directory list files to one location... I put them in


the /mysic directory.

Now edit each of those files. Remove all other information except the DIRECTORY
NAME.
I know it's tedious work. Some people use Excel to Import Data, then simply Cop
y and Paste
back into the TXT document the Folder Names...

Now make that file look similar to this one: ====================================================
% File Echo Description
%
Area DIRECTORY1 0 ! Directory 1 Description
Area DIRECTORY2 0 ! Directory 2 Description
....
Area DIRECTORY99 0 ! Directory 99 Description
%
% End of FSXNet Fileecho List ====================================================


Add the Header:
% File Echo Description
%

Place "Area" BEFORE the Directory Name

Then add the "0" and "!" after the Filename
I'm not sure this is needed, but I put it there because it was an example from t
he Mystic Wiki

Then Add a Desctiption for each Directory.

Then add the footer:
%
% End of FSXNet Fileecho List

Once this is all done, Save the file as CDROMNAME.NA

So for example, if this was WALNUT directory, it would be named walnut.na

Do that for ALL of the DIR.TXT files you've created.

--------------------------------

Now. Run Mystic -cfg
Create ALL FILE GROUPS for the CD's you want to add...

For this example, Create File Groups for:

1 SCACDROM
2 WALNUT
3 SIGMA1
4 SIMTEL1
5 SLACKWARE

(Whatever the Index # (Or Group #) is on the left... Note that #.. They will not
be like these #'s)
Keep track of the GROUP NUMBER.... It's important as you will use it in the nex
t section... Your Group Numbers will be different than this example.
You will need those Group #'s when creating each .INI file below:

--------------------------------

Ok. Once you have done that for ALL of those CD's... Now it's time to create a
n .INI file for ALL of those CD's (Separate .ini for each File Group)

You can pull an example of this from your MUTIL.INI File

For This Example, we will be working with the WALNUT .ini file

; ==============================================================================

; MUTIL configuration file walnut.ini
; -------------------------------------------------------------------------
; WALNUT walnut.na Processing Only
; ========================================================================== [General]
; list of functions to perform on startup
Import_FILEBONE.NA = true

logfile=WALNUT.log
loglevel=3
logtype = 0
maxlogfiles = 3
maxlogsize = 1500
; ========================================================================== [Import_FILEBONE.NA]

; filename of filebone.na
filename = walnut.na

; root_dir is where the Walnut CD ROM resides. Make SURE this is accurate!

root_dir = c:\mystic\files\CDROM\WALNUT\
; For Linux or Raspberry pi. It was root_dir=/home/pi/mystic/files/cdrom/walnu
t/ for mine...

; convert tags to lower case for filebase base filename/dir 1=yes
; I recommend no to keep accurate directory filenames. Linux is C
ase Sensitive and
; setting this to 1 added all new directories with lower case name
s... Leave this at 0!

lowercase_filename = 0

; Default values when creating a new file base
; This is Important. Keep note of the Z number. This is the FILE
GROUP NUMBER (See Above)
; The z2 is for Zone 2 (Walnut)... You can set the S??? to whatev
er you want. Make sure they
; are what you want... Changing them 100 times is no fun afterward
s...

;DANGER: If you do NOT set the Z# correctly, it may place these directories unde
r the wrong File Group!!!!
; Make Absolutely Sure the Z#'s reflect the File Group Index Numb
er you created in mystic -cfg!

dispfile =
template = ansiflst
acs_list = s10z2
acs_ftp = s10z2
acs_download = s10z2
acs_upload = s255z2
acs_hatch = s255z2
acs_sysop = s255z2

; true/false type values 0=false 1=true (newscan 2=forced) If you WANT


them to upload, set Upload to 1

free_files = 0
show_uploader = 0
new_scan = 1
; ==============================================================================



NOW that you have done this. Save this file as walnut.ini

Now make separate .INI filed for Each File Group you are wanting to populate

Ok... Now that you've created each FILE GROUP in Mystic...
And now you have created all of the .NA files for each directory...
And now you have created a .INI file for each directory (Make sure Z# is Accurat
e and different for each .INI file!!!!!

And you've determined that Each .INI file is pointing correctly to the right .NA
file AND the Z#'s are accurate...

Make sure all of your .NA files and your .INI files you created above are in you
r /Mystic directory!

Now go to DOS. (Or Terminal in Linux/Raspberry Pi).
Run Mutil on all of the .INI files you've created above.

Example (Linux). ./mutil walnut.ini
Example (Dos). Mutil walnut.ini

If successful, it will create ALL of the Directories under CDROM/WALNUT into you
r Mystic BBS.
Do the same for all other .INI files you created!

NOTE: To "Some" of you Linux people (Or Raspberry Pi, Ubuntu MATE) users. I've


noted that sometimes
this does not work. Before you run your ./mutil ***.ini files Tr
y this....
chmod 777 -R /home/pi/mystic/files
If I did not do this, it would not add anything... Not needed to run


filesbbs.ini however...

******************************************************************************* *

**************************************
But wait, now when you log on, you can Join Group... And Change Areas... but the
re are no files there!!!

NOW you have to use either Mass Upload or Import Files.bbs to get the files ther
e...
I won't be going into Mass_Upload because for me...
not all .ZIP's in these CD's will have FILE_ID.DIZ's in them. So I've decided t
o use Files.bbs. You may want more
descriptions in your listing, so I would look into MASS_UPLOAD in your Mutil.ini
file to see how that's done.

Most of my CD's that I've placed on my BBS, each directory had a file called FIL
ES.BBS
You can use MUTIL to import all of those into your BBS...

Create a file called filesbbs.ini in your mystic directory.
You only need ONE of these for ALL File Areas on your BBS!

; ==========================================================================
; MUTIL filesbbs.ini configuration file
; -------------------------------------------------------------------------
; Import FILES.BBS
; ========================================================================== [General]

; list of functions to perform on startup

Import_FILES.BBS = true

logfile=filesbbs.log
loglevel=3
logtype = 0
maxlogfiles = 3
maxlogsize = 1500
; ========================================================================== [Import_FILES.BBS]

; Note: Some CD-ROM's use a file called 00index.txt or 00_index.txt along with f
iles.bbs. You can use that
; here instead of files.bbs. Just open some to see where the Descripti
on begins.
; change files.bbs to 00index.txt or 00_index.txt if you want to use th
at instead:

filesbbs=files.bbs

; Upload name for files uploaded by this function
uploader_name = Sysop

; Delete the FILES.BBS file after processing (Your option... I keep mine
)...
delete_after = false

; Update existing files in the database, if their file sizes do not matc
h?
; Both size and description will be imported. I leave this at False...


Your call..
update_files = false

; The FILES.BBS format must be configured here using the following optio
ns
;
; DESC_FIRST: Defines how the first line of the file description is hand
led.
;
; If the value is 0, the importer will expect for the file description
to
; appear directly after the filename (ie, the second "word" on the lin
e).
;
; If the value is -1, then the importer will not look for a descriptio
n on
; the first line.
;
; If the first description line is always at a specific character posi
tion
; on the first line, then DESC_FIRST should contain the character posi
tion

; What I do is open a sample of each FILES.BBS and see what column the descripti
on is on...
; I use that number for all 3 #'s below:

desc_first = 15

; DESC_CHAR: Defines the character identifier for an extended descriptio
n line
; if this value is blank, it will mean a space.

desc_char =
desc_charpos =

; DESC_START: Defines the character position of the extended description
line.
; If a line contains the DESC_CHAR at the DESC_START positio
n,
; then the importer will copy everything after that as an ex
tended
; descripttion line.

desc_start = 15

; ==========================================================================

Thats It. Now save this as filesbbs.ini

Now at the prompt run mutil filesbbs.ini
(Linux: ./mutil filesbbs.ini)

This will go through ALL of your directories and add anything in the FILES.BBS t
o your BBS listing.
(If the File Name is already in Mystic, and the File Size is the same, it will n
ot add from files.bbs unless update_files=1)

Walah... Done!

I hope that this little tutorial will help someone in doing a Mass Import of CD'
s or a LOT of Directories...
It sure saved me Weeks of tedious inputting of Groups/Areas and all of that... Please note: This was done on a Raspberry Pi running Ubunto MATE, and with Mysti
c 1.11. I'm not sure it will work under newer versions or other O/S's. Use
at your own risk.

Gary Crunk
Another F-ing BBS
anotherbbs.bbsindex.com

--- Mystic BBS v1.11 (Raspberry Pi)
* Origin: Another F-ing BBS (21:2/105)

Nice write up.. Seems like still a good deal of work involved here.

I wonder, would this be the sort of thing people would appreciate having a dedicated utility for? I might be willing to build something like that.

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 01/20/17, oog said the following...

Nice write up.. Seems like still a good deal of work involved here.

I wonder, would this be the sort of thing people would appreciate having
a dedicated utility for? I might be willing to build something like
that.

A utility would be great. Seems like way to much work for my liking. I
don't see why a simple import function can't be built in, just enter a base starting directory and then it creates new file areas for each physical directory.

Immortal

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

Yes. I know it was a long tutorial. I just wanted to make sure I covered
all aspects of the process. I probably made it look harder than it really
is. It sure beats the alternative, and entering 10000 directories... Ugh.

Yes, a good program would work great here... Should be for Windows and Linux/Raspberry Pi also. Maybe something written into an MPL...

Gary Crunk
Another F-ing BBS
anotherbbs.bbsindex.com

--- Mystic BBS v1.11 (Raspberry Pi)
* Origin: Another F-ing BBS (21:2/105)

On 01/20/17, garycrunk pondered and said...

How to do a MASS File Area insertion into Mystic BBS. Then import all
of the FI
LES.BBS or 00INDEX.txt files into those areas.

Thanks for posting! When I am not so tired I'll have a read through and
digest this and post feedback / questions..

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

How to do a MASS File Area insertion into Mystic BBS. Then import all
of the FI
LES.BBS or 00INDEX.txt files into those areas.

Nice tutorial, but the text is messed and difficult to read. Make sure that your text has no more than 79 (80 at worst case) chars width and reupload it.

Nice work. :)

.----- --- -- -
| Another Droid BBS
: Telnet : andr01d.zapto.org:9999 [UTC 11:00 - 20:00]
. Contact : xqtr.xqtr@gmail.com

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Another Droid BBS (21:1/111)

FILES.BBS or 00INDEX.txt files into those areas.

Here is a tutorial on how to create File Groups, then all of the File Areas under those groups in Mystic BBS Software. I will note that I am running Mystic 1.11 on a Raspberry PI 3 under Ubuntu MATE. This MAY or MAY NOT work with your setup. Use this tutorial at your own risk. I would study your
own MUTIL.INI file to see how things are done.

This came about because I wanted to add several CD's contents to my BBS.
I did not feel like sitting there for Days creating Each Directory into the File Area.

I knew there was a way to do this in EchoMail/Netmail... So I copied how
they do that in a way... I sort of cheated by using a .NA file with the directories (Areas) to Add into the BBS...

Note: When I say CD, I mean a folder that has numerous Directories under it.

For Example:
SVACDROM
\
ARCHIVE
BBS
PROGRAMS
...
Under for example ARCHIVE you may have 100 files.. SCACDROM\ARCHIVE\zipmaker.zip
SCACDROM\ARCHIVE\arc.zip
SCACDROM\ARCHIVE\lzh.zip
SCACDROM\ARCHIVE\zoo.zip
SCACDROM\ARCHIVE\FILES.BBS
...

I will from now on call these CD's, but they are folder on your BBS Hard
Drive under for example /Mystic/Files/CDROM/SCACDROM/ etc...
I do not think you would be able to do this with Actual CD's.

So Here is what I did.

1) Copy the contents of your CD's to a Subdirectory in /mystic/files/cdrom

2) Go to the Main directory of each CD...
Lets say as an example you have placed 5 CD's under /mystic/files/CDROM like below:
c:\mystic\files\CDROM\SCACDROM\
c:\mystic\files\CDROM\WALNUT\
c:\mystic\files\CDROM\SIGMA1\
c:\mystic\files\CDROM\SIMTEL1\
c:\mystic\files\CDROM\SLACKWARE\
(For linux it may look like as an example: /home/user/mystic/files/CDROM/WALNUT/)

I used DOSBOX (Both on Linux/Raspberry Pi or even Windows).
For Each CDROM Directory above, do this: DIR > scacdrom.txt
or DIR > walnut.txt
etc...

You can copy all of those directory list files to one location... I put them
in the /mysic directory.

Now edit each of those files. Remove all other information except the DIRECTORY NAME.
I know it's tedious work. Some people use Excel to Import Data, then simply Copy and Paste back into the TXT document the Folder Names...

Now make that file look similar to this one: ====================================================
% File Echo Description
%
Area DIRECTORY1 0 ! Directory 1 Description
Area DIRECTORY2 0 ! Directory 2 Description
....
Area DIRECTORY99 0 ! Directory 99 Description
%
% End of FSXNet Fileecho List ====================================================


Add the Header:
% File Echo Description
%

Place "Area" BEFORE the Directory Name

Then add the "0" and "!" after the Filename
I'm not sure this is needed, but I put it there because it was an example
from the Mystic Wiki

Then Add a Desctiption for each Directory.

Then add the footer:
%
% End of FSXNet Fileecho List

Once this is all done, Save the file as CDROMNAME.NA

So for example, if this was WALNUT directory, it would be named walnut.na

Do that for ALL of the DIR.TXT files you've created.

--------------------------------

Now. Run Mystic -cfg
Create ALL FILE GROUPS for the CD's you want to add...

For this example, Create File Groups for:

1 SCACDROM
2 WALNUT
3 SIGMA1
4 SIMTEL1
5 SLACKWARE

(Whatever the Index # (Or Group #) is on the left... Note that #.. They will not be like these #'s)
Keep track of the GROUP NUMBER.... It's important as you will use it in the next section... Your Group Numbers will be different than this example.
You will need those Group #'s when creating each .INI file below:

--------------------------------

Ok. Once you have done that for ALL of those CD's... Now it's time to
create an .INI file for ALL of those CD's (Separate .ini for each File Group)

You can pull an example of this from your MUTIL.INI File

For This Example, we will be working with the WALNUT .ini file

; ==========================================================================
; MUTIL configuration file walnut.ini
; -------------------------------------------------------------------------
; WALNUT walnut.na Processing Only
; ========================================================================== [General]
; list of functions to perform on startup
Import_FILEBONE.NA = true

logfile=WALNUT.log
loglevel=3
logtype = 0
maxlogfiles = 3
maxlogsize = 1500
; ========================================================================== [Import_FILEBONE.NA]

; filename of filebone.na
filename = walnut.na

; root_dir is where the Walnut CD ROM resides. Make SURE this is accurate!

root_dir = c:\mystic\files\CDROM\WALNUT\

; For Linux or Raspberry pi. It was
; root_dir=/home/pi/mystic/files/cdrom/walnut/ for mine...

; convert tags to lower case for filebase base filename/dir 1=yes
; I recommend no to keep accurate directory filenames. Linux
; is Case Sensitive and
; setting this to 1 added all new directories with lower case
; names... Leave this at 0!

lowercase_filename = 0

; Default values when creating a new file base
; This is Important. Keep note of the Z number. This is the
; FILE GROUP NUMBER (See Above)
; The z2 is for Zone 2 (Walnut)... You can set the S??? to
; whatever you want. Make sure they
; are what you want... Changing them 100 times is no fun
; afterwards...

;DANGER: If you do NOT set the Z# correctly, it may place these directories
; under the wrong File Group!!!!
; Make Absolutely Sure the Z#'s reflect the File Group Index Number you
; created in mystic -cfg!

dispfile =
template = ansiflst
acs_list = s10z2
acs_ftp = s10z2
acs_download = s10z2
acs_upload = s255z2
acs_hatch = s255z2
acs_sysop = s255z2

; true/false type values 0=false 1=true (newscan 2=forced) If you WANT
; them to upload, set Upload to 1

free_files = 0
show_uploader = 0
new_scan = 1
; ===========================================================================


NOW that you have done this. Save this file as walnut.ini

Now make separate .INI filed for Each File Group you are wanting to populate

Ok... Now that you've created each FILE GROUP in Mystic...
And now you have created all of the .NA files for each directory...
And now you have created a .INI file for each directory (Make sure Z# is Accurate and different for each .INI file!!!!!

And you've determined that Each .INI file is pointing correctly to the right .NA file AND the Z#'s are accurate...

Make sure all of your .NA files and your .INI files you created above are in your /Mystic directory!

Now go to DOS. (Or Terminal in Linux/Raspberry Pi).
Run Mutil on all of the .INI files you've created above.

Example (Linux). ./mutil walnut.ini
Example (Dos). Mutil walnut.ini

If successful, it will create ALL of the Directories under CDROM/WALNUT into your Mystic BBS.

Do the same for all other .INI files you created!

NOTE: To "Some" of you Linux people (Or Raspberry Pi, Ubuntu MATE) users.
I've noted that sometimes this does not work. Before you run your
./mutil ***.ini files Try this....
chmod 777 -R /home/pi/mystic/files
If I did not do this, it would not add anything... Not needed to
run filesbbs.ini however...

**************************************************************************** But wait, now when you log on, you can Join Group... And Change Areas... but there are no files there!!!

NOW you have to use either Mass Upload or Import Files.bbs to get the files there...

I won't be going into Mass_Upload because for me...
not all .ZIP's in these CD's will have FILE_ID.DIZ's in them. So I've
decided to use Files.bbs. You may want more
descriptions in your listing, so I would look into MASS_UPLOAD in your Mutil.ini file to see how that's done.

Most of my CD's that I've placed on my BBS, each directory had a file called FILES.BBS. You can use MUTIL to import all of those into your BBS...

Create a file called filesbbs.ini in your mystic directory.
You only need ONE of these for ALL File Areas on your BBS!

; ==========================================================================
; MUTIL filesbbs.ini configuration file
; -------------------------------------------------------------------------
; Import FILES.BBS
; ========================================================================== [General]

; list of functions to perform on startup

Import_FILES.BBS = true

logfile=filesbbs.log
loglevel=3
logtype = 0
maxlogfiles = 3
maxlogsize = 1500
; ========================================================================== [Import_FILES.BBS]

; Note: Some CD-ROM's use a file called 00index.txt or 00_index.txt along
; with files.bbs. You can use that here instead of files.bbs. Just
; open some to see where the Description begins.
; change files.bbs to 00index.txt or 00_index.txt if you want to use
; that instead:

filesbbs=files.bbs

; Upload name for files uploaded by this function

uploader_name = Sysop

; Delete the FILES.BBS file after processing (Your option.. I keep mine

delete_after = false

; Update existing files in the database, if their file sizes do not
; match?
; Both size and description will be imported. I leave this at False...
; Your call..

update_files = false

; The FILES.BBS format must be configured here using the following
; options
; DESC_FIRST: Defines how the first line of the file description is
; handled.
;
; If the value is 0, the importer will expect for the file description
; to appear directly after the filename (ie, the second "word" on the
; line).
;
; If the value is -1, then the importer will not look for a
; description on the first line.
;
; If the first description line is always at a specific character
; position on the first line, then DESC_FIRST should contain the
; character position

; What I do is open a sample of each FILES.BBS and see what column the
; description is on...
; I use that number for all 3 #'s below:

desc_first = 15

; DESC_CHAR: Defines the character identifier for an extended description
; line
; if this value is blank, it will mean a space.

desc_char =
desc_charpos =

; DESC_START: Defines the character position of the extended description
; line.
; If a line contains the DESC_CHAR at the DESC_START position,
; then the importer will copy everything after that as an
; extended description line.

desc_start = 15

; ==========================================================================

Thats It. Now save this as filesbbs.ini

Now at the prompt run mutil filesbbs.ini
(Linux: ./mutil filesbbs.ini)

This will go through ALL of your directories and add anything in the
FILES.BBS to your BBS listing.
(If the File Name is already in Mystic, and the File Size is the same,
it will not add from files.bbs unless update_files=1)

Walah... Done!

I hope that this little tutorial will help someone in doing a Mass Import
of CD's or a LOT of Directories...

It sure saved me Weeks of tedious inputting of Groups/Areas and all of that.. Please note: This was done on a Raspberry Pi running Ubuntu MATE, and with Mystic 1.11. I'm not sure it will work under newer versions or other O/S's. Use at your own risk.

Gary Crunk
Another F-ing BBS
anotherbbs.bbsindex.com
garycrunk@amtimes.com

Gary Crunk
Another F-ing BBS
anotherbbs.bbsindex.com

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Another F-ing BBS (21:2/105)

Posted it...

Thanks

Gary Crunk
Another F-ing BBS
anotherbbs.bbsindex.com

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Another F-ing BBS (21:2/105)

On 05/17/17, garycrunk said the following...

How to do a MASS File Area insertion into Mystic BBS. Then import all
of the FILES.BBS or 00INDEX.txt files into those areas.

Saved for later... Thanks so much for taking the time to put that together. Very useful information! :)

.-=Avenger=-.
Avenger BBS
Santa Cruz USA

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Avenger BBS (21:2/122)

together. Very useful information! :)
.-=Avenger=-.

You are very welcome... I actually put that little doc together not for the initial purpose of sharing... but rather a set of instructions so I would remember how to do it each time... :) Truth be known...

Gary Crunk
Another F-ing BBS
anotherbbs.bbsindex.com

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Another F-ing BBS (21:2/105)

On 05/17/17, garycrunk said the following...

You are very welcome... I actually put that little doc together not for the initial purpose of sharing... but rather a set of instructions so I would remember how to do it each time... :) Truth be known...

I take it all back then. =oP

.-=Avenger=-.
Avenger BBS
Santa Cruz USA

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Avenger BBS (21:2/122)