MicroStation configuration

Thanks for your response Jan. My question was initially to the document author and really revolved around the statement "BLOCKED SCRIPTvoid(null);" as mentioned in the referenced document. I see it is separated by the semi-colon, which indicates/represents a separate key-in. Thanks again.

Hi Gary,

Unknown said:

"BLOCKED SCRIPTvoid(null);" "-wsMY_FILE=%1" "%1"

I see three different parts in your question.

It's not quite clear what BLOCKED SCRIPT does. Or was something originally different blocked when posted to this web?

What is clear is -ws argument. It's used to define MicroStation configuration variable when MicroStation started, so it should not be define at Windows level or in some MicroStation configuration file. -wsMY_FILE=%1 create a configuration variable named MY_FILE and sets it to the value of the first parameter used when batch is started. Because %1 parameter is used, I suppose your example is from some bat file?

Last "%1" takes the first argument used when batch file was started and pass it to MicroStation as a design file to be opened.

Unknown said:

Does this stop normal configuration script processing

I guess not, but it can depend on you workspace configuration and Windows environment.

With regards,

  Jan

I read what the tech page  link says but I still dont  understand it.. could somebody explain what that  original posted script actually does or doesnt  allow..

Also it  looks like its what you put into the shortcut of the mstn icon ...or have I completely missed what the tech page meant...

This is in reference to communities.bentley.com/.../configuration-variable-processing
But Tori Queen asked me to post it here instead.