Jump to content
The simFlight Network Forums

FalconAF

Members
  • Posts

    48
  • Joined

  • Last visited

Posts posted by FalconAF

  1. I have read this forum and am still getting the can not connect message. Are there any other solutions?

    As Pete said, the FSC forum lists other things you can try. I tried them all, but only the solution I "discovered" in my post above worked for me.

    One thought I have on your continuing problem. Are you running the programs as "Administrator"? Try right-clicking on the desktop icons, then select "Run as Administrator" in the selection box. If that solves the problem, you can do it that way from now on. Or, you can go to the FSC installation folder, select the two ".exe" files, and change the "Properties" of them so they will "Run as Administrator" every time you double-click the desktop icons.

    If the above doesn't work, you have a different problem yet and need to talk to the FSC forum folks.

    Rick

  2. Thanks for this post, I had the same with FS9 and FSC86, both on one computer and in an network.

    Problem solved now :D

    Frisian,

    Thanks for YOUR reply. At least now I know my problem wasn't because of something I "did wrong" during the installation. Your reply indicates that it may very well be an installer problem, at least for some people or their computer configurations.

    Glad you got it working now. :D

    Rick

  3. If you have been (or are still) getting that dreaded, "Unable to connect to Flight Simulator Msg# (no process started)" error message after upgrading or installing FSX v8.6, you may want to take a look at the post below I made in the FSUIPC forum.

    viewtopic.php?f=54&t=78953&p=480100#p480100

    I just didn't feel like re-typing the whole thing here again. The readme file that comes with the "full install" download for v8.6 is very, very confusing. Plus, I have no idea WHY what happend DID happen when I installed v8.6, but it did. FSC86 would not connect to FSX until I deleted the 2 desktop shortcuts the installer created, and I replaced them with "Create Shortcut Here" copies directly fromthe new FSC installation folder.

  4. I'm going to post a message in their forum linking to this one. I'm just too darn frizzled out right now to retype the whole thing again! :)

    In as much as I have no idea why those two shortcuts got placed on the desktop the way they were, I can't really say it is an installer problem or not. But it may be something they want to look at...yes.

    The other thing that is really confusing about the "full install" download for v8.6 is the "readme86.txt" file that comes with it. It says:

    ---------------------------------------------

    "This zip-file contains the files necessary to upgrade FlightSim

    Commander v.8.5 to v.8.6. You must have version 8.5 properly

    installed in order to use these files."

    "If you have a version installed that is earlier than 8.5, you

    need to download and install the full version. In this case you

    need to make a backup of your registration file (register.fsc)

    which you need to copy into the main FlightSim Commander folder

    after installation."

    -------------------------------------------

    If it is a "full install", why does the first paragraph in the readme file say it is an "upgrade" from 8.5 to 8.6, and you NEED 8.5 installed already? Then the second paragraph completely contradicts THAT, and says do it a DIFFERENT way. Looks to me like they put the "upgrade only" readme file in the full install download.

    I need a vacation..... :?

  5. As pennance for sending an email to Pete instead of posting my question in the forum first (I did it only because I figured he would want to eventually see my zipped copy of my fsuipc4.key file, as he requested another poster to send him), I will post my "discovery" after over 8 hours of angst at getting the dreaded FSC "Unable to connect to Flight Simulator Msg# (no process started)" error message in FSC v8.6. I don't know HOW it happened, or WHY it happened, but it DID happen...even after following the instructions in the FSCommander forum several times with no success at solving the problem.

    I downloaded and installed the FSC "full version" 8.6 installer. Yes...I did "Run as Administrator" when I ran it. It seemed to install fine. It even put the 2 shortcut icons on my desktop for me (for FSC86.exe and FSCDbManager86.exe). I then copied the 2 files that I had backed up (per the instructions) from my previous FSC installation into the new main FSC folder . Then I ran the DataBase Manager, per the instructions. All seemed fine. But FSC would never connect to FSX.

    After over 8 hours of anguish including checking and double-checking all my settings for "Adminstrator" Rights, etc, I stumbled across something. When I right-clicked on the 2 desktop shortcut icons the installer placed there and selected "Properties", the "Target" and "Start in:" boxes were BOTH BLANK. I have no idea how or why that happened. Or why when I clicked on them, they would BOTH run the programs yet. But they did. And the FSC86.exe one would load a 021209 version, which I discovered was not the correct build.

    So I deleted the 2 desktop shortcuts the installer put there, went to the FSC folder where the EXE files were, and dragged them to the desktop myself and did a "Create Shortcut Here" for them. After that, EVERYTHING worked fine. And the Build for FSC was then shown as 101209...the correct one.

    If you are still having "connection" problems with FSC v8.6, check your desktop shortcut properties for the 2 shortcuts. You may need to delete them, create new ones directly from the FSC installation folder, then double-check the security settings for the two files. But it appears now, at least in my case, it was not a problem with FSUIPC.

    If this helps anybody, you're welcome! :)

  6. Does FSC make an entry during installation to the FSX EXE.XML file?

    Reason I ask is I never had any problem with FSC in the past, but now can't get FSC to connect to FSX anymore. This started happening after I updated REX to REX 2.0, which overwrote the FSX EXE.XML file (they put out a patch to fix that from happening in the future, but the original 2.0 installation hosed a lot of folk's EXE.XML files and we need to rebuild them).

    If yes, can someone please post a copy\paste of the entries for FSC in the EXE.XML file? I'll change any "paths" in it to work with my FSX installation location.

    Thanks.

    FSX

    FSC 8.5

    DB Manager 8.5

    Vista 64 Ultimate

    FSUIPC most current payware version

    Rick

  7. OK, got it. But the way the wording is in the "sticky" post about the VATSIM issue it fixes is confusing. It reads like you need TWO patches. First, a patch to Build 09.12.2008, THEN a separate VATSIM patch. I was trying to find TWO separate patches. You might want to clarify that the "Patch for 8.4" shown on the download page is actually the v8.4 patch TO 09.12.2008, AND the VATSIM patch, all-in-one.

    Thanks for the clarification.

    FalconAF

  8. OK, you have me totally confused right now as to Build numbers.

    1. I have the SimMarket FSC edition, v8.3 and the upgrade to v8.4. When I run FSC it says I have ver 8.4, Build 110908

    2. The Patch post says I need Build 09.12.2008 before installing Patch 8.4.1

    3. My SimMarket account shows I can still download my original v8.4 upgrade purchase. I see no other link for an "upgrade" to a Build 09.12.2008

    4. The FSC site has a download for v8.4

    What the heck do I need to do to get to Build 09.12.2008? Or do I even need to? Are the Build dates in Month\Day\Year format? Is Build 09.12.2008 a LATER Build than 110908 (what I'm showing in FSC now)?

    Want to make sure I don't hose FSC by installing the Patch to a wrong Build version.

    Thanks

    FalcaonAF

×
×
  • 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.