[fixed] deploy tool crashes on mpaudioswitcher.ax (1 Viewer)

[mm1352000]

It turns out that I didn't even have the filter installed at the moment. Anyhow I was able to register, unregister and re-register the one that is currently committed to SVN with no problem...

I've got .NET versions 1.1, 2.0, 3.0, 3.5 and 4.0 installed. Not sure about VC++ redistributables - how would I find that out?

 

[tourettes]

Yes, all MpAudioSwitcher.ax files are expected to be the same size.

I'm also on XP, but I just upgrade my DLLs, EXEs etc. when I feel that things are pretty stable (so I didn't use the installer to get 1.2.0b). I'll try and unregister and reregister the latest one when I get home. I don't think I actually use it though - what is it for?

Size could be different when building with VS2010 or VS2008. If I remember correctly some stuff (mfc?) is now staticly linked with VS2010 if used.

 

[elliottmc]

Yes, all MpAudioSwitcher.ax files are expected to be the same size.

I'm also on XP, but I just upgrade my DLLs, EXEs etc. when I feel that things are pretty stable (so I didn't use the installer to get 1.2.0b). I'll try and unregister and reregister the latest one when I get home. I don't think I actually use it though - what is it for?

Size could be different when building with VS2010 or VS2008. If I remember correctly some stuff (mfc?) is now staticly linked with VS2010 if used.

Could it be that the people having problems do not have VS2010 runtime installed? Obviously I am not as knowledgeable as most of you guys, but it seems better to understand why this is failing than to substitute a different file which registers but may not be the best for everyone else.

Mark

 

[tourettes]

Could it be that the people having problems do not have VS2010 runtime installed? Obviously I am not as knowledgeable as most of you guys, but it seems better to understand why this is failing than to substitute a different file which registers but may not be the best for everyone else.

It shouldn't cause a crash but instead say something like "side-by-side configuration is invalid". Of course there could be a bug in MS side (I doubt) that causes the crash when VS2010 redist is missing.

 

[elliottmc]

I have completed the following additional tests:

1. Removed VC++ 2008 KB2467174 from bad PC - rebooted - no change, I still get the access violation trying to register.
2. Installed VC++ 2005 to bad PC (to mirror good PC) - rebooted - no change, I still get the access violation trying to register.

Hi,

What about removing ALL VC++ 2005 and 2008 from the problem PC, so you just have VC++ 2010 runtime?

Mark

 

[mm1352000]

According to my add/remove programs list I have the following redistributables installed:

C++ 2005 (versions 8.0.50727.4053 [ATL], 8.0.56336 and 8.0.59193)
C++ 2008 (versions 9.0.2102, 9.0.30729.17, 9.0.30729.4148, 9.0.30729.4148 [ATL], 9.0.30729.4974)
C++ 2010 (version 10.0.30319)
J# 2.0

Runtimes:

C++ 2010 (version 10.0.30319)
F# 2.0

More detail about my frameworks:

Compact 2.0 SP2
Compact 3.5
1.1
2.0 SP2
3.0 SP2
3.5 SP1
4 Client
4 Extended
4 Multi targeting

I have both VS 2010 and VS 2008 installed...

 

[elliottmc]

Hi,

Just an observation. We only seem to have 5 users with this problem. I would like to assume that if someone had taken the trouble to download the beta, and they had this problem, then they would report it. So, it does seem pretty isolated.

Even with those users, some of them have other XP systems that work fine.

Could registering this filter depend on audio hardware? That could be a common factor to look out for.

Alternatively, is one of the five prepared to reinstall windows XP, update everything and then try to install? If this is a problem with the users' OS, then we should definitely try to understand it and help, but not in a way that fixes the problem for a very few at the expense of 99.9% of the users. Especially not if the truth is 'something wrong with your system, reinstall windows'.

Mark

 

[tourettes]

Just an observation. We only seem to have 5 users with this problem. I would like to assume that if someone had taken the trouble to download the beta, and they had this problem, then they would report it. So, it does seem pretty isolated.

Too isolated indeed to be some common issue - could be a broken system (some virus or other application has modified / patched the redist DLLs).

Could registering this filter depend on audio hardware? That could be a common factor to look out for.

No, registration is not poking any devices - actually it has quite minimal amount of code. Only way to be sure what goes wrong is to have a broken system that someone can debug with the VS installed.

Alternatively, is one of the five prepared to reinstall windows XP, update everything and then try to install? If this is a problem with the users' OS, then we should definitely try to understand it and help, but not in a way that fixes the problem for a very few at the expense of 99.9% of the users. Especially not if the truth is 'something wrong with your system, reinstall windows'.

One thing that could be affecting is some locale setting.

 

[Vasilich]

well, i am not a specialist in MPAudiorenderer, but after short analzye i discovered, than posr50 V3 has dependencies ONLY on DLLs coming with every OS, and V2 has dependencies also on MSVCR100.dll and MFC100u.dll. So we need to make sure that people having problems with v2 have vs2010 redist installed

 

[elliottmc]

According to my add/remove programs list I have the following redistributables installed:

C++ 2005 (versions 8.0.50727.4053 [ATL], 8.0.56336 and 8.0.59193)
C++ 2008 (versions 9.0.2102, 9.0.30729.17, 9.0.30729.4148, 9.0.30729.4148 [ATL], 9.0.30729.4974)
C++ 2010 (version 10.0.30319)
J# 2.0

Runtimes:

C++ 2010 (version 10.0.30319)
F# 2.0

This is on Windows XP, right?

You don't list VC++ 2008 KB2467174.

It seems that others are having problems with this update.

Security Update KB2467174 kills Windows 2000 compatibility of mfc90.dll

and because it is a microsoft security update, is it certain that uninstalling it will actually remove it ?

Can anyone with Windows XP installed and with this particular fix confirm that the 1.2.0beta installer is working for them?

Mark