Juggling partions?

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!

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...;en-us;Q305873


"Noozer" 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!
|
|

"Noozer" 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!


I assume that each version of Windows ended up in
a folder called \Windows. When you boot into WinXP,
what drive letter do you see for each of these folders?

"Pegasus (MVP)" wrote in message
...

"Noozer" 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!


I assume that each version of Windows ended up in
a folder called \Windows. When you boot into WinXP,
what drive letter do you see for each of these folders?

Nope... two separate partitions. Files are completely separate.

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" wrote in message
...
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...;en-us;Q305873


"Noozer" 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!
|
|

If you installed clean on two partitions you did not create
a boot loader.

If you installed on the C: drive but directed the install to
place the second OS on a different partition you would have
a choice when booting to choose the OS.


"Noozer" wrote in message
newsu0bc.7074$Pk3.7005@pd7tw1no...
|
| "Pegasus (MVP)" wrote in message
| ...
|
| "Noozer" 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!
|
|
| I assume that each version of Windows ended up in
| a folder called \Windows. When you boot into WinXP,
| what drive letter do you see for each of these folders?
|
| Nope... two separate partitions. Files are completely
separate.
|
|

"Noozer" wrote in message
newsu0bc.7074$Pk3.7005@pd7tw1no...

"Pegasus (MVP)" wrote in message
...

"Noozer" 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!


I assume that each version of Windows ended up in
a folder called \Windows. When you boot into WinXP,
what drive letter do you see for each of these folders?

Nope... two separate partitions. Files are completely separate.

I may be able to help you, but only if you try to answer
my questions as accurately as possible. I will now rephrase them:

a) When you boot into WinXP, what drive letter is the WinXP
partition on?

b) When you boot into WinXP, can you see the WinME installation?
If yes, which drive is it on?

c) Set your BIOS so that the machine boots into WinME (which,
as you say, will fail). Now boot the machine with a Win98 boot disk
(www.bootdisk.com). Can you see your WinME installation on
drive C:?

The next step depends on your answers.

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?

I assume that each version of Windows ended up in
a folder called \Windows. When you boot into WinXP,
what drive letter do you see for each of these folders?

Nope... two separate partitions. Files are completely separate.

I may be able to help you, but only if you try to answer
my questions as accurately as possible. I will now rephrase them:

a) When you boot into WinXP, what drive letter is the WinXP
partition on?

C: is the only drive that appears.

b) When you boot into WinXP, can you see the WinME installation?
If yes, which drive is it on?

Nope... No trace of the ME installation at all

c) Set your BIOS so that the machine boots into WinME (which,
as you say, will fail). Now boot the machine with a Win98 boot disk
(www.bootdisk.com). Can you see your WinME installation on
drive C:?

It's on one drive, so the BIOS isn't involved at all. I'm setting the active
partition using FDISK, which sees both partitions fine, but since their both
primary partitions only one can be set as active.

The next step depends on your answers.

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" 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" wrote in message
...
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...;en-us;Q305873


"Noozer" 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!
|
|

"Noozer" wrote in message
news:ZW1bc.7184$oR5.1970@pd7tw3no...
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?

I assume that each version of Windows ended up in
a folder called \Windows. When you boot into WinXP,
what drive letter do you see for each of these folders?

Nope... two separate partitions. Files are completely separate.

I may be able to help you, but only if you try to answer
my questions as accurately as possible. I will now rephrase them:

a) When you boot into WinXP, what drive letter is the WinXP
partition on?

C: is the only drive that appears.

b) When you boot into WinXP, can you see the WinME installation?
If yes, which drive is it on?

Nope... No trace of the ME installation at all

c) Set your BIOS so that the machine boots into WinME (which,
as you say, will fail). Now boot the machine with a Win98 boot disk
(www.bootdisk.com). Can you see your WinME installation on
drive C:?

It's on one drive, so the BIOS isn't involved at all. I'm setting the
active
partition using FDISK, which sees both partitions fine, but since their
both
primary partitions only one can be set as active.

The next step depends on your answers.

OK, that sounds fine. It seems you installed each OS in its own
primary partition on the one and only drive you have.

