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


Recommended Posts

What's your point? Of course they use the same gpu/cpu/memory, but you can't count out the external hardware of an Apple computer. The appeal of a mac doesn't come from its performance, but from its design and operating system--that's it.

My point is performance and not Aesthetics.

Leopard is by far faster than Tiger. Improvements in Spotlight, Finder, application caching, disk i/o, and optimization. Consider Siracusa from Ars: http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/15

Giga, while it may be true that some users will see a performance improvement, that is not the case for all macs. If Leopard was faster than Tiger on the same hardware, then they wouldn't completely alienate entire models of Macs. There are many macs that run Tiger quite well, but are not capable of running Leopard. IIRC, Apple themselves said that one of the reasons why they are not allowing older macs to run Leopard was because it would run too slow on them.

I have seen macs running Leopard quite sluggishly, and if Tiger was installed, it would most certainly run faster.

I hear a lot of people say that Apple's hardware has a lot of quality. Well, as with everything, your mileage will vary. I personally own an iBook G3 that has logic board issues. There is literally nothing that can be done to fix it. The case is all warped, because I had to place a large stint over the GPU (that's the supposed fix for the iBook G3 Logic Board issues). And now, the current model of MacBook Pro's are having an issue with vertical striping on the LED displays: http://discussions.apple.com/thread.jspa?threadID=1627678 That link is the continuation to the first thread regarding that issue. The first thread was closed because it got too big (seriously). The MBP is not the only notebook on the market with LED displays, but is really the only notebook on the market that exhibits the issue, and it's also one of the most expensive notebooks on the market. And so far, after being on the market for almost 7 months, Apple has done virtually nothing to resolve the problem.

I would personally love to purchase a MacBook Pro because of the sleekness of the hardware, and the ability to run OS X and Windows side-by-side. However, given all the problems people have had with their MBPs, I don't want another iBook G3 on my hands. That, and the fact that I can currently buy a Dell M1530 with better specs and pay less for it.

The general consensus is that if you have a >1ghz G4 with 1Gb ram or above, upgrade it to Leopard and you will notice speed improvements in some areas. (I can't imagine how anyone can stand the Tiger spotlight these days where indexing takes ages and results aren't instant) Yes, some things might get a bit more beachballs or dock bounces--but that's attributed to more aggresive disk caching and such.

There's no doubt at all that some of the older macs won't run Leopard well (thus the limitation to install it on slower G4s and G3s), but that's not to say it won't make the more recent G4s and higher run faster based on several improvements in the system from 10.4. If anything would make it run slower, would be macs with lower end GPUs such as low end iBooks or eMacs. Hard drive size can play a big factor as well--especially the ones with 30 and 40gb drives where a Leopard install with full printer drivers can take up 1/4 of it.

As for the the MBP issue, consider the amount of Macbook Pros sold each day, then the amount of lemons reported. People often report issues when there is a problem, but not when it is fine. I wouldn't have any hesitation recommending you buy one even with the LCD issue that some are having--several of my colleagues are running the latest 10.5.4 flawlessly on their MBPs.

Though I would sitll hold off because new models are coming soon. ;)

Dont you have to install Bootcamp before you can install any Operating system, dont you have to have osx/bootcamp installed to boot to the os?

If Windows natively supported EFI without Apple having to provide workarounds, you probably wouldn't need bootcamp.

SP1 x64 supports EFI, but doesn't work with the EFI on Macs (Mac EFI is 32Bit, Vista x64 SP1 requires a 64Bit EFI)

And even then, I screwed up with Bootcamp, you don't need it to boot Windows, the system out of the box can boot Windows (Since they provide BIOS emulation in EFI), Bootcamp is a partition manager (And I think does a driver disk)

The general consensus is that if you have a >1ghz G4 with 1Gb ram or above, upgrade it to Leopard and you will notice speed improvements in some areas. (I can't imagine how anyone can stand the Tiger spotlight these days where indexing takes ages and results aren't instant) Yes, some things might get a bit more beachballs or dock bounces--but that's attributed to more aggresive disk caching and such.

There's no doubt at all that some of the older macs won't run Leopard well (thus the limitation to install it on slower G4s and G3s), but that's not to say it won't make the more recent G4s and higher run faster based on several improvements in the system from 10.4. If anything would make it run slower, would be macs with lower end GPUs such as low end iBooks or eMacs. Hard drive size can play a big factor as well--especially the ones with 30 and 40gb drives where a Leopard install with full printer drivers can take up 1/4 of it.

As for the the MBP issue, consider the amount of Macbook Pros sold each day, then the amount of lemons reported. People often report issues when there is a problem, but not when it is fine. I wouldn't have any hesitation recommending you buy one even with the LCD issue that some are having--several of my colleagues are running the latest 10.5.4 flawlessly on their MBPs.

Though I would sitll hold off because new models are coming soon. ;)

Well the imac I was using was a 400mhz g3 with 512 mb so I guess that explians why it was slower than tiger.

If Windows natively supported EFI without Apple having to provide workarounds, you probably wouldn't need bootcamp.

Intels "Standard" EFI which was developed with the help of Microsoft in 1999 includes a feature to emulate a BIOS which then Apple then removed to restrict the platform to OSX only. It is only after early adopters of the Intel Macs and The News Media that Apple decided to put the BIOS emulation back into their modified EFI with bootcamp

I have a Gateway from 2003 that has EFI and will run any Windows OS you throw at it

(It was always meant for the switch to 64-bit but I believe that plan went down with the Itanium)

What does my original quote have anything to do with performance? I was commentating on the business model of Apple and Microsoft?

When allot of people hear the word hardware, they are thinking of the hardware that drives the performance of the system and not the attached hardware like printers and monitors. So I just misunderstood what you were trying to say.

The "experience" everyone is talking about is being able to pull their notebook out everyday and have everything work so seamlessly, they don't even have to think about lots of things that you would have to with a windows notebook. For example, with a pc notebook, if you had a wireless mouse, you would have to turn it on and off every time you put your notebook away or took it out. With a mac, every time you sleep or wake your notebook (if you have a mighty mouse), it turns the mouse on and off for you. Also, I have been AMAZINGLY impressed with how easy and quick the sleep is on my Macbook. Shut the lid and its already sleeping. Open it up, and it's already awake and ready to use.

So... If I do a web search for "mac problems" I will get zero hits?

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

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • 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
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!