Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Boot Linux, BSD, and OS X from Vista

Posted by kdawson on Mon Oct 16, 2006 02:51 PM
from the by-your-bootstraps dept.
An anonymous reader writes, "NeoSmart Technologies has just released EasyBCD 1.5, complete with support for Vista, Windows NT/2k/XP, and Windows 9x/ME. EasyBCD 1.5 adds experimental support for dual-booting any of these along with Linux, Mac OS X, or BSD — straight from the Windows Vista bootloader without any additional configuration needed!" From the article: "Windows Vista's new bootmanager is a double-edged sword. It's one of the most powerful booting scripts in existence, and a far cry from the very limiting boot.ini of legacy Windows operating systems. But it overwrites the MBR without a second thought, and doesn't provide any means for users of alternate operating systems and boot managers to use their old system. That's where EasyBCD 1.5 comes in!" EasyBCD 1.5 is free.
+ -
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.
  • BCD? (Score:4, Funny)

    by convolvatron (176505) on Monday October 16 2006, @02:53PM (#16457539)
    i've always found bcd quite easy. just throw away a large fraction of the legitimate encodings...wait, what?
  • by Eideewt (603267) on Monday October 16 2006, @02:57PM (#16457589)

    "But it overwrites the MBR without a second thought...."

    Well, who would have expected Microsoft to do that?

    • It's nothing new really. When I used to install Win98 as an afterthought alongside a Linux distro, I could be sure the lilo mbr would be trashed, and I made sure I had a boot floppy handy to boot back into linux and reinstall lilo.
      • Re: (Score:3, Informative)

        It's nothing new really. When I used to install Win98 as an afterthought alongside a Linux distro, I could be sure the lilo mbr would be trashed, and I made sure I had a boot floppy handy to boot back into linux and reinstall lilo.

        Consider yourself lucky. When I installed Windows XP alongside Linux, it trashed my entire hard drive [advogato.org]. That was the last time I ever installed Windows. The system simply can not be trusted. I use Linux and OS X exclusively now.

          • by sumdumass (711423) on Monday October 16 2006, @05:00PM (#16459813) Journal
            What if he is like me and already has a working, tweeked and otherwise perfected install of linux running. I'm sure there has to be an easier way then trashing that, installing windows first then rebuilding your linux install.

            Personaly, I choose to instal lilo onto a floppy (the boot code). Then go in later and move it to the hard drive. This allows me to boot to a boot disk and streight into linux if neccesary. Also it allows for a backup of lilo's config in case windows trashes the partition linux is on.

            Something i'm wondering is, Did microsoft do this in order to screw open source boot loaders and make the act of dual booting into a free operating system more dificult? It apears that the site is down for the EasyBCD loader. I cannot tell if it is free as in opensource free or just free as in no costs for now free. It could directly effect the way some distro's are compatible with VIsta.

            I'm also wondering if the "opensource" free version if any, would be GPLv3 compatible because microsoft will no doubtly have certain levels of pattents pertaining to the vista boot loader that the EasyBCD guys might not be able to control enough to be GPLv3 compliant. Not to mention that newer microsoft OS's typicly create a volume serial number that is tied into booting and operation of the OS. This is most evident when cloning drives and when it doesn't keep the corect serial you get errors on booting. How would this be effected by the ANTI-TIVO type wording in the GPLv3 when a GPLed product is working with the code or programs? I Think some clearification might be in order on this. I have raised simular questions before with products like Itunes and Hardware that locks certain performances out in cheaper versions and the answer is always, they shouldn't be doing that or the Closed app should be open. I'm sure booting to vista in a free way might be more important then forcing apple to opensource Itunes in order to keep a GPLv3 frontend compatible with the GPL.

            An no, I'm not trolling. These are legit concerns with the GPLv3 brought up by others too. I'm just putting them into relvent terms that can be related to in this context. It would suck donkey balls if GPLv3 licensed bootloaders are incompatible to dual booting with microsoft operating systems because of this. Especial when the entire idea behind the changes is to control the manufacturers hardware with previous versions of the GPL claims is outside the GPL's scope.
    • I've got a MSI mobo (K7N2G-ILSR) that for some odd reason requires the DDO from Western Digital to be loaded to see my full 250GB. Since Vista replaces the boot sector with a new one it trashed the DDO and only showed the drive as around 32GB. :( I sure didn't expect it, especially since XP plays nicely with DDO. I think I'll wait for a new computer before trying it again.

      Jonah HEX
  • by mpapet (761907) on Monday October 16 2006, @02:58PM (#16457607) Homepage
    This one won't make it to the gold master.

    Kind of like stealing from a Las Vegas casino. Won't happen.
    • You're expecting Vista to act differently than every other Windows version since at least 95? Every one of the damn things overwrite the MBR.

      This is why on multiboot systems I install Grub into the partition rather than the MBR. This way you can keep the Windows MBR and just set the Linux partition as bootable and it works as it's supposed to.
      • Overwriting the MBR is reckless, it isn't their data.... Class::action()

        Have you checked your license agreement?
      • Overwriting the MBR is reckless, it isn't their data

        In case you didn't notice, you are installing an operating system. Generally speaking, machines have always shipped with one OS to control the entire system. It is certainly *not* unreasonable for Microsoft to overwrite the MBR. Especially when they expect that their OS will be the only one. You'd have a hard time convincing a judge otherwise.

        The fact that Microsoft hasn't improved this part of the install as more hobby OSes have showed up just goes to show how little they care about letting you use your hardware as you want to use it. But they are under no obligations, especially when the installer warns you to make backups before you run it.
  • by gcnaddict (841664) <gcnaddict @ g m a il.com> on Monday October 16 2006, @02:58PM (#16457609)
    I know its possible to boot BSD, Vista, XP, and OSX if you use Grub->>Vista Bootloader->>NTLDR (to load bsd/osx, vista, and XP respectively). However, knowing that I can skip grub (no offense. I just didn't feel comfortable using it) is great news!
    • You're not alone! I still use LILO because it's what I've used since 1997, and I'm too lazy to learn GRUB.
      • by Shawn is an Asshole (845769) on Monday October 16 2006, @03:27PM (#16458147)
        Grub isn't very difficult to adjust to. I also held out on learning it for a while, but it actually is kinda nice. The thing I really like about it is after making a change (new kernel, boot option, etc) it isn't necessary to reinstall it to the mbr. Just edit menu.lst and it's done.

        Take the 5 minutes to learn it.
        • by TeknoHog (164938) on Monday October 16 2006, @04:26PM (#16459167) Homepage Journal
          When you "make install" a new Linux kernel, it makes a symlink /boot/vmlinuz to the new kernel. So you won't even have to edit menu.lst if the boot option is this symlink. Grub also has the nice feature of editing the kernel entry at bootup, so you can go back to the old kernel if necessary.
        • Re: (Score:3, Interesting)

          This box that I am on right now is a dual 200 MMX with 256 MB of RAM, and three hard drives.
          I use Windows 98 "DOS" to make batch files to run loadlin with a nice menu to boot either Windows 98 (not very often), or a selection of window managers in my knoppix remaster (see screenshots). I can use a "knoppix.img" file for ~/, or just do without that, and boot into the default IceWM. Next choice is Fluxbox, then KDE, then twm.
          The Windows 98 desktop has icons for all of that also, and the menu too. So, can jump
    • What's wrong with GRUB? I'm not offended by you not liking it, but just curious. To me, it doesn't exactly seem perfect and ideal, but it's easy enough to install and use.
      • by TheRaven64 (641858) on Monday October 16 2006, @03:16PM (#16457941) Homepage Journal
        To me, GRUB seems like insane bloatware. Why do I need something that's so big it needs its own partition just to handle multiboot? The FreeBSD first-stage boot loader is small enough to fit in the MBR. It presents me with a menu of all partitions to boot from (although it does label NTFS partitions as DOS) so I get something a bit like this at boot:
        F1: FreeBSD
        F2: DOS

        F5: Disk 2

        Default: F1
        It defaults to whatever I booted last time. If I nuke all of the partitions on my disk and re-install, it still works, passing off to the OS-specific boot loaders on each partition. It's lightweight, simple, well-tested, and does what I need.
        • by entrylevel (559061) <jaundoh@yahoo.com> on Monday October 16 2006, @04:45PM (#16459535)
          Grub doesn't need an extra parition to boot from. I'm noting that you said the 1st stage BSD bootloader. That would imply that, just like Linux, there is a 2nd stage to the boot loading. The 1st stage of grub fits in the MBR without issue. The 2nd stage is read from your boot partition, which in most modern distros is the same as your root partition. It also happens that is a handy place to put the bootloader config in human-readable form. You might call that bloat, but I call it handy for stuff like single user mode or testing a new kernel without worrying about needing a boot floppy.

          The "last selected OS" is handy, and GRUB can be configured to do this as well, but what if you last selected single user mode, or memtest86? If you reboot your machine remotely, and forget that the last option selected has no network support, you have no way to access the machine. At least with GRUB, you can edit the config and tell it not to do that.
    • Actually, EasyBCD requires Grub to be installed in order to boot Linux.

      Now my problem is, it doesn't want to know what DRIVE I've installed Grub on... so I am doubtful it will work. :/

      • Aha, you have to go edit the Linux entry and set the drive letter (EasyBCD automatically converts it to the device name).
  • by Salvance (1014001) on Monday October 16 2006, @02:59PM (#16457621) Homepage Journal
    I don't see what's so impressive about Vista's bootloader, unless you're simply comparing it to prior MS versions. What would be cool is if Microsoft released software that allowed someone to simultaneously open multiple O/S's at the same time in a non-virtualized environment. Imagine being able to switch back and forth between Linux and Windows simply by hitting a keystroke?

    With the advent of dual core chips and O/S support for these chips, this doesn't seem all that difficult. Isn't Apple already doing it?
    • Re: (Score:3, Informative)

      What would be cool is if Microsoft released software that allowed someone to simultaneously open multiple O/S's at the same time in a non-virtualized environment.

      How is this possible without virtualization of some kind be it hardware or software? Oh wait its not...

    • Imagine being able to switch back and forth between Linux and Windows simply by hitting a keystroke?

      You mean like with this [vmware.com]? no wait, Vista's EULA won't let you do that unless you buy the pricier Vista...
    • Re: (Score:3, Informative)

      Nope, Apple isn't doing it, and neither is anyone else. And they won't, not like you are describing, and here's why: Someone needs to be in charge of the memory, the disks, and all the rest. That's the whole point of the OS. Therefore, only one OS can run on a computer at a time.

      You could get around that with some fancy firmware to save the state to some storage device and load it up again, but it really isn't worth it. Virtualization does a better job for most of what you would want to do: Have a base
      • Someone needs to be in charge of the memory, the disks, and all the rest. That's the whole point of the OS. Therefore, only one OS can run on a computer at a time.

        Or the hypervisor in many mainframes, IBM POWER5 systems, or anything running Xen. The next generation of GPUs are going to include save and restore state operations, and newer x86 systems finally come with an IOMMU, meaning that a Hypervisor will soon be able to share everything, including the GPU, between machines.

        The DirectX 10 driver mod

    • Running multiple OSes simultaneously without virtualization or emulation? Where/how is Apple doing this?
        • by snuf23 (182335) on Monday October 16 2006, @04:26PM (#16459173)
          "He's probably thinking of Rosetta and/or X11, or before that Classic for running Mac OS 9 and earlier apps under Mac OS X."

          None of which represent running "2 OSs at the same time without virtualization".

          Rosetta: a PowerPC emulation layer for running PowerPC binaries on Intel. I don't know the details but I would assume that system calls to Mac OS X APIs are presented to the native Intel OS X components - so the whole thing isn't exactly running in the emulation layer. The OS components being called by the software are running native on Intel.

          X11: A window manager for UNIX. X11 apps running on Mac OS X are still binaries built to run on OS X. The Window manager just handles displaying the GUI elements. This is not running a different OS.

          Classic mode: A form of virtualization. It booted OS 9 in a seperate process under OS X. Similar to how VMWare or Virtual PC work. Probably a bit better in terms of hardware support, because Apple had fixed targets for possible hardware on Apple computers, rather than VMWare which for some devices (video cards) only offers basic support.
    • With the advent of dual core chips and O/S support for these chips, this doesn't seem all that difficult. Isn't Apple already doing it?

      Dual-core chips have absolutely nothing to do with the ridiculous "multiple OS without virtualization" scenario you are imagining. Yes, it really is "all that difficult", actually more in the line with "impossible".

      And no, Apple isn't doing it. Apple hasn't even stepped a foot in the virtualization bandwagon yet, so I'm wondering where you got that idea. Boot Camp is just a
  • > It (BCD) is one of the most powerful booting scripts in existence...

    I'm curious if this statement is more than marketing speak. What's so great about BCD?
    • I'm curious if this statement is more than marketing speak. What's so great about BCD?
      I'm afraid you misunderstood the statement. They're talking about Vista's boot script not BCD. I fail to see what's so great about it though, since it overwrites the MBR "without a second thought".
  • Why BCD? (Score:3, Insightful)

    by Ash-Fox (726320) on Monday October 16 2006, @02:59PM (#16457639) Homepage
    So... any particular reason why BCD instead of GRUB or Lilo? I don't get it.
  • by daveschroeder (516195) * on Monday October 16 2006, @03:06PM (#16457773)
    ...you can't "boot OS X" on non-Apple hardware without:

    1. Breaking Apple's Mac OS X license agreement, which says that Mac OS X is to be run only on Apple-branded computers
    2. Pirating Mac OS X (Intel), since Mac OS X (Intel) is not available as a standalone OS at present
    3. Running a horribly hacked version of Mac OS X, with critical pieces of the system modified, including the kernel
    4. Running Mac OS X in an unupdateable state, since any official Apple software updates that overwrite modified pieces of the hacked version of Mac OS X will break it
    5. Running Mac OS X in a state completely unsupported by its vendor
    6. Possibly violating civil or criminal law in your jurisdiction

    I hope that most people can find at least *one* of the above items that would make them reconsider running Mac OS X (Intel) on a generic PC without paying for it (some will no doubt argue that they should be able to "reuse" PowerPC licenses for Mac OS X in spirit, but the fact is that it's not the same product - that's like saying that you at one time owned one software product from a company that's similar, so you should be able to use this other one/newer version/older version/different version for free). I'm sure others will come up with all sorts of justifications why it's okay.

    But isn't all of the billions of dollars or R&D and hundreds of thousands of manhours invested in Mac OS X worth something? What if their pricing is predicated on what is essentially a good faith agreement that you'll not hack it and run it on non-Apple hardware? Does Apple have ANY say in how they'd prefer it to be used?

    I could go on, of course, but just thought this was worth mentioning.
    • Re: (Score:2, Interesting)

      by Anonymous Coward
      You keep repeating the same stuff over and over again. Here's the real list

      1. Breaking the law
      2. Having an install which might not work right
    • What exactly IS your point? You've got your head so far Apple's backside you can't even write a coherent argument.

      You state that OS X on non-apple hardware is neither stable nor production quality. Legality in terms of licenses is of little importance for personal use and no sane company would use such an unstable product so your "points" are redundant. As a result it is only viable for those individuals who either lack money or wish to play around with OS X, neither of whom is going to buy a Mac instead.

      So
      • What exactly was incoherent or incorrect about my argument? Specific examples, please.

        Your arguments are the ones that are irrelevant, here. You don't get to decide that using Mac OS X in this fashion benefits Apple, therefore it's okay in the context your own moral or logical framework for people to pirate it and so on. Apple is the entity that gets to decide, and they have.

        It doesn't have anything to do with having anything in anyone's backside.

        Again, I'd love to hear about anything that I said that's inc
    • Re: (Score:3, Informative)

      Mac OS X (Intel) is not available as a standalone OS at present

      The retail boxed version of 10.4.7 Server is Intel-compatible.
      • What if you install Vista and Linux on your new Intel-based Mac and would still like to boot into OS X sometimes?
        You can do that already, skipper.
      • Re: (Score:2, Insightful)

        What if you install Vista and Linux on your new Intel-based Mac and would still like to boot into OS X sometimes?

        Um, you can do just that, then?

        ...

        (What are you trying to ask? Because Boot Camp will officially support Vista, and you'll legally be able to purchase and install Vista on an Intel-based Mac, and you can of course install Linux (yes, the final version of Boot Camp will very likely support more than two partitions and thus more than two OSes), and Mac OS X is obviously a supported OS on an Intel-b

        • Re: (Score:3, Insightful)

          You don't have to respect all their wishes. What happened to fair use?
          • by soft_guy (534437) on Monday October 16 2006, @04:39PM (#16459409)
            Pretty much, yeah. If you're a control nazi, don't release your shit. Fuck corporations like Apple who wanna fuck the consumers up the ass sans lube.

            Apple doesn't exactly try to get people thrown in jail for doing this. Sure, they frown on people who distribute hacked versions of their OS. But, I think they are right to do that merely from the point of view that they are protecting less savvy people from fucking themselves and also making it really clear that running OS X in that manner is unsupported and therefore unwise if you are doing any work that might actually be important. But frankly, I've spoken with lots of people from Apple on the subject (admittedly they are not from Apple Legal and are not speaking officially) and they pretty all say that if you want to hack something for the sheer fun of trying to get it to work and aren't redistributing their stuff, then knock yourself out.
  • The real props should go to Microsoft for designing a flexible bootmanager and boot-time-application framework that is flexible and firmware independent (x86 BIOS, IA32 EFI, IA64 EFI, x64 EFI).
  • License: Freeware (Score:5, Informative)

    by Benanov (583592) <brian DOT kemp AT gmail DOT com> on Monday October 16 2006, @03:17PM (#16457969) Homepage Journal
    Downloaded it just to check the license (yeah, I'm odd about this crap)

    It's freeware. Sorta looks like a Creative Commons license, but basically it's just plain old freeware.

    4. Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:
    a. You may distribute the Work only under the terms of this License, and You must include a copy of, or the Uniform Resource Identifier (URI) to, this License with every copy of the Work You distribute, and only with the permission of the Licensor & Original Author. You may not offer or impose any terms on the Work that alter or restrict the terms of this License or the recipients' exercise of the rights granted hereunder. You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties. You may not distribute the Work with any technological measures that control access or use of the Work in a manner inconsistent with the terms of this License Agreement. The above applies to the Work as incorporated in a Collective Work, but this does not require the Collective Work apart from the Work itself to be made subject to the terms of this License. If You create a Collective Work, upon notice from any Licensor You must, to the extent practicable, remove from the Collective Work any credit as required by clause 4(c), as requested.
    b. You may not exercise any of the rights granted to You in Section 3 above in any manner that is primarily intended for or directed toward commercial advantage or private monetary compensation. The exchange of the Work for other copyrighted works by means of digital file-sharing or otherwise shall not be considered to be intended for or directed toward commercial advantage or private monetary compensation, provided there is no payment of any monetary compensation in connection with the exchange of copyrighted works.
    c. If you distribute the Work, You must obtain permission from and let the Original Author know, You must keep intact all copyright notices for the Work and provide, reasonable to the medium or means You are utilizing: (i) the name of the Original Author (and/or pseudonym, if applicable) if supplied, and/or (ii) if the Original Author and/or Licensor designate another party or parties (e.g. a sponsor institute, publishing entity, journal) for attribution in Licensor's copyright notice, terms of service or by other reasonable means, the name of such party or parties; the title of the Work if supplied; and to the extent reasonably practicable, the Uniform Resource Identifier, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work. Such credit may be implemented in any reasonable manner.
  • I had to replace my MBR for it to work, since I had loaded grub into it.

    So I tried to boot into Linux. I must say, I don't remember Linux being a blank screen. I seem to recall it being more interactive...

  • by Doc Ruby (173196) on Monday October 16 2006, @06:32PM (#16461143) Homepage Journal
    " Boot Linux, BSD, and OS X from Vista"

    That's not "from" Vista, it's despite Vista.
    • Apple and the U.S. government established the anti-boot laws to keep people from booting OS X.

      OS X checks the hardware while booting. This, as far as I know, does nothing to remove or bypass that check. Presumably, it may only be used to boot OS X if you are installing multiple OS's on a Mac or have applied other hacks to OS X. I don't see any likely lawsuits over this.

    • Apple and the U.S. government established the anti-boot laws to keep people from booting OS X.

      I'm sorry ... what?

      Are you posting from the future, where the world has been decimated by killer iPods or something?