Device Drivers Download Installation Issue

[AKA_TG]

I am unable to download and then install device drivers from Feb 2013 or any of the newer ones for that matter.

When I download and try to execute the file

dcd_feb_13_1.exe

The self extracting zip file (with an icon 7z SFX)  extracts and promises to launch the installer, but it does not.

The downloaded file then dissapears.(This part I cannot believe. It is sooo annoying!)

When I go to look at the unzipped image all is there except the root install setup files (huh?)

Why is this still happening since 2012?

I have been unable to get access to device drivers since Aug 2012 and I have had this issue on two different machines.

Does anyone here have a clue?

Thank You

[chembo]

This is probably related to your system settings, anti-virus software, or something else ... 🙂

But I suspect that on the same download page (NI Device Drivers February 2013 - Windows), in the Supporting files section, the 501667N-01M_2013Q1_RC2_NIDeviceDrivers.iso is actually an ISO image of the drivers DVD. You could download it, burn to DVD and install from there.

And this file (DCD-FEB13.zip) is maybe the ZIP version of the self-extracting drivers download. This may help also, if you have problems with the executable file.

[AKA_TG]

Thanks for reply chembo,

I can appreciate that it may be a virus protection feature of my machine.

I am attempting to download the zip file now 

DCD-FEB13.zip

I Will report back if I find anything worthy of note.

[AKA_TG]

While this file downloads I am attempting a different kind of work around to get these drivers installed.

I do have LV2014 DVD's but always shy away from installing device drivers directly from DVD as it earlier versions it would not allow me to create user installers

from my project file without dependency issues popping up (Asking for DVD's or install paths etc).

WHen I install Device Drivers from an on-line image it seems easier to make installers later on if I need to. I do not know exactly why this is the case.

I also do not know if it is different today and I really do not have lots of time to try out all these other approaches to get the machine the way I am used to using it.

What I am attempting to do is to transfer the Device Driver files from the DVD's into an image on the HD so that I can install from the HD and not from the DVD's. I hope someone alse has done this successfully.

Please let me know if this will not work.

Most appreciated.

[chembo]

I remember creating DVD ISO images win ImgBurn. It works pretty good.

Then you could use Virtual CD-ROM Control Panel to mount the image as virtual drive. I didn't try it until now, but it should work.

[AKA_TG]

What I have found out is the following..

LabVIEW version 2014 and version 2010 will not co-exist on the same machine because the device driver set for 2014 does not support LabVIEW 2010 and the device driver set for 2010 does not support LV 2014. It only supports up to LV 2012.

I find this quite surprising.

If I got this wrong someone tell me Thanks.

I have stayed with LV 2010 for years now because it has been a stable and predictable version.

Long experience has told me to stay put and not upgrade until I absolutely have to.

But, I really did want to try out LV 2014 so I am essentially stuck with taking a big leap to keep up.

Again , if I somehow have this backwards someone let me know where my mistake is.

Thanks in advance

[Dennis_Knutson]

It should not be surprising that an older driver set does not support a version of LabVIEW that was not written yet. This has always been the case. You are incorrect, though that the 2014 driver set does not support LabVIEW 2012. Can you provide specifics on the sort of error you see?

[chembo]

---

@AKA_TG wrote:

What I have found out is the following..

LabVIEW version 2014 and version 2010 will not co-exist on the same machine because the device driver set for 2014 does not support LabVIEW 2010 and the device driver set for 2010 does not support LV 2014. It only supports up to LV 2012.

I find this quite surprising.

If I got this wrong someone tell me Thanks.

I have stayed with LV 2010 for years now because it has been a stable and predictable version.

Long experience has told me to stay put and not upgrade until I absolutely have to.

But, I really did want to try out LV 2014 so I am essentially stuck with taking a big leap to keep up.

Again , if I somehow have this backwards someone let me know where my mistake is.

Thanks in advance

---

According to this link, this is correct: DAQmx and LabVIEW Version Compatibility. At least because of the DAQmx compatibility. I think this affects mainly development machines.

We made also a pretty big jump from LabVIEW 7.1 to 2011 and then pretty quick to 2013. The latter was easy, but 7.1 to 2011 forced us to have some dual boot systems in production because of the DAQmx drivers. We were using also a virtual machine for the older LabVIEW version on the development PCs.

Well, too late, but two days ago accidentally we figured out that software converted from 7.1 to 2013 and compiled on the development PC (LabVIEW 2013, DAQmx 9.8) works just fine on a test fixture with DAQmx 8.7.2. This doesn't suppose to work according any of the compatibility lists. We are not using any fancy DAQmx functionality, just acquiring tasks on demand, but it works. If we knew about it earlier, we could save a lot of time and effort.

It seems also that programs compiled in LabVIEW 7.1, DAQmx 8.7.2 work on test fixtures with DAQmx 9.8, but I have still to run some testing in order to confirm it. I was about to post about it later in the forums. This is now just preliminary announcement 🙂

[Dennis_Knutson]

Sorry, I misread what you said. I just saw your reference to 2012 and missed that you are actually using 2010. Yes, compatibility is limited and virtual machines are a good solution. Upward compatibility is almost always fine so the successful running of 9.8 does not surprise me.