Yes...I have. Now I uninstalled, rebooted, deleted WB Folder, rebooted, I'm now reinstalling...we'll see. It just finished installing and asked me if I'd like to run it. No reboot message. Shouldn't it be prompting me to reboot?

No luck...oh well, I'm out of patience for today. Will try the next build.

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.

I did all of that, and still nothing. "Apply Skin" does nothing, and there's some black spots like a user said previously.
It activated right too (I saw in the status message part where it normally says "Downloading", "Activating..." then "Activated Successfully").
I know it's still beta, but I got really hyped about it.. So in all honesty it's quite a disappointment. However, I'm sure SD is doing all it can to resolve the issue.
Complaining wont solve anything, so I'll leave it as that.
And if it's of any relevance, in Component Tray, it lists "Window Blinds" AND "Window Blinds 5", there's also no uninstall option in Add/Remove programs..

Why the hell would you not make a 64 bit version at the same time. Just because its 64 doesn't mean we don't pay the same price for this..

While at first I was going to tell iotc that he's wrong for being so angry, upon thinking about things I realize that he is indeed correct.

I already paid for OD. Assuming that a 64-bit version of WB5 is coming out soon, I'm not going to get too upset. However, what about all of the people who had 64-bit, saw those amazing screenshots of WB5, and immediately purchased WB or OD? They thought that they were getting WB5, but they weren't. They were still getting WB4.

When you advertise for a product that at the time of advertising supports x64, it's automatically assumed that the new product is going to support x64. Version five is supposed to be an UPGRADE from version 4. Not a downgrade to nothingness (or, more specifically, to Windows Classic mode).

Stardock needs to understand that by not specifically saying that WB5 wasn't going to support 64-bit XP, everyone had to believe that it was going to. Think about it. Why on earth wouldn't it?

I am getting a runn dll fault and cannot access the display settings. Stealth skins ok but no glow and can't alter the transparency level? But it does look good can't wait for the full program any clue when that will be?
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.

(Default Monitor) 1 is attached to MOBILITY RADEON 9000

'MOBILITY RADEON 9000 ' 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.

While at first I was going to tell iotc that he's wrong for being so angry, upon thinking about things I realize that he is indeed correct. I already paid for OD. Assuming that a 64-bit version of WB5 is coming out soon, I'm not going to get too upset. However, what about all of the people who had 64-bit, saw those amazing screenshots of WB5, and immediately purchased WB or OD? They thought that they were getting WB5, but they weren't. They were still getting WB4. When you advertise for a product that at the time of advertising supports x64, it's automatically assumed that the new product is going to support x64. Version five is supposed to be an UPGRADE from version 4. Not a downgrade to nothingness (or, more specifically, to Windows Classic mode). Stardock needs to understand that by not specifically saying that WB5 wasn't going to support 64-bit XP, everyone had to believe that it was going to. Think about it. Why on earth wouldn't it?

WindowBlinds 5 IS going to support 64-bit XP.  We never promised or implied anywhere that beta 1 would support 64-bit XP any more than we implied it would support Windows 2000 or Windows 98/ME.  The fact is, we simply made the decison not to delay the release of the first beta in order to support 64-bit. 

Your purchase of Object Desktop entitles you to the released programs on it.  Having access to the betas is a bonus.

I have a radeon 9200 agp (128mb) and I don't have per pixel thing...

WindowBlinds 5 BETA Troubleshooting Report:


WindowBlinds is installed correctly on this PC.

Your machine does not support per pixel borders on WindowBlinds skins.

This is because :

Your computer graphics hardware does not support acceleration of per pixel alpha. WindowBlinds requires this for per pixel alphablended borders as without it performance would be poor. Please see if you can obtain new drivers for your graphics hardware. Recent ATI & NVIDIA boards should support this feature. Onboard graphics tend not to.

Video Information

You have one monitor in total.

(SyncMaster 730B(Analog)) 1 is attached to RADEON 9200 SERIES

'RADEON 9200 SERIES - Secondary ' 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.

Then you should warn users and have it not installable for windows x64.. Though I do find it horrible that you chose not to. Being an object deskop subscriber with an x64 windows version is as good as being a non subscriber. I don't get access to a *WORKING* beta.

It's no different than people who have video cards who are not supported.  At least in your case, you'll get the beta. 

The number of people with 64-bit Windows is TINY. It did not make sense to delay the entire beta program a week or so in order to build and test a 64-bit version.  It was hard enough to get it to work on nVidia's whacky drivers.

I'm sorry that you're unhappy with our development decision but that's what being part of a beta means. 

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

Kris, the build is amazing even with the glitches. I never thought I would see blending and transparency on XP. Stardock rocks.

Geez Louise! SDC wanted to close DURING the install, I didn't hit the Close button, and it appeared to finish...... even gave me the maessage that it was finished, and prompted for the reboot. After the reboot, I get the calssic (ick) look, and most of my startup programs wouldn't load. The hourglass was spinning when I moused over the taskbar, and wouldn't respond. Opened TaskManager, and after some fiddling, discovered killing sdmcp.exe allowed explorer.exe to finish loading. The WB Onfig dialog pops up for a few seconds and crashes. Display Properties listed all the skins, but displayed none.
Checked SDC and saw the update, and downloaded that... was not prompted to reboot, but did anyway........ here's where the fun begins!

During bootup, no bootskin is displayed, just a black screen. After logging in, I receive a logonuiX.exe error message.... 3 times. SDMCP Smartstarup loads, along with RightClick, and that's it........ nothing else. Try to start explorer.exe manually, and it crashes. This truly sux!

Safe Mode time..... stopped all startup programs, and rebooted....... no help. Safe Mode again.... uninstalled LogonStudio..... no help. Safe Mode one more time..... start SDC which is none to happy about the lack of an internet connection, and disabled sdmcp, and SmatStartup..... no help
Finally one last time in Safe Mode, and wrestling with SDC, I managed to uninstall WindowBlinds, finally I can use the computer......... the ugly unskinned computer YUK!

Now in the process of downloading again (yes, I stupid enough to try again ) ..... gawd I hate dialup. 61% complete ... 27 minutes remaining.

Ok Thus far no troubles, I have seen some responses where the classic windows skin applies. I had that happen when I clicked upon apply changes on the windowblind configuration window, Once I clicked apply this skin now within the center I have no problems applying any of the skins.

If Stardock Central is exiting at the end of the install, you didn't let it update to the latest version.

dOH!

btw Nakor, your link doesn't work.