We have recently installed Power GEOPAK V8i. In the past we had Microstation V8i and GEOPAK installed seperatly and our mslocal.cfg files were mapped to our server. With the newley installed Power GEOPAK V8i, I have not been successful in mapping the workspace. Power GEOPAK V8i comes with both a msdir.cfg file and mslocal.cfg file. Which one should be used to map the workspace to our server and I will also need help with the code. Our original code for mslocal.cfg that worked for our previous software is the first one below, the new Power GEOPAK V8i mslocal.cfg is the second one below and the 3rd one is the Power GEOPAK v8i msdir.cfg.Thanks for your help.
1.original mslocal.cfg
MSDIR = C:/Program Files/Bentley/Program/MicroStation/#_USTN_WORKSPACEROOT : C:/Program Files/Bentley/Workspace/_USTN_WORKSPACEROOT : Z:/Program Files/Bentley/Workspace/
%include $(MSDIR)config\msconfig.cfg
2. Power GEOPAK V8i mslocal.cfg
%include msdir.cfg_USTN_WORKSPACEROOT : ${_USTN_INSTALLED_WORKSPACEROOT}MSDIR : ${MSDIR_INSTALLED}%include $(MSDIR)config/msconfig.cfg
3. Power GEOPAK V8i msdir.cfg
[General]_USTN_INSTALLED_WORKSPACEROOT=C:\Documents and Settings\All Users.WINDOWS\Application Data\Bentley\PowerGEOPAK V8i\\WorkSpace/MSDIR_INSTALLED=${_ROOTDIR}MS_PRODUCTCODEGUID={9B761AD8-C9AB-40F1-BA77-C24AE5B72D18}
I hope you've solved this issue by now but I'll point out a few things in case others look at this issue.
The normal processing of config files when MicroStation/GEOPAK launch is to open mslocal.cfg, which then calls msdir.cfg and finally msconfig.cfg.
The default mslocal.cfg upon installation of MicroStation/GEOPAK looks like your #2 above, which has the include for msdir.cfg. In your case someone has removed that from your original mslocal.cfg thus msdir.cfg in #1 would never be called/used.
If you do the following (in place of what you have) in msdir.cfg
_USTN_INSTALLED_WORKSPACEROOT=Z:/Program Files/Bentley/Workspace/
your workspace will be found on your mapped network driver rather than on C:
A few reminders on the way the config language works:
Using = within the assignment of a path FORCES the path variable to be set
Example:
MSDIR = C:/Program Files/Bentley/Program/MicroStation/
Using : within the assignment of a path ONLY sets the path variable if it doesn't already have a value
MSDIR : ${MSDIR_INSTALLED}
Using ${<path variable name>} immediately sets/expands the value of the path variable
Example: (fictitious path names to shorten example)
MSDIR_INSTALLED = c:\Program Files\GeoPak\
MSDIR = ${MSDIR_INSTALLED}stuff\
MSDIR will equal c:\Program Files\GeoPak\stuff\ regardless of MSDIR_INSTALLED changing downstream
Using $(<path variable name>) stores the path variable as a part of the value and can change in the future
MSDIR = $(MSDIR_INSTALLED)stuff\
MSDIR will be stored as $(MSDIR_INSTALLED)stuff\ and only when it is used will it be evaluated. Thus if MSDIR_INSTALLED was changed by a config file later on MSDIR would reflect that change.