• Locked Locked
  • Replies 14 replies
  • Subscribers 43 subscribers
  • Views 11616 views
  • Users 0 members are here
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

64-bit install

zride91
Offline

We are going to be starting to use 64-bit Vista machines, but installing MicroStation (and anyother Bentley product) gets installed by default to the Program Files (x86) directory. 

 Can the install directory be changed to install in the Program Files folder?

 I have custom pull down menus in MicroStation that start up InRoads and the such, along with other configuration variables that reference the Program directory, I do not want to have to maintain (2) sets of everything.

There doesn't seem to be anything special with the Program Files folder, is there a reason to have the 32-bit and 64-bit software seperated out?

 

Thanks

  • Offline in reply to Roy Gallier

    Ah!  Thanks again Roy, it was the "/" that I forgot in the variable!  Everything looks to be working GREAT now.  Since I've got it working, it seems the _USTN_BENTLEYROOT variable also works the same way to accommodate the different locations of installs.

    Thanks again all who posted, you've been a big help.

  • Offline in reply to Roy Gallier
    You could also create a variable for the IR install location that works with the keyin. In your build cfg files, try creating a '%if exists' that looks for the 64-bit install location and if not exists then use the 32-but location. Not hard to do, let us know how you go?



  • Offline in reply to zride91

    May have something to do with the "(" &")" which are considered operators. I would try eliminating these from your config variable. Also the "/" after the directory may be a problem:

    PROGAMFILESX86 = ${ProgramFiles(x86)}/

    $ mdl l "$(PROGRAMFILESX86)Bentley V8i\InRoads Group V8.11\bin\CivUstAT.ma" InRoads

    HTH - Roy

  • Offline

    I'm stumped on using the ProgramFiles(x86) variable.

    I am trying to get it to work in a key-in for one of our custom pulldown menus that starts InRoads.

    The Key-in for the pull down we used is as below:

    mdl l "C:\Program Files\Bentley V8i\InRoads Group V8.11\bin\CivUstAT.ma" InRoads

     This worked great when everything was installed in the same location.  Being this pulldown is in a dgnlib on the network, I only want one file to manage for everyone to use.

    This is a great example of where I wanted to use a resolution such as Roy's.

     I basically need one Key-in that points to (2) locations:

    C:\Program Files\Bentley V8i\InRoads Group V8.11\bin\CivUstAT.ma

    and

    C:\Program Files (x86)\Bentley V8i\InRoads Group V8.11\bin\CivUstAT.ma

     I have tried to use EXPAND KEYIN with a Program Files (x86) variable, but I can't get it to work with the rest of the file path.   I've also tried using the _USTN_BENTLEYROOT variable to get me by the 32-bit/64-bit program structure differences, but again the key-in will not take the rest of the path.

    Does anyone have any suggestions?

     Thanks again!

  • Offline

    Thanks again all! 

    Jordan, yes on the Autodesk side of things I am in the same boat.  We have not utilized Autodesk Object enablers in MicroStation yet, but I am having a heck of a time trying to get all of my Autodesk 2008 products going on the new 64-bit machines and getting all the object enablers loaded.  For the 2008 releases, it seems Autodesk intentionally made  some of their packages uninstallable in a 64-bit environment because it wasn't supported.  I've aquired ways to work around installs for all the vertical products, but did get stuck on the MEP object enabler, it's the only one I can not get to work.  I will just have to work with proxy graphics till we can deploy 2010.

Communities
Support and Services
Training and Learning
Social Media