Jump to content

EdwardS

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by EdwardS

  1. Wow, what a crazy last few days with the wife and kids all pulling dad in one direction or another. It's nice to be needed but I want some time to make my flights you know? :lol:

     

    I really should start learning how to work with AFCAD's. Andy, that fixed the problem. Urs, Andy, thank you both for the help. Now I'm off to make my flight and earn my VA's ribbon for the Olympics. I will also be hunting for information on AFCAD's and maybe even how to create scenery while I'm at it.

  2. Hello everyone, :D

     

    My issue, please forgive me if it has already been answered, concerns EFB and updating after adding a new scenery. I manually installed an updated scenery/AFCAD for UAAA, link provided below. I added the update to FSX and checked that it had taken. It did, the scenery and updated runways are all there. Next I started the Data Provider, selected Data, than FSX Scenery Data Update and ran it. When all was completed I opened the Display Unit and checked UAAA there. The display unit was still showing all the old information from the default UAAA scenery. I started FSX and while connected to the Data Provider taxied around the airport including up and down the runways. In FSX everything was fine; however, the Data Provider showed me as taxing all around the area.

     

    My questions are:

    1. What is going on that EFB did not update?

    2. Is it possible to fix?

    3. How can I fix it? Please bear in mind that I have never altered or worked on an AFCAD before.

     

    Thank you,

    Ed

     

     

    UAAA file I used to update: http://www.avsimrus.com/files.phtml?act ... d&id=31049

  3. Thanks for the quick reply, Urs. I did ask and he was at a loss to explain why I'm getting that error. Now that it's happening on a different computer it just makes things more confusing. I'm trying to find out if there are other people in my VA who have EFB and in what configuration they run it. Maybe if the error can be repeated by another person it might help track down the root?

  4. First off I want to thank you all (Urs, et. el.) for the best program I have ever found for FSX which is not a plane. If you ever stick wings on EFB I'll test fly it for you, LOL.

     

    For my VA I use an ACARS program to track flights and file PiReps. I have been with the VA using this program for about a year now. Other then the occasional strange crash-to-desktop that couldn't be reproduced the ACARS program has run smoothly. Almost 200 PiReps filed to date. I bring this up because, after installing EFB on my laptop the ACARS started to crash-to-destop whenever it played a sound. It plays several sounds ranging from co-pilot callouts to a ding which notifies the pilot of messages or checks to make sure you are still there flying. At first I thought it was just the ACARS and reported the problem to its designer who is at a loss to explain the problem. I should mention the only programs I ran on that laptop were the ACARS and EFB. I just migrated to a different laptop and was making my first flight with it running ACARS and EFB last night. The same problem happened again on that flight. So I wanted to ask if it is possible there is a conflict between EFB and the ACARS program? The error message I'm getting is posted below.

     

    Error message from old laptop:

     

    Description:

    Stopped working

     

    Problem signature:

    Problem Event Name: APPCRASH

    Application Name: PVA ACARS.exe

    Application Version: 3.0.1.3

    Application Timestamp: 4dd015ba

    Fault Module Name: WINMM.dll

    Fault Module Version: 6.0.6000.16386

    Fault Module Timestamp: 4549be1d

    Exception Code: c0000094

    Exception Offset: 0000547e

    OS Version: 6.0.6000.2.0.0.768.2

    Locale ID: 1033

     

    Error message with new laptop:

    Problem signature:

    Problem Event Name: APPCRASH

    Application Name: PVA ACARS.exe

    Application Version: 3.0.1.3

    Application Timestamp: 4dd015ba

    Fault Module Name: WINMM.dll

    Fault Module Version: 6.0.6001.18000

    Fault Module Timestamp: 4791a7b6

    Exception Code: c0000094

    Exception Offset: 00005502

    OS Version: 6.0.6001.2.1.0.768.3

    Locale ID: 1033

    Additional Information 1: 604b

    Additional Information 2: 7ab7d56502ef8d3407f08d14d5bd1f1b

    Additional Information 3: 411d

    Additional Information 4: e8ffd27320e42f58504131261ba40eee

     

    Any ideas or suggestions?

     

    Thanks in advance,

    Ed

×
×
  • Create New...