Mapped Drive Support

9.2

A section named '[mapdrives]' can be added to the PLBWIN INI file. Mapped drive assignments can be specified in the mapdrives section. The PLBWIN runtime uses the mapped drive settings to redirect either network drives or local DOS drives. The format of the entries in this section is:

{drv}:=[~]{redir}

Where:

{drv}

Drive device letter ( a to z ) inclusive.

{redir}

Drive device redirection string. This string can be a UNC path or a DOS drive path.

[~]

Optional character before the {redir} string to prevent removal of the {drv}.

Example:

[mapdrives]

f:=c:\temp

g:=\\server\sharename\directory

h:=~c:\sunbelt

i:=~\\server\sharename\directory

Note the following:

When the {redir} string starts with the '\' character, the redirection string identifies a network UNC path name. In this case, the {drv} is redirected as a network drive. If the {drv} already exists, the mapped drive redirection does not occur and no changes are made.
When the {redir} string is a DOS drive path string, the mapped drive redirection is executed as a local DOS drive device. If the {drv} already exists, the mapped drive redirection does not occur and no changes are made. The local DOS drive substitution is not supported for the Windows 95, 98, and ME OS versions. The mapped drives are ignored for these Windows versions.
When running as an automation server, the mapped drive redirection is executed when the AUTOMATION server is started using the /AUTOMATION command line option.
By default, the runtime removes the {drv} mapped drive when the runtime process is terminated. If the '~' character is specified as the leading character before the {redir} string, the runtime does not remove the {drv} when the runtime process is terminated.
When the runtime uses the '-d3' option, the mapped drives are logged when the runtime starts and the mapped drives are removed when the runtime terminates.
This feature is only supported when using PLBWIN and is not available for PLBNET or CE runtimes.