Is there any way to stop isiloX from loading task scheduler?

[huailing]

Hi,

I do not use the Windows task scheduler. I do not WANT to use it. However, every time I run IsiloX, the task scheduler automatically starts up and lands up in my systray and even after exiting isiloX it remains there.

I do not run any scheduled events so there is no need for it. Ive tried setting the option to disable scheduling but it doesn't prevent the loading up of the taks scheduler.

Can anyone tell me a way to stop this behaviour or at least a trick to get rid of it quick. at the moment it takes several mouse clicks and lots of mouse movement to remove it.

Oh I'm also using win 98.

Thanks.

[Voltage Spike]

When you say "disable scheduling", do you mean from here (http://isilox.com/support/manual/iSiloX/ReferenceManual/Options/Scheduling.htm)?

[huailing]

Yes, I've tried checking that option, but on starting iSiloX task scheduler still loads up.

Basically whether the option is checked or not task scheduler always loads up if it hasnt been loaded up in the first place. If i stop task scheduler while isiloX is open, isiloX will reload it again if its unchecked but not bother if its checked.

What I want to do is to prevent it from loading into systray in the first place on starting isiloX.

Thanks.

[iSilo]

iSiloX accesses the Windows scheduler to determine whether there are any conversions scheduled with the Windows scheduler for the currently opened .ixl file and if so obtains the associated account information so that it can update the schedule for the opened .ixl file if necessary. There is no way from preventing iSiloX from performing this check.

If you do not use the Windows Task Scheduler for anything else, then you can disable it. A search on google for "disable windows task scheduler" gave this link http://www.winguides.com/registry/display.php/668/ among others.

[huailing]

Actually I had removed the instances to Task manager (mstask.exe) from the registry years ago and never had it poping up even though it was left in the Windows\System folder. Which leads me to believe that isiloX looks for it in a different way.

I've now taken the more drastic step of deleting the file completely from my system to solve the problem. :D I had left it in the system as deleting random files from that folder was decidedly not a good idea, you never know what you might break :eek:

I had actually noted this annoying behaviour for some time, but was willing to live with it as I wasnt running isiloX more than twice a week, but lately with the new isilo confusing me(categories etc), I was using it (isiloX) way too much and it was driving me crazy while i was trying to figure out how things worked.

Thanks.