Problems with bus access

[Bonhomme]

Okay, last question,

In response to my previous question, I think the greater problem is not the fact that the window doesn't close. When running the external program in LabVIEW, SystemExec.vi says that it's having a problem accessing the PCI devices. So, my question is whether LabVIEW keeps the executable in some type of "envelope" so that it can't access what it needs to? How can I get out of it? Thanks again.

[Ben]

Hi Bonhomme,

If you go to a DOS prompt, does the command work?

Ben

[Bonhomme]

Hi Ben,
Yes, if I go to a regular DOS prompt or just double click and run the program from Windows, it works just fine. But it can't access the device when I run the program inside LabVIEW.

[Greg_McKaskle2]

> Yes, if I go to a regular DOS prompt or just double click and run
> the program from Windows, it works just fine. But it can't access the
> device when I run the program inside LabVIEW.


I don't think this is because the DOS program is run from LV. LV is invoking
the DOS program much the way a batch file does. It is asking the OS to run
another task.

More likely, it is because the device is also being accessed from some VI
already running. Does the DOS device have sole access to the HW? You may
want to make a simpler example, just one VI that calls the executes the DOS
prompt to test it.

Greg McKaskle

[Bonhomme]

Hi Greg,
Unfortunately, I did create a VI that ONLY invokes the DOS program and the results are still the same. The DOS program I'm running interrogates the PCI bus to get information about the PCI devices in the computer. You know, like base address, vendor ID and the like. I don't see why there would be any conflict. Hmm..... ?