xxZeroVirusxx xxZeroVirusxx

WindowBlinds 5 Trouble Already =(

WindowBlinds 5 Trouble Already =(

Why Wont it Work?!

I just upgraded my WindowBlinds to 5.0. It just put my computer into Windows Classic mode. I restarted. Same thing. I checked troubleshooting, and it gave me this message:

-------------------
WindowBlinds 5 BETA Troubleshooting Report:


WindowBlinds is not installed correctly on this PC. If you did not reboot after installing WindowBlinds 5 for the first time, then please reboot and try this again.

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.

(Gateway VX700) 1 is attached to RADEON 9600 PRO Family (Microsoft Corporation)

'RADEON 9600 PRO SEC Family (Microsoft Corporation)' also exists as device '\\.\DISPLAY2', but is not attached to the desktop.

'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.
----------------------------

Isn't installed correctly?! So I uninstalled it, then reinstalled it, and rebooted again. Still, same problem, same message.

By the by, I have Windows XP x64. Is this going to be a problem?
87,943 views 170 replies
Reply #51 Top
The update thats just been released has fixed all my nvidia problems
Reply #52 Top
I thought for sure I would be shafted on this and am amazed that it works.


I hate you Duane
Reply #53 Top
backing up what skins i have befor uninstalling. going to try the fresh install and see how that works
Reply #54 Top
So the one configuration they said wouldn't work does actually work, =P. Is there any x64-er out there willing to try post #45 please? I would but I'm slightly busy and I can't stand the Windows Classic theme.
Reply #55 Top
I pretty much had the same problems as everybody else, but...
After a total uninstall of "Stardock" produkts, 1 reboot and intalling ONLY WB 5,
I've finally got it to work... well... not smooth as silk, but it's up and running!
Let me tell ya, it looks pretty neat.
Still have problem changing skins, tough!

Keep trying, don't give up!



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.

(Dell 1905FP (Digital)) 1 is attached to NVIDIA GeForce 6800 Series GPU

'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.
Reply #56 Top
Ok... I uninstalled WB4 and tried again.
The window rendering issues are solved now and WB5 looks great, however I still experience the start menu problems and I can't access my display property applet.
I'll test WB5 again for incompatibilities with WindowFX and then I'll report here.

I suggest Stardock to write down in WB5 product description in Stardock central that they strongly suggest to remove any previous installed version of WB prior to installing this one
Reply #57 Top
this thing isnt loving my 6800 ultra in my xps2 laptop all kinds of random flukes, and even switching to normal themes after requires i load it a few times. wasnt too bright on my part, shouldve installed this on my play rig, not work horse.
Reply #58 Top
I've completely uninstalled and erased WB4. I'm trying WB5 again. I'm expecting this not to work and I'm expecting to revert back. Answer to the x64 question after reboot.
Reply #59 Top
Of course--still doesn't work. Reverting back to 4.6.

It's good to hear that most people are getting it to work at least slightly better after suggestedf ixes. I just wish SD would release an x64 version .
Reply #60 Top

The beta release of WindowBlinds 5 does NOT support 64 bit windows.  No amount of fiddling will get it to work correctly on that OS.

Once we are happy with the beta of WB5, we will build the 64 bit dlls.

Reply #61 Top
Upgraded and rebooted, WB 5 doesn't load any skins. Uninstalled, rebooted reinstalled, still no luck. Also getting a black spot in all the config dialogs. I have a screen shot if someone wants to see it. I also get the not installed correctly error in the troubleshooting screen.
Reply #62 Top
installed a few times on my play rig (ati x800 xl), normal windows home, and it wont load any skins at all. i uninstalled, reinstalled, same thing.
Reply #63 Top
That's pretty clear. But most programs that say that they don't support x64 still work to a degree. I wanted to test all aspects and see if this was the case with WB. I'm pretty sure my last post says that WB5 simply won't work with x64. Pshh and you're getting all angry at me and whatnot.

Oh, but thanks for the 64 update. I hope you're happy soon ^_^.
Reply #64 Top
Bah, I've given up trying. Maybe if those of you that got it working, explain step by step what you did, that'd be great...
Reply #65 Top
I've tried everything I can think of (including not restarting, just to see what'll happen ) and nothing seems to work whatsoever. Hope there's a fix coming out soon!
Reply #66 Top
Just installed, no problems at all, I forgot to mess with the classic windows thing, I just installed and rebooted as it asked and so far looks and works just fine
Reply #67 Top
It looked like it installed correctly but I get this>>>

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.

(Plug and Play Monitor) 1 is attached to NVIDIA GeForce2 GTS/GeForce2 Pro

'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.
Reply #68 Top
Works fine for me with GeForce4 MX, GeForce FX5200 and GeForce 6600GT

But, first Wb5 build (4.90[b].002) with GeForce4 & FX5200 --> corruption (overbright)
and, second Wb5 build (4.90a[b].002) with GeForce4 & FX5200 --> NO corruption (overbright)
Reply #71 Top
Wow you guys have a bunch of problems, my only problem was it just wouldn't load themes or suites correctly, it would no longer load them from my object desktop manager, I had to physically go into Windowblinds, oh yeah and my toolbar icons wouldn't load to the skin, even manually
Reply #72 Top
It appears to have installed correctly, but will not apply any WB skins. When I try to apply a skin through display properties it brings up the Please Wait dialog, but reverts to classic. When I try to apply through WB Config Window, nothing at all happens. Updated my driver, even switched back to my onboard video card, but had identical results.

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.

(Plug and Play Monitor) 1 is attached to NVIDIA GeForce FX 5200

'Intel(R) 82845G/GL/GE/PE/GV Graphics Controller' also exists as device '\\.\DISPLAY2', but is not attached to the desktop.

'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
Reply #73 Top

It's been less than 3 hours here since it went up. And it's suddenly got a lot more users than in testing.

We've done a 4.90a build with a fix we were able to find for the nvidia driver issue. Please update to that and it should sort the over-bright saturation, can't drag the window issue. Make sure you reboot.

There's a problem reported with the winzip main interface, but not the context menus. We'll be looking at that. One or two reports above of issues with machines prior to SP2 (rundll32 issues?), will check into that as well. This isn't an x64 beta build. The systray icon is not present in this build. We'll look into the AIM Messenger:Mate problem. If you have ghost images on the taskbar, screenshot that and note if locking/unlocking the taskbar makes any difference.

If in doubt, set the skin to classic, remove the files from the WindowBlinds dir (you can keep the subdirs with your skins), rename any that are left, reboot, remove any files that were left in the root of the WB dir, reinstall 4.90a or later, reboot. Run wbconfig.exe to select a skin and get started.

Activate.exe from the SDCentral dir needs to be able to get to the internet at install time to activate the beta build (there will be a sig.bin in the directory after it does that). You can right-click on the WB5 item in Stardock Central and force it to try and activate, but do it too many times and it'll stop. Email kwilas@stardock.com if you pass the threshold. Or if the sig.bin isn't there, find the activate.log from the SDCentral dir and email it to kwilas@stardock.com.

If Stardock Central is exiting at the end of the install, you didn't let it update to the latest version. Please let it do so or reinstall it from http://storage.stardock.com/files/sdcentral_setup.exe.

These files should be in the WindowBlinds dir. There are others, but these are the ones with the mojo, so to speak.

 9/05/05  19:14          90,624  wbui.dll
 9/06/05  15:26         167,936  wbdb.dll
 9/06/05  18:04         232,960  wbload.exe
10/03/05  13:44          49,152  Screen.exe
varies                                   sig.bin
10/04/05  16:18         172,032  WbSrv.dll
varies                                   Skins.mdb
10/04/05  20:11         276,992  wbconfig.exe
10/04/05  23:20         500,818  wblind.dll

SkinStudio 4.90 should be available for download by the time you read this.

Reply #75 Top
i have, and same problem =/ it is working on my laptop now without quirks however, after doing uninstall first, then reinstall.