Newest WB update

Please post your system info from WB.

Your computer has a Windows Experience Index base score of 4.2
Your Windows Graphics Experience score is 5.9

WindowBlinds version : WindowBlinds 6.02 (build 74 x86 - Vista Edition)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(SyncMaster 2232BW/2232GW/2232GW Plus,SyncMaster Magic CX2232GW(Analog)) 1 is attached to NVIDIA GeForce 8600M GT

Wblind.dll 2008/01/14 17:02:20
Wbsrv.dll 2008/01/14 17:02:35
Wbconfig.exe 2008/01/14 17:02:35
Wbload.exe 2007/09/27 17:47:44
Wbhelp.dll 2007/08/27 11:54:07
Tray.dll 2007/09/12 17:58:21
Wbload.dll 2007/09/12 17:58:28
Screen.exe 2008/01/14 17:02:18

I am having the exact same problem after updating to WB 6.02.024.



Your computer has a Windows Experience Index base score of 1
Your Windows Graphics Experience score is 1.9

WindowBlinds version : WindowBlinds 6.02 (build 74 x86 - Vista Edition)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(Generic PnP Monitor) 1 is attached to Intel(R) 82915G/GV/910GL Express Chipset Family (Microsoft Corporation - XDDM)

Wblind.dll 2008/01/14 17:02:20
Wbsrv.dll 2008/01/14 17:02:35
Wbconfig.exe 2008/01/14 17:02:35
Wbload.exe 2007/09/27 17:47:44
Wbhelp.dll 2007/08/27 11:54:07
Tray.dll 2007/09/12 17:58:21
Wbload.dll 2007/09/12 17:58:28
Screen.exe 2008/01/14 17:02:18


On first and second open:


Third time's a charm:

Ideas, anyone?

I didn't know you can run WB with a Windows Graphics Experience score of 1.9. I know at the bottom of the System Info it says at least 2.

I actuall had WB on my old Laptop with a WGE of 1 working fine, slow but fine. What did I expect with an ATI graphic card with only 16mb. LOL

It's never been slow. Very fast, actually. No Aero obviously, but works just fine (until the last update that is).

Well, until this issue is fixed, I've unloaded WB as it works roughly 2/3 the time.

(:(

Same problem under Vista.

@UncleSpellbinder & Dizplaced: Report this problem via Stardock Helpserve
Don't forget to include DxDiag and system info from WindowBlinds.

Thanks. I submitted a ticket.

I have submitted a ticket for this type of issue, but it only appears to affect MS Money.
The last version that did not seem to affect this program was 6.00, I think! I may well restore an archive.

This is for XP SP2.

Why not just exclude MS Money from being skinned?
Can you post a screenshot of the error in MS Money?  It might help the devs.

MS money main window is excluded by design.  It does not have a skinnable titlebar.

Because I do not want to exclude it. It is only the main window that is affected: call outs are skinned. How do I post a screenshot onto the forum?

It used to have and there have been fleeting glimpses of it without the maximize button.

Upload to a hosting site like imageshack.us.  Click the image icon at the top right of the editor. paste in the URL.

Well, here in Vista Home Premium, it's any program window and/or explorer window - completely random. Just now, on system start, Vista's status bar was not skinned. Rebooted and it was. Very odd.

Can you fire up a ticket with us at support@stardock.com? 

I have an open ticket at eSupport (for some reason it shows up as 2 different tickets) - APK-914022 and BOP-708546

Is there somewhere else I should submit?

Here is the first attempt at inserting a picture of MS Money using WB 6.02 .
Given up. I am away for the weekend in a moment and given the pressure of time, can't solve the method of displaying the image in a post.
Back sometime Monday.

http://img442.imageshack.us/my.php?image=wb602sv1.jpg <-- link to the page

Fixed for you [imageshack being a little flakey - best I could do]

No response yet from eSupport regarding the submitted ticket. Hopefully, it's just because of the weekend.

Very likely.  I promise they'll get to you.

Thanks.

Many thanks! It does seem a little flaky at the moment. I have restored an archive - 6.00.005 and MS Money is skinned. Trying to upload a screenshot at the moment, but things are slow and am getting "Gateway Time Out"