INF RegisterDLLs issue

I have an INF problem I cannot explain.

I have an AVStream driver with a ksproxy plugin. The plugin is a COM DLL,
as they all are. I do the COM registration in the INF file, via

[MainSection]
...
RegisterDlls = xxx.Register
...
[xxx.Register]
11,,CompanyPlugin.ax,1
16425,,CompanyPlugin.ax,1

11 is System32, 16425 is SysWow64 on 64-bit systems and is irrelevant on
32-bit systems.

One client is now complaining that on the very first plugin in a fresh
installation Win 7, the 32-bit DLL is not registered. If they re-install
the driver, or if they plug in to another port so it gets a new install, or
if they run regsvr32, then it works fine, and it works fine from that point
on. It's only that very first installation. The 64-bit DLL is fine.

In setupapi.drv.dll, it shows both lines, but only the 64-bit DLL has a
second line saying that registration succeeded.

Is there some systemic issue with RegisterDLLs and 32-bit DLLs on a 64-bit
system? I'm convinced there are no missing dependencies, even on a fresh
install. Further, I'm not entirely sure how I'm going to chase thiis down.
--
Tim Roberts,
Providenza & Boekelheide, Inc.

Can you insert a breakpoint in the 32-bit dll registration code and debug
it?
--pa


"Tim Roberts" <> wrote in message
news:...
> I have an INF problem I cannot explain.
>
> I have an AVStream driver with a ksproxy plugin. The plugin is a COM DLL,
> as they all are. I do the COM registration in the INF file, via
>
> [MainSection]
> ...
> RegisterDlls = xxx.Register
> ...
> [xxx.Register]
> 11,,CompanyPlugin.ax,1
> 16425,,CompanyPlugin.ax,1
>
> 11 is System32, 16425 is SysWow64 on 64-bit systems and is irrelevant on
> 32-bit systems.
>
> One client is now complaining that on the very first plugin in a fresh
> installation Win 7, the 32-bit DLL is not registered. If they re-install
> the driver, or if they plug in to another port so it gets a new install,
> or
> if they run regsvr32, then it works fine, and it works fine from that
> point
> on. It's only that very first installation. The 64-bit DLL is fine.
>
> In setupapi.drv.dll, it shows both lines, but only the 64-bit DLL has a
> second line saying that registration succeeded.
>
> Is there some systemic issue with RegisterDLLs and 32-bit DLLs on a 64-bit
> system? I'm convinced there are no missing dependencies, even on a fresh
> install. Further, I'm not entirely sure how I'm going to chase thiis
> down.
> --
> Tim Roberts,
> Providenza & Boekelheide, Inc.