The problem is WB only knows what skin the current account is using, not what other accounts are using. Windows security prevents WB from finding out.
Neil Banfield
BoddhiC: The current version of the beta will not run on Windows Vista.
Just with 64 bit Windows. We will be adding support for 64 bit Windows later in the beta. A 64 bit processor running 32 bit Windows is compatible with the beta.
The 9600 is a much faster card than the GeForce 2, so yes it should run much better than on the Geforce 2.
Andy02369: A lot of the more advanced FPS games released in the past year would take advantage of pixel shaders which your card does not support. They may run in a less graphically advanced mode though depending on the game. I have a feeling DOOM3 for example would just not run at all as its OpenGL and the early ATI OpenGL drivers were not good. If you are interested in running WB5 per pixel frames, I would be on the lookout for a dirt cheap 9500 or higher card. They
We believe this is a bug in your video card drivers. ATI card?
laurentfr: Please install the latest beta. You are using an older beta.
The reason the controls are now part of the preview is due to a limited amount of space. Moving them into the preview gives us a much larger preview area.
Its by design in the arrow skin as thats a choice the author made.
Regarding YZShadow, I am afraid this may well be a problem with that app and not WindowBlinds 5. We will look into this to see if there is anything we can do about this, but I suspect the app is disabling the transparency on the menus. On dual head cards, any modern ATI (9500 or better) or nvidia (6 series ideally) should work fine with per pixel borders in dual head mode.
Doctor Who: If you are talking about WindowBlinds 5 beta, then it is NOT working on Windows XP 64 bit. It is lacking several key 64 bit dlls and without them WB 5 simply will not function.
Without the activation WB 5 beta will be unable to run. I believe for machines without internet access, there is a procedure where you have to e-mail a file to stardock support and they e-mail back an activation file.
The current theme manager is not compatible with WindowBlinds 5. There were changes to how a skin has to be applied and theme manager is not aware of these changes.
ls_dragons: The current WindowBlinds 5 betas do not work on 64 bit windows. This is noted in the readme. We will be adding support for 64 bit Windows later in the beta.
With all skins?
Which OS is this on?
We have now resolved this internally
Your tab issue appears to be a bug in the skin itself. The skin failed to define sizing margins on the tabs.border section and this is why this problem happens. Find the [tabs.border] section in the GT3 UIS files and change it to [Tabs.Border] Image=GT3\GT3_tabs_border_75.bmp LeftWidth =3 RightWidth = 3 TopHeight =3 BottomHeight=3
Double click on wbload on the 2nd account. This should run & do nothing. Does it now work?
The adobe menu issue should be fixed in the latest build on OD
Please make sure you have the latest WB5 beta installed.
You are missing 2 key WB files. WindowBlinds is not going to run without them. Please try reinstalling WB. Your lack of perpixel alpha is normal for the G450 though. They don't support it and never will do.
As with Windows Vista, these apps are not compatible with semi transparent borders.
There seems to be a misunderstanding here. TweakXP Pro, TrueLaunchBar or any other app which claims to give you a semi transparent taskbar just gives you one constant semi transparent value which is applied to the taskbar. We have this kind of feature in WindowFX for example. This is live transparency but the entire window gets the same level of transparency. The feature in WindowBlinds 5 allows the skin author to decide on the alpha on a per pixel basis. For
Print screen would take a screenshot btw.