Are drive letters bad?

Here you can discuss ReactOS related topics.

Moderator: Moderator Team

user222
Posts: 62
Joined: Thu Mar 03, 2005 1:21 pm

Are drive letters bad?

Post by user222 » Mon May 02, 2005 1:43 pm

Do any of you think using drive letters for mounts are bad, because you can't more than 26 drives at a time? The UNIX/Linux based systems don't have this problem, don't they?

ScoTTie
Posts: 165
Joined: Fri Feb 04, 2005 9:40 am

Post by ScoTTie » Mon May 02, 2005 1:53 pm

sure its an issue, but how many people use 26 drives ? even with mapped network drives 26 is excessive..

it would be nice if there was a possible way to work around thing, but i dont see it as being a problem for 99.9999% of all people.

also *nix based systems dont have such a limit as i understand, you just mount devices to an empty folder. they do however (like any pc) have a device limit (this doesnt inclued network drives obviously).

ea
Developer
Posts: 31
Joined: Sat Nov 27, 2004 11:54 am
Location: Italy, EU

drive letters and mount points in Windows 2000+

Post by ea » Mon May 02, 2005 2:15 pm

Since NT 3.1, drive letters are symbolic links in the kernel name space, not real device names, like in VMS and in DOS.

Since Windows 2000 you can mount physical and logical NTFS volumes to directories. They are named "junctions".

w3seek
Developer
Posts: 144
Joined: Tue Nov 23, 2004 12:12 am

Post by w3seek » Mon May 02, 2005 4:16 pm

drive letters are just a left-over from the old DOS times, windows is able to mount more than 26 drives as ea already mentioned ;)

user222
Posts: 62
Joined: Thu Mar 03, 2005 1:21 pm

Re: drive letters and mount points in Windows 2000+

Post by user222 » Mon May 02, 2005 5:09 pm

ea wrote:Since Windows 2000 you can mount physical and logical NTFS volumes to directories. They are named "junctions".
If you use the FAT/FAT32 filesystem, you won't be able to.

Gasmann
Posts: 283
Joined: Fri Nov 26, 2004 6:53 pm
Location: Germany
Contact:

Post by Gasmann » Mon May 02, 2005 6:19 pm

ScoTTie wrote:sure its an issue, but how many people use 26 drives ?
I do :P If I mount all my (in widows mountable) partitions with a drive letter and then attach some usb-sticks (2 or 3) I run out of letters :x
And mounting in directories on NTFS-partitions isn't an option for me, since I can't delete directories on the in-dir-mounted partition (don't know why there`s always an error).
I think ReactOS can do it better! But it's not so important now I think. And drive-letters are REQUIRED, since just every wndows apps require them, so there's no other way out...

oiaohm
Posts: 1322
Joined: Sun Dec 12, 2004 8:40 am

This problem is fixed And I do mean Fixed.

Post by oiaohm » Tue May 03, 2005 1:11 am

Linux/Unix/Freebsd mount style will be supported. Ie drive inside drive. 1 drive letter might have 20 different drives inside.

This was decided in a older forum chat about it.

w3seek
Developer
Posts: 144
Joined: Tue Nov 23, 2004 12:12 am

Post by w3seek » Tue May 03, 2005 10:23 am

the problem is, there are so many windows applications that expect paths in the form letter:\directory\file.ext

oiaohm
Posts: 1322
Joined: Sun Dec 12, 2004 8:40 am

The linux style support does not have a problem.

Post by oiaohm » Tue May 03, 2005 1:07 pm

c:\ is one drive
c:\somefolder is another drive
d:\ is a drive
d:\somefolder1 is another drive.
d:\somefolder2 is another drive
Ie all flash drives could be place in side one drive Unless there is some partical reason why its requred to be placed else where.

Windows program still thinks its going to its old drive.

Now this could get really sneeky for network drives.
1 drive for home accound. 1 drive for all file shares.

If programs are not placing anything into windows directory.

There is no reason why programs could not be mounted into c:\Program Files\ From file shares.

Forget thinking of 26 drives think of 26 starting points that any number of drives can be stacked on.

From the program point of view Nil has changed. Only problem is the limit on lenth of filenames if windows has any.

Really only stuff like Cdrom drives cannot be stacked. Windows by default support a weak form of stacking. Ie map a directory to a drive as long as drive has letter. So all reactos lets is map a drive to a directory without giving the drive a letter. So it sould be support no problems by all programs.

rastilin
Posts: 34
Joined: Wed Dec 08, 2004 12:26 pm

Post by rastilin » Tue May 03, 2005 4:28 pm

I was thinking the same thing, it's workable and efficient.

MadRat
Posts: 243
Joined: Fri Feb 04, 2005 8:29 am
Contact:

Post by MadRat » Tue May 03, 2005 8:23 pm

That plan should make it slow as molasses to include any of them virtual folders in the environmental path. External drives take alot more overhead to access than internal ones. Windows and UNIX rely on different mounting methods.
*************************************
Go Huskers!

oiaohm
Posts: 1322
Joined: Sun Dec 12, 2004 8:40 am

This plan is not set in stone.

Post by oiaohm » Wed May 04, 2005 5:31 am

There are options around problems.

Virtual directory defining file. Ie a lnk like file that says enter this directory you now change to this drive.

I did not say it would not cause some that still would have to be worked around. Due to the poor limits of windows.

UNIX and Windows use different mounting methords. True. External Drives take alot more overhead to access than internal one False. Network drives can take less than internal. It all come down to the work required to interface microsoft network file access is not good for speed.

Virtual folders are used in Linux and Unix and cause verry minor over head even on Linux.
c:\data\virtual

This would be processed
as c:\data now open virtual hmm that is a vitual folder lets access the open drive and display this.

Do a subst z: c:\somedirectory then include z: in the environmental path.
You will notice only a minor speed loss. Note this is worse than mounting the other way.

Let be blunt Microsoft really does not have a Mounting Methord.

Theres is lets be lazzy and create a new drive letter each time we get a new partition in the mix.

Where Unix says we have a new partition you get to choose where you place it. Of course there is a price but its not large.

Delfi
Posts: 76
Joined: Sat Nov 27, 2004 8:45 pm

Post by Delfi » Wed May 04, 2005 1:03 pm

i think ROS should be windows compatible, any hacks to do with
drive letters that aren't in windows are redounant and unneccesary
because ros has a target which is to be windows compatible.

plus like 99% of programs cannot parse UNC paths properly, so
drive letters are still in heavy use.

Lucio Diaz
Posts: 107
Joined: Fri Nov 26, 2004 10:12 pm
Location: España (perdido en el atlantico)

Post by Lucio Diaz » Wed May 04, 2005 3:58 pm

Leave drive leters where they are, thats my vote. At least in windows I know wich HD i am working :twisted:

user222
Posts: 62
Joined: Thu Mar 03, 2005 1:21 pm

Post by user222 » Wed May 04, 2005 5:53 pm

Lucio Diaz wrote:Leave drive leters where they are, thats my vote. At least in windows I know wich HD i am working :twisted:
Add the ability to mount a volume as a folder, but retain the ablity to use drive letters, since most applications would need it. Having drive letters and directory mounts is even better than UNIX/Linux.

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests