#Accessing (none) drives
05-Aug-93 12:58:34
Sb: #Accessing (none) drives
Fm: Jim Russell 71730,3141
To: Peter Jordan 73422,2360
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.