PH> On 05/20/18, Phil Kimble pondered and said...

 PK>> Then logging in locally took a few attempts before mystic finally 
 PK>> picked it up. I am not 100% convinced that it is mystic causing the 
 PK>> issues, may be the OS injecting some issues.  But it is a clean 
 PK>> installation of Slackware 14_64.

 PH> I'm glad you got the problem sorted 
I am thinking it is more of an ESXi/Slackware/MysticBBS issue than just a
MysticBBS error. I was editing menus last night & getting odd delays.  Thinking
 it is a memory/terminal window problem. I rebooted the VM, allocated more RAM
to it & another processor...

 PH> -+- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
 PH>  + Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz 
 PH> (3:770/100)

Thx,
Phil

--- Msged/LNX 6.1.2
 * Origin: Bayhaus.net - Colorado Springs - Serving the FrontRange (1:128/2)