I hope you may be able to help with this one, it's driving me around
the bend.
A Win2k machine first reported error 1607 while attempting to run setup
using an InstallShield package (first time this crapped out was
iTunes).
I followed the usual stuff as indicated by
http://consumer.installshield.com/kb.asp?id=Q108340 such as confirm
Admin privileges, delete temp directories. I just followed as
instructed with no success.
Digging further found that the machine did not have anything loaded in
the path C:\Program Files\Common Files\InstallShield\Driver --
C:\Program Files\Common Files\InstallShield\Driver\7\Intel 32\
C:\Program Files\Common Files\InstallShield\Driver\8\Intel 32\
C:\Program Files\Common Files\InstallShield\Driver\9\Intel 32\
C:\Program Files\Common Files\InstallShield\Driver\11\Intel 32\
Are all empty.
It seems like isscript was not being installed (?)
Going to the CMD window and executing "msiexec /i isscript9.msi /l*v
log.txt" created a rather large error log, ending in "returning 1603".
This file is located
http://www.geocities.com/markaren10/MSI/error_1603.pdf
Again
C:\Program Files\Common Files\InstallShield\Driver\7\Intel 32\
C:\Program Files\Common Files\InstallShield\Driver\8\Intel 32\
C:\Program Files\Common Files\InstallShield\Driver\9\Intel 32\
C:\Program Files\Common Files\InstallShield\Driver\11\Intel 32\
Are all empty.
The messages within the log file are somewhat cryptic to say the least.
If someone could take a look and give me some ideas how I should
proceed I will be very grateful.
Many thanks,
Mark.
Scanned for viruses using latest definitions using Norton Antivirus.
Scanned for Malware with ewido anti mal-ware.
The machine appears to be clean.
-Mark.