Tixati 1.99.1 on XP SP3 32-bit.
Tixati launches every night by script and shuts itself down when all complete. This has been working fine for several months.
A couple of nights ago I found Tixati frozen with 97-100% CPU utilization and UI window open but blank (no UI elements). Could not get a response from UI window or taskbar icon so killed Tixati with task manager.
Restartng Tixati still hangs on blank UI at startup with 97-100% CPU -- every time.
Uninstalling/reinstalling Tixati did not fix it.
Deleting contents of C:\Documents and Settings\<user>\Application Data\tixati allowed me to launch Tixati successfully again and take all defaults.
I routinely export all settings. So next step imported all settings from last export (created about three weeks ago) and when Tixati restarted after import again it hung on blank UI and 97-100% CPU.
Trial and error got it down to successfully importing all settings except Scheduler.
I had saved off the scheduler2.dat file from one of my attempts to import all settings. I shut down the working Tixati and replaced the "empty" scheduler2.dat with the "bad" scheduler2.dat in above directory.
Restarted Tixati and reproduced the hang with 97-100% CPU. Killed Tixati and erased the "bad" scheduler2.dat file, Tixati launched successfully again.
Tixati has launched fine every day since that export was made, until a couple of days ago. So it doesn't appear to be the scheduler file itself, rather something else has changed to make the scheduler2.dat file become the trigger? What can I check?
Kind regards,
--appyface
