• Mass upload question(s)

    From Olrik@21:2/144 to All on Sun Nov 17 09:06:40 2019
    Hi everybody,

    I'm new to the Mystic BBS system and have some questions about Mystic's 'mutil mass upload.ini'.

    Creating a massupload.ini is easy enough. I understand that it searches for
    new files (and ignores any files I define) and uploads them to the BBS. What I don't understand is that when I then go into the BBS I see the new files
    listed in my Local file areas (say 'demos', or 'utilities'), but that they
    also appear in the fsxnet group file areas with a tag NEW. It's as if they're being duplicated.

    Are they being duplicated into fsxnet or is this simply the
    way Mystic displays new files alert to fsxnet? Obviously I don't want to
    upload any files but keep them Local only.

    Any help would be appreciated!

    Cheers,



    Olrik

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
    * Origin: Outremer BBS (21:2/144)
  • From Ogg@21:4/103 to Olrik on Sun Nov 17 13:15:28 2019
    On 17 Nov 2019, Olrik said the following...

    Hi everybody,

    I'm new to the Mystic BBS system and have some questions about Mystic's 'mutil mass upload.ini'.

    Creating a massupload.ini is easy enough. I understand that it searches for new files (and ignores any files I define) and uploads them to the BBS. What I don't understand is that when I then go into the BBS I see
    the new files listed in my Local file areas (say 'demos', or
    'utilities'), but that they also appear in the fsxnet group file areas with a tag NEW. It's as if they're being duplicated.

    Are they being duplicated into fsxnet or is this simply the
    way Mystic displays new files alert to fsxnet? Obviously I don't want to upload any files but keep them Local only.

    Any help would be appreciated!

    Cheers,



    Olrik

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
    * Origin: Outremer BBS (21:2/144)

    Welcome Olrik!

    As a relative newcomer myself, let me say welcome! I find that these people are extremely helpful and welcoming.

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: Ready Player Two BBS (21:4/103)
  • From Nodoka Hanamura@21:2/106 to Olrik on Sun Nov 17 13:27:12 2019
    On 17 Nov 2019, Olrik said the following...

    Hi everybody,

    Hey there!

    I'm new to the Mystic BBS system and have some questions about Mystic's 'mutil mass upload.ini'.

    I'm still a little fresh but I think I can help you with this.


    Creating a massupload.ini is easy enough. I understand that it searches for new files (and ignores any files I define) and uploads them to the BBS. What I don't understand is that when I then go into the BBS I see
    the new files listed in my Local file areas (say 'demos', or
    'utilities'), but that they also appear in the fsxnet group file areas with a tag NEW. It's as if they're being duplicated.

    Okay - This is simple and one mistake I made a lot when I first started out.

    Do me a favor, go to your System Configuration panel (Under SYSOP Menu) and select the File Bases editor. Check each one and make sure that the FSXNET
    and local filebases are both put into seperate directories for each filebase. If not, then you'll have to manually remove the files from those folders and create new ones unique to the FSXNET Filebases. Each filebase uses a
    dedicated folder for each base, and if two filebases or more share the same folder, then they'll end up being merged together. Once you have them in dedicated folders, mark down the folder names and assign the filebases to
    those folders accordingly. I usually set the names of the folders to their echonames (FSX_MYS, FSX_TXT, etc.) for convenience.

    Hopefully this helps.

    Born too late to experience the scene.
    Born just in time to see it come back.
    Nodoka Hanamura - NeoCincinnati BBS SYSOP - neocinci.bbs.io

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/32)
    * Origin: NeoCincinnati BBS - neocinci.bbs.io:23 (21:2/106)
  • From Nodoka Hanamura@21:2/106 to Olrik on Sun Nov 17 13:32:23 2019
    On 17 Nov 2019, Olrik said the following...

    Are they being duplicated into fsxnet or is this simply the
    way Mystic displays new files alert to fsxnet? Obviously I don't want to upload any files but keep them Local only.

    Sorry, forgot to mention this part!

    As I said in my last message, the files should go into dedicated folders for each filebase. The only reason why I'd see local files appearing in FSXNET filebases is that.

    AFAIK, you should be fine regarding uploading files, as the hub usually
    doesn't permit upstream file transmission and usually 'hatches' files from
    RISA (FSXNET's Hub 1) to the other hubs, like THOLIAN (Hub 2) and the sort,
    and on down to each Hub's respective nodes, and from there, to any points
    under any nodes.

    Born too late to experience the scene.
    Born just in time to see it come back.
    Nodoka Hanamura - NeoCincinnati BBS SYSOP - neocinci.bbs.io

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/32)
    * Origin: NeoCincinnati BBS - neocinci.bbs.io:23 (21:2/106)
  • From tallship@21:2/104 to Nodoka Hanamura on Sun Nov 17 12:50:40 2019
    On 17 Nov 2019, Nodoka Hanamura said the following...

    Okay - This is simple and one mistake I made a lot when I first started out.

    Do me a favor, go to your System Configuration panel (Under SYSOP Menu) and select the File Bases editor. Check each one and make sure that the FSXNET and local filebases are both put into seperate directories for
    each filebase. If not, then you'll have to manually remove the files
    from those folders and create new ones unique to the FSXNET Filebases. Each filebase uses a dedicated folder for each base, and if two


    I believe that once you create those dirs (and they shold be autocreated if
    you specify them in your Message Base Editor - it should ask if you want it to), you can just copy over those echos into those dirs.

    Also, make sure you reflect the correct location in your mailin.ini if you specify already (for future AreaFix subscribes). I think I'm dispensing with good advice here, but I may be totally wrong, and have been before :)

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)
  • From Olrik@21:2/144 to Nodoka Hanamura on Sun Nov 17 14:40:52 2019
    Hi Nodoka,

    Thanks for your mails.. :)

    As I said in my last message, the files should go into dedicated folders for each filebase. The only reason why I'd see local files appearing in FSXNET filebases is that.

    AFAIK, you should be fine regarding uploading files, as the hub usually doesn't permit upstream file transmission and usually 'hatches' files
    from RISA (FSXNET's Hub 1) to the other hubs, like THOLIAN (Hub 2) and
    the sort, and on down to each Hub's respective nodes, and from there, to any points under any nodes.

    So I followed your steps in your first message, and then this second one. I think I understand what I was doing wrong. I went back and created separate everythings for each file base (names, dirs), and then ran mutil massupload.ini. It populated my file areas correctly, which is great (yay).

    When I went into File menu, and File Indexer (I), I saw my Local file bases populated correctly. For some reason however Indexer shows them also on
    fsxnet, but that can't be correct. Because when I actually swtich group to fsxnet then I don't see my local file areas. Maybe it's just the way Indexer
    is displaying it.. I guess.. ~!-

    Any chance I can ask you to login and have a look at my file area to see if
    it looks correct to you? :)

    Thanks for your help in any case!

    Cheers,



    Olrik

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
    * Origin: Outremer BBS (21:2/144)
  • From Al@21:4/106 to Olrik on Sun Nov 17 16:19:00 2019
    When I went into File menu, and File Indexer (I), I saw my Local file bases populated correctly. For some reason however Indexer shows them
    also on fsxnet, but that can't be correct. Because when I actually
    swtich group to fsxnet then I don't see my local file areas. Maybe it's just the way Indexer is displaying it.. I guess.. ~!-

    What do your List ACS lines say?

    In mystic messages groups are defined with g and file areas with z

    In my uploads directory the List acs is s10z1 and those only show up for
    group 1.

    Similar to the way message areas work but with z1 rather than g1.

    I hope that make sense.. :)

    Ttyl :-),
    Al

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Olrik@21:2/144 to Al on Sun Nov 17 17:29:40 2019
    Hey dude..

    What do your List ACS lines say?

    In mystic messages groups are defined with g and file areas with z

    In my uploads directory the List acs is s10z1 and those only show up for group 1.

    Similar to the way message areas work but with z1 rather than g1.

    I hope that make sense.. :)


    Winner! Thank you man, that solved it!

    Cheers,



    Olrik

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
    * Origin: Outremer BBS (21:2/144)
  • From Olrik@21:2/144 to Nodoka Hanamura on Sun Nov 17 17:32:28 2019
    Hey Nodoka,

    Thanks for your help in setting it up..
    And Al has figured out what was wrong with the uploaded files appearing in
    all areas..turns out I wasn't defining the file areas.. 'z3' etc. I fixed it and now it's all cream cheese!

    Cheers,



    Olrik

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
    * Origin: Outremer BBS (21:2/144)
  • From Bucko@21:4/131 to tallship on Sun Nov 17 21:16:07 2019
    Actually, you need to have different data files for each Library. If you have the same data file setup you will have all the files go into every library listing, not necessarily into the folders. I keep my libraries on a server shared folder, I have them broken down like everyone else. Each one has a different data file name, the default is new make sure you change that. I use the title if it is a local lib locutilities if networked xxx (net identifier) name of library (ex. fsxnodelist).. Check that...

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)
  • From Nodoka Hanamura@21:2/106 to Olrik on Sun Nov 17 23:44:36 2019
    On 17 Nov 2019, Olrik said the following...

    Hey Nodoka,

    Thanks for your help in setting it up..
    And Al has figured out what was wrong with the uploaded files appearing
    in all areas..turns out I wasn't defining the file areas.. 'z3' etc. I fixed it and now it's all cream cheese!

    Great! I actually made the same mistake with not understanding zone suffixes for file areas and message bases (z/g) at first myself. Good to see you got
    it fixed. :)

    Born too late to experience the scene.
    Born just in time to see it come back.
    Nodoka Hanamura - NeoCincinnati BBS SYSOP - neocinci.bbs.io

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/32)
    * Origin: NeoCincinnati BBS - neocinci.bbs.io:23 (21:2/106)
  • From Olrik@21:2/144 to Bucko on Mon Nov 18 14:29:40 2019
    On 17 Nov 2019, Bucko said the following...

    Actually, you need to have different data files for each Library. If you have the same data file setup you will have all the files go into every library listing, not necessarily into the folders. I keep my libraries
    on a server shared folder, I have them broken down like everyone else. Each one has a different data file name, the default is new make sure
    you change that. I use the title if it is a local lib locutilities if networked xxx (net identifier) name of library (ex. fsxnodelist).. Check that...


    Got it! :)



    Olrik

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
    * Origin: Outremer BBS (21:2/144)
  • From Olrik@21:2/144 to tallship on Mon Nov 18 14:31:16 2019
    Also, make sure you reflect the correct location in your mailin.ini if
    you specify already (for future AreaFix subscribes). I think I'm dispensing with good advice here, but I may be totally wrong, and have been before :)

    Hey Tallsip,
    Not sure I understand this. Am I editing mailin.ini to reflect my local
    defined filebases and zones, or..?

    Thanks,



    Olrik

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
    * Origin: Outremer BBS (21:2/144)
  • From tallship@21:2/104 to Olrik on Wed Nov 20 01:13:00 2019
    On 18 Nov 2019, Olrik said the following...

    Also, make sure you reflect the correct location in your mailin.ini i you specify already (for future AreaFix subscribes). I think I'm dispensing with good advice here, but I may be totally wrong, and hav been before :)

    Hey Tallsip,
    Not sure I understand this. Am I editing mailin.ini to reflect my local defined filebases and zones, or..?


    Like so:

    ; If you want to create settings specific to certain node addresses you can!
    ;
    ; For example, if you want auto create bases that are linked to your
    fsxNet
    ; test address of 21:1/999 then you can by prefixing with the address below.
    ;
    ; Remember if you are allocated your own node number for your BBS you will
    ; then want to update the settings below.

    21:2/104_acs_list = s10g1
    21:2/104_acs_read = s10g1
    21:2/104_acs_post = s20g1
    21:2/104_acs_news = s255g1
    21:2/104_acs_sysop = s255g1
    21:2/104_use_realname = 0

    And...

    ; Node-specific options allow some options to be overridden when a file is
    ; coming from a specific node. These options should be prefixed with the
    ; address, examples for each supported option are listed below in comments

    ; Create fsxNet file areas when sent from fsxNet HUB 21:2/100
    ;
    ; You may want to change this if you are being fed from another HUB
    ; with a different address e.g. 21:1/100 etc.

    21:2/100_bad_dir = /home/mystic/files/badfile/fsx/
    21:2/100_dir_prefix = /home/mystic/files/fsx/
    21:2/100_allow_replace = true
    21:2/100_acs_list = s10z1
    21:2/100_acs_ftp = s255z1
    21:2/100_acs_download = s20z1
    21:2/100_acs_upload = s30z1
    21:2/100_acs_hatch = s255z1
    21:2/100_acs_sysop = s255z1


    I hope that helps :)

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)