07-02-2015 06:46 AM
While I've never tested it, I don't think the EXE stops working after so many days. I guess NI assumes anyone making an EXE (especially for a production environment) isn't going to be happy with the "Evaluation" watermark on every pane of every window. If I was Ford and came to a suppliers location where they were testing Ford components, and their software had evaluation on it I would be pretty upset.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
07-02-2015 09:27 AM
@Hooovahh wrote:
While I've never tested it, I don't think the EXE stops working after so many days. I guess NI assumes anyone making an EXE (especially for a production environment) isn't going to be happy with the "Evaluation" watermark on every pane of every window. If I was Ford and came to a suppliers location where they were testing Ford components, and their software had evaluation on it I would be pretty upset.
True enough for the Fords of the world, but it would be a boon for small companies that just need some in-house testing software on the cheap. They could write it in LabVIEW Eval and make a EXE, then whenever they need to upgrade/fix/add code just have a different employee download the Eval version again and have another 52 days of free LabVIEW. Not that I'm suggesting anyone should do that!
07-02-2015 09:33 AM
@NIquist wrote:
@Hooovahh wrote:
While I've never tested it, I don't think the EXE stops working after so many days. I guess NI assumes anyone making an EXE (especially for a production environment) isn't going to be happy with the "Evaluation" watermark on every pane of every window. If I was Ford and came to a suppliers location where they were testing Ford components, and their software had evaluation on it I would be pretty upset.
True enough for the Fords of the world, but it would be a boon for small companies that just need some in-house testing software on the cheap. They could write it in LabVIEW Eval and make a EXE, then whenever they need to upgrade/fix/add code just have a different employee download the Eval version again and have another 52 days of free LabVIEW.
Not that I'm suggesting anyone should do that!
My eyes!!! I am blind!!! 😉
07-02-2015 09:54 AM
@NIquist wrote:
then whenever they need to upgrade/fix/add code just have a different employee download the Eval version again and have another 52 days of free LabVIEW.
I think you over estimate how well the NI evaluation date check works. The process is much more simple to extend a trial. And those types of companies will probably just pirate the NI software anyway.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
07-02-2015 10:07 AM
I assumed that this would be done on a separate computer each time.
07-03-2015 09:05 AM
Well I'm not complaining if it means more LabVIEW users. That's better for all of us dedicated customers. My company just bought a huge package of engineering support, site licenses, hardware and training credits from NI (and Bloomy) so I guess their policies reflect their confidence in the future. Plus there's the new $50 LabVIEW Home Edition which also shows they would rather bring new users to LabVIEW than quibble over a few dollars in licencing fees. I'm sure they also know that once you get into LabVIEW it's not long before you're drooling over the advanced toolkits and NI Hardware. They must make good profits on that.