It seems that the problem lies in that the self-extractor (phase 1)
immediately passes control to the installer (phase 2) without giving me any
opportunity to add to (or modify) the XML (just extracted) that controls the
installation. There seems to be a command line parm that "could be" passed
to the phase 2 installer pointing it to some override XML, but the problem
is that I've yet to discover how to tell the self-extractor (phase 1) to
pass that parm --- it just executes it (with no parm) as soon as the
extraction completes.
I have not found any documented parms for the self-extractor program.
I've had some communication with the person at MS responsible for Runtime.
We exchanged a few emails (several months ago) but all proved fruitless.
Has anyone gotten any further than I have (anything would be further than I
have!).
bob h.
extract the runtime using the extract switch e.g.: "AccessRuntime 2010
ENG.exe" /extract:C:\AccessRT
create a config xml file with the following content in the folder
where the extracted files are (file name e.g. config.xml):
<Configuration Product="AccessRT">
<Display Level="Basic" CompletionNotice="no" SuppressModal="yes"
AcceptEula="yes" />
<!-- <Logging Type="standard" Path="C:\Temp\"
Template="Microsoft_Access_2010_Runtime_Setup(*).log" />
<COMPANYNAME Value="Company Name" /> -->
<Setting Id="SETUP_REBOOT" Value="IfNeeded" />
</Configuration>
you can also specify a logfile location and a company name, just
uncomment the two lines.
than run setup.exe in the same folder:
setup.exe /config config.xml
stefan