Jump to content

Jim Kring

JKI Team
  • Posts

    2,199
  • Joined

  • Last visited

  • Days Won

    105

Everything posted by Jim Kring

  1. > 1.0.0.4 (Apr 14, 2023) > 3. Add a mass compile post-install step to avoid bitness-related load warnings when opening the code for the first time after install. @Darren is this load warning a LabVIEW “bug”?
  2. @Bob Schor you'll find the actual packages in the C:\ProgramData\JKI\VIPM\cache folder. You can copy those to another computer and install the packages.
  3. Thanks for reporting this @jyoung8711. FYI @Rolf Kalbermatter
  4. Hi @hooovahh, I didn't realize that this library offers support for spanning TDMS. I'm going to take a look at this right away... 👍 Thanks for the great tool!
  5. @Zaphiro Technologies CC: @RolfK There is a cross-platform shared library naming trick. (It could be that the package build process messed up the paths when writing linker info.) See: LabVIEW Help >> Configuring the Call Library Function Node
  6. @JKI-OfAllTrades I'm not sure about that. I think that, in general, most of the community has moved to LV2020 as the standard version for open source/community tools. You could reach out to some of the folks in the DQMH forum.
  7. Hi @JKI-OfAllTrades, Looking at the VI Peek package info, I see that it's compatible with LabVIEW 2020 or greater, which is why it's not showing in your package list. Note: In the VIPM Settings window you can show all packages, even if incompatible with the selected LabVIEW version. However, you won't be able to install it. One idea is to download the source code and then use LabVIEW 2020 Community Edition to Save For Previous into LV2017. Good luck!
  8. I think this might be a LabVIEW bug related to PPLs and Malleable VIs. Maybe @Jamespowell80 knows.
  9. This is very odd. First, I would avoid running VIPM as Administrator. Probably LabVIEW does not have permission to execute the PostInstall script. Can you run VIPM as a non-admin user?
  10. Which version of VIPM? Which version of LabVIEW?
  11. Some searching online shows. Possible solution… This kind of behaviour can be encountered when a scheduled task is created in order to continue the installation process after a reboot triggered by a prerequisite. After the system reboots, the setup is launched by the scheduled task and, then this scheduled task is then automatically removed. In your case it seems that the removal doesn't happen, thus the setup is launched on every boot. You could try to manually delete this scheduled task from Windows Task Scheduler. If you cannot find a task in Task Scheduler, please check if the following registry keys contain a value which triggers the setup: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run or HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
  12. Hi @Ludwig Berndt. I'm not sure why this would be getting launched at start up. Yes, it looks like it's the installer repair dialog. Can you see if this newer version (2024 Q1 f2) resolves the issue.
  13. Hi @Anton Sundqvist Yes, this will be a common problem for users of your package. By default the LabVIEW CLI folder will not be writable to users. -Jim
  14. Hi Ludwig, Can you show me a screenshot of the "VIPM setup wizard"? It sounds like you're talking about the installer, but I'm not sure. Regards,
  15. Hi @JKI-OfAllTrades Please try upgrading to the latest version of VIPM (2024 Q1 available at vipm.io/desktop) and let me know if that fixes the issue for you. There's also an option in VIPM's settings to show all packages, even if they are not installable in the currently selected version of LabVIEW. If all that fails, I'll offer other suggestions.
  16. Hi @Anton Sundqvist My guess is that the permissions are such that only administrators can install things into the "C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI" folder. Probably, the easiest solution is for the user to make that folder writeable to all users. Then, the package should be able to install files there, even if VIPM is running as a non-admin user -- this is better than trying to run VIPM as Administrator, which can result in other issues.
  17. Yes, there’s always that factor. And, sometimes a reboot is good for all of us 🙂
  18. That's great news! Thanks for lettings us know.
  19. @KevSalmon can you try the network settings and see if that makes a difference? Also, you may also need to upgrade to the latest vipm here: https://www.vipm.io/desktop/versions/ There have been some improvements to the network downloading of the LabVIEW Runtime.
  20. Hi @KevSalmon. Thank you for reporting this. Can you please try again? There were some server issues that we believe are now resolved.
  21. Hi @Sam Sharp. Thanks for releasing this! I was actually playing around with .NET's AES interface and wondering if anyone else had already done so. Nice work!
  22. Hi Andrea, The aim is for dragon.vipm.io to support this. Parts of it, under the hood, do already support it, but it's not yet exposed in the Package Dependencies UI. -Jim
×
×
  • Create New...

Important Information

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