Using fdisk to set the active partition is not a particularly good
way to multi-boot. The normal way is to use a boot loader -
I believe that PQMagic has one (which I'm not familiar with),
or XOSL (which is free).

I will now give you some general instructions that you can
try and apply with the PQMagic Boot Loader. If this does not
work then I can give you some specific instructions for XOSL.

1. Install the boot loader.
2. Add WinXP to its menu.
3. Test it.
4. Add WinME to its menu.
5. Test it. It won't work.
6. Boot the machine with a WinME boot disk (www.bootdisk.com)
7. Issue this command: sys c:
This will restore your WinME boot sector on the first partition.

This ***should*** work - however, some fine tuning may be
required.

Note: It is fairly easy to restore boot sectors and boot files,
both for WinME and WinXP. So if it does not work at first,
don't despair, just repost!

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" 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" 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" wrote in message
...
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...;en-us;Q305873


"Noozer" 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!
|
|

BootIt NG *does* let you setup boot menu items, where you can determine
exactly what partition is booted, and what other partitions are to be
included (i.e., other entries in the mbr, or master boot record), and which
ones are hidden, these are called Boot Menu Items. I didn't want to make
the post even longer by covering *every* detail, but simply address the
immediate problem. I was simply illustrating how incredibly easy it is to
solve this particular problem by using BootIt NG because it gives you the
*option* to directly boot any bootable partition from what it calls the
Direct Boot Menu. If all you have is a simple case of two bootable
partitions, and no shared data partition(s), then you don't *have* to setup
individual boot menu items, the Direct Boot Menu automatically hides ALL
other partitions when you double-click any bootable partition.

IOW, it's mindnumbingly easy to use BootIt NG for the simplest cases, you
literally install it, go to the Direct Boot Menu (where you'll see your two
bootable partitions) and assuming each is currently bootable as C:, just
double-click it. If, however, you want to create boot menu items even for
these cases, fine, do so, but you don't *have* to. When you do create boot
menu items, *you* decide what's bootable, and what other partitions will be
seen or not seen based on whether you include them in the boot menu item's
definition. Any partition that's not in the definition is implicitly
hidden, any partitions that *are* in the definition are, of course, not
hidden. By creating the boot menu item, you make the boot manager handle
all the details, rather than trying to muck with details yourself, such as
when using PM.

Jim


"Pegasus (MVP)" wrote in message
...
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" 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, al
l
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" 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" wrote in message
...
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...;en-us;Q305873


"Noozer" 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!
|
|

"Jim" 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.

Uhm... If I wanted a boot manager I would have used the one in XP, or Lilo
from a Linux install or even the OS2 boot manager.

Instead, install BootIt NG in a *third* partiton all by its lonesome,

Why would I want a third partition?

partition you want booted, and AUTOMATICALLY all others are hidden! You
can
believe how incredibly simple it all is.

Of course XP would have still stomped all over the other partition regarless
of having a boot manager installed.

*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

Where did I say I wanted to use ANY boot manager? PM is to move the
partitions around or change their type without losing the data. Only plan on
using it to correct my previous mistake.

People insist on making this stuff a LOT harder than it need be.

You're the one making it more complicated by adding a third partition and
extra piece of software. XP has a perfectly fine boot manager. I just didn't
want *ANY* boot manager.

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).

Do you even know how disk partitioning works? You can only have one active
primary partition. The other primary partitions (up to three) are not seen
by the OS.

NG or even Boot Magic. Install BootIt NG, you get 30 days FREE,

Or use the perfectly fine Manager built into XP for as long as you want for
free.

snip
Do you even know how disk partitioning works? You can only have one active
primary partition. The other primary partitions (up to three) are not seen
by the OS.

Not quite. WinXP can see all four primary partitions if they are
set to "visible". Furthermore, with the right boot manager, you
can boot from any partition on any disk, even from a logical drive.
I have a machine that is set up like so:
- Master disk, logical drive 1: Win2000 (complete with boot files)
- Master disk, logical drive 2: Win98 (complete with boot files)
- Slave disk, primary partition 1: WinXP (complete with boot files)

The native WinXP boot manager can't do this - this is why you
might want to look at third party boot managers.

Ok, let's backtrack a second here.

In your initial post, you indicated a desire to boot both WinMe and WinXP,
correct? That means dual-booting is the problem/issue. So when you say
"Where did I say I wanted to use ANY boot manager", you're absolutely right,
you didn't say that, and THAT'S the problem. You are essentially trying to
dual-boot WITHOUT a boot manager! Instead, you're mucking w/ PM and trying
to fanagle everything MANUALLY. Even assuming you can do it (and for
reasons I won't elaborate here, it's mighty tricky unless you understand all
the issues), its not necessary nor a good idea. You're encountering many of
your current problems ONLY because you insist on avoiding a boot manager.

Your statement: "Is there any way I can repair these installations so both
installs will work?

Yeah, install a boot manager!

