Microstation V8i configuration files

Hi,

Unknown said:

I am having problems

What kind of problem do you have. Can you provide more information and explanation why you treat the situation as the problem? As Tim wrote in his answer, the output from DEBUG would be valuable.

Unknown said:

on two separate computers, I get different results

It's expected behaviour. The final setting of MicroStation workspace includes a processing of more configuration files and tens of configuration variables, where some of them are conditional. The question is how big the differencies are.

Unknown said:

How do I make sure the configuration is pointing ONLY to the locations which I want it to for line styles, cells, and fonts?

What is your knowledge how workspace setting is created from the configuration files? If you will create msdebug file and will read it, you will see how particular variables are created and by different configuration files, so you will be able to decide what and how to set to reach you aim.

With regards,

  Jan

My knowledge is VERY limited, but I am determined to understand how this works.  Debug does not seem to work.

When you run MicroStation using the -debug switch, it write msdebug.txt to the %temp% folder. You need a space between the ustation.exe and the -debug. If it works, you'll know as it opens a DOS window and the results scroll past until at the end when you must press a key to close the window. In the window, it does give the path to the file it creates.

On source of differences when identical projects are used is the user.cfg files. Someone can change something in the workspace configuration dialog box that results in a value being set  that overrides the value in the PCF files.

When you run MicroStation using the -debug switch, it write msdebug.txt to the %temp% folder. You need a space between the ustation.exe and the -debug. If it works, you'll know as it opens a DOS window and the results scroll past until at the end when you must press a key to close the window. In the window, it does give the path to the file it creates.

On source of differences when identical projects are used is the user.cfg files. Someone can change something in the workspace configuration dialog box that results in a value being set  that overrides the value in the PCF files.

Attached is my debug file

Can you attach a debug from a machine that works, and one that it doesn't work for comparison?

This is from another location

For viewing pleasure, attached is how my project config is currently set up.

Hi,

a few notes:

• The msdebug files you posted were created for different projects and as such are useless, because cannot be compared. You have to generate them for the exactly same workspace configuration, so please create them both again with proper project and user set. The arguments will be something like ...ustation.exe -DEBUG=5 -WP1201-AE-UPTOWN -WUuntitled
• At the end of your pcf file, there is a line -DEBUG=N. Remove it, its nothing that can be in any MicroStation configuration file, because it's not configuration macro.
• These two MicroStation installations were done differently: In one case the workspace was installed locally, in the second it was installed to S drive. Why?
• What I don't understand is you overall idea what and how you want to share. It should be defined well before any configuration is done. What is in my opinion big mistake and wrong solution is you place cell and other file into System folder in the workspace of one MicroStation and define configurations in project file ... it's bad.
• The files you define (cells...) are company wide or project wide? From this information the configuration has to start.

With regards,

  Jan