Re: WinCvs New Repository Causes Hang

On Tue, 14 Nov 2006 01:43:13 -0000, "jmo0099" <[email protected]>
wrote:

>Hi: I tried to research this, found similar problems but not exactly 
>the problem I'm having...
>
>We changed our respository from one server (a Unix box named src, 
>located at /aaa/bbb/CVS) to a new server (we just changed the dns 
>entry to point to a new Unix machine, so it's still src but this 
>directory is /ddd/CVS).  The original machine is now offline.
>
>My problem is that I did not change the repository setting in WinCvs 
>before the original machine came down.  Now when I start WinCvs it 
>hangs, so I can not change the repository information via the gui or 
>access any menu entries.  I was running on 1.3 on Windoz XP, and 
>then upgraded to the current 2.02, but am still having the same 
>problem.  I tried searching the registry for all instances of 
>WinCvs, but could not find anything that looks like the repository 
>settings.  I also tried to grep the WinCvs directory for the CVS 
>server name, hoping to find a configuration file, but no luck there 
>either.
>
>Is the repository definition someplace where I can edit it by hand, 
>or any other suggestions as to how to get WinCvs to respond so that 
>I can change it from the gui?
>
>TIA for your help!
>

The WinCvs settings are in the registry at:
HKEY_CURRENT_USER\Software\WinCvs\wincvs

But WinCvs does not care about the availability of a *server* when it
starts up so that is not your problem.
What is *does* thought is scanning of the *sandboxes* upon starting
and this can take some substantial time if those are big.
Even worse:
If you have your sandbox on a network share (actually forbidden!) and
this share has disappeared then WinCvs will have networking problems
right at startup. These will sort themselves out eventually but it can
take some time still if there are many such cases and slos if you had
"flat view" on when you closed WinCvs the lastr time you closed it.

Try this:
1. After you start WinCvs and it seems locked, press ESC
2. If that does not help then close WinCvs and delete the above
mentioned registry key and start again.
Now WinCvs has forgotten the GUI settings and the location of your
sandboxes so you have to reconfigure that, but that is a simple
procedure.

HTH

/Bo
(Bo Berglund, developer in Sweden)