Recommended Posts

I've been following a topic on wincustomize for a while now. It's the dreaded .wba vs .msstyle debate.

Firstly, it's been said that .msstyle mods are actually illegal. That it's much like p2p for mp3's It's illegal but everyone does it anyway.

It's also been said that .msstyles wont work on the longhorn version, and everyone will have to use windowblinds.

Any truth in this?

Link to comment
https://www.neowin.net/forum/topic/267011-msstyle-releases-illegal/
Share on other sites

.msstyles files are not illegal, but the patch is, cause your modifying copyrighted microsoft files. (But with StyleXP you get away with that, cause it does a in memory patch, and that doesnt count)

Edit: they are probably right about longhorn though, most longhorn apps are vector based (so that poses a problem for windowblinds aswell) and .msstyles are designed for 96DPI screens. And the fact the the ui is radically different, new ui elements, so wb themes will have to be written for longhorn aswell) Also, if microsoft put the themeing engine in xp, they will most likely put a version in longhorn aswell.

the msstyles format is not copyrighted to my knowledge, modifying the luna.msstyles file is breaking copyright, but making a file that mimicks it's format is not breaking copyright (it comes under fair-use laws)

Edit: If it was breaking copyright, would ms have worked with TGT Soft on StyleXP?

Why did microsoft not just allow the posibilites of visual styles without a hack anyway? Is this something we might look forward to in longhorn... I mean it only represents a further flexibility with the OS, although I can imagine StyleXP and Stardock sueing MS if this was done for anti-competitiveness. It's already happened with windows media player ffs!

I was wrong about the 96DPI thing in .msstyles, they support higher DPI's

I am sure i read about microsoft helping them on TGT Soft's page, i just got to find it.

And, Axel, Microsoft said they removed the ability for 3rd party themes incase the would get a flood of calls if users install bad theme files, and blame it on them (it was the right descision, those who want 3rd patry themes get them, those who dont never have to bother)

Why did microsoft not just allow the posibilites of visual styles without a hack anyway?  Is this something we might look forward to in longhorn... I mean it only represents a further flexibility with the OS, although I can imagine StyleXP and Stardock sueing MS if this was done for anti-competitiveness.  It's already happened with windows media player ffs!

585235787[/snapback]

My point exactly.

I don't see any reason why they should limit us to only Luna or Classic.

I am sure i read about microsoft helping them on TGT Soft's page, i just got to find it.

585235820[/snapback]

Uh huh.

You sure your not getting confused with the fact that Stardock worked

hand in hand with microsoft to develop the msstyles engine?

I have never heard such crap. Microsoft have never worked with TGT Soft.

I've been following a topic on wincustomize for a while now. It's the dreaded .wba vs .msstyle debate.

Firstly, it's been said that .msstyle mods are actually illegal. That it's much like p2p for mp3's It's illegal but everyone does it anyway.

It's also been said that .msstyles wont work on the longhorn version, and everyone will have to use windowblinds.

Any truth in this?

585235564[/snapback]

as far as i know. The gui will be totally diferent in longhorn and i wouldn't be suprised at all if only a form of program like windowblinds will be able to skin it,

Heck, maybe microsoft is putting a proper skining engine into longhorn. We have yet to see.

IMO it's to early to answer that question really.

Right now Longhorn (build 4074) use the msstyle format too but its a litle different. The image have one more stage (something like an animations) and it skins a lot more like toolbar buttons.

If Longhorn use similar msstyles in the final version maybe someone will cretae a XP mssstyle to Longhorn msstyle converter. Maybe in Stylebuilder?? :huh:

Here's what Im talking. The first one is the button image of Longhorn msstyle the second image is from XP msstyle.

post-1522-1104935781.jpg

Modifying and realsing a .msstyle is illegal according to the US DMCA. When you take a piece of code, modifiy it, repackge it, and release it to the world it is illegal. How ever harmless your intent was, that act was illegal as you violated MS intellictual property rights under the US DMCA.

