Multible instances?

buckw1 · Post by **buckw1** » Wed Sep 21, 2005 5:11 am

Macro Scheduler is restarting itself at random times when I have only one script running. This puts the start screen in front of active window and screws everything up. Is this a known issue? I guess it could be a virus or other infection but nothing I have detects it......

Don

support · Post by **support** » Wed Sep 21, 2005 7:01 am

Restarting itself!!??

Do you have any schedules set up? Perhaps a script that is scheduled is running Macro Scheduler or focusing itself?

pgriffin · Post by **pgriffin** » Thu Sep 22, 2005 12:46 am

I've had an issue like this in the past. I removed all Hot-Keys in Macro Sched. I found (or at least convinced myself) that sometimes MacroSched could send key strokes to an app that it also intercepted as HotKeys to start a macro.

I have not had the problem since removing the Hotkeys

armsys · Post by **armsys** » Thu Sep 22, 2005 3:02 pm

When assigning a hotkey to a MS script, make sure it won't conflict with keyboard shortcuts of your applications such as Microsoft Word. For example, I assign Ctrl+Alt+M to a MS script to process my MindManager maps, but it's the same keyboard short for commeting in Word. So, I re-wrote my MS script to handle each exception by first detecting the current window.

Definitley, I love hot keys because it saves my time.

buckw1 · Post by **buckw1** » Fri Sep 23, 2005 8:21 pm

Hmm, calling focus to itself is a possibility. No schedules are active, no hotkeys defined. Does not seem to be a known issue so must be something with the script. Will look further.. thanks.

Buck

buckw1 · Post by **buckw1** » Wed Oct 12, 2005 3:31 am

Ok, definitely a program issue. I just formatted and did clean install of XP Pro on my 2nd sytem this weekend. Synamtec Virus running from server. Office 2003 installed locally. Macroscheduler installed and the game that it controls.
Fresh install of version 7.4??? from this site. Macro will run no problem for about 8-12 hrs then a new instance will pop up. Going back to 7.3 resolved this issue. If no idea on cause what can I do to troubleshoot?

CyberCitizen · Post by **CyberCitizen** » Wed Oct 12, 2005 3:45 am

Do A Step By Step Though Your Script & Find Out Where The Error Happens, Turn On Logging, Post The Script.

All These Things Will Help Find The Problem.

buckw1 · Post by **buckw1** » Thu Oct 13, 2005 4:39 am

No script has to be running, just MacroScheduler itself.