PDA

View Full Version : Registry entries for SQL drivers not being installed



NewsArchive
01-07-1998, 01:00 AM
When installing BDE files on Acer computers with Win'95 installed at
the factory, the only drivers that are configured are those for
Paradox & DBase. None of the SQLdrivers are configured. It appears as
though the registry is not being modified to include the entries
required forthese drivers even though the DLLs are being installed.

I'm guessing that this has something to do with the way the registry
is setup by the folks at Acer, but I can't figure out what the problem
is. Has anyone run into this problem before?

I am using InstallShield for Delphi Version 1.11a.




Stephen W. Boyd
e-mail: sboyd@kanservu.ca

___ O
(_^_) o
o--- .
I'd rather be under the sea!

NewsArchive
01-07-1998, 01:00 AM
On Wed, 07 Jan 1998 14:20:57 GMT, sboyd@kanservu.ca (Stephen W. Boyd)
wrote:
>Paradox & DBase. None of the SQLdrivers are configured. It appears as
>though the registry is not being modified to include the entries
>required forthese drivers even though the DLLs are being installed.

Can you install the Microsoft SQL Server drivers and see if they modify the
registry?

Acer probably installs an OEM version of Windows95 on your PC.

Stefan
ellipse data systems

NewsArchive
01-08-1998, 01:00 AM
owner@ellipse-data.com (Stefan Paetow) wrote:

>On Wed, 07 Jan 1998 14:20:57 GMT, sboyd@kanservu.ca (Stephen W. Boyd)
>wrote:
>>Paradox & DBase. None of the SQLdrivers are configured. It appears as
>>though the registry is not being modified to include the entries
>>required forthese drivers even though the DLLs are being installed.

>Can you install the Microsoft SQL Server drivers and see if they modify the
>registry?

>Acer probably installs an OEM version of Windows95 on your PC.

How do I do that? BDE Admin doesn't allow new drivers to be installed
and I don't have SQL Server.

>Stefan
>ellipse data systems


Stephen W. Boyd
e-mail: sboyd@kanservu.ca

___ O
(_^_) o
o--- .
I'd rather be under the sea!

NewsArchive
01-08-1998, 01:00 AM
On Thu, 08 Jan 1998 14:25:29 GMT, sboyd@kanservu.ca (Stephen W. Boyd)
wrote:
>How do I do that? BDE Admin doesn't allow new drivers to be installed
>and I don't have SQL Server.

I believe there is a SQL Server Client package... but I guess you have to
be the owner of SQL Server. I am not sure. Please contact your local
Microsoft office.

I guess once you have that driver set installed you can add the driver to
the BDE. It might also be the case that you do NOT have Delphi
Client/Server and hence not SQL Links. SQL Links will include an
MSSQL-compatible driver.

Stefan
ellipse data systems

NewsArchive
01-30-1998, 01:00 AM

NewsArchive
01-31-1998, 01:00 AM
Hi Gwen,

this seems to be a problem in UnInstallShield. You can find a custom
uninstall DLL that hadles the path correctly at InstallSite
http://come.to/installsite )

Stefan Krueger
skrueger@usa.net

*** InstallSite provides free resources for setup developers
*** http://come.to/installsite


Gwen Fairchild schrieb in Nachricht <34D262F4.CD55753A@advancedsw.com>...
>Yes, I have now gotten it to add the environment variables.
>
>However, when I uninistall the app, It wipes out all my environment
>variables. any Idea what I'm doing wrong now?
>
>Gwen

NewsArchive
01-31-2000, 01:00 AM
Here's a related article from the Bugs Bulletin on
http://www.installsite.org:

Registry Editor in IDE Capitalizes Strings
Description:
Using the registry editor in IDE to create registry entries, the string gets
converted to all caps. You cannot enter lower characters in registry
entries.
Workarounds:
Use the registry script functions instead of the registry editor in IDE.
Status:
InstallShield confirmed that this is a bug in IS6.01.
Created: 10/12/1999

--
Stefan Krueger - Independent Setup Consultant
<<reply-to address is invalid to avoid spam>>

E-Mail support is not free. To get information about paid
support and consulting services send a blank e-mail to
the autoresponder at info@installsite.org

