LabVIEW
resource file installation failed
On a fresh installation of Labview 8.5, I repeatedly without fail get a "failed installation" message as follows on step 70 and step 70 only. It says the NI LabVIEW 8.5 Resource installation has failed. Continue? Clicking yes or no seems to continue with the rest. When you try to open LabVIEW after this, it says "Unable to open resource files"".
I have removed all NI components, reinstalled multiple times, and tried to repair installations as well. I have no idea what the problem could be. Any ideas?
I hate to re-open the can of worms at this point, but I don't think the incompatibility is the issue here. I can install LV 7.x onto Windows 7 with no problem. Actually running LV 7.x on Windows 7 is somehwat tricky, but installing it isn't an issue.
True, you shouldn't be trying to use LV 8.5 on Windows 7, but it shouldn't complain about installing it there. Heck, if it's compatible with Vista, it should at least install onto Windows 7 without complaining.
Something is up with the install. Maybe a bad CD?
@natasftw wrote:
@billko wrote:
I hate to re-open the can of worms at this point, but I don't think the incompatibility is the issue here. I can install LV 7.x onto Windows 7 with no problem. Actually running LV 7.x on Windows 7 is somehwat tricky, but installing it isn't an issue.
Let's take this can of worms and say the installation could work. It's something that isn't supported, but that doesn't mean impossible. You've granted that installing the software doesn't mean it'll be easy to run the software. So, we can work with the OP to get it installed. Then, they'll likely run into another problem. If they need drivers, those certainly won't install.
We can open the can of worms. But, to what end? If we're sending the OP down a path of frustration by finding a workaround for the initial problem, are we really being helpful? It's fun to solve problems. But, in this case it might be best to solve this problem by choosing either an appropriate OS or dev environment.
I think you missed my point. prbably because I didn't go in-depth enough with what I was getting at.
My point was not to actually use this combination of LabVIEW and Windows versions, but it should have installed without a hitch. Something prevented it from installing correctly and it seems like it's a deeper issue unrelated to the LV/Windows combo. It needs to be resolved not so the user can use it, but so the user can understand the reason behind the failed install.
By the way - I've had personal experience with the little hell created when you try to use a combination of incompatible LV/Windows combos. At a company I used to work for, they asked me if LV 7.1 would work with Windows 7 even though the matrix said "incompatible". I highly recommended against it, instead recommending that either LV be upgraded or Windows be downgraded. They made the design choice to use LV 7.1 with Windows 7 to "save some money". 1 month later and I have no idea how many thousands of dollars worth of engineering time wasted on hair pulling, they decided to downgrade Windows 7 to Windows XP. (The core of the application was already coded in LV 7.1.)
@natasftw wrote:
billko wroteI think you missed my point. prbably because I didn't go in-depth enough with what I was getting at.
My point was not to actually use this combination of LabVIEW and Windows versions, but it should have installed without a hitch. Something prevented it from installing correctly and it seems like it's a deeper issue unrelated to the LV/Windows combo. It needs to be resolved not so the user can use it, but so the user can understand the reason behind the failed install.
I understood the point. It was pretty clear. I bolded part of your reply. My point was the bolded part isn't necessarily true. If the user can't use it, there's no need to understand this problem. Putting effort into solving this problem is wasted if the user can't use it. It's not entirely interesting to solve the installation failure.
If we're going to go down the rabbit hole here and try to understand what's causing the problem, we should make sure the user can make use of that effort first. If they can't, it's wasted effort and we should focus on finding a way to actually help the user rather than waste their time. There are many things that simply don't need to be resolved. This appears to be one of them.
I understand your point, also. I think our thresholds for "waste of time" are different, that's all.
