Naming network Drives

I have created a BAT file to (re)connect my mapped network shares onto
my Win 10 device but I would like to know if there is a way to give
them "common" names

I can Rename a drive by right clicking on a mapped share [eg
\\192.168.0.45\thisdrive (G to rename it "Important Stuff" so that
it shows up as Important Stuff (G ]
I'd like to be able to do this within my BAT file rather than to
constantly rename my Mapped drives

Thoughts?

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

On 2018-02-01 22:19, wrote:

I have created a BAT file to (re)connect my mapped network shares onto
my Win 10 device but I would like to know if there is a way to give
them "common" names

I can Rename a drive by right clicking on a mapped share [eg
\\192.168.0.45\thisdrive (G to rename it "Important Stuff" so that
it shows up as Important Stuff (G ]
I'd like to be able to do this within my BAT file rather than to
constantly rename my Mapped drives

Thoughts?

https://superuser.com/questions/6709...-drive-via-cmd

--
! _\|/_ Sylvain /
! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society
oO-( )-Oo I'm a lawyer. Honest? No, the usual kind.

Gralber wrote:

I have created a BAT file to (re)connect my mapped network shares onto
my Win 10 device but I would like to know if there is a way to give
them "common" names

I can Rename a drive by right clicking on a mapped share [eg
\\192.168.0.45\thisdrive (G to rename it "Important Stuff" so that
it shows up as Important Stuff (G ]
I'd like to be able to do this within my BAT file rather than to
constantly rename my Mapped drives

Thoughts?

You never mentioned HOW (what command and args) you use in your batch
file to create the shared resource. Are you using the net command, as
in "net share args"? If so, use the remark arg to add the comment.
Run "net share /?" for help or see:

https://technet.microsoft.com/en-us/.../bb490712.aspx

I don't have any shares on which to test the /remark:"text" argument.
If that doesn't work (the text is not displayed as the share's name)
then I'm guessing you decide what to specify for the share's name when
you define the share; i.e., use what you want in the sharename arg. As
shown when "net share /?" is ran:

net share sharename=driveath ...
\__ so try ImportantStuff here.

I'm not sure but suspect spaces are not allowed in share names. I
remember that printer shares could not have spaces (or be longer than 31
chars) back in Windows XP.


*Finally, probably the answer you were waiting for ...*

If you are using "net use" to map a drive, I didn't see anything to let
you assign a comment to the shared resource when I ran "net use /?". If
you want or have to use "net use" (maybe because you have a old program
that can only do drive letters and not UNC paths or share names, or it's
you that wants to use drive letters instead of UNC paths), why can't you
follow "net use" with a command that changes the volume's label of the
just-mapped drive?

label driveletter "label"

See:

https://www.howtogeek.com/206197/how...ommand-prompt/

I think the label program has been around since the MS/IBM-DOS days
(circa 1972); https://en.wikipedia.org/wiki/List_o...commands#LABEL
and https://en.wikipedia.org/wiki/Label_(command). As I recall, you can
have spaces in a volume's label but you'll need to delimit the string
with double quotes, so add the following to your batch file:

label drive: "Important Stuff"

Ah, there's the [possible] rub: volume labels have maximum lengths - 11
characters for FAT and 32 characters for NTFS. "Important Stuff" is 15
characters long and "ImportantStuff" is 14 characters long. You'll have
to use a shorter label, like "Serious****" if using FAT. If using NTFS
then its 32-character limit is sufficient for "Important Stuff".

https://www.lifewire.com/volume-label-2626045


---

Not a valid signature delimiter - and Avast knows this because they want
you, by default, to be their unpaid spamming affiliate.

This email has been checked for viruses by Avast antivirus software.
h**ps:// www. avast. c*m/antivirus

Oh yes, just because you (via Avast) say so then truly your post must
not be infected (rolls eyes). Policeman: "Did you just rob that bank
whose alarm is blaring and you're running away from with a ski mask over
your head?" Suspect: "No officer, these are my big bags of money with
the bank's name printed on them and I'm very ugly." Officer: "Oh, okay,
you can leave. Sorry to have detained you."

Disable the option in their mail module to spammify your posts by
appending their disingenuous pseudo-signature. Or uninstall the mail
module since it is superfluous (affords no more protection than does
their on-demand scanner).

In alt.comp.os.windows-10, on Thu, 01 Feb 2018 22:19:46 -0500,
wrote:

I have created a BAT file to (re)connect my mapped network shares onto
my Win 10 device but I would like to know if there is a way to give
them "common" names

I named mine Bubbles. I always wanted a girlfriend named Bubbles and
this is as close as I can get.




Just kidding. I can't anwer your question.

On Thu, 1 Feb 2018 22:42:48 -0600, VanguardLH wrote:
see below interspersed...

Gralber wrote:

I have created a BAT file to (re)connect my mapped network shares onto
my Win 10 device but I would like to know if there is a way to give
them "common" names

I can Rename a drive by right clicking on a mapped share [eg
\\192.168.0.45\thisdrive (G to rename it "Important Stuff" so that
it shows up as Important Stuff (G ]
I'd like to be able to do this within my BAT file rather than to
constantly rename my Mapped drives

Thoughts?

You never mentioned HOW (what command and args) you use in your batch
file to create the shared resource. Are you using the net command, as
in "net share args"? If so, use the remark arg to add the comment.
Run "net share /?" for help or see:

https://technet.microsoft.com/en-us/.../bb490712.aspx

I use "Net Use K: //192.168.0.45/4x6T /user: Melvin muffin
- where 4x6T is the shared volumes name
- the last word = password for that resource



I don't have any shares on which to test the /remark:"text" argument.
If that doesn't work (the text is not displayed as the share's name)
then I'm guessing you decide what to specify for the share's name when
you define the share; i.e., use what you want in the sharename arg. As
shown when "net share /?" is ran:

net share sharename=driveath ...
\__ so try ImportantStuff here.

I'm not sure but suspect spaces are not allowed in share names. I
remember that printer shares could not have spaces (or be longer than 31
chars) back in Windows XP.

Net Share would be on the source side -in my case a NAS so I can't
"run" anything there.. The Vol name Can be changed but I sill get the
whole UNC in win 7 & 10



*Finally, probably the answer you were waiting for ...*

If you are using "net use" to map a drive, I didn't see anything to let
you assign a comment to the shared resource when I ran "net use /?". If
you want or have to use "net use" (maybe because you have a old program
that can only do drive letters and not UNC paths or share names, or it's
you that wants to use drive letters instead of UNC paths), why can't you
follow "net use" with a command that changes the volume's label of the
just-mapped drive?

label driveletter "label"

See:

https://www.howtogeek.com/206197/how...ommand-prompt/

I think the label program has been around since the MS/IBM-DOS days
(circa 1972); https://en.wikipedia.org/wiki/List_o...commands#LABEL
and https://en.wikipedia.org/wiki/Label_(command). As I recall, you can
have spaces in a volume's label but you'll need to delimit the string
with double quotes, so add the following to your batch file:

label drive: "Important Stuff"

Base line Currently
4x6t(\\192.168.0.45) (K

Optimum result:
Stuff (K

All the drives I'm trying to effect are data only and any prog that I
use to access that data will be happy with just using the K: as a
locator.

I do use Index Your Files to find things over my 12T of stuff and I
set up the names of the index files to emulate the drives eg Drive-K
hold the stuff in K:
This is more for me to locate things that I can't/won't search for eg
Looking for music?.. look in the drive called Music (J
I CAN live with out it I suppose..
I just added a Win10 box to the pile and it keeps dropping the network
connection (another thing for another day) So I use the BAT file to
reconnect things to my liking.



I tried the LABEL K: Stuff muffin
- and got and error Parameters not compatible
Also tried LABEL \\4x6t Stuff muffin
and it looked like it worked - it didn't argue and gave me back the
cmd prompt.. but no change anywhere else
-used Stuff just to test it.. I'll worry about lengths once I get it
sorted
-I use NTFS everywhere (as far as I know)


Ah, there's the [possible] rub: volume labels have maximum lengths - 11
characters for FAT and 32 characters for NTFS. "Important Stuff" is 15
characters long and "ImportantStuff" is 14 characters long. You'll have
to use a shorter label, like "Serious****" if using FAT. If using NTFS
then its 32-character limit is sufficient for "Important Stuff".

https://www.lifewire.com/volume-label-2626045


---

Not a valid signature delimiter - and Avast knows this because they want
you, by default, to be their unpaid spamming affiliate.

This email has been checked for viruses by Avast antivirus software.
h**ps:// www. avast. c*m/antivirus

In as much as they have protected me for at least a decade with no
other compensation that this sig line.. I'm OK with that.. It works
as far as I can see..
I get that the "stamp of approval" means nothing...

Oh yes, just because you (via Avast) say so then truly your post must
not be infected (rolls eyes). Policeman: "Did you just rob that bank
whose alarm is blaring and you're running away from with a ski mask over
your head?" Suspect: "No officer, these are my big bags of money with
the bank's name printed on them and I'm very ugly." Officer: "Oh, okay,
you can leave. Sorry to have detained you."

Disable the option in their mail module to spammify your posts by
appending their disingenuous pseudo-signature. Or uninstall the mail
module since it is superfluous (affords no more protection than does
their on-demand scanner).
Oh and thank you to those who have tried so far.


Out on a Limb, sawing Madly

Gralber wrote:

I tried
LABEL K: Stuff muffin
and got and error Parameters not compatible

Run "label /?". You did NOT use the correct syntax. Label is for
changing the label of an ALREADY defined volume (which you did in your
"net use" command). Volume *labels* don't have passwords.

In the "net use" command, you already specified the password to access
the remote resource that is defined as the local volume K:, so just use
the following command:

label K: "Important Stuff"

You are changing the volume's *label*, not defining the volume or
password access to it.

In as much as [Avast has] protected me for at least a decade with no
other compensation that this sig line.. I'm OK with that..

You choose to be their spam affiliate. You choose to spam in Usenet.
Nope, I don't help spammers. This thread will be marked as Ignored (and
I use a default view of Hide Ignored so I won't see anything hereafter).

You choose to spam. I choose not to assist spammers. Bye.

On Fri, 2 Feb 2018 16:01:37 -0600, VanguardLH wrote:

Gralber wrote:

I tried
LABEL K: Stuff muffin
and got and error Parameters not compatible

Yeah.. I used copy past when I wrote that My Bad

Run "label /?". You did NOT use the correct syntax. Label is for
changing the label of an ALREADY defined volume (which you did in your
"net use" command). Volume *labels* don't have passwords.

In the "net use" command, you already specified the password to access
the remote resource that is defined as the local volume K:, so just use
the following command:

label K: "Important Stuff"

You are changing the volume's *label*, not defining the volume or
password access to it.

In as much as [Avast has] protected me for at least a decade with no
other compensation that this sig line.. I'm OK with that..

You choose to be their spam affiliate. You choose to spam in Usenet.
Nope, I don't help spammers. This thread will be marked as Ignored (and
I use a default view of Hide Ignored so I won't see anything hereafter).

You choose to spam. I choose not to assist spammers. Bye.

You failed to notice that I DID remove the "spam"

On 2018-02-02 20:47, wrote:

On Fri, 2 Feb 2018 16:01:37 -0600, VanguardLH wrote:

Gralber wrote:

I tried
LABEL K: Stuff muffin
and got and error Parameters not compatible

Yeah.. I used copy past when I wrote that My Bad

[snip]

Network drives don't have labels in the sense that the label command
understands. Instead of ignoring my earlier reply, start thinking about
it, it's a simple 2 lines VBS script away...

Set oShell = CreateObject("Shell.Application")
oShell.NameSpace("H:\").Self.Name = "Stuff Muffin"

Regards,

--
! _\|/_ Sylvain /
! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society
oO-( )-Oo I see a moderator! QUICK--Change the subject!

On Fri, 2 Feb 2018 23:41:44 -0500, B00ze wrote:

On 2018-02-02 20:47, wrote:

On Fri, 2 Feb 2018 16:01:37 -0600, VanguardLH wrote:

Gralber wrote:

I tried
LABEL K: Stuff muffin
and got and error Parameters not compatible

Yeah.. I used copy past when I wrote that My Bad

[snip]

Network drives don't have labels in the sense that the label command
understands. Instead of ignoring my earlier reply, start thinking about
it, it's a simple 2 lines VBS script away...

Set oShell = CreateObject("Shell.Application")
oShell.NameSpace("H:\").Self.Name = "Stuff Muffin"

Regards,

I didn't ignore it, I am just not versed in coding..
Can you direct me to a Vbasic 101 ? I'm willing to give it a boo

And thank you again for your help

B00ze wrote:

Network drives don't have labels in the sense that the label command
understands. Instead of ignoring my earlier reply, start thinking about
it, it's a simple 2 lines VBS script away...

Set oShell = CreateObject("Shell.Application")
oShell.NameSpace("H:\").Self.Name = "Stuff Muffin"

Be interesting to see if your VBS works. In it is:

oShell.NameSpace("H:\").Self.Name = "your_label"

That's assigning a label attribute to an already mounted volume
designated by a drive letter. That is what I figured the 'label' is
supposed to do. After some more research, and because mapped drives are
not physical partitions in a local file system, then common DOS
commands, like 'label', cannot be used on those mounted volumes. Darn.
I figured if the volume was mounted locally than its object could have
its label/comment attribute changed. Guess the DOS commands are too
limited in scope.

While the forum posts to which you linked mention VBS code to perform
the renaming of a mapped drive, it took digging through them to finally
get to an article that actually provides complete code that the OP could
save into a .vbs file and create a shortcut to it to make it easy to
run.

http://www.computerperformance.co.uk/ezine/ezine60.htm

Instead of:

strNewName = "GuyDives"

the OP would change to a different string value of:

strNewName = "Important Stuff"

I'm wondering if the label/comment can only be changed for permanently
mapped drives. I've found some folks discussing how to use PowerShell
to rename a mapped drive but it didn't work for them with a temporarily
mapped drive. A permanently mapped drive gets recorded in the registry.
to register a permanent mapping, you have to add the /persistent
argument to the 'net use' command, as in:

net use k:UNCpath /persistent

Although the complete syntax is /persistentyes|no), I think using just
/persistent defaults to yes. Without extra code for error checking and
graceful recovery, the basic PowerShell script looks like a 2-liner:

$sh=New-Object -com Shell.Application
$sh.NameSpace('Z:').Self.Name = 'My new drive name'

First line creates a new object named 'sh' (can use a different variable
name, if you like). Second line changes the name attribute of the 'sh'
object to 'My new drive name' (which the OP would replace with
'Important Stuff'). I don't have any mapped drives to test if this
simple Powershell script would work. I've rarely used Powershell but
I'm not sure -com is sufficient (might be a shortname) or if that arg
should be -ComObject.

With a persistent mapping registered in the registry, there is also
doing a registry edit to rename the mapped drive. After using 'net use
k: uncpath /persistent' to define a persistent mapping, you'd go into
the registry to find:

One common way to perform this task is to hack the following Registry
key and add the _LabelFromReg string value:

HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer\MountPoints2\%key%

where %key% is the drive letter for the mapping (I suspect just the
drive letter, no trailing colon character). Then add/edit the
_LabelFromReg string value under that key. Obviously that's a lot of
manual effort so I would first use 'net use' to make a persistent
mapping definition, go into regedit.exe and export the above registry
key, save into a .reg file, and then create a shortcut that ran
"regedit.exe file.reg /s" (the shortcut will need elevated privs so it
can run regedit). The OP will have to save the .reg file somewhere so
the shortcut ran use it as an argument to regedit.exe. The /s arg
doesn't bother with a user prompt to ensure the user wants to commit the
registry change. I'd have to create a persistent mapping, use Explorer
to rename the volume, and then use regedit to make user an entry with
that string got added under the MountPoint2 subkey to make sure this
scheme of creating a .reg file would work. This registry trick was
found at http://archive.oreilly.com/pub/h/1105 (which also mentions your
VBS trick with just a 3-line script).

On 2018-02-03 21:23, VanguardLH wrote:

B00ze wrote:

Network drives don't have labels in the sense that the label command
understands. Instead of ignoring my earlier reply, start thinking about
it, it's a simple 2 lines VBS script away...

Set oShell = CreateObject("Shell.Application")
oShell.NameSpace("H:\").Self.Name = "Stuff Muffin"

Be interesting to see if your VBS works. In it is:

oShell.NameSpace("H:\").Self.Name = "your_label"

That's assigning a label attribute to an already mounted volume
designated by a drive letter. That is what I figured the 'label' is
supposed to do. After some more research, and because mapped drives are
not physical partitions in a local file system, then common DOS
commands, like 'label', cannot be used on those mounted volumes. Darn.
I figured if the volume was mounted locally than its object could have
its label/comment attribute changed. Guess the DOS commands are too
limited in scope.

While the forum posts to which you linked mention VBS code to perform
the renaming of a mapped drive, it took digging through them to finally
get to an article that actually provides complete code that the OP could
save into a .vbs file and create a shortcut to it to make it easy to
run.

http://www.computerperformance.co.uk/ezine/ezine60.htm

Instead of:

strNewName = "GuyDives"

the OP would change to a different string value of:

strNewName = "Important Stuff"

I'm wondering if the label/comment can only be changed for permanently
mapped drives. I've found some folks discussing how to use PowerShell
to rename a mapped drive but it didn't work for them with a temporarily
mapped drive. A permanently mapped drive gets recorded in the registry.
to register a permanent mapping, you have to add the /persistent
argument to the 'net use' command, as in:

Ah! Nice Googling skills, I did not come across this at all! Indeed, if
the PowerShell requires permanent maps (i.e. in the registry) then the
same will be true of the VBScript, i.e. it will not work unless
Persistent is used...

net use k:UNCpath /persistent

Although the complete syntax is /persistentyes|no), I think using just
/persistent defaults to yes. Without extra code for error checking and
graceful recovery, the basic PowerShell script looks like a 2-liner:

$sh=New-Object -com Shell.Application
$sh.NameSpace('Z:').Self.Name = 'My new drive name'

Look at the VBS, it is exactly the same, it creates a Shell Application
object then modified the Self Name. VBS is apparently much lighter than
PowerShell, but I would use PS if I can, just because that's where
things are going, and I got 3 PShell books an no VBS books, lol.

First line creates a new object named 'sh' (can use a different variable
name, if you like). Second line changes the name attribute of the 'sh'
object to 'My new drive name' (which the OP would replace with
'Important Stuff'). I don't have any mapped drives to test if this
simple Powershell script would work. I've rarely used Powershell but
I'm not sure -com is sufficient (might be a shortname) or if that arg
should be -ComObject.

With a persistent mapping registered in the registry, there is also
doing a registry edit to rename the mapped drive. After using 'net use
k: uncpath /persistent' to define a persistent mapping, you'd go into
the registry to find:

One common way to perform this task is to hack the following Registry
key and add the _LabelFromReg string value:

HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer\MountPoints2\%key%

where %key% is the drive letter for the mapping (I suspect just the
drive letter, no trailing colon character). Then add/edit the
_LabelFromReg string value under that key. Obviously that's a lot of
manual effort so I would first use 'net use' to make a persistent
mapping definition, go into regedit.exe and export the above registry
key, save into a .reg file, and then create a shortcut that ran
"regedit.exe file.reg /s" (the shortcut will need elevated privs so it
can run regedit). The OP will have to save the .reg file somewhere so
the shortcut ran use it as an argument to regedit.exe. The /s arg
doesn't bother with a user prompt to ensure the user wants to commit the
registry change. I'd have to create a persistent mapping, use Explorer
to rename the volume, and then use regedit to make user an entry with
that string got added under the MountPoint2 subkey to make sure this
scheme of creating a .reg file would work. This registry trick was
found at http://archive.oreilly.com/pub/h/1105 (which also mentions your
VBS trick with just a 3-line script).

Nice find.

As another alternative, Gralber could use what we use where I work, it's
called KixStart - there are drive renaming commands in that shell.

Best Regards,

--
! _\|/_ Sylvain /
! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society
oO-( )-Oo Ewoks make better burgers!

On 2018-02-03 12:01, wrote:

On Fri, 2 Feb 2018 23:41:44 -0500, B00ze wrote:

On 2018-02-02 20:47, wrote:

On Fri, 2 Feb 2018 16:01:37 -0600, VanguardLH wrote:

Gralber wrote:

I tried
LABEL K: Stuff muffin
and got and error Parameters not compatible

Yeah.. I used copy past when I wrote that My Bad

[snip]

Network drives don't have labels in the sense that the label command
understands. Instead of ignoring my earlier reply, start thinking about
it, it's a simple 2 lines VBS script away...

Set oShell = CreateObject("Shell.Application")
oShell.NameSpace("H:\").Self.Name = "Stuff Muffin"

Regards,

I didn't ignore it, I am just not versed in coding..
Can you direct me to a Vbasic 101 ? I'm willing to give it a boo

And thank you again for your help

Oh, sorry, I just wanted to stop you guys from trying to make the LABEL
command work - it won't, it's looking to a label inside the MBR to
change, it will never find this on a network drive. See Vanguard's reply
for alternatives to VBS (i.e. you could use PowerShell or edit the
registry). As for running this little VB Script, all you do is:

0. Make sure the NET USE that you use to create the drive has
/PERSISTENT:YES
1. Edit the second line of the VBS so that H:\ is your drive and "Stuff
Muffin" is the name you want.
2. Run it after your NET USE with "CSCRIPT YouScriptFile.vbs //B //NoLogo"

That's it.
Best Regards,

--
! _\|/_ Sylvain /
! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society
oO-( )-Oo Windows error 04 Erroneous error, nothing wrong.

On Thu, 01 Feb 2018 22:19:46 -0500, wrote:

I have created a BAT file to (re)connect my mapped network shares onto
my Win 10 device but I would like to know if there is a way to give
them "common" names

I can Rename a drive by right clicking on a mapped share [eg
\\192.168.0.45\thisdrive (G to rename it "Important Stuff" so that
it shows up as Important Stuff (G ]
I'd like to be able to do this within my BAT file rather than to
constantly rename my Mapped drives

Thoughts?

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


For those of you still following along.. I think I have found the way
to achieve my goal
I simply created a ".reg" file that includes everything I needed to
know. I scavenged the correct syntax from looking into the registry to
see how it was done, exported that information and appended it to
include all the drives and locations I wished to use.
I have applied it to my Win 7 and Win 10 machines and it seems to be
the perfect answer. I will next create a version that undoes these
changes and thus making sure that new changes will take properly

Thanks to all who answered my query

Beamer Smith
Out on a limb, sawing Madly

On 2/11/2018 1:34 PM, wrote:
On Thu, 01 Feb 2018 22:19:46 -0500, wrote:

I have created a BAT file to (re)connect my mapped network shares onto
my Win 10 device but I would like to know if there is a way to give
them "common" names

I can Rename a drive by right clicking on a mapped share [eg
\\192.168.0.45\thisdrive (G to rename it "Important Stuff" so that
it shows up as Important Stuff (G ]
I'd like to be able to do this within my BAT file rather than to
constantly rename my Mapped drives

Thoughts?

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


For those of you still following along.. I think I have found the way
to achieve my goal
I simply created a ".reg" file that includes everything I needed to
know. I scavenged the correct syntax from looking into the registry to
see how it was done, exported that information and appended it to
include all the drives and locations I wished to use.
I have applied it to my Win 7 and Win 10 machines and it seems to be
the perfect answer. I will next create a version that undoes these
changes and thus making sure that new changes will take properly

Thanks to all who answered my query

Beamer Smith
Out on a limb, sawing Madly

another method is using REG ADD in a batch

--
Zaidy036

On 2018-02-11 13:34, wrote:

On Thu, 01 Feb 2018 22:19:46 -0500, wrote:

I have created a BAT file to (re)connect my mapped network shares onto
my Win 10 device but I would like to know if there is a way to give
them "common" names

I can Rename a drive by right clicking on a mapped share [eg
\\192.168.0.45\thisdrive (G to rename it "Important Stuff" so that
it shows up as Important Stuff (G ]
I'd like to be able to do this within my BAT file rather than to
constantly rename my Mapped drives

Thoughts?

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


For those of you still following along.. I think I have found the way
to achieve my goal
I simply created a ".reg" file that includes everything I needed to
know. I scavenged the correct syntax from looking into the registry to
see how it was done, exported that information and appended it to
include all the drives and locations I wished to use.
I have applied it to my Win 7 and Win 10 machines and it seems to be
the perfect answer. I will next create a version that undoes these
changes and thus making sure that new changes will take properly

Thanks to all who answered my query

Yeah, the Visual Basic only ends-up modifying the registry anyway :-)
Glad you got it working!

--
! _\|/_ Sylvain /
! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society
oO-( )-Oo And all the Borg Left was this copy of Windoze.