Simple VI App constantly accesses hard drive.

[ikiller]

I used an example script as a building block for analog triggered 4 channel A to D on a PCI 4462 card.

When the application is running (either as a vi in labview, or a built application using the runtime engine), the hard drive access light is almost constantly on.  I am a bit concerned about this as we are using  compact flash memory as an ide hard drive and thus we have a limited number of read/writes.  Why would the app be accessing the hard drive so much while waiting for a trigger??  Is there anything I can do about this from software point of view.  This is labview 8.2 on RedHat Linux Enterprise 3, and using NIdaqmx.  I was thinking that I could also make it run off of a virtual drive in RAM, but I don't know what part of the file system it is accessing.  If I at least knew what part of the filesystem it was reading and writing I would know what parts to place into RAM.

 Any help or advice would be greatly appreciated.


   Mario

[Pnt]

---

Mario wrote:
I am a bit concerned about this as we are using  compact flash memory as an ide hard drive and thus we have a limited number of read/writes. 

---

This is not true.

You have a limited number of writes, but unlimited number of reading.

Your application simple reads the program to be executed and that's why the led is on.

You should just control the number of writing to hard drive, in your program.