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 sales@march-hare.com.
An extra piece of information: After the mentioned problems with build 62, CVSNT left a temp dir for each command in the temp folder (cvs-servxxxx). These temp folders are normally deleted by CVSNT but not so this time. Any ideas what could be the problem? And: I copied the new VS7 dll:s over to system32 to get the control panel applet running so this should not be an issue for cvs.exe. /Bo -----Original Message----- From: Bo Berglund [mailto:Bo.Berglund at system3r.se] Sent: den 12 december 2002 09:01 To: CVS-NT Mailing list (E-mail) Subject: [cvsnt] Problem upgrading to build 62 I had my cvsnt server running on build 57j and needed it to be upgraded past the revision where tagging info gets to standard input. So I downloaded the setup for 62 from the cvsnt website and ran it on the server. First I tried the repair option. Afterwards I could not do anything on the server, it just quit all commands with error code 1 saying to consult the above messages if any etc. Then I tried the modify option and had the same result. Finally I grabbed the 57l files (cvs.exe, cvsservice.exe, xxx_protocol.dll) from my laptop and copied them over to the server just to get it working again. This made it start working finally. I am running the sspi protocol from WinCvs latest version. This is using 57l (laptop...). Question: Is there an issue with installing/repairing/modifying cvsnt using build 62 setup on top of 57l??? Bo Berglund _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs