Remembering mapped network drives

[maq]

I regularly change location (regional offices) and when I arrive at each site I load up a configuration file customised for that location. It appears that the config file does not remember mapped network drives. Is there any way to remember a set of mapped network drives and name them so that when I return to that site I can just load them up?

[admin]

I regularly change location (regional offices) and when I arrive at each site I load up a configuration file customised for that location. It appears that the config file does not remember mapped network drives. Is there any way to remember a set of mapped network drives and name them so that when I return to that site I can just load them up?

Mapped drives should be just available when you start up the app. No need to store them.

What XYplorer can do is remember servers (\\MachineName), but that's not what you want, right?

[maq]

No, I do specifically want to remember mapped drives. A drive mapped as M: looks at \\serverA at one location and looks at \\serverB in another location. The specific drive letters used are important because they have spreadsheets and the like that have links in them to drive letters and what one office calls their M: drive is on a different server to another regional offices M: drive. Would be useful if there was a way to store and retrieve a set of mapped drives e.g. MappedDrives_London.ini and MappedDrives_Edinburgh.ini.

[admin]

If I understand you right, this should be a system wide setting and hence a job for Windows, not for XYplorer. XYplorer just uses the mappings provided by the system.

Can XY overwrite the system-mapping? No, that mapping works on a lower level than most APIs. It's the idea of mapped drives to work as if they were local.

[maq]

OK, many thanks for your time.

[admin]

What I could do would be an XY-internal mapping before the system wide mapping sets in.

E.g., in MappedDrives_London.ini

Code: Select all

[Mappings]
Map1=M:>\\serverA 

Then when you'd pass M:\Folder\ into the Address Bar it would be translated to \\serverA\Folder\ on the fly before further processing. Same with all other methods to go to some location.

[PeterH]

If I understand you right, this should be a system wide setting and hence a job for Windows, not for XYplorer. XYplorer just uses the mappings provided by the system.

Can XY overwrite the system-mapping? No, that mapping works on a lower level than most APIs. It's the idea of mapped drives to work as if they were local.

You provide "Map Network Drive" and "Disconnect Mapped Network Drive" - isn't that the basic of this handling?
And what you had to do would be to do "in real", what you explained "as local solution" - dependent from the current location / the current Map-List.
On first view it looks quite simple - but difficulties arise, when for example - whyever - a driveletter to be mapped is in use, or such...
That could be solved by Disconnecting any letter before (new) mapping, but is that good?

(I hope these thoughts meet the ideas of maq?)