Do not delete skins manually from explorer. The delete option in wbconfig should be used.
Neil Banfield
WindowBlinds 5 does not support Windows 2000. It will not work on that OS
poptarget: Which WindowBlinds version?
Please ensure you are running 4.90g from SDC. If you are still having problems, please contact [email protected] for assistance.
It appears to be a driver bug with the 9200 cards. Your monitor is fine.
Animation for per pixel borders will be coming in the next beta of WB5
xXDimiXx: Please upgrade to the 4.90g build. If you are still having problems, contact [email protected] with your information and they will be able to assist you.
You have applied an icon theme which is why the icons remain even when you unload WindowBlinds. To change it back, open IconPackager and reset the icons from there.
A 7500 is not sufficient for WB5 per pixel titlebars.
It sounds like the screensaver has left the desktop partially corrupt. OpenGL apps in particular are not aware of per pixel frames, but thats not a problem with WB itself.
WB5 uses an access database for skin info. WB4 used a basic text file for display properties which was less flexible, slower and less reliable and nothing at all for wbconfig (which had to search the WB dir each time WBConfig was started) Stripping down a system comes with its own risks as there is a reason those things are included by default!
We will be looking into this for a future build.
The name is a name decided by the skin author of the skin. Many skin authors leave it as the default which is why the names are wrong. Finding out which skin they are from is not currently possible without lots of trying.
The latest skin studio should handle the applying of skins just fine with WB5. Your other issues are limitations of the per pixel windows, but given that WB4 doesn't support per pixel windows, rolling back gains you nothing. WB5 continues to support the non per pixel skins in the same way as WB4 does. Corky_0: What sort of issues were you having with WB5?
Does the same thing happen if you change from the blue XP look to the silver XP look?
Your problem is having 2 different windows installations sharing the same directories for OD. This is not something you can do as per installation information is stored in the OD directories. If you e-mail [email protected] or [email protected] , they should be able to reset your activation counts, but you will need to move OD on one of the OS installs to a different directory.
As it says in the readme, the current betas of WB5 do not run on XP 64 bit. We will be adding support for XP 64 bit later in the beta. For now you should continue to use WB 4.6 on 64 bit XP.
If you have problems then e-mailing [email protected] is a good idea. He will be able to see what went wrong & hopefully resolve it.
There is no way to deactivate instances of MP, you will need support to reset it for you.
It refreshes correctly as far as we know.
Which version of WB?
WB5 does not use this. It is used by DesktopX and ObjectBar for its system tray icon support.
This is not possible. The transparency alters how the OS sends its mouse events.
Thats a bug in Windows XP which can occur after a screen resolution change. If you reboot all will be fine again.
Have you tried ticking the 2nd box on the troubleshooting page?