...which will return something which you can use to identify whether you're running a 32-bit versus a 64-bit version of NX. What is reported is the Windows OS which is running but based on HOW that is worded, you can deduce what it is that you're looking for.\
For example, if this call returns a string with says something like...
Windows NT (x64)
...then you know that this is the 64-bit version of NX. However, if it returns something like...
Windows NT 6.1
...then it's the 32-bit version of NX which is running.
I know it's not completely logical, but then it IS Windows which is being asked for the information, so beggers can't be choosy ;-)
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Thx. But of those two answers, I'm thinking the syslog is the better of them. FYI I'm not tryong to make that determination while NX is running. I'd like to make that determination from the OS level. I need to know which systems have the 32bit NX6 on them vs the 64bit version. Our problem is that some, but not all, of our users are running 64bit Win7 are actually running the 32bit version of NX6.
I'd like to get an accutate accounting of our systems, and identify those specific cases.
I thought a batch call from everyone's login script would be easier than having everyone run an NX utility. A lot of our users run NX very infrequently. It's easy to determine OS in that circumstance, but not so w NX.
I was hoping perhaps there may be a few unique filenames in those versions, but perhaps I'll just have a little vbs or powershell script to get it from the syslog.
