3.00b.002? 3.00b.093? Where? What?

IP

from JoeUser Forums
IP replaces the icons on my .exe files (& consequently all their shortcuts) with the generic icon from the icon pkg I loaded.

I'm running IP 3.00b.002 which includes the dreaded iprepair.dll. In reading through recent posts, it's hard to say whether there's a workaround using IP 3.00b.002. There seems to be agreememt that IP 3.00b.093 works, but I can't find a way to get to it. StarDock Central (SC) reloads IP 3.00b.002. Going through the StarDock site, either I get sent to download.com for the free version or I get directed to reload SC.

I did try uninstalling IP 3.00b.002, followed by rebooting, then unregistering & deleting iprepair.dll, followed by rebooting. I was hoping that SC would load 3.00b.093, even though it said 3.00b.002-- no such luck.

Questions:
1) How can we get 3.00b.093?
2) If 3.00b.093 has been working since July 27, why is it not available on SC? Why all the crazy workarounds on the last 2-4 IP forum posts?
3) If 3.00b.093 doesn't work, is there a workaround *from the developer* that makes 3.00b.002 function correctly?
Thanks - not mad-- just want it to work
iconpackager
5,261 views 8 replies
Reply #1 from Stardock Forums Top
I agree with you, I suppose you know the quickie work-around for the IPrepair.dll issue is ? I simply renamed it ... everything is ok... But still hunting for the next update. I guess they (the devolopers) are also working on the issue.
Reply #2 from WinCustomize Forums Top
is there a workaround


See comment #10 Link

disabling it worked for me
WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #3 from WinCustomize Forums Top
do you have SDC? updated to 3.00b.093 with it.
Reply #4 from WinCustomize Forums Top
Tonight when I did the uninstall IP 3.00b.002, followed by rebooting, then unregistering & deleting iprepair.dll, followed by rebooting-- then reinstalling,
the uninstalling & reinstalling parts were done with SC. I got 3.00b.002 again.

I'm going to try #1 above & if it doesn't work I'll try #2. Then I'll go to sleep & maybe tomorrow SC will give me 3.00b.093
Reply #5 from WinCustomize Forums Top
You might try temporarily removing the BACKUP folder from the "\Program Files\Stardock\SDCentral" folder if it contains any IP archives to prevent reinstalling from the archive.

Not sure why it is not showing up for you, it is in my SDC version 2.10.343.
Reply #6 from WinCustomize Forums Top
Whoa! Fixed!

iprepair.dll --> XXXiprepair.dll -->



Thanks, folks!
Reply #7 from WinCustomize Forums Top
Thanks Corky-- I'll check it in the mornin' & post the answer
Reply #8 from WinCustomize Forums Top
OK... My archives are on a different partition from OD, but I checked in case there was a loose IP archive I accidentally saved elsewhere...Not. Then I temporarily renamed the IP backup in my StarDock archive so StarDock Central (SC) wouldn't use it if I reinstalled IP. Also I checked the cache for IP files, but there was no IP folder present. Next I did the uninstall, reboot, reinstall reboot.

SC (v 2.10.343 build 95) still showed that it was installing IP 3.00b.002 (not .093) & .002 was installed. IP 3.00b.002 continues to work fine as long as iprepair.dll is disabled.

I have no idea why SC doesn't seem to see IP 3.00b.093. It has updated several other components of OD since 25-Jul (the date for IP 3.00b.002). Ex, this morning it updated Theme Manager to v 2.22.034.

I dunno. ...shrugs...