Multi-booting Mac Intel Developer Machines
ytsejam-ppc writes "Ross Carlson over at Jasbone.com has a great article up on how to install multiple operating systems on the new Intel based developer edition Macs. His particular setup triple-booted Mac OS X 10.4.1 (Intel), CentOS 4 and Windows XP. Just makes me drool."
Given these aren't production machines, this does not mean too much, especially given that these have a BIOS. There have been many suggestions that production Intel based Macs won't be using the BIOS.
Jumpstart the tartan drive.
...and this is easy since the Developer Transition Platform is just running a generic Intel motherboard, generic Intel video chipset, an Intel Pentium 4 660 processor with HT, and a standard Intel BIOS (NOT a Phoenix BIOS as has been incorrectly reported elsewhere), but what will really be great is when someone makes a Virtual PC- or vmware-like product (perhaps even one of those products themselves) that is a virtual machine that runs under Mac OS X that allows running essentially any x86 OS at near-full speed, side by side with Mac OS X, without having to reboot.
Since it will be running on x86 hardware, processor instructions do not have to be emulated: they can run natively at near-full speed of the underlying hardware.
Further, though Apple will do nothing to stop users from installing Windows on production Intel-based Macintosh systems, it's likely that the production systems will evolve beyond the generic hardware that makes the Developer Transition Platform. Apple itself has said, "Don't assume that what you see in the transition boxes represents what will be present in the final product." This means there may be additional specialized hardware for which Windows drivers and specialized support profiles will not be maintained by Apple. Of course, this isn't stopping anyone from making them, and Intel has said that Intel-based Macs will use commodity Intel processors, chipsets, and other support components, but it might not be quite as seamless as just popping in a Windows CD and installing (though it very well could be).
Let's also not forget that the production machines may not be - and likely will not be - using BIOS, rendering useless any such conventional PC multi-boot configurations. (But even with EFI or Open Firmware, there's no reason Apple couldn't maintain a robust multi-boot system.)
The point is that a virtual machine product could offer a supported configuration for x86 OSes, including Windows, Linux variants, etc., without the headache and hassle of rebooting into another OS. Sure, dual/multi-booting has benefits, and certainly this will be possible on even the production hardware, but most users would likely prefer a Virtual PC-like environment for running x86 OSes/applications without rebooting.
On this topic, one wonders if Microsoft will be the entity that releases this first. After all, they've already got Virtual PC for Mac, and Virtual PC for Windows (and Microsoft Virtual Server) is exactly this type of virtual machine product, albeit for Windows. On one hand, you can argue that for Microsoft, it's just another copy of Windows sold, so why should they care? But on the other hand, if they make a first-class VM product for Mac OS X that runs Windows (and other x86 OSes) seamlessly at near-full speed of the native hardware, it definitely assists in the sales of more machines designed primarily to run Mac OS X, which could be a poor strategic choice...
But even if Microsoft doesn't do it, let's hope someone like EMC does with vmware.
For more general information, see http://appleintelfaq.com/.
How is this a troll/flamebait? It's a logical comment, the number of us normal users who have or have access to the Developer Mac boxen is next to nil.
Your hair look like poop, Bob! - Wanker.
see... unrelated news: see...
Jeebus, this is a no-brainer. Obviously windows... the OSX code is all running under rosetta, unless someone has a nifty CS3 beta or something lying around. What would be more interesting is if someone who writes a cross platform win/mac software could test speed of their app across the two platforms after compiling for intel on OSX...
Make sure everyone's vote counts: Verified Voting
None of the OSX code is running in Roseta. Old PPC binaries for apps that haven't been ported yet is running in Roseta. Photoshop I would have to imagine will work on the release date, or near it.
No see that would at least make sense... ... the perfect choice for your nextgen desktop and laptops...
You know, go with the Pentium4
The fact that any sane person rather see a PentiumM over a 4 doesn't stop Apple from their random rampage into techtown...
If I wanted a p4 box I'd buy a p4 box and throw Gentoo on it and avoid the whole "pay Steve money" issue... oh wait, that's what I did...
Huh?
Word on the street says Apple's Intel-powered machines will use Pentium M based CPUs, not Pentium 4.
Intel has stated several times that Pentium 4 doesn't have a whole lot of life left in it, and their roadmaps show enhanced and muli-core Pentium M systems as the future. Plus of all of the Intel benefits Steve Jobs mentioned, most don't even apply to the Pentium 4 (performance per watt, bright future, etc).
I don't know why Apple is using the P4 for their developer systems, maybe because their Intel builds for the past 3 years used P4 rather than P3, Athlon, or PentiumM.
No, its what they told us WOULD be possible.
Oh my, this must be embarassing for you:
http://en.wikipedia.org/wiki/EM64TLOAD "SIG",8,1
Um, the GPL doesn't restrict the end user more, it restricts (if thats what you want to call it) people developing and extending the software.
By Ross Carlson and Joel Wampler
Quick Guide | Full Guide | Install OS X | Install Windows XP | Install CentOS Linux | Drivers
In this guide we'll take you through installing multiple operating systems on the Intel based Developer Macintosh machine. This guide was put together by Ross Carlson and Joel Wampler to hopefully get you through building a machine that can run every major operating system currently available. This guide takes about 2 hours total. Let's get started...
First there are a few things that you'll need:
Notes:
Quick Guide: - Return to Top
If you're like us and hate reading through pages of crap to get things done here is the quick version of what you'll need to do. We'll explain this step-by-step down below.
Hehe. ;-)
I nterface
For others who might really not know what it is, this is EFI:
http://www.intel.com/technology/efi/
http://en.wikipedia.org/wiki/Extensible_Firmware_
He said: beyond what the regular 64-bit pentium4 has. Both chips implement em64t the same way.
Obviously as developer platforms, these boxes bear no real similarity to the Intel based macs that will eventually go into production, but I'm hopeful that the ability to boot Windows on Intel macs may remain even through to production hardware. Obviously there may be issues regarding whatever bios-replacement Apple chooses to use on their hardware, but I'm sure they're also aware of the potential for dual booting macs between Windows and OS X. Whether this is something they want to embrace with their new platform (and I seem to recall Phil Schiller stating that there was no reason Windows couldn't run on an x86 mac) or whether it's something that they consider would 'taint' the Macintosh user experience remains to be seen.
This boot setup must be a dream for some people out there with a gaming rush who would love to be able to get the best of both worlds (although the mac mini has its logical place here) . I only hope this flexibility doesn't get wiped out in production hardware..
Business Voyeur
per the article: Other Device: There is also one of the Trusted Computing chips on the board - Windows Update will install the driver for that... sse3 and tpm are the reasons that mac os x/x86 will not run on anything other than apple devkits right now. apple's ATSServer is not compiled for i386 - with good reason: so that the 'rosetta' ppc translator is required. oah750 is 'rosetta', which has hooks to run correctly only through the presence of said TPM. executing ppc binaries manually results in a segfault. no tpm, no rosetta, no mac os x.
That particlar torrent is bundled with a trojan.
What I haven't seen is any reason why EFI is better than Open Firmware (better for everyone else, that is - obviously, it is better for Intel since they can control it). The Wikipedia article says that EFI mandates the use of FAT (and, presumably, the ancient creaky ought-to-be-obsolete DOS partitioning format).
Linux already can boot under OF (e.g. the PPC version of Linux), making that work under an x86 version of OF should be trivial. Loading a BIOS emulator under OF to boot Windows should also be fairly easy to do. Writing a bootstrap loader that implements OF, for old machines that want to boot an OS that only boots under OF, should also be feasible (see e.g. the OpenBIOS project.
>Currently, on every Mac sold, MS gets the revenue for a copy of Office.
Uhh, the version of Office that comes with MacOS X, last I checked, was a time-limited trial, and not a fully copy. You still have to purchase a full copy if you want Office. So this statement is false.
Microsoft Office is very much optional on the MacOS X platform.
-Z
(and, presumably, the ancient creaky ought-to-be-obsolete DOS partitioning format).
F AQ.mspx is a good link to what GPT is, and also how different versions of Windows supports GPT today. If Apple goes with EFI (strongly hinted at by Apple devs) and GPT, Windows XP 32 will not boot off this solution, however, 64 bit versions will. Given that most of Intels chips will be 64 bit by the time Apple ships consumer products, it looks like this should be fine.
No actually. It uses GUID Partition Table (GPT). http://www.microsoft.com/whdc/device/storage/GPT_
Dual booting doesn't interest me though, as it's a bunch of wasted time. Instead, I'm more interested in an OS X Apple Intel box that can run DarWine.
First of all, shipping Intel-based machines probably won't even be using the Pentium 4; but:
/
http://appleintelfaq.com/#7
What about 64-bit computing?
Apple has not forgotten about 64-bit computing, or x86-64. However, Apple is trying to make the initial phase of the transition as simple as possible. 64-bit is a requirement for systems utilizing more than 4GB of RAM, which will be a necessity for some applications in the future, and is currently possible on today's Apple systems; Apple knows 64-bit capability is a requirement.
http://www.macworld.com/2005/06/features/intelfaq
Does this mean Apple's abandoning its commitment to a 64-bit architecture?
We don't have any specifics yet, but it seems highly unlikely to us that Apple would turn its back on 64-bit chips. Intel offers 64-bit chips and it's almost impossible to conceive that Apple would move backward in this area.
"Don't assume that what you see in the transition boxes represents what will be present in the final product." -Dean Reece, Apple
If you wanted one, you could buy it for 1500 bucks. It costs 500 bucks to get into the developer program so you're eligible to buy one in the first place, and a thousand bucks for the machine itself. I've thought about it...
You can't 'BUY' one. For $1500, you get a year's select developer membership and you get to 'Lease' the machine. You'll have to return it by the end of 2006.