Jump to content

mzu

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. I am looking for something like this only for packages.
  2. I have one 9.0 entry. Surprisingly enough all the links point to "\program files\national instruments\labview 2009" - 64 bit version, but all the packets got installed to 32-bit version which resides at "\program files (x86)\national instruments\labview 2009" Ha, I think I know what the answer is: 64 bit and 32 bit applications use different parts of registry, see say Microsoft KB So, when I launch VIPM it gets launched using the 32bit LabVIEW runtime engine. So it sees under "HKEY_LOCAL_MACHINESOFTWARENational InstrumentsLabVIEW", what a regedit (A 64 bit program) sees at: "HKEY_LOCAL_MACHINE SOFTWARE Wow6432Node National Instruments LabVIEW". There are 2 entries for 8.6 and 9.0. Hope it helped. Be happy to help you guys figure this out for the benefit of the community. -- CLD rm /mnt/windows
  3. 2 questions: 1. Does VIPM 2.0.3 work with LV2009 64 bit? 2. I have several versions of LV side by side, including LV2009 32bit and LV2009 64bit. Looks like only on of them can be registered with VIPM. But would like to have OpenG packets installed in both, what can I do, except manual installation, or copying VIs and creating menus? I understand that some of the OpenG functionality may not work in 64bit LabVIEW -- CLD rm -rf /mnt/windows
  4. Dear JKI, would you mind me translating the package building guide to Russian (and possible German) and posting it to Labview-related forums?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.