Problem starting IR from desktop

InRoads must be started from the Start menu at least once after installation before the desktop shortcut will work.

HTH, Ron

Hello,

I removed and installed both MS and IR.

 I get the same problem when I open it from the start menu (the same text window pops up). And it still works fine when I open it from Utilities=> MDL application.

Please help...

Karl

If you installed in the order indicated InRoads was installed before MicroStation.  Re-Run the install for InRoads and execute a repair.  This will place the InRoadsAT.cfg file in the microstation config\appl directory.  Short cuts and menus will then be functional. 

Cheers

Lisa Whitson

There's no InRoadsAT.cfg located in the path mentioned.
Although it could be found in the installation path for Inroads, i.e (C:\Program Files\Bentley\InRoads Group V8.11\data)

Hi Lisa,

 Thank you, I am sure this will work. But I am trying to make a standard installation procedure for the entire company. So I don´t want to have to reinstall a program if possible.

 Edit: We're trying to deploy Inroads / Microstation as a silent installation to our clients, using windows installer commands, i.e msiexec.exe.

  Hope you understand our purpose...

/Karl 

Karl,

The order in which you install the programs determines whether this will work correctly or not.  MicroStation needs to already be installed when InRoads is installed so that it can place the InRoadsAT.cfg in the appropriate MicroStation folder.  You need to install in this order:

1. Prerequisites for Desktop Applications
2. MicroStation 08.11.07.171
3. MicroStation Update 08.11.07.180
4. InRoads 08.11.07.229

If you did not install in this order, then you should follow Lisa's workflow on the machines in which the products have already been installed.

Thanks,

Jason Smithey

Once you get a working version, please feel free to post a working example. I have been trying to do the same but some of my efforts have not worked as planned.

But one thing we have done is to copy config files to specific locations as part of this type of process. This may include custom CFG files or modified versions of standard ones delivered by Bentley. This approach could solve some of the issues that you were having.

Once you get a working version, please feel free to post a working example. I have been trying to do the same but some of my efforts have not worked as planned.

But one thing we have done is to copy config files to specific locations as part of this type of process. This may include custom CFG files or modified versions of standard ones delivered by Bentley. This approach could solve some of the issues that you were having.