In a previous thread I asked how to map a UNC path to a drive letter. That
problem is now solved, as written in the previous thread.
My next problem is how to make Explorer display the volume info in “My
Computer”.
When I map a standard network share to a drive letter, it appears in My
Computer as (for example)
“ShareXYZ on ‘Machine123’(G:)”.
But when I map into a drive letter a UNC \Srv\Vol which is mounted by my
FSD, it is displayed in My Computer as (for example)
“Network Drive(P:)”.
I want it instead to appear as
“Vol on ‘Srv’(P:)”.
How do I do this?
thanks
Chuck Shavit
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
NP DLL is necessary for it. Do you have one?
Max
----- Original Message -----
From:
To: “File Systems Developers”
Sent: Wednesday, February 13, 2002 9:25 AM
Subject: [ntfsd] How to link drive letter –> UNC path (part 2)
> In a previous thread I asked how to map a UNC path to a drive letter. That
> problem is now solved, as written in the previous thread.
>
> My next problem is how to make Explorer display the volume info in “My
> Computer”.
>
> When I map a standard network share to a drive letter, it appears in My
> Computer as (for example)
> “ShareXYZ on ‘Machine123’(G:)”.
>
> But when I map into a drive letter a UNC \Srv\Vol which is mounted by my
> FSD, it is displayed in My Computer as (for example)
> “Network Drive(P:)”.
> I want it instead to appear as
> “Vol on ‘Srv’(P:)”.
>
> How do I do this?
>
> thanks
> Chuck Shavit
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Yes, of course.
However, the actual mapping of a UNC path to the drive letter is not done
from the DLL – it is done from a Win32 GUI that talks to the FSD. The
user selects a drive letter (or “none”) from a pull-down, and the Win32 app
makes an IOCTL request to the FSD, which in turn creates the link. My plan
was to latter add this IOCTL call to the NP DLL, so the user will have two
alternative ways of mapping a UNC to a drive letter.
Would that explain it? In other words, if I had made the IOCTL call from
the NP DLL, would it have provided the missing text?
BTW, I have tried to use DefineDosDevice() in the NP DLL, and it did not
work correctly in XP. Instead of spending more time on it, I decided that
it would be easier for me to ask the FSD to make a link. Perhaps that
might also explain the missing text – is it possible that
DefineDosDevice() takes care of it?
thanks,
Chuck Shavit
On 02/13/02, ““Maxim S. Shatskih” ” wrote:
> NP DLL is necessary for it. Do you have one?
>
> Max
>
> ----- Original Message -----
> From:
> To: “File Systems Developers”
> Sent: Wednesday, February 13, 2002 9:25 AM
> Subject: [ntfsd] How to link drive letter –> UNC path (part 2)
>
>
> > In a previous thread I asked how to map a UNC path to a drive letter. That
> > problem is now solved, as written in the previous thread.
> >
> > My next problem is how to make Explorer display the volume info in “My
> > Computer”.
> >
> > When I map a standard network share to a drive letter, it appears in My
> > Computer as (for example)
> > “ShareXYZ on ‘Machine123’(G:)”.
> >
> > But when I map into a drive letter a UNC \Srv\Vol which is mounted by my
> > FSD, it is displayed in My Computer as (for example)
> > “Network Drive(P:)”.
> > I want it instead to appear as
> > “Vol on ‘Srv’(P:)”.
> >
> > How do I do this?
> >
> > thanks
> > Chuck Shavit
> >
> >
> > —
> > You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> > To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> BTW, I have tried to use DefineDosDevice() in the NP DLL, and it did not
work correctly in XP. Instead of spending more time on it, I decided that
it would be easier for me to ask the FSD to make a link. Perhaps that
I also prefer the kmode part to establish the drive letter. I have forgot the exact reason - either NP DLL GUI works badly without
it or “NET” command-line commands are problematic to implement without it… but I had some reason to spend some days to code this
path in the kmode part.
The redirector must establish the resource connection (if not established yet) using the stored credentials on:
- CREATE IRP
- FastIoQueryOpen
- query path request from MUP
If no credentials are stored - either fail it or try to connect with empty username/password.
The redirector must establish the resource connection using explicitly specified credentials (and store them) on:
- explicit request (via IOCTL, or - like RDR - via CREATE with EAs) from its NP DLL.
NP DLL handles both NET command line and Connect Network Drive GUI.
It could be a great idea to use LSA’s credential cache to store the credentials - this would also allow to use the current user’s NT
password to access the resource, but looks like a subauth package is necessary to be able to retrieve the cleartext password back
from LSA.
LSA and MSV1_0 can supply it only in the form of NTLM challenge/response.
Max
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com