Look at the original luna.msstyle that all .msstyles are based on. It has a copyright on it. That copyright and digital signature that comes with it belongs to Microsoft and gives them certain rights. Why they have not chosen to go after companies like tgtsoft or starskin is beyond me but it is true that Stardock and Microsoft DID work together to create the original uxtheme

The high school posters or college posters here may not care that creating a skin in a .msstyle format is illegal and they may even get a thrill out of doing so. But for those of us that want more, that like our computer to do more, and for those artists that make their living off of computer customization, .msstyles are illegal.

luna.jpg

Why [Microsoft has] not chosen to go after companies like tgtsoft or starskin is beyond me but it is true that Stardock and Microsoft DID work together to create the original uxtheme.

585236094[/snapback]

Technically, modifying and reverse engineering a piece of software and all outcomes of the acts are illegal because of copyright law. However, Microsoft chooses not to enforce their copyright (on the file format) for themes, so themers are currently in no legal danger.

Microsoft decided not to open up the ability to make skins for Windows XP because (as previously stated) they did not wish the stability and visual aspects of their product to be compromised. Microsoft wants the desktop to look familar to all users, no matter what theme, and assures the start button and buttons follow similar design guidelines. Users could (and have) developed themes that hide the start button and similarly disguise other visual elements in an unusual fashion. Futhermore, it is reasonable to assume that errors with themes could create an unstable graphical subsystem and that .msstyle files can contain viruses/intentionally harmful code.

So, Microsoft chooses not to support and prohibit (by required themes to be digitally signed by Microsoft) theme development. However, WinXP is technically able to natively support themes and Microsoft has helped third parties to develop software that disables the 'digital signature required' aspect of the uxtheme.dll. It allows those who want to skin their computer the ability to do so if they install a third party product. And because they are installing a third party product Microsoft is not responsible for any adverse effects. Visual styles are new and perhaps Microsoft is still working out the bugs.

WindowBlinds uses a different method of skinning which does not rely on the OS as much. Therefore, can easily be adopted to Longhorn. Microsoft does not care about comptability between XP + Longhorn visual styles because they do not officially support theming. They have the flexibility to change whatever they need/want to.

The high school posters or college posters here may not care that creating a skin in a .msstyle format is illegal and they may even get a thrill out of doing so.

If the company which holds the copyright chooses not to enforce it then there is no danger. Microsoft's intesive legal team has not asked a single web site to stop hosting themes or sued any artists who distribute MSStyles. Clearly, Microsoft does not support editign of MSStyles but they also do not oppose it.

Edited by KayMan2K
So, Microsoft chooses not to support and prohibit (by required themes to be digitally signed by Microsoft) theme development. However, WinXP is technically able to natively support themes and Microsoft has helped third parties to develop software that disables the 'digital signature required' aspect of the uxtheme.dll. It allows those who want to skin their computer the ability to do so if they install a third party product. And because they are installing a third party product Microsoft is not responsible for any adverse effects. Visual styles are new and perhaps Microsoft is still working out the bugs.

I'd like to see the evidence that Microsoft has ever worked with ANY company or software engineer to bypass the WFP system to get around the digital signature of either the uxtheme.dll or the digital signature of the .msstyle.

To date ONLY Stardock's windowblinds program has recieved the "designed for windows XP" logo from Microsoft.

mslogo3.gif

Designed for Windows XP certified programs by Microsoft:

Desktop themes: http://www.microsoft.com/windows/catalog/d...ff13ea45b&tab=1

Edited by AthleticTrainer1981
To date ONLY Stardock's windowblinds program has recieved the "designed for windows XP" logo from Microsoft.

http://www.stardock.com/products/windowblinds/mslogo3.gif

585236751[/snapback]

Which of course doesn't mean that they've worked with Microsoft either - only that they've been certified by Veritest that the program behaves nicely with Windows XP.

Which of course doesn't mean that they've worked with Microsoft either - only that they've been certified by Veritest that the program behaves nicely with Windows XP.

585236799[/snapback]

