Incidentally, one of the issues many people, myself included, have with TGTsoft is their borderline dishonest marketing.
Some people have complained about how "aggressive" Stardock is at marketing but at least we are truthful or at the very least our claims follow the spirit of the law as well as the letter and not just the letter.
For instance, consider TGTsoft's claims about Style XP vs "non Microsoft skinning software" (i.e. WindowBlinds):
Claim: “Zero Footprint Operation”
TGTsoft claims that zero foot print means that because it uses XP’s bundled skinning system that it uses no resources. If that is the case, then WindowBlinds uses less than zero resources. XP’s bundled engine requires memory and system resources to load, draw and maintain visual styles. So does WindowBlinds. However, WindowBlinds uses less memory and resources than the bundled XP skinning system.
Claim: Explorer Views are Skinnable.
This has nothing to do with Style XP. If the skin author includes a shellstyle.dll with their theme, Windows XP will use it. This is the same as WindowBlinds (WB skin authors don't make it a habit to pass around shellstyle.dll's since WB skins install automatically and hence this would require the user to mess around with replacing shellstyle.dll). However, WindowBlinds 4 will offer an integrated, seamless way for users to skin the explorer views. No need to include a copyrighted shellstyle.dll with ones visual style.
Claim: 100% Application compatibility.
This is just plain false. Windows XP visual styles do not work on the majority of existing software fully. Delphi apps, many visual basic apps and many MFC written programs either have to be excluded or only have their title bars and borders modified. The rest look like plain Windows 95. WindowBlinds, by contrast, has much greater compatibility due to the greater amount of time it’s been in testing. Bottom line, if you want your programs to look consistent, WindowBlinds is the only option.
Claim: Integrated into theme files.
TGTsoft means by this that .msstyles files are supported by Microsoft’s .theme format. That is true. However, .msstyles files are not supported by .suite or .xptheme files which are a superset of .theme in functionality. Formats are only as useful as their level of distribution. Consider how silly this claim really is: What is a .theme file really? It's a skin, a wallpaper, maybe some icons, maybe some cursors and maybe some sound. What can a WindowBlinds skin do on its own? A WindowBlinds visual style can contain a wallpaper, an icon package, cursors, sound effects. TGTsoft tries to make a weakness sound like a strength (.msstyles are just the visual style where as a WindowBlinds visual style can do what's in a .theme already).
Claim: Multiple language support.
This is an odd claim as virtually any program can make this claim (such as WindowBlinds which is very popular in Japan).
Claim: No hooking of SetWindowsHookEx
This is a misleading claim that is borderline fraudulent. The Windows XP visual style engine hooks the system similarly to WindowBlinds (despite TGTsoft’s claims to the contrary). Every process gets uxtheme.dll attached to it as a result. This claim gives the impression that TGTsoft is not familiar with how the Windows XP style engine functions.
Claim: Multiple DPI sizes
WindowBlinds also supports multiple DPI sizes.
Claim: Integrated into themeing APIs
WindowBlinds 4 is scheduled to fully support these themeing APIs. Incidentally, the number of programs that directly call these new APIs can be counted on one hand. For a program that utilizes a skinning engine that fails to skin 90% of existing programs fully, this claim seems pretty dubious.