07-12-2016 05:27 PM
My development system is LabVIEW 2011 32 bit on Win7 64 bit.
I wonder in what areas will I definitely get troubles when OS updates to win10 (for example access to user32.dll is forbidden), what areas are safe (LV communicates with driver and he should be compatible), and what depend on some parameters or OS specific configuration (data size, transfer speed is different, security rules require admin only rights, etc,)?
Both general considerations (Win7 and Win10 have difference in architecture in this aspect, so these functions should work differently or stop working) and specific experience (localized problem to this function) will be greatly appreciated and kudoed.
My application includes DAQmx (fast AI, counters), com-port communication, number of .NET interfaces (USB web-cam with image processing, thorlabs motion controllers, COM port, jabber, etc), local UDP to exchange data between LV and something else.
Application is built and customers have only exe and run-time with drivers. When one of the customers said that his PC updated to windows 10, I was scared, but everything worked except 10 year old USB-com that did not have drivers for win10.
Is it because runtime does not compile VIs and development PC (compiler) will have troubles if updated to win10?
07-12-2016 06:56 PM
Officially, the RunTime Engine prior to 2015 is not supported on Windows 10. This is not saying it will not work. I have LabVIEW 8.2 running on my Windows 10 machine with no problem (not really doing anything with it, but it does run). But if I do run into issues, I cannot run to NI and ask for help.
My honest recommendation is to just upgrade to LabVIEW 2015 and then you will have official support. I have yet to run into issues porting from Windows 7 to Windows 10. XP to 7 caused all kinds of issues...