Cool Beans -

The most likely may be just that sometimes when you "change pages" on mudcat, if traffic is heavy or if the server's in a bad mood, the first packet gets sent, then the request for the rest of the new page sits in line until traffic that got in the way is processed. This can look like you're "hung" when you're really not, and the solution is just to wait. In some cases the message really did just get "lost," so try as much patience as reasonable. When you click-to-send the login, the message may be just waiting in line due to the traffic.

If you have a noisy dialup connection, sometimes the send seems to break the connection, especially if there's heavy traffic on the 'phone line. Unless it's obvious in your own setup, there's not much you can do about a bad phone line except complain to the phone co (and/or to your ISP). Sometimes there are alternate phone numbers you can use to dial in to your ISP that may work better.

In most browsers, you can enter the name of a site and give it "special permission" to always work nice. You probably should do that for mudcat. If you happen to use Internet Explorer, click on "Tools" on the top toolbar, then on "Internet Options." Select the "Privacy" tab, and click the "Sites" button. Type "mudcat.org" (without the quotes) in the little box, and hit the "allow" button. This should assure that your browser will never get in the way of exchanging cookies or other stuff with mudcat. Other browsers should have similar settings.

John