09-25-2013 03:41 PM
Is there anything interesting about the CPU (e.g. non-SSE3, many cores, etc.)?
09-26-2013 07:17 AM
It's a Core i7-2620M @ 2.70GHz. 8GB RAM
Win 7 Enterprise
Standard issue Dell laptop used in the company I work for. Started service in June 2011.
Attempted to Run as Admin and got the same error but without the error reporting dialog. I can read the splash screen now. It's "Initializing resource files". Crashes in the early stages of start up.
09-27-2013 12:43 PM
I see that you have contacted support here for additional help. At this point let's focus on getting this worked out through that service request, but please keep us updated with any new infromation!
09-27-2013 12:50 PM
Yup. I'll post the results here. Thanks for your support. 🙂
10-03-2013 07:13 AM
Sorry but the root cause of the issue was not found. Possibly it was too long of a path in the program directory. I got an error of "path too long" when I attempted to make a copy of the LabVIEW 1012 directory. The error was for the following folder: "C:\Program Files (x86)\National Instruments\LabVIEW 2012\instr.lib\_niInstr\DSP\v1\FPGA\Private\Equalization\FIRFilterSimFiles\isim\EqSingleFilter_597026864DC13FFFA120CE82B9307E2D.dll.sim\unisim"
I don't know the function of the folder (and a bunch of other folders like it) but if it implies use of FPGA then I don't need it.
I learned that the "LabVIEW 2012" folder is not deleted during an uninstall. So when you reinstall there is the possibility that you are retaining some unwanted files and folders. The Repair option also did not work.
I renamed the current LV directory and did an install into the default path. Then LV was working again. I learned a lesson, though, and that is to make a backups of your installation folder before and after any changes. But then maybe not because I've not had an issue like this starting with LabVIEW 2.5.2. 🙂
10-03-2013 07:26 AM
Hi,
I had the same problem with 2011->2012 and the solution was to completely reinstall windows. Now I installed 2012->2013 and there was no problem. I think it might be a problem with the registry in windows. Try to run, for example, Ccleaner and repair your registry, or do as I and reinstall windows.