Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Keywords: BinaryEODset DllCall
Can someone explain why this is so?
However when a DllCall stores data into a binary buffer, it is a safe bet that whatever function was DllCall'ed does not know how to update the BinaryBuffer EOD number.
Thus, before you can access the data stored by a dllcall in the binary buffer, you must manually set the EOD number to a value large enough for you to access the data. I usually set it to the same size as the binary buffer.
Article ID: W15137
File Created: 2012:10:22:13:49:56
Last Updated: 2012:10:22:13:49:56