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.
Tony Hoyle wrote: > sabdev wrote: > >> I first used the Innosetup Bo made. Everything installed fine but the >> control pannel refuse to open. MFC71U.dll is missing. >> >> I then installed using the MSI. First installation simply failed to >> install the cvsnt service. After reboot, I had to Repair the >> installation then everything worked fine. > > > Did you uninstall between the two? You can't just install one over > the other (you should be able to but it doesn't work that well). I did uninstall the innosetup, then install using MSI. It failed, then I choose Repair from the MSI installer. > >> For the 'fun', I copied MFC71U.dll in windows\system32 and then retry > > > The old installer breaks the rules (because I didn't know how to do it > any other way when I made it) but you're not supposed to ever put > anything in system32. All the new code is designed to run from a > single directory. The innosetup installer try to keep the CVSNT control pannel appearing in the settings->control panel. So cvsnt.cpl has to be copied in system32 as well as the dependent dll. If now, you decide to keep CVSNT Control Panel only in the start menu, I'm fine with it (that's what the MSI does, I think). > >> So another computer, another OS, no more problem. Might this be due >> to the OS (old NT4 was on my previous computer). >> Did someone installed CvsNT 2.0.62.1817 on that old OS and did it >> work fine ? > > > Part of the pre-release testing is NT4 (less so now that it's not so > popular as an OS) but 2.0.62 hasn't had much of that. The msi > installer has been quite well tested on it though... doesn't work 100% > (the offsite links don't work as NT4 doesn't support the format that > MSI generates) but is good enough. > > Tony