• Mystic Error

    From garycrunk@21:1/100 to All on Friday, May 19, 2017 06:05:22
    Tried logging on to my BBS at 6am, I saw Error 216 reported by Mystic on the BBS machine (Windows XP), my Batch file did it's thing and restarted the
    system after the error... Logged on just fine the next time...

    I am running Mystic 1.12 A33 on a Windows XP SP/3 machine.

    Just reporting the error, no need to reply... With my Auto-Restart Batch file running, my BBS will always bounce-back after an error...

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

    --- Mystic BBS v1.12 A33 (Windows/32)
    * Origin: fsxNet HUB (21:1/100)
  • From Black Panther@21:1/186.2 to garycrunk on Saturday, May 20, 2017 16:36:00
    On 05/19/17, garycrunk said the following...

    Tried logging on to my BBS at 6am, I saw Error 216 reported by Mystic on the BBS machine (Windows XP), my Batch file did it's thing and restarted the system after the error... Logged on just fine the next time...

    I've had that happen a couple times, but it was with A31. The batch file
    worked exactly as it should.

    I am running Mystic 1.12 A33 on a Windows XP SP/3 machine.

    Since A33 was installed on the Windows10/64 bit system, I've only had one
    issue with Error 216. That was when the nightly maintenance was running, and MUTIL came up with that error. Windoze actually had the message window come
    up to either debug or close the program. Unfortunately, it was several hours later when I noticed it, so MUTIL didn't run during that time.


    Dan Richter
    aka Black Panther
    Sysop - Castle Rock BBS

    --- FMailX 1.60
    * Origin: Castle Rock BBS 2 - Castlenet HQ! (21:1/186.2)
  • From garycrunk@21:2/105 to Black Panther on Saturday, May 20, 2017 16:17:09
    issue with Error 216. That was when the nightly maintenance was running, and MUTIL came up with that error. Windoze actually had the message
    window come up to either debug or close the program. Unfortunately, it
    was several hours later when I noticed it, so MUTIL didn't run during
    that time.
    Dan Richter

    Dan;

    I only saw it happen once. I am sure it's happened before, but the Batch file I use just reported it.. Ignored and Looped back to restart the BBS...

    This is the first time I've seen that with 1.12 A33. I'm on a slower Windoze XP 32 Bit system... It's not a big issue because I do run Mystic
    under the looping Batch file....

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

    --- Mystic BBS v1.12 A33 (Windows/32)
    * Origin: Another F-ing BBS (21:2/105)
  • From Avon@21:1/101 to Black Panther on Sunday, May 21, 2017 14:02:25
    On 05/20/17, Black Panther pondered and said...

    Since A33 was installed on the Windows10/64 bit system, I've only had one issue with Error 216. That was when the nightly maintenance was running, and MUTIL came up with that error. Windoze actually had the message
    window come up to either debug or close the program. Unfortunately, it
    was several hours later when I noticed it, so MUTIL didn't run during
    that time.

    I have see one restart error using MIS on Win 7 32 bit for both 1/100 and
    1/101

    I am unsure what the error code was as my batch file is only logging
    date/time to a restart log before it restarts MIS :)

    Best, Paul

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