[Updated 8/04] Apple Sues Unauthorized Clone Maker Psystar


Recommended Posts

To everybody that says apple will loose, Apple is not going after the " Limited to Apple Hardware approach", they are going after Psystar along the ground of Modifying Apple Software ( 10.5.4 Patch ), which is alot more solid and will more effectively hold up in court.

So they are not going after EULA violation along lines of the Only apple Hardware thing, they are going after Copyright Infrigment

I'm surprised how many people think Apple would sue only under the EULA...I'm seriously feeling the entire Copyright Infringement / Illegal Distribution angle here. :)

On those points, IMO:

a) They haven't copied any material. They've installed it onto a computer and modified it to work well (by pre-installing windows, adding custom features, branding explorer in Windows - something which is common among PC OEMS, are you not modifying system files?). In fact, I don't think they've had to modify any files in order to get it to install, I think they use a standard leopard disk.

Distributing the updates I'm not too sure about - technically, the only thing they would be doing here is breaching the license (they're not passing the update off as their own work, they've just made it work). If this *was* illegal, the amount of times I've had to hack Windows Updates around for customers I'd be in jail right about now :p

b) Not sure about in the US, but here in the UK, if I purchase something, it is my prerogative to resell it. If I am doing it as a business, I have to register for VAT, but there is nothing whatsoever stopping me reselling things that I have legally purchased.

That's how I see it anyway. Sorry about the constant comparisons to Windows - It's just I don't see how there can be one rule for one piece of software, and another for another.

I'm surprised how many people think Apple would sue only under the EULA...I'm seriously feeling the entire Copyright Infringement / Illegal Distribution angle here. :)

Because if they try the Copyright Infringement angle, that will play right into the antitrust angle. It will get thrown out there that the only reason their code is the way it is, is so that their hardware partners make larger profits, so they can pay more to be the only hardware available for OSX. The fact that it is easily altered so it can be used on most x86 hardware is what could lose it for them.

On those points, IMO:

a) They haven't copied any material. They've installed it onto a computer and modified it to work well (by pre-installing windows, adding custom features, branding explorer in Windows - something which is common among PC OEMS, are you not modifying system files?). In fact, I don't think they've had to modify any files in order to get it to install, I think they use a standard leopard disk.

Distributing the updates I'm not too sure about - technically, the only thing they would be doing here is breaching the license (they're not passing the update off as their own work, they've just made it work). If this *was* illegal, the amount of times I've had to hack Windows Updates around for customers I'd be in jail right about now :p

b) Not sure about in the US, but here in the UK, if I purchase something, it is my prerogative to resell it. If I am doing it as a business, I have to register for VAT, but there is nothing whatsoever stopping me reselling things that I have legally purchased.

That's how I see it anyway. Sorry about the constant comparisons to Windows - It's just I don't see how there can be one rule for one piece of software, and another for another.

What I do is compare what they are doing to a more intrusive version of what the old Autopatcher did. Though I liked it it wasn't allowed since they were distributing Microsoft software without permission. Also, just because you have made a work around before doesn't mean you'd be in jail, it just takes a high enough profile incident of it for the original company (MS/Apple) to take notice and then pursue the ones involved.

Pystar not only is doing that but making changes to the actual code and distributing it...

Just my POV on this...

I think they use an EFI emulator that runs underneath OS X, so they technically aren't modifying/hacking any system files. Either that or a custom EFI chip that acts like the one inside a Mac.

If they aren't indeed modifying/hacking any system files, I can definitely see them winning.

Not sure about in the US, but here in the UK, if I purchase something, it is my prerogative to resell it. If I am doing it as a business, I have to register for VAT, but there is nothing whatsoever stopping me reselling things that I have legally purchased.

but you purchase a license to use the software and that license comes with restrictions right? and in the case of apple they restrictions are pretty heavy.

Microsoft Specifically allows the branding/custom features/Pre-Install, there are registry key's/settings for it

Microsoft shutdown the AutoPatcher for almost the same reasons Psystar is being sued, with exception that psystar is actually modifying them

On those points, IMO:

a) They haven't copied any material. They've installed it onto a computer and modified it to work well (by pre-installing windows, adding custom features, branding explorer in Windows - something which is common among PC OEMS, are you not modifying system files?). In fact, I don't think they've had to modify any files in order to get it to install, I think they use a standard leopard disk.

Distributing the updates I'm not too sure about - technically, the only thing they would be doing here is breaching the license (they're not passing the update off as their own work, they've just made it work). If this *was* illegal, the amount of times I've had to hack Windows Updates around for customers I'd be in jail right about now :p

b) Not sure about in the US, but here in the UK, if I purchase something, it is my prerogative to resell it. If I am doing it as a business, I have to register for VAT, but there is nothing whatsoever stopping me reselling things that I have legally purchased.

That's how I see it anyway. Sorry about the constant comparisons to Windows - It's just I don't see how there can be one rule for one piece of software, and another for another.

