Hello -
I like to load InRoads using a custom tool (keyin mdl load civustat.ma). However, since updating to newer versions of both IR and MS, this tool no longer "works" and results in the following Message Center errors:
"MDL Loader: Unable to load library (DLL or MDL shared library) CivUstAT"
"OS could not load C:\Program Files (x86)\Bentley\InRoads Group V8.11\bin\CivUstAT.dll, error 126."
The same occurs when trying to "load" from the Utilities->MDL dialog box (the CivUstAT.ma path is listed in both the MS_MDL and MS_MDLAPPS variables). However, if I select "Browse" and load CivUstAT.ma, it loads with no errors. I can then close IR and the custom tool and "load" button will work for the duration of the MS session.
Operation also appears perfectly normal when starting IR from the Start Menu shortcut(s).
Is there something I'm not doing properly to get the custom tool to work?
FYI, I'm running InRoads SS2 (08.11.07.536) in MS SS3 (08.11.09.292).
As I remember start it once from the windows start , then read the readme coming with your actual version, there are some changes to start IR since 8.8!
Regards
Frank
since 1985: GIS, CAD, Engineering (Civil) Senior Consultant : [Autodesk Civil 3D , Esri ArcGIS, VertiGIS: in previous days : Bentley MS V4 - V8i, GeoGraphics, Bentley Map V8i, InRoads, HHK Geograf, IBr DAVID] : Dev: [C, C++, .NET, Java, SQL, FORTRAN, UML][direct quote by: http://en.wikipedia.org/wiki/Helmut_Schmidt]: "Wer Kritik übel nimmt, hat etwas zu verbergen"Wer Grammatik- und/oder Rechtschreibfehler findet, der darf sie behalten :-)
I am not sure if inRoads fully integrates itself into Select series 3 automatically.
You may need to setup the application CFG file and also set the command line switch -wsLoad_InRoads_SS2=1 on any and all MicroStation shortcuts. When done properly, there will be an application menu which can be used to load any InRoads product in MicroStation.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
In the same boat here as SabreTooth78. Previous versions of ustn SS3 and maybe SS2 had the "Applications" menu item where InRoads (etc.) could be opened. Ustn .357 doesn't provide that, even with the plain-vanilla workspace. Even starting from the Start Button via InRoads Group doesn't work: same "can't load CivUstAT.dll" error. In either scenario, I'm stuck with clumsily browsing from the MDL dialog box to start InRoads (which works fine, it's just like rubbing two sticks together to start a fire...)
When using the Start Button (say for (InRoads Bridge, InRoads Site, etc.), there must be some fancy stuff going on in the background, as the same mdl (CivUstAT.ma) starts different products depending upon the product that was selected, yet there are only four MDLs visible in the folder structure. I miss the old days where MicroStation automatically included any .CFG in the \appl\ folder, so it was very easy to see what was going on, and what got loaded and when in msdebug.txt (and tweak if necessary).
I'm not just interested in getting InRoads to start via PHD, I have to get InRoads running in various project workspaces, using different .XINs and what-not for different projects/clients--big-picture stuff. It'd be nice to know what's going on behind the scenes so I can hijack it :-)
You can also load it with a Function Key.
Go to Workspace > Function Keys, and choose your "trigger". I have mine set at ALT+F1. In the Action field, type in:
mdl l "C:\Path to civustat.ma"
On my home machine, it's:
mdl l "C:\Program Files\Bentley\InRoads Group V8.11\bin\civustat.ma"
Yeah, sadly that produces the same .DLL error (I'm using a macro, you're using a function key, same difference).
Even using that key-in in the Key-in window produces the same .DLL error on my PC. However, if I start InRoads from the MDL dialog then exit InRoads, the key-in will work--because the .DLL is already loaded. I assume you're starting a plain-vanilla workspace, or a project workspace that has no "links" to InRoads--as opposed to starting InRoads from the Start Button. If so, I am very curious why it works for you and not me (and others). Windows version? Installation tricks? ("Oh, you have to install ustn .357 AFTER InRoads SS2!" or "Hey, you didn't run makeinroadsrunwithkeyin.exe!") :-)
I will admit we're running Windows 7/64, and because of the Draconian rights with the installations, users have had a helluva time getting write access to some folders on the C drive, which has caused some quirkyness across the board with applications. This is exacerbated with Windows Update, which seems to rollback read/write on some folders. Some offices simply charge users with Admin rights, and hope for the best.