Aslan Posted January 21, 2014 Report Posted January 21, 2014 Hi Pete, I have the lastest version of WideClient (& FSUIPC) running on a laptop W7 connected to a home network. I need to use the program to allow FSIP200X to access another W7 computer running FSX. Since I only use the setup every six months or so, I don't know what has changed since I last used this setup. Six months ago with both computers talking to each other just fine with this setup. The laptop displays the message at the top of the wideClientFS98 Eliminator window "waiting for a connection". At the top of the FSX window it displays "Microsoft Flight Simulator X with WideServer: waiting for clients" What "services" doesFSX/WideClient use for the process? I useUniblue "speedupmypc" to speed up the system every now & then & often notice that it disables some "services" to improve performance. I have to occassionally go back and start up certain "services" & change properties etc. Thanks Aslan
Pete Dowson Posted January 21, 2014 Report Posted January 21, 2014 I have the lastest version of WideClient (& FSUIPC) running on a laptop W7 connected to a home network. I need to use the program to allow FSIP200X to access another W7 computer running FSX. I don't know FSIP200X. I take it that it is an FSUIPC application? The laptop displays the message at the top of the wideClientFS98 Eliminator window "waiting for a connection". At the top of the FSX window it displays "Microsoft Flight Simulator X with WideServer: waiting for clients" There are logs -- WideServer.log on the Server and Wideclient.log on the client. You need t show me those. Paste them into a reply here. What "services" doesFSX/WideClient use for the process? Those services needed for Windows to support Networking and networked compute recognition, whatever they are. I expect it depends how you've configured WideFS. Have you read the section in the user guide about configuring your network, the part which starts with a strong red suggestion that you read at least part of it? Regards Pete
Aslan Posted January 21, 2014 Author Report Posted January 21, 2014 Hi Pete, Thanks for the reply. I managed to find the probable cause - the workgroup name on the PC running the FSX had been somewhere along the line changed by 1 character, hence not common workgroups etc. Problem seems to have been resolved. thanks kind regards Aslan P.S. FSIP200X is an instructors panel "program" for FSX/FS2004 similar to the flight instructor panel in FS2002. Useful for simulating V1 cuts etc.
Pete Dowson Posted January 21, 2014 Report Posted January 21, 2014 Thanks for the reply. I managed to find the probable cause - the workgroup name on the PC running the FSX had been somewhere along the line changed by 1 character, hence not common workgroups etc. Problem seems to have been resolved. Okay. The other way around that is to provide the ServerName and Protocol parameters in the WideClient.INI file. Then it isn't dependent on the Broadcast messages which don't operate over different workgroups. P.S. FSIP200X is an instructors panel "program" for FSX/FS2004 similar to the flight instructor panel in FS2002. Useful for simulating V1 cuts etc. Hmm. Another one. I'll take a look at that. 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