|
Version |
v08.04.02.00 |
|
Category |
Released Products |
|
Operating Systems |
Microsoft Windows® (see Requirements for specific details) |
|
Language |
English |
|
Date |
July 2003 |
Before you begin, please note the following:
- Review the End User License Agreement carefully during the installation of InRoadsEC. By installing this release, you agree to the terms and conditions of the agreement.
- Internet Explorer 6.0 is required to view XML Reports.
Getting Started
This section contains information about the following:
· Directory Structure
· Installation Troubleshooting
· Registration and Licensing
· InRoads Newsgroup
· Known Issues
· Security Information
· Documentation
· Support and Services Information
· Configuration Variables
Directory Structure
InRoadsEC product's directory structure is designed to make administration of Bentley products very easy and efficient while minimizing the impact on existing workflows. It facilitates a continuous improvement model for engineering products and minimizes the possibility of overwriting user created data.
Installation is defaulted to C:\Program Files\Bentley\Civil and has the following directories:
\bin – contains programs and libraries necessary for operation.
\bin\resdlls\0009 – contains BentleyCivil.hlp file and English language specific files for InRoads. Note: \bin\resdlls\0007 contains help and German language specific files for InRoads and \bin\resdlls\000a contains help Spanish language specific files for InRoads.
\data – contains initialization files, superelevation tables, Storm & Sanitary data files and other miscellaneous files necessary for basic operation. This directory also has backup directories for metric and imperial installations, blocks and MicroStation cell libraries.
\data\AASHTO2001 – contains AASHTO's 2001 superelevation tables for imperial and metric.
\Demonstration – contains files that can be used for showing InRoads functionality for various types of design.
\XML Data – contains files for XML reporting capability.
Installation Troubleshooting
InRoadsEC products run under 32-bit Windows operating systems on Intel-compatible computers. The x86 version is not supported on DEC Alpha NT, IBM PowerPC NT, or similar RISC-based workstations running Windows NT.
This product will not install on Windows 95.
Registration and Licensing
For more information on registration and licensing, visit the Bentley Web site at http://www.bentley.com/registration/ or contact the Bentley Registration Center that services your particular area.
InRoads Newsgroup
SELECT members are invited to join the InRoads newsgroup. Access to this newsgroup provides an efficient and timely mechanism for two-way communication between users and the InRoads project team at Bentley. The newsgroup is a convenient forum for questions, comments and observations specifically regarding the InRoads products. It is also a good resource to find the latest known problems in the InRoads products. Click here for more information.
Known Issues
All InRoads Civil Suite V8.3 products must be removed before installation.
There are several items to consider when planning to work in V7 Mode. Create a separate user configuration in MicroStation Manager called V7. Enter MicroStation and set the Workspace > Configuration variables for
MS_OPENV7=3
MS_WORKMODE=V7
Open MS_V7_LEVEL_NAME_PREFIX. Edit it and give it any value like a 1. Select OK. Edit the variable again and remove the value so there is nothing there and select OK again. Pick OK to exit Configuration and save the settings when asked. Exit MicroStation and enter the V7 file and you will have numbers without prefixes and graphics will be placed on the numbered levels correctly.
V7 workmode will not work correctly with Plan & Profile Generator. Plans are being saved as V8 instead of V7. Create files in normal V8 MicroStation and save as V7.
Plan and Profile Generator - When using V7 files that have a shifted global origin, you will need to use a V8 seed file that has the same shift present or the referenced files will not be placed correctly on plans. You can copy one of the translated V7 files, delete all graphics and rename it as a seed file to use with Plan and Profile Generator.
There is a fix in Service Pack 1 for the InRoads group of products that resolved an issue of creating profiles and cross-sections in MicroStation, saving as a .dwg format then InRoads was unable to read the profile or section sets when it was reopened.
You should create/set in the MicroStation > WORKSPACE > CONFIGURATION a variable that is as follows: MS_DWGSAVEAPPLICATIONDATA and set the value for to 1.
Without this variable the product will not write the required data to the profile or the sections graphics for InRoads to recognize when the dwg is reopened.
Security Information
Windows NT NTFS
The NT File System (NTFS) provides you with the ability to set user-file access privileges such that certain users or user groups have controlled access to application and data files.
The InRoads suite will run under any user account that provides for Read & Add (RWX) privilege to the graphics files and Read (RX) privilege to InRoads suite application files.
If the user has only Read privilege to preference, style, and resource files, then an informational dialog box is displayed and the edit/save functions to these files are disabled. You may still continue using the InRoads suite to place new elements in the graphics file, but you will not be able to create or edit preferences or styles during the session.
Documentation
Help is the only documentation delivered for InRoads EC.
Support and Services Information
Please reference http://selectservices.bentley.com/ for more information regarding professional support and services from Bentley.
The e-mail addresses for Bentley Technical Support are as follows:
The telephone numbers for Bentley Technical Support are as follows:
|
U.S.and Canada |
1-800-Bentley (1-800-236-8539) |
|
Europe/Middle East/Africa |
(+31) 023 5560555 |
The $(BSI_CIVIL_APP) configuration variable allows other products to coexist within the MS_DGNAPPS variable. If the InRoads product does not initiate when the icon is invoked, verify this has been defined in your configuration. If not, please add it.
A Windows Environment Variable can be combined with Project Defaults to set paths without creation of multiple projects. Define a variable in the Windows environment such as, InRproject=c:\prj\1234\. Then in the InRoads Project Defaults you can create a project with this variable calling out the location of the preference file with the following. $(InRproject)\civil.ini and the Project Default Directory with $(InRproject).
The SELECTservices icon (by default in the Standard tool box) and the SELECTservices menu item (by default in the Help menu) both start a local HTML document that is delivered with the product. If you have direct access to the Internet, you can easily change this to be more direct by creating or updating the configuration variable MS_SELECTSERVICESHOME (either at a site, project, or user level) and point it to the URL http://selectservices.bentley.com/
Helpful Hints
This section contains information about the following:
· Translation Service
· Screen Resolution
· Project Defaults
Translation Service
Bentley provides a translation service for project files (.tdp, .tml) from previous versions (4.0 or earlier) of InRoads for MicroStation. For details, call the Support phone number.
Screen Resolution
The dialog boxes in the InRoads suite were designed for display resolution set at 800x600 pixels. With hardware that provides screen pixel resolution below 800x600, some dialog boxes may extend beyond the screen boundaries. All dialog boxes may be moved to give you access to fields or buttons.
Project Defaults
The Project Defaults command, located under File on the InRoads pulldown menu, defines default paths for loading and saving various types of files. The Project Defaults command also specifies which preferences files to open upon startup, and it saves multiple configurations. The configurations saved by the Project Defaults command are stored in the system registry under HKEY_CURRENT_USER. For more information, see the online help for your InRoads product.
Last updated July 28, 2003