Odd behavior of filters under Windows 7?

[RolandRX33]

Is the DShow filter registration process handled differently under
Vista and Windows 7? I found that WavDest, in particular, could not
be registered. Turns out that it's already present in
C:\Windows\System32, but it does not turn up in the customary
locations, or even in GraphEdt.

In the case of the 64 bit versions of both Vista and Windows 7, the
existing WavDest filter in the System32 folder seems to be locked, for
some reason. Not sure why that was done, but it seems odd.

I have seen some problems with Video filters as well, but they are
probably similar in origin.

I'm sure that this must be documented somewhere, but I have not
located any info yet. Any idea what's going on?

[RolandRX33]

On Thu, 24 Sep 2009 02:57:10 -0400, RolandRX33 <Rolan...@nospam.com>
wrote:

Not sure if the post above even got noticed, as the group seems
inundated with spam. If anyone notices this, and has any idea about
where the DShow audio/video programmers have gone, please send a
heads-up. Probably a website or Yahoo group or something.

[Tim Roberts]

This may be an installation problem. Is the WavDest filter a 32-bit DLL,
or a 64-bit DLL? In a complete violation of intuiton, \Windows\System32 is
exclusively reserved for 64-bit DLLs. All 32-bit DLLs need to be copied
into \Windows\SysWOW64. If you get a DLL in the wrong place, it cannot be
used.

Many older installation programs are ignorant of this.
--
Tim Roberts, ti...@probo.com
Providenza & Boekelheide, Inc.

[RolandRX33]

On Sat, 26 Sep 2009 12:19:29 -0700, Tim Roberts <ti...@probo.com>
wrote:

Ha! So the 32-bit DLLs go in the -64 folder and the 64-bit DLLs go in
-32. I wonder who thought that was a good idea. <g>

The other odd thing: Vista ships with WavDest in the System32 folder,
which could be a good thing. But unfortunately it does not appear in
the normal DShow filter category, and GraphEdt can't find it. So it's
apparently registered incorrectly, or something else is wrong. And the
file appears to be locked. Any idea about MS's intent there?

Thanks for the insight, Tim. Very helpful.

[Alessandro Angeli]

From: "RolandRX33"

> The other odd thing: Vista ships with WavDest in the
> System32 folder, which could be a good thing. But
> unfortunately it does not appear in the normal DShow
> filter category, and GraphEdt can't find it. So it's
> apparently registered incorrectly, or something else is
> wrong. And the file appears to be locked. Any idea about
> MS's intent there?

If GE or your app is a Win32 EXE, it can not load Win64
DLLs.

--
// Alessandro Angeli
// MVP :: DirectShow / MediaFoundation
// mvpnews at riseoftheants dot com
// http://www.riseoftheants.com/mmx/faq.htm

[RolandRX33]

On Sun, 27 Sep 2009 00:56:38 +0200, "Alessandro Angeli"
<nob...@nowhere.in.the.net> wrote:

>
>From: "RolandRX33"
>
>> The other odd thing: Vista ships with WavDest in the
>> System32 folder, which could be a good thing. But
>> unfortunately it does not appear in the normal DShow
>> filter category, and GraphEdt can't find it. So it's
>> apparently registered incorrectly, or something else is
>> wrong. And the file appears to be locked. Any idea about
>> MS's intent there?
>
>If GE or your app is a Win32 EXE, it can not load Win64
>DLLs.

That part makes sense now (re the 64 bit drivers in System32). MS
must have decided to ship with a 64-bit version of the Wavdest filter
(odd, since they never pre-installed the 32-bit one in previous OS's).
And apparently the version of GraphEdt that ships with the Vista SDK
is actually 32 bit, hence WavDest's no-show in the filter list.

WavDest does appear to be locked though, for some reason. Attempts to
rename the DLL failed.

Thanks for the replies.

[Alessandro Angeli]

From: "RolandRX33"

> WavDest does appear to be locked though, for some reason.
> Attempts to rename the DLL failed.

System files have been protected since Windows ME.