sc302, on 21 January 2013 - 01:08, said:
many applications get married to a drive letter. Even windows itself gets married to a drive letter...Go ahead change the c partition letter after you have installed windows and see what happens. Many legacy applications and current applications get married to a drive letter. besides what is the alternative? using a long alpha numeric drive name that makes absolutely no sense to anyone or anything but the os...yeah lets make things harder than they already are.
You see it isn't just for programmers, it is for the average user too. The average user can understand c or d or f or whatever.
I get what you're saying, but wouldn't it be easier on users (and tech support personnel) if Windows referred to drives by their label?
Just as the OS does not allow files of identical names in the same folder, it could be set to disallow drives with identical labels.
I know of quite a few people who have Windows installed on drives other than C:.
During installation, windows could label the drive as "Windows", and you would tell the user to go to their Windows drive.
Another thing I noticed is that, if you have an existing installation of Windows on one partition, and you set up a dual boot by installing Windows on another partition, one of two things happen:
1. If you run the setup from within Windows, the new installation keeps the drive letters as they are in the current Windows installation. When you boot into the new installation, the Windows drive will be the drive letter of the partition you selected during the setup.
2. If you boot the computer from the installation media, and initiate setup, Windows marks whatever partition you designate, as C:.
This is highly inconsistent, and can be very confusing to some people.