Running Inroads SS2 and SS4 on same machine

Go to C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation\config\appl and make sure you DON'T have a file which calls up the InRoads SS2 Command Line Switch.  Way back when SS2 was first released, we could add it to a configuration file or have the switch on the icon, but with subsequent releases of InRoads, we have different switches and can't have it in a CFG.  Look for a file called "Load_InRoads.cfg".  If you have one and open it you will probably see the switch  Load_InRoads_SS2=1 which is trying to get MicroStation to recognize the ss2 product, but InRoads ss4 can't load this way.  You will want to delete that file if you have it.

https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/18835/can-inroads-ss2-and-ss4-be-installed-on-the-same-machine

The next thing is to make sure there is an InRoads.3.1.cfg along with the InRoadsAT.cfg.  They can both exist here, we just need to make sure you have both because these control the startup of InRoads.

Next I would look at the icons used to start up the program.  InRoads SS4 icon requires 2 switches.  -wsLoad_InRoads_SS4=1 -wsINROADS_APP=Suite because it has to load on startup.  InRoads SS4 no longer has the ability to start from within a MicroStation session and must be started when you start the program because of the functionality placed in the MicroStation Tasks for the OpenRoads tools.

checked for folders  

well its not time to finally get this to work,  still no luck 

do i really need to build a ss4 specific workspace to get this to work? 

i tried loading with default workspace and no projects still crashes 

I'd have to agree with Robert Garrett. You can contact your account manager and use portfolio balancing to convert MicroStation with InRoads licenses to Power InRoads licenses. And then its a simple matter to install both.

Otherwise, you are going to have to rework some CFG files that ordinarily, users do not touch.

Since we only have Power InRoads, I cannot tell you exactly what you will need to do.

On our Ss2 install, there is an InRoads Group subfolder under the main Power InRoads Ss2 folder that looks a lot like the main InRoads folder that exists when using MicroStation with InRoads. And the PowerInRoads.cfg file in the appl config folder defines and uses an INROADSAT_COMMON_PATH variable that points to that folder with %include CFG lines. This is probably a near equivalent to your Ss2 setup as I can describe.

In our Ss4 install, There is a Civil Platform folder in addition to the InRoads Group folder. The PowerInRoads.cfg file in the Ss4 appl config folder %includes CFG files from both of these locations. I can only assume the InRoads Ss4 install contains a similar differentiation.

To split up Ss4 and Ss2, you would need to determine which cfg files point at Ss2 files and which point as Ss4 files and isolate them in some manner. Then, either with custom shortcuts or some other methodology, create two independent setups that allow you to launch either InRoads without getting any crossover files.

All I can add is, Good Luck!

I'd have to agree with Robert Garrett. You can contact your account manager and use portfolio balancing to convert MicroStation with InRoads licenses to Power InRoads licenses. And then its a simple matter to install both.

Otherwise, you are going to have to rework some CFG files that ordinarily, users do not touch.

Since we only have Power InRoads, I cannot tell you exactly what you will need to do.

On our Ss2 install, there is an InRoads Group subfolder under the main Power InRoads Ss2 folder that looks a lot like the main InRoads folder that exists when using MicroStation with InRoads. And the PowerInRoads.cfg file in the appl config folder defines and uses an INROADSAT_COMMON_PATH variable that points to that folder with %include CFG lines. This is probably a near equivalent to your Ss2 setup as I can describe.

In our Ss4 install, There is a Civil Platform folder in addition to the InRoads Group folder. The PowerInRoads.cfg file in the Ss4 appl config folder %includes CFG files from both of these locations. I can only assume the InRoads Ss4 install contains a similar differentiation.

To split up Ss4 and Ss2, you would need to determine which cfg files point at Ss2 files and which point as Ss4 files and isolate them in some manner. Then, either with custom shortcuts or some other methodology, create two independent setups that allow you to launch either InRoads without getting any crossover files.

All I can add is, Good Luck!

thanks Chuck 

nice to hear from you