If you purchased WB 4.2 standalone then you will be entitled to a free upgrade to 4.6. Simply visit https://www.stardock.com/support.asp enter the e-mail address you used when ordering and it will e-mail new serials & links to that address for you. Nobody here will e-mail the installers as they should only ever be downloaded by the customer direct from Stardock.
Neil Banfield
Firstly please do not pirate WindowBlinds The DSN (not DNS) message indicates your database support on your machine is damaged in some way. For later builds of WB, we have changed from an access database to an ini based database which avoids using the OS database support & therefore avoids this error message.
I believe there are more WindowBlinds skins than msstyles actually (there are over 3600 on this site alone) WindowBlinds has never supported msstyles directly, but you can import msstyles into WindowBlinds format using SkinStudio. Because of this and because WB skins cannot be converted into msstyle format, WindowBlinds actually allows you to use more skins than any other product.
I would install the Cat 5.12s and see if that helps.
Please upgrade to WB 4.5 or later. It sounds like you have SP2 on your PC with a machine with supports DEP which is preventing WB from skinning explorer. We resolved this in later versions.
Did you tick the box to ignore this app in the per app dialog? As an alternative way, right click the exe in explorer and on the compatibility tab tick disable visual themes. The colour scheme will still be applied but thats normal as colours are global.
Thats not a menubar. Its a toolbar.
Per pixel skins do not support menubar skinning currently. This is not a bug. Non per pixel skins do & the fix was for those.
Thats because there are no files on the clipboard so explorer doesn't request the data stored on the clipboard. The logic in explorer is basically 1) Check clipboard type 2) If type = file data then obtain clipboard information. Only if an application actually queries what the clipboard data is (not just the type), does Multiplicity have to transfer the information over to the secondary machine.
Please install WB 4.6. WB 4.2 with Service Pack 2 on recent AMD (and now some Intel) chips will not skin explorer correctly.
The lead developers of IP & I discussed a possible fix for your bug report on Wednesday. No promises though.
If you have an OD account then you can download the beta release which should fix all Select Data Source error messages as it switches to an INI based database instead of a MDB one. I would guess this update will be released to customers as a release build either later this week or early next.
Sorry, I thought when you said ' what a waiste of time and money, now i know why it was only $20' you had purchased a copy. Could you still please contact me with a list of the apps running on your PC and the information from the WB troubleshooting page as we can try to track down this problem. Thanks
There are 4 skins included with shareware which have per pixel frames. 5imple Alpha, Aura, DogMax 4 & Cyclops. No downloaded skins support it in the shareware version, just the included skins.
I am guessing it is because explorer.exe is running.
I should point out that the firefox menus are not skinned by WB, so its not WB impacting the cpu usage there. In Opera it seems there was a problem with how WB repainted menus when you moved up & down them. This has been tweaked for the next beta build which should be downloadable via SDC later today.
If an application queries what (not just the type) is in the clipboard, Multiplicity is required to copy it onto the machine before responding. Why explorer is so obsessed with knowing the exact filenames of whats in the clipboard when you right click is something I do not know. I am guessing the nero window is an embedded explorer window. It should be pointed out that Multiplicity is not looking for right clicks or anything like that, it is the applications requesting the
This has been reproduced & resolved for the next build
Gabe3: Please send an e-mail to [email protected] from the e-mail address you registered WB with.
If WB works after the first reboot and then stops working after the next reboot then something is removing the WindowBlinds registry entries after WB has started. If the keys are deleted then clearly WB is unable to start & no amount of patches from us is going to resolve this as its not WB deleting the keys. It seems most likely the problem is a service doing this.
Per pixel skins do not support sound effects currently.
Please e-mail [email protected]
A runas would not have worked as Wbconfig would have been modifying your registry settings & probably changed the skin on your desktop if you were logged in!
The problem with ACDSee 3.0 has been tracked down to a 3rd party plugin included in the antares skin. We will be preventing future WB builds from loading this dll as it appears to have no purpose anyway!
When you purchase WindowBlinds you should have got a link sent to your e-mail address for the WB enhanced version installer. It is not possible to convert the shareware version of WB into the enhanced registered version with a serial number.