A
Another Brian
I'm using an application by IBM Rational called ClearCase. It creates
a virtual file system that is mapped to the M: drive using a service
called MVFS (Multi-Version File System). MVFS can be queried as
running by the sc command but has never been listed by the Services
GUI.
Before I had to rebuild this laptop and reinstall ClearCase (and
everything else), the M: drive correctly showed up in Windows
Explorer, along with the other physical and network mapped drives. Now
the M: drive is not listed in Windows Explorer. All the other drives
are still listed, just not the M: drive.
This M: drive is accessible from the cmd prompt and is accessible from
the Open and Save As dialogs of Word and Excel. Bat and Perl scripts
can reference the M: drive without any problems.
It is just Windows Explorer that cannot access it. If I try typing M:
in the address bar, it gives the error file:///m:/. Make sure the path
or internet address is correct. If I try the Map Network Drive tool,
it knows that the M: drive is already in use.
If I go to the cmd prompt and try net use, it return:
M:\>net use m:
Local name m:
Remote name \\view\
Resource type Disk
The command completed successfully.
I've been talking to IBM tech support and they are telling me that
since it is only Windows Explorer that doesn't work, it must be a
Microsoft issue. So I'm asking here for any advice.
Any suggestions?
Brian Bygland
a virtual file system that is mapped to the M: drive using a service
called MVFS (Multi-Version File System). MVFS can be queried as
running by the sc command but has never been listed by the Services
GUI.
Before I had to rebuild this laptop and reinstall ClearCase (and
everything else), the M: drive correctly showed up in Windows
Explorer, along with the other physical and network mapped drives. Now
the M: drive is not listed in Windows Explorer. All the other drives
are still listed, just not the M: drive.
This M: drive is accessible from the cmd prompt and is accessible from
the Open and Save As dialogs of Word and Excel. Bat and Perl scripts
can reference the M: drive without any problems.
It is just Windows Explorer that cannot access it. If I try typing M:
in the address bar, it gives the error file:///m:/. Make sure the path
or internet address is correct. If I try the Map Network Drive tool,
it knows that the M: drive is already in use.
If I go to the cmd prompt and try net use, it return:
M:\>net use m:
Local name m:
Remote name \\view\
Resource type Disk
The command completed successfully.
I've been talking to IBM tech support and they are telling me that
since it is only Windows Explorer that doesn't work, it must be a
Microsoft issue. So I'm asking here for any advice.
Any suggestions?
Brian Bygland