I have checked different things.There was this IPcheck parameter that could cause problems, but it was OK. Then there was this sessions save file location that could be problematic but that was also OK. I doubled the timeout value from 2 minutes to 4 minutes, but I don't think that this is the problem either. Then there are three possible causes left (might be more though):1. You might have a bad connection2. Your computer won't allow the chat to set a cookie and then the chat doesn't recognize you and boots you3. Our host is overloadedWe'll have to continue our investigations. It might be possible to find another chat solution, but I think it would be best if it would be one that we can connect to our user database so that no one can login with someone else's username.
Hi, Wonky.Just ran a test with no problems using entries with several lines of script. My search engine/ Internet access software was Internet Explorer. Tried last night about two in the morning with similar results. Didn't know about the multi-line issue then, so tried to address that there.Suggestion is to ask folks to list their Internet Access software when reporting.