S
Scott B. Drummonds
Hi, everyone,
I am working on packaging Office XP (2002) for an application that
specifically requires that version (I cannot upgrade). The installer
(SETUP.EXE) that we're using to package it is choking on the chained
installations.
Specifically, if the MSI file specified in the [MSI] section lies in a
directory that contains spaces, SETUP.EXE is clever enough to quote the
complete file name. However, it is *not* doing this for files referenced in
the PATH variable in the [chained_installation] sections.
Is there a way that I can force SETUP.EXE to quote everything? I've tried
enclosing the PATH value in the [chained_installation] section, adding
characters that might force quoting ("./file.msi", "c:file.msi", etc.), and
searched for parameters to SETUP.EXE that might do the same. No luck on any
of these!
Any ideas?
Thanks,
Scott
I am working on packaging Office XP (2002) for an application that
specifically requires that version (I cannot upgrade). The installer
(SETUP.EXE) that we're using to package it is choking on the chained
installations.
Specifically, if the MSI file specified in the [MSI] section lies in a
directory that contains spaces, SETUP.EXE is clever enough to quote the
complete file name. However, it is *not* doing this for files referenced in
the PATH variable in the [chained_installation] sections.
Is there a way that I can force SETUP.EXE to quote everything? I've tried
enclosing the PATH value in the [chained_installation] section, adding
characters that might force quoting ("./file.msi", "c:file.msi", etc.), and
searched for parameters to SETUP.EXE that might do the same. No luck on any
of these!
Any ideas?
Thanks,
Scott