jdgordon Posted June 20, 2005 Report Posted June 20, 2005 gday, ive been playing with the c example program for a bit and it works great, however im trying to make a plugin for another program but when i try connecting to fsuipc from that dll FSUIPC_Open fails with error 13? (the fact that its not registered makes no difference, my dll isnt even mentioned in the FSUIPC.log file :( ) i thought maybe it doesnt like being called from a new thread, so i copyed all the relevant code across to the test exe and it works fine. is this a known problem? (i see Pete wont be back for a few days, but im hopeing someone else would have an idea)[/url]
Pete Dowson Posted June 22, 2005 Report Posted June 22, 2005 ive been playing with the c example program for a bit and it works great, however im trying to make a plugin for another program but when i try connecting to fsuipc from that dll FSUIPC_Open fails with error 13? 13? Data error? That's a result when the data in the memory-mapped file passed to FSUIPC contains un-interpretable data. sounds like something is wrong with the way the data are is created. (the fact that its not registered makes no difference, my dll isnt even mentioned in the FSUIPC.log file :( ) Switch on IPC read/writer logging just to checkHowever, if the memory-mapped file atom number is wrong then FSUIPC won't even be able to identify the program to log it. is this a known problem? No, not at all. There are many programs with FSUIPC access split into DLLs. For external programs threads and DLLs make no difference whatsoever to the interface -- only the Process matters. I think you'll need to use a debugger to see what you are doing wrong. Sorry, I cannot debug your code from here. Regards, Pete
jdgordon Posted June 22, 2005 Author Report Posted June 22, 2005 :( ok thanx for that ill have a play and see if i can figure it out. is it possible it could be a compiler setting that needs being set? (im using vis studio 2003 and coding in c (and have it set to compile as c code))
Pete Dowson Posted June 22, 2005 Report Posted June 22, 2005 is it possible it could be a compiler setting that needs being set? (im using vis studio 2003 and coding in c (and have it set to compile as c code)) I wouldn't have thought so, but that area is a black art to me as well. Sorry. Regards, Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now