Latest TCC 13 echo %@ping[126.96.36.199,1,n] (for different values of n): 0 <= n <= 8: Wireshark shows that the data (payload) sent is actually 60 bytes (the overall size of the echo request packet "on the wire" is 60 + 42 = 102 bytes). 9 <= n < =11: Wireshark shows that the data (payload) sent is actually n - 4 bytes. The return code is -1 ("time out") indicating an error although Wireshark shows the echo reply is received. 12 <= n: Wireshark shows that the data (payload) sent is actually n - 4 bytes (the return code is now correct). Suggestions: make @ping consistent with Windows' ping (-l size) - preferably allowing data sizes starting from 0 and default to 32. Update documentation's "packetsize defaults to 64 bytes. The minimum packet size is 8 bytes" to "data size defaults to 60 bytes. The minimum data size is 5 bytes".