Ready for Pushback - FSUIPC problem

[greeneg 0]

Running CC cleaner certainly will not hurt anything. I do it routinely to clean up cookies and other bits and pieces.One other thing occurs to me, look in the modules folder of FS9, you'll find a couple of files called FSUIPC.log and FSUIPC1.log. Check and make certain that the path statements in those are correct.Ed GreenKCLT

---

http://www.oncourse-software.co.uk/forum_images/fdc_beta.jpg

[Guest JollyRoger]

Hi Ed and Ray,Happy new year and many thanx for your help!I ran CCleaner and it corrected 212 errors in the registry...In FS9Modules the FSUIPC.log file says (besides some other stuff):DebugStatus=15 2188 CFlightsim 2004 4235 FLIGHTSOTHERFLTSIM.flt 4266 AIRCRAFTc172Cessna172SP.air 5328 Aircraft="Cessna Skyhawk 172SP" 11391 Advanced Weather Interface Enabled 52188 AIRCRAFTVMAX RFP House LiveryVmax_Classic_2.air 53297 Aircraft="Vmax 747-200 VMAX RFP"The path 'C:Flightsim 2004' is where I have FS9 installed.What about the last two entries?Is this a list of bugs that occured with FSUIPC?I have only this one FSUIPC log file (no FSUIPC1.log).GreetsJ.R.

[Ray Proudfoot 8,952]

Hi JR,Happy New Year to you too.I'm not an expert on FSUIPC log info. I'm guessing those last two entries relate to the aircraft used, nothing more than that.So how is RFP now? Behaving or not?

[greeneg 0]

Ahppy New Year from here also JR.My FSUIPC log has what appears to be a normal path statement:66563 C:Program Filesmicrosoft gamesFlight Simulator 9I have a default installation as above but notice the absence of the extra marks.The file FSUIPC1.log has a similar statement ( I have no idea why it's there or what it does, or why you don't have it, but it is there and the path statement is part of it.I would try this: 1) back up the log file in a safe place, then change the path statement by removing the extranious characters.2) IF that doesn't solve the problem, move the FSUIPC.ini file out of the modules folder to a safe place; it should build a new one, see if this solves the problem. IF not, look at the two ini files and see if there are differences.Finally, if none of that helps, try deleting all of the FSUIPC files from the modules folder, re-download and install FSUIPC and see what happens. Make certain that you have copies of the files, particularly the key file so that you can put it back if you need to.I remember during testing RFP, there were some issues with the .ini file; unfortunately, it's been long enough ago that I cannot remember specifically what they were.Good luck, please post back what happens.Ed GreenKCLT

---

http://www.oncourse-software.co.uk/forum_images/fdc_beta.jpg

[Guest JollyRoger]

Hi,I tried what you said.Still the same error message :(GreetsJ.R.

[greeneg 0]

Truth be told at this point, I don't know....You aren't trying to use a merged aircraft, are you??Ed GreenKCLT

---

http://www.oncourse-software.co.uk/forum_images/fdc_beta.jpg

[Bob Scott 7,720]

A couple of thoughts here...First, make sure that there are no other copies of FSUIPC.dll anywhere in your FS9 folder or subfolders. That includes copies that have been renamed (i.e. FSUIPC.bak) because FS will try to load any PE executable it finds in the Modules folder regardless of its file extension.Second, I recommend you go to Pete Dowson's FSUIPC support forum, and go to the "Other Downloads and Updates" section, and get the latest mid-release beta (v3.769 now) and install that.Last, consider posting this in Pete's support forum.RegardsBob ScottATP IMEL Gulfstream II-III-IV-VSantiago de Chile

[greeneg 0]

Good suggestions, Bob, Thanks.Happy New Year to you also.EDEd GreenKCLT

---

http://www.oncourse-software.co.uk/forum_images/fdc_beta.jpg

[Guest JollyRoger]

Hi folks!First of all I want to apologize for my late reply (I was abroad...).@ Ed: No, I'm not using a merged a/c. Just the freeware RFP 747-200 as can be found here at avsim.com.@ Bob: Thanx for your help. I'm gonna try this out right now.I'll keep you informed!Thanx @ all for help!GreetsJ.R.