1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • I hate doing this, but...

    From garycrunk@21:2/105 to g00r00 on Friday, September 15, 2017 07:19:01

    I've noticed something, it's not a major thing at all... Could be put at
    the very bottom of your to-do list...

    This is not on A35, but 1.12 A34 if that helps narrow it down.

    When Mystic drops to a Door, it creates several Drop-Files for use... One
    of them dorinfo1.def. (I love the fact it creates all of the others BTW)

    Here is the problem. If a user is on Node 2... The drop file is still
    called dorinfo1.def. It should be dorinfo2.def ... dorinfo3.def and so on... It only creates dorinfo1.def .

    I can get around that problem with a Batch file, so it's not a major
    thing... Just thought you may want to know about this...

    I just wanted to say MANY thanks for all of your hard and excellent work
    you are doing on Mystic... I think it is a Fantastic BBS package...

    Gary Crunk

    ----=[ Gary Crunk * Another F-ing BBS * anotherbbs.bbsindex.com ]=----

    --- Mystic BBS v1.12 A34 (Windows/32)
    * Origin: Another F-ing BBS (21:2/105)
  • From maskreet@21:1/114 to garycrunk on Friday, September 15, 2017 14:29:04
    On 09/15/17, garycrunk said the following...

    g00r00;

    I've noticed something, it's not a major thing at all... Could be put
    at the very bottom of your to-do list...

    This is not on A35, but 1.12 A34 if that helps narrow it down.

    When Mystic drops to a Door, it creates several Drop-Files for use... One of them dorinfo1.def. (I love the fact it creates all of the others BTW)

    Here is the problem. If a user is on Node 2... The drop file is still called dorinfo1.def. It should be dorinfo2.def ... dorinfo3.def and so on... It only creates dorinfo1.def .

    Actually, that's not much of an issue. Mystic has separate directories for
    the drop files, so they all get their own copy. Even if it didn't,
    overwriting a drop file with the same name for multiple nodes shouldn't be an issue. Only issue I could see if the BBS software locking the file, but I'm
    not sure if I've ever seen that.

    There's two setups for DORINFO. One is a single DORINFO1.DEF, and then the other is the one you're letting him know about. Both should work fine in a majority of cases.

    --- Mystic BBS v1.12 A35 (Windows/32)
    * Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)
  • From garycrunk@21:2/105 to maskreet on Friday, September 15, 2017 15:59:46
    the other is the one you're letting him know about. Both should work
    fine in a majority of cases.

    As an example of what I was talking about... One of my Doors looks for DorInfo?.def where ? is the Node the user is on... Mystic only creates a
    file (no matter what temp# folder) named Dorinfo1.def....

    Hence the small issue. I know about the issue so I make corrections for it i the Batch file...

    Yes, it's a small non-issue really... Just something I wanted to mention.

    Gary

    ----=[ Gary Crunk * Another F-ing BBS * anotherbbs.bbsindex.com ]=----

    --- Mystic BBS v1.12 A34 (Windows/32)
    * Origin: Another F-ing BBS (21:2/105)
  • From g00r00@21:1/108 to garycrunk on Sunday, October 22, 2017 15:35:07
    Here is the problem. If a user is on Node 2... The drop file is still called dorinfo1.def. It should be dorinfo2.def ... dorinfo3.def and so on... It only creates dorinfo1.def .

    This is not how it works. DORINFO1.DEF in the node's temp directory is correct. In DOS we are limited to 8 characters, so what would happen on Node 10? DORINFO10.DEF is not a valid DOS filename.

    DORINFO1.DEF is correct and Mystic is creating it correctly. :)

    --- Mystic BBS v1.12 A36 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)