none
LabWindows/CVI 7.0 Device Driver Installation in Windows XP Mode

    Question

  • I am attempting to upgrade a legacy Automated Test Equipment (ATE) system host PC to Windows 7 (from Windows XP).  However, I have found that the COTS application version I need to use is not supported by Windows 7 and will not install.  So, I am attempting to use Windows XP Mode because I have no problems installing my applications on Windows XP.

    During the installation of the Device Drivers for National Instruments LabWindows/CVI version 7.0 (I did say it was a legacy system), I get, "Fatal Error. A failure has occurred in NISystemInfo." message with the below information.

    My fear is that Windows XP Mode does not handle device driver additions/modifications well.  Can anyone confirm or provide other ideas of what is causing this?

    K:\NIInstallers\dev\1.1.2\src\UberInstaller\UberInstaller.cpp(1296): IInstallerError 10014
    Fatal Error. A failure has occurred in NISystemInfo.
    CoLoadLibrary failed on C:\DOCUME~1\XPMUser\LOCALS~1\Temp\nii81.tmp

    Exception code: E06D7363 ()
    Fault address:  7C812AFB 0001:00011AFB C:\WINDOWS\system32\kernel32.dll

    Registers:
    EAX:00DAF954
    EBX:00000000
    ECX:00000000
    EDX:7C97E140
    ESI:00DAF9E4
    EDI:00DAF9E4
    CS:EIP:001B7C812AFB
    SS:ESP:002300DAF950 EBP:00DAF9A4
    DS:0023 ES:0023 FS:003B GS:0000
    Flags:00000206

    Stack Trace
    Address  Frame    LogicalAddr    Module    SymbolName + Offset
    7C812AFB 00DAF9A4 0001:00011AFB C:\WINDOWS\system32\kernel32.dll RaiseException + 82
    004C3160 00DAF9E4 0001:000C2160 D:\setup.exe
    00465FE7 00DAFB60 0001:00064FE7 D:\setup.exe
    00465DD1 00DAFB7C 0001:00064DD1 D:\setup.exe
    0043FD52 00DAFCDC 0001:0003ED52 D:\setup.exe
    00463C4B 00DAFD84 0001:00062C4B D:\setup.exe
    00463D46 00DAFDA8 0001:00062D46 D:\setup.exe
    0046B4A1 00DAFDF0 0001:0006A4A1 D:\setup.exe
    0046B55E 00DAFF18 0001:0006A55E D:\setup.exe
    004EB185 00DAFF80 0001:000EA185 D:\setup.exe
    004C8EED 00DAFFB4 0001:000C7EED D:\setup.exe
    7C80B729 00DAFFEC 0001:0000A729 C:\WINDOWS\system32\kernel32.dll GetModuleFileNameA + 442

     

    Wednesday, March 16, 2011 8:19 PM

Answers

  • Unless your device is NI USB, XP mode won't see it.

    My understanding of the NI stuff is that its a PCI or ISA card on the host PC, correct?  The ISA/PCI bus on the host is not accessible to a virtual machine running in VPC or any other VT program.

    Wednesday, March 16, 2011 8:49 PM
  • Your fear is well founded.  It depends on how a device attaches to a computer as to whether it can be used in a virtual machine.  The devices in a vm are emulated and cannot be changed.  If you can use usb you can use an external device but if your device requires a card slot in the host you have no chance of installing a device driver for it in a vm.  A vm does not detect the device so trying to install a driver for it is pointless.
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Wednesday, March 16, 2011 8:50 PM

All replies

  • Unless your device is NI USB, XP mode won't see it.

    My understanding of the NI stuff is that its a PCI or ISA card on the host PC, correct?  The ISA/PCI bus on the host is not accessible to a virtual machine running in VPC or any other VT program.

    Wednesday, March 16, 2011 8:49 PM
  • Your fear is well founded.  It depends on how a device attaches to a computer as to whether it can be used in a virtual machine.  The devices in a vm are emulated and cannot be changed.  If you can use usb you can use an external device but if your device requires a card slot in the host you have no chance of installing a device driver for it in a vm.  A vm does not detect the device so trying to install a driver for it is pointless.
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Wednesday, March 16, 2011 8:50 PM
  • Hello Madala,

    Did you ever get the drivers installed?  I am attempting the same installation with the same driver versions in XP mode on Win7 64-bit, and I'm getting the same installation failure.

    For others on this thread, although the actual devices may not be usable, the driver framework needs to be present to satisfy linkages.

    Let me know if anyone has been successful.

    Regards,

    Chris Norris

    Thursday, January 12, 2012 12:28 AM