ON Tuesday, October 26, 2004, 6:03:09 PM, you wrote: PJ> I'm coming in late on this, but FWIW, I also experienced this kind of PJ> "freezing" in TB!, version 2.12 I think it was, and it made composing PJ> emails almost unbearable. I ended up reinstalling my OS-- and PJ> eventually upgrading to XP. I'm not suggesting an OS upgrade :-) PJ> --just that I believe it was not a TB! problem (and that in my case, a PJ> major system house-cleaning seemed to stop the freeze).
Pat, I fully agree with you. These temporary freezes are usually caused by a communication process that is not getting connected in some way. Communication process has to be seen in the broadest way possible so not only dailup or Ethernet/Adsl but also Wifi or connecting to your printer or even connecting to a drive (watch how long Windows can "freeze" if you are trying to read something from a floppy. To complicate matters, it can also happen because of a badly installed piece of software in the communications pipeline. anti-virus software or firewalls have caused there share of headaches. How do you solve these problems? By carefully eliminating things. I ussually start by looking at which process takes up most of the processors time. You do this in W2000 and XP by pressing Ctrl-Alt-delete and then selecting the "Processes" tab and sort them on CPU time. Just wait for it to pop up. -- Best regards, Gerard -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I don't enjoy playing video golf because there is nothing to throw. Using The Bat! v3.0.1.33 on Windows XP 5.1 Build 2600 Service Pack 2 ________________________________________________ Current version is 3.0.1.33 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
