greg

Good Morning Pete: You are the man! After following your instructions for reinstalling SimCinnect and installing FSUIPC4-4.104 everything suddenly came alive. All my PFC equipment works prefictly. I can't thank you enough. Have a great day: greg

Hello Peter: I'm so sorry! I miss understood. I'll check that tonight. Thanks for all your help: greg

Hello Peter: Thank you for your reply. Yes, the moduals folder was created and FSUIPC4.dll was in the folder. I included the log file with my first post. I'll try to see if I can get SimConnect working. Sincerly: greg

Hello Peter: I’m sorry to bother you with this and if you’re too busy I understand. I have been using FSX and registered FSUIPC4 and everything was working fine. I installed SP-1 and FSUIPC4 4.10 and FSUIPC4 continued to work as it is supposed to. After SP-1 FSX would error or lock-up my computer when switching to an external view. I decided to chance reregistering FSX do a clean install. I un-installed FSX, defragged, rebooted, reinstalled FSX, installed SP-1 and reregistered FSX. So far so good. FSX runs fine and no errors or lock-ups. I then installed FSUIPC4 4.10 and the log file says it installed okay. (See log below) I also copied the latest PFCFSX.DLL and associated files into the modules folder. Installer for FSUIPC4.DLL version 4.10 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" SetupPath="C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\" Checking version of FSX.EXE: ... Version 10.0.61355.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: ... Okay, Probe Manifest matches installed SimConnect SP1 May07 Checking if there's already a version of FSUIPC4 installed in: C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL ... No previous valid version found. FSX Modules folder created okay! Okay -- installed FSUIPC4 into "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Documents and Settings\Compaq_Administrator\Application Data" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Documents and Settings\Administrator\Application Data" No FSX.CFG there Looking in "C:\Documents and Settings\All Users\Application Data" No FSX.CFG there Looking in "C:\Documents and Settings\Compaq_Administrator\Application Data" Found FSX.CFG in "C:\Documents and Settings\Compaq_Administrator\Application Data\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:\Documents and Settings\Default User\Application Data" No FSX.CFG there Looking in "C:\Documents and Settings\LocalService\Application Data" No FSX.CFG there Looking in "C:\Documents and Settings\NetworkService\Application Data" 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 All installer tasks completed okay! Unfortunately when I started FSX the next time, the modules or FSUIPC tab never appeared. Of course none of my PFC or other FSUIPC dependent equipment worked. I saw your note about getting FSX to recognize SimConnect and I’m going to try that tonight when I get home from work. I was wondering if you had any other suggestions. Thanks for all you do: greg

HelloPeter: First of all, I'm sorry for misspelling your name. I started the TRC link driver (FS2004) and then started FSX. I got an error message the said "MS Flight Simulator incorrect version - please start FS2002 or FS2004" I enabled the IPC read write logging in FSUIPC4 as you asked. I'm not sure what I was supposed to see after that or send you after that. This is all very techno for me. The e-mail I got from SimKits was word for word thier standard reply to FSX questions on the web site. I think they are just shinning people on untill there good and ready to release there own drivers. I sure want to thank you for all your help. You provide a great product and do a great service to flight simming in general. I'll just have to wait untill all of the third party FSX controls and guage drivers are released. Thanks again greg

Hello Moody1: I've looked there but see nothing about SimKit gauges or TRC equipment. Are you refurring to FSUIPC4? If so, I bought a copy and regestered it yesterday. It seems to be working fine but all my gauges are dead. Do you know the name of the file I should down load? Thanks for the help greg

I recently got an e-mail from Peter Brown at SimKits saying that thier new TRClinkX drivers for FSX were not ready yet but I could try Peter Dawson's Beta driver in the meantime. The e-mail provided a link to this forum. I have searched for this beta driver all over this site but could not find it. Where is it or am I just blind? Thanks greg

Hello Peter: Thank you so much for looking into that for me. I will try the work around. I'm looking for ward to the new PFC DLL in the next month or so. Thanks again and have a great day: greg

Hello Peter: I am most sorry. "PropPitch12" is the command I'm trying to assign. As for not reporting it sooner, I apologize. I was sure that "I" was doing something wrong. If PFC DLL needs to be fixed, please don't bother on my account. I would be more then happy to wait untill July. Thanks: greg

Hello Peter: I’m having a problem programming the user portion of my PFC throttle quadrant. When I try to assign “Prop RPM 1-2” to any lever, nothing happens. The slider doesn’t move, the variable values don’t change and of course, the lever does not control the prop RPM’s for engine 1 and 2 in the sim. As a matter of fact, as soon as I select the “Prop RPM 1-2” option from the list of commands, the hash marks next to the slider even appear scrambled on the screen. If I change the command assigned to that lever, the hash marks appear normal again. This problem happens no matter what lever I assign the command to. As far I can tell this happens only with the “Prop RPM 1-2” command option. All other commands can be assigned to any lever. I recently registered my copy of FSUIPC (3.22) but the problem existed before and after registration. I am running PFC DLL 1.844. The problem first appeared a few PFC DLL’s ago. I’m sorry I can’t remember witch PFC DLL the problem started with. Any thoughts or ideas? greg

Peter: I'm verry sorry if this has been discussed many times before but I'm getting old and my thick skull is still a little confused. I have several pieces of PFC hardware. It all works quite well and I've never thought I needed to register my copy of FSUIPC. The more I think about it, now I'm not so sure. I have no problem with paying for it and getting it regestered. (you dersive it) Do I need to regester FSUIPC for PFC hardware and if so, how do I go about doing it and paying for it? Thanks a bunch and keep up the good work. greg pepper