Ken Blake said:
That's not been my experience at all. Please tell us what you think
that "variety of reasons" is.
Ken:
Time & time again over the years we have consistently run into user problems
because the user's boot (system) volume had not been assigned the C: drive
letter. In most cases the situation originally arose because of user error
when installing the Windows OS, e.g., other bootable storage devices were
present at the time of the OS installation or a glitch in the disk-cloning
process resulting in the cloned HDD receiving an other than C: drive letter
assignment.
In any event, the problems we (or, more precisely, the user) subsequently
encountered because of this situation involved the inability (present &
future) for the user to install a particular program on his/her system
(boot) drive because the program simply balked at any attempt to install
such program other than on a C:
designated drive. While it is true that virtually every major program in
existence today will allow this capability, there are still a host of
programs out there (including "custom-made" programs) that simply don't have
this capability. They are programmed to permit installation *only* on a
drive designated as C:. Whether these types of programs can be considered
poorly designed/programmed is beside the point. They are out there in
considerable numbers and users use them.
We also encountered a fair number of problems where future user
configuration modifications simply wouldn't work because the program had
originally been installed on a non-C: designated drive.
Also, we've run into many problems with subsequent upgrades, patches, fixes
of one sort or another affecting an installed program that either would not
modify the targeted program because the program resided on an other-than-C:
drive (even though the user had not originally experienced any difficulty in
installing that program on a non-C: drive), or even if the upgrade, patch,
etc. appeared to be installed properly we ran into subsequent problems of
one kind or another which we attributed to the fact that the program resided
on a non-C: designated drive.
So all-in-all as I've suggested to the OP, if it's not too terribly onerous
to "start over" as it were and perform a correct fresh install of the XP OS
so as to install that OS on a C: designated drive, our advice is do so. On
the other hand if it's simply impractical for the user to do this because
the programs/applications installed on drive make it too difficult or
impossible for the user to reinstall these programs/applications following a
fresh install of the OS (together with the usually onerous chore of
reinstalling all the MS critical updates), then he or she can live with the
present situation and hope for the best.
Anna