Partitions, Image for Dos

E

Ed H

Hey:

I have created 2 images of my XP setups using Image for Windows/Dos just
after a pristine install and setup. Both were created from partition 1, one
is XP Home and the other is XP Pro. Lately I've been wanting to use both as
a dual-boot setup but I can't figure out how to restore one of them to a
second partition without the boot goin' haywire on me. I think I would
simply edit boot.ini but how can that be done?

Thank you,
TTs
 
P

Pegasus \(MVP\)

Ed H said:
Hey:

I have created 2 images of my XP setups using Image for Windows/Dos just
after a pristine install and setup. Both were created from partition 1, one
is XP Home and the other is XP Pro. Lately I've been wanting to use both as
a dual-boot setup but I can't figure out how to restore one of them to a
second partition without the boot goin' haywire on me. I think I would
simply edit boot.ini but how can that be done?

Thank you,
TTs

You cannot do this with the native WinXP boot loader; you need a
third-party boot loader instead. Here is what I recommend:
1. Create a 15 MByte primary partition.
2. Load the XOSL boot loader into it. It's free.
3. Create a suitably sized primary partition for WinXP Home,
and place WinXP Home into it from your image file.
4. Create a suitably sized primary partition for WinXP Prof,
and place WinXP Prof into it from your image file.
5. Create a logical drive for your shared data.
6. Launch XOSL and include WinXP Home and WinXP Pro
in its menu.
7. Customise XOSL so that it always shows one OS and
hides the other. Keep the logical data drive visible for
both OSs.
 
J

Jetro

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro"
/fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home"
/fastdetect

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q289022
HOW TO: Edit the Boot.ini File in Windows XP

discusses how to use the bootcfg.exe utility in details.
 
P

Pegasus \(MVP\)

Jetro said:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro"
/fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home"
/fastdetect

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q289022
HOW TO: Edit the Boot.ini File in Windows XP

discusses how to use the bootcfg.exe utility in details.

Since both images were created on partition No. 1, they must
be run on drive C:. If they are now installed on the same disk
in different partitions, one of them will appear on drive D:. It
won't work. This situation cannot be resolved with boot.ini,
only with a third-party boot loader (or by manually hiding and
unhiding partitions).
 
E

Ed H

I have Partition Magic which includes Boot Magic and Pqboot. I figured on
using Pqboot. I haven't actually tried to boot yet, I installed the image to
the other partition but when I tried to look up the setup through PM, PM
would not open 'unable to read disk. . .'

Ed


Pegasus (MVP) said:
Jetro said:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro"
/fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home"
/fastdetect

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q289022
HOW TO: Edit the Boot.ini File in Windows XP

discusses how to use the bootcfg.exe utility in details.

Since both images were created on partition No. 1, they must
be run on drive C:. If they are now installed on the same disk
in different partitions, one of them will appear on drive D:. It
won't work. This situation cannot be resolved with boot.ini,
only with a third-party boot loader (or by manually hiding and
unhiding partitions).
 
J

Jetro

If you clone the partitions the active system will run from C: drive.
Certainly if you'd install dual-boot system one-by-one then one of the OS
will run from D: or any other than C: drive.
 
E

Ed H

How do you hide and unhide partitions manually?


Pegasus (MVP) said:
Jetro said:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro"
/fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home"
/fastdetect

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q289022
HOW TO: Edit the Boot.ini File in Windows XP

discusses how to use the bootcfg.exe utility in details.

Since both images were created on partition No. 1, they must
be run on drive C:. If they are now installed on the same disk
in different partitions, one of them will appear on drive D:. It
won't work. This situation cannot be resolved with boot.ini,
only with a third-party boot loader (or by manually hiding and
unhiding partitions).
 
I

I'm Dan

Jetro said:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft
Windows XP Pro" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft
Windows XP Home" /fastdetect

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q289022
HOW TO: Edit the Boot.ini File in Windows XP

discusses how to use the bootcfg.exe utility in details.


