is this right?

A] NAS cannot be partitioned as C: D: E:

B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.

C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).

in the client system:
when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
-but-
when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)

thank you

Il 21/02/2023 12:31, timepro timesheet ha scritto:
> is this right?
>
> A] NAS cannot be partitioned as C: D: E:
>
> B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.
>
> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
>
> in the client system:
> when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
> -but-
> when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)
>
> thank you
>
>
To be visible by a Windows machine, the NAS must expose SMB protocol to
clients (usually via SAMBA).
Once you see the server via SMB, you can treat it as a normal networked
Windows machine.
So you can map f.e. \\mynas\TAXDRIVE to Z:

Dan

On Tuesday, February 21, 2023 at 6:17:21 PM UTC+5:30, Dan wrote:
> Il 21/02/2023 12:31, timepro timesheet ha scritto:
> > is this right?
> >
> > A] NAS cannot be partitioned as C: D: E:
> >
> > B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.
> >
> > C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> >
> > in the client system:
> > when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
> > -but-
> > when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)
> >
> > thank you
> >
> >
> To be visible by a Windows machine, the NAS must expose SMB protocol to
> clients (usually via SAMBA).
> Once you see the server via SMB, you can treat it as a normal networked
> Windows machine.
> So you can map f.e. \\mynas\TAXDRIVE to Z:
>
> Dan

thanks dan.

will someone...(Y/N)
A] NAS cannot be partitioned as C: D: E:
B] each folder in NAS is similar/equivalent to what a drive/partition(C:,D:,E:) is in a conventional HDD.
C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).

*

:Mapping Query:
my app resides in 'TAX' folder in D: of the server (server name: 'serveroffice')
..exe: MYTAX.EXE.
in LAN, i am trying to MAP the D: server as W: in a client.
-Map Network Drive
-Drive: W
-but when i click on 'Folder', the D: of the server is not listed. (neither does 'serveroffice')
(in 'Folder:' only the TAX folder in D: has to be selected - not the entire D:)

BUT

there's another app on the same client, where it's icon's properties are:
Drive: W
Folder W:\SHOP\SHOPITEM.EXE

-so, how do i get 'serveroffice' or D: of the server get listed & be mapped.

on successful mapping, my icon properties would be:
Target: W:\TAX\MYTAX.EXE
StartIn: W:\TAX

thanks

On Tuesday, February 21, 2023 at 9:20:42 PM UTC+5:30, timepro timesheet wrote:
> On Tuesday, February 21, 2023 at 6:17:21 PM UTC+5:30, Dan wrote:
> > Il 21/02/2023 12:31, timepro timesheet ha scritto:
> > > is this right?
> > >
> > > A] NAS cannot be partitioned as C: D: E:
> > >
> > > B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.
> > >
> > > C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> > >
> > > in the client system:
> > > when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
> > > -but-
> > > when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)
> > >
> > > thank you
> > >
> > >
> > To be visible by a Windows machine, the NAS must expose SMB protocol to
> > clients (usually via SAMBA).
> > Once you see the server via SMB, you can treat it as a normal networked
> > Windows machine.
> > So you can map f.e. \\mynas\TAXDRIVE to Z:
> >
> > Dan
> thanks dan.
>
> will someone...(Y/N)
> A] NAS cannot be partitioned as C: D: E:
> B] each folder in NAS is similar/equivalent to what a drive/partition(C:,D:,E:) is in a conventional HDD.
> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> *
>
> :Mapping Query:
> my app resides in 'TAX' folder in D: of the server (server name: 'serveroffice')
> .exe: MYTAX.EXE.
> in LAN, i am trying to MAP the D: server as W: in a client.
> -Map Network Drive
> -Drive: W
> -but when i click on 'Folder', the D: of the server is not listed. (neither does 'serveroffice')
> (in 'Folder:' only the TAX folder in D: has to be selected - not the entire D:)
>
> BUT
>
> there's another app on the same client, where it's icon's properties are:
> Drive: W
> Folder W:\SHOP\SHOPITEM.EXE
>
> -so, how do i get 'serveroffice' or D: of the server get listed & be mapped.
>
> on successful mapping, my icon properties would be:
> Target: W:\TAX\MYTAX.EXE
> StartIn: W:\TAX
>
> thanks

i'll rephrase my query:
on a client, can a folder on a server drive be mapped - if that server drive/folder is not listed in 'Folder(Browse...)' of 'Map Network Drive' ?.

