Jump to content

Jim Kring

JKI Team
  • Posts

    2,199
  • Joined

  • Last visited

  • Days Won

    105

Jim Kring last won the day on February 6

Jim Kring had the most liked content!

7 Followers

About Jim Kring

Recent Profile Visitors

29,092 profile views

Jim Kring's Achievements

  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.
×
×
  • Create New...

Important Information

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