From 2000-2001 when XP (then know as whistler) was in testing, Stardock was working with Microsoft to develop the uxtheme skinning engine. Consider the uxtheme to be a a stripped version of windowblinds, basically version 3 of WB.

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

    • No registered users viewing this page.
  • Posts

    • About bloody time. I have got PRs with hundred of files and the Web UI just struggling to even load the pages.
    • I wonder if it was applying secure boot certificates/dbx files?
    • I recently tried edge. It seems a lot better. A lot of the junk in it is gone. It seems less bloated and snappy.
    • Lethal fake phone chargers are still being sold on Amazon and eBay, UK watchdog warns by Paul Hill Credit: Pexels The UK consumer rights organization, Which?, is claiming that “potentially lethal knock-off chargers” are still being sold on online marketplaces seven years after it exposed the danger of these chargers. In its latest investigation, it bought 15 USB phone chargers from several online marketplaces and found they were missing key information, meaning they cannot be legally sold in the UK. Which? bought the 15 chargers from seven online marketplaces. These were Amazon (including Amazon Haul), AliExpress, B&Q Marketplace, Debenhams Marketplace, and eBay. It said that the chargers were so badly made that anyone using them was at risk of electric shock. Over half the chargers also posed fire and explosion risks. Of the chargers purchased, one was a fake Apple USB-C 35W power adaptor charger. To confuse buyers, the box was branded with an Apple logo, but testing found it to be a fake. Further testing picked up arcing sounds after 10 seconds of use, where a current jumps between two parts of the electrical circuit, which can cause fires, explosions, or electric shock. The manufacturers of this particular charger also put modeling clay inside it to make it feel more weighty, robust, and genuine. Not all of the chargers were technically faulty; however, some were missing key packaging, markings, and documentation, meaning they can’t be sold in the UK legally. Which? said that it is now campaigning alongside a coalition of safety groups and businesses for new laws that make online marketplaces responsible for ensuring the safety of products that they choose to list on their websites. It also said the government needs to start using powers under the Product Regulation and Metrology Act, which was adopted last July, to impose safety requirements on online marketplaces via secondary legislation, but so far, there have been delays. No matter what country you are in, be sure to properly research what you are buying and only buy authentic chargers to prevent fires. You can read more about Which?’s research here.
    • Visual Studio finally gets long-awaited feature that developers will love by Usama Jawad Visual Studio Code is Microsoft's popular, lightweight, open-source code editor, it is actually Visual Studio that is the company's flagship integrated development environment (IDE). Although the IDE already offers a boatload of useful features for developers, Microsoft has finally introduced a long-requested capability that will be loved by many. While developers have already been able to create Git pull requests (PRs) directly within Visual Studio for the past couple of years, it had not been possible to review a PR without switching to the browser, until now. Microsoft revealed in December 2025 that it is working on UX that enables developers to do just that, and fast-forward to June 2026, and Visual Studio finally has native capabilities to open and inspect a PR, discuss feedback, and wrap up the review, all without switching to the browser. This integration works for both GitHub and Azure DevOps (including on-prem). Developers have access to multiple surfaces to open a PR, including Git Repository, Git Changes, and the Git menu in Visual Studio. Once you open a PR, all the important details will be immediately visible to you, from where you can navigate to various levels of granularity and branch states, depending on the reviews that you are engaged in. As you would expect, you also get a diff view that enables you to see code changes inline or side-by-side in a separate panel. You can also review commit-by-commit. Additionally, this UX fosters collaboration as you can leave comments, reply to threads, and resolve conversations easily. Naturally, you can also leverage Copilot to apply a code suggestion to fix a potential issue. When you are done, you have the ability to approve, complete, and merge the PR. This is a pretty major feature as it has been requested heavily for the past few years. You can try it out in Visual Studio 2026 version 18.7, made available here recently. Microsoft plans to enhance this experience further in future releases with comment filtering, a timeline of PR activity, and more.
  • Recent Achievements

    • Week One Done
      Timaximus earned a badge
      Week One Done
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Rookie
      FBSPL went up a rank
      Rookie
    • First Post
      davidbazooked earned a badge
      First Post
    • Week One Done
      davidbazooked earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      499
    2. 2
      PsYcHoKiLLa
      174
    3. 3
      +Edouard
      160
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!