Installing LabVIEW nightmare

[MEStech]

Hello,

I am new to LabVIEW and after spending three days trying to get the NI Developer Suite 2004 (p/n 777904-03) installed I must question how poor the installer is. The instructions are not much help either.

I started the installation by trying to install the LabVIEW/CVI and I received messages about needing to install other applications before I could install some of the features. I cancelled the install and then tried installing LabVIEW only to get the same messages. I carried on to the drivers and received a bunch of error messages that made me guess what I needed to uncheck to continue. I felt that I was going in circles and now I am not sure if I have to run through the process again to install any componenets that were not installed the first time. It took me 3 days to get to this point not counting the reboots and disk changes required.

Now I may be spoiled using Linux and having to install this on WindowsXP but if this is the way it is in Windows, I am glad I use Linux.

I would assume that a company that can design easy to use software like LabVIEW could design an installer like RPM, APT or YUM that is used in Linux to deal with all these issues. Or even package the kit with a configured installer that has all the flags set and can request the individual CD's when required. Not leave the person stuck with the task to figure out the mess.

Now to top it off, I received the updated version yesterday with only installation instructions. I searched the knownledge base on how to install the update and found no answer. Of course I couldn't find a clear answer on the installation issue either.

12 CD's to install on less than 2gigs of space. A single DVD with a front end to select all the necessary files to meet the requirements of the software package. Even a package with 3 or 4 CD's configured for the package purchased. I cannot afford this lost production time. At least it isn't my normal work computer. 🙂 🙂

[EdDickens]

This sounds like something specific to your situation. The Windows installer for LabVIEW has never given me any problems even remotely close to what you're describing.

You should be able to call NI for installation help. http://www.ni.com/support/ Something strange is going on.

Ed

[MEStech]

It isn't just LabVIEW it is the whole 12 CD set.

As I said, there should only be one installer, not 6 or 7 or more, I lost count.

Lets see, the 12 CD's are:

Measurement Studio Enterprise Edition, IVI Driver Toolset, LabVIEW 7 Express Professional Development System ..., Toolkit Software, TestStand, Swithc Executive Development System, Device Drivers for Data Acquisition Disk 1 and 2 of 2, PDF Library Disks 1 and 2 of 2, LabWindows/CVI Full Development System for ... and Measurement Studio Enterprise support for Visual Studio.

As we purchased this as a package, why is the installation as individual software packages.

I thought of a great example earlier today.

It would be like purchasing MS Office Pro and having to install Word, reboot. Install Excel, reboot. Install Access, reboot etc. This is what the experience is like. This is a pain from what I have been used to in the last 6 years. In my Linux install, I click the applications that I am installing and then it tells me what disks to put in and then there still is no reboot.

The instructions in the package and from the knowledge base are pretty vague. Even others have posted questions and gotten the vague answer.

Step 1. Application software such as LabVIEW, LabWindows/CVI, Measurement Studio, and TestStand.

As the order of the CD's had LabWindows/CVI before LabVIEW and from both the knowledge base and the above instruction, it doesn't actually specify that LabVIEW is first, I tried to install it first. Okay that didn't work as expected.

Following the above format, I had to install the Driver disk after LabVIEW and when I selected everything as I didn't know where we are going to endup on this system, I received some error messages about not having certain software installed. The problem was I had no idea what some of the options were and which ones were causing me the errors. Later I came across a window that was removing something that was installed earlier. I just clicked okay as I needed to get this done. Some mentioned VISA which to me is a Credit Card. After much work, I got past the drivers. This was the second restart.

Same thing with the LabWindows/CVI. restart. Drivers restart. TestStand and Drivers Restart.

From someone that hasn't rebooted in 77 days, this is frustrating. As example, I tried 5 programs this afternoon and installed them, tested them and removed two of them without even loggin out of my desktop. To me this is supposed to be a single install. I haven't even counted the patch files or the other add-on's.

Maybe it is a rant but the installation of a full suite should be a single package. As stated, the installer should be much more intelligent. I have never used LavVIEW and I have been tasked with getting this operational. I told one person that if they want me to become an expert, they will have to get the Linux version. 🙂

Here is a link to what I am used to.
http://fedora.redhat.com/projects/anaconda-installer/images/screenshot-0002.png
or
http://www.cobind.com/yumgui.html

I am not looking forward to installing the new version which ended up on my desk yesterday. 😞 12 CD's again and the exact same instructions.

[EdDickens]

I do understand what you are saying. The software update package I just received from NI last month had 35 CDs. DVD's are nice, but not every machine out here has a DVD drive. So maybe NI could offer it either way? This drives up productions costs, and guess who would end up paying for that?

If all you are going to run is LabVIEW, all you need to install is LabVIEW and the Device Drivers for Data Acquisition Disk 1 and 2, and that is a single installer. If you're not going to program anything in LabWindows, Measurement Studio etc., there's no need to install them. If you need them later, you can install them later. LabWindows, Measurement Studio and everything else are completely separate applications from LabVIEW. The Toolset CD has some extra tools that you can add to LabVIEW, so you might want to give that a look, but each tool has a separate installer. But again, you only need to install what you are going to use.

I do agree that documentation of the installation process is lacking. It seems they expect everybody has installed before and should know what to do. Maybe there's instructions buried on a CD somewhere, but they should have a paper document with the CDs with basic instructions.