Ed H said:
I have Partition Magic which includes Boot Magic and Pqboot.
I figured on using Pqboot. I haven't actually tried to boot yet, I
installed the image to the other partition but when I tried to look
up the setup through PM, PM would not open 'unable to read disk. . .'

Ed, editing the boot.ini definitely will not work. Since both installations
were created as fully independent installations, they cannot be controlled
through a single boot.ini file. Like Pegasus, for a third-party boot
manager I prefer XOSL, which is far superior to BootMagic, but pqboot will
work just fine, too - I often use it to test the OS's before installing
XOSL.

You also have two "gotchas" that will trip up your second XP: the partition
number in boot.ini has to be changed, and the registry's [MountedDevices]
key will have the wrong starting location of the partition. Both can be
corrected with a little surgery, but . . .

.. . . first things first: the 'unable to read disk' error. You shouldn't
be getting that. We don't know whether this is a PM error or an ImageForDOS
error, so we don't yet know if your second partition is even legitimately
created. Talk of bootloaders and registry editing are premature if you have
a fundamental flaw in the partition structure. What version of PM? Are you
running PM from floppy or from within XP? Did you try looking at the
partition setup in BootIt-NG? Did PM work properly before using IFD to
restore partition 2? If so, you may need to move this over to TeraByte
Unlimited's IFD newsgroup to resolve that issue first.
 
E

Ed H

Thanks Dan:

I probably shouldn't write an error message when I don't remember it
exactly. Both OSs, when installed to partition 1, work perfect (one at a
time of course). I think that restoring an image to partition 2 is forcing
something. PQboot, (which gave a similar error warning), is not showing the
volume labels, as it normally does, and shows both partitions as visible. My
old set up, which was created on that partition, was hidden before the
restoration.

Ed


I'm Dan said:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft
Windows XP Pro" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft
Windows XP Home" /fastdetect

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q289022
HOW TO: Edit the Boot.ini File in Windows XP

discusses how to use the bootcfg.exe utility in details.


Ed H said:
I have Partition Magic which includes Boot Magic and Pqboot.
I figured on using Pqboot. I haven't actually tried to boot yet, I
installed the image to the other partition but when I tried to look
up the setup through PM, PM would not open 'unable to read disk. . .'

Ed, editing the boot.ini definitely will not work. Since both installations
were created as fully independent installations, they cannot be controlled
through a single boot.ini file. Like Pegasus, for a third-party boot
manager I prefer XOSL, which is far superior to BootMagic, but pqboot will
work just fine, too - I often use it to test the OS's before installing
XOSL.

You also have two "gotchas" that will trip up your second XP: the partition
number in boot.ini has to be changed, and the registry's [MountedDevices]
key will have the wrong starting location of the partition. Both can be
corrected with a little surgery, but . . .

. . . first things first: the 'unable to read disk' error. You shouldn't
be getting that. We don't know whether this is a PM error or an ImageForDOS
error, so we don't yet know if your second partition is even legitimately
created. Talk of bootloaders and registry editing are premature if you have
a fundamental flaw in the partition structure. What version of PM? Are you
running PM from floppy or from within XP? Did you try looking at the
partition setup in BootIt-NG? Did PM work properly before using IFD to
restore partition 2? If so, you may need to move this over to TeraByte
Unlimited's IFD newsgroup to resolve that issue first.
 
E

Ed H

Okay,

PQBoot says: "Error #5017 building the partition list on disk #0"
PM says: "Init failed: Error 117. Partition's drive letter cannot be
identified" and if I restore the old image, created in Part.2, all is fine
again.

Ed


Ed H said:
Thanks Dan:

I probably shouldn't write an error message when I don't remember it
exactly. Both OSs, when installed to partition 1, work perfect (one at a
time of course). I think that restoring an image to partition 2 is forcing
something. PQboot, (which gave a similar error warning), is not showing the
volume labels, as it normally does, and shows both partitions as visible. My
old set up, which was created on that partition, was hidden before the
restoration.

Ed


I'm Dan said:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft
Windows XP Pro" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft
Windows XP Home" /fastdetect

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q289022
HOW TO: Edit the Boot.ini File in Windows XP

