Write error in the log file

[Roadagent]

Peter, I'm trying out FSUIPC. I'm very interested in your product. My problem is I've downloaded a copy FSUIPC 3.75 to evaluate and I'm getting the following repeated in the log file. I'm only logging IPC reads and writes at the moment.

178891 READ0 3304, 4 bytes: 02 00 00 00

178891 READ0 3308, 4 bytes: 02 00 00 00

178891 WRITE0 (failed, read-only!) 330A, 2 bytes: B0 04

Any suggestions?

[Pete Dowson]

Peter, I'm trying out FSUIPC. I'm very interested in your product. My problem is I've downloaded a copy FSUIPC 3.75 to evaluate and I'm getting the following repeated in the log file. I'm only logging IPC reads and writes at the moment.

178891 READ0 3304, 4 bytes: 02 00 00 00

178891 READ0 3308, 4 bytes: 02 00 00 00

178891 WRITE0 (failed, read-only!) 330A, 2 bytes: B0 04

Any suggestions?

Yes: the first two lines show that either the code signature failed (look at the top of the log) or you are using an illegal key. In the latter case please immediately delete your FSUIPC.KEY file.

And ignore that "error". It is deliberate so that I can tell the version of the FSUIPC SDK library being used -- the library code writes its version number to a read-only location to force an entry in the log. 04B0 = version 1.200.

BTW later (interim) versions are often available in the Downloads announcements above, if you want to keep really up to date.

Pete

[Roadagent]

Thank you so much. I want to finish up looking FSUIPC over today. It looks great so far. Look forward to a new customer!! Me!! :)