11-14-2006 06:13 PM
11-14-2006 06:34 PM
Ok, just saw the \NIDAQ830\Products folder in the extracted installer...
I would have thought I'd get the windows driver support by installing subpackage:
NI-DAQ_INF_files
but no such luck.. Installs fine but the windows driver wizard still doesn't pick up the installed device - must be getting close though (?)
Also: NIVcppCommon, NIVcppCommon2005, MStudioCommon, MStudioCommon2005 for the other support I suppose.
11-15-2006
03:00 PM
- last edited on
07-16-2025
08:42 AM
by
Content Cleaner
Hi Glyn,
There will more than likely be additional files necessary than just those included in the \NIDAQ830\Products\NI-DAQ_INF_files directory. If you are concerned with minimizing the installed components to only those you absolutely need, when going through the standard NI-DAQmx installation procedure you can customize the components that are installed. If you have not already seen this feature in the installer, please see the screenshot of the installation window in the NI-DAQmx installer that allows you to do the customization.
Did you originally have the NI-DAQmx Base drivers installed on this system for use with the USB-6009? If so and your USB-6009 is still not visible in MAX, it could be very likely that the device is still configured to use the NI-DAQmx Base driver. Please refer to the KnowledgeBase article here for more information on how to correct this.
Regards,
Andrew W
National Instruments
11-15-2006 04:16 PM
11-15-2006 04:19 PM
11-15-2006
04:23 PM
- last edited on
07-16-2025
08:42 AM
by
Content Cleaner
Hi Glyn-
If you do not require development support, you could consider using one of the NI-DAQmx Run-time Engine versions. Each version provides a successively smaller installer by removing certain driver features. More info about the specific features of each runtime version can be found on the download page.
Hopefully this helps-
11-16-2006 09:07 AM
Hi Tom,
Thanks for the info regarding the Runtime versions of the DAQmx sofware. Definitely better suited for deployment than the development package but at 180+mb are still a pretty big and cumbersome.
I'd still rather be able to install the windows driver for my hardware independentally of 100s of MBs of application software (as is possible with most other windows-compatible hardware). Though in the absence of a solution of this nature (or at least until I get around to hunting through the CABs and MSIs) I guess I'll go with the RT packages.
Thanks again for your assistance,
Glyn