I have written a DirectShow filter (C++ 32bit) which I can install for XP32 and
Vista32 without problems with the regsvr32 command.
But if I want to install the filter on a 64 bit OS I have problems.
1. If I use the regsvr32 source from my own application I get always an exception
2. and if I use the regsvr32 command from the command line I get the message,
that the filter is well installed, but it isn't!!
Does anyone have a solution?
Regards
Marc
If you are installing the 32bit filter that will run under WOW64 then you
have to use the WOW64 version of regsvr32. Locate the regsvr32 that is in
the WOW64 folder and use that.
--
http://www.chrisnet.net/code.htm
[MS MVP for DirectShow / MediaFoundation]
I have done this, but it doesn't work properly.
The regsvr32 command says success, but the filter is not available in the registry.
Regards
Marc
Chris P. schrieb:
> I have done this, but it doesn't work properly.
> The regsvr32 command says success, but the filter is not available in the registry.
Are you checking the WOW64 sub-branch of the registry?
You want the filter to work for your 32-bit applications right?
yes I want the filters to work with my 32-bit application.
The problem is, that my application checks at startup if the filters are
installed. With the 32-bit OS, the filters are found with 64-bit OS not!
I don't know if they are really not installed, or if my application
is not able to find them.
I must ask the users of my application who are using 64-bit OS.
Is there a different way to find an installed filter under 64-bit OS
as under 32-bit OS?
Regards
Marc
Chris P. schrieb:
> yes I want the filters to work with my 32-bit application.
>
> The problem is, that my application checks at startup if the filters are
> installed. With the 32-bit OS, the filters are found with 64-bit OS not!
>
> I don't know if they are really not installed, or if my application
> is not able to find them.
>
> I must ask the users of my application who are using 64-bit OS.
>
> Is there a different way to find an installed filter under 64-bit OS
> as under 32-bit OS?
The methods for checking the installed presence of a filter are the same.
You can run the 32-bit version of GraphEdit and look at the list of
installed filters. You can also manually look for the CLSID in the
registry under the WOW64 branch.
To find my filters I search all filters which are listed in the
"DirectShow Filter" branch in GraphEdit.
Are my filters listed in a different branch under a 64-OS?
Is there a WOW64 branch and what is the CLSID?
Regards
Marc
Chris P. schrieb:
> To find my filters I search all filters which are listed in the
> "DirectShow Filter" branch in GraphEdit.
> Are my filters listed in a different branch under a 64-OS?
> Is there a WOW64 branch and what is the CLSID?
From a quick Google search the WoW keys are mirrors of the structure of the
normal registry under each main key under a node called Wow6432Node:
HKEY_*\Wow6432Node\
Example:
HKEY_CLASSES_ROOT\CLSID\{083863F1-70DE-11d0-BD40-00A0C911CE86}\Instance\
--
Please read this before replying:
1. Dshow & posting help: http://tmhare.mvps.org/help.htm
2. Trim & respond inline (please don't top post or snip everything)
3. Benefit others: follow up if you are helped or you found a solution
If you use graphedit is there (under 64-bit) the node "wow6432node" additional
to "DirectShow Filters" or a replacement of them?
Regards
Marc
The March Hare [MVP] schrieb:
> If you use graphedit is there (under 64-bit) the node "wow6432node" additional
> to "DirectShow Filters" or a replacement of them?
Are you running the 32-bit version of graphedit? That is the real test.
What kind of IDIOTS would write an operating system in which the 64-bit
version of "regsvr32" is called "regsvr32"? Did the concept of "regsvr64"
really never come up in those weekly brainstorming sessions?
I think Microsoft has badly screwed up this 32-to-64-bit transition, and
made our jobs 10 times more difficult than in the relatively smooth
16-to-32-bit transition.
--
Tim Roberts, ti...@probo.com
Providenza & Boekelheide, Inc.
> What kind of IDIOTS would write an operating system in which the 64-bit
> version of "regsvr32" is called "regsvr32"? Did the concept of "regsvr64"
> really never come up in those weekly brainstorming sessions?
Which is why I wrote a regsvr64.bat file to replace what should've been.