On 06/06/2012 08:35 PM, Darrell Anderson wrote: I think that is the case. However, this doesn't cause unexpected behavior and it isn't a build error such as the direct access to the png_info struct, etc.. I don't know what is causing it, but we do need to clean it up. All of the stray 'warnings' are telling us that something is not right. I'm always suspicious that 'warning1 + warning2 = unforeseen errors'. What does this mean: libpng warning: Interlace handling should be turned on when using png_read_image Is something not started or initialized before a call to png_read_image? I'll google around, if you already have the answer, let me know... -- David C. Rankin, J.D.,P.E.