OK apologies before I start on this one - if I have missed the obvious place that it is documented in then just point me If it is in the c++ documentation for fsuipc then I don't have it here in Florida and I can look at it when I get back to the UK as I only brought the Visual Basic with me. I have looked in the programmers guide which is great for identifying the offsets etc but the urls shown for further info seem to be dead.
I am trying to get my feeble mind around how the interface works. I understand C++ a little, Visual Basic a lot, but I use another flavor of Basic (REALBasic). I have converted the Visual Basic program into my version and have a working interface so that I can read and write data to and from FS using FSUIPC. I am not at all sure how it works though. I understand the concept of creating a filemapping object pointing at memory (I think) and that I can make read and write requests which I then process using the process routine (which uses windows messaging?). However somewhere in the middle of all this the miracle happens and that I have not gotten to the bottom of yet. I can see that the read request sets up a header and space after it to hold the returned data. A write request sets up a write header and the data to be sent. The process routine then executes the read and write and the read data ends up in the memory after the read request.
At the moment the class I have for FSUIPC exposes all it's methods and properties as public. What I am trying to do is firstly understand at a more pseudocode level how things happen.
Any pointers (no pun intended :wink: ) much appreciated