An image corrupt message means that TI can't successfully read the data from the archive and recreate the stored checksums. This validation process does provide the means to flag hardware problems which certainly can cause corrupt archive messages. The validation process, and while it is not perfect, it probably is a lot more rigorous than most other things. What other application writes a checksum for every256K of data? HDs do a CRC at the drive but once the data is on the buss it is not checked any further in normal operation. RAM data is not checked other than a cursory check on bootup which primarily is to see how big the RAM is. I've mentioned before but I think it was in Windows 95 release2, that Microsoft improved the bootup RAM test because most of the problems reported with the then new and popular disk compression was really caused by RAM. A regular PC is not a high-end server with ECC and various other schemes for improved data integrity. The basic premise is that the hardware is working properly and fortunately for us, it usually is. TI puts a pretty good load on a system with high-speed transfers of many gigabytes of data and as I mentioned previously, the data is checked when read into memory. Bad data in other types of application often is indicated by BSODs or other indications by jumps out of legal program space, lockups, or some bizarre behaviour.