iFly GPS Forum

The USB drive is only found upon initial boot. If I try to do an update while the IFly is already on it asks that I make sure the USB device is pushed in all the way or use another USB drive

Walter -

I was experiencing this same issue, but booting with the flash drive in place worked well. Until today.

Now I seem to have a new issue. When the iFly boots up with the flash drive inserted, I receive an error. Without the flash drive inserted, the iFly boots up normally and works fine. So, the device is usable, but I can't seem to update it. Here are details on the error. It reproduces every time I boot with the flashdrive inserted. I don't have another flash drive handy and so have not tested other drives.

The initial window says: "Error An unexpected error has occurred in esectional.exe."

If I select the "details" button, I get a very lengthy string of information, but here it is (apologies for the length):

Error
esectional.exe
NullReferenceException
at
Gis.LineQuadTree.CreateFromShapeData(ShapeData shapedata, Int32 maxPerQuad)
at
AviationMap.AviationMapControl.SetupStates(String dataDir)
at
AviationMap.AviationMapControl.SetupGeographicLayers(String dataDir)
at
AviationMap.AviationMapControl.CreateVectorLayers(String datdDir, ShapeData tfrData, AirportQuad airportQuads, MetarQuad metarQuad)
at
AviationMap.AviationMapControl.Initialize(String chartBoundsFile, String imagesDir, String sectionalsDir, String lowenroutesDir, String tacDir, String dataDir, AirportQuad airportQuads, MetarQuad metarquad, ShapeData tfrData, IBootLog bootlog)
at
Main.SetupAviationControl(BootLog bootlog)
at Main.Startup()
at Main.Form1_Load(Object sender, EventArgs e)
at
System.Windows.Forms.Form._SetVisibleNotify(Boolean fVis)
at
System.Windows.Forms.Control.set_Visible(Boolean value)
at
System.WIndows.Forms.Application.Run(Form fm)
at Program.Main()

-- Chris

Chris, That is a strange problem. But if you have an update package on the USB stick it should still install; that happens before the iFly software executes.

Chris & Kris, I've given both of you access to our Beta Updates page (under the Updates menu item). If you will please install version 5.15, we think that may correct this issue. (I say "may" because we've not been able to reproduce the bug...but we've made a change to the code based on a best-guess about what might cause this problem). If 5.15 gives you any problems, you can simply roll back to 5.14 by creating a software update package from our regular Create Update Package page.

Thanks!
Walter