I have downloaded and installed Pingplotter 2.20 on 4 different machines tot see if it serves my needs:<br><br>1) Asus P2B + PII-350 + 128 MB running win98 <br>2) Chaintech 5SIM + P233MMX + 128 MB running Win89<br>3) Asus P2B + Cel 600 + 128 MB running W2K server (cable internet gateway)<br>4) Aopen AK33 + Duron 600 + 128 MB running windows 98<br><br>In runs without problems on machines 1,2 and 3. On machine 4 it behaves odd. The first 3 or 4 pings will show normal results but after that respones go to 500 ms and up. <br><br>So I uninstalled v2.20 and went back to PingPlotter v. 2.03 which works fine. <br>Apparently there is something in v. 2.20 (compared to v 2.03) that does not like the AMD DUR or the Aopen AK33.<br><br>Any help appreciated.<br><br><br><br><br>

Hi Jan.<br><br>One of my test machines here is an AMD duron 600 (not sure what kind of MB) with 128 megs of RAM running 98 SE. I've never seen any problems where 2.03 and 2.20 give different results - the underlying core "ping" engine changed very little between the 2 versions.<br><br>I'm interested in knowing how reproducible this problem is. 2.03 and 2.20 will actually both install on the same system at the same time. Is there any chance you could install both of them (different directories, of course), and run them simultaneously, then send me some screenshots of the problem? I'm quite interested in figuring out what's going on here.<br><br>Thanks! <br><br><br><br>

Will do as you requested.<br><br>

I cleaned out all occurances of Ping Plotter.<br>Reinstalled v2.03 and v2.20. Both give the same results now. Compared to Windows' own ping and the results from <br>the other machines the values it shows are correct.<br>Beats me why it started to misbehave and haven't a clue why it works fine now....<br><br>

Thanks for the follow-up. Let me know any possible details (destination address, image of the trace, etc.) if you see this again (or any other problem).<br><br>