Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

NIDAQmx V6.31 on XPe

i am attempting to use the NIDAQmx driver V6.31 (Runtime 5) on an XPe system.  after installing the NIDAQmx driver i get the BSOD on the next reboot [IRQL_NOT_LESS_OR_EQUAL - STOP: 0x0000000A (0x08826840, 0x00000002, 0x00000000, 0x804EB3A9)].  Note: i have not added any NI hardware yet.
 
i have tested the same hardware and driver with XPpro and it functions correctly so i know that i have no hardware issues - just missing components in the XPe image.  the question is what?
 
i have run depends.exe on every DLL/SYS/EXE file i can find that NI installs and have resolved all missing DLL's i could find.  i have bloated my image with almost every component in the Software\System\System Services as well as many other components.  i still get the BSOD.
 
BTW i am not running the Explorer Shell but rather a custom shell that only runs my software.
 
any help or suggestions are welcome.
 
0 Kudos
Message 1 of 5
(3,719 Views)

Hi,

Unfortunately NI does not support our drivers on XP embedded OS neither LabVIEW. Embedded operating systems allow users to choose desired OS components to be installed and hence do not guarantee the presence of all the components required for running LabVIEW or DAQmx drivers.

Although I would like to add that it has worked for other customers but like I said we do not support it. Take a look at this discussion forum for more information.

I hope it helps

Jaime Hoffiz
National Instruments
Product Expert
0 Kudos
Message 2 of 5
(3,694 Views)

i actually posted the incorrect version of NIDAQmx - i am using V8.61.

i was debugging on the assumption that i was missing some XPe component.  it turns out i was running into a conflict between the NIDAQmx driver and the EWF.  without EWF engaged i have no problems with my system.  the second i engage EWF to create a disk overlay i get the BSOD on the next boot.  i have verified that the order of install makes no difference (EWF then NIDAQmx, or NIDAQmx then EWF - yes, i created an image without EWF then hacked it in manually).

so, what is the conflict?  i don't know.  using WinDbg it appears that initializing a DPC in some driver is where the system crashes.  i haven't figured out how to decipher the crash dump file further to analyze the root of the problem.

0 Kudos
Message 3 of 5
(3,652 Views)
Hey Kevin and all who are interested,

We have released DAQmx support for XP Emebedded and resolved the issue mentioned in this post. You can download the DAQmx Runtime 5 components for XPe here. To resolve the issue Kevin ran into you need to use the NI-PAL for EWF component, check out the documentation for details. If you need to install DAQmx in a pre-existing system with EWF, stay tuned: there is a registry fix for the Blue screen that I'll detail in a KB shortly.

Cheers,
Andrew S
MIO Product Support Engineer
National Instruments
0 Kudos
Message 4 of 5
(3,477 Views)
0 Kudos
Message 5 of 5
(3,439 Views)