Anyone else having problems with WB 3.3a?

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.

8,614 views 15 replies
Reply #1 Top
I'm running 3.3a on a win2k and an XP box with no issues at all. Could be I'm just lucky but more likely something is goofed up in your installation Russ. Have you tried uninstalling WB and getting an earlier version, like 3.1 to work? If that one runs ok then try installing 3.3a on top of it.

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
Reply #2 Top
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.
Reply #3 Top
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?
Reply #4 Top
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.
Reply #5 Top
Oh and Brad, ODNT install using the latest CM.
Reply #6 Top
Hi, Russ....how's the synchronized crashing [MTB riding] going?....
Reply #7 Top
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

Reply #8 Top
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.
Reply #9 Top
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?...
Reply #10 Top
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.
Reply #12 Top
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!
Reply #13 Top
Russ....it's been a bit the same here...I've spent more time building the bikes than riding them this past summer...
Reply #14 Top
The problem with things occuring on shutdown (and some photoshop stuff and toolbar blackness) should be fixed with 3.3c on ODNT now.
Reply #15 Top
posted on a Sunday? wow - that's dedication...