Search results for query: *

Here is a method that will prevent the need to re-do your change when patches are applied and will make it much easier to migrate the change to different NX versions as well: 1. Create a folder where you want to store your menu customization. 2. Create a folder called startup in this location...

The folder where the startup and application folders are is sufficient.

To be able to load your .dlls without a path name, you need to tell NX where to look for them in your custom_dirs.dat file. You can find its location by looking for the environment variable UGII_CUSTOM_DIRECTORY_FILE in you log file. Add the folder path to your .dll files and it should fix...

Ronald, 1. When menu files call a dll, they pass the button name as the first argument, while the ribbon/toolbar files only pass the arguments in parenthesis. The equivalent in the ribbon file would be ForEngineDocs_Plotcgm.dll("Illustrator_CGM","Ai"). 2. In a startup directory under a...

Check which program you have associated with .prt files. If it is associated with ugraf.exe, it will start a new session each time. If it is associated with ugs_router.exe it will open in an open session first, and will only open a new session if one is not already open.

With windows 7, to edit the context (right-click) menu you need to modify the registry. Since you already have what you like installed on an XP box, go into regedit, Navigate down to HKEY_CLASSES_ROOT->UGpartfile->shell and export the registry keys for any actions you want to duplicate. Then...

The problem with the installation of Excel 2003 on Windows 7. It fails to write certain registry values needed by NX to access it. Our "fix" was to copy the Excel registry values from an installation of Excel 2003 from a WinXP 64-bit system and import them on the Win7 boxes. The other...

Well, I started with a GTAC solution center search which stated that the problem was related to how WoW (Windows on Windows) dealt with the registry of 32-bit applications (ref:PR-01798177). Since we only saw the problem on mahcines with a clean Win7x64 install with Excel 2003, but not on...

We had this problem with NX5 on Win7x64 with Excel 2003 also. Seems the issue is with how Excel 2003 writes itself into the registry in Win7. The solution for us was to copy the registry branch for Excel off of one of our XPx64 machines and merge it into the Win7 registry. I've attached our...