Drive letters: Microsoft should get rid of them.


Recommended Posts

I have an external hard drive (D:) and an external dvdrw drive (E:) and Windows always remembers the drive letters for them.

As explained by Billyea above, this is as it should be if you always plug them into the same port.

As for the MacOS renames open files it's not that difficult to understand why it works, the name of the file is only a more simple way(for the user) to identify the file, ate least in Linux the open files are represent by a file descriptor that is connected to the iNode(in Ext filesystem the number of the iNode is the real identifier of a file. there are more filesystems that also use this approach) that represents the file on the disk, the name associated with a iNode are stored in a special file called directory. I'm assuming that the internals of Linux and MacOS are similar since both derive from Unix.

cd /tmp

gedit TESTFILE &

type 'blah blah blah' -> save

mv TESTFILE TESTFILE2

back to gedit, type 'a2' -> save

Result -> Completely different files.

  • 2 weeks later...

Are you 100% sure about that? Is it not application specific to only those that use a special library becuase that is NOT normal unix-like behaviour.

Well I know nothing about OSX, but I can say that under Linux this is 100% valid way to move files between partitions.

Lack of this under windows make my cry hard. Under Linux If I want to move files from one disk to another another I just:

1. Create new partition.

2. Copy files from old folder (like /usr/bin /home etc.) to new partition.

3. Delete old files.

4. mount new partition under old folder.

5. Edit fstab file to mount partition at system startup. It's extremely simple and convenient way of moving and managing files if you happen to run out of space or just want to reorganize some files.

Equivalent on Windows for doing that would be:

1. Copy all files from Program Files or Users folder.

2. Delete those files from folders.

3. Mount partitions with copied files under those folders.

Have fun doing this.

It's simply impossible or I'm to stupid to do it.

Funny thing is that Windows internally do not use Drive Letters. Here is interesting post:

http://www.dslreports.com/forum/r24587240-

In other words. Drive Letter assignment was, is and will be flawed by design. There is no defense to this system. The only reason it exist in windows is because app developers assume that there drive letters instead of using system variables.

The mounting system in Linux is admittedly more flexible than the use of drive letters, but for the average user it's probably going to also be more confusing. Having them displayed as letters and shown in "Computer" gives a user a clear identification of which drive is which.

Having them displayed as letters and shown in "Computer" gives a user a clear identification of which drive is which.

In what way do drive letters help here as opposed to simply identifying disks by their label and device type ?

In what way do drive letters help here as opposed to simply identifying disks by their label and device type ?

Seeing them mounted as folders within the filesystem like it's done in Linux has the possibility of confusing ordinary users.

Seeing them mounted as folders within the filesystem like it's done in Linux has the possibility of confusing ordinary users.

In what way ? Users don't care at which disk their files are.

It's more confuing to see 5 disks with letters C, D, E etc than simple folder like /home/userName or /media/movies.

User just see yet another folder. Not some special icon that posing to be Device for no apparent reason.

When it's shown in the computer folder as a drive, what it is is abundantly clear. When it shows up as just another folder, to the average user what it is is not clear. Think like a n00b not a geek and you'll see the point I am trying to make.

I would imagine there's a way to fix this. In Linux I created an entry using the device ID of my external hard drive so that whenever I plug it in it always gets mounted to the same location. I haven't used Windows for anything too technical in a while, but I think there's a way to do something similar in the "Computer Management" app under "Administrative Tools" in the Control Panel.

In what way ? Users don't care at which disk their files are.

It's more confuing to see 5 disks with letters C, D, E etc than simple folder like /home/userName or /media/movies.

User just see yet another folder. Not some special icon that posing to be Device for no apparent reason.

Because people don't think of folders being drives. People think in this drive I have these folders. Flipping it around would confuse novices.

People DO care which disk their files are on. USB Flash Drives and external hard drives require users to know which drive they're putting the file on.

Truly portable apps shouldn't reference things by drive letters and having a different letter assigned shouldn't be a problem. All the portable apps I've used (such as from portableapps.com) all use relative paths. That's half of what makes software portable. The other half is not using the registry.

In what way ? Users don't care at which disk their files are.

It's more confuing to see 5 disks with letters C, D, E etc than simple folder like /home/userName or /media/movies.

User just see yet another folder. Not some special icon that posing to be Device for no apparent reason.

Sorry, but you're wrong. I very MUCH care what drive my files are on.

For me, pressing Win+R, then typing D:\Downloads\ is far, far easier than typing /mount/sd3/downloads or whatever insanity Linux is using these days.

And on OS X, you can't even use the keyboard to do anything.

^ That shows how little you know of other operating systems.

Ubuntu for example maps all drives to the /Media/*DriveLabel* folders, Mac OS X does it similarly with /Volumes. And saying you can't do anything with a keyboard on a Mac shows just how little you know.

I would much prefer Windows got the route of Mac OS X instead of this drive letter bs that we're stuck with. would make network mapping a whole lot easier

When it's shown in the computer folder as a drive, what it is is abundantly clear. When it shows up as just another folder, to the average user what it is is not clear. Think like a n00b not a geek and you'll see the point I am trying to make.

I'm trying and I'm honestly failing to see logic behind drives.

It seems ok for you because you got used to it, and treat it as something obvious.

If we really want to put ourselves in place of noob user, then we should realize that such user doesn't even know what Drive is in the first place. Doesn't know what CPU is and so on.

What average user see is data (music, movies) and devices such as Pendrive or external Hdd.

In linux pendrive will be mount is /media/pendrive this is obvious at first glance. It even tell you what it is.User is not confused because it look like rest of file system structure.

In Disk letters, Letter are actually detached from this structure and this is certainly more confusing, because you have two separate concepts.

For me, pressing Win+R, then typing D:\Downloads\ is far, far easier than typing /mount/sd3/downloads or whatever insanity Linux is using these days.

And on OS X, you can't even use the keyboard to do anything.

Uh...OS X has its issues like any other operating system. But a supposed lack of (consistent and sensible) keyboard shortcuts is not among them.

Press Shift+Command+G (For "Go To Folder...") in the Finder, type "/Volumes/Drive Label/Downloads"

Note that the "D:" in your example is a completely arbitrary assignment as far as the user is concerned, except for (nowadays usually falsely) suggesting, that it might be the CD drive. You haven't given any reason as to why the letter makes anything easier. The letter by itself can neither tell you which drive it references, nor can you generally rely on a certain drive always being available under the same specific letter (hence this thread).

removing the drive letters is completely wrong.

Why? It's a relict. As a longtime user of Microsoft software you get used to it. It's just such a very familiar concept by now. But the fact of the matter is that it dates back to a time when there was only A and B and no hierarchical directory organization. You'd never use the drive letter concept if you started over nowadays.

This topic is now closed to further replies.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      530
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      148
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!