PDA

View Full Version : Calling Executable after Forced Reboot.



NewsArchive
10-20-1997, 12:00 AM
Is there any way of caling an EXE after the PC has been rebooted?
I need to do this as we have a 16 bit application which uses the BDE
with Interbase.

ISX doent allow you to install Interbase, so I have had to write my own
program, which works by merging 2 cfg files, in case the BDE already
exists. The problem is that after installation, the BDE cannot be
initialised until a reboot. (Correct me if im wrong), and i need the
merge function within the IDAPI DLL.

Also, Can the windows search path be modified dynamically?

NewsArchive
10-20-1997, 12:00 AM
On Mon, 20 Oct 1997 14:09:12 +0100, "Paul.Jordan"
<Paul.Jordan@Kewill-Xetal.com> wrote:
>Is there any way of caling an EXE after the PC has been rebooted?

Yes... It is a registry key you can set that allows you to run one EXE ONCE
after a reboot... I believe that this key is mentioned somewhere in the IXS
Knowledge Base.

>Also, Can the windows search path be modified dynamically?

You can do that with your application too :)

Stefan
ellipse data systems

NewsArchive
10-20-1997, 12:00 AM
On Mon, 20 Oct 1997 14:09:12 +0100, "Paul.Jordan"
<Paul.Jordan@Kewill-Xetal.com> wrote:
>Is there any way of caling an EXE after the PC has been rebooted?

Yes... It is a registry key you can set that allows you to run one EXE ONCE
after a reboot... I believe that this key is mentioned somewhere in the IXS
Knowledge Base.

>Also, Can the windows search path be modified dynamically?

You can do that with your application too :)

Stefan
ellipse data systems

NewsArchive
12-16-1999, 01:00 AM
Jim,
Thanks. I set the action to Defered and the CA now takes place when
expected and it also seemed to stop the problem where it would wait for the
exe to finish before continuing. My last question concerns your reply to my
question. What do you mean by "Your condition should be Not Installed"?

Thanks,

Sean
"Jim Kang" <?@installshield.com> wrote in message
news:385864a7.0@news.installshield.com...
> In article <3856bc83.0@news.installshield.com>, "Sean Fawcett"
<swf@rightfax.com> wrote:
> > I have a custom action that calls an executable. Two things are
happening
> > that I am not expecting
> >
> > 1. The custom action only happens on un-install. It should be only
> > called on install.
>
> Your condition should be Not Installed.
>
> > 2. When the custom action does happen it waits for the executable to
> > finish.
>
> > The custom actions properties are as follows
> >
> > Type 210
> > Launch an Executable
> > Installed with Product
> > It is NOT set for Wait for the action to finish executing
> > Ignore Custom Action Return Code(I have tried this both ways)
> > Imediate Execution
> > Always Execute ( I have tried this a couple of different ways)
> >
> > I added it to the Installation>Execute area of sequences. It has a
sequence
> > number of 2075.
> >
> > It is added between Create Shortcuts and Register Class info. During
> > install the Custom Action is not called at all as far as I can see.
During
>
> If you want to run in sequence (after CreateShortcuts) you need to make
the
> action deferred.
>
> > Uninstall the custom action is called. Any one know what I might be
doing
> > wrong?
> >
> > Thanks,
> >
> > Sean
> >
> >
>
> ----
>
> Jim Kang - Developer Support Engineer
> InstallShield Software Corporation
>

NewsArchive
12-16-1999, 01:00 AM
Jim,
I am know trying a dll call and having similar problems. I have set the
ca to defered but it still dies. I have included a bit map showing where
during the install it fails and what the error is. The CA is set in the
install sequence after creating shortcuts, but it still runs before the
files are moved.

Thanks,

Sean


