Your output is going to be sort of worthless for troubleshooting.
Your chopping out the most important feature of Ping which is latency info and failed Ping count which you want to see 0% loss. From looking at what you want. It could say that your connected but yet you could have a major network issue going on.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\dave>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\dave>
Trying to understand why Ping as it is is not good enough?
As far as shaping the output to say whatever you want, it can be done, but not in real time. There would be a slight delay in what is measured and then what is parsed as the output to the display. To get rid of this delay would require writing your own Ping program so that the output is as you want it without having to reshape it to an alternate display layout to user.
