LH478 Posted August 30, 2011 Report Posted August 30, 2011 Hi guys, need some ideas. The scenario is as follows: Windows 7 ultimate x64 FSX on disk C and FSUIPC 4.4 installed FS9 om disk D and FSUIPC 3.72 (not registered) When starting FS Commander can`t connect to FS9. Error message FSUIPC not found. All ideas are welcomed. Thanks
Pete Dowson Posted August 30, 2011 Report Posted August 30, 2011 FSX on disk C and FSUIPC 4.4 installed FS9 om disk D and FSUIPC 3.72 (not registered) Both FSUIPC versions are very old and totally unsupportable. You need at least 3.99 for FS9 and 4.70 for FSX. There are later versions (3.997q and 4.727) in the Download Links subforum, but you need to run those installers first. Regards Pete
LH478 Posted August 30, 2011 Author Report Posted August 30, 2011 Both updated. FSX with FSUIPC 4.72 working perfectly. FS9 with FSUIPC 3.99 not working.
Pete Dowson Posted August 30, 2011 Report Posted August 30, 2011 Both updated. FSX with FSUIPC 4.72 working perfectly. FS9 with FSUIPC 3.99 not working. What do you mean by "not working"? Is there an FSUIPC. Log file in the Modules folder? Show it to me if so. Pete
LH478 Posted August 31, 2011 Author Report Posted August 31, 2011 (edited) Here goes everything I found: FSUIPCLog: ********* FSUIPC, Version 3.991 by Pete Dowson ********* Running on Windows Version 5.1 Build 2600 Service Pack 2 Verifying Certificate for "D:\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.dll" now ... SUCCESS! Signature verifies okay! Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="" User Addr="" FSUIPC not user registered WIDEFS not user registered, or expired Module base=61000000 WeatherReadInterval=4 LogOptions=00000001 DebugStatus=0 25265 System time = 30/08/2011 13:17:41 25265 D:\Microsoft Games\Flight Simulator 9\ 25265 System time = 30/08/2011 13:17:41, FS2004 time = 12:00:00 (00:00Z) 33250 C:\Users\Igor\Documents\Flight Simulator Files\today.flt 33281 AIRCRAFT\beech_baron_58\Beech_Baron_58.air 50375 AIRCRAFT\b747_400\Boeing747-400.air 74953 C:\Users\Igor\Documents\Flight Simulator Files\UI generated flight.flt 75812 Clear All Weather requested: external weather discarded 78203 Advanced Weather Interface Enabled 100609 Traffic File #13 = "scenery\world\scenery\traffic030528" 101984 Traffic File #23 = "scenery\world\scenery\traffic_000_woa_air france_su09" 102031 Traffic File #14 = "scenery\world\scenery\traffic_000_woa_aer lingus_wi08" 102140 Traffic File #62 = "scenery\world\scenery\traffic_000_woa_lufthansa_su09" 102343 Traffic File #74 = "scenery\world\scenery\traffic_094_woa_air berlin_wi07" 157000 WeatherOptions set, now 0000B027 (timer=0) 176218 System time = 30/08/2011 13:20:12, FS2004 time = 13:18:57 (11:18Z) 176218 *** FSUIPC log file being closed Memory managed: 0 Allocs, 730 Freed ********* FSUIPC Log file closed *********** Installer for FSUIPC.DLL version 3.991 Looking in registry for FS9.1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1 Parameter"EXE Path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1 Parameter"EXE Path" ... NOT found! ... Looking in registry for FS9 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0 Parameter"EXE Path" ... >>> OK! FOUND FS9! <<< ... Looking in registry for FS8 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\8.0 Parameter"EXE Path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\8.0 Parameter"EXE Path" ... NOT found! ... Looking in registry for FS7 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\7.0 Parameter"path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\7.0 Parameter"path" ... NOT found! ... Looking in registry for FS6.1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\6.1 Parameter"InstallDir" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\6.1 Parameter"InstallDir" ... NOT found! ... Looking in registry for CFS2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\2.0 Parameter"EXE Path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\2.0 Parameter"EXE Path" ... NOT found! ... Looking in registry for CFS1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\1.0 Parameter"EXE Path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\1.0 Parameter"EXE Path" ... NOT found! ... =========================================================== INSTALLATION FOR FS9: EXE Path="D:\Microsoft Games\Flight Simulator 9" Checking if there's already a version of FSUIPC installed in: D:\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL ... Version 3.720 found. Okay -- installed FSUIPC into "D:\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL" "Modules\FSUIPC Documents" folder already exists. Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC User Guide.pdf" okay Installed "FSUIPC for Advanced Users.pdf" okay Installed "FSUIPC History.pdf" okay Installed "List of FS2004 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 "Lua Plugins for VRInsight Devices.pdf" okay Installed "Example LUA plugins.zip" okay Installed "SIMSAMURAI+FSUIPC+TUTORIAL.pdf" okay FSUIPC.DLL installed and signature checked out okay! Deleted GlobalSign Root fix program ... no longer relevant =========================================================== All installer tasks completed okay! Registration offers were declined *************** End of Install Log *************** errorlog FTG-ACARS 22:06 23.08.2011 : The following error occured: Datei C:\Users\Markus Joppich\Desktop\FTG-ACARS\System\errorlog.txt kann nicht geöffnet werden. Das System kann die angegebene Datei nicht finden Fehlertyp: EFOpenError Sender: Form1 [TForm1] 22:06 23.08.2011 : FTG-ACARS LOADING UP 22:06 23.08.2011 : LOAD ACARS VERSION: 3.1 22:06 23.08.2011 : FTG-ACARS BUILD 0 22:06 23.08.2011 : The following error occured: HTTP/1.1 404 Not Found Fehlertyp: EIdHTTPProtocolException Sender: Form1 [TForm1] FTG-ACARS error log: 19:56 29.08.2011 : FTG-ACARS LOADING UP 19:56 29.08.2011 : LOAD ACARS VERSION: 3.1 19:56 29.08.2011 : FTG-ACARS BUILD 0 19:56 29.08.2011 : CHECKING PASSWORD 19:56 29.08.2011 : CHECKING PASSWORD FOR LH478 19:56 29.08.2011 : PASSWORD ACCEPTED 19:56 29.08.2011 : CHECKING PASSWORD FOR LH478: correct 19:57 29.08.2011 : MINUMUM MACH FOR 747-400 IS 0.82 19:57 29.08.2011 : MAXIMUM MACH FOR 747-400 IS 0.88 19:57 29.08.2011 : TRY TO CONNECT TO FSUIPC 19:57 29.08.2011 : ERROR: FSUIPC NOT FOUND - NOT CONNECTED TO FSUIPC IPC sendmessage failed all retries FSC · Version 8.6 · Build:200210 - 8/30/2011 7:16:08 PM Application path: D:\FSC ReadIni successful (True) SetFSVersion successful (True) SetCurrentFSPath successful (True) SetFlightplanFolders successful (True) DecryptIvaoPWord successful (True) ReadRegister successful (True) AIRAC-0911 Rev.1 - OCT22-NOV18/09 ReadAirac successful (True) ReadAircraft successful (True) Initializing counters successful (True) Opening MagVar file successful (True) D:\FSC\database\FS09\region.fsc = 34 D:\FSC\database\FS09\country.fsc = 15334 D:\FSC\database\FS09\state.fsc = 5924 D:\FSC\database\FS09\city.fsc = 2204644 D:\FSC\database\FS09\airport.fsc = 10229955 Reading airports successful (True) D:\FSC\database\FS09\ils.fsc no pending ILS exist Reading pending ILS successful (False) D:\FSC\database\FS09\taxi.fsc = 5946358; taxicount = 191817 D:\FSC\database\FS09\poly.fsc = 3456112; polycount = 216006 D:\FSC\database\FS09\marker.fsc = 52738; markercount = 3766 D:\FSC\database\msa.fsc = 976600; msacount = 19531 D:\FSC\database\dijinter.fsc = 5978468 D:\FSC\database\vicways.fsc = 1433250 D:\FSC\database\jetways.fsc = 1214310 D:\FSC\database\fixes.fsc = 7820256 D:\FSC\database\vor.fsc = 252784 D:\FSC\database\ndb.fsc = 422834 D:\FSC\database\airspace.fsc = 4938528 D:\FSC\database\userwp.txt = 55181; usercount = 817 D:\FSC\map\worldpolygon.bin = 3140434 D:\FSC\map\worldline.bin = 206595 ReadNaviDatabases successful (True) ReassignILSCoords successful (True) LoadFuelNames successful (True) LoadGateNames successful (True) LoadGateType successful (True) LoadFreqTypes successful (True) LoadSurfaceNames successful (True) D:\FSC\database\fsc_ivac.txt = 67165 D:\FSC\database\fsc_accomp.txt = 163811 D:\FSC\database\fsc_ivao.dat = 455634 D:\FSC\database\fsc_vatsim.dat = 455634 ReadOnlineDatabases successful (True) D:\FSC\urlivao.ini = 37 D:\FSC\urlvatsim.ini = 183 D:\FSC\ivao_status.txt = 985 D:\FSC\vatsim_status.txt = 1643 D:\FSC\database\fsc_ivao.txt = 328366 D:\FSC\database\fsc_vatsim.txt = 257663 Check4OnlineFiles successful (True) D:\FSC\database\sid.fsc = 7997625 D:\FSC\database\star.fsc = 7348495 Check4SidStarFiles successful (True) D:\FSC\database\WxStation.txt = 117404 Check4WeatherFile successful (True) ReadUserObjects successful (True) LogFile written successfully Logfile Closed at: 8/30/2011 7:16:27 PM FSC.ini [uSER] MAPWIN=2 SCALE=10 AIRCRAFT=11 FUEL=2 FILL=0 FONTSIZE=0 ACSIZE=1 LL=3 GC=-1 DECSEC=1 ARC=1 DIRCON=0 TRACEALT=50 TRACEALTTYPE=-1 MZOOM=0 HOTKEYS=0 MOVINGMAP=-1 MMCOUNTERSET=30 [FLIGHTPLAN] SECLEN=30 SECWIDTH=30 FAFDIST=8.5 FPSEL=217 FPPATH09= FPPATH10= SQUAWKBOXPATH=D:\FSC\FSplan\SquawkBox IVAOPATH=D:\FSC\FSplan\IVAO FSINNPATH=D:\FSC\FSplan\FSInn RADCONPATH=D:\FSC\FSplan\RC PROMAGPATH=D:\FSC\FSplan\PM TSPATH= XPLANEPATH= MAP=3473408 COAST=72 LATLONG=6250335 COMP=9408399 WIND=33023 HILITE=255 MEASURE=16777088 ZOOM=16776960 MSA=8421504 VICTOR=16744448 CTRZ=3684408 JET=16776960 AIR1=21760 AIR2=5963867 VOR=22963 NDB=39680 ILS=32896 INT=9922048 FIX=19948 USER=8355711 MOVAC=16776960 ACINCTRZ=255 ACATCTRZ=16776960 ROUTE=33023 AI=65535 AIFREQ=65280 TCAS1=33023 TCAS2=255 AP=11513775 RWY=5197647 TAXI=4144959 TAXINAME=16777088 RWYID=16776960 PARKING=10485760 LAND=4369 RIVER=12615680 IVAOFIR=5308497 IVAOFSS=16776960 IVAOTWR=65535 IVAOGND=1861375 IVAOAPP=255 STATICACCOLOR=16777088 FIRACTIVCOLOR=65535 FIRINACTIVCOLOR=16711935 [MENU] BUTTON=1999 AIMENU=30 AIRSPACE=32 AITRAFFIC=1 GPSVISIBLE=1 COMPMENU=0 LATLONGMENU=1 ONTOP=0 [MAP] REGION=0 COUNTRY=75 STATE=-1 CITY=128 WINX=-120 WINY=-120 REMWINPOS=1 REMGPSWINPOS=0 GPSWINX=500 GPSWINY=1200 [DOWNLOAD] NATRACKURL=https://pilotweb.nas.faa.gov/qryhtml/nat.html NATRACKFILE=North Atlantic Tracks PACOTURL=https://pilotweb.nas.faa.gov/tracks/pTracks.html PACOTFILE=United States NOTAM Office WXURL=ftp://tgftp.nws.noaa.gov/data/observations/metar/cycles/ WXFILE=fsc_metar [ONLINE] AUTODOWNLOAD=-1 DLINTERVAL=3 ONLUSRCALLSIGN= ONLSHOWALTSPEED=0 ONLSHOWDEPDEST=0 VATSIMURLSTATUS=http://usa-s1.vatsim.net/data/status.txt IVAOURLSTATUS=http://www.ivao.aero/whazzup/status.txt IVAOVID=0 USECALLSIGN=-1 [FS] FSX=0 [FIND] CLOSE=0 SHOW=-1 Edited August 31, 2011 by LH478
Luke Kolin Posted August 31, 2011 Report Posted August 31, 2011 Looks like an FTG-ACARS failure. Luke
Pete Dowson Posted August 31, 2011 Report Posted August 31, 2011 FTG-ACARS error log The FSUIPC install and run-time logs show everything is fine as far as FSUIPC is concerned. It is working. If your "FTG-ACARS" program, whatever that is (I don't know it at all) won't connect then it is either because you are running it and FS9 at different privilege levels (one "as administrator" and the other not) -- which is not possible to tell from logs -- or because of some other requirement of that program which you have not met. You probably need to send your logs to FTG-ACARS support to get them to help you resolve the matter. Regards Pete
LH478 Posted August 31, 2011 Author Report Posted August 31, 2011 But what happens with FSCommander that won`t find FS9 either?
Pete Dowson Posted August 31, 2011 Report Posted August 31, 2011 But what happens with FSCommander that won`t find FS9 either? Sorry, I've no idea. Perhaps the same problem? Perhaps you are running FS9 at a different privilege level to the programs wishing to access it? Certainly there's no question about it -- FSUIPC3 is running fine in your FS9 installation. Of course I think FSC wants to access other things in FS than FSUIPC, so be sure it isn't something to do with access to folders. 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