A few of us running Mystic A39 for Windows are having a problem shutting
down the mis server. It will not exit out. CTRL ALT Delete won't kill the
task either. Just wondering if any others are experiencing this phenomenon.

|07 |00 |01ú |14H|12a|04wk|07 |04Hubba|12r|14d
|01ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
|14 |01 |08+o |14B|12l|04ack Fl|12a|14g |01ú|09 telnet:blackflagbbs.com|07

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)

On 08/02/18, Hawk Hubbard said the following...

A few of us running Mystic A39 for Windows are having a problem shutting down the mis server. It will not exit out. CTRL ALT Delete won't kill the task either. Just wondering if any others are experiencing this phenomenon.

I never experienced it when I ran Mystic on Win 10 64 bit in fact it exited very quickly. Now running it in a VM of Win 7 32 bit it happens every so often.. Lately it hasn't happened but it did quite a bit when I first moved over to the VM..

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

I've experienced that as well, I run Mystic 64bit on a Windows 2018 R2
server. I've noticed that it will Exit just fine IF I run it, and noone connects to the server. It will exit just fine... However, if 1 person connects up via telnet, then when I go to shut down the server (Noone is currently connected), then it will do the Exiting sequence (countdown to 0),
do the Exiting thing, but the command window will "Hang" and just sit there, doing the Task-Manager will not even shut it down, it says "Not Responding".\

The only way I can get it released is to Restart the system.

Gary Crunk

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/64)
* Origin: New Mystic BBS (21:4/126)

* An ongoing debate between Hawk Hubbard and All rages on ...

A few of us running Mystic A39 for Windows are having a problem
shutting down the mis server. It will not exit out. CTRL ALT Delete
won't kill the task either. Just wondering if any others are
experiencing this phenomenon.

It won't exit if any events are running, but it usually tells you that if they are. {shrug}

It's never happened to me, though. Running under Win 7 Pro 32-bit, also in a VM

under Win XP SP3.

I use Cmdow to terminate window jobs based on screen title and it works great. I request it nicely CLOSE, then Kill it {chuckle}:

http://ritchielawrence.github.io/cmdow/ Source, Docs/Tutorial & Cmdow.Exe

Note: download zip, install Cmdow.Exe in bin\Release folder. Ignore warnings from anti-virus/malware scanners, Cmdow is safe but IS considered a PUP by some

(Potentially Unwanted Program).


.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet|ssh://cmech.dynip.com |
| ______ Email: fido4cmech(at)lusfiber.net |
| { O O } Home page: http://cmech.dynip.com/homepage/ |
| __m___oo___m__ |
`--| | | |- WildCat! BBS 24/7 +1-337-984-4794 any BAUD 8,N,1 -'

... Bush/Cheney '04: Four More Wars.
--- GoldED+/W32-MSVC v1.1.5-g20180717 + Mystic BBS v1.12 A39
* Origin: FSXNet - Positronium: telnet://cmech.dynip.com (21:2/117)

On 08/02/18, Hawk Hubbard said the following...

A few of us running Mystic A39 for Windows are having a problem shutting down the mis server. It will not exit out. CTRL ALT Delete won't kill the task either. Just wondering if any others are experiencing this phenomenon.

hi i am not having this issue.

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic |08[|15dreamland|09.|15darktech|09.|15org|08]

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/64)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

On 08/02/18, garycrunk said the following...

I've experienced that as well, I run Mystic 64bit on a Windows 2018 R2 server. I've noticed that it will Exit just fine IF I run it, and noone connects to the server. It will exit just fine... However, if 1 person connects up via telnet, then when I go to shut down the server (Noone is currently connected), then it will do the Exiting sequence (countdown to 0), do the Exiting thing, but the command window will "Hang" and just
sit there, doing the Task-Manager will not even shut it down, it says
"Not Responding".\

Sounds like a zombie task issue. On Linux that's easier than Windows to solve. Has anyone searched for the task hanging it?

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)