3

I have a network location, \\myserver\myshare. On my Windows XP box, I wish to map this location to the path c:\somefolder. Am I asking the impossible?

6

Are you sure this is really what you want to do? There's a very good article on why this is a bad bad bad idea over at Joel on Software (see point #3)...

Conclusion: the next time someone tries to sell you a programming product that lets you access network resources the same was as you access local resources, run full speed in the opposite direction.

If you want to know why, read the relevant parts of the article.

  • Joel is right in point 3 that making slow network resources appear local may break user expectations and point 1 that correct search results are better than lots of search results. He's wrong in his point 2 diatribe against antialiasing. – Brian Reiter Jun 24 '09 at 14:56
  • Haha, well that article is actually 9 years old now. He posted another follow-up to state that anti-aliasing was greatly improved in XP – Mark Henderson Jun 24 '09 at 21:31
  • Sometimes, you don't really have a choice - usually, due to application restrictions (eg, MUST be located in a particular folder to work, but you can't actually put it there due to company policy/etc.) That's where I'm sitting right now. Working slowly is always faster than not working at all! – Robert P Oct 14 '09 at 20:16
1

Probably not the way you're intending. Windows handles symlinks as a physical descriptor. The tool to create them is "linkd" on WinXP. It requires a local filesystem formated for NTFS as a target.

The closest Windows gets is through DFS. In that case you're creating a special share on a server that your workstation maps to. That share then has its own assembled name-space that's probably what you're looking for. It isn't local, though.

1

On Vista (and later) you can create a symbolic link with mklink.

  • Thanks, but I need this on a Windows XP box. – Billy Jo Jun 24 '09 at 14:17
  • 3
    Prior to Vista you should be able to make use of sysinternals junction.exe. – Brian Reiter Jun 24 '09 at 14:51
  • @Brian Junctions don't do what I want. – Billy Jo Jul 8 '09 at 4:12
1

The answer is I asked the impossible. There's no way to do what I wanted.

  • Other answers cited the fact that this basically isn't possible. Give credit where it's due. – Chris S May 28 '10 at 13:26
  • 1
    @Chris No, other answers gave alternate solutions. Nobody but me actually said that what I wanted was not possible. – Billy Jo May 28 '10 at 22:10
1

You are asking the impossible :)

You need a NTFS symbolic link for what you want.

Unlike an NTFS junction point (available since Windows 2000), a symbolic link can also point to a file or remote SMB network path.

SMB2 is required for symbolic links in windows, which is written into the vista/win7 network stacks.

-1

I havent tried this...and I am not exactly sure what you are talking about, but could you start off with \\127.0.0.1

THis is just a guess.

  • 2
    reading over this answer almost a year later I have no idea what i was thinking. – cop1152 Mar 18 '10 at 14:53
-1

I'm not too sure if this is what you're after, but windows XP can Map Network Drive/Network Folder into a drive (Z:\ etc) but not to a specific folder.

I'm not sure what you're trying to achieve, but if you have a software that requires access to their files in a local-looking drive, you can do a Map-Network Drive and that should do it for you. (But please take note of Farseeker's answer and the link provided).

If you simply need a way to access your network drive easily, create a Shortcut directly to the Network Drive (or map the network drive).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.