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.
(Was RE: [cvsnt] cvslock trying to connect to multicast address?) On Windows XP Pro SP2, with CNXT V9x PCI Modem, Windows Firewall. CVSNT versions including 2.5.01.1976, 2.5.02.2064, 2.5.02.2088 A fatal error Faulting application cvslock.exe, version 0.0.0.0, faulting module howl.dll, version 0.9.5.2, fault address 0x0000a1eb. occurs during service start-up if Zeroconf publication is enabled. If Zeroconf publication is turned off, or the cvslock service started manually from the control panel after establishing an internet connection then no error occurs. I don't necessarily regard this as a CVSNT problem, but you did ask for details. Kevin -----Original Message----- From: Arthur Barrett [mailto:arthur.barrett at march-hare.com] Sent: 22 September 2005 23:10 To: Kevin Rigotti; cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: RE: [cvsnt] cvslock trying to connect to multicast address? Kevin, > That explains why it falls over on machines with only > dial-up internet access then. I travel a lot (!) and have a repository on my laptop and it's never crashed (currently 2.5.02.2091). The problem you are describing here is different to the multicast question - please report the actual commands and error messages in a separate post with a descriptive subject line. You can also install a loopback connection as described here: Win2000: http://support.microsoft.com/default.aspx?scid=kb;en-us;236869 Or WinXP: http://support.microsoft.com/default.aspx?scid=kb;en-us;839013 > I have to run with LockServer=none, > LockDir=H:\CVS\Locks and the cvslock service > disabled. That feature is no longer supported. See Tony's comments for more info. > The standard installation will work, but only if I > briefly connect and then re-start the lock server > with a network present. This statement implies that sometimes it doesn't work. Please specify what you think "working" is, why you think that it is not "working" and the exact circumstances involved are. Also remember to include the CVSNT client and Server version numbers, Operating system name and version and service pack level, and the exact commands involved and the exact wording of any error messages. Traces and other system information (set, ipconfig, cvsdiag etc) are also often helpful. Regards, Arthur