1. Archway Systems, Inc. Mike Lazear

2. Profile SELECTservices Learning (LEARNserver) Communities (BeCommunities) Video (BeConnected) Events Bentley Student Center (YouTube channel) Bentley LEARNing Conference free on-demand recordings How to learn Bentley Products – YouTube video

3. Bentley Configuration Explorer o Shows all configuration variables and their values o Free from Bentley’s web site – iWare app for PC o http://www.bentley.com/en- US/Free+Software/Bentley+Configuration+Explorer.htm http://www.bentley.com/en- US/Free+Software/Bentley+Configuration+Explorer.htm Notepad++ o Free Notepad type editor that has many excellent features o http://notepad-plus-plus.org/ http://notepad-plus-plus.org/ o Use Settings > Style Configurator to add ucf, pcf, cfg to ini file entry Windows Explorer (part of Windows, Windows-E to launch) o Add path to Workspace and to MicroStation V8i to Favorites

4. MicroStation uses Configuration files to control how it runs Configuration files contain configuration variables The configuration files are searched for in a specific order Examples:.ucf – User Configuration file o Typically located in …\WorkSpace\Users o Editable text..pcf – Project Configuration file o Typically located in …\WorkSpace\Projects o Editable text..cfg – General Configuration file o Editable text..upf – User Preferences file. o Binary file. Edit by changing settings in Workspace > Preferences. o Storage depends on Windows release but stored within User’s folder (see MS_USERPREF) See Workspace > About Workspace for location of current config files being used

5. Program configuration path variables o Tells MicroStation where to find.exe,.dll as well as other file types o Typically will start with a c:\Program Files or c:\Program Files (x86) Workspace (i.e. Data) configuration path variables o Tells MicroStation where to find resource files like dgnlib, rsc, mvba o Typically will start with a c:\ProgramData path Value Configuration variables o Actual values used to tell MicroStation o Ex. 0, 1, 08.11.09.357, FALSE, markup

6. 0) System Level 1) Application Level 2) Site Level 3) Project Level 4) User Level Processed in the above order, Application overrides System, Site overrides Application, Project overrides Site and User overrides Projects. Thus User Level takes priority over all other levels unless locked at an earlier level.

7. 0) System Level o Set by Bentley Developers – avoid changing 1) Application Level o Set by Add-on Application Developers – avoid changing 2) Site Level o Set on behalf of corporate/site management by System/IT Manager 3) Project Level o Set by, or on behalf of, the Project Manager 4) User Level o Set by, or on behalf of, the User These are typical guidelines and not hard & fast rules

8. 0) System Level o …\Program Files\Bentley\Microstation V8i (SELECTseries)\MicroStation\config o mslocal.cfg – location of MicroStation and includes the next two o msdir.cfg – location of WorkSpace o Msconfig.cfg – controls the reading of all other config files and levels 1) Application Level 2) Site Level 3) Project Level 4) User Level

9. 0) System Level 1) Application Level o …\config\appl (this is one folder below the System Level config files) o Set by add-on applications (ex. clashDetection, ProjectWise) o File names ex.: ClashDetection.cfg, PW.cfg, ComponentView.cfg o Could redefine system level config variables but more likely to add new config variables or add additional paths to existing 2) Site Level 3) Project Level 4) User Level

10. 0) System Level 1) Application Level 2) Site Level o …\Workspace\Standards o Contains config customization for the company or site o By default all.cfg (any name) in the Standards folder will be read See use of _USTN_SITE in MSCONFIG.CFG o Many folders with Standards that include dgnlib, cells, macros (.mvba), plot configuration files (pltcfg), seeds, and more 3) Project Level 4) User Level

11. 0) System Level 1) Application Level 2) Site Level 3) Project Level o …\Workspace\Projects o Read AFTER User Level but processed BEFORE User Level o Contains config customization for the project in.pcf file o Many folders within the named project folder with Projects that include dgnlib, cells, macros (.mvba), plot configuration files (pltcfg), seeds, and more o Ex. …\Projects\Building\dgnlib\Levels.dgnlib 4) User Level

12. 0) System Level 1) Application Level 2) Site Level 3) Project Level 4) User Level o …\Workspace\Users o Is read BEFORE Project Level but processed AFTER Project Level o Determines which Project configuration file is processed, which is the reason it is read before the Project Level. o Contains config customization for the user in.ucf file

13. _ROOTDIR o C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation\ MSDIR o ${MS} or ${_ROOTDIR}/ o C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation\ _USTN_BENTLEYROOT o ${parentdevdir {MSDIR}} o C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\ __USTN_WORKSPACEROOT o _USTN_WORKSPACEROOT : ${_USTN_INSTALLED_WORKSPACEROOT} o C:\ProgramData\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\ _USTN_HOMEROOT

14. $(VARIABLEREF) = Expand VARIABLEREF when this variable is used. ${VARIABLEREF} = Expand to current value of VARIABLEREF and does not change. Configuration variables use / instead of \ internally changed to \ when needed All Path variables (should) end with /

15. MS_DIR = “C:/Stuff/” MS_DEF = $(MS_DIR) MS_SEEDFILES = ${MS_DIR} > All variables if accessed at this point equal “C:/Stuff/” If later we set MS_DIR = “D:/Stuff/” If variables accessed at this point what would the values be? o MS_DIR = “D:/Stuff/” o MS_DEF = “D:/Stuff/” o MS_SEEDFILES = “C:/Stuff/

16. = Assign “new_value” to “VARIABLENAME” :Assign “new_value” to “VARIABLENAME” only if that variable does not already exist (not already set) >Append directory or file lists defined by “new_value” to a variable definition that defines a path. <Prepend directory or file list defined by “new_value” to the beginning of a variable defintion that defines a path. +Append “new_value” to current value of “VARIABLENAME”. Uses a space as a separator. (rarely used)

17. %include Includes another config file %if Execute following lines if expression is true %elseExecute following lines if original expression on %if was false %endifEnd of conditional block %error Print “string” and exit MicroStation %lock Locks the configuration variable %levelSet the level of processing

18. To get a listing of all MicroStation’s Configuration Variables o load the cfgvars.ma (mdl app) o Utilities > MDL Applications. Click the Browse button and open the “asneeded” folder. Load cfgvars.ma. o Utilities > key-in type the following: mdl load cfgvars printCfgVarResource (case sensitive) o In the MicroStation root directory (within Program Files) search for cfgvars.txt and cfglong.txt. These files list the configuration variables. Setting _USTN_DISPLAYALLCFGVARS to 1 Workspace > Configuration will show the hidden system Configuration variables. https://communities.bentley.com/products/microstation/w/micr ostation__wiki/microstation-v8i-variables.aspx https://communities.bentley.com/products/microstation/w/micr ostation__wiki/microstation-v8i-variables.aspx