Getting all kinds of errors.....multiple programs.
Wednesday, May 30, 2007 by Morpheous416 | Discussion: OS Customization
Ok....
CursorXP, crashing when trying to use the cursor pack - Oxide. Can't use it if it's installed with the Theme Manager either.
IconPackager 3.2, getting more and more of the SDCZip.dll "can't find" errors. Having to install the themes manually by creating their perspective folders under Stardock directory.
LogonXP, getting "can't read ????.logonxp file", then proceeds to launch the Windows Installer for Quickbooks?? After installer is cancelled, LogonXP opens.
Only previous changes, updates to IP and WB, 3.2 and 5.5 respectively.
CursorXP, crashing when trying to use the cursor pack - Oxide. Can't use it if it's installed with the Theme Manager either.
IconPackager 3.2, getting more and more of the SDCZip.dll "can't find" errors. Having to install the themes manually by creating their perspective folders under Stardock directory.
LogonXP, getting "can't read ????.logonxp file", then proceeds to launch the Windows Installer for Quickbooks?? After installer is cancelled, LogonXP opens.
Only previous changes, updates to IP and WB, 3.2 and 5.5 respectively.
Morpheous416
Reply #2 Thursday, May 31, 2007 1:29 PM
Reply #2 Thursday, May 31, 2007 1:29 PM
Thanks for the reply, Secret.
SDCZip.dll issue fixed from reply 16 of that thread...appreciate you linking to it.
I have no clue as to why QB's installer launched. But, after following up on several of it's error code issues, turns out MS's newest MSI patch release hosed all the information from the Window's 3.1 installer. I have yet to test out LogonXP again, but it didn't come from opening the program and adding the logon screen, it came from double clicking the logonxp file. Which, supposedly..is supposed to kick in the programs to add the themes.
I'll do some more testing on it....see what more information I can provide to any one else reading this thread.
SDCZip.dll issue fixed from reply 16 of that thread...appreciate you linking to it.
I have no clue as to why QB's installer launched. But, after following up on several of it's error code issues, turns out MS's newest MSI patch release hosed all the information from the Window's 3.1 installer. I have yet to test out LogonXP again, but it didn't come from opening the program and adding the logon screen, it came from double clicking the logonxp file. Which, supposedly..is supposed to kick in the programs to add the themes.
I'll do some more testing on it....see what more information I can provide to any one else reading this thread.
MySecret
Reply #3 Thursday, May 31, 2007 6:11 PM
Reply #3 Thursday, May 31, 2007 6:11 PM
Glad that link helped 
Isn't it wonderful how their fixes can cause so many other problems
This is the reason that I refuse to simply install all of their updates...I now install critical updates only after reading the details. 
Of course that doesn't mean they will not cause issues but it makes isolating them easier 
Thanks for all the feedback
It's My Secret
turns out MS's newest MSI patch release hosed all the information from the Window's 3.1 installer
Isn't it wonderful how their fixes can cause so many other problems
This is the reason that I refuse to simply install all of their updates...I now install critical updates only after reading the details. 
Of course that doesn't mean they will not cause issues but it makes isolating them easier 
Thanks for all the feedback
It's My Secret
Morpheous416
Reply #4 Saturday, June 2, 2007 1:45 PM
Reply #4 Saturday, June 2, 2007 1:45 PM
Unfortunately, the MSI update was to alleviate the problems with Windows update's service from using 100% of the CPU and yet doing nothing at the same time.
It fixed the update service!
It fixed the update service!
Moderateman
Reply #6 Saturday, June 2, 2007 3:28 PM
Reply #6 Saturday, June 2, 2007 3:28 PM
hey!, since you win customize folks always beat up on us for dare posting something that flows to your site, i feel it is my duty to point out that your crap is flowing to us poor unwashed plain joeusers and the brilliance of all your intelligence is confusing us poor uneducated folk. get out!
heh heh heh.
heh heh heh.
ArileenDesign
Reply #7 Saturday, June 2, 2007 4:10 PM
that's really intelligent your brilliant mind make me blind
Reply #7 Saturday, June 2, 2007 4:10 PM
hey!, since you win customize folks always beat up on us for dare posting something that flows to your site, i feel it is my duty to point out that your crap is flowing to us poor unwashed plain joeusers and the brilliance of all your intelligence is confusing us poor uneducated folk. get out!
heh heh heh.
heh heh heh.
that's really intelligent your brilliant mind make me blind
Moderateman
Reply #9 Saturday, June 2, 2007 4:47 PM
Reply #9 Saturday, June 2, 2007 4:47 PM
ok no humor folk, was me joking... sheeesh I should know better than to try and joke with my betters {ha!}
Nimbin
Reply #10 Saturday, June 2, 2007 7:44 PM
Reply #10 Saturday, June 2, 2007 7:44 PM
with the oxide cursor xp theme, i got the same error message when i tried to load it through the program, i got around that by just clicking the theme itself and having it load like that, and it works fine now, sdczip.dll sounds to me like stardock central, try downloading and installing that program then updating all your other stardock stuff through there, hopefully this will eliminate some of the errors, good luck
dragonmage
Reply #11 Sunday, June 3, 2007 2:56 AM
Reply #11 Sunday, June 3, 2007 2:56 AM
As far as the CursorXP issue I've never been able to use any of Tycus' cursors , they lock my system up. My CXP may be outdated though, I haven't checked. Try some of Tycus' other cursors and see if you get the same effect.
Bebi Bulma
Reply #12 Sunday, June 3, 2007 3:12 AM
As far as the CursorXP issue I've never been able to use any of Tycus' cursors , they lock my system up. My CXP may be outdated though, I haven't checked. Try some of Tycus' other cursors and see if you get the same effect.
This might help: No more cursorxp crashing!.
Reply #12 Sunday, June 3, 2007 3:12 AM
As far as the CursorXP issue I've never been able to use any of Tycus' cursors , they lock my system up. My CXP may be outdated though, I haven't checked. Try some of Tycus' other cursors and see if you get the same effect.
This might help: No more cursorxp crashing!.
Morpheous416
Reply #13 Monday, June 4, 2007 4:20 PM
Reply #13 Monday, June 4, 2007 4:20 PM
@ Yraq,
Did that a bit ago!! Thanks for adding the info though...appreciate it.
As far as the cursor themes go....re-editing the ini file worked.
Testing the last issue....with the idea of Cursor XP having issues.. I looked into the ini file for the logonxp theme I created. It too suffered from the same spacing issue between the scripting sections.
All issues solved!!
Thanks again everyone for the help.
Did that a bit ago!! Thanks for adding the info though...appreciate it.
As far as the cursor themes go....re-editing the ini file worked.
Testing the last issue....with the idea of Cursor XP having issues.. I looked into the ini file for the logonxp theme I created. It too suffered from the same spacing issue between the scripting sections.
All issues solved!!
Thanks again everyone for the help.
whatwhere
Reply #14 Monday, June 4, 2007 5:40 PM
Reply #14 Monday, June 4, 2007 5:40 PM
if you want a good registry cleaning tool that is free here is tweaknow standard...the standard version is free but the pro version you have to purchase, i use the standard version and it works real nice tweaknow registry cleaner
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 Thursday, May 31, 2007 3:51 AM
In the case of multiple errors with various programs I would uninstall each program, Through Stardock Central if that is how you installed them...reboot...use a registry cleaner. Then install again via Stardock Central.
To trouble shoot even more effectively it would be best to install 1 at a time, run them for a day or 2, customize, change skins ect, then install 1 more ect.
It's My Secret