Drive mapping vs. shortcut

[Guest]

This is probably a very dumb question, but what is the difference between
mapping a drive to access shared folders on a network server (from an XP SP2
client) vs. browsing to the network server folder and creating a shortcut on
the desktop to the folder? Is one method preferred over the other,and if so,
why? Thanks.

 

[Ted]

A shortcut to a network share is easier, because you
can place it on the Desktop or Startmenu, it opens
the file or directory in the network computer.
Not easy to make a shortcut though, you would have
to make any shortcut on your Desktop, right click it
and select Property, change the path to
\\ComputerName\Share or drive letter\Application.exe
for example.

A Mapped share or drive have to be accessed
from the Windows Explorer and get started by clicking
the Tool\Map Network Drive menu.
Then you have to enter
\\ComputerName\Share or drive letter\Application.exe
for example.

Where:
ComputerName= Is the Name of the Network Computer
Share or Drive letter = Could be C or D drive, or the share name
Application.exe = Could be a file or subdirectory

 

[Malke]

This is probably a very dumb question, but what is the difference
between mapping a drive to access shared folders on a network server
(from an XP SP2 client) vs. browsing to the network server folder and
creating a shortcut on the desktop to the folder? Is one method
preferred over the other,and if so, why? Thanks.

When you map a drive, it makes the host computer think the drive is
local. Some programs - particularly niche software - running on a
server require mapping drives. You need a good network connection that
is always up for this. This is ideal for machines in a business where
the server and workstations are never turned off. When you reboot the
workstations, they need to take the time to find all their mapped
drives.

The shortcut is just that - the connection isn't looked for until you
click on it.

Malke