Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Eng-Tips
*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

potrero (Mechanical)
25 May 10 12:32
This is mainly an FYI. In NX6 and prior releases, we used to modify the "ugii_env.dat" file inside [UGII_BASE_DIR]\UGII\ to set things such as the location of the directory for custom company part templates, etc. It looks like there has been a major change to the role/function of the "ugii_env.dat" file in NX7.5, as the file itself is almost entirely empty now, after a clean install. I searched the documentation for references as to the changes in the ugii_env.dat file between NX6 and NX7.5, but am not sure I found anything really explicit.  The clues to the changes are in the ugii_env.dat and ugii_env_ug.dat files themselves.

Here is the content of the new (NX7.5) ugii_env.dat file:


#
#     Copyright 1991 - 2009 Siemens Product Lifecycle Management Software Inc.
#                                   All Rights Reserved.
#
###############################################################################
#
#
# This file should be used to override any standard NX environment variables.
# The values defined here will take precedence over the NX values, as long as
# they are defined before the #include of ugii_env_ug.dat. This file will not
# be overwritten by an MR installation.
#
# Override any variables here.

#
# Do not define any variables after the #include below. They must be defined
# before the #include in order to override the NX defaults.
#
#if FILE ${UGII_BASE_DIR}\ugii\ugii_env_ug.dat
#include ${UGII_BASE_DIR}\ugii\ugii_env_ug.dat
#endif


And here is the preamble of the NX7.5 "ugii_env_ug.dat" file:


#  NOTE:  Customer changes should be made to the ugii_env.dat file directly,
#         which then includes this file. This file will be replaced when a
#         MR is loaded, so customers should not edit this file.  Environment
#         variables in ugii_env.dat supercede any values here, so override the
#         defaults by defining the value in the ugii_env.dat file, which will
#         not be replaced during MR updates.


So, the bottom line is, make your customizations to environment variables in the ugii_env.dat file, just like the old version.  What's changed is that this file won't get overwritten with Maintenance Releases.  I suppose this is a nice change.
Helpful Member!  JohnRBaker (Mechanical)
25 May 10 13:16
This is one reason why I start my various versions of UG/NX from a .bat file since I can set all my environment variables there with no fear that any of them will ever be overwritten by an install or update.  Remember, I not only install all the MR's, but during integration I get all of the development copies and so when you go from one integration phase to the next, there are NO update tools, you have to deinstall the old copy of NX and start over from scratch each time (well, at least I get to thoroughly test the deinstall and install script for each release since I often have to repeast this process 20 times are so with each new version of NX ;-)

Also using .bat files allows me place shortcuts on the desktop which is really handy when you have as many versions of UG/NX installed as I do (11 at the moment, but I only place the last 4 on the actual desktop with the rest inside a folder, which has its own shortcut on the desktop).

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
http://www.siemens.com/plm
http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.
 

HerbC (Automotive)
26 May 10 14:08
John,

That sounds like a great idea.
I would be interested in seeing the .bat file that you are using to start NX. Are you willing to share?

Herb C.
Eifel Mold & Engineering Inc.
Plastics Tooling Designer
UG NX-6.0
 
 

JohnRBaker (Mechanical)
26 May 10 15:25
Attached is a copy of a generic .bat file which can be used to start a session of NX.  It's self-documented, and the way I use it is to place the file somewhere convenient and then place a shortcut on the actual desktop.  It's generally a good idea that you modify the 'Properties' page of the shortcut so that it runs 'Minimized'.  If you wish (as I ahve done) is to also assign a customized icon to the shortcut so that it will be easier to find on your desktop.  If you wish I can also upload the icon file that I've been using since the release of NX 1.0.

Anyway, let me know how it works out.  Have fun winky smile

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
http://www.siemens.com/plm
http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.
 

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!

Back To Forum

Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close