Re: Access Violation in WMVCORE.DLL ver. 10.0.0.3646
From: Tobia Quantrill (xeres_at_eat.me)
Date: Tue, 14 Dec 2004 10:07:21 +0100
"Geoff Dunbar [MSFT]" <firstname.lastname@example.org> wrote in message
> WMVCORE.dll should be backwards compatible with old versions. Without more
> information it's really tough to speculate what might be going wrong.
WMVCORE.DLL sould be backwards comaptible, but unfortanetly it's not. I
didn't have much time to see what is going on here, but I can tell you for
shore that something is wrong with that dll. After installing version 10, I
did something for testing only. I removed new WMVCORE.DLL (10.0.0.3646) and
put version 220.127.116.1180. Our application worked fine again.
I'll try to provide more information about this...
> This posting is provided "AS IS" with no warranties, and confers no
> "Tobia Quantrill" <email@example.com> wrote in message
> > A year ago I wrote some application for capturing. It creates *.WMV
> > Everything worked fine until WMP 10 came up. Now, when I start my app,
> > Access Violation in WMVCORE.DLL message box pops up. I'm not able to
> > why or where in my code it happens. All HRESULT return values are S_OK.
> > I use version of WMVCORE.DLL, everything is okay, but with
> > version 10.0.0.3646 I can't make it work. We use video device based on
> > architecture for capturing. The platform is Windows XP Professional. Can
> > someone please help?!!
> > Does this mean, I'll have to change my source code every time when MS
> > releases new version of WMVCORE.DLL ?????