------------------------------------------------------------- This product includes software developed by the University of California, Berkeley and its contributors. ------------------------------------------------------------- What is it? ----------- This is the FreeBSD ping compiled for OS/2. There was another compilation of this program but it did not appear to work with Warp v4 / TCP/IP v4. This one seems to work without problem. (Note: "work" == "works for me") John Smyth (xy3@usa.net) ----------- Why bother? I (and many others, it seems) like the -i <#> option, allowing for a ping interval. Many ISPs like to hang up when there is a loss of activity for a # of minutes on the line. Using this allows a ping every # seconds (500, for example) thus keeping the connection active. ping -i 500 ibm.com Hints ----- I don't advise replacing the OS/2 ping.exe program with this one, although you can if you want. Some applications (WBI, for example) seem to rely on the OS/2 ping and its syntax during installation. I have renamed mine to 'uping.exe' and put it in my path. Changes ------- This is simply the first FreeBSD ping.c I could find on the net, and recompiled for OS/2 with EMX 09c. It isn't optimized in any way since the following is returned when optimized, and I don't have the patience to figure it out. :) \emx\lib\sigbsd.obj(sigbsd.obj) : error L2029: '_uflags' : unresolved external I made 2 small changes for my own use. I'm only releasing this since no one else seems to want to. - Return codes (error levels) are based on the % of pings that fail to be returned. - return code 0 means no pings failed, and the connection is good - 0 < return code < 100 means that the connection is 'iffy' - return code 100 means all pings failed, and connection can't be made - -h was added to hide the header, making a cleaner view in rexx scripts that want to ping and handle return codes, but not display any of the ping program. Example REXX Script ------------------- If you have friends/colleagues with static IP addresses, and want to know if they are connected while you are, here is a simple script to run. Edit the 'hosts' array and add as many hosts as you want, starting at 1. - sample.cmd is included.