Explorer.exe crashes with latest beta's of Iconpackager
Wednesday, November 23, 2005 by Blue_Steel | Discussion: Bug Reports
Hi,
after spending almost a week re-installing windows XP pro I finally found out (tracked down) what was causing the crashes in explorer.exe
when i install the latest beta's of Icon packager it locks explorer.exe on bootup ...
I've confirmed this by uninstalling Iconpackager ane everything comes back fine ... i re-install it and it locks up explorer.exe yet again.. i un-install it again and everything returns back to normal
my summise is that its replacing cache.dll with the cache64.dll not sure though.. but something is definatly scewif
My system Spechs are
(a 32 bit OS.. not 64)
AMD Athlon 2400+
Win XP Pro (sp2 ) with all te updates / patches from the microsoft update service
ati radeon 9600
1gb ram
after spending almost a week re-installing windows XP pro I finally found out (tracked down) what was causing the crashes in explorer.exe
when i install the latest beta's of Icon packager it locks explorer.exe on bootup ...
I've confirmed this by uninstalling Iconpackager ane everything comes back fine ... i re-install it and it locks up explorer.exe yet again.. i un-install it again and everything returns back to normal
my summise is that its replacing cache.dll with the cache64.dll not sure though.. but something is definatly scewif
My system Spechs are
(a 32 bit OS.. not 64)
AMD Athlon 2400+
Win XP Pro (sp2 ) with all te updates / patches from the microsoft update service
ati radeon 9600
1gb ram
Woodbridge
Reply #2 Thursday, November 24, 2005 7:27 AM
Reply #2 Thursday, November 24, 2005 7:27 AM
I had the same trouble with my PC at work. Explorer would lockup after the reboot.
I didn't have to reinstall XP, just Iconpackager. If this happens to you...
CTRL+Shift+ESC
File->New Task
Find and load Iconpackager
Reset to Classic
Back to the TaskManager
File-> New Task
Find and load Stardock Centeral
Uninstall Iconpackager
Reboot
Clean out the Iconpackager folder and reinstall.
If it helps my system specs are
Dual Xeon 3Ghz
XP SP2
NVIDIA Quadro FX 1000 (IBM drivers 44.03)
2Gb PC3200 RAM
I didn't have to reinstall XP, just Iconpackager. If this happens to you...
CTRL+Shift+ESC
File->New Task
Find and load Iconpackager
Reset to Classic
Back to the TaskManager
File-> New Task
Find and load Stardock Centeral
Uninstall Iconpackager
Reboot
Clean out the Iconpackager folder and reinstall.
If it helps my system specs are
Dual Xeon 3Ghz
XP SP2
NVIDIA Quadro FX 1000 (IBM drivers 44.03)
2Gb PC3200 RAM
Blue_Steel
Reply #3 Thursday, November 24, 2005 7:49 AM
Reply #3 Thursday, November 24, 2005 7:49 AM
I know how to do it now... the prob was that i didn't know what was causing it... This message was a bug report for the devs... I may have posted it wrong
the thing is that I didn't even run iconpackager .. i just installed it.. earlier releases didn't do this... just the latest 2 beta tests from what i worked out when i installed them
the thing is that I didn't even run iconpackager .. i just installed it.. earlier releases didn't do this... just the latest 2 beta tests from what i worked out when i installed them
Blue_Steel
Reply #4 Thursday, November 24, 2005 1:26 PM
Reply #4 Thursday, November 24, 2005 1:26 PM
Bagginz has repaired the problem and should appear in the next beta release of Icon Packager
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Reply #1 Wednesday, November 23, 2005 9:17 PM
Hey J.T.
I have to agree. I loaded the iconpackager beta, and couldn't keep my explorer running for longer than a couple of minutes at a time. It kept restarting. I unloaded iconpackager after reading your post and haven't had a problem. Thanks. I figured it was some object desktop, but didn't know which component.