ABCpt
Expert Member
- Joined
- Oct 20, 2009
- Messages
- 3,269
:wtf:
Was it Control.Engine or Control.engine? If it was the latter, I have no idea what has happened?
Z
Sorry, cannot remember. Will check tonight and give feedback.
:wtf:
Was it Control.Engine or Control.engine? If it was the latter, I have no idea what has happened?
Z
Sorry, cannot remember. Will check tonight and give feedback.
That is very strange indeed!
Do you perhaps know what version of java you are running?
Z
Looks like 1.6.0_27.
That might be the issue. I'm compiling for 1.7. Please would you try update java and see if the problem reoccurs
Z
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 7ms, Average = 7ms
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 10ms, Average = 7ms
Oops, it displays the result of the first ping.@Zertop
Cool utility you've created.
I've tested the latest utility and found that it doesn't report the maximum ping correctly.
Following is the code for the test.
/Snip
@Zertop
Cool utility you've created.
I've tested the latest utility and found that it doesn't report the maximum ping correctly.
Following is the code for the test.
Zertop's "Is it my Line" Results
Date/Time: Thu Sep 17 18:19:17 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 7ms.
Your maximum ping was 7ms.
Your local download speed was 478Kbps
Your international download speed was 506Kbps
Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP
Detailed Report:
Code:Pinging 155.239.255.250 with 32 bytes of data: Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Ping statistics for 155.239.255.250: Packets: Sent = 1, Received = 1, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 7ms, Average = 7ms Pinging 155.239.255.250 with 32 bytes of data: Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=10ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Reply from 155.239.255.250: bytes=32 time=10ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=7ms TTL=63 Ping statistics for 155.239.255.250: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 10ms, Average = 7ms
Oops, it displays the result of the first ping.![]()
It is a pleasure.Hi!
Thanks so much. Was a bug which I didn't even see haha,
Z
It is a pleasure.
I have another question though. Is there a limitation on local and international download speeds?
Whenever I do a test with the utility it doesn't go far beyond 500KB. Tests on speedtest.net constantly report speeds of 8.6Mb.
That is a pity. It is very nice to have all the test in one package.I'm actually planning on removing it again. Java doesn't do a very good job of accurately calculating speeds, so it's not very practical for this kind of test. This is probably the issue you're describing too! I think I'll leave this tool for the line, and the other for downloads etc
Z
It doesn't require installation. Just download the new program and your good to go. Make sure you have the latest Java version installed.How do I re-install this for WIN 10?
It doesn't require installation. Just download the new program and your good to go. Make sure you have the latest Java version installed.![]()
Is Java installed? Are you testing it with an ADSL line? Are you able to ping 155.239.255.250?Doesnt work on my WIN 10 64 bit. Tried that.
Is Java installed? Are you testing it with an ADSL line? Are you able to ping 155.239.255.250?
Just making sure that you aren't using it in 3G/LTE failover mode.Will try that this afternoon, and uhm, yes, it is an ADSL line.