how?

thanks

Il 22/02/2023 05:44, timepro timesheet ha scritto:
> On Tuesday, February 21, 2023 at 9:20:42 PM UTC+5:30, timepro timesheet wrote:
>> On Tuesday, February 21, 2023 at 6:17:21 PM UTC+5:30, Dan wrote:
>>> Il 21/02/2023 12:31, timepro timesheet ha scritto:
>>>> is this right?
>>>>
>>>> A] NAS cannot be partitioned as C: D: E:
>>>>
>>>> B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.
>>>>
>>>> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
>>>>
>>>> in the client system:
>>>> when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
>>>> -but-
>>>> when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)
>>>>
>>>> thank you
>>>>
>>>>
>>> To be visible by a Windows machine, the NAS must expose SMB protocol to
>>> clients (usually via SAMBA).
>>> Once you see the server via SMB, you can treat it as a normal networked
>>> Windows machine.
>>> So you can map f.e. \\mynas\TAXDRIVE to Z:
>>>
>>> Dan
>> thanks dan.
>>
>> will someone...(Y/N)
>> A] NAS cannot be partitioned as C: D: E:
>> B] each folder in NAS is similar/equivalent to what a drive/partition(C:,D:,E:) is in a conventional HDD.
>> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
>> *
>>
>> :Mapping Query:
>> my app resides in 'TAX' folder in D: of the server (server name: 'serveroffice')
>> .exe: MYTAX.EXE.
>> in LAN, i am trying to MAP the D: server as W: in a client.
>> -Map Network Drive
>> -Drive: W
>> -but when i click on 'Folder', the D: of the server is not listed. (neither does 'serveroffice')
>> (in 'Folder:' only the TAX folder in D: has to be selected - not the entire D:)
>>
>> BUT
>>
>> there's another app on the same client, where it's icon's properties are:
>> Drive: W
>> Folder W:\SHOP\SHOPITEM.EXE
>>
>> -so, how do i get 'serveroffice' or D: of the server get listed & be mapped.
>>
>> on successful mapping, my icon properties would be:
>> Target: W:\TAX\MYTAX.EXE
>> StartIn: W:\TAX
>>
>> thanks
>
> i'll rephrase my query:
> on a client, can a folder on a server drive be mapped - if that server drive/folder is not listed in 'Folder(Browse...)' of 'Map Network Drive' ?.
>
> how?
>
> thanks
>

Don't rely on browsing computers. Microsoft discourages the use of SMB 1
so new NAS (and Windows itself) should implement SMB2 only and browsing
network resources should be avoided.

You can mount the shared folders to local drive letters. The server is
reachable via UNC. No drive letters. (f.e \\192.168.0.1\mydir...)

Dan

On Wednesday, February 22, 2023 at 3:48:11 PM UTC+5:30, Dan wrote:
> Il 22/02/2023 05:44, timepro timesheet ha scritto:
> > On Tuesday, February 21, 2023 at 9:20:42 PM UTC+5:30, timepro timesheet wrote:
> >> On Tuesday, February 21, 2023 at 6:17:21 PM UTC+5:30, Dan wrote:
> >>> Il 21/02/2023 12:31, timepro timesheet ha scritto:
> >>>> is this right?
> >>>>
> >>>> A] NAS cannot be partitioned as C: D: E:
> >>>>
> >>>> B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.
> >>>>
> >>>> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> >>>>
> >>>> in the client system:
> >>>> when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
> >>>> -but-
> >>>> when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)
> >>>>
> >>>> thank you
> >>>>
> >>>>
> >>> To be visible by a Windows machine, the NAS must expose SMB protocol to
> >>> clients (usually via SAMBA).
> >>> Once you see the server via SMB, you can treat it as a normal networked
> >>> Windows machine.
> >>> So you can map f.e. \\mynas\TAXDRIVE to Z:
> >>>
> >>> Dan
> >> thanks dan.
> >>
> >> will someone...(Y/N)
> >> A] NAS cannot be partitioned as C: D: E:
> >> B] each folder in NAS is similar/equivalent to what a drive/partition(C:,D:,E:) is in a conventional HDD.
> >> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> >> *
> >>
> >> :Mapping Query:
> >> my app resides in 'TAX' folder in D: of the server (server name: 'serveroffice')
> >> .exe: MYTAX.EXE.
> >> in LAN, i am trying to MAP the D: server as W: in a client.
> >> -Map Network Drive
> >> -Drive: W
> >> -but when i click on 'Folder', the D: of the server is not listed. (neither does 'serveroffice')
> >> (in 'Folder:' only the TAX folder in D: has to be selected - not the entire D:)
> >>
> >> BUT
> >>
> >> there's another app on the same client, where it's icon's properties are:
> >> Drive: W
> >> Folder W:\SHOP\SHOPITEM.EXE
> >>
> >> -so, how do i get 'serveroffice' or D: of the server get listed & be mapped.
> >>
> >> on successful mapping, my icon properties would be:
> >> Target: W:\TAX\MYTAX.EXE
> >> StartIn: W:\TAX
> >>
> >> thanks
> >
> > i'll rephrase my query:
> > on a client, can a folder on a server drive be mapped - if that server drive/folder is not listed in 'Folder(Browse...)' of 'Map Network Drive' ?.
> >
> > how?
> >
> > thanks
> >
> Don't rely on browsing computers. Microsoft discourages the use of SMB 1
> so new NAS (and Windows itself) should implement SMB2 only and browsing
> network resources should be avoided.
>
> You can mount the shared folders to local drive letters. The server is
> reachable via UNC. No drive letters. (f.e \\192.168.0.1\mydir...)
>
> Dan
dan,
if my app is in D: of the server (server name: SERVEROFFICE)
folder: TAX
exe: MYTAX.EXE

