iFly GPS Forum

We have a new Forum!  Go here to get started: https://adventurepilot.community.forum.  
The new forum is easier to use and much more capable than the old, we hope you will join our community! 

Below is a copy of the old forum. This will remain available for a short period so you can access and review the information contained here. To continue a conversation, or start a new one, please register and create a post at our new forum location.
HomeHomeDiscussionsDiscussionsiFly Wish-ListiFly Wish-ListMultiple update filesMultiple update files
Previous
 
Next
New Post
10/8/2011 5:00 PM
 

I tend to build multiple update files when possible. For example I'll select and create an update package of all needed sectionals, then I'll create an update package of TEC's, then the latest software change, etc. When I search for update files, it finds all of them, and says something like "Multiple update files were detected I'm going to use XXX.zip as the update" <OK>. So far it's all fine. My question/request is to have the unit, once the first update file is unzipped and installed, re-search the flash drive and detect the next (group) of update files and choose one to update, when that one is finished, search for another.

While the current method of letting the aviation software start and using the menu to find each file is tolerable although time consuming, it would be nice to have it streamlined a bit.

 
New Post
10/11/2011 12:42 PM
 

Just out of curiosity, do you really load enough data to make multiple files necessary? I used to break up my updates until I realized that even with everything lumped together, I was "only" using 400MB, which is well short of the 2GB limit.

One potential issue with having the iFly automatically incorporate multiple update files is if someone downloads an update file but doesn't immediately apply it, and then it gets dragged along weeks or months later with another batch of updates. If the iFly isn't smart about it, you could potentially have older data overwriting newer data. I'm sure that Walter, et. al. can include data in the update file header and logic in the update process to ensure that doesn't happen, though.

 
New Post
10/11/2011 3:47 PM
 

I usually update all the files that are being updated. I also generally make a separate file for each category (sectional, TEC, plates, software, etc.) so if something goes wrong with one of the files I can just replace that file. In addition, making several smaller files lets me not "waste" so much download in a rare instance my download gets interrupted, and I have to restart it. This isn't really necessary, but it would be a bit more convenient for myself, and at least one other that makes several smaller update files instead of one large one.

As for overwriting a newer file with an older one, I would first off think I would be aware of what's on my drive and what I want to upload. But since you mentioned it, it might also be nice if, in the update process, the software would check and ask us if we were aware we were attempting to replace newer material with older material.

 
New Post
10/12/2011 7:17 AM
 

Different folks, different strokes, I suppose. The hassle of always having to go through the selection/compilation process and then download multiple files unnecessarily would, for me, far outweigh the hassle of re-clicking the download button on the off chance the download failed (which, I think, last happened to me circa 1998 or so)... Of course I understand if you're updating everything, then multiple files are probably necessary to work around the 2GB limit.

 
Previous
 
Next
HomeHomeDiscussionsDiscussionsiFly Wish-ListiFly Wish-ListMultiple update filesMultiple update files