Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Hi JKI, I built a package where I specified a password on a subfolder by unchecking "Use Protection Settings of Parent Folder". This particular folder's destination is still set to "Use Destination of Parent Folder" which is installing to "Toolkit VIs" set to "Directory (Preserving hierarchy)". The problem is that when this package installs, the subfolder that got a password applied does not go into a location that is consistent with "Preserving Hierarchy". Instead it installs into the root "Toolkit VIs" directory. Not specifying a password results in correct directory installation. Any help would be appreciated. -Mike Lyons National Instruments RF Systems Engineer Update: Using VIPM 2013 SP1
  2. Hi all, I'm trying to build a package that contains a series of lvlibs. The lvlibs have associated palette files. I did not use VIPM's ability to create the palette files since there was no way to associate the mnu file with the lvlib in VIPM (at least as far as I could tell). Whenever the package is getting built, the association from the library to the palette file is getting broken so that when the package is installed, the palettes don't display properly. Any assistance on that would be great, but if not, I figured I would just replace the library files in the .vip file after it gets built. I did so with a zip file program, but after doing so VIPM tells me the file is bad. I noticed in the spec file that's inside the vip, there is an ID which looks like a checksum. I couldn't figure out how the checksum was getting calculated though. Does anyone know how I can work around this issue (other than not linking the mnu file to the lvlib and just using VIPM to build the palettes)? Thanks, Mike
  • Create New...

Important Information

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