ISSUES with building DIO_EX1 DDK EXAMPLE

Question

Hello !
I am trying to compile,link and execute the DIO_EX1 program that is part of the device driver kit. I am using Visual C++ 6.0 as my compiler, developing on WINDOWS XP, and want to run the program to access the registers on the installed AT-DIO-32HS card. Looking through the documentation, I am a bit confused over the files I need to include.
Currently I include osibus.h, ositypes.h, tdio.h, and tstatus.h.   I get LINK errors saying it is unable to resolve the functions "releaseBoard()" and "acquireBoard()"  ( + a couple others).   I see several osiXXX.cpp files, and I am unsure which one to include in project. In addition, do I need to #define osiVISA ? 
Hopefully this will be easy to resolve.
Thanks !

Answer 1

I am not using the NI-DAQ driver because after extensive testing and communication with another NI engineer, it was concluded that I could not meet my application's timing requirements with the driver of the AT-DIO-32HS card, or with any NI CARD, for that matter. So I thought I would try RLP programming to see if I could achieve better timing than I experienced with the driver. The protocol between the application and the peripheral is pretty simple. The application simply outputs a continuous series of sets of 32 bit values to the peripheral until a user terminates this via the GUI. So...
1. User starts program
2. Program waits for a REQUEST signal to go high from peripheral to indicate the peripheral  is ready to receive data
3. Program raises an ACK line to tell the peripheral it is ready to send data
4. Program places a value on data lines, and pulses another SIGNAL high to indicate to the peripheral that data is valid on data lines
5. Repeat step 4 about 500 times
6. Program LOWERS THE ACK line to indicate it is complete with this set of values
7. Goto step #2
The original programmer of this application used the AT-DIO-32F card, but did not use its' driver. Instead, he used a software library created by ZEALSOFT to DIRECTLY access the registers of the 32F card. He was able to implement the above protocol and meet the timing requirements simply by programming the registers.
Well, the problem is that the 32F card is now obsolete. I had hoped that I could update to the 32HS card and still use the same original application (that uses the ZEALSOFT library). But it did not work. I compared the actual registers of the 32F to the registers of the 32HS and found it much different, and I would not have a clue how to program the 32HS registers at the lowest level without LOTS of help. So I thought I would attempt RLP programming using the NI DDK.  But it seems now I am running into the problem that the current DDK examples will not work on an AT-based card.
Soooo... I have the following options:
1. Implement another iBus object  for the 32HS AT interface/card and use RLP programming
2. Upgrade to a PCI-based card and use RLP programming
3. Try to directly program the 32HS registers using the ZEALSOFT library. But the 32HS card has about 117 registers compared to the 20 or so on the 32F card.  Probably not a good idea (which is why I attempted to use the RLP DDK classes)
4. Scrap trying to use a NI card and instead try an FPGA -based solution.
Any ideas ?   Anything would be helpful.
Thanks so much !