Hi Ken,
lvdaq.dll is undocumented because it is used only internally by LabVIEW. It might be better to use ni-daq instead, as the API should remain stable and be well documented. The lvdaq.dll may change at any time, or even be completely replaced in the future.
This is how I figured out the arguments:
Write a LabVIEW application that does what you want, for example using the "write to digital port.vi." Double-click the VI to load the block diagram. You will find that it has a "Port Config" and "Port Write" VI. Double click the "Port Config," the block diagram will have a Call Library Function node, right click and choose "configure."
You will see almost everything you need, like the function name (DIO_Port_ConfigInterface), cal
ling convention, number of parameters, etc. In this case they are all pointers (so you know how the stack should be built/destroyed). Close that window and look at the data types being wired to the CLF, and you'll be able to figure everything out.
Do the same for any other functions you may want to use.
Good luck!