Path: utzoo!attcan!uunet!decwrl!apple!vsi1!hsv3!jls
From: jls@hsv3.UUCP (James Seidman)
Newsgroups: comp.windows.ms
Subject: Re: Stop Sheet1 in Excel, suggestion for Program Manager
Message-ID: <5234@hsv3.UUCP>
Date: 11 Oct 90 15:51:02 GMT
References: <8998@jarthur.Claremont.EDU>
Reply-To: jls@headland.UUCP (James Seidman)
Organization: Video Seven / Headland Technology
Lines: 35

In article <8998@jarthur.Claremont.EDU> rspangle@jarthur.Claremont.EDU (Froot Loop) writes:
>The DOS icon appears to be located in three separate files (not counting
>progman.exe):
>
>winoa286.mod
>winoa386.mod
>winoldap.mod
>
>I'm not sure if it would be possible to have several different copies of
>these files around or not - if so, you could write a little batch program
>which renames telix.mod (the modified version of winoa386.mod that you've
>made which has a new icon in it) to winoa386.mod, and then runs Telix.
>
>Anyone who knows more about icons and other such resources care to comment?

I don't think that this plan will work.  Bringing up several windowed
sessions and running HEAPWALK (which is a program which comes with the
SDK to look at the global memory heap), I see only one copy of the icon
resource.  This is exactly what I expect, since any (well-written)
Windows program checks to see if there is a previous instance of itself
already in memory, and if so uses its resources instead of loading its
own.  Since resources are (in theory if not in practice) read-only, this
saves on memory.

The only real solution would be much more complicated:  write an application
which installs a Windows hook to intercept messages.  Then you can find out
when a DOS window is being minimized, and paint your own icon over the one
that winoldap drew.  Let me know when you get it all worked out, Randy.
It's as easy as LPC. :)

-- 
Jim Seidman (Drax), the accidental engineer.
"There's a certain freedom to being completely screwed." - The Freshman
UUCP: ames!vsi1!headland!jls
ARPA: headland.UUCP!jls@apple.com