Hi g00r00

I was helping Solaris with his system today - a Win 10 box running 64 bit Mystic, he's having some issues after updating recently. The system was
running a pre-alpha A37 and a version from around 12 December when I checked
on it.

The issues were

With MIS running pressing tab to display 'connections' display causes the
.exe to crash

[snip]

Runtime error 216 at $000000010001E7F2
$000000010001E7F2 line 224 of mystic/MIS_Globals.pas
$0000000100020B8E line 520 of mystic/MIS_Server_Manager.pas
$00000001000209A4 line 579 of mystic/MIS_Server_Manager.pas
$00000001000218D3 line 856 of mystic/MIS_Server_Manager.pas
$0000000100021C54 line 947 of mystic/MIS_Server_Manager.pas
$0000000100001A29 line 82 of mystic/mis.pas
$00000001000022F2 line 250 of mystic/mis.pas
$00000001000023F6
$000000010000EA23
$000000010000F551
$00007FFF24E01FE4
$00007FFF252BEF91

[snip]

Restarting MIS and it's working ok with incoming telnet, events being run
etc. but press TAB and the problem occurs again

Second issue is mystic.exe ... while you can run mystic -ver you can't run a local login or mystic -cfg ... after a 3-4 second pause and blank screen
you're dropped back to the command prompt again.

So I took a backup, updated to the latest version and found the same issues persisted.

I have taken logging data and created x 2 .zip files for you (check your inbound please :)) and hopefully you can shed some light on the probs :)

Thanks for taking a look.

Best, Paul

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

With MIS running pressing tab to display 'connections' display causes the .exe to crash

I've made a fix for a possible crash there for this today (hopefully) by rearranging some code.

Second issue is mystic.exe ... while you can run mystic -ver you can't
run a local login or mystic -cfg ... after a 3-4 second pause and blank screen you're dropped back to the command prompt again.

Are you not running it as Administrator? Literally the only thing that
doesn't access files is -ver, so that would explain it.

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

On 12/28/17, g00r00 pondered and said...

With MIS running pressing tab to display 'connections' display causes .exe to crash

I've made a fix for a possible crash there for this today (hopefully) by rearranging some code.

Thanks :)

Second issue is mystic.exe ... while you can run mystic -ver you can' run a local login or mystic -cfg ... after a 3-4 second pause and bla screen you're dropped back to the command prompt again.

Are you not running it as Administrator? Literally the only thing that doesn't access files is -ver, so that would explain it.

No not that I am aware of and there are other copies of the 'latest' version running on the same box (fsxNet HUB 2) without issue and under the same
access privs.

I wonder if it could be a data file(s) corrupted or with access issues for mystic.exe ?

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