Jerry McCarroll Posted April 17, 2010 Report Share Posted April 17, 2010 I'm running FS2004 on one computer and Project Magenta on another. I just upgraded both computers from Vista to Windows 7. After reinstalling everything I cannot get Project Magenta to communicate with FSUIPC. In FS2004, FSUIPC says it and WIDEFS are registered to me. My FS2004 folder is shared with everyone with full control and with my Homegroup, also my Flightsimulator files are shared as FSPLANS. I have turned off the firewalls on both computers. NetDir is shared as Netdir and the cdu.ini file modified.............. NetDir=\\COCKPIT-2\netdir\. When I run pmfilecheck it stills says: FSUIPC/WideFS found! FSUIPC No Version number Reported! Please Check FSUIPC Installation No data from Flight Simulator, FS doesn't appear to be running! I've been communicating with Jonathan Richardson and he suggested I post on this forum. It just occurred to me that my FS computer is a 64-bit but the Project Magenta computer is 32-bit. Could that be a problem? Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 17, 2010 Report Share Posted April 17, 2010 No data from Flight Simulator, FS doesn't appear to be running! Have you done any elementary checks? Does WideClient say it is connected (it its title bar)? Did you read the notes on configuring your network in the WideFS user guide, the section after the one about Installation? Are your PC in the same workgroup, or if not have you provided WideClient with the parameters telling it where the Server is and what protocol to use, just as instructed? There are Log files produced by FSUIPC, WideClient and WideServer. These are produced specifically to help you find out what is going on. Take a look. Show them to me if you don't understand what they are telling you. Additionally, in any query whatsoever I always need version numbers -- FSUIPC and WideFS. If not currently supported versions (see the Announcements) update first and re-test. File-sharing is irrelevant to FSUIPC and WideFS. That may be needed by PM, but not by anything of mine. It just occurred to me that my FS computer is a 64-bit but the Project Magenta computer is 32-bit. Could that be a problem? No. Regards Pete Link to comment Share on other sites More sharing options...
Jerry McCarroll Posted April 18, 2010 Author Report Share Posted April 18, 2010 Yes Pete, WideClient says it is connected. In FS2004, Wideserver: 1 Connected Both computers using WINDOWS 7 FS2004 is running on computer: COCKPIT-1 WIDECLIENT is running on computer: COCKPIT-2 FSUIPC ve.r 3.98a WIDEFS VER. 6.78 Both PCs are in Workgroup: MSHOME Both PCs are in the same HomeGroup WideClient.ini has the 2 entries: ServerName=COCKPIT-1 Protocol=TCP Here are my log files: ********* FSUIPC, Version 3.98a by Pete Dowson ********* Running on Windows Version 5.1 Build 2600 Service Pack 2 Verifying Certificate for "F:\FS2004\MODULES\FSUIPC.DLL" now ... SUCCESS! Signature verifies okay! Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Hugh McCarroll" User Addr="jerrymc3@sbcglobal.net" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=6000B727[6000B727] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=255 2933 System time = 17/04/2010 18:06:46 2933 \\COCKPIT-1\FS2004\ 2933 System time = 17/04/2010 18:06:46, FS2004 time = 12:00:00 (00:00Z) 5320 FLIGHTS\OTHER\FLTSIM.flt 5335 AIRCRAFT\c172\Cessna172SP.air 5335 Aircraft="Cessna Skyhawk 172SP" 9469 \\COCKPIT-1\Users\JERRYMC3_2\Documents\Flight Simulator Files\DFW TAKEOFF.flt 9516 AIRCRAFT\AA738KH\737800.air 9532 Aircraft="American Airlines B737-800" 10327 Clear All Weather requested: external weather discarded 13307 Advanced Weather Interface Enabled 32963 Traffic File #21 = "scenery\world\scenery\traffic" 1180429 System time = 17/04/2010 18:26:24, FS2004 time = 18:34:52 (00:34Z) 1180429 *** FSUIPC log file being closed Memory managed: 0 Allocs, 16961 Freed ********* FSUIPC Log file closed *********** ********* WideServer.DLL Log [version 6.78] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 17/04/10, Time 18:06:46.961: Server name is COCKPIT-1 29781 Initialising TCP/IP server 29781 Initialising IPX/SPX server 29781 IPX/SPX socket() failed [Error=10044] Socket type not supported 29781 Failed to start IPX/SPX Server 29781 Initialising UDP/IP server 30186 Incoming connection Accepted ok (skt=3972) TCP 30280 Broadcasting service every 1000 mSecs 30498 Connected to computer "COCKPIT-2" running WideClient version 6.780 (skt=3972) TCP 146657 Error 10053: client socket disconnected at Client: removing (skt=3972) TCP 163442 Incoming connection Accepted ok (skt=472) TCP 163676 Connected to computer "COCKPIT-2" running WideClient version 6.780 (skt=472) TCP 1182909 Close signalled to clients 1184001 Closing down now ... Memory managed: Offset records: 30 alloc, 30 free Read buffer usage: 518 alloc, 518 free, max in session: 1 Write buffer usage: 41693 alloc, 41693 free, max in session: 1 Throughput maximum achieved: 2 frames/sec, 189 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 19 bytes/sec Average receive rate from "COCKPIT-2": 0 frames/sec, 18 bytes/sec ********* Log file closed ********* ********* WideClient Log [version 6.78] Class=FS98MAIN ********* Date (dmy): 17/04/10, Time 18:09:33.219: Client name is COCKPIT-2 218 Attempting to connect now 296 Trying TCP/IP host "COCKPIT-1" port 8002 ... 296Okay, IP Address = 192.168.1.7 296 Connection made okay! 1014209 Received shutdown offset code = ADBC 1014209 FS closing down (param=ADBC), disconnecting 1014209 ********* Interim performance summary ********* 1014209 Total time connected so far = 1014 seconds 1014209 Reception maximum so far: 2 frames/sec, 173 bytes/sec 1014209 Reception average whilst connected so far: 1 frames/sec, 41 bytes/sec 1014209 Transmission maximum so far: 0 frames/sec, 96 bytes/sec 1014209 Transmission average whilst connected so far: 0 frames/sec, 19 bytes/sec 1014209 Max receive buffer = 340, Max send depth = 1, Send frames lost = 0 1014209 *********************************************** 1014318 Received shutdown offset code = ADBC 1020917 Connection closed by server! 1020917 Attempting to connect now 1020917 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1020917Okay, IP Address = 192.168.1.7 1021947 Error on client pre-Connection Select() [Error=10061] Connection refused 1021947 Ready to try connection again 1022961 Attempting to connect now 1082678 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1082678Okay, IP Address = 192.168.1.7 1144454 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1144454Okay, IP Address = 192.168.1.7 1206231 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1206231Okay, IP Address = 192.168.1.7 1268085 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1268085Okay, IP Address = 192.168.1.7 1329924 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1329924Okay, IP Address = 192.168.1.7 1391700 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1391700Okay, IP Address = 192.168.1.7 1453648 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1453648Okay, IP Address = 192.168.1.7 1515409 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1515409Okay, IP Address = 192.168.1.7 1577248 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1577248Okay, IP Address = 192.168.1.7 1639087 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1639087Okay, IP Address = 192.168.1.7 1700879 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1700879Okay, IP Address = 192.168.1.7 1762733 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1762733Okay, IP Address = 192.168.1.7 1824494 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1824494Okay, IP Address = 192.168.1.7 1886348 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1886348Okay, IP Address = 192.168.1.7 1948140 Trying TCP/IP host "COCKPIT-1" port 8002 ... 1948140Okay, IP Address = 192.168.1.7 2009979 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2009979Okay, IP Address = 192.168.1.7 2071802 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2071802Okay, IP Address = 192.168.1.7 2133579 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2133579Okay, IP Address = 192.168.1.7 2195433 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2195433Okay, IP Address = 192.168.1.7 2257210 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2257210Okay, IP Address = 192.168.1.7 2319048 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2319048Okay, IP Address = 192.168.1.7 2380825 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2380825Okay, IP Address = 192.168.1.7 2442617 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2442617Okay, IP Address = 192.168.1.7 2504393 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2504393Okay, IP Address = 192.168.1.7 2566294 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2566294Okay, IP Address = 192.168.1.7 2628133 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2628133Okay, IP Address = 192.168.1.7 2689972 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2689972Okay, IP Address = 192.168.1.7 2751873 Trying TCP/IP host "COCKPIT-1" port 8002 ... 2751873Okay, IP Address = 192.168.1.7 Hope this helps Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 18, 2010 Report Share Posted April 18, 2010 Here are my log files: All those show everything running fine. There's simply no applications even trying to connect to WideClient on the Client PC, so it is simply idling with the 2/3 second update frame to keep the connection.. You aren't running WideClient and the applications at different privilege levels are you? If you run one program "as administrator" and the other normally, they can't talk to each other -- Windows prohibits it. Why aren't you having WideClient load your PM apps via the RunReady parameters? The only other way you can stop clients connecting to WideClient is by setting ClassInstance in the INI file, but you only ever do that to run FS on the same PC as WideClient, or possibly to have several parallel instances of WideClient running (for several "button screens" perhaps, as I do. Regards Pete Link to comment Share on other sites More sharing options...
Jerry McCarroll Posted April 18, 2010 Author Report Share Posted April 18, 2010 Aha! I wasn't running the PFD, CDU OR MCP as Administrator. I knew you would pick my brain till I found the problem. Thank you so much for your support and quick response. Still have a couple of problems with Project Magenta but at least the PFD, CDU & EICAS are communication and functioning properly. Hugh (Jerry) Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 18, 2010 Report Share Posted April 18, 2010 Aha!I wasn't running the PFD, CDU OR MCP as Administrator. But why would you need to? Just don't run WideClient "as administrator" either. If you used the WideClient INI file "Run" or "Runready" facilities to start them, as recommended, you wouldn't have any worries in any case. Regards Pete Link to comment Share on other sites More sharing options...
Jerry McCarroll Posted April 19, 2010 Author Report Share Posted April 19, 2010 Pete I thought I had this thing licked, most everything is working except the flight plan won't display in the ND and no fonts are showing in pmsystems. Everything else is showing, waypoints, airports, tuned VORs, heading bug, etc. I ran pmfilecheck and it still says: pmFileCheck Build 40 Opening Connections Local Path: C:\PROJECT MAGENTA\PFD Checking Computer and User Name Local Computer Name: COCKPIT-2 Local User Name: JERRYMC3 FSUIPC/WideFS found! FSUIPC No Version number Reported! Please Check FSUIPC Installation No data from Flight Simulator, FS doesn't appear to be running! [/b] Closing Everything 4/19/2010 1:43:55 PM Things To Do: * Check FSUIPC Installation (Version is 0) * Run Flight Simulator If you wish to, please check http://www.projectmagenta.com/notams.html When I press CTRL O on the PFD it reports everything is connected and active and recognizes FSUIPC as ver 3.980. This is really boggeling my mind. Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 19, 2010 Report Share Posted April 19, 2010 I thought I had this thing licked, most everything is working except the flight plan won't display in the ND and no fonts are showing in pmsystems. Everything else is showing, waypoints, airports, tuned VORs, heading bug, etc. Well neither the flight plan nor the fonts are anything to do with FSUIPC, WideFS or the connection to FS. You'll need to ask PM support about that. The fonts would be part of the installation, the flight plan is a matter of filesharing and the NetDir business in PM. I ran pmfilecheck and it still says: ... FSUIPC No Version number Reported! Please Check FSUIPC Installation[/b] No data from Flight Simulator, FS doesn't appear to be running! [/b] Well that conflicts with you saying "most everything is working", because if what pmFileCheck says is true, nothing would work. When I press CTRL O on the PFD it reports everything is connected and active and recognizes FSUIPC as ver 3.980. Again giving the lie to the pmFileCheck report. It sounds as if you are getting really mixed up with things "running as administrator" or not. Just don't run ANYTHING "as administrator. It should not be necessary for anything. Stop confusing yourself! This is really boggeling my mind. Sorry I can't help, you appear to have all my part working. Regards Pete Link to comment Share on other sites More sharing options...
Jerry McCarroll Posted April 19, 2010 Author Report Share Posted April 19, 2010 Peter Thanks for all your help. I tried running everything not "as administrator" but it quit working again. However, when I turned off "as administrator" just for FS2004 the Flight Plan loaded on the ND. Crazy, huh? Somebody needs to create an operating system just for flight simmers! Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 19, 2010 Report Share Posted April 19, 2010 Thanks for all your help. I tried running everything not "as administrator" but it quit working again. However, when I turned off "as administrator" just for FS2004 the Flight Plan loaded on the ND. Crazy, huh? Somebody needs to create an operating system just for flight simmers! I think Win7 is a good system, certainly the best Microsoft has produced since Windows 98. I've no idea why you are having so much difficulty, nothing you report seems to make sense. But have you tried discussing it over on the PM Forums in MyCockpit? http://www.mycockpit.org/forums/ . There's are lot of PM users there, and many Win7 users too. Regards Pete Link to comment Share on other sites More sharing options...
Jerry McCarroll Posted April 20, 2010 Author Report Share Posted April 20, 2010 Thanks, I'll try that. Link to comment Share on other sites More sharing options...
Jerry McCarroll Posted June 9, 2010 Author Report Share Posted June 9, 2010 Pete I finally got Windows7 64bit to work with PM. It had nothing to do with 64bit. I discovered 1 computer was on the wrong Workgroup; not sure how that happened, I could have sworn I checked it before. Also I ran all PM programs in compatibility mode for Windows XP and everything is working fine now. Sorry I'm such a dufus! Jerry 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