Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).

[MrEF]

Hi all.  Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).  This really slows things down!  Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini.  Has anyone seen similar, and/or any hints towards a solution?  

[altenbach]

Looks like a general permission problem on the OS side. Did you install it into the default location or elsewhere? What are your admin priviledges?

[MrEF]

Yes, installed in default.  And I've got Admin permission.  But thank you for a direction to look!

[MrEF]

OK, I found the solution.  A cautionary tale... I had installed 64-bit LabVIEW 2013, but some drivers weren't available for this version, so I ALSO installed 32-bit LabVIEW 2013 (without uninstalling 64-bit).  Seems like I was running the 32-bit version, but LabVIEW was saving the LabVIEW.ini to the 64-bit folder, where it couldn't find it.  So my LabVIEW couldn't remember having done the compiles.  SOLUTION:  Uninstalled both versions and re-installed only 32-bit LabVIEW 2013.  Seems to be working so far -- at least my VIs load without recompiling each time, and my Quick-drop is fast again.  

[altenbach]

That's odd. I have the 32bit and 64bit version of LabVIEW installed at the same time without any problems.

I suspect that the problem was with your drivers. What were they and how did you install them originally?

[MrEF]

Interesting.  I'm mostly using the Report Generation Toolkit and the Database Connectivity toolkit (neither compatible with the 64-bit version of LabVIEW).  Only hardware drivers are the NI-RIO set (default configuration).  Whatever the original cause, my 32-bit folder did not have a labview.ini file.   

[Darren]

I'll keep this in mind if I hear about the problem again (since a non-compiled Quick Drop is definitely a showstopper), but I also have both 32-bit and 64-bit LabVIEW installed (many versions), and just about every NI driver, toolkit, and module installed as well, and I've never had the issue.

[Jeff-P]

32-bit and 64-bit LabVIEW installed side by side is tested and supported on both Windows 7 and Windows 8. By default, LabVIEW.ini should not have any effect on forcing VIs to compile - if you are opening VIs that were not created in the same version of LabVIEW, LabVIEW will recompile them, but it sounds like something was strange in your system if opening quick drop caused a recompile.

As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.

Regards,

Jeff Peacock 

Product Support Engineer | LabVIEW R&D | National Instruments 

[altenbach]

---

@Jeff-P wrote:

As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.

---

I thought that the message: "Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini"  might indicate that the labview.ini file cannot even be created... strange...