Visit InstallSite at http://www.installsite.org to download
free code samples, tips, tools and more...

Glen Swindell <gswindell@csm.co.uk> schrieb in im Newsbeitrag:
3895812a@dev_nt_testing....
> Jonni,
>
> I know the effect you are talking about, but why are you worried? Key
> entries within the registry are case in-sensitive, so it does not matter
> that they are converted to uppercase.
>
> Glen Swindell
> CSM Limited
>
>
> "Jonni Faiga" <jonnispam@absolutesys.com> wrote in message
> news:38957fc2.0@news.installshield.com...
> > I am using Install Shield Professional 6.
> > The Value Name of my registery Keys are automatically converted to
> > Uppercase.
> > I am using the "Resources" - "Registry Entries" instead of script. Even
> when
> > I change my physical Registry Entries\Default.rge file they are still
> > converted to uppercase.
> >
> > Anyone have any ideas how to fix this sort of using script?
> >
> > jonnispam@absolutesys.com
> >
> >
> >
>
>

NewsArchive
02-01-2000, 01:00 AM
Stefan & Glen,
Thank you very much for both responding to my question. I really appreciate
it.
My registry component is using a STL "map" (which is case sensitive). Once I
understood that the Registry was not case sensitive, I changed my "map" key
to always be upper case. This solved the problem I was having.
So now the only issue is that the Registry looks ugly in upper case, but its
just an asthetic bug.
Jonni


Stefan Krueger <@> wrote in message
news:3895abd6.0@news.installshield.com...
> Here's a related article from the Bugs Bulletin on
> http://www.installsite.org:
>
> Registry Editor in IDE Capitalizes Strings
> Description:
> Using the registry editor in IDE to create registry entries, the string
gets
> converted to all caps. You cannot enter lower characters in registry
> entries.
> Workarounds:
> Use the registry script functions instead of the registry editor in IDE.
> Status:
> InstallShield confirmed that this is a bug in IS6.01.
> Created: 10/12/1999
>
> --
> Stefan Krueger - Independent Setup Consultant
> <<reply-to address is invalid to avoid spam>>
>
> E-Mail support is not free. To get information about paid
> support and consulting services send a blank e-mail to
> the autoresponder at info@installsite.org
>
> Visit InstallSite at http://www.installsite.org to download
> free code samples, tips, tools and more...
>
> Glen Swindell <gswindell@csm.co.uk> schrieb in im Newsbeitrag:
> 3895812a@dev_nt_testing....
> > Jonni,
> >
> > I know the effect you are talking about, but why are you worried? Key
> > entries within the registry are case in-sensitive, so it does not matter
> > that they are converted to uppercase.
> >
> > Glen Swindell
> > CSM Limited
> >
> >
> > "Jonni Faiga" <jonnispam@absolutesys.com> wrote in message
> > news:38957fc2.0@news.installshield.com...
> > > I am using Install Shield Professional 6.
> > > The Value Name of my registery Keys are automatically converted to
> > > Uppercase.
> > > I am using the "Resources" - "Registry Entries" instead of script.
Even
> > when
> > > I change my physical Registry Entries\Default.rge file they are still
> > > converted to uppercase.
> > >
> > > Anyone have any ideas how to fix this sort of using script?
> > >
> > > jonnispam@absolutesys.com
> > >
> > >
> > >
> >
> >
>
>

NewsArchive
05-05-2000, 12:00 AM
Sorry about that.

I'll try to be more coherent (given that I have literally just started using
installshield, and scrambling to get an installer working at short notice).

I need to produce an installer that checks the registry for the version of
program installed. I downloaded some sample code from installshield called
'Update samples' which you can do a full update or a maintainance. I based
my installer on the full update. When you run their installer it writes a
'version' to the registry (see image1.jpg). But I can't get this function to
perform (reason forincluding my code, to see wether anything is immediately
apparent). This, I think is the code that they are using to do this:

export prototype ProgramFiles_Installed();
> >
> > function ProgramFiles_Installed()
> > STRING szVer;
> > begin
> > NumToStr(szVer, APP_VERSION);
> >
> > RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE);
> > RegDBSetKeyValueEx("SOFTWARE" ^ @COMPANY_NAME ^ @PRODUCT_NAME,
> > "Version", REGDB_STRING, szVer, 4);
> > end;


