[Shell Patcher] Tango Icons for Windows


Recommended Posts

Sweet deal.

EDIT: I just found a tut for changing SP2 bootscreens with the palettes. ( I would try it myself, but I don't have a pc to mess around with

http://www.geocities.com/thejjoelc/XPbootcolors.html

Woot, that's exactly the information I need. Thanks for finding that for me :D
Is the beta skinning those buttons as part of its "really fine"? If it is and the previous versions didn't... SP1?

the beta doesnt skin those buttons, and the previous versions didnt.......sp1? SP2 with all the latests updates

the beta doesnt skin those buttons, and the previous versions didnt.......sp1? SP2 with all the latests updates
Alrighty. I'd appreciate it if anybody who isn't having those skinned would post the directory names with "Common-Controls" in their name in their %windir%\WinSXS directory.
Its not working for me,

I have WinXP SP2 and already run it 3 times (Hack-o-matic) Reboot and the icons still the same...

Any idea why?

dekel

What does the contents of the "modified" subdirectory of the patcher look like?

The icon cache wouldn't affect the toolbars or display of any other bitmaps, so generally, that's a good first-check to see if it worked.

I just read the website for the bootscreen palettes, and it seems pretty easy. It's just long tedious work.

Now how many versions of the kernel are there? (w/ SP1, SP2 updates?)

Long, tedious work... which my philosophy would be to find a way to perform programmatically, with some sort of script, so that it's no longer work at all;))

I can't even begin to guess. I know SP0 and SP1 both had two versions each, one for single-processor systems and another for multiprocessor systems. SP2 has new versions of those two as well, times two for systems with Physical Address Extension enabled, and I'd assume "the GDR hotfix" (as I'm calling it) includes new versions of all four. I'm pretty sure the GDR kernel is used when that hotfix is installed on SP1, as well, as I've seen threads here from people wondering why their XPSP1 system is versioned "Service Pack 1: Build 2600 (xp.sp_xpsp2)" or something to that effect. That's at least twelve right there, not counting Server 2003. But that doesn't matter, I just have to search-and-replace the pallette strings, and run a reshack script - for any of them. I'm not including pre-hacked binaries - that's a lot of space in the archive, it'd limit the useful lifetime of a point release, and it'd probably get MS lawyers breathing down my neck.

Edited by vertigosity
my english is not so good anyway, this is what u want???
Precisely, thanks. It also tells me why that's not being replaced - that's not a location I've identified for that file. Beta 2 should patch it.
Psssssst... vertigosity!

http://vertigosity.benpbrown.com/beta

*runs away*

Guess I need to brush up on my Latin, to read the example text:rolleyes::

Here they are:

x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a

x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9

x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2649_x-ww_aac16c8b

Eek, I've found a nasty bug in Beta 1. Uh... it doesn't seem to back up the comctl32.dlls, so anybody who gave that a spin is stuck with Tangofied filepicker dialogs. I don't have a clue how that could have passed quality control. Erm... sorry, please don't murder me? I've pulled the download, and removed the links. If anybody wants the original files, PM me with your email address - drop 'em in the pack's backup directory, and the uninstaller will Do The Right Thing with them. I'll have a "Beta 2" build with proper comctl32ing, an obscure bug from XPize fixed, and with Firefox's location read from the registry sometime this weekend. Thanks for playing Russian Semi-Automatic Beta Roulette!

Gah. The beta could have blown up my computer and I still wouldn't care. The quality of this patcher is simply extraordinary. Take your time! :p

I just got done playing around with the custom made icons and changing them to 256 x 256 PNGs. I am such a PNG freak heh. Anyway, now I'm going to waste time and play around with skinning up Firefox and whatever else I can think of for my own personal use. Thanks for the icons, vertigosity! Simply amazing :D

Woot, now I can cut-and-paste. You have build 2649, as does Daeron... I wonder when that version was introduced.

Hmm. I thought about mentioning that my machines have different Windows updates installed. On the english one I used the latest Autopatcher from June (updated last weekend) and on my german version I used Windows Update (updated about 2 weeks ago). So it must have been in the past 2 weeks ;)

Since you found the problem I'm really, really looking forward to the next release :D

I just got done playing around with the custom made icons and changing them to 256 x 256 PNGs. I am such a PNG freak heh. Anyway, now I'm going to waste time and play around with skinning up Firefox and whatever else I can think of for my own personal use. Thanks for the icons, vertigosity! Simply amazing :D

r u gonna release them??? me want them :p

If someone makes me some resources to work with, I would be more than happy to try gettting a working notoskrnl for the Windows XP SP2 I am running on.

EDIT: I just tried to make a custom notskrnl and I'm trying it out now... I hope it works.

Edited by tehmemories

r u gonna release them??? me want them:pp

You mean the 256 x 256 PNGs? Am I allowed to release them? They are 100% not mine, heh. I guess if vertigosity is okay with it I could put them into a zip and upload them into dA or something. I can't take any credit for them and I only used Inkscape to export them. Not that hard...I think lol

You mean the 256 x 256 PNGs? Am I allowed to release them? They are 100% not mine, heh. I guess if vertigosity is okay with it I could put them into a zip and upload them into dA or something. I can't take any credit for them and I only used Inkscape to export them. Not that hard...I think lol

You don't need my permission - free and open source licenses :yes: - just make sure you get the right creator and license information in the package, I'm not the creator of 99% of the icons, just another packager.

http://creativecommons.org/licenses/by-sa/2.5/ for Tango/Tangerine stuff, http://en.wikipedia.org/wiki/GNU_General_P...e#License_terms

for Gnome-icon-theme stuff.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Are you going to do performance benchmarks comparing all states? I'd be interested in seeing that in the next "part".
    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
  • Recent Achievements

    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      78
  • Tell a friend

    Love Neowin? Tell a friend!