Everything was on time and without a problem. I met at a hotel conference room being hosted by ARINC where the discussion was "internet" connectivity to the plane. It was very interesting.

A brief intro in the hallway and we grabbed an outlet in an empty room for what was ultimately a very casual, friendly, and worthwhile 2 hours.

All work was done on the host's system. The FDR data was loaded and we got right to seeing what we could see.

There were no problems or delays in loading the data and seeing that the file is good.
About 11-13 flights were evident just by displaying airspeed in graph for the length of the file.

I let the host run with show. This was the first several minutes of our meeting, and their was still that 'silly tension' in the air. More so, the many questions he surely was pondering about me and my data and just what was I doing.

The first close up {after checking a few parameters for definition} was height at the end. Radio Alt was 273 Feet. A lot of time was spent looking at different parameters.  Checking my list of Short must-see parameters, as well as comparing with the NTSB CSV.

In about 10-20 minutes there was a conclusive moment when it became clear we could get 'close' to the NTSB data, but that was about it. There was no impact recorded, the basic numbers weren't matching.

We tried to export CSV the entire file for all params but gave up after a long time. We estimated the resulting CSV would have been huge and taken hours to process.  You wouldn't even be able to begin to look at it unless you put it in a database.  It would have been great to have, but oh well.

I asked many questions and the conversation took to many off-topic points, but we covered a lot of insightful information.
Some points

AA77 (and/or like models) do not have GPS.  'besides, all that's used for is the in flight map for the seats' -- host

Lat/Lon is by interia systems. The 20Minute NTSB error was discussed. Possible with violent airframe events to knock the interia out of sync. But this could not affect the entire flight. i.e. any violent movement can not error Lat/Lon data prior to itself. (unless it occurred in a previous flight, and was un-fixed for this flight)  I couldn't map the corridantes right there, but they looked close.  What a surprise this gave me later on.

Pressure//Baro was covered pretty quickly.  I didn't get a comment on the Animation flaw after I mentioned it.  We discussed differeent aspects of altitude detection.  There was no conclusion other then the alititude is what it is, and the data does not show any crisis or impact.

We discussed what we can and can not see with this software. One key point is that this software is not intended for accident investigation. Do not think this implies a shoddy piece of code however.  These people have been in the recorder business when 11 parameters was a new thing. 
The software only processes full subframes. There is was no binary view.
The parameters data frame mapping configuration used was a 757-3b.  The host's copy was used most commonly and 'every day'. Differences in revisions are small and view. { In the grand scheme of FDR's and the Airlines there will never be common interface though. There will never be a open recorder standard. Propietary hardware/software, strict confirmance for safety/performance/profit, and other reasons}  I did not ask for a copy of his Parameter file. At most times, we compared my layout with his and it was a good match.  We compared about 15-20 parameters, we found 1 that didn't match and it wasn't recorded in the raw file anyway.  If anyone wants to see a real 757 data frame layout, good luck.