Ok, im stil having the random "lockup" problem as described in my previous post. MQSEQ2 added extra error logging to the client (seperate box in this case) and as it turns out, there are no odd errors on the client. (I just get the standard in / out messages right before it dies)
I've noticed a problem on my host box though. Shortly after the client dies, i get a "Delayed write error" in windows XP. It ususally says "Windows could not save the information e:\Everquest\$ms" or something odd like that. Then in the event viewer i get an error log that says "An error was detected on device \Device\Harddisk0\D during a paging operation."
Now i know you're going to say my HDD is screwed up, but im certian it is not. I've run several low level diagnostics on it, and benchmarked with Sandra for 24 hours with no errors. It's a WD 4meg buffer Caviar edition.
I've also terminated any other applications on my host box to try to eliminate any possible interference. Im down to running EQ w/ EQW, myseq server, and MQ.
Im assuming that the reason the delayed write error is happening is because something is getting "hooked" (for lack of a better term) and not being released properly. Like when you try to save a document that is in use.
Is there any way we could add some error logging to the server?
Im using the new years build of MQ. Myseq 1.15.16, the 1.11 server, and eqw beta 2.35A. I dont think it's the eqw, because i've been using that version for a long time with no problems.
-Mixy!