[sopoku]

I've had my avedesk working for ages but now it crashes all the time when i trie to add a text overlay to any config.
Error log file attached.

Help would be appreciated.

Sorry for my bad english

Attached File(s)

•  6b4e_appcompat.txt (39.25K)
  Number of downloads: 35

[technosinner]

Have you tried starting over with a new theme to see if it crashes?

[sopoku]

technosinner, on Feb 27th 2009, 02:14 AM, said:

Have you tried starting over with a new theme to see if it crashes?

Hi technosinner,

Yes, I've tried with a new clean theme and it still crashes.It seems the problem it's caused by sysstats, because it also occurs when i try to use sysstats with another application like rocket dock or object dock. Clean up my registry, made a fresh install of sysstats and it still crashes. By the way, i had avedesk running with sysstats for a least a year without problems, but I've had to reinstall to computer and after that i've never managed to make him work. All the configs that i was running won't load the text overlay class and every time i try to add a text overlay class to a config old or new it crashes. By the way my OS is XP Pro Sp3.

Thanks for your help

This post has been edited by sopoku: 27 February 2009 - 12:08 PM

[technosinner]

Ok... strange in deed. Which version of Ave and SysStats do you have? I found Ave 1.4 was unbelievably buggy under XP so I had to downgrade to 1.3. Also there was a version of SysStats going around that was faulty. The latest is 2.5.11 if I'm not mistaking, and you're better off getting it straight from judge's site here.

It does sound like a sysstat issue though, more than Avedesk. Just to make sure, try to run Ave without any Sysstats items activated. We should continue this in your topic in the Systats forum... I'll reply there as well.

Keep me posted, although I have to warn you I'm not exactly a programmer so my usefulness might go to the lew soon enough

This post has been edited by technosinner: 27 February 2009 - 08:05 PM

[sopoku]

Hi all,

Thanks for your help guys but the problem was recently solved by a clean install of my OS. I think it was something wrong with some windows file and not with any of the avedesk or sysstats components.
I think this post can now be closed.

Thx again.