• Mystic on Win10

    From Dan Richter@21:1/186 to All on Sunday, January 08, 2017 00:54:00
    So, I'm setting up Mystic on this computer, which will be replacing Synchronet as my main system. I've got a message network set up, and received netmail and echomail.

    The problem I'm having, is when I run "mutil mailin", it will toss about 25 to 40 messages, and exit out with "Runtime error 216". I can't find that error listed anywhere in the docs. The only indication is from the log which states:

    Jan 08 00:47:03 Shutdown Corrupted memory (216)

    Is this an error with Mysic, or is there a problem with the computer? I'm not even utilizing half of my system memory.

    Any help would be appreciated.

    Thanks.



    Dan Richter
    aka Black Panther
    Sysop
    Castle Rock BBS
    Rio Rancho, NM



    Profanity is the one language all programmers know best.
    --- SBBSecho 3.00-Win32
    * Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)
  • From Avon@21:1/101 to Dan Richter on Sunday, January 08, 2017 21:08:00
    On 01/08/17, Dan Richter pondered and said...

    The problem I'm having, is when I run "mutil mailin", it will toss about 25 to 40 messages, and exit out with "Runtime error 216". I can't find that error listed anywhere in the docs. The only indication is from the log which states:

    Likely to be an issue with a message base file rather than a windows 10 issue.

    Is this an error with Mysic, or is there a problem with the computer?
    I'm not even utilizing half of my system memory.

    I'd say it's a corrupt message base file and not a windows thing. It has happened to others also that don't run windows.

    What do your level 3 logs show when it cans out?

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From Dan Richter@21:1/186 to Avon on Sunday, January 08, 2017 01:32:00
    Re: Re: Mystic on Win10
    By: Avon to Dan Richter on Sun Jan 08 2017 21:08:00

    The problem I'm having, is when I run "mutil mailin", it will toss
    about 25 to 40 messages, and exit out with "Runtime error 216". I
    can't find that error listed anywhere in the docs. The only
    indication is from the log which states:

    Likely to be an issue with a message base file rather than a windows 10 issue.

    Ok, that makes me feel better. The message bases have all just been set up. It's a fresh install of Mystic...

    I'd say it's a corrupt message base file and not a windows thing. It has happened to others also that don't run windows.

    Does Mystic have a way of fixing these message bases, or should I delete them, and start over?

    What do your level 3 logs show when it cans out?

    I did just notice that every time is errors out, it had just found a duplicate message. Here's a clip from the mutil.log

    + Jan 08 00:56:04 Import #5476 to AGN_ADS
    + Jan 08 00:56:04 Import #5477 to AGN_ADS
    ! Jan 08 00:56:04 Duplicate message found in AGN_ADS
    + Jan 08 00:56:04 Shutdown Corrupted memory (216)

    Every time it errored, it had just reported a duplicate.



    Dan Richter
    aka Black Panther
    Sysop
    Castle Rock BBS
    Rio Rancho, NM



    It would be illogical to assume that all conditions remain stable.
    --- SBBSecho 3.00-Win32
    * Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)
  • From Dan Richter@21:1/186 to Avon on Sunday, January 08, 2017 01:38:00
    Re: Re: Mystic on Win10
    By: Avon to Dan Richter on Sun Jan 08 2017 21:08:00

    I'd say it's a corrupt message base file and not a windows thing. It has happened to others also that don't run windows.

    What do your level 3 logs show when it cans out?

    Nevermind. I found out where the problem was. I had my mailin.ini set to save the dupe messages into a message base. I commented that line out, and reran the mailin process, and it worked just fine. There must have been a problem in trying to save the message to the bad message area. I'll have to look into it.

    Thanks, Paul.



    Dan Richter
    aka Black Panther
    Sysop
    Castle Rock BBS
    Rio Rancho, NM



    Everyone has his day, and some days last longer than others.
    --- SBBSecho 3.00-Win32
    * Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)
  • From Avon@21:1/101 to Dan Richter on Sunday, January 08, 2017 22:00:00
    On 01/08/17, Dan Richter pondered and said...

    Nevermind. I found out where the problem was. I had my mailin.ini set to save the dupe messages into a message base. I commented that line out,
    and reran the mailin process, and it worked just fine. There must have been a problem in trying to save the message to the bad message area.
    I'll have to look into it.

    Make sure you have the dupe base set up as a 'local' type :)

    Best, Paul

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