[cvsnt] RE: Bad upgrade experience to current CVSNT 2.50.3 (2260)

[Bo Berglund]

Having 3 entries doesn't look good....

What you should do is:
1. Uninstall the latest installed version 

2. Then uninstall the middle one. This will possibly fail because the first
uninstall has already removed stuff. But try it anyway.

3. Uninstall the last one as well.

4. Now if you still have any entry left over then go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
then try to locate the entry for the CVSNT uninstall icon you still have and
delete it.
It might be hidden inside one of the GUID type keys, so you might have to do
a search for cvs.exe in the data inside the Uninstall key to find it.
Once found delete the whole key.

Then finally locate the directory you installed to and delete its contents.

Now reboot.

Then use the Inno installer or the one provided by Tony and make an install.

My best guess is that you will now succeed and you will have a working
server.
This time it is clean so you can in the future upgrade it using the same
installer source.
But you cannot mix MSI installers with InnoSetup ones without uninstalling
in between...

Don't be afraid of uninstalling, it won't touch any of your data including
the config data.
I have uninstalled and reinstalled numerous times without a hitch. (While
testing various versions) 


Best regards,

Bo Berglund



-----Original Message-----
From: John Peacock [mailto:jpeacock at rowman.com] 
Sent: den 24 mars 2006 22:55
To: bo.berglund at telia.com
Subject: Re: Bad upgrade experience to current CVSNT 2.50.3 (2260)

Bo Berglund wrote:
> If you like I could email you the zip file so you can get the dll from
> there.

Or I can download the InnoSetup version, right?

> But on the other hand:
> - Add/Remove Programs
> - Uninstall CVSNT (by now you probably have two entries there)

Actually I have three entries:

CVS for NT
CVSNT
CVSNT 2.5.03.2260

> - Reboot
> - Then run the CVSNT installer again (MSI or InnoSetup)
> 
> I think you will be OK now.

I'm not changing anything right now, since it seems to be working for 
the moment. :-)

John