Re: Juggling partions?

From: Pegasus \(MVP\) (I.can_at_fly.com)
Date: 04/02/04


Date: Fri, 2 Apr 2004 11:41:44 +1000

I agree with the thrust of your lengthy post even though I prefer
to use a boot loader that lets ***me*** determine which partitions
should be hidden and which ones should be visible, rather than
doing it automatically like BootIt (going only by what you wrote).

"Jim" <null@null.com> wrote in message news:qg3bc.4464$zh.3486@fed1read07...
> This is why you use a boot manager like BootIt NG!!! (
> http://www.bootitng.com ) If you had, you'd have NONE of these problems.
> The problem with the MS boot manager is that it can't hide partitions, so
no
> matter what you do, you always see one or the other. Granted, perhaps you
> can install PM (Partition Magic) and manually muck with the partition IDs
> and active indicators every darn time you want to change the bootable OS,
> but my lord, what a hassle. Even then, you *STILL* have to choose which
of
> the two partitions will contain PM! IOW, you've already started a
partition
> dependency, albeit, tied to PM.
>
> Instead, install BootIt NG in a *third* partiton all by its lonesome,
> perhaps at the very end of the HD, only requires about 8MB. Then, you can
> boot your partitions, either one of them right off its direct boot menu,
you
> don't even need to set up individual boot menu items as long as you don't
> want, say, a third shared data partition. You just double-click the
> partition you want booted, and AUTOMATICALLY all others are hidden! You
can
> believe how incredibly simple it all is. In fact, you're making life only
> *more* difficult by mucking w/ PM to do this job. PM is *not* a boot
> manager, not unless you install the Boot Magic boot manager that comes w/
it
> (at least that's way it was packaged way back in version 4.0 when I
> abandoned it for BootIt NG, which made PM obsolete, IMO). Even so, Boot
> Magic is nearly identical to BootIt NG in this regard.
>
> People insist on making this stuff a LOT harder than it need be. As long
as
> you continue to muck w/ the MS boot loader, it will drive you nuts. It's
> major flaw is an inability to hide partitions. Because it can't, you're
> left in this mess of having to hide other partitions so, for example, all
> your OS installations can still boot as C: (i.e., you have no
> inter-partition dependencies). The MS boot loader leaves you with no
choice
> but to build-in drive letter dependencies because it can't hide other
> partitions. Trying to mitigate that w/ manual procedures via PM is
perhaps
> doable, but it's incredibly silly, leave that to a boot manager, like
BootIt
> NG or even Boot Magic. Install BootIt NG, you get 30 days FREE, you don't
> like it, take it out (uninstalls easily, leaves your system EXACTLY as it
> was before installation). Trust me, once you do, and use all its other
> features, like backup imaging, partition management, etc., you'll wonder
why
> you ever bothered w/ PM. At the very least, it will demonstrate how
> *procedurally* you're making a mmountain out of a mole hill.
>
> HTH
>
> Jim
>
>
> "Noozer" <dont.spam@me.here> wrote in message
> news:8C0bc.6972$oR5.3831@pd7tw3no...
> > I wanted to avoid the XP and ME installations having anything to do with
> > each other.
> >
> > I was hoping that by using two primary partitions that they would stay
> > separate, booting to whichever partition was active (the way it SHOULD
> > work), but Microsoft insists on stomping on whatever other OS's are on
the
> > drive.
> >
> > "Jim Macklin" <p51mustang[threeX12]@xxxhotmail.calm> wrote in message
> > news:uL2SShCGEHA.2612@TK2MSFTNGP09.phx.gbl...
> > > To set up a dual boot you install the older OS to the C:
> > > partition, as you did and then while in that partition begin
> > > to install XP. It will detect the existing OS (ME) and ask
> > > where you want to install XP. You select D: and XP will
> > > install on D: but it will install a boot loader on C: that
> > > will be detected when you boot and ask whether you want to
> > > run ME or XP.
> > > See
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;Q305873
> > >
> > >
> > > "Noozer" <postmaster@127.0.0.1> wrote in message
> > > news:gP_ac.6610$Pk3.3699@pd7tw1no...
> > > | I recently installed Windows ME and Windows XP into my
> > > computer.
> > > | Unfortunately Win XP trashed the Win ME installation so
> > > I'm about to repair
> > > | and need some advise...
> > > |
> > > | I created TWO primary partitions on the hard drive. I set
> > > the first
> > > | partition active and installed Window ME onto that
> > > partition. I got it all
> > > | setup and it was working fine.
> > > |
> > > | I then set the second partition as active and installed
> > > Win XP onto that
> > > | partition. It is also configured how I like and works
> > > fine.
> > > |
> > > | Now, I try and set the first partition active and the PC
> > > does not boot. I
> > > | assume that Win XP has stomped on the boot sector of the
> > > hard drive.
> > > |
> > > | I have Partition Magic 8 and am hoping I can do some
> > > partition
> > > | convertion/moving and get the Win ME installation back
> > > without having to
> > > | re-install. If necessary I could get a ghosting program
> > > and dump the
> > > | partition to CD and restore it later, but I'd rather avoid
> > > that if possible.
> > > |
> > > | Is there any way I can repair these installations so both
> > > installs will
> > > | work?
> > > |
> > > | Thanks!
> > > |
> > > |
> > >
> > >
> >
> >
>
>



Relevant Pages

  • Re: Problem after converting FDisk Partitions to LVM
    ... The issue I was reporting about was, that my 2 freshly installed W4.0 partitions didn't boot up anymore, after the eCS beta was installed and changed FDisk to LVM in the process. ... I wasn't trying to migrate an existing, over time matured W4 system to eCS, rather than trying to learn about the shortcomings of the latest FDisk and potential dangers in possibly switching my W4 FP16+ box to LVM, in order to install and boot additional OS' from HDD areas beyond FDisk's limited abilities. ...
    (comp.os.os2.setup.storage)
  • Re: Windows kill Linux?
    ... Now during every install after CD1 ... a dual boot with Windows. ... Windows can not detect ext3 partitions. ...
    (alt.os.linux)
  • Re: Install hangup....
    ... you at a download for it - perhaps boot into the livecd desktop and run ... fsck on your created partitions? ... setup your partitions before you run the install, ... I did the memory test and found some interesting little tidbits about this computer.... ...
    (Ubuntu)
  • Re: dual boot with windows xp question
    ... I have a book that explains how to install an older ... It said I have to make a boot disk. ... he should not attempt to create Linux partitions with Microsoft ... He should leave the space intended for Linux unpartitioned. ...
    (comp.os.linux.setup)
  • Re: Windows kill Linux?
    ... Now during every install after CD1 ... a dual boot with Windows. ... Windows can not detect ext3 partitions. ...
    (alt.os.linux)