The error message was, 'MSI cannot be ran directly. Setup.exe must be used.' After inspecting the msiexec.exe command line options, I tried 'no graphical user interface mode' or '/qn': 'msiexec.exe /qn /a TARGETDIR=' and this worked beautifully. Next I simply copied the appropriate hierarchy of files to the appropriate destination, which was obvious (i.e. TARGETDIR windows system32 would go to C: windows system32, etc.). But the key was getting the c: windows inf content in place. Because this was a hardware installation, a reboot triggered the install, and the appropriate installation package (the one manually extracted above) was chosen and installed. If I had to run the installation manually, I would right click on the C: windows inf.*.inf file copied over from above, and click install. I had to do this on the dual boot for the C: WINNT INF ie.inf file because a windows xp IE 7 update desynchronized the versions the two dual boot OSs (winxp and win2k3) instances believed to be installed. Como alterar medidor de luz digital cfe update# I didn't realize the Program Files folder being common to both operating systems would be a headache before I decided to do this.
0 Comments
Leave a Reply. |