INI to XIN not all preferences translated

We are having problem with translating our MS V8 InRoads ini files to V8i xin files. The translation works but most of our preferences that we created have not been converted. Is there a step we are missing or do we need to do something with our ini files before it wil work.

Thanks

Simon

  • INI files convert to XIN format but there are several new and revised software options introduced between the versions of InRoads that used INI to the V8i version.  The initial conversion from INI was setup to convert to the XIN file used in InRoads XM and it did a fairly good job with only a few areas requiring adjusting due to new and revised functionality.

    The upgrade from InRoads XM to InRoads V8i once again did required adjustments to the XIN preference files to incorporate new and revised functionality.  So converting directly from INI prefs to XIN (V8i) Preferences will required someone to fix and adjust the preferences to work with the latest software functionality. 

    The conversion form INI to XIN converted the format of the file from CSV to the XML data but the user still needs to update and make changes for the additional and revised software functions.

    HTH

    Mike Longstreet
    Vermont Agency of Transportation
    Civil Engineering Technical Support
    VTCAD Help

  • Can you convert down from an xin file in v8I down to an ini file in v8?
  • It is generally a bad idea to revive very old posts, even to ask a related question. However, I will not respond with only an admonishment.

    There is generally no XIN to INI conversion possible.

    However, in theory, since the XIN file is an XML file, it is feasible that an XML Report could be written to convert an XIN to INI, but it would be a monumental task. Creating portions of the civil and wysiwyg ini files would be somewhat less monumental, based upon the number of areas desired.

    But, there are numerous area of the INI files which were not well documented. This include strings of comma separated numbers, some of which appeared to include bitmask values. Without a "dictionary" or schema-like guide document, recreating such values would be a tedious trial and error process.

    In the XIN and Survey folders of the XML reports folder are some example XML Reports that report information on XIN files - some create html files while others create ASCII text files.

    One area of promise would be survey FWF files - if a survey feature is edited with Report Lock on, the results screen prints a screen of text that looks virtually identical to a feature table entry from an FWF file.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996