Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!uwm.edu!linac!midway!msuinfo!USER2@cgevs3.cem.msu.edu
From: user2@cgevs3.cem.msu.edu (Stephen Medlin)
Newsgroups: comp.windows.ms
Subject: Icons and *.ICO Files
Message-ID: <00948496.3FF72760@cgevs3.cem.msu.edu>
Date: 8 May 91 12:22:20 GMT
Sender: news@msuinfo.cl.msu.edu
Reply-To: user2@cgevs3.cem.msu.edu (Stephen Medlin)
Organization: MSU_Chemistry
Lines: 19

I'm wondering if someone can provide a reason for an empirical discovery that I 
made:  Before I put a larger hard disk on my computer, I was running out of
room--I had killed most of the obvious things and I decided that I would
get rid of all of my icon files (both EXE and ICO files).  I assumed that
all of the icons that I had assigned to group items would be gone and I
would be left with the default PROGMAN icons.  Lo' to my surprise, I still
have all of the icons "stuck" to the items.  I had expected that windows
read in the icons at boot time and applied them to the groups, but that
is not obviously what it does.  It seems to me that this is a really neat
feature/bug, because I can now keep all of my icons on floppy, apply new 
icons to new entries, and keep the *.ICO files off the HD.  Can someone
let me know why Win3 does this and/or any reasons to not do this (other than
the slowness of accessing icons from floppy).  Otherwise, this is a great
trick for people out there with limited HD space (now a days, even 40 MB 
is too small).  

If I get enough replies, I will summarize and re-post.

Stephen Medlin