Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
On Thu, 5 Dec 2002 14:08:58 -0500, "Paul St. John" <pstjohn at visible-bytes.com> wrote: > >1) trace the communication between WinCvs client and Server and see > where the communication is breaking down (is there a facility for > this? In worse case I could build sources and use debug mode if > necessary - but I'm not familiar with the code base so this would > be time consuming). Set CVS_CLIENT_LOG on the client to the name of a file somewhere that you can write to. That'll produce <file>.out and <file>.in which contains all the data. It can get very large though. >2) try another protocol. Good idea, if they're both Windows boxes. Tony