Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Major_Bloodnok

Members
  • Joined

  • Last visited

Everything posted by Major_Bloodnok

  1. Hi again - I think we had this issue before - IIRC you use Webroot? In which case the following .exe I found were missing after the update and should be added to the Webroot "PC Security- Block/allow files" "Fenix.exe" (in FenixSim A320 Folder) "FenixDisplay.exe" (in FenixSim A320/deps folder) "FenixSystem.exe" (In the same folder as above) After which I had to go back into Webroot (Click "Utilities/System Control/Start") this will show the active processes. I noted that the above 3 .exe files were present but were under "monitor" - I changed them to "allow". I got the EFB back after that.
  2. The problem that "lehbird" had was similar to mine - possibly linked to our both using Webroot as an antivirus/firewall/etc and that this program may have altered some permissions to the Fenix .exe files after the BFU. That was the "utilities" I was referring to. If your Airbus hasnt got any detail/BFU this may be a different issue - I would suggest contacting the guys at Fenix - they answered me very quickly and had plenty of suggestions in order to try and solve the problem (sadly -the problem was me....)
  3. Sorry - I made a mistake - its not the firewall. I went to "utilities - system control" "press start" you will see a list of active processes. When I looked I found "FenixDisplay.exe" and FenixSystem.exe" on the list - but - they were marked as "monitor" - I changed them to "allow" After this I checked on the "pc security - Block/allow files" - these two .exe files were also on the list - something that hadnt been the case before the BFU. Hopefully that will do the trick.....
  4. Hi - I had the same - had excellent help from Fenix in order to troubleshoot - but without success. As a last resort I disabled my anti virus/firewall ( Ive got Webroot, for what its worth) and the EFB connected. I found that it wasnt just the "fenix.exe" in the A320 folder that needed to be allowed - it was also "FenixDisplay.exe" in the A320 "deps" folder as well as "FenixSystem.exe" in the same folder. Somehow these two executables were shown as "monitor" in my firewall instead of "allow" - changing them enabled the EFB. I also hadnt had this issue prior to the BFU, maybe the firewall in your case?
  5. Christopher - MK´s LSZH is 20% off on ORBX...
  6. Take a look at this - its for the A320 but gives a good insight into sfc etc for the different types of engines offered on the A320 family. http://www.team.aero/images/aviation_data_insert/Owners_OperatorsGuide_A320.pdf
  7. Hi. Take a look at this:- http://www.concordesst.com/graphics/gear/frontgearbig.gif
  8. I am a long-time lurker and very infrequent poster on the AVSIM forums but from time to time wander through this particular sub-forum cannot believe that it continues the way it does. If I may, Mr. Shuttleworth, quote from the forum frontpiece:-"This forum is established for owners to share hints and help and for non-owners to ask questions of the owners on performance, techniques and guidance."I believe that the official Level-D forum caters for the first part, so the original posters question, IMHO, would be permitted as outlined under the second part of the above sentence.So what was the point in the standard "see the official forum etc..." reply, and then to add the crass action of revoking access to the Level-D forums to a Level-D sim member?I am also a Level-D 767 owner, and member of the Level-D forums, by the way, and support fully any action against piracy or the questions that arise from obvious "rogue" LDS767 owners, but quite frankly the continual mantra offered by Mr. Shuttleworth should result in the closing of ths particular forum.Tim Evans
  9. Sir,I will give this a try tonight, and, if sucessful, I will owe you a very large beer!!!!Many thanx for the replyTim
  10. Hi Peter, I seem to have a further problem.....it seems that I am unable to start FS9 at all, I receive a message saying "Flight Simulator Registry has not been found on your system" does this mean the dreaded re-install....???kind regrdsTim
  11. OK Thanx Peter Ill give it a try tonight and let you know how I get on, thanx for the replyRegardsTim
  12. Good morning from sunny Portugal, long time lurker and very infrequent poster here.Had a major hard drive crash over the weekend, thankfully FS9 on separate drive.After recovery, I remembered that there should be a FS9 file on the c drive, something like \Flight Simulator Files.....My question is, will this file be automatically re-created when FS9 is started or would it require copying from one of the FS9 Cds, (anyone know perchance which one??)many thanx in advance for any replies/help.Best regardsTim
  13. OK... first post but perhaps I can help out here, (having found out myself last night).The CDU is somewhat like the Airbus in that it has two arrows pointing up and down beside the keyboard. Use these to scroll up and down to the last entered waypoint. To enter any single waypoint, you can enter the name on the scratchpad and insert on the lsk that states "flightplan discontinuity" If you are going to enter an airway, you must use the LAT REV page. To access that page, click on the lsk next to the last entered waypoint. (this cant be done by clicking next to an airport). Then you can enter the airway and the waypoint accordingly.I hope this is of help, nothing like frustration to mess up your flightplan..... :( Tim EvansSomewhere by the sea.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.