rodalpho rodalpho

Iconpackager screwed me on windows 7

Iconpackager screwed me on windows 7

I tried out the current iconpackager trial, and it totally messed up all of my icons. They're all wrong; my DVD icon looks like a floppy disk, my default icon is a big UAC shield, and so on. Restoring to windows default doesn't help, uninstalling iconpackager doesn't help, and running the odnt_zapper doesn't help.

Reading through the forums, it looks like my mistake was installing 4.2 on windows 7, and this is fixed with version 5.0-- but I can't get version 5.0 without paying, which obviously I'm not particularly inclined to do at this exact point in my life. Can anyone help with this? Am I basically out of luck?

18,159 views 29 replies
Reply #26 Top

I can confirm that iconpackager 4.2 runs like a charm on Windows 7 Ultimate (32bit and 64 bit). Both are genuine and untouched installations. Looking at when the posts have been made, i guess he also did not want to pay for Windows 7 (which at that time was not officially available yet.....).

But then to be honest: I confess being one of these crazies who congregate on legal support forums rather than on warez sites

Reply #27 Top

Looking at when the posts have been made, i guess he also did not want to pay for Windows 7 (which at that time was not officially available yet.....).
End of quote

Many people had legitimate installations of Windows 7 will before the date of this thread.

This one on my primary machine [Win 7 Ultimate 64bit] was installed on 17th August 2009.  There were earlier ones than that though in my case they were RC installs which would be time-limited.

This one is RTM...;)

Reply #28 Top

Hi all,

I am using Win 7 (french language) with iconPackager 5.00.021 (downloaded from impulse). When IP install a new set of icons it makes modifications directly inside c:\windows\system32\imageres.dll ... original size and date changed in my Win 7.

When IP reverts to the original set of icons it's unable to restore the original file structure of imageres.dll. I guess that because size of imageres.dll isn't the same as the original + original live folders icons are missing !! Exploring live folder data (no 153) inside imageres.dll I noticed the icon of the previous theme is still present and used by IP. Looking inside IP all the live folders are blank and didn't work to change them manually.

The work around I've found is to rename imageres.dll into imageres.old and then copy from a backup the original untouched imageres.dll. After that open IP and in the settings rebuild the icon cache.

I hope stardock will fix this annoying issue some day ...

Grettings

Reply #29 Top

Incompatibility is one thing. Overwriting icon files with nothing is another. Yeah check the requirements, whatever. Are you going to sit there and tell me you have never installed something that was designed for anther OS just to see if it will run (because 50% of the time it does)? And yes, 4.2 does run, and yes, occasionally you find that piece of software that will not and even then you may have to boot into safe mode to get rid of it. But once it's gone everything works just fine! However, this is the first program I have EVER run into that has incompatibility issues that completely destroys part of the system cache.

THERE NEEDS TO BE A WARNING SO PEOPLE UNDERSTAND WHAT MIGHT HAPPEN DUE TO INCOMPATIBILITY!

Wouldn't you be a little upset if you installed something that bricked your system with option for recovery and the company never told you it might happen if your system is incompatible? Most respectable software will stop you before you completely install it if it knows it isn't designed for the environment you are about to install it on.

Telling someone they are an idiot because they didn't read the requirements and that means they are just S.O.L. is about the biggest kick in the teeth I have ever seen. If you don't know how to fix it, then keep your unproductive opinions to yourself. Grow up.