search

cyberponk / psubst

Automatically exported from code.google.com/p/psubst
41 stars 10 forks source link

Drive is not mapped after reboot #3

Closed Zingam closed 7 years ago

Zingam commented 7 years ago

On Windows 10 when I run the script for the first time. The drive was mapped and worked as expected. After rebooting thou the drive was not mapped. I checked the registry and the entry is there in DOS Devices. Also running just psubst displays the mapped drive.

I used subst until yesterday but some MS tools do not work with drives mapped with subst.

BTW: The drive letter is reported as X:\: which is not correct.

cyberponk commented 7 years ago

Could you tell me what version you are using and what is the folder path you are trying to subst?

On Jan 17, 2017 08:29, "Zingam" notifications@github.com wrote:

On Windows 10 when I run the script for the first time. The drive was mapped and worked as expected. After rebooting thou the drive was not mapped. I checked the registry and the entry is there in DOS Devices.

I used subst until yesterday but some MS tools do not work with drives mapped with subst.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cyberponk/psubst/issues/3, or mute the thread https://github.com/notifications/unsubscribe-auth/ALsdfY6uiDRgomjMG0IiyyU-_LMa20tpks5rTJgAgaJpZM4Lld6G .

cyberponk commented 7 years ago

And am example of a Ms tool that does not work so I can investigate

On Jan 17, 2017 10:49, "ni" homemlagosta@gmail.com wrote:

Could you tell me what version you are using and what is the folder path you are trying to subst?

On Jan 17, 2017 08:29, "Zingam" notifications@github.com wrote:

On Windows 10 when I run the script for the first time. The drive was mapped and worked as expected. After rebooting thou the drive was not mapped. I checked the registry and the entry is there in DOS Devices.

I used subst until yesterday but some MS tools do not work with drives mapped with subst.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cyberponk/psubst/issues/3, or mute the thread https://github.com/notifications/unsubscribe-auth/ALsdfY6uiDRgomjMG0IiyyU-_LMa20tpks5rTJgAgaJpZM4Lld6G .

Zingam commented 7 years ago

Maybe it was a temporary Windows glitch. I reapplied psubst with /F and then I rebooted a few times. No problems any more.

I mean the MS tools work the way psubst maps a drive. If drives are mapped with the standard subst - there are issues. For example Visual Studio cannot deploy UWP apps from a subst-ed drive, nor do the packaging tool from the Xbox XDK. I use psubst now (instead of mapping manually in the registry) and the tools work. The only issue is that the mappings are not per user. If there is a way to make them per user it would be great.

Thank you for the great tool! I think it was a false alarm for now.

cyberponk commented 7 years ago

Great idea, i´ll look into the 'per user' functionality! cheers

cyberponk commented 7 years ago

Don´t forget to watch the project if you wish to be notified of new releases