New
#11
You're right, the Windows Classic Theme, as well as the other Basic and High Contrast Themes, don't use aero.msstyles. In fact, they don't use a .msstyles file at all, which I figured out by opening classic.theme in Notepad. Since Vista Style Builder doesn't support editing .theme files and since I have no idea where classic.theme pulls it's values from, I can't help you there, unfortunately.
I've heard that before yet I haven't had any experience with it as my only laptop is crisp at any resolution. After installing Windows 7 on my desktop, however, I did set my desktop LCD to 1024x768 because I was having trouble reading the text at the monitor's native resolution of 1280x1024. After switching the resolution, everything was incredibly blurry, but that was only at a refresh rate of 60 Hz. For some reason, setting the monitor to 75 Hz (which is my only other option) cleared everything right up. Strangely, I did not have this issue in Windows XP. If you haven't already, I'd recommend lowering your resolution and then playing around with the refresh rate. I suppose I should have clarified this earlier, sorry about that. If things are still blurry, I guess modifying the aero.msstyles file is your only option.
I did think about changing the DPI (which is the 125% thing) when you first mentioned your problem, but I remembered that it didn't do me any good as it resizes everything and not just text, so I didn't even bother to mention it. Plus I figured you probably already knew about it.
I don't know if the method I'm thinking of is officially documented anywhere, but it does work. It is also unrelated to Vista Style Builder and my installer. As I mentioned in the Windows Aero (Tahoma Font) Manual Installation Instructions (wow, that is long winded) it is possible to use multiple versions of aero.msstyles after only a few steps. Here's the relevant part, reformatted and with some slight additions:
- Make a copy of C:\Windows\Resources\Themes\Aero\ and rename the folder to something different, such as "Aero Tahoma".
- Do not rename any of the files in the folder. While it is possible to rename them and retain full functionality, all relevant files must be renamed. In my initial implementation of Tahoma in the Aero Theme (known as Aero Theme (Fixed)) I made the mistake of renaming them and unfortunately missed one file, causing a visual bug.
- Replace the aero.msstyles in your new folder with your custom .msstyles file. Make sure that your custom file is also named aero.msstyles unless you are renaming the other files in your new folder as well.
- Make a copy of the desired Aero-based .theme file (located in C:\Windows\Resources\Themes\) and rename it to whatever you would like. For example: "architecture-tahoma-9pt.theme"
- The new .theme file will have to be edited (this can be done in Notepad) to point to the proper aero.msstyles.
- Under the [Theme] section, change DisplayName to whatever you desire. For example: "DisplayName=Architecture - Tahoma 9pt".
- Under the [VisualStyles], change the Path to point to the appropriate .msstyles file. For example: "Path=%ResourceDir%\Themes\Aero Tahoma 9pt\Aero.msstyles"
You will need to change every single .theme file that you wish to use with the custom .msstyles file. The reason that I didn't do this with the Windows Aero (Tahoma Font) Installer and instead replaced the original aero.msstyles file was to achieve compatibility with third-party themes. I felt that it would be way too much to ask the average use to edit their .theme files.
I think that it means "Use in Windows" and I assume that this issue is just a bug. Since multiple .msstyles files can be implemented at once, as described above, I didn't bother looking for a solution. If you're still interested, try the Vista Style Builder Forums. It's quite likely that there's already a solution for this problem.
Yup, you're right about the files needing to be repatched if a Windows Update ever overwrites them. Though as far as I know, it is very unlikely that will ever happen. If it does, just do a search for deepxw. Hopefully he/she will have a new version of Universal Theme Patcher in such an event. If not, I'm sure someone else will take care of it.
I've noticed this as well. It doesn't seem to be an issue since, as you said, .msstyles files are savable if you just keep trying.
Even if you have no further issues in solving your problem, please let me know how it goes.
Last edited by Eric G; 10 May 2010 at 21:16.