>>The thing (about my experiment) that still puzzles me is this. I refreshed and
>>refreshed the desktop and the 256 color icon (supposedly) didn't go away. I re-
>>boot, and it's the Fox head. OK, so I rebuild with the original icon (16
>>colors only) and refresh. The Fox head stays. I go to the property sheet, see
>>the icon is change icon dialog. Select it, refresh the desktop. The Fox stays.
>>No matter what I do, the Fox stays. Then I re-boot...the original icon is back.
>>
>>You got any clue here, Garrett? I know I don't.
>
>Not much of a clue. What happens if you try it with a VB app w/custom icon?

I tried with VC++ (it was, believe it or not) easier than dealing with VB on a "quickie"). Interestingly, VC++ attached both icons as seperate files. When I combined them into one (with one as a 256 color icon) the shortcut was fine, even after re-boot.

VFP's another story, however. Just to see what I could see, I tried a single file with VFP 6 and 7. The shortcuts were, as one might expect, the Fox. I then dragged out a couple of programs (one of which is mine), designed to view and extract icons from a DLL or executable. Both showed the Fox as the only icon in the file.

By contrast, when, in VC++, the two files were separate, both were seen. When combined as one, only the large one appeared.

If I had to hazard a SWAG, I'd say that if the large icon is 256 colors, the compiler inserts the Fox, in addition to the specified icon. Interestingly, when compiled with an icon file (with one containing 256 colors and a 16x16 16 color small one), the application in the Windows Explorer correctly shows the small icon. This indicates that the icon file is, indeed in the file. However, I would say that, for some reason, the Fox head is inserted before it. I really don't know how else to explain it.