I wanted a 'version' registry entry so that my script would search for the
version intalled. If the version to be installed is newer than the existing
one, then an update is performed. If it is older then a message appears then
it aborts. If it is the same version, a message appears and aborts.







Stefan Krueger <@> wrote in message news:3911df12.0@208.30.171.38...
> Please provide a detailed description of your problem (desired behaviuor,
> how does it fail) and post only the relevant part of your code.
>
> --
> Stefan Krueger - Independent Setup Consultant
> <<reply-to address is invalid to avoid spam>>
>
> Visit InstallSite at http://www.installsite.org to download
> free code samples, tips, tools and more...
> For information about individual support and consulting services
> please send a blank mail to the autoresponder at info@installsite.org
>
> Stefan Krueger and the InstallSite.org web site are not affiliated
> with InstallShield Software Corporation.
>
> LeeBoy <lee@transarts.freeserve.co.uk> schrieb in im Newsbeitrag:
> 39113d06.0@208.30.171.38...
> > I've tried to base an installation on the sample pack that you can
> download
> > from the install shield website, and I am trying to write a registry
entry
> > of the version I am installing. Here is my code can anybody tell me
whats
> > wrong.
> >
> > // Include header files
> >
> > #include "ifx.h"
> >
> > #define APP_VERSION 2
> >
> >
> >
> > #define SEARCH_DIR TARGETDIR
> >> >
> >
> > prototype UpdateUI();
> > prototype MaintUI();
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > //
> > // FUNCTION: OnFirstUIBefore
> > //
> > // EVENT: FirstUIBefore event is sent when installation is run for
> the
> > first
> > // time on given machine. In the handler installation
usually
> > displays
> > // UI allowing end user to specify installation parameters.
> > After this
> > // function returns, ComponentTransferData is called to
> perform
> > file
> > // transfer.
> > //
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > function OnFirstUIBefore()
> >
> > begin
> > MessageBox("The Program is not installed on this machine.
> > The Updater setup will exit now.", INFORMATION);
> > abort;
> >
> > end;
> >
> >
> >
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > //
> > // FUNCTION: OnMaintUIBefore
> > //
> > // EVENT: MaintUIBefore event is sent when end user runs
installation that
> > // has already been installed on the machine. Usually this
> > happens
> > // through Add/Remove Programs applet. In the handler
> > installation
> > // usually displays UI allowing end user to modify existing
> > installation
> > // or uninstall application. After this function returns,
> > // ComponentTransferData is called to perform file
transfer.
> > //
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > function OnMaintUIBefore()
> > STRING svValue;
> > STRING szTitle, szMsg;
> > STRING svResult;
> > NUMBER nvSize, nVer, nvType;
> > NUMBER nResult;
> >
> >
> > begin
> >
> >
> > Enable( FULLWINDOWMODE );
> > Enable( BACKGROUND );
> > SetColor (BACKGROUND, RGB (128, 0, 255) | BK_SMOOTH);
> > SetTitle( @TITLE_MAIN, 24, WHITE );
> > SetTitle( @TITLE_CAPTIONBAR, 0, BACKGROUNDCAPTION );
> >
> >
> >
> >
> > Check_version:
> >
> > // read from registry what version of the app is installed on the
machine
> > RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE);
> > RegDBGetKeyValueEx("SOFTWARE" ^ @COMPANY_NAME ^ @PRODUCT_NAME,
> > "Version", nvType, svValue, nvSize);
> > StrToNum(nVer, svValue);
> >
> > // if(nVer < APP_VERSION)then
> > // the installed version is older
> > // MessageBox ("Your machine has a newer version of The Program
already insatalled on it. \n\nSetup will now exit.",
> > INFORMATION);
> > // abort;
> >
> > // else
> > // if(nVer = APP_VERSION)then
> > // the installed version is the same
> > // MessageBox ("Already on", INFORMATION);
> >
> > // else
> > // the installed version is newer
> > // MessageBox("The version of Program installed
> > on your machine \nis newer than the one you are attempting to
install.
> > \n\nSetup will exit.", INFORMATION);
> >
> > // abort;
> >
> >
> >
> >
> > Dlg_Start:
> > nResult = SdWelcome( szTitle, szMsg );
> > if (nResult = BACK) goto Dlg_Start;
> >
> > ComponentUpdate("");
> >
> > // setup default status
> > SetStatusWindow(0, "");
> > Enable(STATUSEX);
> > StatusUpdate(ON, 100);
> >
> > endif;
> > // endif;
> > // endif;
> >
> > end;
> >
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > //
> > // FUNCTION: OnMoving
> > //
> > // EVENT: Moving event is sent when file transfer is started as a
> > result of
> > // ComponentTransferData call, before any file transfer
> > operations
> > // are performed.
> > //
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > function OnMoving()
> > begin
> > file://Load the original values of SRCDIR, etc., from IS6's log file
> > file://into memory so that they are re-entered into the log by IFX's
> > file://call to ComponentSaveTarget( "" ).
> > ComponentLoadTarget("");
> > end;
> >
> >
>
////////////////////////////////////////////////////////////////////////////
> > //
> > //
> > // FUNCTION: OnBegin
> > //
> > // EVENT: Begin event is always sent as the first event during
> > installation.
> > //
> >
>
////////////////////////////////////////////////////////////////////////////
> > //
> > function OnBegin()
> >
> >
> > begin
> >
> > SdProductName("The Updater");
> >
> > end;
> >
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > // EVENT: Installed event is sent just after files for the
> component:
> > // ProgramFiles are transferred.
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> >
> > export prototype ProgramFiles_Installed();
> >
> > function ProgramFiles_Installed()
> > STRING szVer;
> > begin
> > NumToStr(szVer, APP_VERSION);
> >
> > RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE);
> > RegDBSetKeyValueEx("SOFTWARE" ^ @COMPANY_NAME ^ @PRODUCT_NAME,
> > "Version", REGDB_STRING, szVer, 4);
> > end;
> >
> >
> >
>
>