I think they use an EFI emulator that runs underneath OS X, so they technically aren't modifying/hacking any system files. Either that or a custom EFI chip that acts like the one inside a Mac.

If they aren't indeed modifying/hacking any system files, I can definitely see them winning.

Why do they tell users to run their "scripted installer" then?

Remember, it takes a really long time to download. It will download through our installer. Do not manually download the update from the Apple website. The updater will do that for you. Also remember to allow the computer to reboot itself when it is on the gray Apple loading screen.

The update for Leopard 10.5.4 is available through Leopard's native Software Update utility for users who have run our 10.5.3 scripted installer or whose computers shipped with 10.5.3 Leopard. Just click the Apple on the top-left of the screen and select "Software Update" to run the built-in Software Update application.

A 1.6GB download for 10.5.3 from Psystar...

select.jpg

http://209.85.141.104/search?q=cache:KNzED...;cd=1&gl=us

I see Apple losing this case, I seriously do. Psytar isn't making money on OS X because they're paying for a license. Apple is only losing money on the hardware, and considering the 1984 ruling, Apple doesn't stand a chance. At most, Pystar will be forced to stop offering modified versions of OS X.

But if Psytar has no interest in settling out of court, Apple could end up screwing themselves because a court orders them to stop forcing customers to purchase Apple hardware with OS X. And if that happens, I'm going to crack up laughing. And believe me, if the court rules the same way the 1984 court does, then Apple won't have a choice in the states but to comply.

Microsoft shutdown the AutoPatcher for almost the same reasons Psystar is being sued, with exception that psystar is actually modifying them

AutoPatcher never modified any Microsoft patches or updates, they simply didn't have permission to (re)distribute them. On speaking with Microsoft, they felt that customers would blindly trust this 3rd party method and if troubles came from it, it would look like it's Microsofts fault and not AutoPatcher.

Sometimes updates are released and then pulled within 48 hours due to critical errors in the patching process, something they can't control with 3rd party distributors.

Plus they never had a problem with AP until it started getting shipped with all sorts of popular PC magazines ;)

Edit: Misread your last part of the sentence. Oops!

I see Apple losing this case, I seriously do. Psytar isn't making money on OS X because they're paying for a license. Apple is only losing money on the hardware, and considering the 1984 ruling, Apple doesn't stand a chance. At most, Pystar will be forced to stop offering modified versions of OS X.

But if Psytar has no interest in settling out of court, Apple could end up screwing themselves because a court orders them to stop forcing customers to purchase Apple hardware with OS X. And if that happens, I'm going to crack up laughing. And believe me, if the court rules the same way the 1984 court does, then Apple won't have a choice in the states but to comply.

surely if the legal ground apple is on is that shakey then someone would have sued them long ago?

AutoPatcher never modified any Microsoft patches or updates, they simply didn't have permission to (re)distribute them. On speaking with Microsoft, they felt that customers would blindly trust this 3rd party method and if troubles came from it, it would look like it's Microsofts fault and not AutoPatcher.

Sometimes updates are released and then pulled within 48 hours due to critical errors in the patching process, something they can't control with 3rd party distributors.

Plus they never had a problem with AP until it started getting shipped with all sorts of popular PC magazines ;)

I don't think anyone, specially not me, thought AutoPatcher was modifying files. :)

I think this should be an interesting case, and I look forward to an Apple victory...but just incase I think I'll start polishing up my resume because if Apple loses and a clone war ensues Apple will not be able to keep their quality up and will simply become a (dieing) software vendor. Apple continues to operate based on the revenue from iPod, iPhone, and the Apple HARDWARE lineup...take out that and...

AutoPatcher never modified any Microsoft patches or updates, they simply didn't have permission to (re)distribute them. On speaking with Microsoft, they felt that customers would blindly trust this 3rd party method and if troubles came from it, it would look like it's Microsofts fault and not AutoPatcher.

Sometimes updates are released and then pulled within 48 hours due to critical errors in the patching process, something they can't control with 3rd party distributors.

Plus they never had a problem with AP until it started getting shipped with all sorts of popular PC magazines ;)

Edit: Misread your last part of the sentence. Oops!

Apple could pull the same thing then on Psystar, couldn't they? Not only is Psystar redistributing them without permission, but they're modifying them to their heart's content. 10.5.3 was definitely not 1.6GB.

surely if the legal ground apple is on is that shakey then someone would have sued them long ago?

You tell me: http://caselaw.lp.findlaw.com/cgi-bin/getc...;friend=nytimes

That's the ruling that Psytar is hiding behind. I guess we'll see; what comes of this will be huge for Apple either way.

Apple could pull the same thing then on Psystar, couldn't they? Not only is Psystar redistributing them without permission, but they're modifying them to their heart's content. 10.5.3 was definitely not 1.6GB.

