niufurkw.sys

[Klecha]

We currently use USB-6229 OEM DAQ board. We have received a recent batch that display the following error on windows XP start-up:

"niufurkw.sys needed for NextTOINF"

Looking at the vendor ID and part ID there seems to have been a changed from VID_3923&PID_72E2 to VID_3923&PID_7254. We are running NIDAQ955f4Core drivers.

Has there been a firmware update that is causing windows to fail to recognise the device/load the correct drivers?

[Brad_K]

Hi Klecha,

In normal operation, the USB-6229 (OEM) has a Windows hardware ID containing VID_3923&PID_72E2. When DAQmx needs to upgrade or downgrade the firmware, it reboots the device into firmware updater mode, where the device shows up in Device Manager as a "USB Firmware Updater" and its hardware ID contains VID_3923&PID_7254. This should happen the first time you plug the device into a PC running a newer/older version of DAQmx than the last one it was plugged into.

However, you should not get a "niufurkw.sys needed for NextToINF" error. This sounds like an installation or deployment problem, not a hardware problem. Are you running Windows XP Embedded or some other variant (Professional, etc.)? If XP Embedded, how did you deploy DAQmx (via a custom image or by running the installer)? Were your previous devices plugged into a development PC at some point?

Brad

[Klecha]

Hi Brad,

we are running XP embedded. Each system has an SBC and DAQ. Each SBC has an identical image copied to it during production. This image was originally built with a different DAQ, so the XP image will have seen at least 1 other DAQ before.

We have built several of these systems without this issue. I assume this is a recent change?

The image had 9.2.2 core installer deployed on it (again, this was fine with all the other DAQ batches). Yesterday I tried installing 9.5.5, but it didn’t fix the issue.

What do I need to do to fix it? Are there any particular windows services that I need to enable?

Regards,

Steph

[Brad_K]

> we are running XP embedded. Each system has an SBC and DAQ. Each SBC has an identical image copied to it during production.
> This image was originally built with a different DAQ, so the XP image will have seen at least 1 other DAQ before.

Is this a Windows Embedded Studio image, built using a process similar to that described in Integrating NI-DAQmx Components into a Windows XP Embedded Image? Or was it created by running the DAQmx installer on the target and cloning the disk using Ghost, Acronis True Image, or similar?

> We have built several of these systems without this issue. I assume this is a recent change?

The USB-622x has had a separate PID for firmware update since support for the device was added in DAQmx 8.3 (mid 2006). The firmware update support was moved from nixsrkw.sys to niufurkw.sys in DAQmx 8.7 (early 2008).

The firmware version installed at the factory may be different between your two batches of devices. Ordinarily this is not a problem because DAQmx will automatically upgrade/downgrade as needed, but if your image is missing the firmware update code then that won't work.

> What do I need to do to fix it? Are there any particular windows services that I need to enable?

Disclaimer: I have never deployed Windows XP Embedded. I'm happy to answer questions about DAQmx, but I can't answer questions about using Windows Embedded Studio.

Since your image works with other USB-6229 (OEM) devices, I think we can probably rule out missing Windows services. Please check that these firmware update related files are installed:

%SystemRoot%\system32\drivers\niufurk.dll
%SystemRoot%\system32\drivers\niufurkl.sys
%ProgramFiles%\National Instruments\NI-DAQ\fpgaFiles\miousb\62xxfw.cfg
%ProgramFiles%\National Instruments\NI-DAQ\fpgaFiles\miousb\flashprg.cfg
%ProgramFiles%\National Instruments\NI-DAQ\staging\nimiousb\nicsrkw.sys
%ProgramFiles%\National Instruments\NI-DAQ\staging\nimiousb\nidaqui32.dll
%ProgramFiles%\National Instruments\NI-DAQ\staging\nimiousb\niemrkw.sys
%ProgramFiles%\National Instruments\NI-DAQ\staging\nimiousb\NIMIOUSBxpS.cat
%ProgramFiles%\National Instruments\NI-DAQ\staging\nimiousb\NIMIOUSBxpS.inf
%ProgramFiles%\National Instruments\NI-DAQ\staging\nimiousb\niraptrkw.sys
%ProgramFiles%\National Instruments\NI-DAQ\staging\nimiousb\nisdigkw.sys
%ProgramFiles%\National Instruments\NI-DAQ\staging\nimiousb\niufurkw.sys
%ProgramFiles%\National Instruments\NI-DAQ\staging\nimiousb\nixsrkw.sys

Note that this list of files is for DAQmx 9.5.5 and is subject to change in future releases. %ProgramFiles%\National Instruments\NI-DAQ\staging\nimiousb is a driver package which is normally registered using DIFxApp. If it wasn't getting registered you probably wouldn't get far enough for a "niufurkw.sys needed for NextToINF" error.

Brad

[Klecha]

Thanks Brad.

We solved the issue - our standard XP image has the DAQmx Core software installed on it. In order for the firmware/driver update, the DAQs need to be plugged into the full DAQmx build.

We have changed our procedures to plug all DAQs into a test set-up with the full DAQmx build installed, before installing in the final stripped down system.

Thanks a lot for your help.

Steph

[Brad_K]

Hi Steph,

> We solved the issue - our standard XP image has the DAQmx Core software installed on it. In order for the firmware/driver update, the DAQs need to be plugged into the full DAQmx build.

NI-DAQmx Core includes all of the files required for firmware update, and I have verified that it works correctly with Windows XP Professional, NI-DAQmx 9.5.5 Core, and a USB-6251. Unless your XP image is stripped down to include only a subset of NI-DAQmx Core, there might be something else going on.

> We have changed our procedures to plug all DAQs into a test set-up with the full DAQmx build installed, before installing in the final stripped down system.

>

> Thanks a lot for your help.

I'm glad to hear that you found a solution that meets your needs.

Brad