OK folks, I think I figured out most if not all of the problems over the weekend. I suppose you could say it was a mental error on my part. I was trying to increase the realiability and speed of the site by spreading out all the functions of the mudcat over 3 machines. So I needed to make sure each of the 3 machines had the same 10 functions/programs/settings that make the mudcat work. Well... I guess I forgot a couple.

The system works by randomly rotating each of the 10 or so functions on the 3 machines, so it is impossible to know which machine you are actually hitting which makes it very hard to test.

Over the next couple of weeks, I probably will be doing more tests to try to make the mudcat more instantly responsive to requests. We've been peaking every resource in the evenings, apparently when you all get off work and go home to check the Mudcat... Its a valuable learning process for me, so it hardly seems like work.

So if in the weeks to come, you see glitches or errors, don't panic, its just me messing with things. Since it's a random distribution, you could probably close your browser and restart it, or just try back later, and you'll get a different machine. IE is a little more tricky, you may have to reboot your whole machine, for they cache the ip address rather than the domain name (that's nerd for IE sucks).