Published on October 6, 2005 By seapup In WindowBlinds
After installing the new WindowBlinds nothing would install but the classic design, so I click the apply button twice and now it's working? Thought I rely that for what it's worth I did also get an error code under Troubleshooting which was: WindowBlinds 5 BETA Troubleshooting Report: STATUS : WB+ SRV+ HLP+ UI+ WindowBlinds is installed correctly on this PC. WindowBlinds appears to be activated on this PC Your machine supports per pixel borders on WindowBlinds skins. You have one monitor in total. (Dell E771a) 1 is attached to NVIDIA GeForce2 MX/MX 400 '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. Have no idea what the above means, but some of the glass effects don't seem to work on my computer.
Comments (Page 1)
2 Pages1 2 
on Oct 10, 2005
Which version of the Windowblinds5 Beta are you using and which version of Windows (including service packs)?

-Mike
[Stardock Support]
on Oct 10, 2005
I too only get the Classic Skin and have installed the 4.90d[b].002 build from Saturday.

I have gotten an e-mail back with a sig.bin file included from Stardock, but that did not help. I copied off all my old skins to a "WB_old" directory and uninstalled the WB5 beta then re-installed. This time it said it activated and installed successfully. I rebooted, but the WB Config started up right after reboot and would not load when I clicked on "Apply Changes" after choosing a skin. I can copy my sig.bin file into the directory and click on Troubleshooting and it shows as "it appears to be activated", but after I click on "Apply Changes", I can see that file disappear from the directory and nothing happens and I have the following show up when I click on "Troubleshooting".

Please help!!!!

Thanks in advance,
Craig (cmuggle)

WindowBlinds 5 BETA Troubleshooting Report:

STATUS : WB+ SRV+ HLP+ UI+

WindowBlinds is installed correctly on this PC.

WindowBlinds has not been activated correctly on this PC. Please activate it from SDC.

Your machine supports per pixel borders on WindowBlinds skins.

You have one monitor in total.

(Plug and Play Monitor) 1 is attached to Intel(R) 82865G Graphics Controller
'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.


Posted via WinCustomize Browser/Stardock Central
on Oct 10, 2005
The version of WB is 5.490d [b] now seems to have resolved the issue of installing the skin

Still getting the error code under troublshooting, although I do have an older Nvida 2 MX400 card (drivers are updated).

Thanks for your help.
on Oct 10, 2005
Sorry forgot part of your question Running XP Service Pack 2
on Oct 10, 2005
I'm glad to hear everything's working. As far as the video card, you might want to update it to get full support. Geforce 2's are much older and incapable of newer features that current video cards support.

-Mike
[Stardock Support]
on Oct 10, 2005
cmuggle: Please try uninstalling, rebooting, and reinstalling again, I have fixed a glitch in your account info.

-Mike
[Stardock Support]
on Oct 10, 2005
Thanks, but that did not fix the issue. Same problems. I have dropped back and punted to WB 4.60 for now. The Apply Changes button is not active or selectable. It says that it is not active still in the trouble shooting option.



I have uninstalled 4.60, rebooted, installed 5, rebooted, found issues, uninstalled 5, rebooted, installed 4.60 again.


Posted via WinCustomize Browser/Stardock Central
on Oct 11, 2005
cmuggle: It looks like there was yet another issue in your account info that I had overlooked. If you're interested, you could try installing the WB5 Beta again. Since it parses this information when registering your product, even a successful activation on our end could mean you still have issues (it shows two successful activations here). We apologize for your trouble!

-Mike
[Stardock Support]
on Oct 13, 2005
Thanks for your help. I tried one more time with help from Kris Kwilas re-sending the sig.bin file. I installed and then before I rebooted, I ran the wbconfig.exe to select a skin and then before rebooting copied the sig.bin file to my WB directory. When my system restarted WB5 was active and working just fine.

I'm also trying the latest Object Bar 2 beta right now (I'm realy on the "bleeding-edge) too with the Stardock Virtual Desktops as a plug-in on the Control Center theme that I have modified. That plus RightClick running all the time seems to be working well.

These are my 4 gotta-haves from SD (not counting CursorXP).

I have noticed that neither RightClick or Object Bar 2 remember the settings for "Hide Windows Taskbar" after reboot and OB2 doesn't remember to "Hide Desktop Icons" after reboot. What gives?


Posted via WinCustomize Browser/Stardock Central
on Oct 13, 2005
Glad to hear you're finally up and running with the latest betas

Not sure why the changes aren't holding over until the next reboot, but I've forwarded the issue to the development team.

As far as the "Hide desktop Icons" issue, you could actually use a Windows setting which should save the changes. This can be found by right-clicking on the desktop, going to "Arrange Icons By" and unchecking "Show Desktop Icons"

-Mike
[Stardock Support]
on Oct 15, 2005
Okay, I load WB 5 (latest and greatest download as of tonight Oct. 15th and I am having the same problem I have been having. All it will load is Classic and when I unload it keeps that Classic skin and I have to go into the perfomance control pannel and make "any" small change and then click apply and voila Windows XP's theme returns. I have uninstalled, reinstalled 4.6, uninstalled 4.6 and then reinstalled 5 a few times to no avail. I have tried clicking the apply button a couple of times, again to no avail.
I have been reading the forums and some folks are having this problem like above but seem to have stumbled upon a fix. Weird thing is they are all saying they recieved an error code, or at least that's what I remember. I have not recieved any error codes.... but I don't get the little screen telling me to be patient as it changes the theme. The screen flashes a few times, but nothing changes but to see the classic thing come back. HELP.
on Oct 15, 2005
Okay, I load WB 5 (latest and greatest download as of tonight Oct. 15th and I am having the same problem I have been having. All it will load is Classic and when I unload it keeps that Classic skin and I have to go into the perfomance control pannel and make "any" small change and then click apply and voila Windows XP's theme returns. I have uninstalled, reinstalled 4.6, uninstalled 4.6 and then reinstalled 5 a few times to no avail. I have tried clicking the apply button a couple of times, again to no avail.
I have been reading the forums and some folks are having this problem like above but seem to have stumbled upon a fix. Weird thing is they are all saying they recieved an error code, or at least that's what I remember. I have not recieved any error codes.... but I don't get the little screen telling me to be patient as it changes the theme. The screen flashes a few times, but nothing changes but to see the classic thing come back. HELP.
on Oct 15, 2005
Sorry... I forgot to mention. I am running Windows XP SP-2, should be fully updated. On a Dell 8600 with an ATI 9600 and 128 Megs of VRAM. The Dell has a resolution of 1920x1200 and a gig of physical memory. I am running a few other StarDock apps and a compliment of other Widget programs and the like. Pretty standard stuff though.
on Oct 15, 2005
BTW---- I don't see a Windows Blind icon in the SysTray, is this by design? I thought in 4.6 there was one, although I had it hidden. I don't see any for 5.0, was wondering if that was somehow attached to my bigger problem.
on Oct 15, 2005
Okay, now I see where the error is coming into play... course now I have to see if I can figure out what has gone wrong beyond the obvious that it isn't activated.
2 Pages1 2