Bugzilla – Bug 12059
Unable to play .m4a files on Windows XP unless you install Microsoft Visual C run-time libraries
Last modified: 2012-02-27 17:18:54 UTC
This forums posting reports that .m4a files can only be played on Windows XP systems if they have a specific set of Microsoft run-time libraries installed: http://forums.slimdevices.com/showthread.php?t=61488&page=5
I don't know if there is anything we can do about this. We cannot really go installing the MSC runtime libraries ourselves and I don't think that it is acceptable to statically link (or even if it is possible). As mentioned in the thread, it will be pretty unusual for users to have a bare-bones Windows* installation without any Microsoft applications that install the required run-time support. Michael, what is the situation with WHS?
I tested all binaries we ship on a clean WHS install, and none failed.
This is a problem only when the Windows operating system CDs does not install the appropriate Visual C libraries. http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en Here are the ones that do and don't: Windows 2000 before SP3: Not OK Windows 2000 after SP3: OK Windows XP before SP2: Not OK Windows XP SP2 and after: OK Windows Vista: OK This can also happens if the user tweaks his XP configuration to remove these libraries. The Windows installer could possibly check and display an error message if these libraries are not installed.
Programs written in MS VisualC such as faad.exe need support libraries. As most user have some MS application already installed, the libraries are already present. The following page has a link for the MS libraries that will work on your system. Can you try it and see it if works. http://www.microsoft.com/downloads/d...displaylang=en There are license reasons why these files cannot be distributed with SC. -------------------------- Another solution is to have customers install Windows Media Player 11, which will also include all the VisualC libraries needed.
This is not just a faad.exe issue but this same issue will occur with any of the Bin directory tools which were built with MS Visual C - including socketwrapper. Re License issue - I think if a copy of MS Visual Studio C is bought by Slimdevices/Logitech then the file vcredist_x86.exe could be included in the SC installation script and run on installation.
> Re License issue - I think if a copy of MS Visual Studio C is bought by > Slimdevices/Logitech then the file vcredist_x86.exe could be included in > the SC installation script and run on installation. Adding 5MB or so for a library which in most cases will be installed already sounds like a lot of overhead. But we should at least add a check and display a warning if it's missing. For my reference: http://blogs.msdn.com/astebner/archive/2007/01/16/mailbag-how-to-detect-the-presence-of-the-vc-8-0-runtime-redistributable-package.aspx
Dan to write a FAQ and WIKI topic to cover this for any possible customers calling in with this issue
I'm going to try building a version of faad that works. If not, we should consider shipping the vcredist file, even if it's big.
OK, so I installed a vanilla XP SP2 VM, and without even updating to SP3, I can run all the exe's in 7.3.3. Am I missing something?
*** Bug 12496 has been marked as a duplicate of this bug. ***
Adding time worked info Nothing left to test, I just need to come up with the FAQ text to be posted. Low Priority as TS gets very few calls on this.
I'm going to fix this for 7.4 as the new perl modules depend on the same libraries. Marking duplicate of already targetted bug 14133. *** This bug has been marked as a duplicate of bug 14133 ***
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.