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.

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

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

To answer the notes above.  Please bear with me, I am not computer savvy and have no idea what I am doing, but I am the best my company has to offer in this subject.

The reason one is done locally and one is done through the S: drive is because the over all goal is to get everyone in the company to use the same config file.  The problem doesn't just lie between 2 computers, but with two "installations", I guess.  Both of the debugs were ran off one computer because I get the same general responses pending the location of the config file.  They are the same config file (or at least the ones I am attaching this morning are).

The cells, line styles, fonts, etc. will be project wide, since each project will require different settings.

Attached is the debug for the S: drive.

Hi,

I think the discussion should be split into two topics: (A) Why your current configuration doesn't work as expected and (B) How your workspace should be implemented in a right way. I think (A) is not so important now, because your try has substantial weaknesses, so we should focus on (B).

A few notes:

• MicroStation configuration, workspaces and configuration files are complex and wide area.
• To try something without good specification what is the aim and priorities usually fails.
• Each workspace (final MicroStation configuration) is a result of many configuration files. Because of that, msdebug is the basic tool how to share information. To discuss e.g. project file only is the same as to discuss car properties without knowledge about things like engine, its output, specific configuration etc.
• One situation / request can be sometimes solved in different ways.

You have defined that the basic features are:

• Files should be shared over network by more MicroStation users.
• Files like cells are project specific, so they should not be available generally.

What I think you can do (or at least try):
(It's a simplified template you can try and to modified accordingly to your needs.)

1. Leave System (and any other) MicroStation folder intacted, don't place any files into them!
2. On the server create a folder named e.g. SharedProjects.
3. From standard MicroStation workspace copy to this folder untitled folder (including subfolders) and untitled.pcf file .
4. Rename both to WP1201-AE-UPTOWN and WP1201-AE-UPTOWN.pcf.
5. Copy cell libraries and other files to proper subfolders in WP1201-AE-UPTOWN folder.
6. Share this folder to network users.
7. On your workstation attach this shared drive as e.g. disc P:
8. Start MicroStation with ustation.exe -WS_USTN_PROJECTSROOT=P:\ -WPWP1201-AE-UPTOWN -WUuntitled
   Note: Recommended way is to copy MicroStation shortcut to your desktop and to change Target in shortcut properties. It would be something like "C:\Program Files (x86)\Bentley\MicroStation\ustation.exe" -WS_USTN_PROJECTSROOT=P:\ -WUuntitled -WPWP1201-AE-UPTOWN ... be careful where quotations are ;-)
9. MicroStation should start with set project to WP1201-AE-UPTOWN and untitled user with all path configured to the shared network disc.
   Note: Because MicroStation remembers the last used folder, sometimes it's necessary to switch project to untitled and back to the one shared on the network, otherwise it still points to former folder.

As you can see, you don't have to do anything with pcf file. It's because the system how variables are evaluated is defined in a hierarchic way, so the only way you have to do is to start MicroStation with own definition where project files (pcf file + project folder) are placed.

If you add another project (pcf file + project folder with standardized subfolders) into this shared folder, it will be automatically available in MicroStation open file dialog immediately (after MicroStation restart).

With regards,

  Jan

One more note (there is always one more note ;-)

Another approach is to share the whole workspace folder (everything under Workspace) on a network, which can be done by changing _USTN_WORKSPACEROOT configuration variable. But in my opinion it's more complex because many more files are shared, so I think you should start with simplier "project only" sharing.

With regards,

 Jan

What is wrong with the definitions I currently have designating "MS_DRY=P:/...../12-01 AE-UPTOWN/" and "MS_COLD=S:/BENTLEY/V8/WORKSPACE/System/"

The intent is to keep all of the used cells, tables, fonts, etc. on the server and refer back to them as new projects come in (City, Client, TxDOT, etc).  This description sounds like the intent is to copy all the cells, etc. to each project as it comes about, which would lead to the duplication of files.

Even with the Project configuration set to look for on location, why is it that when the configuration has different results when placed in one place versus another?