Policy regarding OS X on non-Apple Hardware


Recommended Posts

Is creating a new subforum for this a good idea if Neowin is going to allow this discussion? (I know, Neowin is looking to simplify its forum structure) - but I think it's reasonable to say that it will annoy genuine Mac users in having the Apple General Discussion forum full of [OSx86] threads. I'm not a Mac user (yet!), but I can imagine having these topics in this forum would annoy those who have Macs.

I'm already annoyed with it - I'm a mac user, trying to read genuine mac threads and I've already had to bypass one... where's the ignore button?

I agree with the previous poster about the origin of the media (as i've seen in other threads)... when someone has to say that they are using genuine media, do we assume they are not? How many OSx86 users would go out and buy it legally just to try it to see if it works?

Those shipped with a mac are only allowed to be used with that mac are they not? Similar to how Windows licenses OEM software...

the OSX EULA doesn't explain why neowin wont let threads exist on OSx86 before this thread...

i will not applaud this sorry should have been this way from the beginning... you can buy OSX! piracy was the issue not because you feel like installing it on your own hardware....

anyone who defends OSX or apple on the "is must be sold with a mac and used on a mac" is a tart

So, the policy is "don't ask, don't tell"? That a "wink" about the media origin is OK? I guess that the same assumptions are made about Vista and Photoshop in the forums. Only direct admitting to warez copies is acted on. So being evasive about the source of your OSX is the way for pirates to go.

If this was all based on that ruling, then why did not anyone say so at the beginning announcement?

If it is of any consolation, I now accept this not only as a staff decision, but I understand the reasoning behind it. I won't be posting any more questions on this. :yes:

(I still am strongly opposed to "wink warez", though) :p

I've added that to the first post if that makes you feel better :)

And since when Cara speak for Neowin or Apple? Never, she speaks for herself.

Didn't say that, I was just offering a different relevant perspective...

Regardless, it should certainly get its own forum rather than pollute the existing forums.

I'm not saying I believe or disbelieve her to be an Apple employee. That wasn't my point. My point was we're not here to cater to Apple, we're here to help the community.

I don't understand this. You're not here to cater to Apple, so you're willing to let people discuss how to violate their EULA. By this reasoning, you're not here to cater to Microsoft, so why aren't users allowed to discuss how to bypass Windows registration? I mean, you're here for the community, right?

So if the mods allowed discussion and distribution of warez or bomb manufacturing we shouldn't have the right to discuss whether they may have made a terrible mistake?

Nope. Its the owner's server. They can post whatever they want on it. Don't like it? Leave.

I for one, will not help anyone I am even suspicious of using OSX86.

But you will help someone installing Windows on their Mac right? Wrong direction :(

For members like StevoFC is the reason I think x86 should have its own section :)

So, the policy is "don't ask, don't tell"? That a "wink" about the media origin is OK? I guess that the same assumptions are made about Vista and Photoshop in the forums. Only direct admitting to warez copies is acted on. So being evasive about the source of your OSX is the way for pirates to go.

Neowin does not condone warez, but this has really the way it has always been. Neowin is not the internet police. We can't know where software comes from unless you clearly make it obvious that it is warez. It isn't "don't ask, don't tell", we firmly believe users should purchase legit copies of software, which is why we're not allowing discussion of downloading Hackintosh from the internet, someone must have their own legit copy of it.

I don't understand this. You're not here to cater to Apple, so you're willing to let people discuss how to violate their EULA. By this reasoning, you're not here to cater to Microsoft, so why aren't users allowed to discuss how to bypass Windows registration? I mean, you're here for the community, right?

That's different as that's covered by US law. Neowin, as Timdorr has mentioned, allows the discussion of uxtheme.dll, for example, and allows users to post links to patches and modified .dlls. This violates Microsoft's EULA, but does not violate US law.

I don't understand this. You're not here to cater to Apple, so you're willing to let people discuss how to violate their EULA. By this reasoning, you're not here to cater to Microsoft, so why aren't users allowed to discuss how to bypass Windows registration? I mean, you're here for the community, right?

patching windows (uxtheme.dll, icon packs (the ones that replace system files)) is against the EULA yet it's allowed, I think that's what they're referring to

I don't understand this. You're not here to cater to Apple, so you're willing to let people discuss how to violate their EULA. By this reasoning, you're not here to cater to Microsoft, so why aren't users allowed to discuss how to bypass Windows registration? I mean, you're here for the community, right?

"'Cracking' is circumventing a copy protection of some sort. There is no copy protection with OS X. There isn't even a CD key at all. What's being done by people is they are modifying the software in a way that violates their EULA. But a EULA is just an agreement between the user and Apple. It's nothing illegal to violate it, since it's not a law that you're breaking. The most Apple can do for violating it is to deny you support."

We allow users to discuss breaking the EULA for Windows. It has already been stated in this thread that by installing the uxtheme.dll file that breaks the MS EULA.

That's different as that's covered by US law. Neowin, as Timdorr has mentioned, allows the discussion of uxtheme.dll, for example, and allows users to post links to patches and modified .dlls. This violates Microsoft's EULA, but does not violate US law.
patching windows (uxtheme.dll, icon packs (the ones that replace system files)) is against the EULA yet it's allowed, I think that's what they're referring to

Ok, thank for clearing that bit up. (Y)

That's different as that's covered by US law. Neowin, as Timdorr has mentioned, allows the discussion of uxtheme.dll, for example, and allows users to post links to patches and modified .dlls. This violates Microsoft's EULA, but does not violate US law.

Exactly.

LOL You all get so whiny about stupid stuff. Why are so many of you so passionate of buying a Mac? Do you all get commission for every Mac Apple sells?
Nope. Its the owner's server. They can post whatever they want on it. Don't like it? Leave.

But you will help someone installing Windows on their Mac right? Wrong direction :(

For members like StevoFC is the reason I think x86 should have its own section :)

+1

I am willing to bet $10 that at least 50% of NeoMac users run either pirated XP or Vista on their Macs. So why should we treat OS X any different? Neowin sure doesn't condone piracy and I am not advocating it either. Just can't figure out all the Mac users on their high horses.

+1

I am willing to bet $10 that at least 50% of NeoMac users run either pirated XP or Vista on their Macs. So why should we treat OS X any different? Neowin sure doesn't condone piracy and I am not advocating it either. Just can't figure out all the Mac users on their high horses.

I actually use the copy I had purchased for my Macbook Pro, when I sold it I restored it back to 10.4 and kept my Leopard box

Neowin does not condone warez, but this has really the way it has always been. Neowin is not the internet police. We can't know where software comes from unless you clearly make it obvious that it is warez. It isn't "don't ask, don't tell", we firmly believe users should purchase legit copies of software, which is why we're not allowing discussion of downloading Hackintosh from the internet, someone must have their own legit copy of it.

That's just it. Neowin has always had a 'don't ask, don't tell' policy with warez. If the member doesn't specifically come out and say it, the assumption is that they are asking about legally obtained software.

That stance has never really sat well with me, but ah well. I really doubt many people will go out and buy a copy to install on their Dell, Gateway, custom-built computer. That action really doesn't jive with the intent of the Hackintosh community. Perhaps things are different now, but previously the only way to install OS X on a non-Mac was to download a hacked copy from P2P sites. Either that or be the one doing the hacking.

While I agree that the EULA has no legal binding, and therefore the discussion and action of installing OS X on non-Mac computers is not illegal, I can see where Mark is coming from. The Windows EULA would seem to be treated differently than the Apple EULA

Edited by Chad

Contracts, such as EULAs are protected by law, that's why they are written by lawyers and in lawyer speak. So they are protected by US and international laws.

Whether Neowin chooses to abide by specific things in those contracts is up to them and at their own risk to support the breaking of these clauses. I wouldn't be convinced by Neowin pulling out cases that back them up as I'm sure Apple would be more than willing to drag someone into court to prove that case wrong one of these days.

Anyway, I've got nothing particular against it, but as I said, seperate forum please, this will really **** off those who are avoiding this grey area or typical mac users who would not have OSX86's many issues.

Hey everyone, I know some people have been wondering when I'd chime in here.

Just for the record at no time do I officially speak for Apple in any correspondence here on Neowin, all thoughts or material posted here is done as my own thoughts, observations, or so forth.

I would hope that people will respect the decisions of the Neowin Administration in their decision to open this topic up. Though many of us do not agree that it is appropriate, or legal as the case may be, Neowin is free to do as they please in this matter until such a time as Apple (as a corporate entity) were to serve a Cease and Desist order to them regarding a specific topic. With that said, I do sincerely hope this DOES NOT HAPPEN as I know all of us enjoy and love the Neowin Community.

My concern is the (potential) flood of x86 posts clogging up the Apple Forums. x86 is not Apple related, it is different hardware and software from official distributions of Mac OS from Apple. People can argue this all they way, if you are required to use an EFI Emulator then you are not running the software Native and thus it is not the official method of running it.

I feel that in order to best serve the Apple community here on Neowin, if this topic is going to be allowed there does indeed need to be a x86 forum created for simplicity. How does adding a forum make things more simple? It keeps these threads out of the way of Apple users and allows the x86 community to have their own identity away from Apple users. I feel that many real Apple owners will refuse to aid x86 users, as is their right, and I feel that moving those threads into their own section will cut down on the potential for flame or hostile posting as a result.

These are my thoughts, I do plan to draft up these thoughts into something more solid to send off to the Admins when I get home but until then I hope that the Apple Community here on Neowin is adult enough to handle these x86 threads and not start flames/hostility over them.

We are all Neowinners guys, regardless of the OS being used.

Edited by Cara
You can run Vista for 30-days per install. Will that rule forbidding this be removed now? After all, less circumvention is being done reinstalling than there is in making OSX work on beige box hardware.

That isn't an issue of just an EULA with Vista, it's also a copyright issue. Microsoft, through the 30 day trial program, has implicitly granted you 30 days to make use of the copy of the product. Circumventing that system is breaking copyright law, not just the EULA. That is a US law and is therefore illegal where the servers for this site are housed.

Didn't Vista have some absurd clause in the EULA stating that it couldn't be run in a VM for certain editions? It's the same thing. As long as you obtained the copy of Vista legally or are using it under the copyright of Microsoft, then it doesn't matter with the US courts if you violate the EULA. Microsoft might be able to sue you individually, but that's a (very minor) risk you'd have to take.

Contracts, such as EULAs are protected by law, that's why they are written by lawyers and in lawyer speak. So they are protected by US and international laws.

The law states that Apple cannot force a user to install their OS on specific hardware, that trumps any EULA Apple can come up with, I don't care who wrote it.

Quote from Apple Insider, ""a 1984 U.S. Circuit Court of Appeals decision held that a software publisher can't require consumers to run an operating system on a specific type of hardware".

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!