after mapping, what will be the properties in the icon (client)
(Target & StartIn)

thanks

On Wednesday, February 22, 2023 at 3:48:11 PM UTC+5:30, Dan wrote:
> Il 22/02/2023 05:44, timepro timesheet ha scritto:
> > On Tuesday, February 21, 2023 at 9:20:42 PM UTC+5:30, timepro timesheet wrote:
> >> On Tuesday, February 21, 2023 at 6:17:21 PM UTC+5:30, Dan wrote:
> >>> Il 21/02/2023 12:31, timepro timesheet ha scritto:
> >>>> is this right?
> >>>>
> >>>> A] NAS cannot be partitioned as C: D: E:
> >>>>
> >>>> B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.
> >>>>
> >>>> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> >>>>
> >>>> in the client system:
> >>>> when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
> >>>> -but-
> >>>> when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)
> >>>>
> >>>> thank you
> >>>>
> >>>>
> >>> To be visible by a Windows machine, the NAS must expose SMB protocol to
> >>> clients (usually via SAMBA).
> >>> Once you see the server via SMB, you can treat it as a normal networked
> >>> Windows machine.
> >>> So you can map f.e. \\mynas\TAXDRIVE to Z:
> >>>
> >>> Dan
> >> thanks dan.
> >>
> >> will someone...(Y/N)
> >> A] NAS cannot be partitioned as C: D: E:
> >> B] each folder in NAS is similar/equivalent to what a drive/partition(C:,D:,E:) is in a conventional HDD.
> >> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> >> *
> >>
> >> :Mapping Query:
> >> my app resides in 'TAX' folder in D: of the server (server name: 'serveroffice')
> >> .exe: MYTAX.EXE.
> >> in LAN, i am trying to MAP the D: server as W: in a client.
> >> -Map Network Drive
> >> -Drive: W
> >> -but when i click on 'Folder', the D: of the server is not listed. (neither does 'serveroffice')
> >> (in 'Folder:' only the TAX folder in D: has to be selected - not the entire D:)
> >>
> >> BUT
> >>
> >> there's another app on the same client, where it's icon's properties are:
> >> Drive: W
> >> Folder W:\SHOP\SHOPITEM.EXE
> >>
> >> -so, how do i get 'serveroffice' or D: of the server get listed & be mapped.
> >>
> >> on successful mapping, my icon properties would be:
> >> Target: W:\TAX\MYTAX.EXE
> >> StartIn: W:\TAX
> >>
> >> thanks
> >
> > i'll rephrase my query:
> > on a client, can a folder on a server drive be mapped - if that server drive/folder is not listed in 'Folder(Browse...)' of 'Map Network Drive' ?.
> >
> > how?
> >
> > thanks
> >
> Don't rely on browsing computers. Microsoft discourages the use of SMB 1
> so new NAS (and Windows itself) should implement SMB2 only and browsing
> network resources should be avoided.
>
> You can mount the shared folders to local drive letters. The server is
> reachable via UNC. No drive letters. (f.e \\192.168.0.1\mydir...)
>
> Dan
dan:

