Vista or XP? They seem to be skinned in Vista.

XP service pack3 Greek version

I think i will wait untill all other troubles with IP4 will be solved to get a chance   

The update went up last night for version 4.00.165 that has the correction for the .exe file.

We have tested it and it looks like we squashed the bug well. Please let us know here or at support@stardock.com if you have further troubles with it at all. If you want you can uninstall, restart, reinstall, restart again before running if you would like to be ultra thorough. It never hurts but it is likely unnecessary.



Is there something I can help you with Opus?


Neo Phil - Sorry for the delay in a direct response and thank you for your patience as we beat our head into the wall fixing that last one quickly.

So to replicate the problem you are having are you going into Icon Packager and changing the color, then hitting apply? Are the settings not saved from there as in you restart and the icons are back to normal? Or are you changing the icons in Icon Developer and it isn't saving out?

If you are trying to save the file with the color change on IP4 that will not work. The color change is just a saved setting in IP.

As for the language that might just be the language pack actually incorrect with the translation. Check the lang file in the main directory and open the French file in a text editor to see if you see anything out of place.

christolia (and others): The issue with the non-customized optical (CD/DVD) drive icons on XP is a known problem. The developers are aware of this and a fix will be released in another update when it is ready.

Mike

Thank you miLKama and Seabass .
I wait for the fix

That's what i'm looking for as it existed with IP3
If it doesn't exist anymore, i think IP4 is a downgrade version (well maybe except for Vista users ...)


Though a specific color setting will be the same for all packages ??   
That's just ugly  ( 


The lang file is in C:\Program Files\Stardock\Object Desktop\IconPackager\lang, i've no language file in C:\Program Files\Stardock\Object Desktop\IconPackager   

As an aside, that is the same as in WB since 6.0.

Yep, perhaps, but we're not talking here about WB but about less features that is now in IP4 than in IP3 ...   

I'm still having the issues with activation with 4.0.165 and I thought I'd give you a small update.

IP and IPE overwrites eachothers activation, and the shell extension seems to belong to
the IPE part of this, the reason of this assumption is below.

I had the IconPackage program perfectly activated, i.e it worked without asking for activation (as long as I don't run IPE).
Using the 'Icon' tab to change a icon showed a "can't execute 'C:\Documents and Settings\All Users\Application Data\Stardock\IconPackager\activate.exe" dialog.

I then copied activate.* from IP's folder to that location, then tried to change the icon again, viola, activation screen. After activating it, IP was invalidated again.

I'm in contact with support regarding this, but so far no solution has been found.

Same before and after update:DVD drive E icon appears when the window first opens,then it defaults back instantly.Minor,imo.Recoloring a package creates a subfolder in public documents/stardock/icon packager/packagename/colored.The one I tested with was 20mb in size.So I now have 40mb of space occupied by this package.Same for all that I've recolored,except a couple that also have a back-up file!How do I temporarily change the colors without creating a duplicate file? Or do I just have to delete it manually? I have a small HDD (since birth) and need to conserve space. 32bit Vista,btw.Updated through Impulse,restarted,ran IP. Thanks in advance.

As far as i also exprimented, i just think we can't

So I downloaded ... No Probs at all guys .... Good work !

Heard back from Support!   

As Mike already mentioned, the devs are aware of optical drive not being skinned.

Still no word on the 'can't find ... activate.exe', but I asked Mike in my reply if that and the optical drive problem were related and if the update released today was intended to fix that activation issue or the not activating on install issue.

More when I hear back!

@ pictoratus,

The update did *not* fix either of those issues for me.

-Jeff