Hi Jonathan,

 JdBP>  JdBP>> One then has to have *another* table of drive letter 
 JdBP>  JdBP>> assignments to say "drive letter Q: is this point in 
 JdBP>  JdBP>> the directory tree".

 PK> ONLY if it is necessary to HAVE a drive letter 
 PK> there! Remember, in my scenario this is for backwards 
 PK> compatibilty only!

 JdBP> The flaw is that the scenario fails to take into account that the 
 JdBP> system API is constructed around the paradigm of 
 JdBP> multiple drives with independent directory 
 JdBP> hierarchies.  Not only would you have to rewrite the 
 JdBP> operating system with a new API, you'd have to 
 JdBP> rewrite all of the applications programs as well.  

If ALL files are referenced somewhere under just the one drive letter C:, or
via just ONE drive number, how does anything have to change? I just can't see
this causing such a problem.

If the user wishes to manually configure "virtual" drive letters/numbers, I
also can't see how this is going to be a massive problem.

Cheers...........pk.

--- Maximus/2 3.01
772/1