Today I rebooted my pc, and when I started it back up and started MUSHclient, its timers wouldn't fire. If I add a new timer it will maybe fire once and then stop firing. I have no idea what that is about, I have tested the PC's memory and it appears to have no errors. What could this be?
Timers not firing.
Posted by Poromenos on Fri 10 Nov 2006 03:07 AM — 12 posts, 41,043 views.
I don't know why this would suddenly happen. What OS are you using? XP?
Remember, timers by default don't fire on a disconnected world, so it can be a trap to try scripting with timers that fire every second, if you are disconnected.
Remember, timers by default don't fire on a disconnected world, so it can be a trap to try scripting with timers that fire every second, if you are disconnected.
I'm using 2003 server, it has been working fine for a year now. It's very odd, the worlds are connected normally, I add a one second timer and it fires once and then stops. I hope it's something really stupid on my part, but I haven't changed anything and the timers are all enabled.
Tried reinstalling MC? I'd suggest to also try a registry fix, but I dunno.
Yes, I reinstalled it a few times, even trying old versions. I deleted most of the old registry data, and still nothing. The timers are just not firing :(
are the timers set to run at an interval less than 1 whole second? if so you might need to set in global preferences, the timer delay to 0 (zero), so that they can fire at 1/10th a second delays as well
Have you tried that?
Laterzzz,
Onoitsu2
Have you tried that?
Laterzzz,
Onoitsu2
No, they're 2-3 seconds. They run anywhere from 0-3 times after I set them and then stop. This is on a new world with no scripts or plugins as well as old worlds. It makes no sense at all.
I can't explain that, but you seem to be the only one amongst thousands of users it is happening to.
It is probably something to do with the operating system, or maybe something else you installed. Timers are implemented by an operating system call that raises a "timer event". Somehow that is not getting through maybe.
It is probably something to do with the operating system, or maybe something else you installed. Timers are implemented by an operating system call that raises a "timer event". Somehow that is not getting through maybe.
Hmm, not only that, but I've been using MUSHclient for 6 years or so and it's never happened before. So the system isn't raising timer events? Is there any other way you can think of that I might be able to check that?
I don't know, maybe they are being absorbed by something else you have installed. Maybe the event queue is full. Hard to say. Try installing something that probably users timers, like a stopwatch or something like that.
Quote:
I deleted most of the old registry data, and still nothing.
I deleted most of the old registry data, and still nothing.
I would uninstall and reinstall. That deletes all the registry data.
If you can't get it to work, as a last resort I would try these things:
- Uninstall and reinstall MUSHclient, preferably into a new directory.
- Run an anti-virus checker.
- Run a hardware checker - maybe your clock chip, or whatever it is that generates timer events, is faulty.
- Re-install Windows.
It might sound extreme to reinstall Windows, but out of tens of thousands of copies of MUSHclient "in the wild" you seem to be the only one with this problem, so it sounds like something particular to your PC. Doing that would also clear out any obscure viruses or trojan horses.
I've done most of these, I was hoping more for a way to troubleshoot this problem than an actual bug in MUSHclient. I think there's something wrong with windows as well, looks like I'm going to have to reinstall after all...