This is an example of one of the 'gotchas' we ran into as we started to port NX to 64-bit Windows. It turns out that some of the 3rd party tools that we use to display and read the documention while running NX on Windows have not been ported to 64-bit yet (and may never get ported). And while it is true that when running 64-bit Windows, you can run both 64-bit and 32-bit applications, they can't be mixed together. That is, 64-bit and 32-bit applications can be run side-by-side, but only as SEPARATE applications.
Now inside of NX all of the items that we launch from the Resource Bar, such as the Navigators and Internet Explorer and so on, if you're running a 64-bit verion of NX, they must all be 64-bit applications since the Resource Bar is executed from INSIDE NX as part of the main application. Now it's possible for a 64-bit version of NX to 'spawn' a 32-bit application, but it will run in it's own window as a sepatate application. So we were forced to move the Documentation functions, which includes both the User Documentation and the Help Documentation, OFF the Resource Bar and onto the Help Pull-Down menu or by launching it as 'On-Conext' Help using F1.
Now you may ask what does this have to do with me if I'm running a 32-bit version of NX 5 on a 32-bit version of Windows? Well we only develop ONE version of NX in terms of source code and then port it to the various operatings systems that we support with only as few platform specific changes and considerations as possible. So in the case of Windows, we developed it so that the same source code can be compilied and integrated on both 32-bit and 64-bit Windows, which means that starting with NX 5, we had to remove the Help tab from the Resource Bar and instead launch all Help and Documentation tasks in their own Window. Also, one of our commitments to our customers has been to always try and keep the different platform versions of NX as close to alike as possible in terms of appearance, location of functions and their behavior, for those situations where we have customers who run different platforms but whose employees may have to move from platform to platform as part of their normal work environments.
Note that this same situation also forced us to move the window there the CAST product runs OFF the Resource Bar and into its own independent Window.
Anyway, I hope this helps explain what happened and why.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA