OK. I'm back. I dunno who's responsibility (at least at that time) so see that JAVA is installed correctly, but I understood that bar to be telling me it WASN'T installed so I kept trying to fix it (JAVA)
The new modem failed after 2 hours. Cable OK, no internet or phone. I reset it and it hasn't bothered me again.
That Texas test is now running on Firefox and Chrome, but neither one is asking me for that SID code. I put a message on the ISPgeeks forum.
They say that I can click on the test results to get a detailed analysis and download that. It opened a new tab at connectionanalyzer.com but I don't see any option to download the data. I can do a capture tho:
[TABLE="class: border, align: center"]
[TR="class: font12"]
[TD][/TD]
[/TR]
[TR="class: font12"]
[TD][TABLE="class: border, align: center"]
[TR="class: font12"]
[TD]Test Type:[/TD]
[TD]
Application Speed[/TD]
[/TR]
[TR="class: font12"]
[TD]Location:[/TD]
[TD][/TD]
[/TR]
[TR="class: font12"]
[TD]Download Speed:[/TD]
[TD]
24500 kbps[/TD]
[/TR]
[TR="class: font12"]
[TD]Upload Speed:[/TD]
[TD]
1840 kbps[/TD]
[/TR]
[TR="class: font12"]
[TD]Speed Consistency:[/TD]
[TD]
92 %[/TD]
[/TR]
[TR="class: font12"]
[TD]Round Trip Time:[/TD]
[TD]
45 ms[/TD]
[/TR]
[TR="class: font12"]
[TD]Max Delay:[/TD]
[TD]
254 ms[/TD]
[/TR]
[TR="class: font12"]
[TD]Average Delay:[/TD]
[TD]
1 ms[/TD]
[/TR]
[TR="class: font12"]
[TD]Bandwidth:[/TD]
[TD]
24500 kbps[/TD]
[/TR]
[TR="class: font12"]
[TD]Forced Idle:[/TD]
[TD]
24 %[/TD]
[/TR]
[TR="class: font12"]
[TD]Route Concurrency:[/TD]
[TD]
1[/TD]
[/TR]
[TR="class: font12"]
[TD]Test Type:[/TD]
[TD]
s / s[/TD]
[/TR]
[TR="class: font12"]
[TD]Round Trip Time Consistency:[/TD]
[TD]
57 %[/TD]
[/TR]
[/TABLE]
[/TD]
[/TR]
[TR="class: font12"]
[TD][/TD]
[/TR]
[TR="class: font12"]
[TD][/TD]
[/TR]
[TR="class: font12"]
[TD][/TD]
[/TR]
[TR="class: font12"]
[TD]
2 connection problems found, click the
to learn more.
[TABLE="class: border, align: center"]
[TR]
[TD]
MSMD01: TCP is waiting too long for data
The test recorded a TCP maximum delay that exceeded the natural TCP forced idle delay as a result of the connection's trip time. This indicates that there may be problems with consistent data flow between the server and the client. A poor data flow QoS reading is also likely if the max TCP delay is much higher in comparisons to the trip time. Common reasons for this type of problem are packet loss and duplicates. The test graph view will show the TCP delay over the time of the test. Height and width of the 'orange' delay line shows the delay consistency.
Learn More
[/TD]
[/TR]
[/TABLE]
[TABLE="class: border, align: center"]
[TR]
[TD]
MSTR02: The trip time for this connection is too erratic
The test recorded erratic trip times between server and client indicating congestion/regulation difficulties on the connection. Erratic trip times will usually cause problems with data duplication which will impact throughput speed. This usually results in a lower speed data flow quality measurement.
Learn More
[/TD]
[/TR]
[/TABLE]
[/TD]
[/TR]
[TR="class: font12"]
[TD][/TD]
[/TR]
[TR="class: font12"]
[TD]I ran 4 tests, Firefox and Chrome at TX and GA. Texas Chrome was 18.8 Mbps, the other 3 were over 21 Mbps. The difference was the quality of service results.
FF - TX 75% yellow dot 21.3 / 1.82
FF - GA 92% green dot 26.9 / 1.83
CH - TX 77% yellow dot 18.8 / 1.83
CH - GA 50% red dot. 26.1 / 1.83
[/TD]
[/TR]
[TR="class: font12"]
[TD]
Jim
[/TD]
[/TR]
[TR="class: font12"]
[TD][/TD]
[/TR]
[TR="class: font12"]
[TD][/TD]
[/TR]
[TR="class: font12"]
[TD][/TD]
[/TR]
[TR="class: font12"]
[TD][/TD]
[/TR]
[/TABLE]