01-18-2010 02:06 AM
Our team (FRC 2472) was installing LabVIEW from the discs on our programming computer and someone unknowingly turned it off as we packed up for the night. The installation stopped and we can see evidence of unfinished softare components because of broken NI shortcuts on the desktop.
Two of our members who are more computers-in-general savy apparently looked at it and tell me that the partially installed files are corrupted. They say there is no way to fix this except for wiping the whole memory of the computer and starting completly over. I refuse to believe that this is the only way to fix this without knowing for sure myself. This doesn't make sense and is a major major thing to do.
I will ask them about the situation tomorrow at our meeting, but I'd also like to get an opinion from NI or anyone else who may have had this problem. I'll also call NI up through their helpful FIRST hotline during the meeting, but maybe I'll get some hits in this discussion before then. Does anyone know what can be done as an alternative?
I asked my dad about it and he said typically you should just be able to start the installation over and it will copy over the previous/bad files. It might also notice that the good ones from the beginning of the installation are already there and skip those. If that didn't work, try uninstalling/removing the files and then re-installing. This makes a lot of sense to me and I will certainly try this.
Thanks for your help!
01-18-2010 08:28 AM
I would start with the Control Panel and the Add or Remove Programs.
Scroll down to the "National Instruments Software" and try the repair option first.
If this does not work try your Dad advise next
If that does not work then your trying removing the NI software and doing a complete re-install.
Omar
01-18-2010 07:15 PM
Thanks for the advice, we didn't know about the repair option.
We tried it but when it asked us for some files to refer do (can't remember what type they are called), we couldn't get it to work the way we thought it should. To avoid any further mess-ups, we just installed it again right over the corrupted files. It worked great; it skipped ahead very quickly and resumed installing. Now we just need to install the update and it should work, we don't see any problems.
Thanks!