DesktopX 4 Beta Bug reports

Published on November 12, 2009 By ZubaZ In OS Customization

Another Desktopx 4 beta has been released. The standard and the professional version have both gotten the same updates This build focuses the feedback that has been recieved after the initial release last week.

Post anything that looks odd. Make sure to give us system information like your OS (including 32 or 64 bit), and if it's hard to explain (or even if it isn't) a screenshot.

Comments (Page 5)

WebGizmos

on Nov 17, 2009

but since Stardock added the DX parts to the right click menu, I get a locked up explorer when I right click

Yeah I noticed that...any particular reason for that? Never needed it before.

neophil78

on Nov 17, 2009

Though, finally is the DesktopX 4 bug corrected or not ? (for XP SP3 at least ...)

(BTW, on one PC, i haven't it yet DesktopX V 3.50 mentionned as updatable to a DesktopX 4 version

Murex

on Nov 17, 2009

RedneckDude

reply 60

Well, I may have spoken too soon. I dunno if it's connected, but since Stardock added the DX parts to the right click menu, I get a locked up explorer when I right click on a file. Pre DX4 it wasn't happening.

What DX parts are you talking about? If it's this it's always been there

sViz

on Nov 17, 2009

Probably mean this:

That DX option also shows up when you r-click in any explorer window. Though I'm not having any major problems, I don't think the option should be in the explorer r-click menus; it serves no purpose there.

Murex

on Nov 17, 2009

Never mind i think i found what you were talking about

RedneckDude

on Nov 17, 2009

sViz

reply 64

Probably mean this:

That DX option also shows up when you r-click in any explorer window. Though I'm not having any major problems, I don't think the option should be in the explorer r-click menus; it serves no purpose there.

Correct, the right click frozen explorer thing isn't happening on the rig that does not yet have desktopX on it, but it does happen on both 7 and Vista on the rig that does have DesktopX installed.

Murex

on Nov 18, 2009

Using the right click option in explorer doesn't make explorer freeze up. However if I click on new object I get the window Desktopx has quit working. If I click on

configure Dsesktopx it will bring up the dx theme along with the window (ODZip.dll not found in the desktopx directory or in the Stardock common files directory.) Close out that window and the theme works.

Also a problem I am having is I can't change any graphics in any theme I have already made. When I do try to change out a graphic image I get Desktopx has quit working and shuts down.

When trying to load a theme I always get the ODZip.dll window but the theme does come up and works ok after I close the ODZip.dll window.

I am using Windows 7 (32 bit)

Jerry LeDoux

on Nov 18, 2009

I tried the fix and I'm still getting the same error when I start up. When I ran it, it indicated the registry entry was there and I let it overwrite it. I downloaded the .dll and let it overwrite the file that was already there. It accomplished nada. Something else must be going on. I've really got to stop installing these betas.

sViz

on Nov 18, 2009

BUMP of the day.

wtripp

on Nov 19, 2009

For the record, I'm getting the same error when I try most clock widgets. Not all, but many of them. I have put the file just about everywhere (odbzip.dll I mean). I've run the batch file and made the registry change. HELP!

DaveRI

on Nov 19, 2009

wtripp if you want to you can try using DTX builder mode to import a few widgets, best to do one at a time. Then export it as an object. Then delete it from your DTX desktop. Do another widget, etc. Then change back to DTX client mode. Then right click on the Builder mode icon in the system tray and exit DTX Buider mode, DTX Client will remain loaded. The objects should then load into client mode by double clicking on them. Don't know how many of them will work that way but I've done it with a few.

Occasionally a widget loaded as an object won't run right - I've seen a couple of them take over the DTX right-click menues, so keep an eye out for that. Also if any of the new objects happen to use the same name references between them and you try to load them at the same time you'll get a conflict error.

Or of course you can wait for the next build or go back to the previous one.

I've also noticed that I'm not getting the error when running gadgets, so that might be an option for you.

RedneckDude

on Nov 19, 2009

I've had to revert to 3.5 in order to do anything at all now.

Wizard1956

on Nov 19, 2009

Nov. 16th

RedneckDude

reply 55

No probs at all here!

Nov.19th

RedneckDude

reply 72

I've had to revert to 3.5 in order to do anything at all now.

I take it the honeymoon is over then?

skibadee

on Nov 20, 2009

Wizard1956

reply 73

Nov. 16th
Quoting RedneckDude, reply 55No probs at all here!

Nov.19th
Quoting RedneckDude, reply 72I've had to revert to 3.5 in order to do anything at all now.

I take it the honeymoon is over then?

lol i think i will wait for fix

DrJBHL

on Nov 20, 2009

I wish SD would remove the problematic Update from Impulse until a fixed one can be offered.

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.
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!