"Sean Fawcett" <swf@rightfax.com> wrote in message
news:385926c7.0@news.installshield.com...
> Jim,
> Thanks. I set the action to Defered and the CA now takes place when
> expected and it also seemed to stop the problem where it would wait for
the
> exe to finish before continuing. My last question concerns your reply to
my
> question. What do you mean by "Your condition should be Not Installed"?
>
> Thanks,
>
> Sean
> "Jim Kang" <?@installshield.com> wrote in message
> news:385864a7.0@news.installshield.com...
> > In article <3856bc83.0@news.installshield.com>, "Sean Fawcett"
> <swf@rightfax.com> wrote:
> > > I have a custom action that calls an executable. Two things are
> happening
> > > that I am not expecting
> > >
> > > 1. The custom action only happens on un-install. It should be only
> > > called on install.
> >
> > Your condition should be Not Installed.
> >
> > > 2. When the custom action does happen it waits for the executable
to
> > > finish.
> >
> > > The custom actions properties are as follows
> > >
> > > Type 210
> > > Launch an Executable
> > > Installed with Product
> > > It is NOT set for Wait for the action to finish executing
> > > Ignore Custom Action Return Code(I have tried this both ways)
> > > Imediate Execution
> > > Always Execute ( I have tried this a couple of different ways)
> > >
> > > I added it to the Installation>Execute area of sequences. It has a
> sequence
> > > number of 2075.
> > >
> > > It is added between Create Shortcuts and Register Class info. During
> > > install the Custom Action is not called at all as far as I can see.
> During
> >
> > If you want to run in sequence (after CreateShortcuts) you need to make
> the
> > action deferred.
> >
> > > Uninstall the custom action is called. Any one know what I might be
> doing
> > > wrong?
> > >
> > > Thanks,
> > >
> > > Sean
> > >
> > >
> >
> > ----
> >
> > Jim Kang - Developer Support Engineer
> > InstallShield Software Corporation
> >
>
>

NewsArchive
12-16-1999, 01:00 AM
In article <385926c7.0@news.installshield.com>, "Sean Fawcett" <swf@rightfax.com> wrote:
> Jim,
> Thanks. I set the action to Defered and the CA now takes place when
> expected and it also seemed to stop the problem where it would wait for the
> exe to finish before continuing. My last question concerns your reply to my
> question. What do you mean by "Your condition should be Not Installed"?

If you want your CA to run only when the product has not yet been installed,
you want to put a condition of "Not Installed" on it. The MSI engine sets the
Installed property if the product is already installed on the machine.

>
> Sean
> "Jim Kang" <?@installshield.com> wrote in message
> news:385864a7.0@news.installshield.com...
> > In article <3856bc83.0@news.installshield.com>, "Sean Fawcett"
> <swf@rightfax.com> wrote:
> > > I have a custom action that calls an executable. Two things are
> happening
> > > that I am not expecting
> > >
> > > 1. The custom action only happens on un-install. It should be only
> > > called on install.
> >
> > Your condition should be Not Installed.
> >
> > > 2. When the custom action does happen it waits for the executable to
> > > finish.
> >
> > > The custom actions properties are as follows
> > >
> > > Type 210
> > > Launch an Executable
> > > Installed with Product
> > > It is NOT set for Wait for the action to finish executing
> > > Ignore Custom Action Return Code(I have tried this both ways)
> > > Imediate Execution
> > > Always Execute ( I have tried this a couple of different ways)
> > >
> > > I added it to the Installation>Execute area of sequences. It has a
> sequence
> > > number of 2075.
> > >
> > > It is added between Create Shortcuts and Register Class info. During
> > > install the Custom Action is not called at all as far as I can see.
> During
> >
> > If you want to run in sequence (after CreateShortcuts) you need to make
> the
> > action deferred.
> >
> > > Uninstall the custom action is called. Any one know what I might be
> doing
> > > wrong?
> > >
> > > Thanks,
> > >
> > > Sean
> > >
> > >
> >
> > ----
> >
> > Jim Kang - Developer Support Engineer
> > InstallShield Software Corporation
> >
>
>

----

Jim Kang - Developer Support Engineer
InstallShield Software Corporation

NewsArchive
12-16-1999, 01:00 AM
In article <38593467.0@news.installshield.com>, "Sean Fawcett"
<swf@rightfax.com> wrote:
> Jim,
> I am know trying a dll call and having similar problems. I have set the
> ca to defered but it still dies. I have included a bit map showing where
> during the install it fails and what the error is. The CA is set in the
> install sequence after creating shortcuts, but it still runs before the
> files are moved.

According to the MSI SDK help, 2715 means that the file table entry referred
to by your CA cannot be found in the File table. Try re-running the wizard on
your custom action and re-selecting the dll in your component for the CA
source. Then, make sure that the source listed for the CA after you are
finished matches the key in your file list for the component.

----

Jim Kang - Developer Support Engineer
InstallShield Software Corporation