But you resist the boot manager, in fact, you specifically insist you never
indicated a desire to use a boot manager. Well, what can I say, you want to
dual boot, a boot manager is specifically designed to avoid the problems
you're currently having, so someone (me) suggests a boot manager, and you
say "I don't want a boot manager", then you list several problems that are
directly related to not using a boot manager, then wonder why people are
suggesting you use a boot manager! And around and around we go.

As far as using the XP boot loader (it's not really a boot "manager", that's
an overstatement), yes, this is an option for managing the dual boot. BUT,
you also indicated in a follow-up post the following:

"I wanted to avoid the XP and ME installations having anything to do with
each other."

Well, that's another problem. When you use the XP loader, it will dual-boot
both OSs, BUT, they will NOT be independent of each other! Let's step thru
the process. Assume WinME is on partition #1 as C:. You now what to
install XP on partition #2. Because the XP loader cannot hide partitions,
the WinME partition will always be exposed when XP boots. This is why the
XP installation will be booted as D:! The XP partition will still see C:
(WinME), albeit as data. If we also assume the XP installation is FAT32
(and I believe WinME sees FAT32 partitions), when WinME boots, it will see
the XP partition as D: (again, as data). IOW, the partitions are NOT hidden
from each other. In fact, the dependencies are much worse than cosmetic.
The XP installation will install all the boot files in C:'s partition! So
now, if you need/want to delete the C: partition some time in the future,
you're in a mess. XP needs C: to be there for its boot files *and* to make
sure that the XP partition remains D:. You can't move the XP partition too
easily either, since it's boot files specifically point to that partition,
and moving it may alter its drive letter assignment (such assignments are
determined, by default, by the BIOS).

I know it's all rather complicated, but the point is, dual-booting either
manually or using the XP boot loader is in direct conflict with your stated
objectives. Yes, the XP loader is FREE, but it's severely limited too. I'm
suggesting BootIt NG, Boot Magic, heck, even the free XOSL boot manager, are
MUCH better alternatives based on your stated objectives. You can NOT have
total partition/OS independence using the XP boot loader. You *may* be able
to achieve this manually using PM, but it's very tricky and takes a deep
understanding of what a boot manager does in order to prevent an even bigger
mess.

To get back to BootIt NG, I suggested a third partition, again, to maintain
your stated desire to keep these OS partitions independent. Now, to be
honest, you can certainly install it (or any other boot manager) into an
existing partition if you like. I don't recommend it, but you can. But if
you create a small third partition ONLY for the boot manager, you won't have
any boot manager dependencies associated with your OS partitions either.
For example, if you install BootIt NG (or any other boot manager) into the
first partition, w/ WinME, it will work fine. BUT, you know have to be
careful not to move, delete, or alter the first partition, lest you risk
mucking up the boot manager! In fact, all the boot manager files/folders
will be EXPOSED whenever the C: partition is visible (which without a boot
manager is ALWAYS). Why take that risk? Why introduce that dependency too
when you don't have to? Instead, keep the boot manager in its own partition
(you have a maximum of four primaries anyway, and currently are using only
two). But again, if you want to use an existing partition for the boot
manager, go ahead, be my guest.

Do you even know how disk partitioning works? You can only have one active
primary partition. The other primary partitions (up to three) are not seen
by the OS.


I've been multi-booting for nearly 12 yrs. (since NT 3.1). I've used
virtually EVERY boot manager ever invented (System Commander, Boot Magic,
BootIt NG, XOSL, MS boot loader, you name it, ALL OF THEM). I've been a
software developer for 20 yrs. I manage 5 machines in my own home office,
including 2 servers (W2K, W2K3) and Win98, XP, NT, and W2K clients for
development purposes. Virtually ALL of them are multi-boot machines, ALL
using BootIt NG (most on this particular boot manager for the past 4 yrs).
Most clients boot at LEAST three or four OS's, including MS-DOS 6.22, MS-DOS
7.0, WinXP, Win98, to name a few. Even have a dual boot of Lindows 4.5 and
Win98 on my laptop.

Yes, I'm am VERY aware of how partitioning works, my knuckles are raw from
many years of being whacked by mistake after mistake, learning the hard way
what does and doesn't work. Trust me, you don't know the half of it, there
are TONS of caveats and gotchas involving multi-booting that I haven't even
touched on, lest this conversation get even longer.

