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.
We use the following Innosetup entry in our setups in order to register the internal typelibrary:
[Run]
Filename: {app}\Program.exe; Parameters: /regserver; WorkingDir: {app}; StatusMsg: Registering Program
Of course ours is an application developed with Delphi and it might not work the same way with cvs.exe
/Bo
-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Oliver Giesen
Sent: den 13 februari 2004 13:24
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] Re: Why do recent installers require a restart?
Tony Hoyle wrote:
> That'll be the setuid.dll (LSA helper), which is always locked as it's
> loaded by the system on boot. Eventually that'll settle down (I don't
> see that I can do much more to it anyway) and the version checking
> will mean it never gets updated.
>
> If you're not using pserver you can just uninstall that and there
> isn't much else that'd require a reboot.
Hmm, I just tried the 2.0.28 installer (I updated from 2.0.26) and
deselected the LSA setuid helper as well as the sserver protocol (and
with it the CA certificates). It still demanded a restart. With a little
research I found the file which contains the information which Inno
intends to apply after a reboot: In
HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce it created a link
to c:\winnt\is-7OBBR.exe /REG and right next to that file is another one
named is-7OBBR.lst which contains the following:
* List of files to be registered on the next reboot. DO NOT EDIT! *
[t]C:\Program Files\cvsnt\cvs.exe
Thus it appears to be the bit about registering the typelib inside
cvs.exe (I guess this is done for the COM plugins support?) that's
prompting the reboots. I have no idea why this could have failed. There
was no CVS process running at the time and I did the install with
administrative privileges (via Run as...).
BTW: if setuid.dll is really only required for :pserver: wouldn't it
make sense to make it a subcomponent of Protocols\Pserver in the
installation?
Cheers,
--
Oliver
---- ------------------
JID: ogiesen at jabber.org
ICQ: 18777742 (http://wwp.icq.com/18777742)
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs