Thanks.
Yes, I agree that it looks like an windows installer problem, but I have to
suspect that the issue is being triggered by something Adobe specific.
After all, the PSE11 install ran fine, but the PRE11 install attempted
immediately after it failed. Not a lot of time for anything to happen in
between. And I have installed other software since (MSI based, I’m sure),
so this does point to it being an Adobe issue.
I did what you suggested with renaming the installshiled directory, but it
had no effect. The install just ‘died’ at the same point – just after the
dialogue box headed “Preparing to Install” and the status “configuring
windows installer”. There is still no error message.
I’ve taken a look for the log files you mentioned before, but it would
appear that they were not modified at all by the installation attempt (the
‘date last modified’ is from several days ago).
Should a new “Installshield” folder have been created? It has not been.
FYI, the old Installshild folder contained only one folder tree:
Instalshield/Driver/9/Intel 32 all created on 18/12/2012. Surprisingly the
Intel 32 folder contains a small number of files, with creation dates from
2003. Files include IDriver.exe and iGDIcnv.dll
Looking at my system through Task Manager, it would appear that, after each
attempted installed, a copy of msiexec.exe (windows installed) is left in a
“suspended” state. The msiserver service is in a “stopped” state.
I have also tried another apparently common remedy to install problems: I
have cleared the registry key “PendingFileRenameOperations”. Again, no
apparent effect on the PRE11 Install.
What next, please?
And do I need to re-instate the Installshield directory?
Thank you
Ian Addison