New skins from Tennessee
Published on December 19, 2004 By jhempelmann In WindowBlinds
When applying a WB skin my taskbar wont skin. The rest of the skin is fine. Any ideas??
Comments
on Dec 19, 2004
Hmm...what version of WB do you have, and what OS version?
on Dec 19, 2004
Is it just one particual skin, or all of them?
on Dec 19, 2004
If you have an AMD64 processor, make sure you have Windowblinds 4.4 or later installed.

Posted via WinCustomize Browser/Stardock Central
on Dec 21, 2004
I see the same problem. Applies to all skins. I have WB 4.4 running on an AMD64.
on Dec 21, 2004
from another thread:

Where did you get WB from?

We believe there is an installer of 4.4 around which has 4.3 files in it rather than some of the updated 4.4 files, but we are not sure where it came from.

Are you using

1) WB shareware

2) WB from ObjectDesktop (OD customer)

3) WB standalone registered enhanced (WB customer)

or 4) Other...

A couple of sites certainly 'released' a WB 4.4 shareware before we did (in fact before we had even compiled it!) so its possible thats whats causing this confusion.

If you are a standalone WB enhanced customer, request the link again & then reinstall. As the very first 4.4 enhanced build (out for 1 day or so) had a bad file included. This was fixed though.
on Dec 22, 2004
I had the same problem with WindowsMax2... The Blue color worked great for everything, but the other 3 colors didn't skin the TaskBar... I have the current version of WB, and I didn't have the 'old' version of Max2... That has been the only problem I've had... except the IconPackager not 'updating' along with everything else when I bought in.
on Dec 22, 2004
hello. i have the same problem that the taskbar wont skin. i have a amd 64 processor but it was working fine until i installed windows sp2. since then it will not skin, neither will it revert back to original windows xp style. all it will show is windows classic style.

picture with "soulluna" in use


so it is unlikly it is windows blinds.

error while trying to apply windows theme theme using control panel>display:
---------------------------
Applying Visual Styles Error
---------------------------
The visual styles could not be applied. Access is denied.

//edit: fixed the problem with a 6th reinstall of windowblinds. ^^
on Dec 22, 2004
I know how to post in already made threads, but how do you create a new thread, i would of made a new thread for this question, but i dont know how

sorry about the dumbass question, ive figured it out now
on Dec 22, 2004
the same exact thing has happened to me...do I have to buy a different version or...?
I have version 4.4 installed, but it still happened
Just keep re-installing it?
on Dec 27, 2004
Open 4.4, look at left column, Settings, click on User Over rides, the next window will have XP over rides located at right of this screen...at this point, check box and pull down menu to select skin choice for taskbar....do the same at the next line for the shell style...this window has further over ride info ...check 'em out...close back to first 4.4 window and click apply changes from column on lower left side...voila
on Dec 28, 2004
I had this happen yesterday. ---sheepish grin--- there was something leaning up against my keyboard when I booted up, didn't notice it. It was pushing down the control key. Oddly, windows were still skinned, but the taskbar and startmenu weren't. Rebooted-resolved.

Posted via WinCustomize Browser/Stardock Central
on Jan 01, 2005
I had this problem because i have an athlon64 socket 939 which has built in Data Execution Protection (DEP), a security measure which works with XP SP2. To get windowblinds to skin your taskbar you must disable it. To do this go to control panel> system> advanced> startup and recovery settings> edit. A text document should open in notepad. Save a backup copy and then change the text after /noexecute= to alwaysoff. Then save this copy as boot in c:.

See here for more on DEP http://support.microsoft.com/default.aspx?scid=kb;en-us;875352
on Jan 01, 2005
This DEP problem was supposed to be fixed with version 4.4 of Windowblinds. But it is definitively worth while to try and disable DEP for a while and see wether this was the cause of it.

Posted via WinCustomize Browser/Stardock Central