Anyone else having problems with WB 3.3a?
Saturday, April 6, 2002 by Dangeruss | Discussion: WinCustomize Talk
Blah! I've installed 3.3a and I keep getting errors while trying to run WB config or choose skins from the Appearances dialog. Fails to run .dll as an app or somesuch. I'm also getting "The instruction at "0x77f53d1d" referenced memory at "0x69726fa0". The memory could not be "read" Click OK to terminate the program." Upon program exit.
I'd love to go back to RC 3.2 but it claims it's a time limited GUI 'lympics version.
Also after uninstalling WB the Windows classic titlebar and scrollbar sizes are all fuxored up.
I'm running a Visual Style instead.
I'd love to go back to RC 3.2 but it claims it's a time limited GUI 'lympics version.
Also after uninstalling WB the Windows classic titlebar and scrollbar sizes are all fuxored up.
I'm running a Visual Style instead.
Neil Banfield
Reply #2 Saturday, April 6, 2002 3:30 PM
Reply #2 Saturday, April 6, 2002 3:30 PM
It sounds like a corrupt skin is in your WB dir and thats what is causing the crashes.
I would also suggest uninstalling WB, deleting all files in your WB dir (in case any are left over) and perhaps removing all WBD files (in the skin dirs)
Then reinstall 3.3 and it should all be happy again.
I would also suggest uninstalling WB, deleting all files in your WB dir (in case any are left over) and perhaps removing all WBD files (in the skin dirs)
Then reinstall 3.3 and it should all be happy again.
Frogboy
Reply #3 Saturday, April 6, 2002 4:20 PM
Reply #3 Saturday, April 6, 2002 4:20 PM
Sounds like something got hosed on the install. I haven't seen any reports of this. You might want to just try reinstalling it.
You using the stand alone or ODNT?
You using the stand alone or ODNT?
Dangeruss
Reply #4 Saturday, April 6, 2002 5:31 PM
Reply #4 Saturday, April 6, 2002 5:31 PM
OK - that was it, a corrupt skin. I deleted the offending skin and reinstalled WB 3.3a and it's working fine now. Odd. I installed the 3.3a update over the previous install without uninstalling this time. I still had to reset the scrollbars and titlebars back to normal sizes. Thanks guys.
Jafo
Reply #6 Saturday, April 6, 2002 6:10 PM
Reply #6 Saturday, April 6, 2002 6:10 PM
Hi, Russ....how's the synchronized crashing [MTB riding] going?....
Frogboy
Reply #7 Saturday, April 6, 2002 6:50 PM
Reply #7 Saturday, April 6, 2002 6:50 PM
I can't wait for the new Component Manager to arrive.
Here's a screenshot of it on Drengin (https://www.stardock.com/temp/drengincm.jpg)
It has a lot of advantages:
1) It only updates what you need updated instead of downloading the whole thing.
2) It'll have a much more intuitive interface (it won't look like that screenshot, we're still working on that, it's just that we can include a lot more documentation integration into CM itself with the new one).
3) We can have private betas and alphas
Here's a screenshot of it on Drengin (https://www.stardock.com/temp/drengincm.jpg)
It has a lot of advantages:
1) It only updates what you need updated instead of downloading the whole thing.
2) It'll have a much more intuitive interface (it won't look like that screenshot, we're still working on that, it's just that we can include a lot more documentation integration into CM itself with the new one).
3) We can have private betas and alphas
LoidiBoid
Reply #8 Saturday, April 6, 2002 11:26 PM
Reply #8 Saturday, April 6, 2002 11:26 PM
Dangeruss, you mentioned that you'd deleted the corrupted skin, but didn't say which one it was. (I too had the problem with scrollbars/title bar etc.) Perhaps you could share this discovery just in case. 
Jafo
Reply #9 Sunday, April 7, 2002 3:16 AM
Reply #9 Sunday, April 7, 2002 3:16 AM
Yes...if this is a case of a corrupted skin in a database somewhere, it'd pay to know which and have it removed, or repaired.
Or is it just a bunged-up download?...
Or is it just a bunged-up download?...
grayhaze
Reply #10 Sunday, April 7, 2002 7:39 AM
Reply #10 Sunday, April 7, 2002 7:39 AM
Is anyone getting an 'End Program' dialog for WB when they shut down XP? This seems to be the first version I've been getting this.
Leslie Hoffman
Reply #11 Sunday, April 7, 2002 8:30 AM
Reply #11 Sunday, April 7, 2002 8:30 AM
Many problems, wb won't do anything it use to. Reinstalling it didn't work
Dangeruss
Reply #12 Sunday, April 7, 2002 4:24 PM
Reply #12 Sunday, April 7, 2002 4:24 PM
Loidboid, it was a skin in development that another skinner had shared with me. It shouldn't be out in the wild wreaking havoc.
JAFO, The MTB riding has been infrequent at best, the weather here has been very rainy and the trails are soup. It's been raining every weekend here for about a month. Pffft!
JAFO, The MTB riding has been infrequent at best, the weather here has been very rainy and the trails are soup. It's been raining every weekend here for about a month. Pffft!
Jafo
Reply #13 Sunday, April 7, 2002 5:00 PM
Reply #13 Sunday, April 7, 2002 5:00 PM
Russ....it's been a bit the same here...I've spent more time building the bikes than riding them this past summer...
GreenReaper
Reply #14 Sunday, April 7, 2002 5:54 PM
Reply #14 Sunday, April 7, 2002 5:54 PM
The problem with things occuring on shutdown (and some photoshop stuff and toolbar blackness) should be fixed with 3.3c on ODNT now.
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 Saturday, April 6, 2002 1:59 PM
It sounds like the problem is with the control panel/display properties interface bit so maybe you'll have to manually delete the .cpl thingy in the Windows directory.
--visual styles? ugh