Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Not really sure what has changed but apperantly something on my computer was changed (various NI software installation) and now VIPM starts up and shows the splash screen and then suddenly disappears. I updated to the latest version of VIPM from the download page and the same thing happens. The attached crash report shows lots of broken VIs in the list, but without any way to look into the executable I'm not sure what I could do with that. VI Package Manager_32_14.0.1f3_rkalbermatter_cur.txt
  2. I wondered why I hadn't received any Firewall prompt so I checked in the Windows Firewall and indeed, VIPM Package Manager was not in there. So I added a rule to allow VI Package Manager local access and now communication with LabVIEW is reasonably snappy. The strange thing is that here it seemed to work anyhow although EXTREMELY sloooooooooooooooow. And clicking on a package in Explorer now also opens that package in the VIPM. So check the Firewall rules, if you can't seem to connect to LabVIEW.
  3. I have installed VIPM 2012.0.0 under Windows 7-64 Bit and LabVIEW 2010SP1 64 Bit. The first problem is that the file extension launcher doesn't seem to work. When clicking on a file with the ending .ogp nothing happens, where as under Windows 7 32-Bit the file is opened right away in VIPM. I checked in the registry and the OpenGPackage/shell/open/command is defined to "C:\Program Files (x86)\JKI\VI Package Manager\support\VIPM File Handler.exe" -- "/command:open_package" "/source:%1" which I couldn't see a problem in itself with. This is a test installation inside VirtualBox and I'm running with administrative privileges so I don't think permissions should be an issue. Another problem I'm seeing is that VIPM seems to be very slow when installing a package. Everything works reasonably smooth in the VM including VIPM as long as I'm not trying to install a package. The duration to open a a package is VERY slow and after unpacking it, when VIPM tries to connect to LabVIEW according to the progress dialog, it takes many seconds before the Masscompiling starts. Masscompiling is also very slow, compared to a 32 Bit installation, both inside a VM and on a host system. In fact anything that attempts to connect to LabVIEW to do something is VERY slow, such as the Show in Palette, or Show Examples.
  4. Actually the OpenG Package Builder does have the possibility to individually apply install conditions to file groups. The only problem there is that it does not yet include 64 Bit selection. Does VIPM support 64 Bit keyword selection in the spec file and how? Ok I checked into that a bit more but haven't made any tests with VIPM so far to see how it behaves. LabVIEW 64 bit returns in the OS.Name property nicely "Windows x64" so it would be easy to distinguish between Windows 32bit and Windows 64 Bit, since the 32 bit version returns "Windows NT" for that property. I'm going to make this small modification to the OpenG Builder to create a test package. The question is only how VIPM has modified the OGPM library! I have a deep suspicion that VIPM is probably manipulating the returned property in order to not fail installation of components that are marked to be installable for Windows NT, when installing them on Windows 64 Bit. This sort of would defeat the purpose of the platform property for file groups, since technically Windows 64 Bit is a completely different platform than Windows 32 Bit. So could one of the VIPM developers comment if the use of the Exclusive_OS="Windows x64" in a file group should work for marking that file group to only be installed on 64 Bit Windows? An additional question: Since VIPM itself is always a 32 Bit executable, this won't work anyhow unless VIPM is executing this OS.Name property in the context of the target LabVIEW system, which is technically possible since that property (and the OS.Version) are remotely accessible according to the LabVIEW help. BTW: The OpenG main page has been spammed again.

Important Information

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