#Accessing (none) drives
2 messages in this thread
Peter,
>> Jim, you can browse the connection from a command line by issuing a "dir
>> \\machine name\share point". Your connection is established, however file
This is supported since 3COM LM 1.0, but that's NOT what want it.
What does NT offer me that's new 🙂
>> manager represents the net address of the connection by a drive letter.
>> Since the drive letter does not exist, browsing would require you to supply
>> the UNC name. Also since the connection exists, file manager is capable of
>> disconnecting the connection.
Sorry, but I am not understanding this, I am supplying filemgr with the UNC
name
except it does NOT give me a window to browse the UNC connection
and launch things?
(I don't care to see some sort of icons on the drive toolbar for driveless
connections, selecting from the list-box is fine provided they show up as they
do in the disconnect list.)
So, why does file-manager let me set a driveless connection? Is it just so
that
I can issue a command-line "dir \\server\share" I can already do this
without the need of file-manager. Is this absurd or what?
Thank you for clarifying this.
Hewlett-Packard
Cardiology Business Unit
1700 South Baker St.,
Mc-Minnville, OR 97128
503-434-8434
There is 1 Reply.
<<Sorry, but I am not understanding this, I am supplying filemgr with the
UNC name except it does NOT give me a window to browse the UNC connection
and launch things?>>
Exactly, because you are not redirecting a drive. In effect you are
registering the remote resource with a piece of Windows NT networking
software called the Multiple UNC Provider; you have established a session
and not a logical connection. Therefore any subsequent I/O requests, etc
that are made using that UNC name will allow immediate communication rather
than performing all the necessary tasks to identify the network, station,
etc. This facilitates Interprocess Communication methods such as NetDDE,
name pipes, etc.
<<(I don't care to see some sort of icons on the drive toolbar for driveless
connections, selecting from the list-box is fine provided they show up as
they do in the disconnect list.)>>
Since you've created a session and not a logical connection there will not
be an option in file manager to browse that resource. Only redirected
drives show in file manager.
<<So, why does file-manager let me set a driveless connection? Is it just
so that I can issue a command-line "dir \\server\share" I can already do
this without the need of file-manager. Is this absurd or what?>>
File manager can now create the session rather than issuing a command at a
command line as in WFW. These sessions faciliate Interprocess
communication.
I hope this clears things up for you.
Regards,
Peter Jordon [MS]