New
#21
Whew, another Indonesian :)
You don't discard old data...
You'll never have "enough" storage space
Harus banyak lah !!!
zzz2496
Do we still need drive letters...?
-
-
New #22
Glad to meet you.
Ahh, i think i know what you mean.
Why don't you get harddisk of server which could save terabytes size of data?
It's better than reading alphabet from A to Z and sorting them out one by one.Last edited by Brink; 17 Jan 2010 at 14:09. Reason: removed unneeded comment
-
New #23
I have one, now serving around 6TB of storage space :) It's a home made SAN box :) Which when it went online made me realize that I had ran out of drive letter to use...Glad to meet you.
Ahh, i think i know what you mean.
Why don't you get harddisk of server which could save terabytes size of data?
It's better than reading alphabet from A to Z and sorting them out one by one.
zzz2496
-
New #24
I guess I say what I say, due to the fact that there are huge companies out there that use all Windows Servers and PC's and don't have these problems. So, it's a matter of setting things up properly and using the right equipment. I just don't think there is a real need or out cry for change on this as Drive Letters still work.You can have almost unlimited number of folders compared to the very small 27 drive letters... Which then made me realize, Drive letters is an old legacy and Microsoft should have just leave it behind.
With that said, could there be a better way of doing things? Yes.
But progress is a slow process sometimes.
-
-
New #26
i've got to be honest i understand why this could be important to a few select users but the majority of the market has a long time before this becomes an issue.
-
New #27
Sorry to get this old thread up, but I could not help trying to open your eyes.. o)
No one really needs driveletters! It's the stiffest thing anybody can think of, when handling volumes and data.
I often insert usb-sticks or the like into several computers. On every machine that usb-stick comes up with another drive letter, how insane is that ?! Or you realize, the usb-stick suddenly "is" the network-share, because windows handles those letters badly.
I image something like this, I choose to name my bootdisk "win7" and can open a DOS-Box and type "dir win7:\windows". I could move the disk over to any other machine, and get the same output, because drives have "names" which are actualy used for something, other than just showing their label in the explorer drives overview.
Another example:
My usb-stick has the label/name "usb-travel:" and here applies the same. I open explorer.exe, on any machine that the stick is connected to and type "usb-travel:" and the content comes up. Individiually named volumes or media can be distinguished by their label very easily, for humans AND for the machines.
There is nothing against a "secondary" or more hardware-like identifier for each volume as known from unix/linux (but that win-style with GUIDed devices is quite unhandy).
To top things out, you could create virtual lables like "mp3:" and map them to any directory on your drives. So you say to winamp.exe, my mp3s are here in "mp3:". Whenever you change the real physical location of your music files, you just change that "mp3:" virtual assignment and there's no need to change any configuration in any tool.
You have another disk with mp3-files ?! No problem, use the virtual assignment "mp3:" and add to that assignment another directory, so you merge different folder contents into one virtual place.
All this has been done already and was of high use and acceptance on an operating system, which did not really survive the last 10 years, surely not due to this unique way of managing drives, files and their identification.
You need to open up your mind.. there really is not a single usecase where a driveletter is an advantage. In case you need to address the bootdisk directly, there would be a generic "sys:" assignment and no need for you or the computer to know the real bootdisk-label. Obviously all this kills any thoughts on limited drive-letters as well.
So, this is my first post here, i hope it wasn't the last.. o) I needed to post this, hoping future releases of windows create a much nicer experience than current versions do.. o)
-
New #28
Simple to use
Drive letters are simple to use.
I'm not a fan of pooled storage (for personal use).
How would you know where something was stored, if you mounted several drives to "mp3:"?
Which mp3s are on the HDD which is failing (and has to be replaced)?
One of the things that I really hate about Linux is manual mounting!
More Terminal typing (mkdir, mount, chown; repeat for each drive).
Volume labels can be handy though.
When I reconfigure my HDD layouts (e.g. buy a new drive) my Linux fstab file can automatically find the new partitions (if I use the same volume labels).
-
New #29
I wouldn't mind if drive letters went away, but they have to be replaced with something else. UNC paths are one option. Mounting partitions in filesystems works fine for technically savvy users, but normal users get confused by it. It's hard enough to teach them that H: is stored on a remote computer, but when you bury it in your filesystem then it just makes things worse.
The old AmigaOS allowed you to create drive labels, so you would simply say HD1: or NETWORK: and that was pretty cool.
End users want seperation of their physical media, they want to know that they're coping files from one drive to another, not just one folder to another.
Even Linux and the Mac cause cd-roms, usb sticks, network shares, etc.. to show up as clickable units on the desktop.
-
Quote
Related Discussions