Have an xp image that is quite a complex and involved build but I need to create another drive letter on this system without creating a full new build. What are my options? I know partitionmagic can do things like this, resize and create new partitions without affecting the data etc, but I've had some trouble with partition magic in the past so I don't trust it too much, especially with this build.
What other options do I have to create a new drive letter? I know you can map a drive on any available letter using the gui to:
\\"local hostname"\c$\"Folder Name"
But since this is basically a network mapping pointing at yourself I was wondering if this would have any disadvantages and what the alternatives are.
With windows xp, from my expierence you have the "mounted device" drive letter and the "partition ID" drive letter. Changing one doesn't necessarily change the other. Both these drive letters need to match in order for windows to boot.
You can use "paragon rescue kit 9.0 express" to change the "partition ID" drive letter. I've done it many times and it always does the job.
As far as changing the "mounted devices" drive letter that is more complicated. It requires the software "savepart". I've never change the "mounted devices" drive letter but have read about it below.
http://www.wilderssecurity.com/showthread.php?t=174958#20
I don't really need to change the drive letter of a mounted disk or a partition, I need to add a whole new one.
What I'm really trying to do is this:
The system has a piece of software on it that always reverts back to a pre configured state upon reboot. So you could uninstall all the programs, delete stuff from system32, delete ntldr, whatever, once you switch the pc off and on again it will start as if nothing happened. Likewise if you make some new files and folders and leave them anywhere on the c: drive, for instance on the desktop, once you reboot they will be gone.
What I need is an area that I can add files, folders, make changes to, etc, now this piece of software only allows that when it's on another partition. So I could configure it to keep the c: drive in a static state but to allow the h: drive to be a normal drive allowing changes.
With what I initially suggested I don't think that would actually work since the mapping to a folder on a local drive would still actually be on the c: drive, and since the whole c: drive would be configured to remain unchanged whatever changes made within that drive would disappear upon restarting. So I suppose what I'm really looking for is to create a new partition without having to build a whole new image (this build has lots and lots of software and particular settings).
What about converting the disk to a dynamic disk and then resizing the c: partition (to make it a bit smaller) and then creating a new partition on the end in the newly unallocated space, could that work? I think once you convert a disk to dynamic you can't convert it back to basic though.
You are using a virtual software like deepfreeze or returnil? I do the same (use returnil). These programs are the one that have to be configured to allow changes to remain after reboot.
I know with returnil it will allow me to create a "virtual" drive that will survive the reboot on my "c" partition. But usually I have numerous partitions and returnil only protects my "c" partition, I save everything on different partitions.
Creating a new partition on a one partition drive can be dangerous, I've encountered problems with partition magic not doing the job right and corrupting my data. But I've also had success. It's 50/50. If this is a desktop, I recommend just add another internal drive. But if that is not possible, make an image backup of your hard drive before you try to partition. An image backup will allow you to restore your hard drive if it runs into problems.
