Re: How to list all drive maps? ('net use' only shows *current user's* maps)

Hi!
In advance...
"Greg Ercolano" <erco@xxxxxxxxxx> wrote in message
news:46xIf.120$gf7.66@xxxxxxxxxxx
Arkady Frenkel wrote:
Look at http://support.microsoft.com/default.aspx?scid=kb;en-us;Q180362
for details ( each user has it's own set )

Thanks, good info.

The relevant text regarding 'net use' not showing all the info
is probably this bit:

--- snip
If a user tries to enumerate the list of redirected drives through
WNetOpenEnum()
and WNetEnumResource(), the functions only list redirected drives that
were established
by that user. Drives that were redirected by other users will not be
visible.
--- snip

What scares me is Microsoft saying this:
--- snip
A service should not directly access local or network resources through
mapped drive letters.
--- snip

Taken at face value, that means folks who telnet in to a DOS prompt
can't use drive letters. (telnet is a service)

Being service telnet can receive that data from user part of it, where no
problems with mentioned function
Arkady

But sometimes you are forced to use drive letters, because some DOS
commands don't support UNC paths, such as 'cd' and 'chdir':

C:\>cd \\meade\net\tmp
'\\meade\net\tmp' is an invalid current directory path. UNC paths are not
supported.

..which means you're SOL if you want to run 'nmake' or 'cl'
in a network directory.

Fortunately drive maps /do/ seem to work from telnet.

Good thing too, because AFAIK, there's no way around the DOS
CHDIR problem with UNC paths, which is I think is more of a legacy issue
with DOS than it is a technical issue with WIN32, which I think fully
supports UNCs, even for chdir().


.

Relevant Pages

  • Re: How to list all drive maps? (net use only shows *current users* maps)
    ... --- snip ... If a user tries to enumerate the list of redirected drives through WNetOpenEnum ... But sometimes you are forced to use drive letters, because some DOS ... UNC paths are not supported. ...
    (microsoft.public.win32.programmer.networks)
  • RE: [SLE] Problems with initrd after mkinitrd
    ... mainboards and the BIOS are all contemporary enough ... meaning the physical location of /boot and initrd is not ... > meaningful forensics on all of the drives that are failing to boot. ...
    (SuSE)
  • RE: [SLE] Problems with initrd after mkinitrd
    ... no issues with BIOS access to the disk. ... > natural metric for partitioning drives that use LBA. ... > overcoming this 'flavor' of boot failure by reinstalling Grub. ...
    (SuSE)
  • Re: To Upgrade or Not. Whats the difference?
    ... little use at all (although installation of RISC OS SIX needed one of them). ... I have shared an optical drive to the A9Home, maybe 4 times since I got the ... I think stating that lack of extra hard drives and lack of CD ...
    (comp.sys.acorn.apps)
  • Re: Disk transfers
    ... is usually detected as the drives have sensors that detect the changes in ... having a test bench that could fill up the write cache, ... breaker to cut power, but the need to verify regularly that everything is ...
    (comp.arch)