Jump to content

Jim Kring

JKI Team
  • Content Count

    1,717
  • Joined

  • Last visited

  • Days Won

    42

Everything posted by Jim Kring

  1. Thanks for reporting this. We have identified the issue and will resolve it, ASAP. Thank you, -Jim
  2. The Linux version of RC2 was just released. Mac version to follow.
  3. This issue has been fixed in Release Candidate 2. Please see the announcement, here.
  4. Sorry about the trouble. We are working hard to get a fix out, ASAP, so stay tuned. Thank you for your patience.
  5. Jeff, We'll look into your issue and try to reproduce it. Regarding non-networked computers, take a look at this post: Transfering Packages to Non internet computers., How do I transfer packages to a computer not connected to the Internet Thank you, -Jim
  6. Wonderful. I am glad that it is working for you, now. Thank you, -Jim
  7. Waldi, A couple other things.... Make sure that in "VI Server: Configuration" you allow access to "VI calls", "VI properties and methods", "Application methods and properties", and "Control methods and properties" (see below). And, in "VI Server: Exported VIs" ensure that you entered a value of "*" (see below). Thank you, -Jim
  8. Waldi, This is a VI Server access issue. Make sure that you are allowed to invoke VIs using VI Server. Could you post a screenshot of your LV VI server settings (more specifically the following section: VI Server: Machine Access and VI Server: Configuration). Also, note that sometimes the wrong IP is set in the VI Server : Machine Access and inputting 127.0.0.1 in the machine name/address (and allowing access to this IP) occasionally fix the connection issue. Note: you may have to restart LV for these changes to take effect. Thank you, -Jim
  9. Ton, Release Candidate 1 (RC 1) is now available for download. Please see the announcement, here. Thank you, -Jim
  10. Ed, The internal tracking number for this is Case 2915. Thanks again, -Jim
  11. Ed, Thanks for the feedback. We are aware of this issue. I'll post an issue tracking number, shortly. Thank you, -Jim
  12. Ton, Stay tuned. Today, we will be releasing RC1 (Release Candidate 1). Regards, -Jim
  13. I'm glad it's working for you. It seems that there was some kind of glitch during the installation of that package.
  14. This is caused by installing the "ogpatch_template_bugfix" package. This package does the following: Renames NewDlg InitTree.vi as NewDlg InitTree__buggy.vi Installs a new version of NewDlg InitTree.vi which calls NewDlg InitTree__buggy.vi as a subVI. If you are not able to fix this problem by uninstalling the "ogpatch_template_bugfix" package, you can restore the original file, which is included in the attached zip file: NewDlg_InitTree_LV80.zip \resource\plugins\templatebrowser.llb\NewDlg InitTree.vi
  15. Ed, The package files that are stored in the cache folder are similar to a user's library of packages. This is analagous to how one's MP3 (and other) files are stored in an iTunes music library folder. In order to uninstall a package, we must have a copy of the original package file (so that we can access the install/uninstall script VI), regardless of whether the user has removed the package file from the cache -- this is why we store the original package file in the db folder. Is this redundancy a real issue for you or are you just curious? Regards, -Jim
  16. Joe, Version 2.3 of the oglib_lvzip (zip tools) package was just released. See here, for more info. Regards, -Jim
  17. Chris, The problem was caused by one of the files inside the package having a read-only attribute, which was preventing it from being installed correctly -- this is a bug, and an internal report has been created (Case 2548). As a work-around, you should remove all read-only attributes from files, before they are packaged. Thank you, -Jim
  18. Chris, Yes, please open a support ticket, here, and then we can look into the specifics of your problem. Thank you, -Jim
  19. Mark, As Chris mentioned, you can simply copy the cache folder contents (from a Commander or VIPM installation) to another VIPM installation's cache folder. Another option is to use the Package >> Add Package(s) to Package List, menu option to add a folder of packages into VIPM's package list. Please note, that we are actively working on features to make it easier to import package configurations onto non-networked VIPM installations. Thank you, -Jim
  20. Mark, I'm glad that your using VIPM and that you've been able to quickly resolve your issue Here's a tip, you might find useful... We recommend putting each version of LabVIEW on a unique TCP-IP port. This will allow VIPM to communicate with different versions of LabVIEW, even when multiple versions of LabVIEW are running at the same time. When all versions of LabVIEW are configured for the same TCP-IP port, the first version of LabVIEW will grab the port and other versions of LabVIEW that are subsequently launched will not be able to start the TCP-IP listener. The easiest way to adjust your TCP-IP settings is to let VIPM automatically adjust LabVIEW's VI Server settings while testing the connection (see screenshot, below). Thanks,
  21. Luca, Thanks for testing and for confirming the fix. -Jim
  22. Great. Thanks for testing and getting back to us with a confirmation. -Jim
  23. Chris, Thank you for reporting this problem. Hopefully we can get to the bottom of it. Error 8 is a file permission error. Also, I need some more insight into what you mean when you say "installing a package that I recently added file to"? Did you add new VIs/files to the package (.ogp) file or that you added VIs/files into the installed location (such as the palette-sync'ed folders beneath user.lib)? Also please take a look inside "C:\Program Files\JKI\VI Package Manager\error\" for more error details. Thank you, -Jim
  24. Please see the announcement, VI Package Manager 1.0 Beta 2 Released. This release has a fix for this issue. Thank you, -Jim
  25. Ton, Please see the announcement, VI Package Manager 1.0 Beta 2 Released. This release has a fix for your issue. Thank you, -Jim
×
×
  • Create New...

Important Information

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