Linked by Hadrien Grasland on Thu 13th Jan 2011 12:53 UTC, submitted by sawboss
Hardware, Embedded Systems "The question that forms the title of this article has recently been posted on the Super User Q&A site for computer enthusiasts. At first I was shocked at how silly a question it was as everyone should know that, right? But then I started to think about it and realized anyone under a certain age probably has no clue."
Thread beginning with comment 457553
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Toonie
by Hans Otten on Thu 13th Jan 2011 15:13 UTC in reply to "Comment by Toonie"
Hans Otten
Member since:
2009-12-24

Microsoft did not invent the drive letters, its the CP/M heritage, so blame Gary Kildall.

The use of shorthand notation for drives is much older btw.

No need to comment on Mirosoft still using drive letters, there is not much need in modern Windows environments for driver letters, UNC for network drives works fine.

Reply Parent Score: 1

RE[2]: Comment by Toonie
by henderson101 on Thu 13th Jan 2011 15:48 in reply to "RE: Comment by Toonie"
henderson101 Member since:
2006-05-30

UNC for network drives works fine.


Most of the time. Not all of the time. I have found a few apps that dislike UNC. Usually older ones, but it's not universally supported at all.

Reply Parent Score: 3

RE[3]: Comment by Toonie
by StephenBeDoper on Fri 14th Jan 2011 16:18 in reply to "RE[2]: Comment by Toonie"
StephenBeDoper Member since:
2005-07-06

"UNC for network drives works fine.


Most of the time. Not all of the time. I have found a few apps that dislike UNC.
"

I can think of at least one:

C:\>cd \\server\share
'\\server\share'
CMD does not support UNC paths as current directories.
C:\>

Reply Parent Score: 2

RE[2]: Comment by Toonie
by bogomipz on Thu 13th Jan 2011 18:36 in reply to "RE: Comment by Toonie"
bogomipz Member since:
2005-07-11

You can't cd to an UNC path, which is extremely annoying!

At work, I practically live in Emacs. It handles UNC paths beautifully, but when I spawn a shell to run a couple of svn commands, I get:

'\\foo\bar\baz\wombat'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows>_


Also, WINE does not support UNC paths at all, AFAIK. This is obviously not Microsoft's fault, but still a pretty bad situation.

Reply Parent Score: 4