[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

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Just because Nanite can render meshes with millions of polygons doesn't mean you should use it like that, in fact, Epic recommends you avoid doing that. Most of the stuttering can easily be fixed by cutting down on unique shaders by using master materials and generating a PSO cache and compiling every shader before loading the game and also managing what must be loaded and unloaded at runtime, it's up to the developer to set all that up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!