• State Not Answered
  • Replies 8 replies
  • Subscribers 61 subscribers
  • Views 1784 views
  • Users 0 members are here

Changes in ..\apps\PW.cfg between Ss2 and Ss4 causing workspace issues.

caddcop
Offline

We bagan taking advantage of the mcm.user.cfg file to implement some settings that we used to have to place within the product CFG folders. This made it possible for non-administrators to modify and implement workspaces.

Recently we began preparing for the retirement of Power InRoads V8i Ss2 and it replacement with Power InRoads V8i Ss10. What we found was that essentially identical workspaces in the two platforms were functioning differently and traced the issue to a difference in the PW.CFG file in the APPL folder of the two products. The Ss10 version had an extra %elseif block that resulted in the mcm.user.cfg file being processed while the Ss2 version, without that block never read that file and therefore missed out on its important variable assignments.

Does anyone know why these would be different and if a fresh installation of PW would correctthis?

  • 0 Online in reply to caddcop

    is there a particular reason you want these settings on the local machine at all? We put all our projectwise settings in our site config on our server and just load it as part of the standard workspace. If a particular project or user needs a different setting we would put it in the project config or the user config.

     

  • 0 Offline in reply to caddcop

    Chuck,

    Good to know that Ss10 works with registryread. I guess that's one change that makes the earlier versions incompatible with newer connect editions of PW explorer. As a test you could try install the V8i version of the explorer to see what the pw.cfg files settings look like. I'd be surprised if it contained the registryread command, but it may give you an insight into a potential solution.

    Regarding having the workspace configurable without admin privileges, we use the managed workspace only to determine the locations of config files that are located in PW folders and then "%include" those cfg files as part of the workspace. These can be set as editable by non-admin staff.

  • 0 Offline in reply to Kevin van Haaren

    We are trying to simplify workspace setup for our consultants - many use our workspace for other clients which we like to encourage as it makes them more efficient when working for us. And not all of our offices require the use of ProjectWise.  Many of our consultants struggle with multiple workspaces so we are working to make it easier for them. 

    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

Communities
Support and Services
Training and Learning
Social Media