As for installing the new pack you just received, you probably don't need to bother. With the subscription service, you get a complete pack every quarter of your particular set, even if nothing has been updated. Check the version printed on the disk. On the top, it should say "LabVIEW 7 Express", but on the right hand side just above the blue line, it should say "Version 7.1". Which should be same version you are running from the 2004 pack. Yes, they could just send only those with updates since the last release, but I guess it's easier for NI to just send everybody a complete set instead of trying to track who needs what. I've been getting these huge packs of CDs for a few years now. Guess how many extras I have laying around.

A single installer for everything would be nice. I can't argue with that. Although it would have to be much smarter than the Office installer. Office has maybe 4 or 5 different distributions? There are probably several dozen different distributions of LabVIEW and the Developer Suites. And anyway, the Office installers aren't perfect either. Our Office pack comes with everything they offer, but the "full" installation only installs Word, Excel, Outlook, Access, Publisher and PowerPoint. I also need Visio, Project and MapPoint. All three of these are individual installations, even though they came with the rest.

Ok, now I'm ranting a bit, sorry 😉 Give support a call if you're still having problems. NI really has a good support system.

Ed

Message Edited by Ed Dickens on 03-17-2005 04:33 PM

[tbob]

I have used UNIX for 10 years and I can sympathize with MEStech. We can all thank everyone's favorite rich person, Bill Gates, for burning down the competition so he could sell his 4th rate Windblows OS. With Windows, reboots is a fact of life. In 10 years I have never seen some UNIX system be rebooted. The only time they reboot is when they install a new OS version. Drivers and applications are installed and uninstalled without having to reboot at all. And UNIX NEVER CRASHES. I mean NEVER.
That being said, I nor anyone else I know has had any problems installing Labview. Put in the disk, run the installer, let the defaults be chosen, and it installs with no problems. It then prompts you to put in the Driver CD, disk 1 then disk 2, and then you have to reboot. Not much trouble at all. MEStech, you must be doing something wrong. I agree that it is a pain to have to install all the different toolkits and applications (TestStand, CVI, Switch Exec, etc) separate and reboot after each one. But that's because Windows sucks and makes you do that, not NI's fault. If you are having this much difficulty with simply installing Labview, somthing is very wrong. Uninstall everything and start from scratch. If you run into a problem, call NI. They will be able to guide you through whatever your problem is. I wish everyone would switch to Linux and abandon Windows. But it ain't gonna happen.

[Ray.R]

Thank (fill blank) for Unix / Linus / Solaris.

I have not yet had the pleasure of using NI sw on these pleasant platforms. But I have to agree with many comments that I read.

I think it is time that NI offers the products over DVD. Uncle Gates is already doing it with MSDN. However, since his Win-XtraProblematic OS... I am seriously being converted (again) towards Linus and such.

However, that being said, although lenghty, I haven't had many problems with NI product installations.

😄

[MEStech]

Actually we will need all the tools. What we are doing is moving towards LabVIEW as a standard base for all instrumentation in the future. Some people have used 6.x in the past and one new scientist is using 7.1 (he just received his yesterday, 4 CD's).

What I am doing is setting up a central workstation to make final applications to be put on the various pieces of equipment. One of the reasons for the Application builder. We will also be building applications to do post test processing, even though this isn't the best usage of LabVIEW. We will be developing some of our own drivers as well.

There is talk of getting a site licence and in the conversation, I mentioned the Linux version as part of the licence. The NI sales person thought that we could have a mix under the one licence. Here is hoping. 🙂

As I said in my previous post, I don't know what tools will be needed on this machine and I tried to install everything but I couldn't.

I will agree with the Windows sucks tone but I don't think this is truly a Windows issue but a installer design issue. I don't think it would be that hard to improve the installer to take into account the different packages by linking product number(s) to a standard install database. Heck each application or package could have a file similiar to the old Slackware install did. If I remember correctly with my aging memory, that the slackware installer you used to pick the packages to install and then the necessary floppies were asked for at the time. I do remember having floppies with letters and numbers depending if they were development, kernel, source or application. Heck even Windows 3.1 could work across different floppies.

I think even in the Paradox for Windows I had, it would open a selection box and I could pick which applications or modules I wanted to install.

As for DVD's or CD's. This isn't that big of an issue. The total install is less than 1.6 gigs that I can see. It would be easier and a much lower cost to just improve the installer.

If this thread is being monitored, hopefully something may come out of it.

Thanks for the tip Ed. I won't try any upgrade until I checked all the disks to make sure there is no changes. I find it strange that they send out a complete new set of disks all the time, even if there is no change. This makes me feel so much better. Now I can get into the testing phase and running through the tutorials. I am much happier. Now to go and see if there are any new windows upgrades.

Maybe someone could design an installer with LabVIEW to install LabVIEW. 🙂

[EdDickens]

---

Maybe someone could design an installer with LabVIEW to install LabVIEW. 🙂

---

This has already been discussed, at least to help with the extra toolkits. Maybe it's time to actually do something about it.

I've actually complained about the toolkit installers before, but I can't find the thread here at NI, but did find it in the LAVA forums. http://forums.lavausergroup.org/index.php?showtopic=369

Ed

[MEStech]

Replying to my own message.

On the new CD,s the LabWindows (I believe, another part of the building) was at 7.1.1. I inserted the disk and ran setup. It installed and it allowed me to install all the drivers that I couldn't install last time. No headaches other than needing to restart. I didn't check any of the other CD's though. I just wanted to try this.

[MEStech]

I took a look at the list. I am glad that we are all going to 7.1 from the start.