Go Back   Winamp & Shoutcast Forums > Winamp > Winamp Bug Reports

Reply
Thread Tools Search this Thread Display Modes
Old 23rd June 2013, 02:47   #1
tenbucks1
Junior Member
 
Join Date: Jun 2013
Posts: 1
msvcr90.dll not found causing Winamp not to start. XP only?

msvcr90.dll from the Microsoft Visual C++ 2008 Redistributable is included with Winamp. Well there is a bug when running under Windows XP SP3. Winamp is not using the one included under Winamp\Microsoft.VC90.CRT. Winamp will not start with the error "this application has failed to start because the application configuration is incorrect". This is on a clean install of both Winamp and Windows XP SP3.

If you install Microsoft Visual C++ 2008 Redistributable or just put these 2 files in the WinSxS folder Winamp will start and run normally.



Installing Visual C++ 2008 should not be a requirement as you have already included the file needed and it has always worked. Please make this one work.

Steps to reproduce:
  1. Install Winamp on a Windows XP that does not have the Microsoft Visual C++ 2008 Redistributable installed.
  2. Attempt to run Winamp. You will get a "this application has failed to start because the application configuration is incorrect" error.


Specs:
-Mobo: Gigabyte Technology Co., Ltd. H67MA-UD2H-B3 (Socket 1155)
-CPU: Intel Core i5 2300 @ 2.80GHz
-Ram: 4.00GB Dual-Channel DDR3 @ 532MHz
-Sound: Microsoft LifeChat LX-3000
-Videocard: ATI Radeon HD 5400
-Windows OS: Windows XP SP3
-DirectX version: 9.0c
-Winamp version: 5.6.4.3418
-Winamp installation type: Full or Lite

Thanks
Attached Files
File Type: log hijackthis.log (2.0 KB, 194 views)
File Type: txt DxDiag.txt (38.3 KB, 170 views)
File Type: txt Winamp_Info_Report_22.06.2013.txt (13.2 KB, 167 views)
tenbucks1 is offline   Reply With Quote
Old 24th June 2013, 15:01   #2
Batter Pudding
Major Dude
 
Batter Pudding's Avatar
 
Join Date: Jun 2008
Posts: 1,665
Grab the beta and check that. I know there was a change to the install for this feature on Win7 - may have sorted itself out for XP too.

(Don't be scared by the "beta" tag. It is near enough a release version)
Batter Pudding is offline   Reply With Quote
Old 24th June 2013, 15:13   #3
DrO
 
Join Date: Sep 2003
Posts: 27,873
he's already using the 5.64 release so the beta won't have any effect on this.

i'm not sure why this issue is being seen as there's no reason for it, but am checking it out to see if there is an issue from the update of the dll or something else going on that's not been accounted for.
DrO is offline   Reply With Quote
Old 24th June 2013, 15:37   #4
Batter Pudding
Major Dude
 
Batter Pudding's Avatar
 
Join Date: Jun 2008
Posts: 1,665
Quote:
Originally Posted by DrO View Post
he's already using the 5.64 release so the beta won't have any effect on this.

i'm not sure why this issue is being seen as there's no reason for it, but am checking it out to see if there is an issue from the update of the dll or something else going on that's not been accounted for.
Ah - shared installers. Should have twigged that.

I've gotta rebuild an XP laptop in the next couple of days - just shout if you want a test run on it while it is still "bare bones".
Batter Pudding is offline   Reply With Quote
Old 24th June 2013, 16:02   #5
DrO
 
Join Date: Sep 2003
Posts: 27,873
something like that, same code base, just a different build run with / without Cloud parts included in the final installers.

anyhoo, i've just gone through and renamed all instances of msvcr90.dll on my XP VM and am now able to replicate the issue. dunno why it's happening as to my knowledge how the manifests are setup is correct but will see from what i can find from having a look now.
DrO is offline   Reply With Quote
Old 24th June 2013, 16:12   #6
DrO
 
Join Date: Sep 2003
Posts: 27,873
ok, have found the issue and is down to the manifest inside of winamp.exe trying to reference v9.0.21022.8 instead of v9.0.30729.6161 as is now included with Winamp for 5.64/5.7.

will look to get that fixed, though in the mean while, using a resource editor (like resource hacker' will allow for the manifest to be edited to with the correct value to get Winamp running on that setup.
DrO is offline   Reply With Quote
Old 24th June 2013, 16:46   #7
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Phoenix, AZ
Posts: 4,661
Is this just related to XP? On my Win 7 64-bit OS, the 9.0.30729.6161 version of that dll was being used by Winamp (instead of the version in the sub-folder) even before it was updated in the installer. I guess the newer version came from some other app I'm using.

Winamp Pro v5.666.3516 fully-patched - Komodo X Touchscreen v1.0 by Victhor skin
Windows 10 Home 64-bit v1809 desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 24th June 2013, 17:15   #8
DrO
 
Join Date: Sep 2003
Posts: 27,873
so it's due to an issue within the build tools we're using as part of VS2008 SP1 where it puts 9.0.21022.8 in the manifest as the version for msvcr90.dll irrespective of what is found during the build process (as per here and here).


the issue isn't limited to XP and just relates to the recent 5.64 / 5.7 builds only if the 9.0.21022.8 version of msvcr90.dll is not already present in the WinSxS location (or appropriate place on other OSes).


so the solution is going to be changing the version used in the dll and our manifests (before going through the VS2008 tool) to reference 9.0.21022.8 even though we're actually using 9.0.30729.6161. then that will get it working as expected when the redistributeables are not present on the rest of the machine and still allows the OS to find the appropriate version to use as needed (as i think is what you're seeing Aminifu - side-by-side dll dependencies are loads of fun *joy* ).

[edit]
or maybe not. looks like we'll have to go with the patching of winamp.exe option as just changing everything to reference 9.0.21022.8 instead of 9.0.30729.6161 didn't work.
DrO is offline   Reply With Quote
Old 24th June 2013, 18:48   #9
DrO
 
Join Date: Sep 2003
Posts: 27,873
so i've a solution for the build system after trying out a few things which supposedly should work but didn't *grumble*

what is meant to happen is the OS's version of the dll will be used and if the version requested cannot be found then our version in the Winamp\Microsoft.VC90.CRT will be used (at least that's how i understand things are meant to be working and from what i'm seeing when testing).


so the fix until we provide an updated build (which has it in) will be to edit the manifest.xml inside of winamp.exe and change 9.0.21022.8 to 9.0.30729.6161 in the dependency node.
DrO is offline   Reply With Quote
Reply
Go Back   Winamp & Shoutcast Forums > Winamp > Winamp Bug Reports

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump