Not sure how stable the PNG support in NetSurf is supposed to be, but the few test files I tried at <http://www.schaik.com/pngsuite/pngsuite.html> result in crashes like : content/fetch.c fetch_curl_data 579: fetch 0x35d6ffb8, size 61 content/fetch.c fetch_process_headers 662: HTTP status code 200 content/fetch.c fetch_process_headers 708: FETCH_TYPE, 'image/png' content/fetchcache.c fetchcache_callback 162: FETCH_TYPE, type 5 content/content.c content_set_type 229: content http://www.libpng.org/pub/png/PngSuite/x00n0g01.png, type 5 content/fetch.c fetch_curl_data 588: FETCH_DATA content/fetchcache.c fetchcache_callback 173: FETCH_DATA content/content.c content_process_data 252: content http://www.libpng.org/pub/png/PngSuite/x00n0g01.png, size 61 riscos/png.c nspng_process_data 67: data 0x35ce9a80, size 61 libpng error: Image width or height is zero in IHDR "riscos/png.c", line 64: nspng_process_data: Assertion failed: 0 Fatal signal received: Aborted A stack backtrace will now follow ...) stack backtrace: pc: 179554 sp: 213c20 ^write_backtrace() pc: 18c220 sp: 213c48 ^post_signal() pc: 18c520 sp: 213c60 __unixlib_raise_signal() pc: 823f8 sp: 213c70 raise() pc: 8122c sp: 213c84 abort() pc: 1039fc sp: 213cb4 __assert_fail() pc: 42558 sp: 213d18 nspng_process_data() pc: bb90 sp: 213d3c content_process_data() pc: d474 sp: 213df4 ^fetchcache_callback() pc: a3c7c sp: 213e1c ^fetch_curl_data() pc: 12168c sp: 213e3c ?() pc: 163520 sp: 213edc ?() pc: 4f954 sp: 213f0c ?() pc: a3988 sp: 213f30 fetch_poll() pc: ae4b8 sp: 213f44 ^netsurf_poll() pc: ae3b4 sp: 213f60 main() pc: 178d44 sp: 213f78 _main() John. -- John Tytgat, in his comfy chair at home BASS John.Tytgat(a)aaug.net ARM powered, RISC OS driven