I'm guessing my review of the Forerunner at:
www.eskimo.com/~joelm/forerunner201.htm is probably driving some traffic to TopoFusion. It's interesting that Garmin's MapSource won't upload tracks from a Forerunner, but TopoFusion performs flawlessly. Nice work guys...
Anyway, from fooling around with the Forerunner for the past 2.5 months, here's what's happening with the tracks. There appears to be a single track log file in memory. The Forerunner can store 3,000 track points (roughly a bit over 5 hours of data). In addition to the current active track log, the unit stores the tracks for the past 10 runs. These tracks are compressed to a maximum of 250 track points. When you reset the stop watch and then start a new run, the Forerunner compresses and saves the active track log, and starts dumping new track points to the cleared active log. (This info is current as of the latest firmware upgrade. It appears Garmin increased the number of track points and also changed the granularity, collecting more track points over a period of time.)
The Logbook does suck big time, and considering the new data columns, TF is a much more accurate and complete solution in storing Forerunner output (at least for serious athletes). Really about the only thing that's missing in TF is calories burned. (Garmin kind of messed up in making the Forerunner an exclusive running appliance. It's also well suited for biking and cross-country skiing, but all of the metrics in the unit and software are exclusively oriented toward running.)
Any specific questions on the Forerunner, let me know...
Joel