If you want to go that route then, isn't what OnyX does the same thing? It takes the original binaries that comes with OS X and modifies them (making them smaller by taking out the PPC or Intel stuff). Or am I wrong about the way it works?

I hope Apple lose, they shouldn't restrict people to have to purchase hardware as well as software. If people wanna run this on PCs then let them and start selling it properly, cash in!
Incorrect point of view.

I cannot (and should not) infringe Microsoft copyright by re-distributing their code (and modified versions of it!). That would be illegal.

What pystar seems to be doing is exactly just that.

As far as end users, then I would support the rights of an end user to disregard their own EULA, as long as they do not break laws by selling/redistributing that content.

So, I would agree with your point if it were end users, but not for anyone distributing (whether for free or for profit - it doesn't matter).

You tell me: http://caselaw.lp.findlaw.com/cgi-bin/getc...;friend=nytimes

That's the ruling that Psytar is hiding behind. I guess we'll see; what comes of this will be huge for Apple either way.

If you want to go that route then, isn't what OnyX does the same thing? It takes the original binaries that comes with OS X and modifies them (making them smaller by taking out the PPC or Intel stuff). Or am I wrong about the way it works?

I'm not sure where OnyX does that, but that software isn't distributed as Apple software. It's not redistributed with any macs as Apple intellectual property.

I think Apple will win here, as it seems pretty obvious you shouldn't be allowed to distribute modified code that originally belongs to someone else without their permission. However, I don't like Apple restricting OSX to Apple hardware. I'm well aware that Apple makes a lot of money from their hardware but they can still do that with OSX being open - the difference is that the competition will keep them motivated to innovate, instead of relaxing in the knowledge that people HAVE to buy their hardware to run OSX. All customers would be better off if Microsoft had some serious competition from Apple. I also strongly oppose Apple refusing to license FairPlay to allow DRM'ed files from iTMS to be played on non-Apple hardware.

It's rather sad that Apple is so image obsessed, particularly when it seems to compromise products - the iPhone (no changeable battery, previously no 3G, limited multimedia functionality, etc) and the iPod (no WMA support) are perfect examples. Apple runs its business by effectively forcing people to buy their products through tie-ins (iTMS, OSX requiring Mac hardware) rather than by simply making products that stand up on their own. It's disappointing because they have the potential to be a great company but just keep spitting it people's faces (the I'm a Mac adverts, etc).

I'm no apple fanboy (not even close) but I don't see why they can't restrict their os to their hardware. It's there OS, their hardware, if you don't like it don't buy a mac.

Because they stepped away from their own hardware. The second they came out with OSX on Intel, it really put them in a bad way, since they restrict it to certain brands, not really to a type of hardware.

Because they stepped away from their own hardware. The second they came out with OSX on Intel, it really put them in a bad way, since they restrict it to certain brands, not really to a type of hardware.

And? There's no monopoly as long as there are competing products out there. (Blackberry OS is limited to RIM devices--doesn't mean that they can't not limit it. Same with TouchFlo on HTC.)

It's been told on Neowin that no OS brand can force users to ONLY use their own Hardware legally.

So they can't sue Prystar just because they sell OSX on non-Mac system.

They can sue if OSX copies are illegal in anyway.

The justification statements made by this 'Robert' person are completely moronic and goes against every major computer manufacturer for the most part. The whole what if MS said windows can't run on anything but Dell isn't exactly the same argument because Microsoft doesn't make their own hardware... on the other hand though Dell, HP, Compaq, Sun, and a host of other computer manufacturers sell computers and servers with software that work ONLY on their computers especially management consoles etc... It is impossible to install Dell Open Manage software on anything but Dells unless you do some hacking around. My point in all this is MOST if not ALL major computer manufacturers offer tools and software to their customers that are made to work ONLY with the hardware they provide. So why is it different because Apple does it?

It's been told on Neowin that no OS brand can force users to ONLY use their own Hardware legally.

So they can't sue Prystar just because they sell OSX on non-Mac system.

They can sue if OSX copies are illegal in anyway.

They can sue; in the US you can sue for anything. I could sue you for starring at me through your computer. I felt violated, but that doesn't mean they'll win though.

Exactly, This case is going to be a lot bigger than what first appears. Why, software modifcation is an untested ground for copyright infringment. Is it illeagle to take legally boughten software and modify it for your own use as that is essnetially what Pystar is banking on...remeber, they sell you a sealed box of OSX.

This could have effects on the EULA, is that allowed? Can you really tell someone who buys software that they cant do what they want with it? Sure you can cut off support but whose to say that you cant do what you want with it....Im really interested to see how this plays out, although it will be for many years

The difference here is OEM distributors and other companies that sell computers with windows on it not only pay for the OS/software, they ALSO pay MS to be a licensed reseller of Windows and Microsoft products... how much money IF ANY has Psystar offered Apple for the right to resell their OS?

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

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      591
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      75
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!