Have been having problems with logic for the past 3 to 4 revisions whenever I run "callbook to log" and/or telnet especially while using spots and spot alerts windows. I'm currently running LOGic 9.0.81.

My OS is Win7.

There seems to be several problems. After logic runs for a few minute the mouse will not show any of logic's windows or when the mouse will show I cannot select anything. Sometimes I cannot even close logic except by using the Task Manager. Even when it will shutdown using the Logic's exit, it comes right back up with the same problems immediately. However, usually logic will not start and has to run its cleanup process and then index everything again like a first time load. It makes no difference what telnet DX cluster I log into.

I am on a network (hard wired to my router) and logic is the only program I have problems with.

Logic runs fine in its logbook mode and even when connected to my radio (IC-756PROII). But as soon as I try to use the advanced features mentioned above the problems start.

I have no problems with other programs that use online callbooks or telnet DX clusters.

Anybody have any ideas?

Dave, K7PDW

I'll try turning off QRZ.com. I've had problems with telnet turned off too. I'll turn off QRZ.com as a start point.
I have set the telnet server to "set dx filter spotterstate=[ut,co,wy,id,nv] and not skimmer". This cuts the spots to 10 or less per minute even on a contest day when the traffic is very heavy. I'm not using LOGic's pre-filters at all. I did this thinking that perhaps LOGic was getting overwhelmed. I know I do when telnet sights are left with all filters off.
Thanks for the help.

I have only LOGic's and the FCC's databases enabled. It seems to work fine when I have the telnet and spots log with alerts turned on until I look up something using the callbook window. Then it hangs for a while then the behavior becomes unpredictable. With the telnet off it takes 15 to 20 seconds for the callbook to respond even with only LOGic's callbook enabled and after LOGic has been run from a computer cold start. I did notice that the first call I looked up came up in about 5 seconds which is not bad but the next call took about 10 seconds (not too bad) but everyone after that took 15 to 20 seconds. Without the telnet running the behavior remained predictable but slow. It seem to me that when the telnet and the callbook are both running there are problems. I have a 10 Meg internet connection that is used only by me so I don't think it is the connection. The internet connection does not give me problems even when I stream video or music.

I appreciate the help. I think we're making progress. As is always the case, it takes some time to find the root cause of the problem when it comes to software.