So, back to your statement, an "active" partition is nothing more than a
"mark", an "indicator" on the partition that says "this partition is
bootable". Thats' it, nothing more than that. In fact, nothing prevents
ALL the partitions from being marked "active", you can easily do this (not
sure why you would, but you could) using a partition manager (e.g., BootIt
NG). When the system is booted, the system will only boot the *first*
bootable partition it encounters in the partition table (where the active
indicator resides) of the mbr (master boot record). When you install a boot
manager, like BootIt NG, it automatically changes/moves the active indicator
for you, so that the correct OS is booted. But, unless you take provisions
to hide the other partitions, they *will* be seen *if* the current OS
recognizes those partition types (FAT32, NTFS, etc.). THAT'S WHY YOU NEED A
BOOT MANAGER! The other partitions don't just magically disappear once one
of the partitions is booted. And it doesn't matter a wit whether the other
partitions are marked active or not, that only affects what gets booted.
Once an OS is chosen by the system, the OS will see the other partitions
(according to the conditions I've already stated) irrespective of the active
indicator (it has no bearing on hidden vs. not hidden, none).

The simplest, easiest, most OS independent solution that comports with your
stated objectives is a boot manager. I recommend BootIt NG, it's a steal at
the current price since it functionally replaces Boot Magic, Partition
Magic, and Drive Image, all of them, in one inexpensive, integrated package.
Heck, I bought it four years ago for $30, and haven't had to pay a dime in
upgrade costs in all that time! And there have been MANY enhancements since
that time. Consider what all three of those other packages cost over that
same period, initial and upgrade costs combined. But this is not an
advertisement for BootIt NG, use Boot Magic, XOSL, whatever, almost ANYTHING
is better than attempting this manually OR using the XP boot loader.

I recommend BootIt NG because it's nearly foolproof. Simply install BootIt
NG into its own partition. Assuming WinME is already installed, it will
boot immediately from the Direct Boot Menu. Now Create a new partition for
XP, create a boot menu item, and add the new partition as the bootable
partition to the definition. Set the one-time boot option to "CD", save,
and reboot. Now run your XP install as normal, it will only see the new
partition, so install XP there. When complete, XP will run normally, but
will have overlaid the BootIt NG boot loader. Just insert the BootIt NG
disk, reboot, reactivate it, remove the floppy, and reboot. Now you have
two OS's installed, each bootable directly off the Direct Boot Menu, or
create a boot menu item for WinXP too, if you prefer. Each will boot as C:,
XP will keep its boot files in its own partition, and when booted, will
automatically hide the other partitions (including the one belonging to
BootIt NG). How does BootIt NG do all this magic? Simple, if it's not in
the boot menu definition, then it's not placed in the partition table of the
mbr when the OS is booted, thus the OS never sees it. IOW, BootIt NG
actually manages the "mbr", NOT the partition IDs like other partition or
boot managers. That's why it works so effortlessly. It keeps track of
partition locations for you, and when an OS needs to be booted, "loads up"
the mbr according to the boot menu item's requirements. If something isn't
in the mbr, it just never gets seen.

That's it! No partition inter-dependencies, no mucking w/ active
indicators, no moving partitions around, no boot loader dependencies within
OS partitions, none of that crap, all of that nonsense is gone. Your
grandkids will grow-up to be highly successful, flowers will bloom, the
world will be a happier place, all thanks to you.

Anyway, that's my last word on the subject, if you don't feel that 12+ years
of experience has much to offer, what can I say, keep rolling that snowball
uphill, maybe you know something I don't, I gave it my best shot. Good
luck, god bless, and have a happy life.

HTH

Jim


"Noozer" wrote in message
news:Uu4bc.8433$Pk3.5408@pd7tw1no...

"Jim" 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.

Uhm... If I wanted a boot manager I would have used the one in XP, or Lilo
from a Linux install or even the OS2 boot manager.

Instead, install BootIt NG in a *third* partiton all by its lonesome,

Why would I want a third partition?

partition you want booted, and AUTOMATICALLY all others are hidden! You
can
believe how incredibly simple it all is.

Of course XP would have still stomped all over the other partition
regarless
of having a boot manager installed.

*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

Where did I say I wanted to use ANY boot manager? PM is to move the
partitions around or change their type without losing the data. Only plan
on
using it to correct my previous mistake.

People insist on making this stuff a LOT harder than it need be.

You're the one making it more complicated by adding a third partition and
extra piece of software. XP has a perfectly fine boot manager. I just
didn't
want *ANY* boot manager.

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).

Do you even know how disk partitioning works? You can only have one active
primary partition. The other primary partitions (up to three) are not seen
by the OS.

NG or even Boot Magic. Install BootIt NG, you get 30 days FREE,

Or use the perfectly fine Manager built into XP for as long as you want
for
free.