Yes.
You can only specify executables in TProcess. .msi is not an executable
file.
You need to use the shellexecute function (maybe the LCL provides an
equivalent) to start the executable associated with a file type (in this
case, the MS installer).
Ah, that makes sense. Thanks everyone
Error 193 is %1 is not a valid Win32 application, what is your .Executable
or .CommandLine property?
--
View this message in context:
http://free-pascal-lazarus.989080.n3.nabble.com/Lazarus-TProcess-and-Windows-XP-tp4032239p4032244.html
Sent from the Free Pascal - Lazarus mailing list archive
://free-pascal-lazarus.989080.n3.nabble.com/Lazarus-TProcess-and-Windows-XP-tp4032239p4032244.html
Sent from the Free Pascal - Lazarus mailing list archive at Nabble.com.
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http
On Wed, 3 Jul 2013, Richard Mace wrote:
It was the complete path to an .msi file. Does that make a difference?
Yes.
You can only specify executables in TProcess. .msi is not an executable file.
You need to use the shellexecute function (maybe the LCL provides an equivalent)
to start the
Am 03.07.2013 08:57, schrieb Richard Mace:
It was the complete path to an .msi file. Does that make a difference?
*.msi files are not executables by themselves, they are just stupid
files. You don't see this, because they are linked to (AFAIK) msiexec
which executes them when you open them in
Am 03.07.2013 09:03, schrieb Michael Van Canneyt:
On Wed, 3 Jul 2013, Richard Mace wrote:
It was the complete path to an .msi file. Does that make a difference?
Yes.
You can only specify executables in TProcess. .msi is not an
executable file.
You need to use the shellexecute function
On Wed, 3 Jul 2013, Sven Barth wrote:
Am 03.07.2013 09:03, schrieb Michael Van Canneyt:
On Wed, 3 Jul 2013, Richard Mace wrote:
It was the complete path to an .msi file. Does that make a difference?
Yes.
You can only specify executables in TProcess. .msi is not an executable
file.
