See my note on Pg 13 in the "Impulse Official Support Thread" forum regarding the IconPackager 'change individual' icons problem.

@Ruben: May I suggest that you remove IconPackager, run CCleaner afterwards, and re-install with Impulse.

Birger

@birger

hm, something like that I will need to do - interesting though

I gave it another try, answered all question with -don't keep and everything worked fine, till I dared to change an existing setting -explorer trouble started again. So for now, ip will stay off my system

And aslong as impulse is not being fixed on how it installs its downloads - see threads for that -I think I will stay away from that too.Last time I tried I ended up haveing 2 wb's and two od versions on my system

Ruben

Here's what's (copy from Impulse forum) worked, so far. for me. A lot of work, but...

OK... I decided to restart from scratch. Completely, or as much as possible for me, eliminated 'all' StarDock apps from my system (firewall and anti-virus disabled throughout process) using the following method:

1. Uninstalled all available StarDock apps using Revo uninstaller in advanced mode.

2: Deleted all other references (C:/Programs/Stardock, C:/Documents and Settings/All Users/.., etc) except reg entries via std windows delete function. Note: I could not del IconPackager folder in Stardock folder due error message ref iprepair.dll

3:Cleaned system first using WindowWasher, then CCcleaner, McAfee QuickClean, OneCareLive clean, and Raxco PerfectDisk RX Suite.

4: Rebooted, disabled firewall & anti-virus, and verified del of all apps except as noted.

5: Rebooted again (again disabling firewall and anti-virus) and DL'd a fresh copy of Impulse. Link: http://www.impulsedriven.com/about.asp

6: Installed Impulse and rebooted as requested. On completion of reboot again disabled firewall & anti-virus.

Note: After opening Impulse and going to the Desktop tab after the above both WindowBlinds6 and the two (IP/IP4) versions of IconPackager showed as being 'installed'. Doing an 'uninstall' from Impulse corrected the problem with both WB6 and IP with each then showing as 'available' and only one version of IconPackager (IP4) being evident.

7: Installed individual apps via Impulse allowing each to fully complete installation before proceding to the next beginning with, for no good reason, WB6. Also, verified install of each to confirm a successful install. Note: I only had one problem (ObjectDesktop - NIC) which was corrected by un/reinstalling and re-verifying.

At this point I still show no DesktopGadgets as being available. There remain two IP versions (IP & IP4) being shown (same version with 'Latest Update' date varying by one day and .1MB) as installed. And the three versions of SkinStudio (which has been addressed) are in evidence, but only one (SS6 Pro) shows as installed.

The problem with changing individual icons still remained. I was, however, successful (at least temporarily) in enabling this by copying the 'activate.exe' file from the C:/Program Files/Stardock/Object Desktop/IconPackager folder into the C:/Documents and Settings/All Users/Application Data/Stardock/IconPackager folder. On the first attempt to change an individual icon IconPackager asked to reenter my registration info and then proceeded to process the change as it should.

Haven't gotten an farther so far in testing other apps but, so far, all appear to be in order.

My current experience is also telling me that IconPackager is broken, and Stardock should really collect all the data from the users, this to solve as much problems as possible. It has been a while since IconPackager received a large update, and it is due time.

Birger

it's been a while since IP has seen a large update? where have you been hiding? alomst every update for IP within the last 6 months have been HUGE updates!

And what do you consider HUGE? If I were hiding, I would have heard of a HUGE update. But no...

Birger

getting back to different icons for individual drives........it used to be that a flyout menu for My Computer on ObjectDock would use these different icons. now, a generic icon is used for each hdd. is it possible to get that feature back? it may be that this is an OD issue and not IP issue, tho. i won't post in both forums. it think that is rude, to be honest.

@hallv5, yes when you activate the shell extension (as you described) it will stay activated... ..until you activate IP or IPE (one or both of those will demand activation).

As someone described it.. It's the battle of activations..

My support issue regarding this has a 2 month anniversary in a few days.
They have tried, but so far everything has failed.

IP 4 still won't recolor packages. Past versions would recolor certain packages.
There is also the same issue I mentioned before , of some packages not loading or applying, even after delete and reinstall of package.
I have totally uninstalled IP4 and reinstalled after cleanup and regcleanup, and still having same problems. I hope the problem gets fixed soon, I try to recolor to show the many functions available in stardock products when I write my articles but it's impossible to show the functionality of something that isn't working right.

As I understand it there are two 'activation' errors currently existing with IP/IP4. One relates to the program itself either failing to activate or requesting re-activation after installation. And one that relates to an error when attempting to change individual icons for file types rather than installing complete icon sets.

I wasn't referring to the general 'activation' problem/s that occur when an attempt to run IP/IP4 is made. In the instance you're referring to I was describing the recurrence of the 'can't find..activate.exe' key error when an attempt is made to change an individual icon via the 'change icon' function under the properties tab of an individual file type.

After the 'clean start' process I described was completed I was able to enter IP4 with no problem. When I got the 'can't find..activate.exe' error on attempting to change an individual file type icon copying the 'activate.exe' file from C:\Program Files\Stardock\Object Desktop\Icon Packager to C:\Documents and Settings\All Users\Application Data\Stardock\IconPackager allowed me to change the individual file type icon.

Subsequently (meaning 'just now) I experienced a "new" variant on the problem where (under the above circumstance - having copied the 'activate.exe' file to the appropriate directory) IP4 was asking for activation info (email/sn) when the "apply' of the 'change icon' tab is selected. After entering the requested info for IP4 the change on the individual icon for the file type was processed and the icon was changed.

It's a bit sloppy, but it does work if you want/need to change the display icon for certain file types not covered in an icon set.

So, it's been a tab bit over 2 months now since the release of IP4. Can we get an update of where things stand on a fix?

Tnx...

I, too, would appreciate a quick update. Even if it's only to say, "Testing is taking longer than we thought", or "Market forces are driving us to put developer resources into other, more competitive areas right now".

Thanks,
-Jeff

I wouldn't mind an update myself..
Thanks

Ditto