Cancel
Showing results for 
Search instead for 
Did you mean: 

DialogMemory, history and nx_mru

Valued Contributor
Valued Contributor

Hello,

 

DialogMemory.dlx

history.pax

nx_mru.txt

 

the location of these is controlled by Environmental variables, at least on our machines. We are running native NX. Currently I have NX8.5 and NX11 and those two share the files. How should I setup NX to use each its own dialog memory, history and nx_mru files.

 

...and apparently these files too:

ReuseLibraryConfiguration.krx

user.mtx

FastenerAssemblyConfiguration.krx

 

Thank You

 

 

8 REPLIES

Re: DialogMemory, history and nx_mru

Siemens Phenom Siemens Phenom
Siemens Phenom

A good example of how to run multiple versions each with its own set of environment variables can be found in the discussion of NXCustom.

 

Here are the links to what you can do to get a batch file to run each version independently.

 

 

NX Custom for NX 7.5 to NX 9.0

 

NX Custom for NX 11

 

Scott

Re: DialogMemory, history and nx_mru

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Note for NXCustom, there is a thread "locked" to the top with links to the threads for each version:

 

https://community.plm.automation.siemens.com/t5/NX-Programming-Customization/NXcustom-Utilities/m-p/...

 

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled


Re: DialogMemory, history and nx_mru

Siemens Honored Contributor Siemens Honored Contributor
Siemens Honored Contributor
The environment variable UGII_USER_PROFILE_DIR controls the location of the files you mention.

Regards, Ben

Re: DialogMemory, history and nx_mru

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

I do have the following lines in our ugii_env.dat file:

############################################################################
#
#  The following sets the folder for the user customizations
#
#if FILE ${APPDATA}\Haidlmair\NX\${UGII_VERSION}
UGII_USER_PROFILE_DIR=${APPDATA}\Haidlmair\NX\${UGII_VERSION}
UGII_HISTORY_PALETTE_DIR=${UGII_USER_PROFILE_DIR}
UGII_PALETTE_WORK_DIR=${UGII_USER_PROFILE_DIR}
#endif
#
#if FILE ${UGII_USER_PROFILE_DIR}\ugii_env_user.dat
#include ${UGII_USER_PROFILE_DIR}\ugii_env_user.dat
#endif
#
#if FILE ${UGII_USER_PROFILE_DIR}\UG_user
UGII_USER_DIR=${UGII_USER_PROFILE_DIR}\UG_user
#endif
Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: DialogMemory, history and nx_mru

Valued Contributor
Valued Contributor

That, I know. But how do I split it between different versions? How do I split history palette, etc.

I do not want to mess NX8.5 settings, while playing with NX11 preferably clean setup.

2016-11-07_09h44_48.png

 

 I am now looking at NXcustoms. But I think there must be a simple line or dialog to setup these folders/files (just like with .dpv files).

Re: DialogMemory, history and nx_mru

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Do not use the Windows environment variables for that.

It is best to use a shared ugii_env.dat file on a server, since there you have the ability to check or use the UGII_VERSION variable, which contains the version of the started NX session.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: DialogMemory, history and nx_mru

Phenom
Phenom

We have an environment variable to hold the NX version and include that in any paths. So for your case you could use:

NX_VERSION=NX85
UGII_USER_PROFILE_DIR=C:\%NX_VERSION%

Of course whenever you want to use different NX versions you need to change the value of NX_VERSION. We handle that by using a BAT file to start NX.

Graham Inchley Snr R&D Engineer (Systems Development), Sandvik Coromant
Lenovo ThinkPad W540, Win7, 16GB. Developing in: Java | C | KF
Production: [NX8.5.3.3 MP11 64bit] Testing: [NX12.0.2 MP1]

Re: DialogMemory, history and nx_mru

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

I would go the dynamic approach instead of static environment variables.

I have the following set as an operating system environment variable:

UGII_ENV_FILE=K:\NX_Custom\ugii_env.dat

This points to the main NX environment file that handles anything that is not version specific.

 

############################################################################
#
#  HAIDLMAIR customized settings
#
#  The following variables are exceptions, they must still be set correctly
#  in the operating system environment.
#     HAI_NX_GROUP   UGII_ENV_FILE   HAI_NX_CUSTOM_DIR
#
#  HAI_NX_CUSTOM_DIR is the folder containing this file and the root
#  of the customization folders
#
HAI_NX_CUSTOM_DIR=K:\NX_Custom
#
#  HAI_NX_CONFIG_DIR is the folder containing the version specific environment
#  file and customizition
#
#if FILE ${HAI_NX_CUSTOM_DIR}\${UGII_VERSION}
HAI_NX_CONFIG_DIR=${HAI_NX_CUSTOM_DIR}\${UGII_VERSION}
#endif

#
#  HAI_NX_GROUP is used to determine the group relation of the current computer
#  This value is just a default if it is not set
#
#  !!! This must be set in the operating system environment !!!
#
HAI_NX_GROUP=CAD

#
#  HAI_SKIP_NX_CUSTOM determines if the HAIDLMAIR customizations should be skipped
#  or not
#
#if FILE ${HAI_NX_CONFIG_DIR}
HAI_SKIP_NX_CUSTOM=false
#else
HAI_SKIP_NX_CUSTOM=true
#endif

#
#  Solution Center - Document ID: 001-6606875
#
#  To control the command window opened when starting Tcserver.
#  MIN ........ open console window minimized
#  NOWINDOW ... hide console window
#
UGII_APISERVER_WINDOW_STARTUP=MIN

############################################################################
# 
#  Include HAIDLMAIR customizations or not
#
#if ${HAI_SKIP_NX_CUSTOM} = true
#include ${UGII_BASE_DIR}\UGII\ugii_env.dat
#else
#include ${HAI_NX_CONFIG_DIR}\UGII\ugii_env.dat
#endif

So K:\NX_Custom\v10\UGII\ugii_env.dat contains the NX 10 settings and there is a K:\NX_Custom\v8.5 folder for NX 8.5, so nothing to switch before starting NX, it is all done when the correct release is known.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide