WindowBlinds 5 Beta 1 - Same Problem

from Stardock Forums
I did what everyone else has done. My troubleshooting message reads:-

WindowBlinds 5 BETA Troubleshooting Report:


WindowBlinds is installed correctly on this PC.

Your machine supports per pixel borders on WindowBlinds skins.

If you suffer visible corruption (overbright) on the frames and have a NVIDIA board then please be aware this is a NVIDIA bug. It has been seen on GeForce 4 cards and some FX series cards.

Video Information

You have one monitor in total.

(CTX PR960F series) 1 is attached to NVIDIA GeForce 6800 GT

'NetMeeting driver' also exists as device '\\.\DISPLAYV1', but is not attached to the desktop and is a mirror driver.

'RDPDD Chained DD' also exists as device '\\.\DISPLAYV2', but is not attached to the desktop and is a mirror driver.

PLEASE report all this information when submitting a problem report, especially anything related to per-pixel skinning. We don't know what's in that Dell you bought last July or the notebook the office gave you. Per-pixel skinning requires your drivers to at least claim to support the functions needed for it.

I am running Windows XP SP2 on an Athlon XP 2400+, with 1MB of RAM and a Sparkle 6800GT graphics card. I too have the classic desktop: I don't like it!

Ian
2,947 views 3 replies
Reply #1 from WinCustomize Forums Top
What problem are you receiving? Please be as specific as possible. ("Same problem" is not descriptive enough)

-Mike
[Stardock Support]
Reply #2 from WinCustomize Forums Top
Sorry, my problem was being stuck with the classic desktop! However, the next version of the beta has cured that.

There is another problem with the latest beta, which I have just reported to you. It concerns Copernic Agent Personal. If I have not given enough detail please let me know. I can always send you a screen capture so you can see what's going on.

Best wishes

Ian
Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from WinCustomize Forums Top
Glad to hear your first issue was resolved. A screenshot would definitely help, yes. Did this issue surface just after your last update, or was it apparent since installing the WB5 Beta?

-Mike
[Stardock Support]