Jump to content

Jim Kring

JKI Team
  • Content Count

    1,440
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by Jim Kring

  1. I don't understand... why would you ever want to uninstall VI Package Manager? Joking aside, you can uninstall it by doing either of the following: Select: Start>>Programs>>JKI>>VI Package Manager>>VI Package Manager Uninstall Run: C:\Program Files\JKI\VI Package Manager\uninstaller.exe Thanks, -Jim
  2. Matthias, You're welcome -- I hope we can help. Your error log file shows a permission error when trying to access the VIPM configuration file. Does your user account have write access on the VIPM installation location and files? Is the "VI Package Manager.ini" file read-only? Try running VIPM from an admin account and see if it works. Thanks, -Jim
  3. Hello, Sorry to hear you're having issues. Can you please look to see if there are any error log files? They would be located here: C:\Program Files\JKI\VI Package Manager\error\ Please post any error messages inside the log files and we'll see if we can figure out what's going wrong. Thank you, -Jim
  4. Hi Dan, I'm happy to hear that. My suspicion is that it might have been an issue with a proxy (or other) server between you and our download server. Thanks, -Jim
  5. Hi Dan, Please send us a support request, using this link: http://jameskring.com/index.php?page=contact We will work with you to resolve the dowload issue and make sure that you get up and running, quickly. Thanks, -Jim
  6. Hi Ton, Thanks for the suggestion. This certainly would be a nice feature -- I really hate having to restart LabVIEW just to refresh the palettes. I have added your suggestion to our internal "Feature Requests" tracker (Case 4533: Optionally refresh palettes after installing/uninstalling packages). Thanks, -Jim
  7. Hi Ton, Which feature would you like associated with the Open action? I'm thinking that you're probably wanting this associated with the Package>>Add Package(s) to Package List feature. Traditionally, the Open action is associated with File>>Open. Currently, VIPM is not a file editor, but, as you know, we are working on implementing a configuration management solution and will have configuration files, soon. We are planning to support File>>Open for package configuration files. Thanks, -Jim
  8. Hello, This appears to be an issue with the LabVIEW Run-Time engine resolving paths to shared libraries. It can probably be fixed by creating a symbolic links in the expected location to the shared library in the installed location. I'll try to find an answer. In the mean time, please try placing a support request to NI or posting on the NI LabVIEW discussion/support forum. If you do find the answer, please post it here, so that we know your up and running and perhaps it can help someone else who is having the same issue. Thank you, -Jim
  9. We have created a new section of our VIPM Resources forum for Tutorial Vidoes., here: JKI Software Forums > VI Package Manager > Resources > Tutorial Videos Our first video is titled "Getting Started with VIPM and Installing OpenG Libraries into LabVIEW" If you have any feedback, please let us know
  10. Hi Jason, Actually, uninstalling all the dependants (recursively) ensures that packages are not broken, after the uninstallation step. For example, assume that you have packages A, B, and C installed. And, assume that package A requires package B. If I try to uninstall B, then VIPM will tell me that I should also uninstall package A (since A depends on . After I proceed, uninstalling A and B, I am left with package C installed. Package C has no dependencies on A or B, so it is fully working, after the uninstallation of A and B. Thanks, -Jim
  11. Hi Tim, Thanks for reporting this. We will work to reproduce this issue and find a fix. Thank you, -Jim
  12. Danny, Installing the 1.1 beta version requires that you upgrade your 1.0 installation. However, the 1.1 beta is very stable, and you should not have any issues -- we have been using it ourselves, internally, for quite some time. I encourage you to sign up for the beta. Thanks, -Jim Kring
  13. Hi Tim, Sorry for the trouble. Are you installing on an x86 Mac (vs PPC)? I'm not really sure of the problem. Any info that you can give about which versions of CPU type and LabVIEW version you are using will help. Thanks, -JIm
  14. TiTou, As Philippe mentioned, your issue likely due to the selected TCP port being in use already or blocked. 3363 is the default port for VI Server and works well. If you have multiple LabVIEW versions, you should probably put them each on a different TCP port, and increment them off of 3363 (e.g., 3363, 3364, 3365, ... ) -- this approach has worked great for others. Thanks, -Jim
  15. TiTou, > I found kind of a work-around... I'm happy to hear that it's working, now. > I copied on my PC the LabVIEW.ini of my colleague and then it work... That's very strange. Can you post your original (non-working) INI file, so that I can take a look? Thanks,
  16. There are a couple possible issues. The simplest one is that your VI Server settings might not be configured to allow VIPM to run the installation script VIs that are inside the dynamicpalette package. Can you please take a look at this FAQ entry and see if your VI Server settings are set up correctly? Why do I get Error Code 1032 when I try to install some packages? Thank you, -Jim
  17. Chris, I've spoken to you off-line about the VIPM 1.1 beta, but I'll restate myself here so that others can benefit from the info. We are actively working on VIPM 1.1 and the beta will be starting soon. If you're interested in helping test these new features (and possibly get early access to bug fixes to issues such as this one) please let us know and we'll keep you in the loop about the beta. Thanks, -Jim
  18. Hi Greg, Thanks for the feedback. We have this feature on the map. We're currently working out the specifics of the implementation. Thank you, -Jim Kring
  19. Doug, Thank you for reporting this. We will look into it, right away. Thank you, -Jim
  20. David, We have just completed our first How'd they do that? article, titled Alternating Row colors in Multicolumn Listbox. Thank you, -Jim
  21. I'm sorry to hear that you are still having some issues. Please try to set your VI Server settings manually in the LabVIEW options. Please see this FAQ posting for some instructions. Regarding the TCP timeout, please try setting your Internet setting TCP Timout to 60 seconds, and see if that helps with the connection problems. I see from your screenshots that it is currently set to 10 seconds. Also, it would help if you posted your error log files, which will be located here: C:\Program Files\JKI\VI Package Manager\error Thank you, -Jim
  22. You need to make sure that each LabVIEW version is configured for a different TCP port. Please see this post for instructions on how to fix the problem. You might also want to read the LabVIEW Options - Version Management and Configure LabVIEW Port dialog documentation pages. Thank you, -Jim
  23. Jeffrey, Thanks for the kind words and for the valuable feedback. We are actively working on features that address configuration management issues. Stay tuned... Thank you, -Jim Kring
×
×
  • Create New...

Important Information

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