Jump to content
The simFlight Network Forums

Jim Hand

Members
  • Posts

    9
  • Joined

  • Last visited

Jim Hand's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Pete: Of course I meant to say the Reality XP Garmin 430W's for use with MSFS. My error. JHH
  2. Pete: Are you aware of anyone writing an interface between Elite's new Garmin 430W hardware and MSFS? I really enjoy the unit and the Elite v8.5, but would really like to use the hardware with the Realistic 430W's on Eaglesoft's Cirrus SR20 and the stand alone version of the Realistic Garmin 430W which I purchased to use with MSFS 9 and X. Thanks in advance for any leads! Jim Hand, Portland, OR, USA
  3. Pete: Forgot to let you know....the fault was in Elite's patch to FSX and FS9...actually my installation of the patch....all is well now. Thanks for all you help and patience! JHH
  4. Pete: Got it. After the re-build, it shall be done. I did use the show hidden folders option with "search" and came up with nothing that way as well. The settings will be altered as you suggest when we set up. The computer is going in for a full equipment check due to a suspicion by the IT guy that there may be some bad ram at work as well. Thanks for your advice! JHH
  5. Pete: Noted. Believe it or not, I could not SEE those files. I used both normal and hidden file mode, etc. in search. I noticed the lines in the log as well and tried everything I know (limited, but nonetheless) to find them with 'Search', explore, etc with no luck, in order to delete them. There are other computer issues with the video card, as I mentioned, which make the Windows re-build a good idea anyway, so, one way or the other, this should fix it. I will let you know. BTW, I searched the FSX forum but couldn't see a script for FSX uninstall, but then, I couldn't find these troublesome files either. Thanks again! JHH
  6. Pete: After another cycle of install of fSX, here is the latest install log of FSUIPC4. Due to some ongoing video issues, I am going to commence a full windows re-install. That may get the job done. More later, JHH Installer for FSUIPC4.DLL version 4.20 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.60905.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: ... Okay, Probe Manifest matches installed SimConnect 60905 (Original) 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\James\Application Data" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Documents and Settings\All Users\Application Data" No FSX.CFG there Looking in "C:\Documents and Settings\Default User\Application Data" No FSX.CFG there Looking in "C:\Documents and Settings\James\Application Data" Found FSX.CFG in "C:\Documents and Settings\James\Application Data\Microsoft\FSX\FSX.CFG"! Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. No previous FSUIPC4 entry found, so adding it now ... ... 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\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! *************** End of Install Log ***************
  7. Pete: Just to be more clear, I will send you the logs in a few hours time, all I can find. Thanks again! JHH
  8. Pete: You are correct in assuming I only repaired the base one, not the ones in the two service packs....when I was dealing with the two installs where they were installed. However, this latest attempt, after doing the best cleansing of my computer of anything FSX I could find, running a register cleaner over the whole thing (ccleaner AND Norton's in one case) I still have the problem after re-installing ONLY FSX from the discs. I used windows to un-install FSX Service Pack 2 because that was the only FSX that it could see in control panel, I used "ccleaner's" uninstaller to get rid of FSX and the other service pack, then went to explore (works just like Windows's one but sees more stuff) and deleted the remaining FSX folder in "Microsoft Games" folder under Programs....went to My Documents and deleted the entire FSX folder it creates there. One note of interest which may indicate something to you, I changed the side number on my Cessna 172 normal selection and even after the frantic efforts to remove anything related to FSX, when I re-install, the new side number remains, as well as a selection of music FSX-3 I believe it is rather than the normal ditty. I do not divine whether the fact that I have FS9.1 up and running may mean that some of the pref files are common. The final and still installed attempt is only disc installed FSX, no updates, and I have tried both your driver that comes with the normal download, 4.2 and I have also tried a couple of the updates posted above, installed as you instructed, with exactly the same outcome. Seemingly a normally functioning game that responds to keystrokes from the keyboard but is absolutely ignoring the PFC gear and Elite AV2000 avionics stack. Thankfully, the hardware bit is not a cause because FS9.1 works fully and beautifully with everything from yoke to pedals to quadrant to avionics panel functioning like a dream in FS9.1 as it did in FSX before my IT guy decided to run wild and install one graphics card driver over another instead of a delete-reinstall. It caused all sorts of grief with the menus of FSX and eventually screwed FSX up to a point where a re-install was required after the monitors and graphics card and drivers were put right. I thought maybe a re-install of FS9.1 might help, but it is working so perfectly, I hate to screw it up too. Back on the Cessna 172 selection, even though the description says it is red and gold, it is battleship grey when it shows up in the selector and on screen during use inside the game. Not sure what that means but I am trying to tell you everything quirky I can remember. I can, if you would find it helpful, send you any logs, settings profiles, or whatever from my existing install when I get to my office. I am not particularly proud to say that I have devoted five days of my life to setting this system up and then dealing with all the problems, of which this FSX issue is relatively late in the game. I await your sage advice! Thanks in advance. JHH
  9. Pete: I am a paid up registered user (J.Hand) of both FSUIPC 3 and 4. I have, in the last few days successfully installed MS FSX, updated it with both Service Packs, and installed the FSUIPC4.20, and flew the result successfully for hours with some old PFC serial port controls, which I can describe in detail if need be. Since having to re-install FSX exactly the same way after having some issues with a video card driver install, I cannot make the connection any more. I have tried your earlier suggestion in locating, deleting and then running repair to replace the simconnect folder, I have done two complete and thorough uninstalls of all components of FSX, deleted any residual folders, wherever I could find them, reinstalled from the ground up twice, same result, did a full reinstall without the service packs, same result...meanwhile, my hardware and your FSUIPC 3 continues to run my FS9.1 install perfectly, with absolutely no problem, so I know it is somewhere in FSX that the demon is hiding. Should I just give up on FSX and shoot my approaches with FS9.1 and my existing hardware, or send you a log sometime tomorrow after running my current FSX installation to see if you can spot the disconnect? Thanks in advance! You make my day every time I run FS9.1!, and FSX was sure a blast with FSUIPC4 until the gremlins got me.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.