OCX conflicts - I'm out of ideas...

from Stardock Forums

I have a rather large application that uses some of Stardocks files.  Specifically wbocx.ocx version: 4.6.2.3 description: WindowsBlinds : DirectSkin and wbhelp2.dll version: 1.5.0.0  Description: WindowsBlinds Helper DLL.  I have a plug-in (AttachmentViewer.ocx) for this application that is conflicting with the wbocx.ocx file and causing the application to crash with Access Violations:

The message is: An exception of type HS Exception was caught with a description of: 0xC0000005 - Access Violation.

I was able to determine that it was the wbocx.ocx file by removing it, the attachment viewer works fine but the application keeps trying to reinstall itself.  This started happening with the last upgrade of the application when it introduced the wbocx.ocx file into the application.  It wasn't used in previous versions.

I'd ask the maker of the attachment viewer but they are out of business.

I'm out of ideas and wanted to see if anyone had any suggestions.  There's no interface into WindowsBlinds so I can't make any configuration changes.

Thanks!

1,508 views 5 replies
Reply #1 from WinCustomize Forums Top

While contacting the large application vendor might be the best thing to do in that case, Stardock developpers might still want to know about it so that they can fix the issue (or try to add a workaround in case this is a bug in the attachment viewer code that get triggered by WB somehow).

You can contact support at [email protected]. You should also contact the application vendor and let them know there is a problem with their update. While Stardock might be able to fix the bug, they probably won't be able to give you an updated ocx - you will have to go through the application developper.

Reply #2 from WinCustomize Forums Top

Open the WindowBlinds Configuration screen and click on "System info" then click the "Copy text" button. Paste that info here.

DeskScapes - Bring your desktop background to life.
Reply #3 from WinCustomize Forums Top

Hankers: this seems to be a problem with a third party application using DirectSkin, so no WB screen or configuration UI

Reply #4 from Stardock Forums Top

Thanks Littleboy!  I have contacted the application creators and emailed Stardock's support so maybe they will have some ideas...

Reply #5 from Stardock Forums Top

Working with Doug right now, thanks guys!