problem installing NI drivers in XPMode on Win7 64-bit

[clnorris]

Good evening,

I'm attempting to install the NI Device Drivers from May 2003 that shipped with LabVIEW 7.0.  I'm trying to install in an XPMode instance running on Windows 7 (64-bit).  This is for maintenance of legacy applications.

LabVIEW itself installed successfully, but the driver setup immediately failed with a message "Fatal Error. A failure has occured in NISystemInfo."  The error dialog also contained this information:

K:\NIInstallers\dev\1.1.1\src\UberInstaller\UberInstaller.cpp(1248): IInstallerError 10014
Fatal Error. A failure has occurred in NISystemInfo.
GetProcAddress failed on DllGetClassObject

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

Registers:
EAX:0115F998
EBX:00000000
ECX:00000000
EDX:7C97E140
ESI:0115FA28
EDI:0115FA28
CS:EIP:001B7C812AFB
SS:ESP:00230115F994 EBP:0115F9E8
DS:0023 ES:0023 FS:003B GS:0000
Flags:00000206

Stack Trace
Address Frame LogicalAddr Module SymbolName + Offset
7C812AFB 0115F9E8 0001:00011AFB C:\WINDOWS\system32\kernel32.dll RaiseException + 82
004BFD20 0115FA28 0001:000BED20 C:\Documents and Settings\XPMUser\Desktop\DRIVERS\setup.exe
00463ADD 0115FBA4 0001:00062ADD C:\Documents and Settings\XPMUser\Desktop\DRIVERS\setup.exe
00463871 0115FBC0 0001:00062871 C:\Documents and Settings\XPMUser\Desktop\DRIVERS\setup.exe
0043EDC2 0115FD14 0001:0003DDC2 C:\Documents and Settings\XPMUser\Desktop\DRIVERS\setup.exe
00461BB3 0115FDBC 0001:00060BB3 C:\Documents and Settings\XPMUser\Desktop\DRIVERS\setup.exe
00461CA6 0115FDE0 0001:00060CA6 C:\Documents and Settings\XPMUser\Desktop\DRIVERS\setup.exe
00468D01 0115FF18 0001:00067D01 C:\Documents and Settings\XPMUser\Desktop\DRIVERS\setup.exe
004E7BC3 0115FF80 0001:000E6BC3 C:\Documents and Settings\XPMUser\Desktop\DRIVERS\setup.exe
004C593D 0115FFB4 0001:000C493D C:\Documents and Settings\XPMUser\Desktop\DRIVERS\setup.exe
7C80B729 0115FFEC 0001:0000A729 C:\WINDOWS\system32\kernel32.dll GetModuleFileNameA + 442

I have some questions for NI or anyone else who's been through this:

(1) Is there any way to force the May 2003 drivers to install in XPMode?

(2) If that's not possible, will any of the NI driver collections install in XPMode?  If yes, what is the mininum version?

(3) What is the latest NI driver collection that would still work with LabVIEW 7.0?

Thanks for the advise!

Chris Norris

[smercurio_fc]

Installation of device drivers in XP mode is not supported. While you can use XP Mode to run previous versions of the LabVIEW software (as I do), it won't work for low-level drivers. You will need to either update your applications or use another computer that has an older operating system installed.

[clnorris]

Thanks for the feedback.  I wonder if newer installers will have any degree of compatibility.

I saw on another page that people are at least getting some 488.2 functionality in XPMode:

http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/NI-488-2-does-work-on-Windows-XP-Mode-within-...

In some cases, I don't necessarily need physical access to the hardware.  I just want to satisfy dependencies for linkage when running application builder, CVI, etc.  I know I can manually copy VI's, headers, etc. but that's a pain.

[-lucho-]

Hello thanks for posting!

Definitely smercurio is correct, the device drivers other than LabVIEW  do not work in a simulated environment as XP mode is.
Also as general information when using  virtual machines your DAQ devices might not be recognized unless they are USB devices. 

Regards, 

Luis A

Applications Engineer.

National Instruments.

[smercurio_fc]

---

@clnorris wrote:

Thanks for the feedback.  I wonder if newer installers will have any degree of compatibility.

---

The issue isn't the installers, but the fundamental way that XP Mode works: it's a simulated environment. Hence, hardware drivers will not work properly since there is no actual hardware.

While you can copy the DAQ VIs, those VIs also use shared libraries. On Windows these would be DLLs. You'd need to place all of the DLLs in the appropriate locations, and I'm not sure if that will even work.