Kathleen,
[quote user="Kathleen Pn"]
Furthermore, this version of MCSDK was installed correctly on one computer and wasn't on another and the only difference I can see is operation system. First is 64-bit windows 7 and second is 32-bit. I don't think it has some influence on installation but I have no idea what's going on.
I am not 100% sure why the different installs are yielding different results, as the datapath size of the OS has very little to do with the Product Discovery tool. However, since CCSv5.3 does not show the NDK error (at least on my installation), I can't help but think the CCS installed in the 32-bit machine was either v5.3 or it was updated from v5.3 to v5.4 - can you confirm that?
All that said, this issue is not critical: as the release notes for the MCSDK patch mention, to work with CCSv5.4 you simply need to use the newer NDK instead.
Check the attached screen to see how to get rid of the invalid product discovery message every time you open CCS.
Hope this helps,
Rafael