Those old winsock-style error messages can be frustrating. What I'd do is run netstat -a immediately after encountering the error to check on the socket state. A possible problem is that you might be running an old style single threaded listener.
--- Kevin Adams <[EMAIL PROTECTED]> wrote: > Thanks Greg, I found an earlier post in the archives that suggested > someone rerun ZTMGRSET when they were getting the WSAEINTR error when > attempting to start CPRS. That has obviously caused the problem with > my errors. Upon restarting Taskman, my D ^%SS output is as below, > but > CPRS still gives me the same interrupted system call error > (WSAEINTR). > Again, I'm just trying to start CPRS with Cache and Vista configured > on the same machine, and I'm trying to connect to my localhost. Is > there some other common mistake that I am making? === Gregory Woodhouse <[EMAIL PROTECTED]> "Design quality doesn't ensure success, but design failure can ensure failure." --Kent Beck ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
