So I clicked Rebuild Icon Cache & IP changed my wallpaper
Monday, June 20, 2005 by aimzzz | Discussion: IconPackager
It's true... but Rebuild Icon Cache is the 2nd of 2 issues. I'm using IP 3.00.090, but the 1st problem began several builds ago. It's the reason I was fooling around with features I'm unsure of.
1) IP replaces the icons on my .exe files (& consequently all their shortcuts) with the generic icon from the pkg I loaded. If I try to change shortcuts back to the default icon manually (thru properties setting}, they revert to the generic setting.
I looked in the list of IP Settings & can't find anything that addresses .exe's. (Not the same thing, but I always selected Only load File Icons for regestered file types.)
There's no access to .exe icons or to program shortcuts in Icons & Cursors
I'm assuming there's a setting I missed somewhere, but how do I get IP to leave my .exe's alone?
2) In trying to find an approach to (1) above, I clicked Rebuild Icon Cache. Can't find documentation for this feature, but I assumed it would reset the cache of Loaded icons back to the pkg I had selected if I had made any changes. Wasn't sure if it would also change the applied icons or not. Anyway, I clicked it to see what it does & after a couple of flashes, the wallpaper changed-- and to a picture I don't remember ever seeing before (I'm sure I just forgot I had it)
I would like to suggest that StarDock make documentation available that at least identifies the intended functionality of each feature exposed to the user. I've worked in software & I know there's only so much time, but as a user, it's not reassuring to have to guess what might happen if I push this button. (Though it's a safe to guess that IP isn't a wallpaper changer...)
1) IP replaces the icons on my .exe files (& consequently all their shortcuts) with the generic icon from the pkg I loaded. If I try to change shortcuts back to the default icon manually (thru properties setting}, they revert to the generic setting.
I looked in the list of IP Settings & can't find anything that addresses .exe's. (Not the same thing, but I always selected Only load File Icons for regestered file types.)
There's no access to .exe icons or to program shortcuts in Icons & Cursors
I'm assuming there's a setting I missed somewhere, but how do I get IP to leave my .exe's alone?
2) In trying to find an approach to (1) above, I clicked Rebuild Icon Cache. Can't find documentation for this feature, but I assumed it would reset the cache of Loaded icons back to the pkg I had selected if I had made any changes. Wasn't sure if it would also change the applied icons or not. Anyway, I clicked it to see what it does & after a couple of flashes, the wallpaper changed-- and to a picture I don't remember ever seeing before (I'm sure I just forgot I had it)
I would like to suggest that StarDock make documentation available that at least identifies the intended functionality of each feature exposed to the user. I've worked in software & I know there's only so much time, but as a user, it's not reassuring to have to guess what might happen if I push this button. (Though it's a safe to guess that IP isn't a wallpaper changer...)
aimzzz
Reply #2 Monday, June 20, 2005 9:43 PM
Reply #2 Monday, June 20, 2005 9:43 PM
Thanks! I had assumed I could get the .exe icons back with Restore All Icons, but tried it just now & it behaved as described above (ie, applied the generic icon to the .exe's-- the difference being, with Restore, the generic is the XP generic)
What does Rebuild Icon Cache actually do? I wrote my guess in the 1st post, but have not idea if I'm right.
What does Rebuild Icon Cache actually do? I wrote my guess in the 1st post, but have not idea if I'm right.
werewolf
Reply #3 Monday, June 20, 2005 9:52 PM
Reply #3 Monday, June 20, 2005 9:52 PM
Your guess is the same thing that I guessed and I have no idea if I'm right or wrong. Your guess sounds logical.
The latest update of IconPackager supposedly fixes the .exe problem.
The latest update of IconPackager supposedly fixes the .exe problem.
aimzzz
Reply #4 Monday, June 20, 2005 10:04 PM
Reply #4 Monday, June 20, 2005 10:04 PM
I just got out of regedit & had the same result as you-- The 1st 2 items were OK, but the key in #3 did exist-- but not anymore!
Thanks for your help. I'll run Restore All Icons & take it from there. Have a good evenin' & take care
Thanks for your help. I'll run Restore All Icons & take it from there. Have a good evenin' & take care
aimzzz
Reply #5 Monday, June 20, 2005 10:30 PM
Reply #5 Monday, June 20, 2005 10:30 PM
Yeah!
The .exe's & program shortcuts are back now. Thanks again
BTW, the wallpaper *was* a picture I never saw before-- It was a wall that came with a new WindowBlind I installed a couple of hours before my 1st comment. Don't know why it spontaneously appeared-- could have been a coincidence that it happened when I clicked Rebuild Icon Cache. Dunno what might have brought it to the screen
The .exe's & program shortcuts are back now. Thanks again
BTW, the wallpaper *was* a picture I never saw before-- It was a wall that came with a new WindowBlind I installed a couple of hours before my 1st comment. Don't know why it spontaneously appeared-- could have been a coincidence that it happened when I clicked Rebuild Icon Cache. Dunno what might have brought it to the screen
Bichur
Reply #6 Tuesday, June 21, 2005 12:01 AM
Reply #6 Tuesday, June 21, 2005 12:01 AM
Glad you got it fixed. 
When I read the title, my first thought was> whoa, you really need a bigger monitor.
When I read the title, my first thought was> whoa, you really need a bigger monitor.
OhGimmeABreakWhatIsThisFor
Reply #8 Saturday, June 25, 2005 11:22 PM
Reply #8 Saturday, June 25, 2005 11:22 PM
> I would like to suggest that StarDock make documentation available that at least identifies the intended functionality of each feature exposed to the user. I've worked in software & I know there's only so much time
Stardock, like WP and all the others with whom I've been even remotely involved, has a class of followers who make themselves available to help others learn the ropes to using various utilities and applications. I don't know that I'd be on this board right now were it not for the patience on the part of the volunteers at the WordPerfect forums on CompuServe oh so many years ago; later I became a paid worker providing similar support for WP users on AOL.
Many of these go on to write useful (though sometimes crudely written) third-party manuals that contain a world of information for users. (Hint! Hint!) Okay, I'll name names: Gordon McComb helped me become a power macro writer in the WordPerfect program; Woody Leonhard, co-author of the various Mother Of All Windows ___ Books, though I've never contacted him, enabled me to hack the registry and generally pick my way through the various settings in Windows -- without ruining my system (backup backup backup).
One problem I see with Stardock products (and with many products these days) makes itself manifest every time I open up the Stardock program: there's a new upgrade to something every two or three days! That can make it virtually impossible to provide help other than what's available on these boards. (At least now we can post Stardock questions without revealing our addys to the spammers!)
> Don't know why it spontaneously appeared-- could have been a coincidence that it happened when I clicked Rebuild Icon Cache.
Ha, ha, ha! Moments ago I was simply viewing some icon packages I had downloaded last week, and suddenly now all the icons in my QuickLaunch are the Program Group icon for some package or another (but not the one that's currenly loaded onto my system)!
Reboot, I say! Reboot!
If that doesn't fix it, then I've got a backup copy of the QuickLaunch shortcuts, complete with icons. Setting the shortcut to Read Only usually keeps programs from meddling with them, which is why I suspect this one will clear up with a simple reboot (at least my 30th reboot of the day). Yes, I just bought a bunch of new equipment: yet another rack of USB jacks, a new Mickeysoph mouse, a new Mickeysoph ergonomic keyboard (doesn't anybody else make these?), and a new scanner. And I've also been trying to get a couple of unwieldly Stardock setups to calm down. Still, it looks as if I'll have to spend some time over on the Mickeysoph hardware boards -- wherever they are (Google, Google, Google!).
Take care!
CliffWalkingFool
aka The Zero Card
Stardock, like WP and all the others with whom I've been even remotely involved, has a class of followers who make themselves available to help others learn the ropes to using various utilities and applications. I don't know that I'd be on this board right now were it not for the patience on the part of the volunteers at the WordPerfect forums on CompuServe oh so many years ago; later I became a paid worker providing similar support for WP users on AOL.
Many of these go on to write useful (though sometimes crudely written) third-party manuals that contain a world of information for users. (Hint! Hint!) Okay, I'll name names: Gordon McComb helped me become a power macro writer in the WordPerfect program; Woody Leonhard, co-author of the various Mother Of All Windows ___ Books, though I've never contacted him, enabled me to hack the registry and generally pick my way through the various settings in Windows -- without ruining my system (backup backup backup).
One problem I see with Stardock products (and with many products these days) makes itself manifest every time I open up the Stardock program: there's a new upgrade to something every two or three days! That can make it virtually impossible to provide help other than what's available on these boards. (At least now we can post Stardock questions without revealing our addys to the spammers!)
> Don't know why it spontaneously appeared-- could have been a coincidence that it happened when I clicked Rebuild Icon Cache.
Ha, ha, ha! Moments ago I was simply viewing some icon packages I had downloaded last week, and suddenly now all the icons in my QuickLaunch are the Program Group icon for some package or another (but not the one that's currenly loaded onto my system)!
Reboot, I say! Reboot!
If that doesn't fix it, then I've got a backup copy of the QuickLaunch shortcuts, complete with icons. Setting the shortcut to Read Only usually keeps programs from meddling with them, which is why I suspect this one will clear up with a simple reboot (at least my 30th reboot of the day). Yes, I just bought a bunch of new equipment: yet another rack of USB jacks, a new Mickeysoph mouse, a new Mickeysoph ergonomic keyboard (doesn't anybody else make these?), and a new scanner. And I've also been trying to get a couple of unwieldly Stardock setups to calm down. Still, it looks as if I'll have to spend some time over on the Mickeysoph hardware boards -- wherever they are (Google, Google, Google!).
Take care!
CliffWalkingFool
aka The Zero Card
WhiteshooZ
Reply #9 Thursday, July 14, 2005 8:17 AM
This does not exist in my registry at all... Do I need to make it? And if so, how?
Thanks
Reply #9 Thursday, July 14, 2005 8:17 AM
| HKEY_CLASSES_ROOT\lnkfile\\shellex\\IconHandler (default)={00021401-0000-0000-C000-000046} |
This does not exist in my registry at all... Do I need to make it? And if so, how?
Thanks
aimzzz
Reply #10 Tuesday, July 26, 2005 1:51 PM
Reply #10 Tuesday, July 26, 2005 1:51 PM
NO! The program could have been changed in a way that makes it unnecessary. 
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Reply #1 Monday, June 20, 2005 9:08 PM
Check the registry for these settings:
HKEY_CLASSES_ROOT\exefile\DefaultIcon
(default)=%1
HKEY_CLASSES_ROOT\lnkfile\\shellex\\IconHandler
(default)={00021401-0000-0000-C000-000000000046}
HKEY_CLASSES_ROOT\exefile\shellex\IconHandler (if this key exists, DELETE it).
If you did make any changes to your registry, you will need to rebuild the icon cache.