Microstation V8i configuration files

I am having problems laying out the project configuration file.  When I use the same configuration file on two separate computers, I get different results.  How do I make sure the configuration is pointing ONLY to the locations which I want it to for line styles, cells, and fonts?

Parents
  • 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.

  • 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?

  • Unknown said:
    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/"

    May be nothing, usually the way is to use existing configuration as much as possible and to create the new ones when it unambiguously simplify the solution. I just offered you the idea of the solution that works for sure and doesn't require to use nothing else than standard variables. If you decided to use own solution, but don't define exactly what is the overall concept of your solution (what is where, what file is shared on what level), you cannot expect somebody will invest substantial time and effort to examine the whole your system and workspace and investigate the problems.

    Unknown said:
    The intent is to keep all of the used cells, tables, fonts, etc. on the server

    Done.

    Unknown said:
    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.

    From your description I understood the files are project files, so they will be used in one project, not shared between more projects. If they are the same for all projects, they would belong to Standard (and never ever into System).

    Unknown said:
    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?

    No way how to answer your question other than you use differently set configuration files (at least one of them), there probably cannot be any different reason. But you don't provide any valuable information  (msdebug log from these two computers but with the same user + project + interface), that can help to asnwer the question.The only solution is to create msdebug files with completely the same workspace, compare it side by side (any advanced text editor can do it) and check, where they are different.

    Regards,

      Jan



  • I am sorry, I did not mean to offend.  I just didn't understand the process.  Lets walk through your solution:

    1. Leave System (and any other) MicroStation folder intacted, don't place any files into them! - I am not sure what you mean.  Are you saying that I should leave my projects as they are for right now?
    2. On the server create a folder named e.g. SharedProjects.
    3. To this folder copu untitled folder (including subfolders) and untitled.pcf files from standard MicroStation workspace. - Copy what untitled folder and untitled pcf?  Where do I get them?  (Not sure the location is for standard workspace)
    4. Rename both to WP1201-AE-UPTOWN.
    5. Copy cell libraries and other files to proper subfolders in WP1201-AE-UPTOWN folder.
    6. Share this folder to network users. - For now I just want this to work for me and then we can branch out.  The issue I was having previously was that the same pcf in two locations (C: drive and S: drive) was giving two different results.
    7. On your workstation attach this shared drive as e.g. disc P: - Are you saying to remap the P: drive to this new folder?
    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 propertis. It would be something like "C:\Program Files (x86)\Bentley\MicroStation\ustation.exe" -WS_USTN_PROJECTSROOT=S:\ -WUuntitled -WPWP1201-AE-UPTOWN ... be careful where quotations are ;-) - This will be done by right clicking on the properties button and replacing the Target location, just like the "-debug" correct?
    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.

    I am just looking for consistency.

  • Download Bentley Configuration Explorer from our Free Downloads iWare Apps section.
    http://www.bentley.com/en-US/free+software/

    Bentley Configuration Explorer Features
    • Error/syntax checking
    • Detailed variable reporting
    • File history change management
    • Configuration comparisons

Reply Children
  • Andrew,

    I think Lory is correct, take the 'yellow page' approach, ask someone to help you directly. It's difficult to understand your intention for someone outside. There are a number of things to be thought about when changing from a local to a network configuration. I.e. a user configuration file can destroy nearly all the effort you have made with site + project configuration.

    If you will find someone, who is of help with spoken words and a look at  the current config (on place or remote+telefon), than this one may help you understand whats going on and/or do the config for you.

    I don't know how much time you still spent, but time is money, and it might be cheaper to pay someone else to instruct you basically and do the main work, instead of trying to make you understand the whole config stuff.

    I even had difficulties to underrstand those config files when having a first look at them, although I'm a programmer and a geek. But I had help inside our company and today I feel fine and understand the pro's of the concept behind.

    Jan is trying to be of help, but I don't think that we can provide all the information of a whole training day (+ experience) in a single forum thread. Even though we try to support you as far as we can.

    btw. did you have a look at the administrators guide at docs.Bentley.com ? Although for Xm it is still valid.