Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

No EFI Support for Vista

Posted by CowboyNeal on Fri Mar 10, 2006 04:25 AM
from the apples-and-oranges dept.
DietFluffy writes "Microsoft revealed today that it will not support EFI booting for Windows Vista on its launch. The news will be a shock for owners of Intel Macs who had hoped they would be able to dual-boot between Windows Vista and OS X. Intel Macs only support booting via EFI."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Aokubidaikon (942336) on Friday March 10 2006, @04:28AM (#14889338) Homepage
    "If you won't let us boot yours, we're not gonna let you boot ours either! Hehehe!"
    • by stunt_penguin (906223) on Friday March 10 2006, @05:30AM (#14889531)
      Yea but what I don' get it what booting has to do with Electronic Fuel Injection.. WAIT A MINUTE....!
      • by MrNiCeGUi (302919) on Friday March 10 2006, @06:03AM (#14889616)
        Bingo! you win the prize for the most clueless comment of the day.

        Emulation is hard. The Wine project has been started 13 years ago, and they still support only a handfull of applications. Apple has only been able to emulate their past architectures because they owned or licensed all the specifications for them. To emulate Windows would mean to use reverse engineering, which is a whole different ball game, and to expose themselves to potential lawsuits from Microsoft.

        Plus, if there's anything to be learned from the whole OS/2 experience it's that perfect emulation of your rival's platform brings no market advantage.

        In my opinion, Apple would just use a virtual machine and tell users to run Vista in that. For them, it is the perfect solutions. People would still have acces to their strategic apps on their platform, and there would also be a great incentive to port them to run natively on MacOS.
        • One little error. (Score:5, Informative)

          by Jerk City Troll (661616) on Friday March 10 2006, @07:17AM (#14889797) Homepage

          Emulation is hard. The Wine project has been started 13 years ago, and they still support only a handfull of applications.

          I hope you weren't implying that Wine is an emulator because Wine Is Not an Emulator [winehq.com]. ;)

        • by klubar (591384) on Friday March 10 2006, @10:56AM (#14890931) Homepage
          Thus you could turn your mac into a really expensive PC.

          Step 1: Buy a mac
          Step 2: Buy emulation software
          Step 3: Buy an MS operating system
          Step 4: Buy applications to run on th MS OS
          Step 5: Enjoy the good looks and positive karma of your new mac

          • And WINE's progress is a poor example. Part of the reason for its slow pace is that there hasn't really been as strong a need for it as there is today. Until Intel-based Macs appeared, there was no real compelling need for WINE - it ran on x86 boxes that could boot Windows anyway. Now we have x86 boxes that can't boot Windows, WINE's API-level Windows app support is a somewhat interesting for Mac users.

            I think this is an excellent point that can't be said enough.

            WINE suffers, at least right now, from a rather limited appeal. The only people I've run into who use it regularly, are pretty hardcore Linux users who are adamant about not wanting to reboot into Windows in order to use some app, or run a game. I've played around with it (well, Cedega anyway) enough to get WoW working on a Linux machine, because I bought it bare-bones and wasn't about to buy a Windows license just for one game.

            But it's a limited market of people who have a regular Intel PC and won't just reboot in Windows.

            There is going to be a huge untapped market for a MacWINE variant, that will run Windows applications on the new Intel Macs. I think this market is far in excess of the existing Linux-user demand, and Mac users won't hesitate to pay for a product that does this elegantly and well. In short, there's a big space right now for a company to jump in (maybe Cedega would license their codebase, if the company was scared of the GPL) and produce a commercial product for running Windows applications on Mac.

            I think you could probably sell a product like that, even if it only ran a few PC-only applications (but if it ran those applications well and you clearly advertised which it would run) for upwards of $100 a seat. A lot would depend on packaging and support -- I don't think that Cedega-style forums are going to cut it for a Mac-using audience.

            If there are a dozen groups possibly working on something like that right now, as you suggest, they're doing it damn quietly. I suppose we're still pretty early in the Intel transition yet, though.
      • by Proteus (1926) on Friday March 10 2006, @11:44AM (#14891293) Homepage Journal

        According to the w3schools site [w3schools.com], As of Feb2006, market share is approximately:

        Windows : 89.8%
        Linux.. : 03.4%
        Mac.... : 03.6%

        Most notably, the overall share of Mac and Linux have grown steadily while Windows has shrunk at about the same rate. I agree that I doubt MS decided not to support EFI based solely on the new Intel Mac strategy, but marketshare analyses are not the way to point it out.

        The point comes down to this: MS would benefit by allowing Mac hardware to boot Windows. A copy sold is a copy sold. Besides, MS already sells a Mac version of Virtual PC with a Windows license for hardly more than just a copy of Windows itself, so it's clear that they have no issue with people running Windows on Mac hardware.

        I'm more willing to bet that EFI support is just one more vaporware feature that MS ran out of time to implement for Vista. Every time I hear of yet another Vista feature being axed, I have to wonder if anyone will care about Vista when its released -- what will it actually do for us?

  • by liangzai (837960) on Friday March 10 2006, @04:28AM (#14889340) Homepage
    Well, Microsoft has always been a slow adapter of everything. USB was late, even a GUI came late. There is still support for floppy disks... no surprise here.

    This is good. I don't want to see Macs contaminated with 10 GB of installed rubbish.
    • by lmlloyd (867110) on Friday March 10 2006, @06:52AM (#14889729)
      I hate to rain on you MS-trashing party, but Microsoft already DOES support EFI. EFI is, after all, a PC technology, developed for the Itanium, not something Apple designed for their systems. The summary of the article is quite simply wrong. Vista will support EFI in the 64-bit version, for 64-bit chips, this being a technology designed for a 64-bit processor. In fact 64-bit XP and 2003 ALREADY support EFI. What will not be supported is EFI on 32-bit chips, since no one is doing that except Apple.
          • by Solosoft (622322) <chris@solosoft.org> on Friday March 10 2006, @07:28AM (#14889826) Homepage
            Ive flashed my bios on both Asus boards in my house from windows without a hitch. It was actually quite easy

            1. Run Program
            2. It automagicly Downloads what's needed
            3. Click Okay
            4. Wait 10 seconds
            5. Profit !!! ???
            One of the asus boards was a P2B Slot1 (PII 350 100MHz Bus) and a A8V 939 (Athlon64 3000+ @ 200MHz FSB) and ive seen not an issue. Windows won't magicly crash during those 10 seconds and I doubt it really will or else asus won't let you flash from windows.
            You guys really gots to get out of the "Windows is unstable" crap. This isn't Windows 98 ive seen desktop XP systems get months and months of uptime without any problems.

            For fun I decided to run windows vista and it seems to already be using EFI because it makes a "Boot" directory in both Windows Drives (XP MCE and Vista) and an "EFI" directory containing fonts. So there going to remove the feature from the beta ??

            Solosoft
  • I'm not at all excited by the idea of shutting down my computer just to use another operating system.

    Anybody who's used a virtualization product like VMWare knows what I'm talking about. That is where it's at.

    You can run another operating system in a window without leaving your current OS. It's not an emulator in any traditional sense of the word; things run at (or a few percent shy of) native speed. The only downside is that you need enough RAM to run both operating systems simultaneously in a comfortable fashion, but 2GB of RAM is under $200 these days.

    I'm going to buy an Intel Mac as soon as VMWare releases an OSX version of VMWare or an open-source implementation reaches that level of quality (there are some strong contenders). I'm willing to put down the cash to run Windows on an Intel Mac, but dual-booting isn't even part of the equation.
    • by earthbound kid (859282) on Friday March 10 2006, @05:15AM (#14889484) Homepage
      Amit Singh and his friends at IBM got XP running under VMWare in Linux on an Intel iMac [osxbook.com]. As he says, "To anybody who has used Windows XP under Virtual PC on the PowerPC version of Mac OS X: you will simply be blown away by how fast Windows XP runs under VMware on the new hardware." So that's good news. Now someone just has to make it work under OS X directly.
      • "XP running under VMWare in Linux on an Intel iMac..."

        Wow. Are they sure they can't get DOS and OS/2 involved in that process somehow?

        • > > "XP running under VMWare in Linux on an Intel iMac..."
          > Wow. Are they sure they can't get DOS and OS/2 involved in that process somehow?

          Sure, no problem. All you need to make that work is an EFI-emulator written in Java; there's already an x86 emulator written in Java, so then we hook that up together with the EFI emulator and basically what we have then is an Intel-Mac emulator, which runs on the JVM. The JVM is available for OS/2, so we'll have XP running under VMWare in Linux on an emulated Intel iMac running on the JVM under OS/2, running in VirtualPC on OS X, which is running on PearPC under FreeBSD, which is running under bochs on DOS in domain2 on Xen. That'll be much faster and more convenient than dual-booting, since at least three of those emulation layers promise near-native execution speeds.

          HTH.HAND.
        • by CdBee (742846) on Friday March 10 2006, @08:50AM (#14890135)
          start linux, start vmware in linux, start XP, start vmware in XP, start linux on vmware on xp on vmware on linux, then you can unplug the iMac and carry it off leaving the operating syatems hanging in mid-air in an endlessly self-supporting loop.
    • I'm not at all excited by the idea of shutting down my computer just to use another operating system.

      Anybody who's used a virtualization product like VMWare knows what I'm talking about. That is where it's at.


      One word: Games.

      Unless things have changed recently, opengl, directx etc don't work.
    • VMWare is a very fine product, and I too look forward to seeing it on a Mac. A friend of mine solved a rather hairy Windows problem by running multiple virtual NT machines under VMWare, since he wasn't allowed to ditch NT altogether (decisions made many, many levels above his customer).

      In the application in question, they had 21 NT hosts running their web apps. In production, these machines stayed up about five hours. The band-aid solution was to make one machine reboot all the others every four hours. The permanent fix was to run NT under VMWare: the NT instances still failed, but restarting one from a pristine state became a five-second operation.

      For a bonus, they picked up enough performance from Linux's paging versus NT's utterly brain-dead paging, that they were able to free all but three of the 21 machines that had been using to other tasks.

      The answer to a broken OS is to run it in a penalty box under a working OS.

      -jcr
    • by akheron01 (637033) on Friday March 10 2006, @08:19AM (#14890014) Homepage
      Oh man, I can't believe all of the people I hear saying they'll get an Intel Mac as soon as it can run Windows. I think all of these people are going to be a little surprised when they realize their Windows partition has been doing little more than gathering dust for several months ;)
    • by Macka (9388) on Friday March 10 2006, @09:27AM (#14890346)
      I've got a PowerBook at the moment, and will definitely be upgrading to a Macbook Pro in the near future. Being able to run MS Windows on it at (near) native speed would be a huge bonus for me, but I've got zero interest in dual booting to get that. I don't give a rats ass about running games under windows; I hardly have enough free time in my life to play WoW on my PowerBook more than a few times a week (without getting into trouble with my other half).

      What I really need it for is those work occasions where I run into equipment that needs a dedicated Windows app to manage it, and dual-booting to deal with that is just stupid. I need a good native virtual environment I can just fire up in a minute, do my work and then close it down. VPC on PowerPC just doesn't cut it. It's way too slow.

      The things I'm keeping an eye on ...... QEMU + Accelerator seems to be the only choice for Intel OSX right now. VMware are apparently showing interest (but nothing solid yet) and another outfit called iEmulator.com are supposed to have an Intel port of their existing Mac OSX product in the pipeline.

      If Xen worked I'd be delighted, but there seem to be problems that are going to take some time to work out. 1) there is no Intel VT support in the current Intel Mac's, and 2) Moshe Bar has said that "OS X has its own virtualization technology that interferes with Xen". Apparently he's been able to get FreeBSD and Debian working, but Apple's protectiveness of its hardware specs has so far prevented Bar from getting the graphics, sound or Wi-Fi to work.

      So it's really only a matter of time :-)

  • by laptop006 (37721) on Friday March 10 2006, @04:35AM (#14889359) Homepage Journal
    "Although Microsoft has previously said EFI booting would be supported by Vista, Ritz admitted that EFI support won't be seen in any version of Windows until the release of Longhorn Server."

    Great, yet another vista feature removed before released.
    • by Zadaz (950521) on Friday March 10 2006, @04:38AM (#14889368)
      Great, yet another vista feature removed before released.

      Better than being removed after release.

    • by Jesus_666 (702802) on Friday March 10 2006, @06:53AM (#14889732)
      Redmond - In a surprising turn of events Microsoft held a press conference yesterday stating that Windows Vista will not support the 32 bit mode of Intel 80386 and compatible processors. When asked about why this feature was left out from the release lead coder Alfred E. Newman replied: "We felt that 32 bit support was just not ready for Vista. The NT line of operating systems is still too cutting-edge to be used in the productivity powerhouse that Vista is going to be." Instead, Microsoft will deploy a new version of MS-DOS as the operating system's foundation. The new DOS, called "MS-DOS 2006" will feature improved support for TSRs and the capability of automatically loading supporting programs directly into extended memory, allowing it to have all 640 kilobyte of conventional memory ready for applications that depend on it.
      Microsoft promised that all other proposed Vista features (except for those already canceled) will "have a chance of making it into Vista". When asked about whether customers coud be expected to put up with Vista's proposed 480 installation floppies Newman replied: "What, me worry?"

      The new decision was universally met with conetempt within the Apple world. "They think that pushing the MS-DOS version number from 7 to 2007 is a big step," Random MacGeek from AppleRumorsUpYourButt.com commented, "but we clearly had the biggest version number jump when Bungie went from Marathon 2 to Marathon: Infinity. Microsoft is late to the game, as always."
      When asked about the topic of Microsoft being late to the game Apple replied: "It's true! Microsoft promides to buy me and GNU here a beer at the game. Now it's halfway over and Microsoft is nowhere to be seen!" "We're not going to invite Microsoft to the next game," GNU added, "we have better things to do with our time than to spend it waiting for some guy from Redmond."
  • by ssj-xordyh (613424) on Friday March 10 2006, @04:36AM (#14889362)
    Quote from the article: "It said its decision to 'reprioritise'[sic] EFI development to the server version of Windows was based on a lack of available desktop PCs with EFI support on the market."

    Maybe the reason that there are no desktop PCs with EFI support is because everyone knows that Windows still only boots on BIOS. If Microsoft was serious about jump-starting a move to EFI (or any other alternative) they would support it now, and watch the hardware follow.

    I wonder if this is due to laziness, maliciousness, or a combination of both?
  • elilo? (Score:4, Interesting)

    by Ledsock (926049) on Friday March 10 2006, @04:38AM (#14889367)
    I guess this means that someone is going to have to hack a Linux bootloader to boot Windows. Maybe something with elilo. It's be kinda cool for these [mactel-linux.org] guys to say, "Sure. You can run Windows on an Intel Mac. You just gotta install Linux first!"
  • by Cadallin (863437) on Friday March 10 2006, @04:45AM (#14889386)
    Does anybody give a damn? I mean seriously, did anyone out there actually BUY a new Intel mac counting on the rumors that it MIGHT be able to run windows sometime soon? If so, why?

    And does this really come as a suprise to anyone anyway? "Oh my God! Someone tries to update the x86 architecture in a meaningful way and Microsoft arrives late to the Party: Drunk, kicking, and screaming! Who knew that might happen?"

    • by ZeroOne42 (713052) on Friday March 10 2006, @05:43AM (#14889566)
      I for one was counting on the rumors that my new mac mini would be able to run windows. Why? Games. Although it'll take more than just EFI to play games in M$ Windows on an intel mac (drivers etc.), EFI is an important step towards that goal.

      You're obviously not a Windows user, nor a gamer, since the ONLY use of Windows is to play games anyway. Maybe view pr0n as well, but you can do that better on a Mac already...
  • WTF is EFI? (Score:5, Informative)

    by Big Nothing (229456) <big.nothing@bigger.com> on Friday March 10 2006, @04:50AM (#14889403)
    For those of us who DON'T have a BN acronyms in a LUT in our heads, EFI means "Extensible Firmware Interface". Read up on Wiki [wikipedia.org].

  • A shock, you say... (Score:5, Interesting)

    by mederjo (899667) on Friday March 10 2006, @04:52AM (#14889409)
    I know it's the fashionable thing to do, but the whole article summary is a troll. I can't imagine all that many people are buying Intel Macs because there's a chance they might boot Windows, or rather any one who is going to be shocked-SHOCKED! if they can't. Not out in the real - not /. - world anyway. Some might be a bit miffed perhaps. I would hope that those who do want to dual boot Windows and OS X are savvy enough to wait to see if it's actually going to be possible before making a purchase. If not, well, sad for them but they have a pretty good OS and machine. I'm sure there'll be some sort of virtualisation environment available which will probably make for a more useful experience than dual booting anyway - much easier to share stuff between OSes when you can run both at the same time. Using Windows on my PC via RDC on one of my Macs is often more convenient than flipping between machines using my KVM.

    Many of the people I'm aware of who are buying Intel Macs are people who have been hanging out for a pepped up PowerBook. There are a few who seem to be getting them because they're the "new Mac", more money than sense :-). I only know one or two first time Mac buyers who have been waiting for a spread of Intel Macs ( i.e. mini, iMac and MacBook ) to choose from. None of them seem to be particularly interested in running Windows on their new machines.

    I have a 17" Intel iMac, which I got as a replacement machine from Apple for my DTK prototype Intel Mac. It's a great little machine. I have no intention at all of booting Windows on it - that's what my PC is for ;-).

    BTW, does anyone know where the "shocked-SHOCKED!" thing ( not necessarily with my capitalisation ) came from? I've seen quite a few people saying/writing it, and the only place in the popular media, if you will, that I've seen it is in the movie "High Fidelity" where Joan Cusack says it when having lunch with the Laura character. Is that where it came from? It's been buggin' me :-).

    Regards,

    Jo Meder
    • by 1u3hr (530656) on Friday March 10 2006, @06:00AM (#14889607)
      BTW, does anyone know where the "shocked-SHOCKED!" thing ( not necessarily with my capitalisation ) came from?

      Casablanca. [vincasa.com] (1942)
      RENAULT (Claude Rains): I am shocked, shocked to find that gambling is going on in here!
      The croupier comes out of the gambling room and up to Renault.
      CROUPIER: (handing Renault a roll of bills) Your winnings, sir.
  • by erroneus (253617) on Friday March 10 2006, @04:55AM (#14889416) Homepage
    I'm really worried now! It seems like almost every feature boasted in Vista has been pulled. Database filesystem and all that? What will be left that isn't essentially Windows XP with a much larger greed for memory and other hardware requirements?
  • Seems logical. (Score:5, Interesting)

    by Vo0k (760020) on Friday March 10 2006, @04:57AM (#14889423) Journal
    Supporting EFI would be supporting competition. Incentive to abandon Microsoft.
    "I want a computer that's good for gaming and graphics. Either PC or the new Intel Mac, which I'd dual boot, OS X for gfx, Vista for games."

    EFI supported:
    "So, supposedly Mac is better for gfx than PC, let's try it... Wow, this OS X rocks and Vista sucks. I'm gonna get a PS3 for games and drop Vista altogether, staying with OS X."
    EFI not supported:
    "Well, there is Photoshop for Vista and no games for OS X, so I'd better buy a PC so I have both games and photoshop. Well, it sucks, but I bet OS X would suck just the same if I ever tried it."
  • Effing Vista (Score:5, Insightful)

    by FishandChips (695645) on Friday March 10 2006, @05:14AM (#14889480) Journal
    So Vista is coming to seem more and more like an XP service pack with a massive price tag and unwelcome restrictions. I don't know why Gates doesn't throw in the towel and announce that from now on the chair of Microsoft will be held on a rotating basis by the chairs of the major Hollywood studios. All Microsoft seem to be doing these days in the consumer market is kowtowing to the content providers while trying to grab a slice of the action for themselves. Microsoft offer no vision, no inspiration or feel-good factor. It's a pathetic end to the dream of a computer on every desk. What we have instead is a glorified credit card processor.
  • Horrors. (Score:5, Funny)

    by Chris Pimlott (16212) on Friday March 10 2006, @05:39AM (#14889555)
    The news will be a shock for owners of Intel Macs who had hoped they would be able to dual-boot between Windows Vista and OS X. Intel Macs only support booting via EFI."

    Neither of them was available for comment.
  • by linebackn (131821) on Friday March 10 2006, @06:18AM (#14889643)
    The more I think about it the more I think that if Microsoft ever provides official support for installing Windows natively on a Mac then it very likely will be the end of MacOS X and eventually Apple.

    Why? Because in general developers want "one true" operating system to develop for, often religiously so. I have heard people tell Mac users to "just get a PC" to run popular Windows-only software, but that is not a realistic expectation. That would be asking the Mac user to throw away thousands of dollars of hardware, and is generally considered unreasonable.

    If it ever becomes possible to easily install any version of Windows on a Mac in a manner that is supported by Microsoft, even if not by Apple, then these same people will demand that Mac users "just install Windows" to run their software. And they will consider that to be perfectly reasonable thing to do - they are adding something to they system and taking nothing away. They could afford an expensive Mac, so certainly they can afford to spend a few more buck for Microsoft Windows, right? And if it is running natively on the Mac rather than in VirtualPC developers will not worry that they might be making the users work in a crippled or limited environment.

    Then in time no one will see the need to develop MacOS X applications any more and all Mac users will be forced to use Windows.

    Apple will then be just another boring commodity PC maker like Dell or Gateway.

    So let's please stop even thinking about running Windows on the Mac. It just isn't cool.
  • by lmlloyd (867110) on Friday March 10 2006, @06:42AM (#14889704)
    This is ridiculous! The story is, the crippled (I am amazed they are even releasing it) 32-bit version of Vista won't support the odd mac-only combination of 32-bit chips, and EFI. The 64-bit version of Vista, will support the standard configuration of 64-bit chips, and EFI, just like XP 64 already does.

    I love all the comments about how far behind Apple MS is, as proven by the fact that they can't even get EFI working. No, they have it working, just on modern 64-bit systems. Apple is the only company on earth that decided to go with a brand new technology like EFI, and then stick 32-bit chips on a 32-bit OS in their system! If Apple actually comes out with a 64-bit machine (like most modern PCs), I'm sure 64-bit Vista will boot on it just fine. This is one of those cases where the problem isn't how far behind MS is on their support for EFI, but how far behind Apple is on their choice of x86 chips. I have no idea why Apple let itself get talked into dumping a 64-bit architecture, just to get what basically amounts to some fast dual-core P3s, but they did.

    Talk about the very definition of FUD!
  • by KJKHyperion (593204) on Friday March 10 2006, @07:36AM (#14889846)

    Windows supports EFI. Here, now, today. Has been for years. Currently is. Except only on the IA64 architecture. This makes the article partly bullshit, and a large amount of comments here as well. But the bullshit doesn't stop here.

    Of course the thing about drivers being stored entirely in EFI is completely false, misleading and somewhat retarded (it really depends on how twisted your idea of drivers is. If you come from a Linux background there's a 9 in 10 chance you are clueless and forever jaded about it). Of course the DRM comments here don't make the slightest sense, since TPM chips are here, now, have been for years, and they work with the old, usual, actually-existing BIOS extensibility interface (i.e.: drop a function pointer somewhere, get called). Have you bought an IBM laptop or workstation that was made some time after the Cretacean? congratulations! your cute little black box is Trusted Computing compliant (r), (c) and (TM)!

    From a more technical point of view: Windows doesn't depend on legacy hardware. It used to, in ye olden days (until before Windows Server 2003 R1), but it was so easy to get around it with software emulators (provided by Microsoft herself, as part of Windows NT 4 Embedded, Server Appliance Kit for Windows 2000 Server, et cetera) that only people with a really small penis complained. Nowadays it's a matter of the right boot loader and Hardware Abstraction Layer (all aboard the cluetraaain! if you are among the differently-endowed mouth breathers who confuse "instruction set" with "hardware" - and you know if you are one - this might just be your chance to finally get it!).

    Technical trivia: the Windows boot loader is a beauty. It totally mops the floor with anything in the wild, save maybe for Grub. The horrid ntldr flat executable is just a teeny weeny stub containing the real thing, a PE executable called osloader.exe (with a resource section, even - the description simply says "Boot loader"; sadly it has no icon) which is the universal loader - why, yes, your humble peecee can network-boot too! In short, the little bugger comes with a full SCSI+ATAPI stack (it can even stay loaded and be used by the kernel as the SCSI class driver - no shit!), a network stack for the TFTP client (yep) and its very own hardware abstraction layer, since the thing was written against ARC (think EFI, only for the Alpha AXP architecture) which is only really available on Alpha. The thing is a driver model short of a full operating system

    So, reconsider the length of your penis in the light of these new facts

    • by AntiDragon (930097) on Friday March 10 2006, @04:50AM (#14889404)
      Simple really - because OS X is still lacking in certain software.
      The OS is great. Really. The hardware is a bit overpriced, yes but let's face it, it *is* oh so desirable!

      But there is still a ton of software out there that doesn't come in OS X flavour. Notably games.

      And to get the absolute maximum performance for Windows games, you'd want to dual-boot, not use some VMware system. ...Hang on...Did I just use the words "performance" and "windows" in the same sentence? I need more sleep....
      • Re:Bios Work. (Score:5, Informative)

        by hattig (47930) on Friday March 10 2006, @05:28AM (#14889523) Journal
        What you describe is an optional module for EFI already.

        Apple just chose not to include it, for the obvious reason that they don't need it.

        I expect standard bootloaders in the free software world will all support EFI by the end of this year, if they don't already. I don't know if you'd need an EFI-specific live-CD / install CD too for CD installs.
      • Half wrong ! (Score:5, Informative)

        by Anonymous Coward on Friday March 10 2006, @05:47AM (#14889582)
        Soory, but will not be a bad idea if you read an 80386 users' manual...

        286 processors and up start in what is know as real-mode. like the original 8086. That is the 16 bit mode.
          There is not 8 bit mode (not any more, and I think that was only available in the nec v20 AFAIK).

        VGA cards do not start-up in CGA mode. They are initialized by the VGA BIOS in text mode, compatible to CGA but is not the same because 480 vertical lines (plus retrace) are used instead of 200 plus retrace.

        BTW, newer graphic cards don't even support all C/E/VGA modes anymore, and I think that has benn for almost for 8 years more or less.

        I don't think that the setup of the protected mode should be done in BIOS, but some useful mode (better than the crappy real-mode) should be enabled.
        May be some flat mode (32 or 64 bits).

        On the other hand, you don't enable more than protected mode, the "features" are always available (but maybe just in protected mode the instruction don't produce illegal opcode... I don't know that.)
    • by lmlloyd (867110) on Friday March 10 2006, @08:18AM (#14890006)
      Steve Jobs actually tried this with NextStep, and learned a painful lesson. While NextStep was heralded for its stability and features on the Next hardware, as soon as it was "out in the wild" on commodity hardware, it was pretty much panned as a buggy, slow, cumbersome piece of garbage that never really sold or gained any major following.

      There were a few reasons for this.

      First off, the people who went out of their way to buy a Next box, much like macheads, had already decided that it was a wonderful machine before they ever turned it on, so were a bit more forgiving than someone just trying out the OS alongside others.

      Secondly, it is a lot easier to develop an OS that only needs to run on one or two motherboards, with one or two chips, and one or two graphics systems, than it is to develop something that has to work with everything.

      Thirdly, if you have complete control of the hardware, you can cheat on a lot of things. For example, if you know a feature crashes horribly on anything under a certain amount of RAM, then you can hold back that feature on any system that doesn't have enough RAM to handle it. When the user has control of the hardware, all you can do is make recommendations, and hope they abide by them, which almost without doubt, some won't.

      Lastly, the number of bugs and problems you have to fix is limited to the number of users that have problems. Every piece of software as complex as an OS has bugs, if you have a few thousand users, the chances of them running across all the bugs is a lot smaller than if you have tens of thousands of users.

      All of this, at the very least, taught Steve Jobs that trying to be Microsoft is harder than it looks. I think that Apple would probably make a ton of money if they could release their OS as a software product for commodity PCs, and would probably put a HUGE dent in the Linux market. However, I don't know if the company is really up to handling that, and I am quite sure that from his Next experience Jobs realizes the danger of trying to make that move when you aren't ready for it.