Seemingly randomly, if I "reset and restart" a trace to a hop like updates.zdnet.com, I'll occasionally get a few "Can't get a time for a sample that's not been done yet!" errors near the end of the first pass. It's difficult to reproduce, but it seems to happen more when the trace interval is low (1 second or lower) and you interrupt an active trace by doing a "reset and restart" a couple of hops into it, during a pass.<br><br>Let me know if there's anyway to get better information about this to you. :-)<br><br>*Updated*: A low "time interval between hop traces" (25ms or so) might help, too, as that's what I have mine set to.<br><br>Jason<br><br>

Duplicated here. Thanks!<br><br>

This has been fixed in beta 5.<br><br><br>

I am seeing something similar under v2.21 Beta2. It seems to occur most often when there are 255 previously recorded files in the directory. <br><br>Thanks,<br><br>Corey McCormick<br>corey@citgo.com<br><br>