Jump to content
The simFlight Network Forums

warthog02

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by warthog02

  1. Hi Thorsten

    I still face the same problem in re-installing Paris CDG after following the instructions from Aerosoft.

    After clicking the "Finish" button at the end of the installation process, my PC hung up. The scenery.cfg file showed that the scenery was successfully installed but the Aerosoft folder was not present in the FS9 main folder. This caused FS9 to generate an error message that the scenery could not be located when I started up FS9.

    If you can arrange for me to download the complete Aerosoft folder, perhaps I can place it manually in the FS9 folder and see if it will work. I can email you my email address if you give me yours and we can proceed from there.

    Regards.

    --

    Warthog02

  2. After a PC hangup, I re-installed FS9 and deleted all add-on sceneries. The Paris CDG entry remained in the Windows Add/Remove Programs list despite my attempts to remove it.

    When I re-installed Paris CDG using the 21-character Registration Code received from Simmarket, the Installshield Wizard Complete page indicated "Paris CDG 2005 is now installed on your computer". However pressing the "Finish" button below it caused the installation to hang and after aborting the process a message "An error occurred while launching the setup. The remote procedure call failed."

    Is there any other registration code or serial number that should be used instead?

    If the registry entries of the earlier installation is the cause of the problem, please advise how it can be removed.

    Warthog02

  3. :( Had a problem when Wideclient failed to connect to the Wideserver PC with a "Pre-Connection Error" message appearing in the wideclient.log file.

    Another Wideclient installed on a third PC and running simultaneously did not have this problem.

    :D Problem solved by:

    1. Specifying the IP address instead of the PC name in the wideclient.ini file of the problem PC, and

    2. Disabling SPX/IPX protocol in both the server and problem PC's.

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