Re: Hippo icon for cygwin...

2009-12-07 Thread Greg Chicares
On 2009-12-06 18:33Z, Charles Wilson wrote:

[...vista-sized icons cause crashes on old XP machines...]

 Well then, what happens if the icon in question is inside a DLL?

We have a winner.

 Can you try creating a shortcut, and setting its icon to the hippo in
 each of these two DLLs?  The _vista one has the hippo with all
 resolutions including 256x256 png, and the _xp one has the hippo with
 everything but that.

On both machines--XP SP1 and XP SP2--these shortcuts seem
well behaved. Their icons are hippos in windows explorer.
They remained hippos when I copied both shortcuts to each
machine's desktop. No crash was observed with the dll as
the source of the icons.

Just for yucks, I tried dropping both resource dlls on the
1997 borland C++ 5.02 IDE, which is designed to extract
resources from executable binaries. The 'xp' dll loaded
fine: I could see all the icons, and even manipulate the
hippo. The 'vista' dll failed to load, giving a messagebox:
  Resource compiler error: Invalid icon format
I also tried dragging and dropping the 'vista' dll on my
2004 copy of 'irfanview'; it correctly displayed the classic
32x32x24bpp Cygwin icon.

--
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



Re: Hippo icon for cygwin...

2009-12-05 Thread Robert Pendell
On Sat, Dec 5, 2009 at 4:06 AM, Charles Wilson wrote:
 for your enjoyment. It's based on public domain art; this version
 released under a creative commons license (CC-BY-SA 3.0) which is GPL
 compatible.

 If ya'll like it, I might put it into cygicons.dll eventually.

 --
 Chuck


I like it.  Oh and by the way.  The file never got bzip compressed.
It is just a standard tar archive.  For decompression if you use
cygwin tar then leave out the -j parameter so it doesn't bother
trying.  For native archive manager drop the .bz2 extension. ;)

--
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



Re: Hippo icon for cygwin...

2009-12-05 Thread Corinna Vinschen
On Dec  5 04:06, Charles Wilson wrote:
 for your enjoyment. It's based on public domain art; this version
 released under a creative commons license (CC-BY-SA 3.0) which is GPL
 compatible.
 
 If ya'll like it, I might put it into cygicons.dll eventually.

It's absolutely cute!  But... what is that second hippo doing in the
background?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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



Re: Hippo icon for cygwin...

2009-12-05 Thread Greg Chicares
On 2009-12-05 09:06Z, Charles Wilson wrote:
 for your enjoyment. It's based on public domain art; this version
 released under a creative commons license (CC-BY-SA 3.0) which is GPL
 compatible.

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.

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 0008.
(no BSOD). Yet the icon displays successfully in 'windows explorer'.

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.


--
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



Re: Hippo icon for cygwin...

2009-12-05 Thread Charles Wilson
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 0008.
 (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

Re: Hippo icon for cygwin...

2009-12-05 Thread Reid Thompson

Charles Wilson wrote:

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.


irfanview handles it fine on my box (XP).

--
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



Re: Hippo icon for cygwin...

2009-12-05 Thread Robert Pendell
On Sat, Dec 5, 2009 at 9:27 AM, Charles Wilson wrote:
 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...


Not necessarily.  A BSOD can be caused by any faulty driver,
application, or service in the system.  It can also be caused by
faulty hardware.  Bad ram will cause memory corruption and make
programs or drivers fail to run properly.  I have diagnosed BSOD
errors before and tracked them down to both faulty ram and faulty hard
drives.  Using windbg to identify the culprit helps.

Robert Pendell
shi...@elite-systems.org
CAcert Assurer
A perfect world is one of chaos.

--
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



[OT] Re: Hippo icon for cygwin...

2009-12-05 Thread Dave Korn
Robert Pendell wrote:

 Using windbg to identify the culprit helps.

  Yes, anything else is pointless speculation; these kinds of crashes are way
too esoteric to waste time guessing at.  Enable full crash dumps in the system
preferences, install windbg, trigger the crash, then (after rebooting) open
memory.dmp in windbg; the output of analyze -v should tell you at once which
driver was on top of the stack and so should be suspected.  If you're lucky,
you'll see the driver name on the BSoD and won't have to go to such lengths,
but if it's a level or two up the stack when the crash happens, you'll need a
debugger to show you the relevant module name.

cheers,
  DaveK

--
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



Re: Hippo icon for cygwin...

2009-12-05 Thread Greg Chicares
On 2009-12-05 14:27Z, Charles Wilson wrote:
 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.

Yes, apparently it's an XP SP1 kernel defect: in 'win32.sys',
PAGE_FAULT_IN_NONPAGED_AREA, STOP 0x0050.

I also tried the original .ico on an XP SP2 machine, which produced
a different BSOD. That machine was set to reboot itself upon BSOD,
so I didn't have time to record the message; but the program name
began with 'ati', so it was almost certainly a graphics driver.

But those are defects in ring-zero programs, so it's their job to
avoid crashing no matter what .ico file is handed to them. The
resulting vulnerability is their fault--not the .ico's fault.

BTW, both these machines have no known hardware problems, and
recent full runs of memtest86 indicate that their RAM is fine.

 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 0008.
 (no BSOD). Yet the icon displays successfully in 'windows explorer'.
 
 That's a pretty old version of gimp...

It's a native msw build that was released 2005-03-03: quite old,
I agree. Still, I'm probably not the only person running Cygwin
on a 2005-vintage system, so it's good to isolate the problem...

 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:

Okay, yet many large-corporation IT departments are sticking
with XP for the foreseeable future, even for brand-new machines.
And apparently the vista-sized icons aren't gracefully ignored
by XP (SP1 at least), no matter what ms may say. BTW, the
graphics drivers on the SP2 machine were current when I checked
them for updates about two weeks ago.

 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.

This new .ico works fine in every graphics program I can find,
even on the XP SP1 machine--specifically including the two
programs that failed with the original icon.

--
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



Re: Hippo icon for cygwin...

2009-12-05 Thread Dave Korn
Greg Chicares wrote:
 but the program name began with 'ati'

  There's your problem, right there.

cheers,
  DaveK

--
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