Mapped network drive on same PC not writable

[CaptainSlog]

Hi All,

I'm running Windows7 64bit Pro.

I run some CAD and compiler software that (unfortunately!) uses absolute path names in project files, so I need to access all my files with exactly the same path for my PC and my laptop. Enventually I want to put all files on an external NAS drive, but only have the PC at the moment.

So my first thought was create a folder on my PC, say C:\X_Drive, map it as a network drive, say X:, and share the folder as X: on the laptop. Then I'd always access files through the mapped drive, and all paths would be consistent, and moving to an external drive should be trivial.

This sort of works. I've set up the Security tab to give everyone full access. I can read and write the folder itself, but cannot write to the mapped drive version on the same PC, I'm warned I don't have permission. I'm an administrator and the only user on the system. I've tried UNC addressing and direct fixed IP addressing when mapping, no joy. Subst doesn't work properly either (drive comes up as disconnected in explorer, but I believe that's a known Windows bug).

Has anyone done this? I can't see why it shouldn't work. Any help appreciated.

Mark.

 

[litiki777]

Have you fixed this problem ? I have the same one and cannot find a solution anywhere! Thanks.

 

[CaptainSlog]

Yes, I used psubst:
psubst - Persistent SUBST command - Google Project Hosting

Using the format below to make the drive persistent across reboots:

psubst drive1: drive2:path /P

Similarly the format below to delete the mapping:

psubst drive1: /D /P

Note this didn't show up immediately in explorer, I had to reboot but it retains the mapping and is writable.

Mark.

 

[Parman]

Remeber that you have to setup network permissions and ntfs permissions to be able to view it locally and through the share.

 

[CaptainSlog]

Remeber that you have to setup network permissions and ntfs permissions to be able to view it locally and through the share.

For some reason setting permissions for both local and network access doesn't fix this issue. Using psubst rather than subst or map network drive wizard (at least for me) does. I'm sure there's a bug somewhere...