WinCustomize Forums
Its a firefox bug.
WinCustomize Forums
You do not need to disable DEP with WB 4.4 If you are having problems with 4.4 and AMD64 processors please contact [email protected].
The problem with WB & SP2 with AMD64 chips was fixed in 4.4. If you still have a problem with WB 4.4 on the machine then please uninstall WB, delete its directory (and wbsys.dll in the system32 dir) & then reinstall WB as the install obviously didn't overwrite some files correctly. CursorXP has a known issue which will cause it to crash when DEP is enabled on AMD64 chips running SP2.  Disabling DEP is a workaround for now but we are working on a solution to this.
It does not work with Athlon 64 processors when running SP2 and with DEP enabled. Stardock are working on resolving this.
The next time we release a build of WB onto OD it will have an option for when there is not a close button.
If its not working for you when you reboot I would add a shortcut to wbload.exe in your startup group. See if that helps.
WinCustomize Forums
Who confirmed that? If we are talking about transparency in the background part of a progress bar than thats not permitted.
Have you modified any of your system files in anyway? (in particular desk.cpl) It should appear in display properties the same way WB 4.3 etc did, but the code was changed to make things quicker.
sacrat : I have looked at your problems and have the following comments: 1) The russian font issue is most likely a side effect of the font the skin decided to use for its menus. If that font didn't support the Cyrillic chars then you would get a problem. This is NOT a WindowBlinds problem. You could do the same by setting that font for menus in classic mode. HOOGE OS_53 isn't exactly a standard font! 2) The BAT. Your progressbar
It seems IE is being too clever & doesn't want to open those files.  They do save as .wba files here though. We will look into why IE is acting oddly & hopefully find a workaround for it.
Yes the most recent SP2 build has resolved the problem with it and WBs toolbar icon support.
It sounds like there is an app running which has installed a buggy hook. I would look at what apps auto start via the startup menu or the registry RUN keys.
WB stops menu skinning after you have had the shareware version of WB installed for 30 days.
Only the XP version gets the new faster skin apply & 'morph' feature.
It will only 'morph' if you change skins from wbconfig and if you are not using a multiple monitor system (works on some, not others).  You also require a high end graphics card (ATI, Nvidia, Matrox) NightTrain2002: Earlier versions of WB did not have this feature.
WinCustomize Forums
It would be very useful if we can determine which BHO is causing the problem.  Then we can try and repro it and see why it causes a problem.
It sounds like your monitor is the problem. Large areas of black or white will alter the shape.  It will curve out for lots of white and in for lots of black.  I even once saw a monitor that went out of focus briefly when you maximized a window. A good monitor can switch from almost fully black to almost fully white without the edges of the screen moving at all (just like a TFT monitor)
Where did you hear that from?
The blinking shadow on the taskbar appears to be a DX issue. If you don't use IconX then it doesn't happen.
Do you have semi transparent window dragging enabled? Also do you have anything running like nview or hydravision?
Xave: You have to enable it from the WindowFX settings dialog.  See the tile windows page.
If a 'trial' version of WB that runs all of the WB skins is skinning the scrollbars in anything apart from IE/Explorer sidebars then its not a trial copy. An easy way to check is to bring up the about screen from the system tray icon. If it says shareware then its a trial copy, otherwise it isn't.
Thats the only issue we are aware of and its probably due to a minor bug somewhere in WB thats been exposed by minor changes to the OS. Its likely to be resolved before WB 4.3 is released.
WinCustomize Forums
Actually the problem is much simpler than that. The shareware version of WB stops skinning menus after 30 days. The idea is you register the software if you like it and using both 3.5 and 4.0 for more than 30 days would suggest you do like it!
4.19b on XP is the same as 4.10 apart from an updated WBConfig UI. 4.19a was newer, but there was a bug which corrupted some internal WB structures and caused it to act oddly with some skins. It should have had no impact on any other app or the contents of your HD. Missing skins usually means the new WB was installed in a different directory and so it will only show the skins which come with WB (as they are the only ones in the WB directory) There should be a 4.1
JoeUser Forums