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

    • Not such a great deal, Ultimate, which gives you full 5080 features is $181.99 CAD per month, that's $2183.88 per year, I can buy the 5080 for $1809.99 CAD, then it goes up to $279.99 per month after the first billing cycle. Typical cloud rental, costs more than buying the hardware.
    • Wow, spoken like a true blind hater, you don't even provide arguments. Please, go check my comment above to @seacaptain and you'll find out why what you say doesn't make sense in this context...
    • Get used to this, with AI tooling now uncovering new vulns and getting them exploitable far faster than has ever been possible before software is going to need to be updated far more frequently. Back in the day it may take reseachers weeks or months to do what AI can now do in hours. Once its a threat is discovered it's weaponsized far more quickly, meaning you simply can't be waiting 2, 3, 4 weeks to deploy a patch, it needs to be patched immediately. Going to be interesting handling this in the enterprise space where traditionally patching has been steady, but very staged (and rightly so up until now), that is going to have to change.
    • You don't need to "close all browser sessions constantly" or wait for updates to install. The updates download in the background while you use the browser, without interrupting you, they install automatically the next time you launch the app. And they install very fast (depending on your storage speeds, of course), you have to wait at most 2-3 extra seconds, if any. Seems like you haven't used Edge in a loooooooong time...
    • Segra 1.6.0 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.6.0 changelog: Recording: Added HDR support. Grand Theft Auto: Added game integration for deaths (FiveM and RAGE MP supported). Highlights: Added customizable padding for highlights. Replay Buffer: Added a shockwave visual effect when a replay buffer clip is saved. Audio: Increased the maximum sound effects volume from 100% to 200%. Hotkeys: Fixed hotkeys not triggering while unrelated keys were held. Installer: Added code signing to verify publisher identity, branded the installer, and reduced OS security warnings. OBS: Updated the supported OBS version to 32.1.2. Download: Segra 1.6.0 | 74.4 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

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

    1. 1
      +primortal
      508
    2. 2
      PsYcHoKiLLa
      174
    3. 3
      +Edouard
      163
    4. 4
      Steven P.
      86
    5. 5
      ATLien_0
      80
  • Tell a friend

    Love Neowin? Tell a friend!