Hello all... Has anyone ever encountered this: I'm running Mystic 1.12 A31 in Windows XP. It will run for a long time... then once in a while, it will just close without any errors or log entries...
I come in sometimes in the morning, turn on the monitor and MIS is closed... Anyone else???
Hello all... Has anyone ever encountered this: I'm running Mystic 1.12 A31 in Windows XP. It will run for a long time... then once in a while, it will just close without any errors or log entries...
MIS
GOTO LOOP
Now can add a time out in there if needed but pretty sure under XP shouldnt be needed.
Let me know if this helps.
On 03/06/17, Pequito pondered and said...
MIS
GOTO LOOP
Now can add a time out in there if needed but pretty sure under XP shouldnt be needed.
Let me know if this helps.
Aha.. I should have kept reading as I was just sharing the very same looking batch file courtesy of Pequito Help Desk Inc. :)
Actually your commands the TIMEOUT /T will not work on XP why I did not mention that one.
This is more for XP users, anything later can use the TIMEOUT in their batch script.
@ECHO OFF
:LOOP
MIS
ping 192.0.2.2 -n 1 -w %1000 > nul
GOTO LOOP
The above allows XP users to have a 1 second timeout if you wanted more just changed the %1000 to say %5000 for 5 seconds etc.
On 03/06/17, Pequito pondered and said...
Actually your commands the TIMEOUT /T will not work on XP why I did n mention that one.
This is more for XP users, anything later can use the TIMEOUT in thei batch script.
@ECHO OFF
:LOOP
MIS
ping 192.0.2.2 -n 1 -w %1000 > nul
GOTO LOOP
The above allows XP users to have a 1 second timeout if you wanted mo just changed the %1000 to say %5000 for 5 seconds etc.
Ahh.. thanks. Please feel free to share that :)
@Echo On
c:
cd\mystic
:LOOP
MIS
TIMEOUT /T 5
FIDOPOLL KILLBUSY
GOTO LOOP
Pequito;
I don't know why the he%% I did not think of that... My brain must be turning to Jelly from age...
I will try that and see if I have any more Drop Offs.. Many Thanks!
Ahh.. thanks. Please feel free to share that :)
But I just did!
Paul;
Many thanks. I don't know why I did not think of that. Pequito also answered with the same thing. My Aging Brain must not be working as
Almost! Here is one better and I know I posted this before.
IF EXIST \MYSTIC\SEMAPHORE\MIS.BSY (
DEL \MYTSIC\SEMAPHORE\MIS.BSY
For some reason, my system doesn't create the mis.msy semaphore file. The only one that is normally in the semaphore directory is 'nodeinfo.now'. I'm not sure what that one is for, but the file date is 11Jan2017...
On 03/06/17, Pequito pondered and said...
Ahh.. thanks. Please feel free to share that :)
But I just did!
For some reason (I blame a current head cold) I thought this post and my reply were netmails [smacks forehead] - doh!
On 03/06/17, Pequito said the following...
Almost! Here is one better and I know I posted this before.
IF EXIST \MYSTIC\SEMAPHORE\MIS.BSY (
DEL \MYTSIC\SEMAPHORE\MIS.BSY
For some reason, my system doesn't create the mis.msy semaphore file. The only one that is normally in the semaphore directory is 'nodeinfo.now'. I'm not sure what that one is for, but the file date is 11Jan2017...
On 03/06/17, Black Panther pondered and said...
For some reason, my system doesn't create the mis.msy semaphore file. only one that is normally in the semaphore directory is 'nodeinfo.now I'm not sure what that one is for, but the file date is 11Jan2017...
Could be a windows thing I think?
I'd need to check non windows systems to confirm.
I can confirm in windows if you run MIS2 it creates a MIS2.BSY semaphore
For some reason, my system doesn't create the mis.msy semaphore file. only one that is normally in the semaphore directory is 'nodeinfo.now I'm not sure what that one is for, but the file date is 11Jan2017...
Could be a windows thing I think?
I'd need to check non windows systems to confirm.
I can confirm in windows if you run MIS2 it creates a MIS2.BSY semaphore
Should be a MIS.BSY file is MIS is running only, least in the most
current versions anyhow. Believe the nodeinfo.now is a placeholder for node information but currently its an empty file.
Wont be a windows thing this will be a Mystic Version thing, pending on which version you are using and how you have your paths setup and which process you are currently using.
On Linux, I can confirm I most certainly do have an mis.bsy. When I ran mis2, I also got an mis2.bsy. Hope this helps.
On my Win10 system, I'm only using MIS, so I'm not sure on the MIS2.BSY. On my Linux system I am running both MIS and MIS2, and I am only seeing the MIS2.BSY file, along with nodeinfo.now.
On 03/06/17, Pequito pondered and said...
Wont be a windows thing this will be a Mystic Version thing, pending which version you are using and how you have your paths setup and whi process you are currently using.
Not so sure about that, most are running 1.12 A31 and I'm wondering if it could also be confounded by Linux/RPi systems running Mystic in deamon mode whereas in Windows that is not possible.
Since my system runs on a cloud server, -d is a requirement, unless I
want the BBS to shut down the moment I exit the terminal. :)
Distorted wrote to Avon <=-
Since my system runs on a cloud server, -d is a requirement, unless I
want the BBS to shut down the moment I exit the terminal. :)
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 3 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 34:00:34 |
| Calls: | 2,137 |
| Calls today: | 2 |
| Files: | 11,149 |
| D/L today: |
5 files (4,018K bytes) |
| Messages: | 951,025 |