NewsArchive
05-05-2000, 12:00 AM
Sorry about that. I'll try to be more coherent (given that I have literally
just started using
installshield, and scrambling to get an installer working at short notice).

I need to produce an installer that checks the registry for the version of
program installed. I downloaded some sample code from installshield called
'Update samples' which you can do a full update or a maintainance. I based
my installer on the full update. When you run their installer it writes a
'version' to the registry (see attached image1.jpg). But I can't get this
function to
perform (this was the reason for including my code). This, I think is the
code that they are using to do this:

export prototype ProgramFiles_Installed();
> >
> > function ProgramFiles_Installed()
> > STRING szVer;
> > begin
> > NumToStr(szVer, APP_VERSION);
> >
> > RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE);
> > RegDBSetKeyValueEx("SOFTWARE" ^ @COMPANY_NAME ^ @PRODUCT_NAME,
> > "Version", REGDB_STRING, szVer, 4);
> > end;


I wanted a 'version' registry entry so that my script would search for the
version intalled. If the version to be installed is newer than the existing
one, then an update is performed. If it is older then a message appears then
it aborts. If it is the same version, a message appears and aborts.







Stefan Krueger <@> wrote in message news:3911df12.0@208.30.171.38...
> Please provide a detailed description of your problem (desired behaviuor,
> how does it fail) and post only the relevant part of your code.
>
> --
> Stefan Krueger - Independent Setup Consultant
> <<reply-to address is invalid to avoid spam>>
>
> Visit InstallSite at http://www.installsite.org to download
> free code samples, tips, tools and more...
> For information about individual support and consulting services
> please send a blank mail to the autoresponder at info@installsite.org
>
> Stefan Krueger and the InstallSite.org web site are not affiliated
> with InstallShield Software Corporation.
>
> LeeBoy <lee@transarts.freeserve.co.uk> schrieb in im Newsbeitrag:
> 39113d06.0@208.30.171.38...
> > I've tried to base an installation on the sample pack that you can
> download
> > from the install shield website, and I am trying to write a registry
entry
> > of the version I am installing. Here is my code can anybody tell me
whats
> > wrong.
> >
> > // Include header files
> >
> > #include "ifx.h"
> >
> > #define APP_VERSION 2
> >
> >
> >
> > #define SEARCH_DIR TARGETDIR
> >> >
> >
> > prototype UpdateUI();
> > prototype MaintUI();
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > //
> > // FUNCTION: OnFirstUIBefore
> > //
> > // EVENT: FirstUIBefore event is sent when installation is run for
> the
> > first
> > // time on given machine. In the handler installation
usually
> > displays
> > // UI allowing end user to specify installation parameters.
> > After this
> > // function returns, ComponentTransferData is called to
> perform
> > file
> > // transfer.
> > //
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > function OnFirstUIBefore()
> >
> > begin
> > MessageBox("The Program is not installed on this machine.
> > The Updater setup will exit now.", INFORMATION);
> > abort;
> >
> > end;
> >
> >
> >
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > //
> > // FUNCTION: OnMaintUIBefore
> > //
> > // EVENT: MaintUIBefore event is sent when end user runs
installation that
> > // has already been installed on the machine. Usually this
> > happens
> > // through Add/Remove Programs applet. In the handler
> > installation
> > // usually displays UI allowing end user to modify existing
> > installation
> > // or uninstall application. After this function returns,
> > // ComponentTransferData is called to perform file
transfer.
> > //
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > function OnMaintUIBefore()
> > STRING svValue;
> > STRING szTitle, szMsg;
> > STRING svResult;
> > NUMBER nvSize, nVer, nvType;
> > NUMBER nResult;
> >
> >
> > begin
> >
> >
> > Enable( FULLWINDOWMODE );
> > Enable( BACKGROUND );
> > SetColor (BACKGROUND, RGB (128, 0, 255) | BK_SMOOTH);
> > SetTitle( @TITLE_MAIN, 24, WHITE );
> > SetTitle( @TITLE_CAPTIONBAR, 0, BACKGROUNDCAPTION );
> >
> >
> >
> >
> > Check_version:
> >
> > // read from registry what version of the app is installed on the
machine
> > RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE);
> > RegDBGetKeyValueEx("SOFTWARE" ^ @COMPANY_NAME ^ @PRODUCT_NAME,
> > "Version", nvType, svValue, nvSize);
> > StrToNum(nVer, svValue);
> >
> > // if(nVer < APP_VERSION)then
> > // the installed version is older
> > // MessageBox ("Your machine has a newer version of The Program
already insatalled on it. \n\nSetup will now exit.",
> > INFORMATION);
> > // abort;
> >
> > // else
> > // if(nVer = APP_VERSION)then
> > // the installed version is the same
> > // MessageBox ("Already on", INFORMATION);
> >
> > // else
> > // the installed version is newer
> > // MessageBox("The version of Program installed
> > on your machine \nis newer than the one you are attempting to
install.
> > \n\nSetup will exit.", INFORMATION);
> >
> > // abort;
> >
> >
> >
> >
> > Dlg_Start:
> > nResult = SdWelcome( szTitle, szMsg );
> > if (nResult = BACK) goto Dlg_Start;
> >
> > ComponentUpdate("");
> >
> > // setup default status
> > SetStatusWindow(0, "");
> > Enable(STATUSEX);
> > StatusUpdate(ON, 100);
> >
> > endif;
> > // endif;
> > // endif;
> >
> > end;
> >
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > //
> > // FUNCTION: OnMoving
> > //
> > // EVENT: Moving event is sent when file transfer is started as a
> > result of
> > // ComponentTransferData call, before any file transfer
> > operations
> > // are performed.
> > //
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > function OnMoving()
> > begin
> > file://Load the original values of SRCDIR, etc., from IS6's log file
> > file://into memory so that they are re-entered into the log by IFX's
> > file://call to ComponentSaveTarget( "" ).
> > ComponentLoadTarget("");
> > end;
> >
> >
>
////////////////////////////////////////////////////////////////////////////
> > //
> > //
> > // FUNCTION: OnBegin
> > //
> > // EVENT: Begin event is always sent as the first event during
> > installation.
> > //
> >
>
////////////////////////////////////////////////////////////////////////////
> > //
> > function OnBegin()
> >
> >
> > begin
> >
> > SdProductName("The Updater");
> >
> > end;
> >
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> > // EVENT: Installed event is sent just after files for the
> component:
> > // ProgramFiles are transferred.
> >
>
////////////////////////////////////////////////////////////////////////////
> > ///
> >
> > export prototype ProgramFiles_Installed();
> >
> > function ProgramFiles_Installed()
> > STRING szVer;
> > begin
> > NumToStr(szVer, APP_VERSION);
> >
> > RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE);
> > RegDBSetKeyValueEx("SOFTWARE" ^ @COMPANY_NAME ^ @PRODUCT_NAME,
> > "Version", REGDB_STRING, szVer, 4);
> > end;
> >
> >
> >
>
>





