Hello All: - I had a very similar problem a while ago. Peter gave some suggestions that I think are the ultimate cause. I happened to upgrade to Service Pack 2 at roughly the same time I started occasionally using AOL instant messenger. According to Peter, SP2 has limits on outgoing internet connections. I believe AIM likes to take up a bunch. When I stopped using AIM at the same time as glGo the problem ceased. Perhaps you are running some other applications that would also be connected to the internet? I am sure Peter can expand. - Yes, I had the same problem with reloading to an earlier point than listed. Until that is fixed, completely exiting the application and then reopening it should fix that as well. - It does bring up another thought though. I really wish that when a disconnect did occur, there was more explicit notice from glGo than just a line in the telnet window. Your program is always getting better Peter. Thank you from all the go users out there! Best Regards, Kevin Purvis ----- Original Message ----- From: "Jarkko Lindblad" <jarkko.lindblad@xxxxxxxxxx> To: <ggo-discussion@xxxxxxxxxxxxx> Sent: Sunday, January 30, 2005 3:52 PM Subject: [ggo-discussion] Re: big old and forgotten bug >I have now had connection trouble with IGS twice in a few days or so - > the first times for many years I've lost connection. This is rather odd, > since IGS has not crashed, nor my connection died to anywhere else, > including asia, so maybe it might be in part a client problem - I wonder > if you've changed the net code lately?. I also noticed a related issue: > when I finally managed to reconnect, I reloaded the game, and only moves > upto 127 or so appeared on the board though we had played 170 moves - I > checked the game list, and according to it the game had reloaded > properly to move 170. I typed in the moves-command and all the moves > appeared and I noticed I still had some 10 seconds time to make 18 moves. > > -- > Jarkko Lindblad > jarkko.lindblad@xxxxxxxxxx > This all is temporary > > >