there is no reason for a user to maintain variables or batch files to set multiple PTC_WF_ROOT, PTC_WF_CACHE and CREO_AGENT_HOME. I think there is room for improvements here, in terms of functionnality. It looks like the already posted ones, but always good to illustrate more. This is to let you know the kind of claim a user can have with Creo 3. It is nice to see same regrets are shared all over.
floating license difference has been around for at least twelve years, so I highly doubt PTC will consider changing it now.
Once borrowed, the floating license will act like a node-locked license for the duration of the borrowing period.) This node-locked vs. (The only way around this restriction is to borrow a floating license.
If you start a second session, a second floating license will also be retrieved. On the other hand, floating licenses only allow one session of Creo at a time. This means if you have a node-locked license on your computer, you can run as many simultaneous session of Creo you want (or your computer can handle). Third, node-locked licenses are considered "uncounted". If you change workspaces in one of the Creo sessions it will change workspaces in all the others. Second, a change was made to how cache sharing works starting in Creo 3 that requires all Creo sessions connected to the same cache to also be connected to the same workspace. " Cache sharing between multiple Pro/ENGINEER sessions of the same datecode when logged into Windchill with the same account, working with the same cache and even the same Workspace is supported." See CS131176 for more info. Let me see if I can clarify some things.įirst, running multiple sessions of Creo (Pro/e) while connected to Windchill and sharing the same cache is currently supported and has been supported since Windchill 9.1 (M010+) w/ Wildfire 4 (M070+) and Windchill 9.1 (M020+) w/ Wildfire 5 (F000+).
There seems to be a lot of confusion going around.
0 kommentar(er)
