Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!sol.ctr.columbia.edu!samsung!cs.utexas.edu!rice!uw-beaver!ubc-cs!alberta!dvinci!news
From: lowey@dvinci!herald.usask.ca (Kevin Lowey)
Newsgroups: comp.os.os2
Subject: Re: Installing an Icon
Message-ID: <1990Feb16.224120.14222@dvinci.usask.ca>
Date: 16 Feb 90 22:41:20 GMT
References: <775@sce.carleton.ca>
Sender: news@dvinci.usask.ca
Reply-To: lowey@dvinci!herald.usask.ca
Organization: University of Saskatchewan
Lines: 37

From article <775@sce.carleton.ca>, by ajai@sce.carleton.ca (Ajai Sehgal):
> 
> I downloaded Logicomm from SIMTEL, it came with a file called Logicomm.ico.
> Can anyone tell me how to install the icon in PM for v1.2?

Full Screen programs know nothing about the Presentation Manager, so
naturally the .EXE files don't store any Icon information  for the 
application.  Instead, these applications get the default VIO icon 
(the terminal screen with OS/2 in it).

However, you can have special "icon" files (ending .ICO).  To activate these
put them in the same directory as the .EXE file you want it associated
with.  Name the .ICO file the same as the .EXE file, but with the .ICO 
extension.

Now when the program is minimized, it will use the icon described in the 
.ICO file. 

For example, I put the Logicomm icon in the same directory as my KERMIT.EXE
file, and renamed the .ICO file KERMIT.ICO.  Now the Kermit program uses
the Logicomm icon (two PC's connected by a lightning bolt).

Version 1.2 of OS/2 has expanded this for use with data files as well. 
From within the File Manager, you can use the Extended Attributes option
to provide the name of a .ICO file you want to associate with
that file.  From then on, that Icon will be displayed for that file within 
the File Manager.

I have a collection of .ICO files for various purposes on my Opus bulletin
board.  (306) 966-4857, 300, 1200, 2400 baud.  The file name is
ICONS-HS.ZIP and is about 7K.  You will need the PKUNZIP program to unpack
this archive.

This BBS also has many other OS/2 programs available.  Unfortunately I
do not have FTP access here otherwise I would make it available.

-- Kevin Lowey (1:140/43 - LOWEY@SASK.USASK.CA)