[Shell Patcher] Super Turbo Tango Patcher 6000


Recommended Posts

^Yep, laptop, indeed.

While charging I get a plug next to the battery - but I'll keep an eye on that; still haven't seen the low and critical status :)

I guess most users that actually use the battery icon have a laptop, so the generic image should be fine, at least it is with me.

How i would love a 64bit version.. Hows it going regarding that, vert?
Yeah, it's about time that gets a faq-like entry.

Information on 64-bit support:

  • Doesn't exist. At least not right now.
  • There aren't any commandline scriptable resource hacking tool that supports 64-bit binaries. Sure, there's a few graphical tools, but they're not scriptable, and several of them are commercial software.
  • Not a whole lot I can do about it; I'm not into the kind of low-level binary executable disassembly voodoo it would take to make one.
  • http://www.msfn.org/board/official-ize64-topic-t105086.html is probably the thread for you to watch, if you're interested in that.

Sweet mother of f***. I'm so playing with that when I get home... time to download a 64-bit image and play with that for a few rearms. It sounds like it only runs on 64-bit systems, though, so I'd have to either maintain two sets of scripts, or build something to translate between formats (probably not a bad idea anyways), but that sort of thing is totally my domain. Edited by vertigosity
Sweet mother of f***. I'm so playing with that when I get home... time to download a 64-bit image and play with that for a few rearms. It sounds like it only runs on 64-bit systems, though, so I'd have to either maintain two sets of scripts, or build something to translate between formats (probably not a bad idea anyways), but that sort of thing is totally my domain.

Cool, I hope there is a 64 bit version in the future, although I know you can make no promises now. :)

Re jardasmid's resource patching tool:

Unless I'm missing something (possible!), it won't work directly, but it is d***ed close to being what is needed. It doesn't seem to support the icongroup resource type (it's some kind of weird index amalgamation that ties together the singular icon resources, which are what actually store the image data, but might not always line up 1:1 between a system file and a donor .ico)... but it seems to be close enough to be worth pestering the author about.

Eh, it is, but at the same time it kinda isn't, since I will probably have to be seriously using X64 before I start working on it. VMware doesn't seem to want to run it in a VM on 32-bit Vista, so I have to use it as my main OS, even to just test stuff on it in a VM.

Mini-review of my experience with 64-bit WinVI:

It's a mixed bag - there's not really a direct point in it for me.

(0) My total memory addressing space comes in under 4GB

(0) Literally every program I run has a little *32 by it in Task Manager

(-) I'd have to give up using Tango, at least until I got the patcher working.

(0) I don't really have any 16-bit apps that weren't better run in DOSbox anyways, so it doesn't lose any points there.

(0) I'm really impressed at the number of 32-bit programs that rely on drivers and/or shell extensions to operate that "just work."

(0) Something just bugs me about having two versions of most system files sitting around, one for 32-bit, and one for 64-bit... I know why they did it the way they did, but I would have preferred having lots of shims and thunkers instead.

(-) Lots of little UI customization programs I like need specific 64-bit versions, which aren't out yet (if ever)

(+) On the other, hand, 64-bit does seem to work around a strange hardware bug that I've been experiencing in 32-bit WinVI, so I might switch anyways, just so I can use a secondary HD...

So that would make it (-1) for 64-bit in total...

You could of course install Vista x64 on a small, separate partition... Hm, ok, I wouldn't do that either...

But what about Virtual PC 2007? It worked quite well when I used it, although I have no idea if it would run 64-bit Vista (product site however says it runs 64-bit).

But anyway - I don't use WinVi64, so I don't really mind ;)

edit: Forget about Virtual PC - it wasn't all that clearly formulated. The release notes say:

* supports 64-bit host operating systems (but not 64-bit guest OSes)

Edited by MrFuji
Eh, it is, but at the same time it kinda isn't, since I will probably have to be seriously using X64 before I start working on it. VMware doesn't seem to want to run it in a VM on 32-bit Vista, so I have to use it as my main OS, even to just test stuff on it in a VM.
Yeah, I don't know WTF I was doing, it was complaining about not having VT support; it's working fine now with 32-bit host and 64-bit guest.
  • 3 weeks later...

From the "meh" files, icons in dialog boxes (error / warning / question / info) are stuck as Vista stock... they're located in user32.dll, as they were in XP, but if you replace it with a modified version, Vista goes into activation failure panic mode. I just LOVE playing with The OS That Knows Better.

8.03 with some minor updates sometime this weekend, unless my internet connection keeps acting up (which seems likely...), in which case it'll come out Monday when I go to work.

It's been a busy month for me outside of Tango-land, but perseverance has brought 8.03 to see the light of day. It's not overwhelmingly impressive, but it is a quantum leap from the previous version. Also, although I know I'll regret it as soon as I've posted this, I'm ready for people to start posting their skinning requests so I can prioritize and make the most efficient impact with what little time I do have free for the patcher these days.

Highlights from my SVN log:

  • Remove the "identifier" overlays from the battery meter
  • At least the beginnings of Tangoization on iexplore, wimp, wab, hh, msi, cleanmgr, games also in gnome-games, and a few miscellaneous things that were in 2600
  • Add branding images for each Vista+Srv2k8 edition
  • Classic start button bitmap (Srv2k8 OOB default)
  • Tweaks to folder icons, and add an icon for the home folder
  • Miscellaneous fixes to the installer and patcher

As usual, download link in first post.

Some caveats: I'm almost positive that this will break horribly on non-English setups, and certain dual-boot scenarios. If you don't have a standard c:\windows setup, you may need to perform a search-and-replace on the paths hardcoded in FileList.xml. I really have no idea how XPero's handling this in Vize, I guess I need to either look into it or write some code myself. Don't uncomment the line in FileList.xml for user32.dll unless you're feeling brave and are comfortable talking to the activation support machines/people – but please, let me know what happens if you do / I'm not buying you a new license if it gets you on a WGA blacklist. If you are editing FileList.xml, remember to start notepad with admin credentials, or you won't be able to save your changes.

I'm almost positive that this will break horribly on non-English setups, and certain dual-boot scenarios. If you don't have a standard c:\windows setup, you may need to perform a search-and-replace on the paths hardcoded in FileList.xml.

Now that scares me a bit. 8.02 worked just fine, what's 8.03 doing differently?

Now that scares me a bit. 8.02 worked just fine, what's 8.03 doing differently?
Nothing - I've heard a few reports, looked through to see if anything in the Vize code was translating paths, and just now decided to say it.
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!