----------------------------------------------------------------------------
----

NewsArchive
06-28-2000, 12:00 AM
The MSI help page "Formatted" has more information about "escaped" square
brackets and other special forms.

"David Thornley" <davidt@installshield.com> wrote in message
news:395a6e08.0@208.30.171.38...
> I was looking into an issue using similar strings. In my case, the
> registry entry was getting written, but it was causing an ICE30 validation
> error since the Windows Installer thinks you are using a property and the
(,
> % and " characters are not valid in property names. What I ended up
doing
> was using escape characters to explicitly denote the square brackets:
>
> [\[] evaluates at runtime to [ and [\]] evaluates to ]
>
> so
>
> [open("%1")]
>
> becomes
>
> [\[]open("%1")[\]]

NewsArchive
06-29-2000, 12:00 AM
David,
Thank you very much. It works.
Regards,
Denis

"David Thornley" <davidt@installshield.com> wrote in message
news:395a6e08.0@208.30.171.38...
> Hey,
>
> If the Windows Installer engine is unable to resolve a property it is
> *supposed* to write the text string as is. So if you tried [DaveRocks]
and
> there is no DaveRocks property it should just write [DaveRocks] into the
> registry.
>
> I was looking into an issue using similar strings. In my case, the
> registry entry was getting written, but it was causing an ICE30 validation
> error since the Windows Installer thinks you are using a property and the
(,
> % and " characters are not valid in property names. What I ended up
doing
> was using escape characters to explicitly denote the square brackets:
>
> [\[] evaluates at runtime to [ and [\]] evaluates to ]
>
> so
>
> [open("%1")]
>
> becomes
>
> [\[]open("%1")[\]]
>
> If this does not help, my recommendation to troubleshoot this further
would
> be to start with a string like open1 and then start adding the decoration
> characters like ( % and " until it fails to write the registry entry.
Once
> you have isolated the offending characters, try using the escape sequence.
> I.E. [\"] or [\(] or [\%]
>
> Regards
> David Thornley
> InstallShield Software Corporation
>
>
> "Denys V. Zalizetskyy" <dz@x-tend.kiev.ua> wrote in message
> news:3959ca36.0@208.30.171.38...
> >
> > Hello,
> >
> > I need to write [open("%1")] value to the registry.For this I write in
my
> > components Registry Data section specified value under some key as
default
> > string. But after product installation there nothing is written! I
assume
> > ISWI understand this as it should substitute it with the property, whose
> > name is specified in the square brackets, doesn't find it and writes
> > nothing.
> > So can I write to the registry value [smth.] ?
> >
> > Regards,
> > Denis
> >
> >
>
>

NewsArchive
03-12-2001, 01:00 AM
Are your CA's running as "deferred execution" custom actions? If not, then
they are running VERY early in the Execute Sequence regardless of where you
place them in the sequence; "immediate execution" CA's do not actually run in
the sequence where you put them (a nice "feature"...). The only way to make
them run when they are supposed to run is to make them "deferred execution"
CA's - unfortunately, it is more work to pass Properties to "deferred
execution" CA's (see KB article Q104413). You could have a CA that writes the
registry values...if it was sequenced before the other CA's, then they would
run correctly (early in the sequence but in the correct relative order)...

Mike

Kyle Crowder wrote:

> At what point do the registry entries get created during the install?? My
> CA's are after publish features and before publish product which is after
> WriteRegistryValues. At that point the reg entries are not yet made, and
> thus my CA's are failing. Any suggestions are appreciated.
>
> Thanks