WindowBlinds 5 Trouble Already =(
Why Wont it Work?!
Tuesday, October 4, 2005 by xxZeroVirusxx | Discussion: WindowBlinds
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?
-------------------
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?
 |
|
Page 7 of 9 | |
|
|---|
AbrahamLincoln
Reply #122 Wednesday, October 5, 2005 3:06 AM
Reply #122 Wednesday, October 5, 2005 3:06 AM
Installed now Beta2 but the rundll32.exe is still crashing.
Is this something i have to worry about,
or can i continue to use windows (nearly) as normal until this
is fixed ?
Or in other words: Should i deinstall it until there's a version
which does not crash the rundll32.exe ?
Thanks
Is this something i have to worry about,
or can i continue to use windows (nearly) as normal until this
is fixed ?
Or in other words: Should i deinstall it until there's a version
which does not crash the rundll32.exe ?
Thanks
starkers
Reply #123 Wednesday, October 5, 2005 3:27 AM
Reply #123 Wednesday, October 5, 2005 3:27 AM
I installed the WB5 update over the previous version and have no display problems. WB5 applies all previously installed blinds correctly, and it seems there are no issues with the packaged blinds, either. However, newly downloaded blinds show as being installed correctly but cannot be applied as per usual when clicking the notification balloon, nor do they show in the list of available blinds to apply from there, although present in the WB folder.
Given the comment in 56#, about firstly uninstalling 4.6, perhaps an uninstall and clean install will resolve this issue....fingers crossed
If not, I'm sure Stardock will find a fix fairly soon.
Given the comment in 56#, about firstly uninstalling 4.6, perhaps an uninstall and clean install will resolve this issue....fingers crossed
If not, I'm sure Stardock will find a fix fairly soon.
starkers
Reply #124 Wednesday, October 5, 2005 3:29 AM
Reply #124 Wednesday, October 5, 2005 3:29 AM
I installed the WB5 update over the previous version and have no display problems. WB5 applies all previously installed blinds correctly, and it seems there are no issues with the packaged blinds, either. However, newly downloaded blinds show as being installed correctly but cannot be applied as per usual when clicking the notification balloon, nor do they show in the list of available blinds to apply from there, although present in the WB folder.
Given the comment in 56#, about firstly uninstalling 4.6, perhaps an uninstall and clean install will resolve this issue....fingers crossed If not, I'm sure Stardock will find a fix fairly soon.
Given the comment in 56#, about firstly uninstalling 4.6, perhaps an uninstall and clean install will resolve this issue....fingers crossed
If not, I'm sure Stardock will find a fix fairly soon.
rsplitter
Reply #125 Wednesday, October 5, 2005 3:34 AM
Reply #125 Wednesday, October 5, 2005 3:34 AM
I noticed in the readme.txt, it said this
I looked at the wblind.dll and it was version 500.000. Yes, I had uninstalled WB4 fully, and deleted the WindowBlinds directory.. And a reboot didn't do anything, I've done so about five times to no success.
| Please make sure your dll is updated after updating, a reboot should do it. Again, you must reboot after the initial beta install to enable skinning. 10/04/05 23:20 500,818 wblind.dll |
I looked at the wblind.dll and it was version 500.000. Yes, I had uninstalled WB4 fully, and deleted the WindowBlinds directory.. And a reboot didn't do anything, I've done so about five times to no success.
CAClark
Reply #126 Wednesday, October 5, 2005 5:50 AM
Reply #126 Wednesday, October 5, 2005 5:50 AM
My dll is the correct size as it should be. And I rebooted, and tried uninstalling 4.5, rebooting, installing 5, and rebooting again, all without luck. I have tried this both at home on my Athlon X24800+ with 256mb Radeon X850XT, and my P4 2.6 with gforce4 420ti. Both the same.
Report:
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 GeForce4 Ti 4600
'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.
Report:
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 GeForce4 Ti 4600
'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.
Shadows Edge
Reply #127 Wednesday, October 5, 2005 6:11 AM
Reply #127 Wednesday, October 5, 2005 6:11 AM
version 4.90a[b].002
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 ATI MOBILITY RADEON 9000 IGP
'ATI MOBILITY RADEON 9000 IGP' 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.
FYI: This version has stopped all WB skins and same as others returned to basic windows.
Process followed: First uninstall WB4.6 then reboot, then install WB4.9 then reboot. Old skins listed but apparently not available to apply. Those that are available to apply, simply don't.
Everything else seems ok.
Heading back to 4.6 for a while.
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 ATI MOBILITY RADEON 9000 IGP
'ATI MOBILITY RADEON 9000 IGP' 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.
FYI: This version has stopped all WB skins and same as others returned to basic windows.
Process followed: First uninstall WB4.6 then reboot, then install WB4.9 then reboot. Old skins listed but apparently not available to apply. Those that are available to apply, simply don't.
Everything else seems ok.
Heading back to 4.6 for a while.
starkers
Reply #128 Wednesday, October 5, 2005 7:03 AM
Reply #128 Wednesday, October 5, 2005 7:03 AM
UPDATE...a clean install of WB5 did not resolve the issue of newly downloaded blinds not loading correcty. I was still unable to apply from the notification popup and they did not appear in the installed list. I have since reverted back to WB4.6 
and all is as it was. Boo hoo, everything else worked fine and the new features are fantastic, so hopefully there's a fix real soon.
and all is as it was. Boo hoo, everything else worked fine and the new features are fantastic, so hopefully there's a fix real soon.
Jonep
Reply #129 Wednesday, October 5, 2005 7:31 AM
Reply #129 Wednesday, October 5, 2005 7:31 AM
I have an ati Radeon 9200 pro 256mb, Athlon 2400+ ,768mb ram ,5.9 catalyst drivers, No transparancy in windows borders and no logon studio(anymore).I'm sure my card supports the per pixel borders. My machine still skins using Noire and some others but some like KOLs vista xp don't apply properly. what am I doing wrong?. Help Please!
Jeroen Verhoeven
Reply #130 Wednesday, October 5, 2005 7:40 AM
Reply #130 Wednesday, October 5, 2005 7:40 AM
Installed ok and looks great on my system: PM 760 with Ati X700 and 1680 x 1050 LCD (Asus W2 notebook)
Two things: I cannot access my display configuration (not by the rightclick desktop menu and not by config panel) and the taskbar has a little problem with transparany. If I refresh the bar its okay but after a wallpaper change I have to do that again.
Using the Aura skin, its beautiful!
Two things: I cannot access my display configuration (not by the rightclick desktop menu and not by config panel) and the taskbar has a little problem with transparany. If I refresh the bar its okay but after a wallpaper change I have to do that again.
Using the Aura skin, its beautiful!
DArnaez
Reply #131 Wednesday, October 5, 2005 8:17 AM
Reply #131 Wednesday, October 5, 2005 8:17 AM
I have XP 64 too and I read that a new version beta of WindowBlinds is coming for this OS. THe current beta is only for Windows XP 32 bit.
00Chris00
Reply #132 Wednesday, October 5, 2005 9:34 AM
Reply #132 Wednesday, October 5, 2005 9:34 AM
For some reason the forum software keeps on putting my posts into the wrong forum, so I'll post what I'm trying to tell here:
I had the same problem so many folks were reporting here; WB5 installed but all I could get was the 'classic' skin in XP. I was about to uninstall it but fortunately just before I did I noticed that our network firewall had logged a failed connection to sdcentral.stardock.com/activate/activate.aspx at about the time I installed the beta.
So I fired up Stardock Central and saw that WB5 wasn't activated. I asked it to activate, then set a theme, and all was well.
I have two comments on this. Firstly I clearly remember watching SDC finish off the beta install and say 'activating'; it did not display any error that I could see, even though I know now that the activation failed.
Secondly, if the app isn't activated, at least it could refuse to run or complain when I try to set a theme, rather than just not working and leaving me to work out why! I even checked the event log files and there was nothing to lead me to believe that the app was deliberately not working as appears to be the case ...
So I thought I'd just mention this to others in case they also have an activation problem.
PS I just looked at wb5.log in sdcentral\installed dir and the last four lines are:
Execute: C:\Program Files\Stardock\Object Desktop\WindowBlinds\wise_post.exe 1
Activation: 0 Failed (0)
Update: C:\Program Files\Stardock\SDCentral\installed\wb5.xml 1
Result: Update successful
As can be seen it says 'update successful' even though it knows the activation failed.
I had the same problem so many folks were reporting here; WB5 installed but all I could get was the 'classic' skin in XP. I was about to uninstall it but fortunately just before I did I noticed that our network firewall had logged a failed connection to sdcentral.stardock.com/activate/activate.aspx at about the time I installed the beta.
So I fired up Stardock Central and saw that WB5 wasn't activated. I asked it to activate, then set a theme, and all was well.
I have two comments on this. Firstly I clearly remember watching SDC finish off the beta install and say 'activating'; it did not display any error that I could see, even though I know now that the activation failed.
Secondly, if the app isn't activated, at least it could refuse to run or complain when I try to set a theme, rather than just not working and leaving me to work out why! I even checked the event log files and there was nothing to lead me to believe that the app was deliberately not working as appears to be the case ...
So I thought I'd just mention this to others in case they also have an activation problem.
PS I just looked at wb5.log in sdcentral\installed dir and the last four lines are:
Execute: C:\Program Files\Stardock\Object Desktop\WindowBlinds\wise_post.exe 1
Activation: 0 Failed (0)
Update: C:\Program Files\Stardock\SDCentral\installed\wb5.xml 1
Result: Update successful
As can be seen it says 'update successful' even though it knows the activation failed.
dvduvil
Reply #133 Wednesday, October 5, 2005 12:29 PM
Reply #133 Wednesday, October 5, 2005 12:29 PM
I've got same RUNDLL32.EXE issue than AbrahamLincoln (post #36) and Peppi (#121).
Issues are :
- WindowBlinds seems to work (can change VS)
- no acces to Display Properties
- no acces to System Properties
the Windows Event Viewer reports this when I try to display the above properties :
"Application défaillante rundll32.exe, version 5.1.2600.2180, module défaillant unknown, version 0.0.0.0, adresse de défaillance 0x5ad7af15."
As you can see, I'm french, and I'm using a French release of Windows XP.
I think the problem of Rundll32 could come from non-english or non-US versions of XP (Rundll32 could be different). It's just an idea. AbrahamLincoln & Peppi, what is your regional version of XP ?
For information, I use Windows XP MCE 2005 SP2 (french) with ATI X800 XL card.
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.
(Écran Plug-and-Play) 1 is attached to RADEON X800 Series
'RADEON X800 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.
Issues are :
- WindowBlinds seems to work (can change VS)
- no acces to Display Properties
- no acces to System Properties
the Windows Event Viewer reports this when I try to display the above properties :
"Application défaillante rundll32.exe, version 5.1.2600.2180, module défaillant unknown, version 0.0.0.0, adresse de défaillance 0x5ad7af15."
As you can see, I'm french, and I'm using a French release of Windows XP.
I think the problem of Rundll32 could come from non-english or non-US versions of XP (Rundll32 could be different). It's just an idea. AbrahamLincoln & Peppi, what is your regional version of XP ?
For information, I use Windows XP MCE 2005 SP2 (french) with ATI X800 XL card.
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.
(Écran Plug-and-Play) 1 is attached to RADEON X800 Series
'RADEON X800 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.
Drakknar
Reply #134 Wednesday, October 5, 2005 1:50 PM
Reply #134 Wednesday, October 5, 2005 1:50 PM
After some hours of testing, I found other bugs (my hardware details and troubleshooting report can be found in my previous post in page 1)
First, after a complete uninstall and reinstall of WB5, I have tested again the software with WindowFX activated, but it still don't work. When I apply any effect in WFX, every window is visualized in "Classic" mode.
As post #36, #121, #141, I experience some kind of error when I first run WindowBlinds (but I can't be more precise because I can't find any sort of warning or report in my Event log). However WindowBlinds loads fine, but I can't access any of the control panel applets.
I also have experienced that WB5 sometimes hangs MSN Messenger 7.5 (as a workaround I excluded the program in the application settings).
Also, if I change the lenght of the quick launch bar, it's not remembered after a reboot.
After some hours using my pc and opening/closing several application, I noticed that WB loads in a wrong way the background of the right click menus and toolbar menus (i.e. before the background is white with alpha transparency and after it becomes black/gray with alpha transparency).
I found also that sometimes toolbar icons don't get skinned, but I can't reproduce exactly the cause of the problem.
First, after a complete uninstall and reinstall of WB5, I have tested again the software with WindowFX activated, but it still don't work. When I apply any effect in WFX, every window is visualized in "Classic" mode.
As post #36, #121, #141, I experience some kind of error when I first run WindowBlinds (but I can't be more precise because I can't find any sort of warning or report in my Event log). However WindowBlinds loads fine, but I can't access any of the control panel applets.
I also have experienced that WB5 sometimes hangs MSN Messenger 7.5 (as a workaround I excluded the program in the application settings).
Also, if I change the lenght of the quick launch bar, it's not remembered after a reboot.
After some hours using my pc and opening/closing several application, I noticed that WB loads in a wrong way the background of the right click menus and toolbar menus (i.e. before the background is white with alpha transparency and after it becomes black/gray with alpha transparency).
I found also that sometimes toolbar icons don't get skinned, but I can't reproduce exactly the cause of the problem.
dvduvil
Reply #135 Wednesday, October 5, 2005 2:33 PM
Reply #135 Wednesday, October 5, 2005 2:33 PM
Drakknar, my problems are similar in certain ways. When I right-click for display properties, noting happens. But I have a report in Event Log under "Application" sub-categories, "Error" type with a white crossed red circle (perhaps I don't explain it perfectly).
What's your Windows language ? English, US ? Still don't know if it could care !
What's your Windows language ? English, US ? Still don't know if it could care !
Drakknar
Reply #136 Wednesday, October 5, 2005 3:19 PM
Reply #136 Wednesday, October 5, 2005 3:19 PM
Dear dvduvil, my operating system language is Italian, but I don't think it can be the source of our problems.
I suppose it's an error because I hear the typical error sound (twice) while WB5 is skinning for the first time my opened windows, but till now I was unable to see any error window or report (the last reports in my application logs are related to a MSInstaller which failed to complete (caused by Styler Toolbar, not WindowBlinds))
I suppose it's a rundll problem because not only display properties, but all my control panel applets don't work, and because I experienced some Windows Explorer and other background application instability. IMO it's just some kind of conflict and we can't do nothing except waiting for Stardock to address this problem. However if I find any kind of workaround I'll post it immediately here.
I suppose it's an error because I hear the typical error sound (twice) while WB5 is skinning for the first time my opened windows, but till now I was unable to see any error window or report (the last reports in my application logs are related to a MSInstaller which failed to complete (caused by Styler Toolbar, not WindowBlinds))
I suppose it's a rundll problem because not only display properties, but all my control panel applets don't work, and because I experienced some Windows Explorer and other background application instability. IMO it's just some kind of conflict and we can't do nothing except waiting for Stardock to address this problem. However if I find any kind of workaround I'll post it immediately here.
Neil Banfield
Reply #137 Wednesday, October 5, 2005 4:09 PM
Reply #137 Wednesday, October 5, 2005 4:09 PM
Regarding WindowFX + WB5, as I have said many times today, there will be a beta of WFX 2.5 this month that is compatible with WB 5 because WFX 2.11/2.19 is not compatible with it.
There will a new build tonight which I hope will help with many of the reported issues. Until then if you have problems with it not skinning then please wait for the new build.
DigitalDanes
Reply #138 Wednesday, October 5, 2005 4:28 PM
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 GeForce4 MX 420
'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 #138 Wednesday, October 5, 2005 4:28 PM
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 GeForce4 MX 420
'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.
Brokensquare
Reply #139 Wednesday, October 5, 2005 4:47 PM
Reply #139 Wednesday, October 5, 2005 4:47 PM
iotc - your quote follows-"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. "
On WC home page - "WindowBlinds 5 BETA currently requires Windows XP (32-bit edition). A 64-bit edition will be available with beta 2" kinda sys it all...
On WC home page - "WindowBlinds 5 BETA currently requires Windows XP (32-bit edition). A 64-bit edition will be available with beta 2" kinda sys it all...
Brokensquare
Reply #140 Wednesday, October 5, 2005 4:48 PM
Reply #140 Wednesday, October 5, 2005 4:48 PM
Even on my 32 bit system, it doesn't work right yet, so I wait for next release-like you!
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
|
|
Page 7 of 9 | |
|
|---|
Reply #121 Wednesday, October 5, 2005 3:00 AM
I'm a software developer working on a visualization app that uses OpenGL. It seems that as soon as the OpenGL context is initialized, all per-pixel alpha blending breaks. The menus are almost (but only almost) opaque. When I quit the app and re-apply the skin, everything is back to normal. Any suggestions?
Machine Specs: Pentium4 3.2GHZ, 2GB RAM, WinXP Pro SP2, GeForce 6800
---
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 und Play-Monitor) 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.
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.