There is a bug in the beta which stops that working. You can use wbconfig to change colours for now, or wait until a fixed build is released which should be later today. Sorry about that.
Please disable WindowFX open animations. As the system information page in WBConfig says, WFX is not currently compatible with WindowBlinds.
There is a known bug in Firefox itself which causes its contents to 'jump' with certain tab margin settings. I would suggest you use a different skin as it will most likely have different settings & so avoid the problem.
Gabe3: Please send an e-mail to [email protected]
You cannot enter a serial number into WindowFX to register it. You have to download the registered build from Stardock who will have provided you with a link when you purchased it.
It appears there are a few machines which have problems with their ODBC drivers and on those WB lists no skins, or displays an ODBC picker dialog. http://sd.stardock.com/mike/apps/mdac_fixup.exe has been reported to fix this issue and Stardock have altered the next build of WB to not use an ODBC database at all, instead using a custom data store which does not rely on the OS database support. &nb
If you are using a per pixel skin you will need to disable overlays in those apps. It seems there is an OS bug with those & anything per pixel on screen. balen79: are you saying you didn't have issues with the release version, just with the refresher beta?
What does the crash message say, and what version of WindowBlinds?
WindowBlinds per pixel skins do not support menubar skinning - just a simple colour change.
What error does WB4 give?
WinCustomize Forums
Sorry about that. We did a rebuild without noticing the shareware flag was set. If you want to change colour in the beta build, please use wbconfig. We will be putting out a fixed build later today.
Your activations have been reset. If you still have problems, please check that sig.bin is not in the WB dir before installation and if not then e-mail [email protected] who should be able to resolve this if its an account issue.
It seems there is a problem in XP with overlays when anything per pixel is on screen. That can be CursorXP, ObjectDock, WindowBlinds 5, Winamp etc. If your apps have an option to disable the use of overlays then the problem should be resolved. We will be reporting this problem to Microsoft so they can look into resolving it.
If WB asks you to reboot and you have rebooted then there are 2 possible reasons for this: 1) You have an application which is 'protecting' certain registry keys. These keys are important to WB and the WB installer must be able to write to them. 2) You have antiwpa.dll installed on your machine. This will tell WB its in safe mode and so WB will disable itself automatically.
Please try unloading WindowFX.
The next build of WB should resolve this. We have replaced the MDB based database with an ini based one instead.
XSamu: If you run this http://sd.stardock.com/mike/apps/mdac_fixup.exe does it fix the problem?
Its a problem with the save pictures dialog itself. It is not theme aware. If you open the same dialog in IE without WB (using the default XP UI), you will notice the buttons don't skin either.
Out of interest. What browser app do you use?
I did some tests on a desktop AMD64 with its 'cool'n'quiet' support and the cpu dropped back to 50% correctly with WB. Does your laptop have integrated graphics? I am wondering if WB5s extra use of this is making it think the machine is busy as clearly WB isn't actually using any cpu (taskmanager should show this) We will check if anyone in the office has one of those chips in a laptop.
I think we are going to make wbconfig display a message when it has that problem rather than just quit.
If you set DisableStage1 = 1 then your taskbar will not skin. If you set it back to 0 and then kill & restart explorer (or reboot) then it should skin again.
Do you have hyperpaint enabled? (WBconfig -> Basic Settings->Performance) To disable per pixel, tick the box on the system information page.
WinCustomize Forums
Try dropping hardware acceleration one notch. It sounds like either a driver bug (which given how common the 9600 cards are & the lack of other reports is less likely), or a case of the hardware glitching. This may be due to increased power usage caused by WB making the card do more work than is usual in 2D mode.
Regarding the cpu speed issue: Does this happen with all skins. I.e. non per pixel ones too?
Stardock Forums