7even System partition letter change.

Hello everyone on theese awesome forums, another troll here! :)

The system:
Drive 1: vista boot loader, vista32, two partitions (vista on C, some stuff on D), both NTFS
drive 2: broken grub loader (never mind actually), one ntfs partition with some porn, games, and other usual stuff . named E.

so then, i copy the 7100 x64 distr into my flash drive, boot it, and install our beloved 7even into the drive 2. it does not ask me anything, write its boot loader to drive 1, lets me choose which OS to boot into each time... perfect. BUT(T):
7even named her own partition C, while drive 1 partitions became D and E. i swapped last two easily, using 7even's disk management utility. that's 1 of 3 and that's not enough. i really want 7even's partition to have the same letter as in vista. i even googled it, and didn't find any answers.
7even is still unconfigured, so it would not be a problem to reinstall it.
even more, if it's really necesarry, i can move all of drive 1's data somewhere else, so i can format it.
any help please please?

Basically, i want my seven to be installed on drive 2, with its system partition named "E", just like it is in vista.

once again, if you want:
when i login to vista, i see: drive1{C;D}, drive2{E}, system vista partition is C, and that is RIGHT.
when i login to seven, i see: drive1{E;D}, drive2{C}, system seven partition is C, and that SUCKS.

what i want to see is:
i login to seven, i see drive1{C;D}, drive2{E}, system seven partition is E.

seems like you got me wrong. my 7even distr were downloaded from microsoft.com, it's perfect. and when i install it, i could only choose the destination partition (the only one on drive2), but could not choose which letter that partition should have, атв that's what i want to change.

you ask why?
because i don't want to have two ridiculously large "program files" folders on two different drives. in current situation, when i login into Seven, i cannot run almost any software from disk1partition1(E), because its internal links are made for disk C (from vista).
and as well, my music player likes the music to be on drive E, while in Seven, the music drive suddenly becomes C.
is my point clear now?

i believe Paragon disk manager will just broke my Seven installation. and re-instalation would not have any positive effect.

Although this would be possible in theory I personally believe that the amount of work required to achieve and more importantly to maintain this would be a difficult ongoing task.

This does not involve changing the drive used by the OS but pointing the system to a new location for the program files

The program files folder could be moved by editing the location in the second OS in the registry and as a backup' creating a Junction (symbolic Link) where it normally sits to also point to the new actual location.
This would need to be done before installing any programs, and tricks would be required to move the MS programs installed as part of the OS.

The programs would need to be installed on the second OS or a lot of registry edits performed

Certain programs, (the majority that have a custom install), allow you to specify the install location during setup, so these could be installed to the new location without issue.

The normal installs should work either through the registry changes or the redirect from the junction.

In addition to these changes you may need to do a similar thing to the programdata folders and the user appdata folders

The following link is a good starting point if you wish to investigate these techniques - although unless you are seriously short of disk space I would advise against it

How to move the WinSXS folder in Vista. a Single Point of Contact

Hi,

There may well be a method of overriding the C when creating a slipstream install which was probably the method used by the admins you mention.

Also I believe if you install a separate install from within an existing install Ie install a separate Windows 7 install by running the setup.exe from within an existing Vista or 7 and selecting a new install not upgrade.

The logic behind this is I believe that as the C: drive is in use by the originating OS it cannot be allocated for the new OS, have not actually tried this so cannot confirm if this actually works with Windows 7 but the theory is at least plausible