Make Parallel Installation Independent

[wrt]

Pegasus, I am interested in a resolution.

I made a "parallel" install of XP PRO as a safety measure (I.e., instead
of wiping out C: and making a fresh install on C bcs of other disks
the parallel install was assigned the letter F:.

I realize now that I should have hidden the C: partition or disconnected
the HD (since C: is in fact on another HD) so as to make my fresh
install independent.

But, as you correctly point out, the boot.ini files etc. reside on C: so
my image of F: for future use is not that useful by itself. I could
delete everything from C: except the boot dependent files and then Image
C: so that in the future I could recreate the C: drive (with boot files)
and the F: drive with the OS; but I would rather make the F: drive
completely independent.

Is this possible?

Several things about this intrigued me, could you shed light on what you
know about the following:

1) When XP loads are the boot files "customized" for the OS environment
(number of HDs, partitions, etc.) or are they generic, I.e. simply
copied from the XP install disk to the HD. IOW, I realize that the
boot.ini file is "customized" to the system - that's obvious - but are
ntldr, ntdetect, and any other boot related files also "customized"? If
they are "customized" than that introduces a hurdle; if not, there is
one less thing to work through.

2) Do the boot files HAVE to reside on C: or is it possible to have a
system were C: is all data files with F: (or some other letter)
containing the boot files at its root? (I ask the above w/o reference
to a 3rd party boot loader)

3) What about all the registry and .ini pointers to F: (or whatever
letter the OS' original home was ("where it saw the light of day")?

This hitch has always seemed obvious to me, viz. What do you do with all
the registry pointers to drive X: (any letter other than C not to
mention the pointers in .ini files? They don't magically change upon
moving an OS to another partition/drive.

I have thought about this especially in terms of Images. If you image a
system residing on F: and then someday wish to restore to C: what do you
do with the registry/ .ini files.

Partition Magic has a drive map utility but it's not clear to me that
this would be very useful in the scenario above.

For what it's worth, my thoughts have brought me to the following:

One must either:

a) recreate the original "partition environment"
or
b) search the registry for all the "F:" pointers and change them to
"C:" (or whatever letter the image will reside in) as well as change the
..ini files (are there others?). Some of these changes could probably be
done on an "as needed" basis. IOW, change as much as you can ahead of
time so that you can get into the OS and when something doesn't work as
it should either the system will complain (looking for F or one must
intuitively resolve the issue. But, obviously this requires enough of
the drive letter issues to be resolved to make the system bootable and
useable so that the remaining issues can simply be mopped up.

4) In my case, since the boot files on C: already successfully load the
system that resides on F:, could I copy the boot files from C: to F:
alter the boot.ini file (I'm not even sure that would be needed) and
then (somehow) get the MBR to point to F:? OR, is the whole point that
Win XP will ONLY boot from C:?

Again, thank you for your patience.

 

[Pegasus \(MVP\)]

See below.

Pegasus, I am interested in a resolution.

I made a "parallel" install of XP PRO as a safety measure (I.e., instead
of wiping out C: and making a fresh install on C bcs of other disks
the parallel install was assigned the letter F:.

I realize now that I should have hidden the C: partition or disconnected
the HD (since C: is in fact on another HD) so as to make my fresh
install independent.

But, as you correctly point out, the boot.ini files etc. reside on C: so
my image of F: for future use is not that useful by itself. I could
delete everything from C: except the boot dependent files and then Image
C: so that in the future I could recreate the C: drive (with boot files)
and the F: drive with the OS; but I would rather make the F: drive
completely independent.

Is this possible?

I'm afraid not. You installed WinXP on drive F:, and drive F: it has
to be until you re-install it. Your basic idea of creating another instance
of WinXP for future use was sound, but you should have ensured
that it is installed on drive C:, either by disconnecting your primary
disk or by using a boot manager such as XOSL to hide the other
partitions.

On the other hand, why not save your current WinXP installation
(the one on drive C for a rainy day?

Several things about this intrigued me, could you shed light on what you
know about the following:

1) When XP loads are the boot files "customized" for the OS environment
(number of HDs, partitions, etc.) or are they generic, I.e. simply
copied from the XP install disk to the HD. IOW, I realize that the
boot.ini file is "customized" to the system - that's obvious - but are
ntldr, ntdetect, and any other boot related files also "customized"? If
they are "customized" than that introduces a hurdle; if not, there is
one less thing to work through.

c:\boot.ini reflects the partition on which WinXP is installed. I believe
that there are also some other files in the Windows installation folder
that reflect the current drive letter. However, most files in the Windows
folder are drive letter independent.

2) Do the boot files HAVE to reside on C: or is it possible to have a
system were C: is all data files with F: (or some other letter)
containing the boot files at its root? (I ask the above w/o reference
to a 3rd party boot loader)

The boot files must reside in the active partition. Some boot loaders
(e.g. XOSL) can arrange it so that the boot files may reside on the
same drive as the OS (i.e. on drive F: in your case). This is my preferred
multi-booting solution, because it keeps everthing on the one drive.

3) What about all the registry and .ini pointers to F: (or whatever
letter the OS' original home was ("where it saw the light of day")?

They must be maintained. If WinXP is installed on drive F: then it
must always run on drive F:.

This hitch has always seemed obvious to me, viz. What do you do with all
the registry pointers to drive X: (any letter other than C not to
mention the pointers in .ini files? They don't magically change upon
moving an OS to another partition/drive.

Correct. However, it is possible to move an OS to any other
drive, yet maintain the drive letter.

I have thought about this especially in terms of Images. If you image a
system residing on F: and then someday wish to restore to C: what do you
do with the registry/ .ini files.

You leave the drive letter as F:, regardless of the physical partition.

Partition Magic has a drive map utility but it's not clear to me that
this would be very useful in the scenario above.

I don't think it helps you in this scenario.

For what it's worth, my thoughts have brought me to the following:

One must either:

a) recreate the original "partition environment"
Yes.

or
b) search the registry for all the "F:" pointers and change them to
"C:" (or whatever letter the image will reside in) as well as change the
.ini files (are there others?).

