Can LV2016 32 bit run on Win 10 64 bit?

[Cryotester]

We just upgraded to a win10 system, and now are finding out that traditional DAQ is not supported in 2016 64-bit. Will LV2016 32-bit run without issue if loaded onto a 64-bit OS? I have other software setup and calibrated on the 64 bit machine and loathe the idea of possibly losing my cal files in the process of removing and reinstalling EVERYTHING.

[Jacobson-ni]

Yes, it will work. You can also have both 64 and 32-bit LabVIEW installed side by side.

http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98

[tyk007]

In addition to the answer; virtually all Windows 32-bit applications will run on Windows 64-bit OS (including LabVIEW). Microsoft added this backwards capability via the WOW64 mode of Windows 64-bit OS.

The only caveat is that 32-bit applications can still only access a maximum amount of virtual memory of 2Gb (3Gb if the large address aware flag was compiled in) irrespective of what physical memory is available. This also include LabVIEW 32-bit. The implication of this is that the LabVIEW 64-bit version is required if your application needs more than the 2Gb. In your case you already having code working within this limit so it is not a concern. 

[altenbach]

---

@tyk007 wrote:

This also include LabVIEW 32-bit. The implication of this is that the LabVIEW 64-bit version is required if your application needs more than the 2Gb. In your case you already having code working within this limit so it is not a concern. 

---

When running on  64bit windows, 32bit LabVIEW can use 4GB. (details)

[tyk007]

---

@altenbach wrote:

---

---

When running on  64bit windows, 32bit LabVIEW can use 4GB. (details)

---

Thanks for the correction.

[altenbach]

OTOH, traditional daq requires a 32 bit OS.

[Bob_Schor]

---

@altenbach wrote:

OTOH, traditional daq requires a 32 bit OS.

---

But DAQmx is much to be preferred to Traditional (a.k.a. Legacy) DAQ.  I once had to try to understand a data acquisition/control program written in LabVIEW 7.0 -- what a mess to get A/D configured, compared to three or four DAQmx function calls ...  Even talking with an NI DAQ Guru didn't add all that much clarity.

Bob Schor

[Yamaeda]

Yeah, if you're running LV2016 you really should use/upgrade code to DAQmx if you haven't.

/Y

[Hooovahh]

---

@Yamaeda wrote:

Yeah, if you're running LV2016 you really should use/upgrade code to DAQmx if you haven't.

---

No lets take it further, how about if you are using LabVIEW 8.5 (released in 2007) or newer you should be using DAQmx.  It really is a well done API.

[Cryotester]

Using DAQmX is a non-starter as we have AMUX boards that must be accessed, which mX doesn't support.

Thanks for the info tyk007, at least we can load them side by side without a complete strip of the system.

OTOH, traditional daq requires a 32 bit OS.

Altenbach- Are you implying that the traditional DAQ won't even function with a 64 bit OS?

---

---