Greg Chicares wrote: > Might this file: > 1a652c4c8c31b80c85d6cbc2b4093060 *hippo.ico > be somehow malformed? My computer BSODs every time I try to view > it in 'irfanview'. This has happened three times in a row.
BSOD? Well, *any* BSOD is by definition a bug inside ring 0 (e.g. the core Windows kernel, or a graphics driver. So, it isn't *.ico's fault. Still, it'd be good to avoid... > I tried opening the icon file in gimp-2.2.4, which crashed with: > winicon.exe caused an Access Violation at location 00402795 > in module winicon.exe Reading from location 00000008. > (no BSOD). Yet the icon displays successfully in 'windows explorer'. That's a pretty old version of gimp... > An .ico file actually can cause an application to crash: > http://securitytracker.com/alerts/2007/Jun/1018202.html > That tracker says ms planned to patch the problem, but right now > I'm using XP SP1, so I wouldn't have that patch. Hmmm. Well, the .ico contains the *vista*-approved sizes: 256x256 32bit RGBA .png-compressed 64x64 32bit RGBA 48x48 32bit RGBA 48x48 8bit 256-color indexed (1bit transparency) 48x48 4bit 16-color indexed (1bit transparency) 32x32 32bit RGBA 32x32 8bit 256-color indexed (1bit transparency) 32x32 4bit 16-color indexed (1bit transparency) 24x24 32bit RGBA 24x24 8bit 256-color indexed (1bit transparency) 24x24 4bit 16-color indexed (1bit transparency) 16x16 32bit RGBA 16x16 8bit 256-color indexed (1bit transparency) 16x16 4bit 16-color indexed (1bit transparency) Supposedly, the 256x256 png-compressed size should be ignored on platforms that do not support it -- but maybe that's causing your problem. Try the attached version, which omits the 256x256 resolution. -- Chuck
hippo_xp.ico.gz
Description: application/gzip
-- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