This is a recipe for a disaster.

Some of these changes could probably be
done on an "as needed" basis. IOW, change as much as you can ahead of
time so that you can get into the OS and when something doesn't work as
it should either the system will complain (looking for F or one must
intuitively resolve the issue. But, obviously this requires enough of
the drive letter issues to be resolved to make the system bootable and
useable so that the remaining issues can simply be mopped up.

4) In my case, since the boot files on C: already successfully load the
system that resides on F:, could I copy the boot files from C: to F:
alter the boot.ini file (I'm not even sure that would be needed) and
then (somehow) get the MBR to point to F:? OR, is the whole point that
Win XP will ONLY boot from C:?

More or less. Here is the complete recipe:
1. Copy ntldr, ntdetect.com & boot.ini from C: to F:.
2. Save an image of drive F: (just in case . . .).
3. Make certain registry modifications.
4. Use an imaging program to copy F: to C:.
5. Perhaps fix the WinNT boot sector with fixboot under the Recovery
Console.
The MBR will run the code in the boot sector of drive C: (no change
here), which will invoke c:\ntldr. The machine will boot up with the OS
located in the first partition, which will still appear as drive F:. Your
old drive F: will appear as drive X:.

Again, thank you for your patience.

You're welcome.

 

[wrt]

Just to be clear:

I'm afraid not.

The critical issue being the registry pointers to F:? I do agree that
this is a critical issue; but are there any other critical issues that
are involved in the diagnosis: "I'm afraid not." ?

You installed WinXP on drive F:, and drive F: it has

to be until you re-install it. Your basic idea of creating another instance
of WinXP for future use was sound, but you should have ensured
that it is installed on drive C:, either by disconnecting your primary
disk or by using a boot manager such as XOSL to hide the other
partitions.

On the other hand, why not save your current WinXP installation
(the one on drive C for a rainy day?

My present C: installation is "worn out"/ too unstable to be of use
except in a real disaster

More or less. Here is the complete recipe:
1. Copy ntldr, ntdetect.com & boot.ini from C: to F:.
2. Save an image of drive F: (just in case . . .).
3. Make certain registry modifications.

Could you elaborate?

4. Use an imaging program to copy F: to C:.

I use Acronis True Image. Never tried it with Acronis but I it is a
sound piece of software - should work fine.

5. Perhaps fix the WinNT boot sector with fixboot under the Recovery
Console.
The MBR will run the code in the boot sector of drive C: (no change
here), which will invoke c:\ntldr.

This "c:\ntldr" is one and the same as the ntldr which is to be copied
from my present C: to F: and finds it's way back to C: because I then
copy F: to C: with imaging software? Correct?

The machine will boot up with the OS

located in the first partition, which will still appear as drive F:

I'm sorry, I don't quite get this. Is not the first partition already
C:? The very C: that contains c:\ntldr which is invoked by the MBR? If
so how does it become F:?


"Your old drive F: will appear as drive X:."
I understand what you are saying here: the reassignment of drive
letters.

 

[Pegasus \(MVP\)]

See below.

Just to be clear:



The critical issue being the registry pointers to F:? I do agree that
this is a critical issue; but are there any other critical issues that
are involved in the diagnosis: "I'm afraid not." ?

The numerous registry pointers are the main problem.
If there are files that have F: embedded, they would
be a problem too.

You installed WinXP on drive F:, and drive F: it has
My present C: installation is "worn out"/ too unstable to be of use
except in a real disaster

Could you elaborate?

I developed this method only two days ago, as a result
of that other worn-out thread. I have not yet tested it
extensively. Before I make it public in this forum, I would
like to see some results on PCs other than my own. If
you are interested to try it on your own PC then drop
me a line with your EMail address. You can use this address:
(e-mail address removed). Replace every "z" with an "s".

I use Acronis True Image. Never tried it with Acronis but I it is a
sound piece of software - should work fine.

I know it well.

This "c:\ntldr" is one and the same as the ntldr which is to be copied
from my present C: to F: and finds it's way back to C: because I then
copy F: to C: with imaging software? Correct?
Correct.

The machine will boot up with the OS
I'm sorry, I don't quite get this. Is not the first partition already
C:? The very C: that contains c:\ntldr which is invoked by the MBR? If
so how does it become F:?

You use Acronis to copy the fourth partition (F to the first
partition (C. However, because of the registry hack in Step 3,
the first partition will now appear as drive F:. This is how you
avoid the drive letter problem that would otherwise affect you..

Putting it in other words: You move your WinXP installation
to a different partition but you are preserving the drive letter.
Your system partition will continue appear as drive F:!

"Your old drive F: will appear as drive X:."
I understand what you are saying here: the reassignment of drive
letters.

By the way - I omitted one step in my instructions:
=====================
After copying c:\boot.ini to f:\, you must adjust it so that
it points to the first partition. Below is an example.

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

In your case you probably have "partition(4)". You MUST change it!