Freeware: Electronic Flight Bag Boeing Style for FS9, FSX and X-Plane

[nricky]

Danke Peter, gut gemacht.

Cheers Norbert

[pebo]

Very nice!

As a b777 builder I sure am looking forward for the update on this.

Have tested the 0.6 version and it is looking real promising.
Placed in the proper place in my b777 cockpit it fills a big ugly gap

Keep us updated!

[skino]

New Version: 0.7 , working with FSUIPC/XUIPC/WideFS



Music: "L'amour" by Paolo Zanarella

Download: http://boefb.webnode.com/blog/

A manual in English comes in the next days. The Airbus/GA Version (iPad-style) is online as of tomorrow afternoon.

[yoss]

Very cool, Peter
Gouing to be a 'must to have' in any simcockpit

Yoss

[iwik]

Hi Peter,
My eyes lit up when i saw GA. Had a lok at the video and noticed the Checklist
for the Baron58. You have just made my day. The EFB is amazing, have a spare
touch screen waiting for a task, its just been found . Look forward to the Airbus/GA release.
Thanks
Les

[skino]

The GA and Airbus Version of the EFB 0.7 is online



The Download is here http://boefb.webnode.com/

This is an update. BoEFB must be available. The two files hPad.Exe and Pad.Exe simply copy in the BoEFB folder and then starting BoEFB, hPad or Pad alternatively.

BoEFB is the BoeingStyle EFB, hPad ist the Program in the Video above.

For running on Ipad or Android Pad (with "Air Display") is the Pad.Exe (frameless, maybe for Laptop to)



Made EFB Checklists:
preparing a new folder in the data/ECL folder who is called like the check list (PMDG 737 or WILCO A340 or ...or...). Making simple .TXT files in this folder.

For every checklist (Befor Starting, Starting . . . ) making a TXT of one's own and typing in the data or c&p from the original HTML Aircraft Checklist. The first line starts normally. All other lines must start with @ . At most 16 entries per check list are possible; only 16 buttons are available in the EFB. Please split longer checklists (Starting 1, Starting 2 ...).
Writes the names of all the checklists into a Main.TXT-File without the .TXT but with comma between the names and without Enter. All name must be in a single line. like: Bevor Starting,Starting 1,Starting 2,Taxi,

Have a look at the sample checklist for the FS2004 default B58 in the \Data\ECL Folder.

[pebo]

I am not able to see the documents in \ DATA \ DOCS or see the integrated file browser in the system.

Is the above suppose too be working and ready in the beta v.0.7?

I get the following message when clicking the “Documents” button:
boefb_error.jpg

[skino]

Have you installed the Adobe reader? Where exactly does your BoEFB folder stand and which Windows do you have?
I cannot cause the fault. I get an empty screen but no error message even if no files are into DATA/DOCS. I suspect this your Adobe reader is faulty or too old.

I had written it on the web page but only in German:
For the PDF shows the Acrobat Reader is necessary. However, he doesn't have to be the standard PDF reader, installed only.

Have unfortunately forgotten to write this also here. Excuse me

[pebo]

You have nothing to excuse as I’m more than happy that someone is taking time to make this application that I have been missing in my B777 sim-cockpit.
I’m the one to be sorry as I guess there to be some problem on my part, but I really do like what I see so far and love to have it working properly
Everything else are working properly.
Finding the fault might be of use for you and others, if one can determine what is wrong on my side.
The BoEFB is on the root of my C drive: C:\BoEFB\....
I use the Acrobat Reader version 9 (and have run a “repair” on it, just in case) on a 32bit Windows7 (newly updated) on a laptop.
The entire fault dialog as follows:
--------------------------------------------------------------------
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.InvalidOperationException: An error occurred creating the form. See Exception.InnerException for details. The error is: Error HRESULT E_FAIL has been returned from a call to a COM component. ---> System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
at System.Windows.Forms.AxHost.CreateWithoutLicense(Guid clsid)
at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid clsid)
at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
at System.Windows.Forms.AxHost.CreateInstance()
at System.Windows.Forms.AxHost.GetOcxCreate()
at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
at System.Windows.Forms.AxHost.CreateHandle()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.AxHost.EndInit()
at WindowsApplication1.Documents.InitializeComponent()
at WindowsApplication1.Documents..ctor()
--- End of inner exception stack trace ---
at WindowsApplication1.My.MyProject.MyForms.Create__Instance__[T](T Instance)
at WindowsApplication1.My.MyProject.MyForms.get_Documents()
at WindowsApplication1.BoEFB.Button6_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
BoEFB
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/BoEFB%20Alpha%2007/BoEFB.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
AxInterop.AcroPDFLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/BoEFB%20Alpha%2007/AxInterop.AcroPDFLib.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

In the hope of someone to be able to "translate" / desiffer the above

Regards
Per

[notgotaclue]

Hi,
I am going to be picky again with spelling
You have spelt "Descent Planner" as "Descent Planer", also "Hide delete button" as "Hidde delete button".
If I had a hat I would take it off and doff it to you for coming up with a fine piece of software.....
Allan.