See if you can give it a try.

Hey everyone,

I have a problem with WindowFX where (In a breif explination) where when it's enabled none of the transitions work; it's extremley sluggish (As if i had the default Windows video drivers installed) and just about only the drop shadow works. Before you ask, i have an ATi Radeon X800XL 256MB AGP video card, and the most recent drivers (Not that it matters, i've tried about three different driver versions). And, i've tried WinFX v1.11, v1.12, and v1.12 Free and they all have the same symptoms. I have the exact same problem on my laptop, with an ATi Mobility Radeon X600 PCI-e 256MB video card. There must be something in common to the two PC's to be causing this. Basically, stardock made me repeat my e-mail 50 times and gave me not even a possible idea to why i'm having this problem on two seperate computers. Please, take a look at what they said, maybe you guys can help me out! Link is below:

http://home.comcast.net/~cody00zero/stardock/stardock.htm

P.S. I also tried a nVidia FX 5700 256MB card with latest drivers. Same result. Could my patched uxtheme.dll be the problem. Thanks in advance!
1,762 views 2 replies
Reply #1 Top
the email you gave them won't work for them unless you purchased WindowsFX with that address. Hence the asking of order number, serial, etc (which if you have, you don't want to post)

The latest version available (paid) is 2.20c[b].003. I think Mike was leading towards getting you to update to that through SDC. just a guess.

I noticed you said it doesn't work with WB5. I don't think they are compatible yet (though some have said to have no real problems)- it even mentions this (or did) when you click system info in WB Configure

i have no idea....shooting craps here

have no idea about any effect due to the uxtheme thing either. I'll just wander off now.....
Reply #2 Top
Well, what makes me angry is that WindowFX won't apply ANY shadow, nor ANY effect to explorer at all (Only programs NOT part of explorer, such as Firefox, etc). even when using WindowsClassic! This happens on two totally different PC's -- yet no one has experienced this bug! How can it be happening both computers [with different hardware] yet be so rare?