SB doesn't normally specifically copy (set) the creation stamp from the Source - it just copies 'the file' via a Windows API (assuming copying to a disk or UNC path). The Destination OS/firmware normally sets the Destination copy file's Created stamp to 'now' (date/time of copy) - without any input from SB.
We have an option to force-copy the Created stamp from the Source (that is, set the Destination copy's stamp to match the Source), but not to set it to 'now' (because that normally happens anyway, c/o the OS/firmware)
Did you check to see you you didn't have the 'copy Source stamp' setting active?
If not, your HTPC is behaving rather strangely, but all you can do in that case is create an installable script to do it.
Note that we don't write bespoke scripts for people, nor provide bespoke assistance in doing so. We provide the scripting facility, the Scripting section in the Help, and the examples provided in the program folder* and the scripting page of the website. The rest is up to the user...but you could take a look at ROCopy,vbs in your Pro program folder. This has an example of how you would trigger an action after copying each file, and how to change the attributes (though you'd need to change it to affect .DateCreated, and add VB to find out what the .DateCreated stamp of the Source file is, to copy it)
* not all scripts in the program folder are installable. Some are 'callable' (for use in Programs-Before, or similar) and/or stand-alone.
We have an option to force-copy the Created stamp from the Source (that is, set the Destination copy's stamp to match the Source), but not to set it to 'now' (because that normally happens anyway, c/o the OS/firmware)
Did you check to see you you didn't have the 'copy Source stamp' setting active?
If not, your HTPC is behaving rather strangely, but all you can do in that case is create an installable script to do it.
Note that we don't write bespoke scripts for people, nor provide bespoke assistance in doing so. We provide the scripting facility, the Scripting section in the Help, and the examples provided in the program folder* and the scripting page of the website. The rest is up to the user...but you could take a look at ROCopy,vbs in your Pro program folder. This has an example of how you would trigger an action after copying each file, and how to change the attributes (though you'd need to change it to affect .DateCreated, and add VB to find out what the .DateCreated stamp of the Source file is, to copy it)
* not all scripts in the program folder are installable. Some are 'callable' (for use in Programs-Before, or similar) and/or stand-alone.