SUPPORT: Trillian and Vista Aero

[cobrax2]

Please, can somebody answer to the problem stated in a few posts about windows vista reversing to vista basic theme when trillian loads?
I am using vista rtm ultimate and for the first time in a few years i am thinking of dropping trillian because it has this problem...
i do not know if it is quicktime related or what, because it seems to be appearing somewhat randomly... yesterday it was working, today it isn't. i tried installing or unsintalling quicktime latest version, deleting av plugin, setting compatibility to everything possible, and nothing :((
please, stop for a few moments the developing the new trillian and issue a small fix to the old one.

thank you very much

[iniquitous]

The real / quick answer:

http://blogs.msdn.com/kamvedbrat/archive/2006/04/02/566788.aspx

Real-world examples of when you might see this are Apple's QuickTime Player & iTunes software. When they start up, they use DirectDraw to get access to the front buffer, even though they aren’t full-screen applications. Luckily – you can work around this! Here’s how:

1. Open Quicktime preferences by selecting “Preferences” and then “QuickTime Preferences…” from the “Edit” menu in the QuickTime player application. A dialog box will pop up, with the title: “Quicktime Settings”.
2. Select the “Advanced” tab in this dialog, and in the third section from the top, called “Video” select “Safe Mode (GDI Only)”
3. Close the QuickTime player, and exit the QuickTime system tray application as well

Worked for me.

[Ithildir]

I've read a number of people were having problems. where some had to diable the av.dll plugin while others have had to set their quicktime settings to GDI (safemode only) I have another avenue for some that it hasn't worked for and has nothing to do with Trillian. My laptop has one of thoes built in webcams. If I load the drivers for that then Trillian will not load due to the av.dll plugin as well as the yahoo plugin because of the webcam. As soon as i remove the webcam and don't install the drivers this corrects it. These are the drivers that are coming from MS directly from windows updates. Hope this helps some people.

[ameoba]

Updating to 3.1.5.1 can also resolve this problem.