Compiled XP Embedded, successfully passed the FBA on the target machine, installed the driver, but found that there is a software (my target machine only need to install this thing) has not been installed, prompted cacls failure.
Estimate is what component did not add, first suspect is the problem of Windows Installer, check after found that the component has been added, and MSI format installation package can run normally; the installation package for this software is made with InstallShield, Suspect is not InstallShield what run library is wrong? InstallShield is installed on the target machine, the result is still not able to install the software, decompile the Software Installation script Setup.inx file, and did not quickly find out why.
Helpless, only try another way:
1. Use the Registry Monitoring tool (Sysinternals produced by Regmon.exe) to see what happens to the registry when the error message is prompted? But nothing unusual has been found.
2. Use the File Monitoring tool (Sysinternals Filemon.exe) to see what files were done when the error message was prompted? Haha, I finally found it, Filemon.exe prompt Call Cacls.exe when, did not find Cacls.exe file, so, hurriedly from my system to find a Cacls.exe copy to the target machine System32 directory, again installed this software, sure enough next, shun smooth benefit.
Since my system has Cacls.exe, I think XP Embedded will certainly have, Google found a component is called Primitive:Cacls.exe, but in Target designer did not search, carefully looked at the target Designer settings, found that there is a "Component Visibility" option, set its value to 100, open the target Designer again, a glance to see Primitive:Cacls.exe, hehe.
The above description is more verbose, but provides a solution to the problem, so put this article here, in order to show that encountered problems as long as can be studied, the results are soon.
Primitive:Cacls.exe component not added causes some software to not install on XP Embedded