Still having the same problem. ODZip.dll error for a lot of objects and widgets.

no fix yet?

still holding off.. for now..

skyzyk: Try download this to your desktop (you will need to open this link within Internet Explorer) and run this file as administrator

http://sd.stardock.com/mike/apps/fixup_odzip.bat

Mike

No probs at all here! 

milksama, will that work on a Win 7 Home Premium 64 bit system?

It says it only works on x86 systems.  What does that mean?

I have Win7 64 on AMD Phenom Quad core.

Hey Mike-  Tried your batch file, I'm on XPHomeSP3 here.  Sorry but it didn't do the trick.  When it was adding the registry entry it prompted me that the entry already existed, I let it overwrite.  When it downloaded the dll, I went to the common file directory where the batch prompt indicated, the file was already there, I let it overwrite.  Rebooted, still getting the ODZip.dll error.

I get the error when I try to load DTX in client mode (and client mode won't load) but not when I try to load it in builder mode (and builder mode loads).  Also get it when I try to run (double click) any widget I've tried and the widget won't run. (I just now made a widget that was nothing but a single layer object, got the error.)  I don't get the error when I double click on an object (.dxpack) or a desktop (.dxtheme) to load it, even if I'm running in client mode, and those load.  Also don't get the error when I'm in builder mode and import a widget, and the widget runs.

Thanks for trying of course.

I'm wondering how Redneck got rid of it?

More here

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.

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

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

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

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.

Never mind i think i found what you were talking about

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.

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. 

BUMP of the day.

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!

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.

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

Nov. 16th

Nov.19th

I take it the honeymoon is over then?

lol i think i will wait for fix

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