Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Intel Businesses Apple

First Look at Apple's Intel Developer Macs 770

xyankee writes "Think Secret is reporting that developers have started taking receipt of Apple's Intel-based Mac kits. Along with some specs and photos, the site reports that Windows XP installs without a hitch on the systems and that casually trying to install Mac OS X for Intel on a Dell doesn't work... yet..."
This discussion has been archived. No new comments can be posted.

First Look at Apple's Intel Developer Macs

Comments Filter:
  • Strategy? (Score:5, Interesting)

    by dsginter ( 104154 ) on Thursday June 23, 2005 @07:04AM (#12888017)
    the site reports that Windows XP installs without a hitch

    Perhaps this is part of the strategy? I wonder if they could run Windows on one core and OSX on the other.
    • Re:Strategy? (Score:5, Insightful)

      by hcdejong ( 561314 ) <`hobbes' `at' `xmsnet.nl'> on Thursday June 23, 2005 @07:07AM (#12888033)
      Probably not; you'd need some kind of arbitration, otherwise the cores would interfere with each other's communication to the rest of the system. A 'virtual machine' approach would be much easier to accomplish.
      • Re:Strategy? (Score:5, Informative)

        by Anonymous Coward on Thursday June 23, 2005 @07:30AM (#12888142)
        Intel's chips for 2006 should all have the 'Vanderpool' work in them, which improves hardware support for virtualization. This will make programs like VMWare, VirtualPC and Xen much faster.
        • Re:Strategy? (Score:5, Insightful)

          by InvalidError ( 771317 ) on Thursday June 23, 2005 @10:58AM (#12890247)
          Vander may have some performance issues though since much of the memory management is done in software.

          AMD pulled an ace on Intel with x86-64 and it seems AMD will also have the better deal on virtualization with more of it being transparently handled by hardware.

          To me, it seems Intel severely dulled its edge on the P4 anvil. I wonder how many years it will take for it to be solidly back on tracks... I am guessing 3-5 years as a minimum unless something truly ground-breaking failed to leak through the usual rumour channels.
    • Re:Strategy? (Score:3, Interesting)

      I would buy a machine that would allow me to run both OS natively w/o sacrificing/performance. And I believe that this would appeal to a great many Mac and PC owners. I hope that this will truly be the case, but somehow I doubt Apple will let their hardware get watered down in this fashion -
    • Just put wine on it (Score:4, Interesting)

      by nietsch ( 112711 ) on Thursday June 23, 2005 @07:28AM (#12888131) Homepage Journal
      Ok this may have been suggested before, but:
      If wine runs on all x86 unix-like OS's, and OSX is unix-like, will wine run on OSX-86? It would open up a very large market for apple without having to invest too much money. They will need to do some tricks to get it to use native widgets and stuff, but that's not impossible to do.

      The downside is that the better wine works, the better the adware/spyware works on it too. I am probably not the only one to infect my wine IE install with ad/spyware.

      What works for OSX will maybe also work for linux. There are already ABI's to make use of executables compiled for *BSD, so maybe OSX-86 binaries will run on linux soon too.
      (yup wishfull thinking and pie in the sky...)
      • by Megane ( 129182 )
        1) it's still going to use X-windows, not Quartz/Aqua
        2) did you read the article yesterday about Codeweavers support? Apparently the Wine codebase works great under Linux, but BSD support is regularly broken.
      • If Apple was counting heavily on Wine they'd have forked the project just like they did with KHTML. I suppose maybe they already did. We'll find out as soon as OS X86 is released.
    • Re:Strategy? (Score:5, Insightful)

      by pedantic bore ( 740196 ) on Thursday June 23, 2005 @07:32AM (#12888152)
      A simpler explaination is that Windows XP has already been ported to practically every x86 chipset and common peripheral, so it's no surprise it works.

      • I keep screaming, but no one is listening [blogspot.com]...

        That is the same exact same reason Linux will do so great on that new Apple hardware!!!!

        fsck you Dvorak, you are a hack
        • by moonbender ( 547943 ) <moonbender@@@gmail...com> on Thursday June 23, 2005 @09:25AM (#12889076)
          Yes, well, so what? Linux already works moderately great on current Apple hardware, and it works great on existing x86 hardware. Yes, you probably will be able to run Linux on the Apple/x86 hardware, which probably will be pretty "sexy" as far as x86 hardware goes. But being able to run Windows on that same hardware is a much bigger deal for most people. OS X already is a very capable Unix-like niche operating system - but it's not very good in some aspects that Windows is extremely good in, mostly this comes down to the application support.

          Or in other words: Hardly anybody cares about running Linux applications on an OS X platform because many Linux applications have been ported and run just as well on OS X. The same isn't true for Windows.
    • Re:Strategy? (Score:3, Informative)

      by PM4RK5 ( 265536 )
      The problem with doing this, maybe mentioned elsewhere, is trying to share hardware peripherals such as the network card, sound card, etc... among multiple operating systems running concurrently. If both operating systems try to initialize each peripheral, then one will randomly clobber the configuration set up by the other.

      It is not a problem of being able to run both concurrently on separate processors; it is being able to manage hardware resources (busses, graphics, peripherals, etc...) among operating
      • Re:Strategy? (Score:3, Insightful)

        by bhtooefr ( 649901 )
        First, I haven't seen a problem with MS Virtual PC running on a system using direct connection to the network. I'd be surprised if it WEREN'T two IPs, one MAC.

        Second, a simulated NAT could be done. So, the second OS has a different IP address, and doesn't directly touch the router, only the OS that eventually touches the router.
        • Re:Strategy? (Score:3, Interesting)

          by PM4RK5 ( 265536 )
          That's a bit different, because Virtual PC provides a layer of software between Windows and OS X. I'm pretty sure Virtual PC has two network configurations:

          1. Let both OSes share the same IP, same MAC.
          2. Put Windows behind a virtual NAT router on its own IP and own software-generated MAC.

          Either way, Virtual PC software sits between Windows and the OS X network stack. In the first case, Virtual PC handles corner cases where both OSes are trying to run services on the same port, etc... To the outside w
      • Re:Strategy? (Score:3, Interesting)

        by GweeDo ( 127172 )
        "Even more complicated would be using a single NIC to connect two operating systems to the same network. Unless someone came up with a clever solution, each OS would need its own IP address. However, routers and switches outside the computer would become immensely confused when a single NIC and a single MAC address belong to two IP addresses, since most routers/switches only have a one-to-one correlation between MAC addresses and IP addresses."

        Never had a single NIC in Linux bound to multiple IP's have yo
        • Re:Strategy? (Score:3, Interesting)

          by PM4RK5 ( 265536 )
          Well, I have, but I still had it set up to be 1 IP per NIC. Thanks for pointing that out, though; I'd never really seen that type of configuration, so I stand corrected on that point.

          Running two OSes still doesn't seem quite parallel to having Linux sitting underneath all those IPs to manage them, but apparently I don't quite understand how switches learn to direct packets. So... I still see problems on the machine trying to run two OSes, but I trust that you're right in saying that external switches/rou
  • by Anonymous Coward on Thursday June 23, 2005 @07:05AM (#12888019)
    A first look at Apple's Intel Mac (with photos)

    By Ryan Katz, Senior Editor
    June 22, 2005 - Apple's Intel-based Mac development kits have started trickling into developer's hands, Think Secret has learned.
    advertisement

    The Apple Development Platform ADP2,1, as the systems are officially designated, features 3.6GHz Pentium 4 processors with 2MB of L2 cache operating on an 800MHz bus with 1GB of RAM.

    The Intel systems run Mac OS X 10.4 Tiger identically on the surface as ordinary Macs, with the exception of a modified Processor System Preference (from Apple's CHUD tools) that allows the user to toggle Hyper-Threading on or off. Apple System Profiler includes a new line under Hardware listing CPU Features; for the 3.6GHz Pentium 4 this comprises a rather lengthy list of technical acronyms: FPU, VME, DE, PSE, TSC, MSR, PAE, MCE, CX8, APIC, SEP, MTRR, PGE, MCA, CMOV, PAT, PSE36, CLFSH, DS, SCPI, MMX, FXSR, SSE, SEE2, SS, HTT, TM, SSE3, MON, DSCPL, EST, TM2, CX16, and TPR.

    Apple's System Profiler reports the graphics card as an Intel Graphics Media Accelerator 800. Inside the Intel Mac, DVI support for the video card is provided by a Silicon Image Orion ADD2-N Dual Pad x16. Oddly, neither Silicon Image's Web site nor Google turns up much information on the latter card, the latter yielding a single link to a recent Dell support forum posting.

    The motherboard on the system is unmarked except for the word Barracuda. The system's internals are housed inside a case similar to Apple's Power Mac G5 systems but with a different configuration of fans.

    Running Windows; Mac OS X on other PCs

    Along with running Mac OS X, Windows XP installs without hitch on the Intel-based Mac, just as it would on any other PC, and booted without issue when installed on an NTFS-formatted partition. The only misbehavior sources encountered involved the video card. Initially, Windows refused to budge from an 800x600 setting on a 23-inch Cinema Display. Some prodding managed to get the screen to 1600x1200, but sources were unable to get Windows to take advantage of the entire screen.

    Apple alluded to developers at its recent Worldwide Developer Conference that Windows should be able to run on Apple's Intel Macs.

    As for installing Mac OS X on non-Apple hardware, attempts to boot from the included Mac OS X for Intel disc resulted in an error message on both a Dell and off-brand PC. The message states that the hardware configuration is not supported by Darwin x86.

    Sources have indicated that Apple will employ an EDID chip on the motherboard of Intel-based Macs that Mac OS X will look for and must handshake with first in order to boot. Such an approach, similar to hardware dongles, could theoretically be defeated, although it's unknown what level of sophistication Apple will employ.

    Also uncertain is whether the Intel-based development kits seeded to developers already feature the EDID chip or whether the installation disc contains a less sophisticated installation check that simply seeks out one particular hardware configuration--the one given to developers--and will not install on other configurations.
    • Darwin support (Score:3, Interesting)

      by lysander ( 31017 )
      As for installing Mac OS X on non-Apple hardware, attempts to boot from the included Mac OS X for Intel disc resulted in an error message on both a Dell and off-brand PC. The message states that the hardware configuration is not supported by Darwin x86.

      What if one tried installing on a machine with chipsets supported by Darwin x86, e.g. something already running Darwin? I'm curious if it's actually a Darwin issue or if it's some other check that the install does.

    • by CODiNE ( 27417 ) on Thursday June 23, 2005 @10:21AM (#12889686) Homepage
      Also uncertain is whether the Intel-based development kits seeded to developers already feature the EDID chip or whether the installation disc contains a less sophisticated installation check that simply seeks out one particular hardware configuration--the one given to developers--and will not install on other configurations.

      I think the 2nd option is more likely. It's exactly what Apple has been doing with OS X for years. When you buy a Mac you get an install CD which is exactly like any other except each model comes with a "supported hardware" check as it installs. The eMac install will not work on a Mac mini, nor the iBook install on a Powerbook, etc... They all have a list of chipsets / CPU's and other hardware built in that they use to identify which system it's running on. (That is, assuming you don't have OF as these x86 Macs won't) All Apple has to do is keep doing what they've always done and you're pretty much locked into Apple hardware, I suspect they'll simply include drivers for their own chipsets and motherboards and tada... everyone is already locked out. There's no need to add extra hardware components simply to identify it as a Mac when Apple is the only one using a certain Mobo.

      -Don.
  • by Anonymous Coward on Thursday June 23, 2005 @07:05AM (#12888020)
    Does the reality distortion field still work?
  • Leaks? (Score:3, Interesting)

    by wiggly-wiggly ( 682254 ) <wigglywiggly@gmail.com> on Thursday June 23, 2005 @07:05AM (#12888021)
    Now that Think Secret has confirmed that developers have the Mactel machines, will it only be a matter of time before OS X leaks out onto the Internet? Perhaps the previous stories were a little premature, but as soon as the protection mechanism on these machines is understood, it's only a matter of time.
  • so.. (Score:4, Funny)

    by isecore ( 132059 ) <isecore@i s e c o r e.net> on Thursday June 23, 2005 @07:05AM (#12888023) Homepage
    where's the torrent for OSX Intel Edition?
  • Can't decide (Score:5, Informative)

    by wchin ( 6284 ) on Thursday June 23, 2005 @07:06AM (#12888027)
    I worked one over at WWDC for 2 hours... our stuff doesn't need six or 9 months to port, as we mostly have Java or Cocoa Obj-C code. However, we do need it for a short period of time for testing. It would be nice to be able to ARD into a Macintel for testing, but $999 for a 1.5 year lease is a bit steep when we won't be able to effectively use the box for very long.
  • Driver Support (Score:4, Insightful)

    by Bob Gelumph ( 715872 ) on Thursday June 23, 2005 @07:08AM (#12888034)
    There might be some simple (or complex) mechanism for locking the OS to the Apple/Intel system, but even if this is broken, who is going to write all of the drivers for that Dell that everyone keeps talking about?
  • by Ath ( 643782 ) on Thursday June 23, 2005 @07:08AM (#12888036)
    I will say it before someone else does:

    Nowhere did Apple say x86, they just said Intel chips! So maybe there is a brand new chip that Apple will use from Intel.

    Now the truth: Apple did say x86 and that, if you are interested in which specific Intel x86 chips Apple will use, check the Intel CPU roadmap for mid 2006 to get an idea.

    Just trying to be efficient...

  • OS X on a Dell (Score:3, Interesting)

    by DenmaFat ( 704308 ) <denmafat@gmail.com> on Thursday June 23, 2005 @07:09AM (#12888039)
    Other versions of Darwin will run on that Dell. I'm not familiar with OS X innards, but couldn't someone figure out how to replace the handshake-enabled Darwin with the Dell-friendly bits?
    • Re:OS X on a Dell (Score:5, Insightful)

      by numbski ( 515011 ) * <numbskiNO@SPAMhksilver.net> on Thursday June 23, 2005 @07:20AM (#12888100) Homepage Journal
      People people people....

      We're all unix geeks here, right?

      **crickets**

      Okay, well even if not....

      Go to the Darwin site. Download Darwin for x86, install it. Ta da! We have the BSD Subsystem. :)

      Okay, get your shiny new developer mac, place it side by side with your Darwin machine. Check the passwd file, the passwd entry in netinfo, and groups. Make sure the uid's and gid's generally match up.

      Export for nfs from you dev mac:

      / --alldirs --maproot=0

      Now, mount that someplace on your darwin boxen.

      Use cp -pr anything of interest to the darwin box. I would take special note of anything in /etc/rc.

      Kick the darwin box.

      I filesystem comparison between a clean dev box and a clean Darwin box might me useful, diffs on text files to go along with it.

      Provide me or any good hacker that, and we'll have an installer out in no time. ;)

  • by mpontes ( 878663 ) on Thursday June 23, 2005 @07:11AM (#12888053)
    Can't wait until someone hacks the x86 version of Mac OS X to run on non-Mac. However, I suppose the biggest problem wouldn't be the "Mac-only" protection itself, it would be to find OS X drivers for your average PC hardware. Well, I suppose you could make many BSD drivers work under the x86 Darwin with little tweaking, but I might be wrong.

    Can't wait, though. Triple boot PC! Or if a decent OpenSolaris distro comes out, tetra-boot! After that, no one on Slashdot can trash my OS anymore...

    • Re:OS X on a PC... (Score:3, Informative)

      by 0xABADC0DA ( 867955 )
      I suppose you could make many BSD drivers work under the x86 Darwin with little tweaking, but I might be wrong.

      Mac OS X has a completely different, subset of C++ driver system called IOKit. They did this because the *BSDs had basically no ability to change power states, and writing new drivers was time consuming (now you subclass a similar driver that does not of the work already).

      So, no, it would take a complete re-write to get normal BSD or Linux drivers into OS X.
  • OS X on a PC (Score:5, Insightful)

    by LittleGuernica ( 736577 ) on Thursday June 23, 2005 @07:14AM (#12888068) Homepage
    No doubt that they will eventually get OS X to work on a generic PC clone. It will probably take some serious work around and then you have the driver problem. nobody can get an airport extreme to work on a mac right now with any version of linux, so driver's are goign to be a problem.

    But since Apple won't officially allow it to install OS X on any other computer but a mac, nobody will ever be able to sell a computer with OS X pre-installed. So it will enver get mainstream and i'm sure Apple will have few sleepless nights because a few geeks have it running on their generic PC box.
    • Re:OS X on a PC (Score:3, Insightful)

      by porcupine8 ( 816071 )
      Wow, somebody actually talking some sense. The reason Windows has spread like pirated wildfire isn't because people are downloading illicit torrents. It's people borrowing the CD that came with their friend/relative/neighbor's new computer when it's time to upgrade instead of buying a new one themselves. Heck, I did the same thing to upgrade from OSX 10.1 to 10.2.

      You'll never be able to do that with a Mac, unless Apple specifically decides to let you. If my mom wanted to switch to OS X, it would never oc

  • It sez... (Score:3, Insightful)

    by da ( 93780 ) on Thursday June 23, 2005 @07:15AM (#12888073)
    "Windows XP installs without hitch" but it also says "Some prodding managed to get the screen to 1600x1200, but sources were unable to get Windows to take advantage of the entire screen." Isn't it unlikely they'd be keen to make it work, given that if the hardware's was any good and priced competitively, people would buy them and run Windows ?
    • Isn't it unlikely they'd be keen to make it work, given that if the hardware's was any good and priced competitively, people would buy them and run Windows ?

      I doubt Apple would care too much. They make money selling hardware. If you bought an Intel Mac just to run Windows on it, it's your loss, not Apple's.

      Even so, Apple probably won't do anything to make it easy for those who want to run Windows on the MacIntels. They've said that they won't prevent, it either.

      It's probably simply not an issue.

      The

  • Coral Cache (Score:4, Informative)

    by cr3ative ( 881393 ) on Thursday June 23, 2005 @07:27AM (#12888127) Homepage
    Looks like the server is groaning already, so here:

    http://www.thinksecret.com.nyud.net:8090/news/0506 intelmac.html [nyud.net]
  • by jht ( 5006 ) on Thursday June 23, 2005 @07:31AM (#12888145) Homepage Journal
    You know, outside of a few Slashdotters who desperately want to run OS X on their pimped-out x86 boxes, there's probably not a lot of people who give a darn about this. Apple makes Macs, and as long as they provide a reasonably complete spectrum of systems across the price band, there's going to be zero measurable demand to defeat Apple's tying and install OS X on a generic PC. Zero. The biggest reason Mac cloning worked in the market for a few years last decade was that Apple wasn't providing the systems that the Mac marketplace wanted to buy. Even then, it cost Apple a lot more money than they ever expected it to, because even with the licensing fees it didn't make up for the lost hardware margins. Apple needs a lot more base market share before they can stop worrying about cannibalization.

    Sure, somebody'll figure out a way to do it - every DRM scheme devised thus far has been cracked, pretty much - but what do you get after cracking OS X? You get a unsupported OS on your PC that may or may not work right with the combination of cards, chipset, and BIOS you happen to have. Do people really think that there's going to be any enterprise demand for that? Really?

    Bottom line: Macs are Macs, PCs are PCs, and despite the change in architecture the twain are not going to meet any time soon. Stick to Windows, Linux, or xBSD on your generic PC, and run OS X on your Mactel. You can probably expect Apple to give up a little bit of their price delta now that the hardware is directly comparable (and the hardware superiority image is gone), but not all of it - after all, Apple puts a lot more engineering into their boxes than the typical PC vendor does. And when you're running your Mactel, you can look forward to emulation that's finally less crappy than what Virtual PC gives you. Yippee!
    • there's going to be zero measurable demand to defeat Apple's tying and install OS X on a generic PC. Zero.
      If you mean legitimate market demand sure there'll be no demand, mainly because it'd (probably) be illegal to circumvent the protection.
      But every hacker/hobbyist/etc. and their uncle will be trying to get it running on their clone pc, ASAP.
      Unsupported OS? you mean like the millions upon millions of copies of windows?

      • That's pretty much my point - the Slashdot market is, despite what we tent to think about ourselves, not a really significant market on the scale of what the Apples and Microsofts of the world care about. Sure, they'd like to be loved by the geek crowd, but it's just not a priority. If a few thousand alpha nerds run OS X on their Asus mainboards, it's not even a drop in the bucket to Apple.

        And remember, Windows may not be supported very well, but it's designed and qualified to run on any system that meet
    • Better yet, don't throw money away on a mac. Throwing thousands of dollars at a crippled PC isn't worth it for one operating system.
  • by amichalo ( 132545 ) on Thursday June 23, 2005 @07:33AM (#12888158)
    This article [osopinion.com], which is an opinion piece, brings up some insightful benefits of Apple reinvigorating the "Red Box" project to allow full compatibility between OS X and Windows apps.

    Seems to fit with this whole Intel dev edition story.
    • by TheRaven64 ( 641858 ) on Thursday June 23, 2005 @07:56AM (#12888290) Journal
      I'd be more interested in them reviving Yellow Box. Use the Mac as a development platform for deployment on Windows. If they can encourage Windows developers to use Macs (or even Yellow Box on Windows) then it suddenly become just a matter of a recompile to produce native Mac apps, which could be a huge benefit for OS X adoption.
    • Y'know, I was waiting for someone to mention this finally.

      The "Red Box" was real, at least on OpenSTEP for x86. I believe it was WWDC 2000 when Apple engineers (Avi Tevanian himself?) showed Quake running on OpenSTEP.

      Granted, Windows has changed considerably since then. But a built-in virtualization environment for other Intel-based OSes would shake up the market drastically.

      Sadly, pissing of MSFT is not a viable option for the AAPL business plan. But if I needed Windows, and could get Red Box, I know

  • Hardware style (Score:3, Insightful)

    by Winterblink ( 575267 ) on Thursday June 23, 2005 @08:40AM (#12888666) Homepage
    One of the things I thought was really nifty about my iMac when I bought one a few months ago was how the inside looked. Anyone who's seen the interior of any Mac will tell you the layout of the hardware, and the hardware itself, is pretty spiffy looking.

    Now I know the pictures in TFA are of a developer's kit, but I'm hoping the hardware for the release models looks a hell of a lot better than that. It's entirely disorganized, especially the cabling (when compared to current Mac models). I'm hoping this isn't a side-effect of the Intel switch.

    Admittedly this is a bit of a silly gripe, but Apple's philosphy to date has to been to have a very definitive style for their systems, for both their hardware and software. I'd hate for them to become just another PC hardware supplier with a nifty OS.
  • IP to share (Score:3, Interesting)

    by unconfused1 ( 173222 ) on Thursday June 23, 2005 @08:53AM (#12888792) Homepage
    I think that a lot of people have forgotten that Intel didn't really have a plan to get anywhere. Shrinking the process doesn't buy you the world, and that was all they were doing.

    Intel has ditched their own 64-bit platform in favor of AMD's, they have essentially reached many material limits in their process, they backpedaled to the PIII for the current Celeron and Pentium M designs, and their fake-dual-core designs are pretty lackluster also.

    Apple has problems with IBM advancing the PowerPC and producing enough of them to give Apple a very good image in the processing power area. Sure...the PowerPC might have a lot more room to grow (and other such arguments), but if you can't get them fast enough for demand...you have a problem. And with Microsoft, Nintendo, and Sony looking to the 970 and the Cell for their new consoles...supply wasn't looking better for Apple.

    Intel is gaining new life with dual and quad-core designs that Apple has property rights over. Intel is also getting new VPU designs. Lo and behold they have already announced new processors with some of these design changes in them, and I bet Apple will use them in their new machines.

    Apple get a product line that doesn't have the shortcoming concerning clock-speed envy. They get Intels successful marketing. And Apple gets a company that can meet processor supply demands. In addition Apple has a very smooth transition plan with fat-binaries for new applications, and Rosetta to run old binaries on the new systems.

    They have obviously had this on the back burner for a long time. I personally think this is win-win for both Intel and Apple.

    And additionally for us consumers and professionals, we may get a slightly cheaper machine...but will definitely get lower cost items like video cards, controllers, etc. that don't have to have special firmware for PowerPC platform.
  • Apple/Intel FAQ (Score:5, Informative)

    by daveschroeder ( 516195 ) * on Thursday June 23, 2005 @09:19AM (#12889023)
    http://appleintelfaq.com/ [appleintelfaq.com]

    What did Apple announce at the Apple Worldwide Developers Conference (WWDC) on June 6, 2005?

    Apple announced that it is transitioning from PowerPC processors provided by IBM and Freescale (formerly Motorola) to x86 architecture processors from Intel. The first Intel-based Macs will ship before mid-2006, and the transition will be complete by the end of 2007.

    Where can I find out more official information about this announcement?

    Apple press release [apple.com]

    Intel press release [intel.com]

    WWDC keynote address [apple.com] (Transcript [com.com])

    Why did Apple make this change?

    The following scenario likely contributed to this decision:

    IBM has been unable to meet its performance commitments for the PowerPC 970 family (G5) processors. In mid-2003, IBM promised 3 GHz G5s to Apple by mid-2004. As of mid-2005, 3 GHz G5s are still not available, over two years after the initial announcement, and over one year after the promised delivery.[1 [eweek.com]]

    Meanwhile, Microsoft has announced that IBM will make 3.2 GHz triple-core G5 derivatives available to Microsoft for Xbox 360.[2 [com.com]] IBM is also concentrating efforts on chips for Nintendo Revolution and Sony PlayStation 3.[3 [sci-tech-today.com], 3.1 [investors.com]] With IBM concentrating on expensive high-end server class processors and the console and embedded markets, and with Apple at less than 2%[4 [usatoday.com]] of IBM's PowerPC business, it was clear IBM's priorities were focused elsewhere.

    Apple is also less than 3%[4 [usatoday.com]] of Freescale's PowerPC business, with Freescale focusing on embedded, communications, and automotive markets. The priorities of IBM and Freescale do not coincide with performance and other needs of the traditional desktop and portable computing marketplace.

    What has Apple done to prepare for this transition?

    Apple has been publicly maintaining the core OS of Mac OS X, Darwin [apple.com], for both PowerPC and x86 platforms since the release of Mac OS X. Internally, Apple has been secretly maintaining Mac OS X in its entirety and all Apple applications for both PowerPC and x86 for over 5 years, since before Mac OS X's public release.[5 [cio-today.com]] Mac OS X's predecessors also ran on x86.

    Apple has made available Xcode 2.1 [apple.com], which adds the capability of creating PowerPC/x86 universal binaries [apple.com]. Xcode 2.1 can be used on either PowerPC or x86 systems to create universal binaries. Application developers already using Xcode in most cases need only recompile their application with an additional checkbox adding x86 architecture support.

    Apple has also licensed[6 [com.com]] QuickTransit [transitive.com] from Transitive Corporation [transitive.com] for Rosetta, a realtime binary translation system to support PowerPC binaries seamlessly on x86 hardware. The current performance of Rosetta
    • by LionMage ( 318500 ) on Thursday June 23, 2005 @06:39PM (#12895767) Homepage
      This FAQ is generally good -- it assimilates a lot of information found elsewhere on the web. However, it contains some inaccuracies.

      Meanwhile, Microsoft has announced that IBM will make 3.2 GHz triple-core G5 derivatives available to Microsoft for Xbox 360.
      Actually, the Xenon processor in the Xbox 360 is not a G5 derivative at all, though it shares some pedigree in common with the G5. Each Xenon core most closely resembles the PPE from the Cell processor. The similarity between the G5 and the Xenon core is that they both support the PowerPC instruction set and they both are 64-bit capable. That's about it. The Xenon cores support SMT, whereas the G5 does not. The Xenon cores also lack out-of-order execution logic, which the G5 possesses. You can find out more about Xenon at ArsTechnica. [arstechnica.com]

      The PowerPC processor included the capability to emulate 68K instructions, allowing almost all 68K applications to run.
      This is false. The PowerPC can't emulate the 680x0 instruction set on its own; the early PowerMacs were shipped with a sophisticated piece of emulation software which allowed "context switching" between running PowerPC native code and 680x0 code. (You may have heard the term CFM, or Code Fragment Manager.) This facility was necessary because many Mac toolbox routines had not been rewritten in PowerPC-native code, and many libraries and other pieces of the OS were similarly only available in 680x0 code. In fact, some toolbox routines were supplied in both PowerPC versions and 680x0 versions, because there were cases where emulated 680x0 code needed to call upon a toolbox routine, and the context switch from emulation to native PowerPC and back again was worse than just running the toolbox routine under emulation.

      Anyway, bottom line, the PowerPC never had built-in 680x0 emulation. The design win with PowerPC was that it could be made with the same bus that the 680x0 processors used, allowing Apple to retain much of its existing hardware designs. It should be noted that before the PowerPC was decided upon, some folks wanted Apple to go with the Motorola 88000 series of chips -- these were Motorola's first stab at RISC, and had the virtue of being pin-compatible with the 68000 series. I've seen some Omron workstations that used 88000 processors, but I don't think they ever got a lot of traction in the general market. At least one history of the Mac that I've read indicated that the 88000 was seriously considered within Apple before PowerPC was decided upon.

      Support is eventually dropped for all older hardware in the current OS (for example, for PowerPC G3-based systems).
      Not all G3-based systems are unsupported in Tiger. I believe G3-based iBooks are still supported, for example. Of course, "supported" doesn't mean you get all the eye candy, but that's true for some lower-end G4 systems as well.
  • by Anonymous Coward on Thursday June 23, 2005 @09:28AM (#12889116)
    Hold the delete key down at boot. It's a Phoenix Bios!

    Now if you want to get really freaky, go into the 'boot' menu and turn off the quick and silent boot options. This will display the bios information at boot...

    The bios at boot will display the same serial number that is on the chasis sticker, and another secondary id string. It also indicates the system as a Apple Transition Dev system.

    Now on the first time you boot it, for 2 seconds you will see 'Darwin x86' on the screen - but we all figured that out all ready.

Some people manage by the book, even though they don't know who wrote the book or even what book.

Working...