1.3 fails to load but 1.2 works
Posted: Wed Aug 25, 2010 6:52 pm
I am running XP Pro, service pack 3 on a ThinkPad T61. I have been using Audacity for a few years. Several months ago I downloaded and installed 1.3 and had used 1.3.9, 1.3.10, 1.3.11 then 1.3.12 without problem.
About a month ago, my Windows suffered a minor meltdown. When I recovered, 1.3.6 would no longer start, displaying the error message:
"The application failed to initialize properly (0xc0150004). Click on OK to terminate the application."
I uninstalled, rebooted, and reinstalled all the versions of 1.3 that I had saved (.9, .10, .11, and .12), multiple times in varied sequence, all to no avail. I even reinstalled XP service pack 3, which did nothing. The same error message was all I could get.
So I installed 1.2.6. Bingo - works fine even though the plugins.cfg file is empty.
But all attempts at installing 1.3 after showing that 1.2 works still produced the same error message.
My conclusion: 1.3 depends on some Windows routine that is not used in 1.2 and that routine was corrupted in the meltdown. One other hint - the only other program that seems to have been affected in the same way is WinAmp (although none of the older versions work either). All other programs that use the audio (Total Recorder, Windows media Player, VLC Player, etc.) work normally.
Does anyone have an idea what file could cause this behavior?
About a month ago, my Windows suffered a minor meltdown. When I recovered, 1.3.6 would no longer start, displaying the error message:
"The application failed to initialize properly (0xc0150004). Click on OK to terminate the application."
I uninstalled, rebooted, and reinstalled all the versions of 1.3 that I had saved (.9, .10, .11, and .12), multiple times in varied sequence, all to no avail. I even reinstalled XP service pack 3, which did nothing. The same error message was all I could get.
So I installed 1.2.6. Bingo - works fine even though the plugins.cfg file is empty.
But all attempts at installing 1.3 after showing that 1.2 works still produced the same error message.
My conclusion: 1.3 depends on some Windows routine that is not used in 1.2 and that routine was corrupted in the meltdown. One other hint - the only other program that seems to have been affected in the same way is WinAmp (although none of the older versions work either). All other programs that use the audio (Total Recorder, Windows media Player, VLC Player, etc.) work normally.
Does anyone have an idea what file could cause this behavior?