I think it is actually possible to copy and paste from cmd.exe
rather do this though:
(assuming you are in Windows)
ping 196.25.1.200 -t > pings.txt
wait about 30 seconds then press Ctrl+C or Ctrl-Break
The Ctrl-Break breaks out of the sequence temporarily to show running averages and stats. Not much use when piping to file.
Its quite easy actually
I just ran a ping and here are some results (copy-and-paste from pings.txt)
Pinging 196.25.1.200 with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=85ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=70ms TTL=250
Reply from 196.25.1.200: bytes=32 time=70ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=70ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=90ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=70ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=90ms TTL=250
Reply from 196.25.1.200: bytes=32 time=80ms TTL=250
Reply from 196.25.1.200: bytes=32 time=70ms TTL=250
<snip>
Ping statistics for 196.25.1.200:
Packets: Sent = 86, Received = 86, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 110ms, Average = 80ms
Anybody tried an inter-Sentech ping yet? ie. MyWi user to MyWi user?