Reply to "DCS LOADER ERROR WITH CHAIN FILES"

6/26/17 UPDATE:

On the advice I received from this thread, I attempted an upload of chain files again for the problem locomotive.  A different set of conditions was used for this test, which are listed below:

1.   A different Windows 7 PC was used, one that has run various DCS updates successfully in the past.
2.   A different TIU was used, one that has also been a part of successful sound and DCS operating system updates in the past.
3.   The test rig was an isolated 40" section of Atlas track, powered by a regulated 16VDC supply.  This powered Fixed Channel #1 on the TIU.

The procedure was performed as listed below.

1.   The TIU was powered up, followed by a ~60 second hold.
2.   The locomotive was powered up, followed by a ~60 second hold.  (NOTE: the alternate headlight flashing behavior was observed).
3.   A factory reset of the locomotive's P3 board was performed via the remote, followed by a ~120 second hold.
4.   The locomotive was powered down, followed by a ~120 second hold.
5.   The locomotive was powered up, and 'started' via the remote.  Sound and visual effects were normal, however there was no response to motion commands from the remote.
6.   The locomotive was 'shutdown' via the remote, and a sound file upload initiated via the DCS 5.0 loader.  This ran successfully, resulting in the same effects behavior reported in step #5.  This was followed by a ~120 second hold.
7.   The locomotive was 'shutdown' via the remote, and a chain file upload initiated via the DCS 5.0 Loader, using the 'Flash' button as prescribed in the DCS Companion.  This resulted in the same failure screen as was originally reported.  This was followed by a ~120 second hold.
8.   The locomotive was powered down, followed by a ~120 second hold.
9.   The locomotive was powered up, and the alternate headlight flashing behavior was observed.  The was followed by a ~120 second hold.
10.   An attempt was made to 'start' the locomotive via the remote.  There was no response to any commands from the remote. 

At this point, it appears this locomotive needs to be sent to MTH for a true 'factory reset'.  If there is any part of this procedure that is not correct, or I performed erroneously, please let me know.  Otherwise, thank you all for your input and advice.