It seemed to be a routing problem in SprintLink when I tracerouted it right after it died. Died in SprintLink Chicago somewehere, then came back with lots of extra hops in the middle a few seconds later, and died some more and did the same a couple times while I was playing. Actually if I scroll up a bit I should still have it in one of these terminals... traceroute to sage.real-time.com (206.10.253.60), 30 hops max, 40 byte packets 1 f6-0-0.cr1.qui.cent.net (140.186.18.193) 1 ms 0 ms 0 ms 2 sl-gw9-nyc-6-0-TS11.sprintlink.net (144.232.173.1) 8 ms 8 ms 8 ms 3 sl-bb10-nyc-4-0.sprintlink.net (144.232.7.93) 8 ms 8 ms 9 ms 4 sl-bb12-chi-10-0.sprintlink.net (144.232.18.53) 29 ms 29 ms 33 ms 5 144.232.26.5 (144.232.26.5) 29 ms 29 ms 28 ms 6 sl-gw22-chi-8-0.sprintlink.net (144.232.10.10) 29 ms 30 ms 29 ms 7 sl-bb10-chi-10-0.sprintlink.net (144.232.10.9) 30 ms 30 ms 32 ms 8 sl-bb11-chi-9-0.sprintlink.net (144.232.10.50) 29 ms 29 ms 28 ms 9 sl-bb12-chi-8-0.sprintlink.net (144.232.10.2) 28 ms 29 ms 27 ms 10 sl-bb13-chi-8-0.sprintlink.net (144.232.10.53) 28 ms 28 ms 33 ms 11 sl-bb3-chi-0-0-0.sprintlink.net (144.232.10.154) 28 ms 27 ms 28 ms 12 sl-gw10-chi-0-0.sprintlink.net (144.228.50.14) 29 ms 28 ms 28 ms 13 sl-rtent-1-0.sprintlink.net (144.228.52.126) 39 ms 39 ms 48 ms 9 hops just within SprintLink Chicago, quite amusing. On Mon, 4 Sep 2000, Zachary Uram wrote: > Ask anyone playing on Continuum in past 3 hrs about the annoying > freezes :( The game freezes and you can't move, then game resumes > and you find yourself accelerated ahead in time. I timed the > freezes and the last 3 were approximately 24-26 seconds in > duration. It is even worse than lag burts! Whoever runs Continuum > please investigate this most vexing problem. > > SDG, > Zach > > uram at cmu.edu > "Blessed are those who have not seen and yet have faith." - John 20:29 > > _______________________________________________ > vanilla-list mailing list > vanilla-list at us.netrek.org > https://mailman.real-time.com/mailman/listinfo/vanilla-list >