Error Message

[Fairlight]

Y'all catch dis heeyah?  Kenneth Brody been jivin' 'bout like:
> 
> But, the way that Window's "ping -t" works, it will show you which
> packets went missing, in-line.  Unfortunately, I don't have any
> intermittent lost packets at the moment, but what you would see is,
> within the "reply from ..." series, some "request timed out" messages.

You're right.  To a point.  I semi-forgot it would do that, mostly because
I deal largely with *nix, and you don't get that lame error message, you
observe missing SEQ.  But SEQ also tells you exactly how many packets went
missing for that event, in realtime.  Again, if you do a long-term run, you
may have missed one that you didn't notice and your count may be off.

Further, you may be staring at several screens or an entire buffer worth of
"Request timed out" followed by an intermittant success or two, followed by
a string of timeouts, followed by another few successes.  Depending on the
scale of the outage, you can't tell how intermittant it was unless you're
manually counting either/or, or unless you -only- had it up for the event
and can rely on the grand totals or percentage to directly correlate only
to that event.  

I just -really- prefer an exacting diagnosis where I can observe exacting
data in realtime.  Windows' ping isn't exacting enough for my tastes.  This
may seem esoteric, but it does have some relevance IMHO.

mark->