Hello, My last 2 flights resulted in runtime error 75, i noticed that it happen right after or because of, trying to pass coms to Otto ?I use Vista 64 and RC in network with WideFS, i run as an administrator, my FLT/wx is well configured...I forgot to take a log... any ideas ?Thanks!Alain from Montreal

You need to describe the operating system on both your host (FS) and client (RC) computers, FX version, etc.You post mentions your last two flights. Did Otto comms work before? Anything changed?On the RC computer, you should be an running as an admin user and also have created a shortcut to RC4 with the property to run as admin set. FS should be started the same way on its computer as well as WideClient.exe.http://www.schiratti.com/dowson.html is where you get the current release versions of FSUIPC and WideFS. Alse get the current makerws.Also checked the pinned topic regarding error 75 at the top of this forum. While you may not have Kapersky you might have another security system including VISTA itself that you need to trust the WideFS, WideClient, RC4, and you running over the network.Check through this post regarding file/folder access writes over a network.http://forums1.avsim.net/index.php?showtop...;error+75\You need to insure that all you host and client shares are set up.Try this until someone more knowledgeable replies. These are just generic ideas. Error 75 is a folder/file access problem.

Yes, Otto worked for 3 flights before, i haven't change anything on both computers (running vista 64 on both) and i am running RC as an administrator;I downloaded the makerways and ran it again just in the case before the last flight since it was not down from when i installed the network on saturday morning.Is it possible that, by starting RC BEFORE Wideclient (not the start button but the program itself) or FSX could cause that ?Alain from Montreal

ok, I started ASA, then FSX, Wideclient and finally RC; started the flight, was clear for take off, at about 1500 agl, i switched coms to Otto, fine, a minute later i tried to switch commands to Otto, runtime error 75.....will get a log.Alain from Montreal

ok, I started ASA, then FSX, Wideclient and finally RC; started the flight, was clear for take off, at about 1500 agl, i switched coms to Otto, fine, a minute later i tried to switch commands to Otto, runtime error 75.....will get a log.Alain from Montreal

the .flt/.wx path on the fs machine, has to be shared, with write permissions, and you have to specifiy the share as the .flt/.wx path on the rc machine.

Thanks for responding JD;As i replied to you on email earlier, i had check FSUIPC Autosave option earleir this week, that is about when i had problems with RC; at my lunch break, i started a flight with that option uncheck and sure enough, RC behaves normally and accepted Otto with coms and control of the plane.Will check tonight if flight plan folder is shared, i know the path is correct for FLT/WX.Alain from Montreal

Thanks for responding JD;As i replied to you on email earlier, i had check FSUIPC Autosave option earleir this week, that is about when i had problems with RC; at my lunch break, i started a flight with that option uncheck and sure enough, RC behaves normally and accepted Otto with coms and control of the plane.Will check tonight if flight plan folder is shared, i know the path is correct for FLT/WX.Alain from Montreal

the path may be correct, but i can't write to a network path. i can only write to a network share.