*.vi has unsaved changes, how to solve this ?

[NateWang]

I have an existing test.vi file from other people, when I open the test.vi, I got warning message as below :

the test.vi runs just normally, but when I close the test.vi, I got message as below :

and if I click save, I got :

and if I click OK it just got back to the previous window :

so the only choice to me is to clock don't save

but in this case every time I open the test.vi I see the same message again and again, how to solve this ?

Thanks.

[ZYOng]

Most likely the VIs were saved in an earlier version of LabVIEW and you open them using a newer version of LabVIEW. One way is to Mass Compile so that all VIs are saved in the current version of LabVIEW.

As for the permission error, most likely the VIs reside in a directory where LabVIEW does not have the permission to write. You can try to move the project to another directory, or run LabVIEW as admin.

[NateWang]

Hi ZYOng,

One way is to Mass Compile

move the project to another directory

run LabVIEW as admin.

>> all of the above three suggestions were done but the probelm is still the same, thanks.

[billko]

The first screen shows a conflict.  Solve this conflict and likely your issue goes away because it is no longer pointing to the file you cannot save.

[NateWang]

Hi billko,

I am new to Labview and may need some more guidance. 

From the warning message, Labview tells me the "CsLv_FreeSystem.vi" was loaded from a new path :

C:\Program Files(x86)\National Instruments\LabVIEW 2023\user.lib\Gage\CsLv.lib\), rather than the original path :

C:\Program Files(x86)\Gage\CompuScope\CompuScope LabVIEW SDK\CsLv\.

And I believe the "CsLv_FreeSystem.vi" file on both locations are correct, either one would be fine, I do not understand what's the conflict you are meantioning about.

Also, I do not understand what's the relationship between the "CsLv_FreeSystem.vi" and the "CsTool-ErrorHandler.vi", is "CsTool-ErrorHandler.vi" called from "CsLv_FreeSystem.vi" ?

what's the exact steps to solve the conflict ? Thanks.

[billko]

---

@NateWang wrote:

Hi billko,

I am new to Labview and may need some more guidance. 

From the warning message, Labview tells me the "CsLv_FreeSystem.vi" was loaded from a new path :

C:\Program Files(x86)\National Instruments\LabVIEW 2023\user.lib\Gage\CsLv.lib\), rather than the original path :

C:\Program Files(x86)\Gage\CompuScope\CompuScope LabVIEW SDK\CsLv\.

And I believe the "CsLv_FreeSystem.vi" file on both locations are correct, either one would be fine, I do not understand what's the conflict you are meantioning about.

Also, I do not understand what's the relationship between the "CsLv_FreeSystem.vi" and the "CsTool-ErrorHandler.vi", is "CsTool-ErrorHandler.vi" called from "CsLv_FreeSystem.vi" ?

what's the exact steps to solve the conflict ? Thanks.

---

It's actually the opposite - CsLv_FreeSystem.vi is being called from CsTool-ErrorHandler.vi.  The location of CsLv_FreeSystem.vi changed, causing CsTool-ErrorHandler.vi to recompile and need to be saved.  This is a very bad situation because a file in one library now depends on a file in another.  Delete the Gage folder from either place and then accept all the dependency changes.  I could make a case for either folder to win over the other, so it's your choice.  Maybe someone else here has a different opinion?

[NateWang]

Hi billko,

If I delete the below folder and accept all dependency

C:\Program Files\Gage\CompuScope\CompuScope LabVIEW SDK

I got this error and have no idea how to fix it :

(I actually know the location of "cs_1c.vi")

and if I delete the below folder and accept all dependency

C:\Program Files (x86)\National Instruments\LabVIEW 2023\user.lib\Gage

I got the below error :

I am new to Labview and any suggestion would be really appriciated, thanks.

[NateWang]

Hi Sir,

It seems I had solved the problem by adding full control authority of "User", thanks.