learning, understanding, using... SMB2 will take some doing from me. (it's a totally new concept/operation for me)
-i even had to google what SMB2 is.
but, at this present moment, my user is stuck at:

'on a client system, how to map \TAX folder residing in D: of the server - if D: drive/folder is not listed/visible in 'Folder(Browse...)' of 'Map Network Drive' ?. '

thanks

On Wednesday, 22 February 2023 at 10:07:09 pm UTC+11, timepro timesheet wrote:
> On Wednesday, February 22, 2023 at 3:48:11 PM UTC+5:30, Dan wrote:
> > Il 22/02/2023 05:44, timepro timesheet ha scritto:
> > > On Tuesday, February 21, 2023 at 9:20:42 PM UTC+5:30, timepro timesheet wrote:
> > >> On Tuesday, February 21, 2023 at 6:17:21 PM UTC+5:30, Dan wrote:
> > >>> Il 21/02/2023 12:31, timepro timesheet ha scritto:
> > >>>> is this right?
> > >>>>
> > >>>> A] NAS cannot be partitioned as C: D: E:
> > >>>>
> > >>>> B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.
> > >>>>
> > >>>> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> > >>>>
> > >>>> in the client system:
> > >>>> when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
> > >>>> -but-
> > >>>> when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)
> > >>>>
> > >>>> thank you
> > >>>>
> > >>>>
> > >>> To be visible by a Windows machine, the NAS must expose SMB protocol to
> > >>> clients (usually via SAMBA).
> > >>> Once you see the server via SMB, you can treat it as a normal networked
> > >>> Windows machine.
> > >>> So you can map f.e. \\mynas\TAXDRIVE to Z:
> > >>>
> > >>> Dan
> > >> thanks dan.
> > >>
> > >> will someone...(Y/N)
> > >> A] NAS cannot be partitioned as C: D: E:
> > >> B] each folder in NAS is similar/equivalent to what a drive/partition(C:,D:,E:) is in a conventional HDD.
> > >> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> > >> *
> > >>
> > >> :Mapping Query:
> > >> my app resides in 'TAX' folder in D: of the server (server name: 'serveroffice')
> > >> .exe: MYTAX.EXE.
> > >> in LAN, i am trying to MAP the D: server as W: in a client.
> > >> -Map Network Drive
> > >> -Drive: W
> > >> -but when i click on 'Folder', the D: of the server is not listed. (neither does 'serveroffice')
> > >> (in 'Folder:' only the TAX folder in D: has to be selected - not the entire D:)
> > >>
> > >> BUT
> > >>
> > >> there's another app on the same client, where it's icon's properties are:
> > >> Drive: W
> > >> Folder W:\SHOP\SHOPITEM.EXE
> > >>
> > >> -so, how do i get 'serveroffice' or D: of the server get listed & be mapped.
> > >>
> > >> on successful mapping, my icon properties would be:
> > >> Target: W:\TAX\MYTAX.EXE
> > >> StartIn: W:\TAX
> > >>
> > >> thanks
> > >
> > > i'll rephrase my query:
> > > on a client, can a folder on a server drive be mapped - if that server drive/folder is not listed in 'Folder(Browse...)' of 'Map Network Drive' ?.
> > >
> > > how?
> > >
> > > thanks
> > >
> > Don't rely on browsing computers. Microsoft discourages the use of SMB 1
> > so new NAS (and Windows itself) should implement SMB2 only and browsing
> > network resources should be avoided.
> >
> > You can mount the shared folders to local drive letters. The server is
> > reachable via UNC. No drive letters. (f.e \\192.168.0.1\mydir...)
> >
> > Dan
> dan:
>
> learning, understanding, using... SMB2 will take some doing from me. (it's a totally new concept/operation for me)
> -i even had to google what SMB2 is.
> but, at this present moment, my user is stuck at:
>
> 'on a client system, how to map \TAX folder residing in D: of the server - if D: drive/folder is not listed/visible in 'Folder(Browse...)' of 'Map Network Drive' ?. '
>
> thanks

UNC mapping should be your friend if you have the correct permissions.

On Tuesday, February 28, 2023 at 6:51:31 AM UTC+5:30, poopall wrote:
> On Wednesday, 22 February 2023 at 10:07:09 pm UTC+11, timepro timesheet wrote:
> > On Wednesday, February 22, 2023 at 3:48:11 PM UTC+5:30, Dan wrote:
> > > Il 22/02/2023 05:44, timepro timesheet ha scritto:
> > > > On Tuesday, February 21, 2023 at 9:20:42 PM UTC+5:30, timepro timesheet wrote:
> > > >> On Tuesday, February 21, 2023 at 6:17:21 PM UTC+5:30, Dan wrote:
> > > >>> Il 21/02/2023 12:31, timepro timesheet ha scritto:
> > > >>>> is this right?
> > > >>>>
> > > >>>> A] NAS cannot be partitioned as C: D: E:
> > > >>>>
> > > >>>> B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.
> > > >>>>
> > > >>>> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> > > >>>>
> > > >>>> in the client system:
> > > >>>> when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
> > > >>>> -but-
> > > >>>> when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)
> > > >>>>
> > > >>>> thank you
> > > >>>>
> > > >>>>
> > > >>> To be visible by a Windows machine, the NAS must expose SMB protocol to
> > > >>> clients (usually via SAMBA).
> > > >>> Once you see the server via SMB, you can treat it as a normal networked
> > > >>> Windows machine.
> > > >>> So you can map f.e. \\mynas\TAXDRIVE to Z:
> > > >>>
> > > >>> Dan
> > > >> thanks dan.
> > > >>
> > > >> will someone...(Y/N)
> > > >> A] NAS cannot be partitioned as C: D: E:
> > > >> B] each folder in NAS is similar/equivalent to what a drive/partition(C:,D:,E:) is in a conventional HDD.
> > > >> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> > > >> *
> > > >>
> > > >> :Mapping Query:
> > > >> my app resides in 'TAX' folder in D: of the server (server name: 'serveroffice')
> > > >> .exe: MYTAX.EXE.
> > > >> in LAN, i am trying to MAP the D: server as W: in a client.
> > > >> -Map Network Drive
> > > >> -Drive: W
> > > >> -but when i click on 'Folder', the D: of the server is not listed. (neither does 'serveroffice')
> > > >> (in 'Folder:' only the TAX folder in D: has to be selected - not the entire D:)
> > > >>
> > > >> BUT
> > > >>
> > > >> there's another app on the same client, where it's icon's properties are:
> > > >> Drive: W
> > > >> Folder W:\SHOP\SHOPITEM.EXE
> > > >>
> > > >> -so, how do i get 'serveroffice' or D: of the server get listed & be mapped.
> > > >>
> > > >> on successful mapping, my icon properties would be:
> > > >> Target: W:\TAX\MYTAX.EXE
> > > >> StartIn: W:\TAX
> > > >>
> > > >> thanks
> > > >
> > > > i'll rephrase my query:
> > > > on a client, can a folder on a server drive be mapped - if that server drive/folder is not listed in 'Folder(Browse...)' of 'Map Network Drive' ?.
> > > >
> > > > how?
> > > >
> > > > thanks
> > > >
> > > Don't rely on browsing computers. Microsoft discourages the use of SMB 1
> > > so new NAS (and Windows itself) should implement SMB2 only and browsing
> > > network resources should be avoided.
> > >
> > > You can mount the shared folders to local drive letters. The server is
> > > reachable via UNC. No drive letters. (f.e \\192.168.0.1\mydir...)
> > >
> > > Dan
> > dan:
> >
> > learning, understanding, using... SMB2 will take some doing from me. (it's a totally new concept/operation for me)
> > -i even had to google what SMB2 is.
> > but, at this present moment, my user is stuck at:
> >
> > 'on a client system, how to map \TAX folder residing in D: of the server - if D: drive/folder is not listed/visible in 'Folder(Browse...)' of 'Map Network Drive' ?. '
> >
> > thanks
> UNC mapping should be your friend if you have the correct permissions.

thanks everyone for the contribution.

*for UNC mapping, would someone please jot down the steps.*
(on a standalonePC, i simulated LAN using NET USE W: \\SINGLEPC\C\MYTAX, but from cmd prompt, W: works slower)

for reference, this is how i map CURRENTLY: (servername:SERVEROFFICE, clientname:TAXPC)
* -rightclick ThisPc
-Map Network Drive
-Drive (W: or T: or Z: or...)
-Folder_Browse (besides SERVEROFFICE,will list all networked systems)
-Click SERVEROFFICE
-Click D (my app installed in D:. mapping 'entire' D:, although my app,.dbf,.exe,.dll are in MYTAX folder)
-Reconnect at Signin
-Finish
[desktop icon properties]
-Target W:\MYTAX\TAX.EXE
-StartIn W:\MYTAX
*

On Tuesday, 28 February 2023 at 2:12:27 pm UTC+11, timepro timesheet wrote:
> On Tuesday, February 28, 2023 at 6:51:31 AM UTC+5:30, poopall wrote:
> > On Wednesday, 22 February 2023 at 10:07:09 pm UTC+11, timepro timesheet wrote:
> > > On Wednesday, February 22, 2023 at 3:48:11 PM UTC+5:30, Dan wrote:
> > > > Il 22/02/2023 05:44, timepro timesheet ha scritto:
> > > > > On Tuesday, February 21, 2023 at 9:20:42 PM UTC+5:30, timepro timesheet wrote:
> > > > >> On Tuesday, February 21, 2023 at 6:17:21 PM UTC+5:30, Dan wrote:
> > > > >>> Il 21/02/2023 12:31, timepro timesheet ha scritto:
> > > > >>>> is this right?
> > > > >>>>
> > > > >>>> A] NAS cannot be partitioned as C: D: E:
> > > > >>>>
> > > > >>>> B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.
> > > > >>>>
> > > > >>>> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> > > > >>>>
> > > > >>>> in the client system:
> > > > >>>> when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
> > > > >>>> -but-
> > > > >>>> when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)
> > > > >>>>
> > > > >>>> thank you
> > > > >>>>
> > > > >>>>
> > > > >>> To be visible by a Windows machine, the NAS must expose SMB protocol to
> > > > >>> clients (usually via SAMBA).
> > > > >>> Once you see the server via SMB, you can treat it as a normal networked
> > > > >>> Windows machine.
> > > > >>> So you can map f.e. \\mynas\TAXDRIVE to Z:
> > > > >>>
> > > > >>> Dan
> > > > >> thanks dan.
> > > > >>
> > > > >> will someone...(Y/N)
> > > > >> A] NAS cannot be partitioned as C: D: E:
> > > > >> B] each folder in NAS is similar/equivalent to what a drive/partition(C:,D:,E:) is in a conventional HDD.
> > > > >> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> > > > >> *
> > > > >>
> > > > >> :Mapping Query:
> > > > >> my app resides in 'TAX' folder in D: of the server (server name: 'serveroffice')
> > > > >> .exe: MYTAX.EXE.
> > > > >> in LAN, i am trying to MAP the D: server as W: in a client.
> > > > >> -Map Network Drive
> > > > >> -Drive: W
> > > > >> -but when i click on 'Folder', the D: of the server is not listed. (neither does 'serveroffice')
> > > > >> (in 'Folder:' only the TAX folder in D: has to be selected - not the entire D:)
> > > > >>
> > > > >> BUT
> > > > >>
> > > > >> there's another app on the same client, where it's icon's properties are:
> > > > >> Drive: W
> > > > >> Folder W:\SHOP\SHOPITEM.EXE
> > > > >>
> > > > >> -so, how do i get 'serveroffice' or D: of the server get listed & be mapped.
> > > > >>
> > > > >> on successful mapping, my icon properties would be:
> > > > >> Target: W:\TAX\MYTAX.EXE
> > > > >> StartIn: W:\TAX
> > > > >>
> > > > >> thanks
> > > > >
> > > > > i'll rephrase my query:
> > > > > on a client, can a folder on a server drive be mapped - if that server drive/folder is not listed in 'Folder(Browse...)' of 'Map Network Drive' ?.
> > > > >
> > > > > how?
> > > > >
> > > > > thanks
> > > > >
> > > > Don't rely on browsing computers. Microsoft discourages the use of SMB 1
> > > > so new NAS (and Windows itself) should implement SMB2 only and browsing
> > > > network resources should be avoided.
> > > >
> > > > You can mount the shared folders to local drive letters. The server is
> > > > reachable via UNC. No drive letters. (f.e \\192.168.0.1\mydir...)
> > > >
> > > > Dan
> > > dan:
> > >
> > > learning, understanding, using... SMB2 will take some doing from me. (it's a totally new concept/operation for me)
> > > -i even had to google what SMB2 is.
> > > but, at this present moment, my user is stuck at:
> > >
> > > 'on a client system, how to map \TAX folder residing in D: of the server - if D: drive/folder is not listed/visible in 'Folder(Browse...)' of 'Map Network Drive' ?. '
> > >
> > > thanks
> > UNC mapping should be your friend if you have the correct permissions.
> thanks everyone for the contribution.
>
> *for UNC mapping, would someone please jot down the steps.*
> (on a standalonePC, i simulated LAN using NET USE W: \\SINGLEPC\C\MYTAX, but from cmd prompt, W: works slower)
>
>
> for reference, this is how i map CURRENTLY: (servername:SERVEROFFICE, clientname:TAXPC)
> *
> -rightclick ThisPc
> -Map Network Drive
> -Drive (W: or T: or Z: or...)
> -Folder_Browse (besides SERVEROFFICE,will list all networked systems)
> -Click SERVEROFFICE
> -Click D (my app installed in D:. mapping 'entire' D:, although my app,.dbf,.exe,.dll are in MYTAX folder)
> -Reconnect at Signin
> -Finish
> [desktop icon properties]
> -Target W:\MYTAX\TAX.EXE
> -StartIn W:\MYTAX
> *

Looks ok to me : so you can use net use w:\\\SINGLEPC\C\MYTAX you can include the username and password and make the connection persistent /PERSISTENT: YES

See net use ?

You could also include the net use ... create etc in a .bat Batch file and run at startup

If you want make sure that only the folder that you need is shared, and therefore access to the entire drive may not be required.

NET USE W: \\SINGLEPC\C\MYTAX /PERSISTENT:YES , but from cmd prompt, W: works slower (This looks OK) However I have never used UNC mapping to a folder on my own computer, so I could not tell you why it would appear to be slower

On Tuesday, February 28, 2023 at 4:42:18 PM UTC+5:30, poopall wrote:
> On Tuesday, 28 February 2023 at 2:12:27 pm UTC+11, timepro timesheet wrote:
> > On Tuesday, February 28, 2023 at 6:51:31 AM UTC+5:30, poopall wrote:
> > > On Wednesday, 22 February 2023 at 10:07:09 pm UTC+11, timepro timesheet wrote:
> > > > On Wednesday, February 22, 2023 at 3:48:11 PM UTC+5:30, Dan wrote:
> > > > > Il 22/02/2023 05:44, timepro timesheet ha scritto:
> > > > > > On Tuesday, February 21, 2023 at 9:20:42 PM UTC+5:30, timepro timesheet wrote:
> > > > > >> On Tuesday, February 21, 2023 at 6:17:21 PM UTC+5:30, Dan wrote:
> > > > > >>> Il 21/02/2023 12:31, timepro timesheet ha scritto:
> > > > > >>>> is this right?
> > > > > >>>>
> > > > > >>>> A] NAS cannot be partitioned as C: D: E:
> > > > > >>>>
> > > > > >>>> B] each folder in NAS is similar to what a drive(C:,D:,E:) is in a conventional HDD.
> > > > > >>>>
> > > > > >>>> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> > > > > >>>>
> > > > > >>>> in the client system:
> > > > > >>>> when mapped to a server with a conventional HDD , Target in the icon will be Z:\TAX\MYTAX.EXE
> > > > > >>>> -but-
> > > > > >>>> when mapped to a NAS server, the Target in the icon will be \TAXDRIVE\TAX\MYTAX.EXE. (where TAXDRIVE is a 'folder' in the NAS)
> > > > > >>>>
> > > > > >>>> thank you
> > > > > >>>>
> > > > > >>>>
> > > > > >>> To be visible by a Windows machine, the NAS must expose SMB protocol to
> > > > > >>> clients (usually via SAMBA).
> > > > > >>> Once you see the server via SMB, you can treat it as a normal networked
> > > > > >>> Windows machine.
> > > > > >>> So you can map f.e. \\mynas\TAXDRIVE to Z:
> > > > > >>>
> > > > > >>> Dan
> > > > > >> thanks dan.
> > > > > >>
> > > > > >> will someone...(Y/N)
> > > > > >> A] NAS cannot be partitioned as C: D: E:
> > > > > >> B] each folder in NAS is similar/equivalent to what a drive/partition(C:,D:,E:) is in a conventional HDD.
> > > > > >> C] each folder in the NAS can be mapped as an independent drive (when mapped in a client system).
> > > > > >> *
> > > > > >>
> > > > > >> :Mapping Query:
> > > > > >> my app resides in 'TAX' folder in D: of the server (server name: 'serveroffice')
> > > > > >> .exe: MYTAX.EXE.
> > > > > >> in LAN, i am trying to MAP the D: server as W: in a client.
> > > > > >> -Map Network Drive
> > > > > >> -Drive: W
> > > > > >> -but when i click on 'Folder', the D: of the server is not listed. (neither does 'serveroffice')
> > > > > >> (in 'Folder:' only the TAX folder in D: has to be selected - not the entire D:)
> > > > > >>
> > > > > >> BUT
> > > > > >>
> > > > > >> there's another app on the same client, where it's icon's properties are:
> > > > > >> Drive: W
> > > > > >> Folder W:\SHOP\SHOPITEM.EXE
> > > > > >>
> > > > > >> -so, how do i get 'serveroffice' or D: of the server get listed & be mapped.
> > > > > >>
> > > > > >> on successful mapping, my icon properties would be:
> > > > > >> Target: W:\TAX\MYTAX.EXE
> > > > > >> StartIn: W:\TAX
> > > > > >>
> > > > > >> thanks
> > > > > >
> > > > > > i'll rephrase my query:
> > > > > > on a client, can a folder on a server drive be mapped - if that server drive/folder is not listed in 'Folder(Browse...)' of 'Map Network Drive' ?.
> > > > > >
> > > > > > how?
> > > > > >
> > > > > > thanks
> > > > > >
> > > > > Don't rely on browsing computers. Microsoft discourages the use of SMB 1
> > > > > so new NAS (and Windows itself) should implement SMB2 only and browsing
> > > > > network resources should be avoided.
> > > > >
> > > > > You can mount the shared folders to local drive letters. The server is
> > > > > reachable via UNC. No drive letters. (f.e \\192.168.0.1\mydir...)
> > > > >
> > > > > Dan
> > > > dan:
> > > >
> > > > learning, understanding, using... SMB2 will take some doing from me.. (it's a totally new concept/operation for me)
> > > > -i even had to google what SMB2 is.
> > > > but, at this present moment, my user is stuck at:
> > > >
> > > > 'on a client system, how to map \TAX folder residing in D: of the server - if D: drive/folder is not listed/visible in 'Folder(Browse...)' of 'Map Network Drive' ?. '
> > > >
> > > > thanks
> > > UNC mapping should be your friend if you have the correct permissions..
> > thanks everyone for the contribution.
> >
> > *for UNC mapping, would someone please jot down the steps.*
> > (on a standalonePC, i simulated LAN using NET USE W: \\SINGLEPC\C\MYTAX, but from cmd prompt, W: works slower)
> >
> >
> > for reference, this is how i map CURRENTLY: (servername:SERVEROFFICE, clientname:TAXPC)
> > *
> > -rightclick ThisPc
> > -Map Network Drive
> > -Drive (W: or T: or Z: or...)
> > -Folder_Browse (besides SERVEROFFICE,will list all networked systems)
> > -Click SERVEROFFICE
> > -Click D (my app installed in D:. mapping 'entire' D:, although my app,..dbf,.exe,.dll are in MYTAX folder)
> > -Reconnect at Signin
> > -Finish
> > [desktop icon properties]
> > -Target W:\MYTAX\TAX.EXE
> > -StartIn W:\MYTAX
> > *
> Looks ok to me : so you can use net use w:\\\SINGLEPC\C\MYTAX you can include the username and password and make the connection persistent /PERSISTENT: YES
>
> See net use ?
>
> You could also include the net use ... create etc in a .bat Batch file and run at startup
>
> If you want make sure that only the folder that you need is shared, and therefore access to the entire drive may not be required.
>
> NET USE W: \\SINGLEPC\C\MYTAX /PERSISTENT:YES , but from cmd prompt, W: works slower (This looks OK) However I have never used UNC mapping to a folder on my own computer, so I could not tell you why it would appear to be slower

1.
so, if i map with:
option a) rtclick-thispc,map-network-drive, select drive, ....finish
option b) net use X: \\server\serverdrive\serverfolder /persistent:yes

in the client, which would open files,process,save,reindex... quicker (or would it still depend on my prg coding)

2.
is there a better/quicker alternative to:
sele 0
use abc inde abc1,abc2,abc3...
sele 0
sele def inde def,def2;def3,def4
....
....
sele 0
sele pqr inde pqr,pqr2,pqr3,pqr4

sele def
seek compani+dtos(billdate)+str(amount,10)+clientname
do whil def_field1=compani.and.def_field2=billdate.and.def_field3=amount.and....eof()
if clientgst='invalid';skip;loop;end
....
....
skip
endd
....
...