06-05-2021 08:44 PM
When restarting an old computer that had been sitting off for years, I discovered that LV 7 and LV 2010 both will not run until the computer clock has been set....! After the CMOS battery dies some computers default to an absurd date year 9999. That alone can keep Labview from launching properly, resulting in an error dialog with the subject message.
06-06-2021 01:52 PM
06-08-2021 07:18 AM
Indeed, GerdW, but things would have been so much better (and I would have saved hours of running computer diagnostics) if the error message had been:
"Labview.exe has stopped working....because the computer's date is invalid."
Scott
06-08-2021 07:21 AM - edited 06-08-2021 07:22 AM
I'm actually surprised that your computer's antivirus program and/or operating system didn't pick this up.
06-08-2021 11:11 AM - edited 06-08-2021 11:12 AM
@Scott_Little wrote:
Indeed, GerdW, but things would have been so much better (and I would have saved hours of running computer diagnostics) if the error message had been:
"Labview.exe has stopped working....because the computer's date is invalid."
Of course it would. But then who would ever think about testing that? I'm pretty sure the problem was not because LabVIEW tried to explicitly setup some time function at the moment it was dieing but rather was doing something else such as initializing some other OS interface or whatever that is supposed to be such a fundamental part of its OS interaction that its mere possibility to not initialize successfully is considered impossible by programmers since Windows then surely can't even be running and hence LabVIEW can't have been started by the non existing OS. 😀
Also most computers with died CMOS battery that I have seen set the clock rather to some default date instead, usually somewhere around the BIOS creation time. One old Laptop I have always starts up with some date in 1999 when it was more than a few days switched off! That has caused some applications to fail in the past but LabVIEW is happy to startup anyways.