You are currently reviewing an older revision of this page.
NOTE: Remember to remove the switch from the icon after creating theMSDebug.txt file.
3. From the Windows "Run" command windowChoose Start > RunType the path to the ustation.exe file
Examples:For MicroStation V8 - c:\program files\Bentley\Program\Microstation\ustation.exe -debugFor MicroStation J - c:\Bentley\Program\MicroStation\Ustation.exe -debugFor MicroStation 95\SE - c:\win32app\ustation\ustation.exe -debugClick OK.You should get a DOS window that says "Debugging output saved to [msdebug.txt]".Hit the escape keyLocate the msdebug.txt file in the appropriate directory.How to make use of the MSDebug fileThere are basically two sections to the MSDebug file. The first sectioncontains a list of all the configuration files that run, and what variables were set byeach file. Each configuration file that gets run has a starting point and an endingpoint identified as follows:1. Processing macro file[C:\Bentley\Program\MicroStation\config\mslocal.cfg]2. End of macro file [C:\Bentley\Program\MicroStation\config\mslocal.cfg]Located in-between these two lines are all variables and their settingsthat get loadedfrom that particular configuration file:Examples:Processing macro file[d:\Bentley\Program\MicroStation\config\system\mslocale.cfg](system): MS_SPELLINGLANGUAGE=AmericanEnglish [AmericanEnglish](system): MS_HELPLOAD_LANGUAGE=en [en]End of macro file [d:\Bentley\Program\MicroStation\config\system\mslocale.cfg]Processing macro file [d:\Bentley\Program\MicroStation\config\appl\qvisgl.cfg](appl): MS_GRAPHICSACCELERATOR=qvisgl [qvisgl]End of macro file [d:\BentleyProgram\MicroStation\config\appl\qvisgl.cfg]It also indicates at what level the variable has been set, i.e. system,appl, user, site, project, or predefined.Below is a list of default configuration files that should be listed inthe MSDebug.txt:
The last section of the MSDebug.txt file is the Configuration Variable SummaryHere you will find the following:1. A listing of all configuration variables2. At what level each variable was set3. The full path to the location of the files4. Whether or not the variable is locked or unlockedUsing the MSDebug.txt file to help trouble shoot Processor exceptionerrorsThe msdebug file can help you trouble shoot Processor exception errorsby helping you find where specific files are located. The steps for this procedure arelisted below:1. Create the msdebug.txt file and then open it in notepad.2. Search for the following variables using the Search > Find drop downmenu, in notepad:MS_USERPREF (this will tell you where your user preference file islocated)MS_INITAPPS (this will tell you if any other programs are beinginitiated during startup)MS_SYMBRSRC (this will point you to the location where all theMicroStation resource files are located)MS_DGNAPPS (this will tell you what other programs are being launchedwith MicroStation)MS_DGNMACROS (this will tell you what macros are being launched with MicroStation)_USTN_UIPATH (this will tell you the location of any *.m0* files)3. Be sure to click the "next" button in the Search dialog box to besure you find all instances of the variables.