Jochen,

Here is what you get from a Windows 95 workstation.
Notice that a valid ping first, then run script... Looks okay.
Then ping an address that times out, ping shows REQUEST TIMED OUT
Then run script... Still says it replied to the ping request even though it DID NOT.
That is because @error is not being set. i.e. There is no %errorlevel% set on
Windows 95, thus this method can not be used.

C:\SCRIPTS>ping 192.168.1.101

Pinging 192.168.1.101 with 32 bytes of data:

Reply from 192.168.1.101: bytes=32 time=1ms TTL=128
Reply from 192.168.1.101: bytes=32 time=1ms TTL=128
Reply from 192.168.1.101: bytes=32 time=1ms TTL=128
Reply from 192.168.1.101: bytes=32 time=1ms TTL=128

C:\SCRIPTS>kix32 9x2.kix
192.168.1.101 replied to the ping request!

C:\SCRIPTS>ping 139.104.117.95

Pinging 139.104.117.95 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

C:\SCRIPTS>kix32 9x2.kix
139.104.117.95 replied to the ping request!