InstallShield script copy file FAQs

Many friends often ask: why is it invalid for me to copy files using the copyfile/xcopyfile function?
There are many reasons for this situation. I have summarized it a little today. You are welcome to follow this article to find some incomplete information.
1: The file path is incorrect. For example, the copyfile/xcopyfile script is put in onfirstuibefore, but the Referenced File Path is installdir/targetdir.ProgramThe installation file has not been copied to the user's installation path. Of course, the file that can be copied cannot be found.
Debugging and solution: Use the findfile function to determine whether your file path is correct before any copy operation. If necessary, adjust the location of the script.

2: function parameter usage error. For example, if xcopyfile copies all files, the parameter format is XXX \\*. *, some friends just write the name of the folder to be copied without wildcards *. * If all files under the folder are matched, the copy operation is unsuccessful.
Debugging and solution: Read the example of the built-in function several times.

3: protection measures for sensitive areas. Common ones include Windows Server and Windows Server. Some sensitive areas of the system disk are strictly protected. Operations with common permissions cannot copy files.
Debugging and solution: try to change the function copy to the normal non-system disk path to determine whether the operation is successful, so as to determine whether the problem is caused by operating system protection. Solution: For Windows permissions, there is no special solution. It is nothing more than improving the permissions of the installation package. For example, in release, you can select required execute level as highest available. Sometimes you still need to do some less elegant things, for example, you can change the configuration to improve the permission after packaging, see
Http://hi.baidu.com/westsky/blog/item/a114f4390bb1cafd3b87ceec.html