discusses how to use the bootcfg.exe utility in details.
Since both images were created on partition No. 1, they must
be run on drive C:. If they are now installed on the same disk
in different partitions, one of them will appear on drive D:. It
won't work. This situation cannot be resolved with boot.ini,
only with a third-party boot loader (or by manually hiding and
unhiding partitions).


Ed H said:
I have Partition Magic which includes Boot Magic and Pqboot.
I figured on using Pqboot. I haven't actually tried to boot yet, I
installed the image to the other partition but when I tried to look
up the setup through PM, PM would not open 'unable to read disk. . .'

Ed, editing the boot.ini definitely will not work. Since both installations
were created as fully independent installations, they cannot be controlled
through a single boot.ini file. Like Pegasus, for a third-party boot
manager I prefer XOSL, which is far superior to BootMagic, but pqboot will
work just fine, too - I often use it to test the OS's before installing
XOSL.

You also have two "gotchas" that will trip up your second XP: the partition
number in boot.ini has to be changed, and the registry's [MountedDevices]
key will have the wrong starting location of the partition. Both can be
corrected with a little surgery, but . . .

. . . first things first: the 'unable to read disk' error. You shouldn't
be getting that. We don't know whether this is a PM error or an ImageForDOS
error, so we don't yet know if your second partition is even legitimately
created. Talk of bootloaders and registry editing are premature if you have
a fundamental flaw in the partition structure. What version of PM? Are you
running PM from floppy or from within XP? Did you try looking at the
partition setup in BootIt-NG? Did PM work properly before using IFD to
restore partition 2? If so, you may need to move this over to TeraByte
Unlimited's IFD newsgroup to resolve that issue first.
 
P

Pegasus \(MVP\)

