If /FILESONLY is specified, only files are copied. Fully-qualified path names should always be used with this instruction. Using relative paths will have unpredictable results.

Feature Requests item #1244812, was opened at 2005-07-26 01:04 Message generated for change (Comment added) made by kichik You can respond by visiting: Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Scripting Group: 2.0 Series >Status: Open Priority: 5 Submitted By: comperio (comperio) Assigned to: Nobody/Anonymous (nobody) Summary: CopyFiles obeying SetOverwrite function Initial Comment: It would be a nice enhancement if the CopyFiles function would look at the Overwrite mode just like the File command does. Examples of where this would be useful: 1. Our company distributes software on a CD. All files are in a directory, uncompressed, with the idea that if a file becomes corrupt on a client's PC, they can simply copy and paste the affected file. Therefore, by NOT having the files compressed into the setup.exe makes sense in this case.

Another example would be you had an installation that was part of a multi-disk set. You'd probably extact some files to a temp folder and then copy them in place. ---------------------------------------------------------------------- >Comment By: Amir Szekely (kichik) Date: 2006-07-19 16:33 Message: Logged In: YES user_id=584402 Why close this feature request? It's still valid. ---------------------------------------------------------------------- Comment By: Amir Szekely (kichik) Date: 2005-07-26 23:07 Message: Logged In: YES user_id=584402 The CopyFiles instruction is currently using SHFileOperation which doesn't support such logic. It will require rewriting CopyFiles with other APIs.

It'll fix the NT4 bug that's still open and probably some other incompatibilities of SHFileOperation between versions of Windows. ---------------------------------------------------------------------- You can respond by visiting: Thread view.

Feature Requests item #1244812, was opened at 2005-07-25 15:04 Message generated for change (Settings changed) made by comperio You can respond by visiting: Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Scripting Group: 2.0 Series >Status: Closed Priority: 5 Submitted By: comperio (comperio) Assigned to: Nobody/Anonymous (nobody) Summary: CopyFiles obeying SetOverwrite function Initial Comment: It would be a nice enhancement if the CopyFiles function would look at the Overwrite mode just like the File command does. Examples of where this would be useful: 1. Our company distributes software on a CD. All files are in a directory, uncompressed, with the idea that if a file becomes corrupt on a client's PC, they can simply copy and paste the affected file. Therefore, by NOT having the files compressed into the setup.exe makes sense in this case. Another example would be you had an installation that was part of a multi-disk set.

You'd probably extact some files to a temp folder and then copy them in place. ---------------------------------------------------------------------- Comment By: Amir Szekely (kichik) Date: 2005-07-26 13:07 Message: Logged In: YES user_id=584402 The CopyFiles instruction is currently using SHFileOperation which doesn't support such logic. It will require rewriting CopyFiles with other APIs. It'll fix the NT4 bug that's still open and probably some other incompatibilities of SHFileOperation between versions of Windows. ---------------------------------------------------------------------- You can respond by visiting. Winlite.iso 72 mb.