IP 3.99 update

By Snidely Whiplash Posted March 25, 2008 15:23:53

According to both SDC and Impulse, I currently have version 3.99 installed. The history section on SDC states there is a new user Interface involved but I'm still seeing the old interface. In the Help - About section of IP, it states I have 3.00 and in the Help - History section, the last build mentioned is 3.20. I've tried using both the Iconpackager.exe and Iconpackager64.exe but both give me the same interface. My OS is Vista Ultimate 64.

+23 Karma 46 Replies 14 Referrals

"most" might be an exaggeration.

I just wanted to let everyone know that I have reported this problem to the developers this morning.

While I don't have an official fix or timetable for when a fix might be available, there may be a workaround (which enabled mspaint and msconfig to run OK on my XP machine here). Try closing out of IconPackager and renaming the iprepair.dll file (located within the IconPackager directory - C:\program files\stardock\object desktop\iconpackager) to something else, like iprepair.dll.bak.

This problem affect only Windows XP. MS Paint and MS Config + latest build of IconPackager 3.99 works fine without any problem under Windows Vista.

I've tried ip 3.99 on vista 64 and vista 32, after instaling it doesn't load.

When I reset, my icons all disappear until I uninstall it.

Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.

I've tried ip 3.99 on vista 64 and vista 32, after instaling it doesn't load.

Vista SP1?

"most" might be an exaggeration.

Zu, judging by the various problems posted I would think "most" people downloading 3.99 - whether they are using XP or Vista - will have a problem even if they have not realised it yet. I am surprised that it's still up on SDC and Impulse and would have thought that it would have been more prudent to 'pull it' whilst work is in progress to find solutions.

I am surprised that it's still up on SDC and Impulse and would have thought that it would have been more prudent to 'pull it' whilst work is in progress to find solutions.

Uninstall IconPackager alpha/beta
Uncheck > "Show pre-release versions"
Install latest stable release of IconPackager

The problem is gone. That's it!

I am surprised that it's still up on SDC and Impulse and would have thought that it would have been more prudent to 'pull it' whilst work is in progress to find solutions.Uninstall IconPackager alpha/betaUncheck > "Show pre-release versions"Install latest stable release of IconPackagerThe problem is gone. That's it!

Yep, I know Darken that's exactly what I did to put things right but not all Stardock customers use these forums and those that don't will be unaware of the issues with this build and before you know it the emails will be piling up at support. Just thought I'd suggest 'the pull' to save grief to both the company and customers.

All,

We have been working on this since Milksama brought it to our attention. We have uploaded a fix for the msconfig/mspaint issue in the latest BETA (3.99b). The build has been published to both SDC and Impulse.

Also, I am happy to announce we will have the 64-bit support in the beta within a week.

Thank you for your time and feedback.

Leo the Lion

comment 30

"most" might be an exaggeration. Zu, judging by the various problems posted I would think "most" people downloading 3.99 - whether they are using XP or Vista - will have a problem even if they have not realised it yet. I am surprised that it's still up on SDC and Impulse and would have thought that it would have been more prudent to 'pull it' whilst work is in progress to find solutions.

Leo,

The purpose of the BETA is to obtain feedback. It is not our policy to pull a BETA unless the software is just not functioning for anyone. Since we have Vista users who were providing feedback and could bring other issues to our attention, we left the BETA up (and resolved the outstanding issues quickly) to continue to obtain feedback.

As far as the weekend posts, we do not have support on the weekends (at this time) so we appreciate your patience. We recognize that most time to play with software is on the weekend so this is not an ideal situation, but not providing support on the weekends keeps the cost of our applications down which we believe is a tradeoff users are willing to make.

Thanks for your support and feedback!

Appreciate your feedback, Zargon.

This was an unusual situation where quite a few users were even wiping their drives and reinstalling and when you have customers going to that length it cannot be good for them and certainly not 'good show'for the companies products. Anyway, I understand your reasoning and applaud the fact that you have worked so quickly to provide some fixes. Thank you

thanks, zargon. i'm looking forward to it having vista64 support.

This is awesome guys! Thanks for getting the fix out for this so fast!

I currently have 3.99c[b].054 installed and I just restarted my pc for the first time since the last couple of updates to Iconpackager.

Before I shutdown I was using an Iconpackage that I had recolored with a green hue. Upon rebooting the pc it is now showing all of the icons it should be from that set with the exception of the folder icon.

The folder icon that is showing somehow reverted back to an Iconpackage I used previously and the kicker is its showing that folder icon recolored the way I had it when I used it which is a different recolor setting than I am using on the current Iconpackage.

Also upon opening IconPackager it shows as set to the same Iconpackage as before rebooting but it shows it without the recoloring settings in place.

After picking another package and recoloring and applying it everything seems fine.

Oh and i forgot to put in the above post that I am on XP SP2.

What does 3.99c add? The "View History" in impulse comes up as page cannot be found, and SDC still shows 3.99b as the newest.

I just updated to 3.99.146...on XP...colorize dosnt work,even after a reboot.

Suddenly began working...ooooweeeeeeeeeoooouuuuuu.

Kinda nice but disappointing compared to WB's colorize feature.

And now it dosnt...aawwwww.

Kinda nice but disappointing compared to WB's colorize feature.

That'd be alot nicer if we could recolor and save the recolors the way you can in windowblinds.

Once upon a time IconPackages were able to be recolorizied (and saved as new IconPackages) with IconDevelopper. It seems that this good time is over ... Surely another big improvement on those two Stardock products ...

Oh there's probably a good reason linked to Vista icons ... Very nice Vista, after loosing a lot of features in WindowBlinds just to get tranparency and translucy possibilities for Vista, here's the turn for icons ...

when it did work for a short while...it was actually recoloring the grey parts...so even if an image was grey with color...just the color wasnt being changed...it was altering the entire image...same way WB used to.

like putting a coat of paint on something...the effect is indescriminate

Hi All,

The issue and workaround for this is straightforward.

It is the "Repair Shell Icons" feature that is the problem, but you don't have to rename iprepair.dll to fix it.

2 bugs are at work here:

1. The main problem of iprepair.dll hiding the UI of several apps.
2. The process exclusion list in IP not working at all.

Here's the workaround:

If you select "Repair shell Icons for the following processes only", then you can safely add the programs to the list that you want to have affected by iprepair.dll. For those who don't know, iprepair.dll lets the file and folder icons in Open/Save dialogs be skinned by IP. EDIT: It also allows the skinning of IE Favorites icons and the skinning of file and folder icons in non-IP-aware apps like XYplorer.

I found the source of this issue and reported it to SD support over a year ago! There has been a lot of development of SD apps in the last year, and this bug fix was not a priority. It still exists in the 3.99g beta.

Good news, though. In the 3.99g beta, IP has created a new file that I've not seen before. It is the iprepair_exclusions.ini file. So now that the .ini file exists, getting iprepair.dll to recognize and use it may be on the way for the 3.4 release.

Hope this helps,
-Jeff