CDreier Posted November 9, 2009 Report Share Posted November 9, 2009 I can't get WideFS/FSX (FSUIPC) to communicate. Both computers are running Win7 64-bit. FSX runs on its own drive (E:) while fsx.cfg and most everything else is on the C: drive. Here's the WideServer log - there's no WideClient log: ********* WideServer.DLL Log [version 7.53] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 09/11/09, Time 14:31:02.487: Server name is CORSAIR 15975 Initialising TCP/IP server 15975 Initialising IPX/SPX server 15975 IPX/SPX socket() failed [Error=10044] Socket type not supported 15975 Failed to start IPX/SPX Server 15975 Initialising UDP/IP server 16115 Broadcasting service every 1000 mSecs 32823 Closing down now ... Memory managed: Offset records: 13 alloc, 12 free Read buffer usage: 0 alloc, 0 free, max in session: 0 Write buffer usage: 0 alloc, 0 free, max in session: 0 Throughput maximum achieved: 0 frames/sec, 0 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec ********* Log file closed ********* Here's the WideFS.ini file: ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] ServerName=Corsair Protocol=TCP Port=8002 Window=43,44,886,589 Visible=Yes ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== There's just nothing happening and I can't figure it out. Help or ideas, please. Thanks. Link to comment Share on other sites More sharing options...
CDreier Posted November 9, 2009 Author Report Share Posted November 9, 2009 One other thing.... in checking my install log for FSUIPC it appears that it couldn't find my fsx.cfg. I can post the log if you like. Thank you. Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 10, 2009 Report Share Posted November 10, 2009 I can't get WideFS/FSX (FSUIPC) to communicate. Both computers are running Win7 64-bit. FSX runs on its own drive (E:) while fsx.cfg and most everything else is on the C: drive. Here's the WideServer log - there's no WideClient log: The server is fine. If there's no WideClient log then you haven't run WideClient, which explains why it cannot talk to the server. You need the client program running in the client else they cannot talk to each other! :roll: There's just nothing happening and I can't figure it out. Help or ideas, please. Thanks. Why not try running the WideClient program on the client PC? If there's a problem then, show me the client log file. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 10, 2009 Report Share Posted November 10, 2009 One other thing.... in checking my install log for FSUIPC it appears that it couldn't find my fsx.cfg. I can post the log if you like. Thank you. If the installer couldn't find the FSX.CFG file it couldn't have found or created the DLL.XML file and so FSUIPC4 couldn't have been loaded by SimConnect. If FSUIPC4 isn't loading then WideServer cannot run, which you seem to have disproved by posting its log. Pete Link to comment Share on other sites More sharing options...
CDreier Posted November 10, 2009 Author Report Share Posted November 10, 2009 First off, thanks for helping me with this. It appears that WideClient is running. It is in its own folder on the client machine along with WideClient.ini. The .exe is 50kb and .ini is 1kb. When I enable it, Task Manager shows it's running as "WideClient FS98 Eliminator - Waiting for a connection" using 8020k of memory. Yet, there's no connection! Here's my install log: Installer for FSUIPC4.DLL version 4.53 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... Looking in registry for ESP install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"AppPath" ... NOT found! ... =========================================================== INSTALLATION FOR FSX: AppPath="E:\Program Files\Microsoft Games\Flight Simulator X\" Checking version of FSX.EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: E:\Program Files\Microsoft Games\Flight Simulator X\Modules\FSUIPC4.DLL ... Version 4.530 found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "E:\Program Files\Microsoft Games\Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Chuck\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\Chuck\AppData\Roaming" Found FSX.CFG in "C:\Users\Chuck\AppData\Roaming\Microsoft\FSX\FSX.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Chuck\Application Data\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Contacts\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Cookies\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Desktop\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Documents\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Downloads\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Favorites\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Links\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Local Settings\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Music\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\My Documents\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\NetHood\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Pictures\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\PrintHood\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Recent\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Saved Games\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Searches\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\SendTo\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Start Menu\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Templates\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Tracing\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Videos\Roaming" No FSX.CFG there Now installing additional files into the Modules folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX controls.pdf" okay Installed "GlobalSign Root.exe" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Example LUA plugins.zip" okay FSUIPC4.DLL installed and signature checked out okay! Deleted GlobalSign Root fix programno longer relevant =========================================================== All installer tasks completed okay! Registration for WideFS was successful! (result code 00) *************** End of Install Log *************** Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 10, 2009 Report Share Posted November 10, 2009 It appears that WideClient is running. It is in its own folder on the client machine along with WideClient.ini. The .exe is 50kb and .ini is 1kb. When I enable it, Task Manager shows it's running as "WideClient FS98 Eliminator - Waiting for a connection" using 8020k of memory. Yet, there's no connection! You need to show me the WideClient.log file, from the same folder. WideClient ALWAYS produces a log -- it is the first thing it does when started! The FSUIPC4 install log shows that was installed okay, but we already knew that. Pete Link to comment Share on other sites More sharing options...
CDreier Posted November 10, 2009 Author Report Share Posted November 10, 2009 There is not a wideclient.log in either the FSX\modules on the server computer or in the WideFs directory on the client machine. I'm at a loss. Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 10, 2009 Report Share Posted November 10, 2009 There is not a wideclient.log in either the FSX\modules on the server computer or in the WideFs directory on the client machine. I'm at a loss. There's no point looking on the Server PC for a Client log. The client runs on the other PC, not the Server! WideClient cannot run without producing a log. What files are listed in the same folder as WideClient? It IS possible to put a parameter into the WideClient.INI file to make it put its log elsewhere -- you've not done that I assume? Or have you put WideClient in a folder in Vista or Windows 7 "Program Files"? If so, then you are looking at an aliassed folder, not the real one, because those operating systems don't allow writing to Program Files, and make aliassed copies. You'd need to run Explorer "as administrator" (a right-click option) to view the correct folder. Otherwise the only plausible explanation is that you are running a different copy of WideClient than you think you are. Regards Pete Link to comment Share on other sites More sharing options...
CDreier Posted November 10, 2009 Author Report Share Posted November 10, 2009 I did a reinstall and the x86 program files is where I'd placed my WideFS folder originally. I have just moved it to the C: root directory. Here is the wideclient.log - actually there are two - one has a 0 attached but this is the log without the 0: ********* WideClient Log [version 6.78] Class=FS98MAIN ********* Date (dmy): 10/11/09, Time 18:33:36.368: Client name is ACER 375 Attempting to connect now 1389 Trying to locate server: Need details from Server Broadcast 1389 Failed to connect: waiting to try again 3432 Attempting to connect now 19921 ****** End of session performance summary ****** 19921 Total time connected = 0 seconds 19921 Reception maximum: 0 frames/sec, 0 bytes/sec 19921 Transmission maximum: 0 frames/sec, 0 bytes/sec 19921 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 19921 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 11, 2009 Report Share Posted November 11, 2009 I did a reinstall and the x86 program files is where I'd placed my WideFS folder originally. I have just moved it to the C: root directory. Here is the wideclient.log - actually there are two - one has a 0 attached but this is the log without the 0: Wideclient deliberately saves the previous log (the one with the 0) when it is started so that folks with problem can restart it quickly without losing any possibly diagnostic information. 1389 Trying to locate server: Need details from Server Broadcast 1389 Failed to connect: waiting to try again The only thing wrong there is that the Client is not seeing the broadcasts from the Server, probably because they aren't in the same workgroup! Did you ever read the part of the User Guide which is headed like this: Configure your Network IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS! It does actually mean what it says, and it does tell you these things and provides a work-around if you really don't want your PCs in the same workgroup. Pete Link to comment Share on other sites More sharing options...
CDreier Posted November 11, 2009 Author Report Share Posted November 11, 2009 Yes, I did read that section specifically. I agree that it now appears that it has to do with the network. However, on both computers the network information is identical showing both computers (Corsair and Acer) and the workgroup is identified as "Workgroup" and the location is "Dreier" Again they are identical on both. I am really lost here. Again, thank you for bearing with me on this. Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 11, 2009 Report Share Posted November 11, 2009 Yes, I did read that section specifically. I agree that it now appears that it has to do with the network. However, on both computers the network information is identical showing both computers (Corsair and Acer) and the workgroup is identified as "Workgroup" and the location is "Dreier" Again they are identical on both. I am really lost here. Again, thank you for bearing with me on this. Well, you could try setting the ServerName and Protocol parameters in the WideClient.INI file just in case there's a problem with broadcasting. Have you either disabled the firewall or specifically allowed wideClient and FSX to get through it on ports 8002 and 9002? Regards Pete Link to comment Share on other sites More sharing options...
CDreier Posted November 11, 2009 Author Report Share Posted November 11, 2009 I got it working!!!! The workgroup names showed the same on one computer (the client) but on the server when I drilled down I found that the workgroup name for the server was different. I'm not sure why that was - but in any event, we're up and running. I want to really thank you for your help and patience in working with me on this. It's wonderful support and again, I can't thank you enough. Take care, Chuck :D Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 11, 2009 Report Share Posted November 11, 2009 I got it working!!!! The workgroup names showed the same on one computer (the client) I thought there was only the one workgroup name? How do you get more? in any event, we're up and running. Great news! Nowhappy flying! Regards Pete Link to comment Share on other sites More sharing options...
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