Unable to save LabVIEW VI or project when using ULx with LabVIEW 2024

[Jonathan MA Tech]

I have LabVIEW 2024 (32-bit) and am trying to get ULx for LabVIEW installed with it.

After installing LabVIEW, I used the MCCDAQ Software CD v6.75 to install InstaCal (but not ULx for LabVIEW) and then installed ULx for LabVIEW v2.29 as described by  here.

And I am having the same issue described here with icons not showing up in the functions pallet and have applied @Fausto's fix. The ULx_LV.dll and example files were there already but I had to copy the ULx.mnu and help files manually.

Unfortunately, I had an additional issue: When I place one of the ULx VIs onto a block diagram and try to close and save things, I get this error.

When I click OK, I get the a dialog prompting me to name the file.

If I click OK to that, it asks me if I want to replace the file.

If I click OK to that it takes me back to the "Cannot save VI......You do not have permission" error.

 

This makes it so that I cannot properly close larger software projects.

How should I proceed?

Edited August 14 by Jonathan MA Tech
Move images to middle of post

[Fausto]

Hello @Jonathan MA Tech.

Please reference the following post.

Regards,

Fausto

 

[Jonathan MA Tech]

Thank you for the reference. But the solution there is unacceptable.

In the past I've had the "While loading ______ LabVIEW reported 95 warnings. That's not that big a deal.

The permission issue when saving is new and is a problem. When I'm working on our larger LabVIEW application and changing multiple VIs (not necessarily involving ULx, I need to be able to "Save All" without picking apart what is and is not ULx code.

I want to have the library installed and to use the VIs that are in the functions pallet - not having to resave them in my own project's folder. What you're suggesting is NOT normal practice.

I think there is something different, either with a new LabVIEW version or Windows 11 that changed the permissions of the .llb files so that LabVIEW cannot overwrite the files in a new version.

Could you work on fixing this please?

[Jonathan MA Tech]

In this NI forum thread from 2012, Nextal's problem appears to have been fixed by unchecking "Read-only" on an LLB file.

Right clicking each .llb in C:\Program Files (x86)\National Instruments\LabVIEW <Version>\vi.lib\ULx\ , going to properties and unchecking "Read-only" solved my problem.

Why were the files marked as Read-only?

Would be great if the installer did all the things.

Edited August 14 by Jonathan MA Tech