1. Boot the machine with a Win98 boot disk (www.bootdisk.com).
2. Run ptedit.exe (ftp://ftp.powerquest.com/pub/utilities/).
3. Select the partition you wish to hide.
4. Change its type. Each partition type has two codes: One for "visible",
the other for "invisible".
5. Run fdisk.exe
6. Set the active partition.

The process is rather tedious. Using PQMagic.exe makes it somewhat less so.


Ed H said:
How do you hide and unhide partitions manually?


Pegasus (MVP) said:
Jetro said:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro"
/fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home"
/fastdetect

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q289022
HOW TO: Edit the Boot.ini File in Windows XP

discusses how to use the bootcfg.exe utility in details.

Since both images were created on partition No. 1, they must
be run on drive C:. If they are now installed on the same disk
in different partitions, one of them will appear on drive D:. It
won't work. This situation cannot be resolved with boot.ini,
only with a third-party boot loader (or by manually hiding and
unhiding partitions).
 
I

I'm Dan

Ed H said:
Both OSs, when installed to partition 1, work perfect (one at a time
of course). I think that restoring an image to partition 2 is forcing
something. PQboot, (which gave a similar error warning), is not
showing the volume labels, as it normally does, and shows both
partitions as visible. My old set up, which was created on that
partition, was hidden before the restoration.
...
PQBoot says: "Error #5017 building the partition list on disk #0"
PM says: "Init failed: Error 117. Partition's drive letter cannot be
identified" and if I restore the old image, created in Part.2, all is
fine again.

What version of PM? Are you running PM from floppy or from within XP? Did
you try looking at the partition setup in BootIt-NG?
 
E

Ed H

What version of PM? Are you running PM from floppy or from within XP? Did
you try looking at the partition setup in BootIt-NG?

I am running PM 8, these errors are coming up while I'm in Windows, I don't
want to try a boot till I find out more of what to expect. I've used PM in
DOS before but not with this issue. I don't have BING.
 
E

Ed H

Would this work? Using PM wizard to copy a partition, I copy my XP Pro setup
on Partition, to Partition 2, then restore my XP Home image to Partition 1.
Would that work and if I then created an image of Partition 2 (which would
now be Pro) would that work in Partition 2 for now on, if I need to restore
again in the future?

Thanks for all your time.

Ed
 
I

I'm Dan

Ed H said:
I am running PM 8, these errors are coming up while I'm in
Windows, I don't want to try a boot till I find out more of what
to expect. I've used PM in DOS before but not with this issue.
I don't have BING.

Okay, I suspected you might be running PM under Windows. That has never
been a very reliable procedure. PM8 is modern enough to handle your system,
but try running it from DOS (boot floppies, aka, "rescue disks") and see if
you don't get the Error 117. I assume you know that BING has a 30-day free
trial period, so it can be downloaded and used to check out the partitions.
Boot from the BING floppy and click [Cancel], which will bypass installing
BING and go straight to the Maintenance menu.

The intent is to see if DOS-PM or BING corroborates Win-PM's claim of a
problem with the IFD-restored partition. If they don't, and Win-PM is the
only one that has a problem, then I think you can ignore the Error 117 and
move on to fixing the two issues (boot.ini ARCpath and MountedDevices
registry key) that you need to understand to get your second partition
working. Using IFD to merely restore XP to a different partition than it
came from will not work without understanding these points. But first you
should put to rest this Error 117.

BTW, are the XP partitions NTFS or FAT32?
 
E

Ed H

Sorry I'm a bit side tracked with anther issue. PM is okay in Dos, I did not
download BING, XP computer management shows the hidden partition as 'hidden'
(unknown). I use all ntfs partitions.

Ed


I'm Dan said:
Ed H said:
I am running PM 8, these errors are coming up while I'm in
Windows, I don't want to try a boot till I find out more of what
to expect. I've used PM in DOS before but not with this issue.
I don't have BING.

Okay, I suspected you might be running PM under Windows. That has never
been a very reliable procedure. PM8 is modern enough to handle your system,
but try running it from DOS (boot floppies, aka, "rescue disks") and see if
you don't get the Error 117. I assume you know that BING has a 30-day free
trial period, so it can be downloaded and used to check out the partitions.
Boot from the BING floppy and click [Cancel], which will bypass installing
BING and go straight to the Maintenance menu.

The intent is to see if DOS-PM or BING corroborates Win-PM's claim of a
problem with the IFD-restored partition. If they don't, and Win-PM is the
only one that has a problem, then I think you can ignore the Error 117 and
move on to fixing the two issues (boot.ini ARCpath and MountedDevices
registry key) that you need to understand to get your second partition
working. Using IFD to merely restore XP to a different partition than it
came from will not work without understanding these points. But first you
should put to rest this Error 117.

BTW, are the XP partitions NTFS or FAT32?
 
I

I'm Dan

I'm Dan said:
. . . You also have two "gotchas" that will trip up your second XP:
the partition number in boot.ini has to be changed, and the registry's
[MountedDevices] key will have the wrong starting location of
the partition. Both can be corrected with a little surgery . . .

Ed H said:
Sorry I'm a bit side tracked with anther issue. PM is okay in Dos,
I did not download BING, XP computer management shows the
hidden partition as 'hidden' (unknown). I use all ntfs partitions.

Okay, if DOS-PM shows no error, I think the Error 117 was a Windows-PM bug
and not a genuine partition error. I think it's safe to ignore the Win-PM
error and go on to the real issue(s), so don't bother to download BING just
for the sake of additional corroboration.

I've requoted the relevant parts of the earlier posts as a refresher. Copy
the steps below, and when you get time to get back to this project, here are
the steps to follow. I'll assume the second partition should be XP Pro, but
substitute accordingly if you want it the other way around:

(1) Restore XP Pro image to partition 1, then boot into it.

(2) Remove the [MountedDevices] entries from the registry - see
www.goodells.net/multiboot/notes.htm#04 for details. (Don't worry about the
paging file - it's usually only a problem with Win2K). XP will rebuild this
key when it reboots, but we want an image *without* the key values, so as
soon as you remove them, make a new image of the XP Pro partition.

(3) Restore XP Home image to partition 1. Restore XP Pro image to partition
2.

(4) Download two free DOS utilities, editbini and ptedit, and put them on a
floppy. See www.goodells.net/multiboot/tools.htm for sources.

(5) Boot from floppy and run ptedit. It's possible for the partitions to
be listed out of order in the partition table, so this step is just to
confirm whether the partition table is in the same order as the actual
partitions. If partition 1 starts at an earlier cylinder number than
partition 2, all is as expected, and proceed to next step. If not, post
back for revised instructions.

(6) Each partition will have its own boot.ini file. Each boot.ini must
point to *its own partition*. Boot from floppy and run editbini. See
www.goodells.net/multiboot/editbini.htm for details. Select the first
partition and check its boot.ini. It probably says "...partition(1)...",
which is correct for partition 1, so leave it be and exit.

(7) Run editbini again, this time select the second partition, and look at
its boot.ini. This one should point to "...partition(2)...", but most
likely will show "...partition(1)..." because that was where the partition
was when the image was made. Change '1' to '2' (two places), and exit,
saving your changes.

(8) Test both partitions. Use pqboot from a boot floppy to set either
partition 1 or partition 2 active, and reboot. Note pqboot will
automatically "hide" the alternate partition from the active one, so you
don't need to go through Pegasus' roundabout step-by-step posted earlier.
Check Disk Mgmt in each to make sure the proper partition, either first or
second, is designated as 'C:' and as the "system partition". The alternate
(non-booted) partition should show as "Healthy (unknown)", with no drive
letter. Note the table at the top of the window is in *alphabetical* order,
so look at the *bar chart in the middle*, which shows the physical partition
layout.

If all is well, you now have two completely independent installations. The
keys to cloning (or imaging/restoring) is making sure the boot.ini enclosed
in the partition points to itself, and making sure the MountedDevices key
doesn't "remember" partition 1 as "drive C:".
 
E

Ed H

Thanks IAD, this is very clearly laid out and I understand each point. Stay
tuned so that I can let you know how it works.

Ed

I'm Dan said:
I'm Dan said:
. . . You also have two "gotchas" that will trip up your second XP:
the partition number in boot.ini has to be changed, and the registry's
[MountedDevices] key will have the wrong starting location of
the partition. Both can be corrected with a little surgery . . .

Ed H said:
Sorry I'm a bit side tracked with anther issue. PM is okay in Dos,
I did not download BING, XP computer management shows the
hidden partition as 'hidden' (unknown). I use all ntfs partitions.

Okay, if DOS-PM shows no error, I think the Error 117 was a Windows-PM bug
and not a genuine partition error. I think it's safe to ignore the Win-PM
error and go on to the real issue(s), so don't bother to download BING just
for the sake of additional corroboration.

I've requoted the relevant parts of the earlier posts as a refresher. Copy
the steps below, and when you get time to get back to this project, here are
the steps to follow. I'll assume the second partition should be XP Pro, but
substitute accordingly if you want it the other way around:

(1) Restore XP Pro image to partition 1, then boot into it.

(2) Remove the [MountedDevices] entries from the registry - see
www.goodells.net/multiboot/notes.htm#04 for details. (Don't worry about the
paging file - it's usually only a problem with Win2K). XP will rebuild this
key when it reboots, but we want an image *without* the key values, so as
soon as you remove them, make a new image of the XP Pro partition.

(3) Restore XP Home image to partition 1. Restore XP Pro image to partition
2.

(4) Download two free DOS utilities, editbini and ptedit, and put them on a
floppy. See www.goodells.net/multiboot/tools.htm for sources.

(5) Boot from floppy and run ptedit. It's possible for the partitions to
be listed out of order in the partition table, so this step is just to
confirm whether the partition table is in the same order as the actual
partitions. If partition 1 starts at an earlier cylinder number than
partition 2, all is as expected, and proceed to next step. If not, post
back for revised instructions.

(6) Each partition will have its own boot.ini file. Each boot.ini must
point to *its own partition*. Boot from floppy and run editbini. See
www.goodells.net/multiboot/editbini.htm for details. Select the first
partition and check its boot.ini. It probably says "...partition(1)...",
which is correct for partition 1, so leave it be and exit.

(7) Run editbini again, this time select the second partition, and look at
its boot.ini. This one should point to "...partition(2)...", but most
likely will show "...partition(1)..." because that was where the partition
was when the image was made. Change '1' to '2' (two places), and exit,
saving your changes.

(8) Test both partitions. Use pqboot from a boot floppy to set either
partition 1 or partition 2 active, and reboot. Note pqboot will
automatically "hide" the alternate partition from the active one, so you
don't need to go through Pegasus' roundabout step-by-step posted earlier.
Check Disk Mgmt in each to make sure the proper partition, either first or
second, is designated as 'C:' and as the "system partition". The alternate
(non-booted) partition should show as "Healthy (unknown)", with no drive
letter. Note the table at the top of the window is in *alphabetical* order,
so look at the *bar chart in the middle*, which shows the physical partition
layout.

If all is well, you now have two completely independent installations. The
keys to cloning (or imaging/restoring) is making sure the boot.ini enclosed
in the partition points to itself, and making sure the MountedDevices key
doesn't "remember" partition 1 as "drive C:".
 
E

Ed H

Wow! Smooth as silk! You just saved me hoouurrss of work. Thanks for your
clear and dedicated effort.
--
Ed H
Dell Dimension 4550, WinXP Home SP1 (and Pro)
60 Gig. HD, 512 DDR, Pentium IV 2.40 GHz.


Ed H said:
Thanks IAD, this is very clearly laid out and I understand each point. Stay
tuned so that I can let you know how it works.

Ed

I'm Dan said:
I have created 2 images of my XP setups using Image for
Windows/Dos just after a pristine install and setup. Both
were created from partition 1, one is XP Home and the
other is XP Pro. Lately I've been wanting to use both as
a dual-boot setup but I can't figure out how to restore one
of them to a second partition without the boot goin'
haywire on me . . .

. . . Both OSs, when installed to partition 1, work perfect
(one at a time of course). I think that restoring an image
to partition 2 is forcing something . . .
. . . You also have two "gotchas" that will trip up your second XP:
the partition number in boot.ini has to be changed, and the registry's
[MountedDevices] key will have the wrong starting location of
the partition. Both can be corrected with a little surgery . . .

Ed H said:
Sorry I'm a bit side tracked with anther issue. PM is okay in Dos,
I did not download BING, XP computer management shows the
hidden partition as 'hidden' (unknown). I use all ntfs partitions.

Okay, if DOS-PM shows no error, I think the Error 117 was a Windows-PM bug
and not a genuine partition error. I think it's safe to ignore the Win-PM
error and go on to the real issue(s), so don't bother to download BING just
for the sake of additional corroboration.

I've requoted the relevant parts of the earlier posts as a refresher. Copy
the steps below, and when you get time to get back to this project, here are
the steps to follow. I'll assume the second partition should be XP Pro, but
substitute accordingly if you want it the other way around:

(1) Restore XP Pro image to partition 1, then boot into it.

(2) Remove the [MountedDevices] entries from the registry - see
www.goodells.net/multiboot/notes.htm#04 for details. (Don't worry about the
paging file - it's usually only a problem with Win2K). XP will rebuild this
key when it reboots, but we want an image *without* the key values, so as
soon as you remove them, make a new image of the XP Pro partition.

(3) Restore XP Home image to partition 1. Restore XP Pro image to partition
2.

(4) Download two free DOS utilities, editbini and ptedit, and put them
on
a
floppy. See www.goodells.net/multiboot/tools.htm for sources.

(5) Boot from floppy and run ptedit. It's possible for the partitions to
be listed out of order in the partition table, so this step is just to
confirm whether the partition table is in the same order as the actual
partitions. If partition 1 starts at an earlier cylinder number than
partition 2, all is as expected, and proceed to next step. If not, post
back for revised instructions.

(6) Each partition will have its own boot.ini file. Each boot.ini must
point to *its own partition*. Boot from floppy and run editbini. See
www.goodells.net/multiboot/editbini.htm for details. Select the first
partition and check its boot.ini. It probably says "...partition(1)...",
which is correct for partition 1, so leave it be and exit.

(7) Run editbini again, this time select the second partition, and look at
its boot.ini. This one should point to "...partition(2)...", but most
likely will show "...partition(1)..." because that was where the partition
was when the image was made. Change '1' to '2' (two places), and exit,
saving your changes.

(8) Test both partitions. Use pqboot from a boot floppy to set either
partition 1 or partition 2 active, and reboot. Note pqboot will
automatically "hide" the alternate partition from the active one, so you
don't need to go through Pegasus' roundabout step-by-step posted earlier.
Check Disk Mgmt in each to make sure the proper partition, either first or
second, is designated as 'C:' and as the "system partition". The alternate
(non-booted) partition should show as "Healthy (unknown)", with no drive
letter. Note the table at the top of the window is in *alphabetical* order,
so look at the *bar chart in the middle*, which shows the physical partition
layout.

If all is well, you now have two completely independent installations. The
keys to cloning (or imaging/restoring) is making sure the boot.ini enclosed
in the partition points to itself, and making sure the MountedDevices key
doesn't "remember" partition 1 as "drive C:".
 
E

Ed H

Checked everything out, only one glitch, PM still displays that error and
won't open, pqboot in dos through windows displays it's error but does work.
Tried to delete the reg. key again and reboot but that did not do it, hum.

Ed


Ed H said:
Wow! Smooth as silk! You just saved me hoouurrss of work. Thanks for your
clear and dedicated effort.
--
Ed H
Dell Dimension 4550, WinXP Home SP1 (and Pro)
60 Gig. HD, 512 DDR, Pentium IV 2.40 GHz.


Ed H said:
Thanks IAD, this is very clearly laid out and I understand each point. Stay
tuned so that I can let you know how it works.

Ed

I'm Dan said:
I have created 2 images of my XP setups using Image for
Windows/Dos just after a pristine install and setup. Both
were created from partition 1, one is XP Home and the
other is XP Pro. Lately I've been wanting to use both as
a dual-boot setup but I can't figure out how to restore one
of them to a second partition without the boot goin'
haywire on me . . .

. . . Both OSs, when installed to partition 1, work perfect
(one at a time of course). I think that restoring an image
to partition 2 is forcing something . . .

. . . You also have two "gotchas" that will trip up your second XP:
the partition number in boot.ini has to be changed, and the registry's
[MountedDevices] key will have the wrong starting location of
the partition. Both can be corrected with a little surgery . . .

Sorry I'm a bit side tracked with anther issue. PM is okay in Dos,
I did not download BING, XP computer management shows the
hidden partition as 'hidden' (unknown). I use all ntfs partitions.

Okay, if DOS-PM shows no error, I think the Error 117 was a Windows-PM bug
and not a genuine partition error. I think it's safe to ignore the Win-PM
error and go on to the real issue(s), so don't bother to download BING just
for the sake of additional corroboration.

I've requoted the relevant parts of the earlier posts as a refresher. Copy
the steps below, and when you get time to get back to this project,
here
are
the steps to follow. I'll assume the second partition should be XP
Pro,
but
substitute accordingly if you want it the other way around:

(1) Restore XP Pro image to partition 1, then boot into it.

(2) Remove the [MountedDevices] entries from the registry - see
www.goodells.net/multiboot/notes.htm#04 for details. (Don't worry
about
the
paging file - it's usually only a problem with Win2K). XP will
rebuild
this
key when it reboots, but we want an image *without* the key values, so as
soon as you remove them, make a new image of the XP Pro partition.

(3) Restore XP Home image to partition 1. Restore XP Pro image to partition
2.

(4) Download two free DOS utilities, editbini and ptedit, and put them
on
a
floppy. See www.goodells.net/multiboot/tools.htm for sources.

(5) Boot from floppy and run ptedit. It's possible for the
partitions
look
first
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top