I did a "repair", which did not pull down the "ext" protocol DLL. I guess "repair" merely overwrites existing DLLs and doesn't check for new ones. An InstallShield bug if you ask me, but using VS.NET to make MSI files is no better. "Modify" doesn't do anything since I didn't have any components to add or remove. This is at least the second time I have been bitten by not uninstalling before installing. I think I'll make it a habit to do so in order to avoid asking stupid questions.
BTW, before I got Bo's email I resorted to Tortoise CVS which includes an SSH client (putty/ssh not required, therefore installation is much simplified). Tortoise CVS has become an excellent product in its own right. It almost replaces the need for WinCVS or the command line. > Terris wrote: > > Thank you! I had to uninstall and reinstall. > > > > For future reference, you can also do a "Repair" and a "Modify" to both upgrade > to the latest CVS.EXE as well as add any new features/DLL's. Un/reinstall > should not be necessary. Of course, I think that if you do a "Modify" and the > CVS executable is checked (as is the default), the installer should actually > replace the CVS.EXE with the newer version, but maybe that is just me. ;~) > > John > > > > _______________________________________________ Cvsnt mailing list [EMAIL PROTECTED] http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
