It seems there is the opinion that this warning is not necessary and confuses the standard user.
Maybe in this case most of all copied (system) files propably are identic with the already present file.
But what is with files like 'Setup.exe' or 'License.txt'?
That just as introduction, the issue because I write this topic, is much more critical.
I was 'hunting a bug' and found a line:
RegWrite,HKLM,0x7,"WB-Setup\ControlSet001\Control\Session Manager\Memory Management","PagingFiles","NUL: 0 0"
0x7 is Reg_Multiple_Sz!
What, if there is already a content from a previous script?
Could be e.g. with the Path environment variable.
IT IS LOST!
The above code should be written similar like this:
RegHiveLoad,WB-Setup,%target_sys%\setupreg.hiv Set,%Current%,NIL If,EXISTREGKEY,HKLM,"WB-Setup\ControlSet001\Control\Session Manager\Memory Management","PagingFiles",RegRead,HKLM,"WB-Setup\ControlSet001\Control\Session Manager\Memory Management","PagingFiles",%current% If,EXISTVAR,%Current%,Set,%Write%,%Current%#$cNUL:#$s0#$s0 Else,Set,%Write%,NUL:#$s0#$s0 RegWrite,HKLM,0x7,"WB-Setup\ControlSet001\Control\Session Manager\Memory Management","PagingFiles",%Write% RegHiveUnLoad,WB-Setup
(maybe it is worth to think about a 'RegAddMultiple' command)
Second issue:
Several scripts RegWrite to an 'Enum' key, using the value the script author has found on his own PC.
Sample:
reg_add,0x0,"%reg%\ControlSet001\Enum\Root\NET\0000\Device Parameters"What, if '0000' already is defined?
We have a script command
RegGetNext,HKLM,%reg%\ControlSet001\Enum\Root\NET,%var%which would assign '0001' to %var% in this case.
But I did not find any script where this is used.
All prefer to use 'Author's number'
@lancelot: In LiveXP you exclude some NIC drivers each other.
Maybe here is the reason?
I think that nobody should worry about warnings, nor overwrite existing reg keys w/o any scruple.
Non-cooperative scripts are bad scripts!
Peter