Jump to content

Dmytro

Members
  • Posts

    9
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Dmytro

  1. 1 minute ago, Alik Sargsyan said:

    Thank you, @Dmytro, for raising your question in this forum.

    I've responded to you via email, but I'll also provide the answer here for everyone's benefit.

    The problem was due to a corrupted .vip file on NI's FTP server. This issue has now been fixed, and the most recent version of the toolkit can be installed once again.

     

    Thank you, Alik! Can confirm, I am playing with the CuLab right now.

  2. I am trying to install the CuLab (GPU Accelerated Toolkit), version 2.1.1.50, but this does not work.

    When I try to install from the VIPM, the package download is stuck in the middle of the process and eventually cancels automatically without even an error message.
    When I try to open the downloaded package (downloaded from https://download.ni.com/evaluation/labview/lvtn/vipm/packages/ngene_culab_gpu_accelerated_toolkit/ngene_culab_gpu_accelerated_toolkit-2.1.1.50.vip) in the VIPM and install it - VIPM chews the package for a minute or two, then shows a strange message (on the picture below), then throws an error.
    image.png
    image.png
     
    I've tried two latest versions of VIPM, tried to run VIPM as an admin user, but to no avail. 
     
    Does anybody have any ideas?
     
    Just in case, my system is Windows 10 x64 Pro, LabVIEW 2023Q3,  VIPM 2024.1f1 Free edition.
    • Like 1
  3. On 6/19/2023 at 7:30 PM, Jim Kring said:

    Hi All,

    There is a VIPM 20203 release candidate available here:

    vipm-2023Q3-rc2-windows

    Some of the Fixes and Improvements:

    - VIPM now works with any LabVIEW Runtime greater than or equal to 20.1, to simplify installation process and avoid installing older versions of LabVIEW runtime if a newer version is installed (VIPM previously required exactly version 20.1 of the LV Runtime)
    - Fix Issue #25 affecting various user input dialogs (e.g. palette item renaming caused the dialog to get stuck and not close)
    - Improved package building in LabVIEW 2017-2019 (some improvements make for packages saved in LV 2020 and greater were back-propagated to work with older LabVIEW versions)
    - Speed-up of VIPM startup time for first launch after installation (installer now includes a cache of package info of latest versions of public packages)

    Please let us know if you run into any issues.

    Hello Jim. 

    Strange, I've posted around a week ago and now post just disappeared...

    Nevertheless, I've tested this new version, and while it works in general, there is still the same issue present (when some packages shown as incompatible while in fact the are compatible), as discussed here: https://www.vipm.io/posts/2de25b0c-baeb-4ace-aa7e-8fb53d315afc/

     

    Hope this helps.

     

    Kind regards,

    Dmytro

  4. Same problem. Tested and confirmed with VIPM 21.0.2750, 21.1.2754, 22.0.2371.

    The latest version which works is 20.0.2302, but it does not know about the newest LabVIEW versions.

     

    According to Process Explorer, VIPM process hits ~3.2 GB and crashes (see couple of screenshots below).

    PC configuration:

    Processor    AMD Ryzen Threadripper 2950X 16-Core Processor    3.50 GHz
    Installed RAM    64,0 GB (63,9 GB usable)
    Edition    Windows 10 Pro
    Version    22H2
    OS build    19045.2251
    Experience    Windows Feature Experience Pack 120.2212.4180.0

     

    Installed LabVIEW versions: 2018 and 2022 Q3 (both 64 bit).


     

    Screenshot 2022-11-15 180853.png

    Screenshot 2022-11-15 175240.png

    Screenshot 2022-11-15 175146.png

    Screenshot 2022-11-15 175130.png

×
×
  • Create New...

Important Information

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