Between the 1st and 2nd putbacks for CR 6601859 it was discovered that additional action is needeeed to make the MoveFile.idt change effective in moving the 7-Zip SDK LZMA native library lzma.dll to a place where the Java Kernel core libraries can access it. At the same time, numerious test scenarios involving use of the j2re-image-kernel directory, running the JK .msi directly, and running the JK online installer make it clear that it's easy to be frustrated by failures stemmming from lack manual setup of the native library location.
After finding/fixing the problem preventing the MoveFile action from working  a strategy needs to be used to prevent developers wasting time. Here's an initial proposal:
   1) After a build end up with lzma.dll in $OUTPUTDIR/lib/deploy and
       $OUTPUTDIR/j2re-image-kernel, HOWEVER
   2) Omit it from production .msi files.
   3) Put the lzma.dll file in the same directory as the JK .msi file on deployment web
      servers with an email list note that both have to be downloaded to the same location
      to enable the .msi file to be executed directly.
   4) Explain that when the JK online installer is executed, the lzma.dll file will first
      "appear" in the same folder as the .msi file and then 
The result of this will be an additional ~60000 byte savings on the .msi file size and minimal wasted time from test failures caused by the native lib being in the wrong place at the wrong time.