Changed from XP Pro TO W2K Pro - Drive Letters all Changed !

[victory]

Due to a temporary corruption in XP I have changeed the OS from XP to
W2K Pro and one of the effects of this is that some of my Drive
Letters have changed .

This makes some of the Applications fail to launch due to the paths of
relevant necessary files having been changed.

I seem to remember an Application which I used some years ago which
changed the re-arranged links when this happened so that everything
knew again where everything necessary was located.

Does anyone know of any solutions to this problem so that I can avoid
any major re-allocation of my Applications.

B.N.

 

[Pegasus \(MVP\)]

Due to a temporary corruption in XP I have changeed the OS from XP to
W2K Pro and one of the effects of this is that some of my Drive
Letters have changed .

This makes some of the Applications fail to launch due to the paths of
relevant necessary files having been changed.

I seem to remember an Application which I used some years ago which
changed the re-arranged links when this happened so that everything
knew again where everything necessary was located.

Does anyone know of any solutions to this problem so that I can avoid
any major re-allocation of my Applications.

B.N.

If you installed Win2000 on drive F: (for example) then it will
have to stay on drive F:, because there are numerous entries
in the registry that point to drive F:.

On the other hand, if Win2000 was installed on drive C: but
got subsequently confused so that it now appears on drive F:
then you can make it appear on drive C: again by running
regedit and navigating to HKLM/SYSTEM/MountedDevices.
Make sure that no value "\DosDevices\C:" exists, then rename
"\DosDevices\F:" to "\DosDevices\C:" and reboot.

 

[victory]

If you installed Win2000 on drive F: (for example) then it will
have to stay on drive F:, because there are numerous entries
in the registry that point to drive F:.

On the other hand, if Win2000 was installed on drive C: but
got subsequently confused so that it now appears on drive F:
then you can make it appear on drive C: again by running
regedit and navigating to HKLM/SYSTEM/MountedDevices.
Make sure that no value "\DosDevices\C:" exists, then rename
"\DosDevices\F:" to "\DosDevices\C:" and reboot.

Thanks for the reply - that's new information to me .

However, that is not what happened here in my case . W2k installed on
C: OK , but the subsequent order of drives and partitions have
changed.

Previously, I had , on the Master h/d , drives C,E,F,&G and on the
Slave h/d, D( this was an unpartitioned 120 Gbte drive I had added
later).

Now , after the re-installation of W2K, the drive letters have been
allocated in alphabetical order without regard to the Master and Slave
setup.

So what I would like to do is have is have D and E interchanged in
names , the other drives don't have too much on them and thus won't
give too much of a problem.

I can't now remember why the installation of an aditional h/d drive
caused it to be named D with the partitons on the original ( Master
Drive) being named C,E,F,&G - it may have been due to the original C
drive being in FAT32 whereas this time I've put it into NTFS.

 

[Pegasus \(MVP\)]

Thanks for the reply - that's new information to me .

However, that is not what happened here in my case . W2k installed on
C: OK , but the subsequent order of drives and partitions have
changed.

Previously, I had , on the Master h/d , drives C,E,F,&G and on the
Slave h/d, D( this was an unpartitioned 120 Gbte drive I had added
later).

Now , after the re-installation of W2K, the drive letters have been
allocated in alphabetical order without regard to the Master and Slave
setup.

So what I would like to do is have is have D and E interchanged in
names , the other drives don't have too much on them and thus won't
give too much of a problem.

I can't now remember why the installation of an aditional h/d drive
caused it to be named D with the partitons on the original ( Master
Drive) being named C,E,F,&G - it may have been due to the original C
drive being in FAT32 whereas this time I've put it into NTFS.

Use the recipe I gave you in my first reply.