Windows 7: Win Explorer Background Change

More problems ...

I managed to use Restorator 2007 to extract the NORMAL.res to a file and then edited it with XVI32, changing the harsh white left and right panes to a nice subdued gray (assuming the offsets where I found the FCFCFC are correct):



At least with the 30-day trial of Restorator 2007, I can't replace the aero.msstyles. I used the Assign option to (hopefully) import the edited normal.res. What's weird is the offsets are not the same when viewed with Restoator as with XVI32 - they are close, but not exactly the same. When I try to save it with Restorator, it first tells me that I am using 30-day version and that it will add top-level menus and other things. <sigh> If I tell it "go ahead" it fails, saying that aero.msstyles is in use, and saves the modded file as aero1.msstyles.


Assuming that Windows 7 is using the aero file, how can I:
1.] Just edit the darn thing with an editor that won't nag me to buy it
2.] Get Windows to accept the edit?

Thanks in advance to nice hand-holding people;

$teve

you extract normal.res in restorator, open normal.res with a hex editor. find colorcode fc fc fc and replace with own, assing the edited normal res to your aero.msstyles. then in restorator you have a folder called images to the left. thats where all the imgages that will edit are placed.

i would recommend vista style builder, instead of all the hazzle with restorator and hexediting. sence its a way bit harder.

i would also recommend that you download a theme that is very like what you want, and then change it the way you want it. a lot of work getting it all to work properly.

gl hf

\\Targa

I did this already (see previous post)

I also did this already.


This confuses me. I don't think that normal.res is an image, even though I have no idea what normal.res is.

I need to know how to get Windows 7 to accept my modified aero1.msstyles and use it. It won't let me replace it with my modded version - complains that I don't have rights, even though I have taken ownership.

Regarding searching for theme's that are close to what I want, I appreciate the suggestion, but that will not work. I just want the ability to change, as often as I want - on a whim - the background colors in Explorer windows. There will never be existing themes floating around that have my eclectic color preferences.

I will research "Vista" style builder ... wondering why there is not a Windows 7 style builder.

I'm really starting to Hate Aero. (Using a classic theme right now that lets me pick my own colors ....). If I were not stubborn I would have given up by now. Grrr.

$teve

It's the same. Now it's known as Windows Style Builder and is compatible with Windows 7

Thanks Greg.

But - please pretty please - help me just get the edited aero.msstyles to work. I'm so close I can taste it. I've made the changes to FCFCFC and just need to make Windows 7 use it.

Can't get Windows 7 to let me replace the original aero.msstyles with my modded verision. WindowsStar is trying to help me in this thread:
Take / Assign Ownership of file / folder


Thanks!

$teve

You must select classic or basic theme one with square gray start (don't remember right now I'm on xp64 right now).
then try to rename the original file aero.msstyles and then paste the new one with original name.

right click your aero.msstyles that you are replacing, select properties.then security. under group or username select edit. choose yourself and give full access. done

if you are using an aero theme, select windows classic and restart explorer, before you try to replace the auro.msstyles

@targa85 and six9sis - have already done all of that, and more. I'm using Classic non-aero theme during all of this. I have ownership. Even with all apps closed and explorer processes killed, I can't touch aero.msstyles. For details and screen shots on what I'm trying and what is not working, please check this thread:

Take / Assign Ownership of file / folder

Here is my last post from that thread:

@ztrucker - will try safe mode next.
@WindowsStar - same problem. FYI I'm using the Classic non-Aero theme while I try all of this. I also run Ivo's Classic Shell, if that helps. The problem smells as if something has a lock on the file. Is there a way to see file lock activity?

I hit the printscreen key after the last attempt. Here's the screen shot:


One thing to keep in mind - the only reason I'm trying to mess with aero.msstyles is to be able to change background colors in Aero Themed Explorer windows. I have no desire per-se to take ownership and mess with the OS. Just trying to make backgrounds have colors of my choice. If there is an easier way I would gladly use it ...

Thanks again,

$teve

Ok, I've solved the "access denied" problem. (But my customized aero.msstyles does not give me grey Explorer backgrounds, instead, it just turns off the "glass" effect in all Aero themes! Grrrr....)

As are most solved problems, the "access denied" seems trivial in retrospect.

As I sat here fuming, I calmed down and reminded myself that although it has been many years since I passed the tests I am a W2K MCSE. I called up some of the mantra's that got me through the tests, way back in July 2001.

The problem of course, was permissions. Ownership per-se does not grant permissions. TrustedInstaller, the original owner of that and most 'system' files, has Full Control. Administrators don't. After granting Administrators Full Control, I could do what I wanted with the file.





Ok, so now back to the original problem - why did changing the FCFCFC 's at those offsets provided earlier in this thread not work? Why no "glass" effect now?

$teve

Yes, even after taking ownership which in my opinion is joke, one still needs to allow admin full control. I've even found this to be buggy and having to go one step further and temporarily assign full control at the user level. But hey, that's me and my setup. What others can do with ease, I've always had to find an alternate way.

About the no glass thingy, it's my understanding that the uxtheme.dll file still has to be patched and here again this may not be the case but just me and my unfortunate bad luck. I had to patch before it worked.