Audacity Forum

http://stackoverflow.com/questions/1531 ... -link-dead

Make sure you get the service pack. 2008 was notorious for random linker errors before it.

BTW that's a great guide.

I see nothing wrong with the links for VS2008 on http://wiki.audacityteam.org/wiki/Developing_On_Windows , except that it's a continual battle to keep the links updated as Microsoft remove download links to VS2008.

I have not installed VS2008 on Windows 8 yet but from numerous comments on Stack Overflow I believe it works. I assume you can use the version of Windows SDK advertised on http://wiki.audacityteam.org/wiki/Developing_On_Windows .

The later "Windows SDK for Windows 8" doesn't target Windows XP so it would not be any use to Audacity Team, and there are questions on the web (but no answers) as to whether "Windows SDK for Windows 8" supports VS2008.


Gale

steve wrote:

Gale Andrews wrote:If you were attempting it on a virtual machine under Ubuntu, that could be the reason.

That was my first attempt.
I then tried it on a real, (but old) hardware with little more success. At that time I didn't really have the will or inclination to persevere with something that appeared so convoluted and long winded on Windows, that could be done so easily on my preferred OS.

Yes it sounds like lack of motivation or interest was the problem.

When I first did it I had VS2008 without SP1 but the first run of Windows Update after that offered me VS2008 SP1 and other fixes for it (as it says on http://wiki.audacityteam.org/wiki/Developing_On_Windows ).

steve wrote:

Gale Andrews wrote:I thought http://www.hometownband.org/Audacity/Co ... acity.html was reasonably step like?

Let's try step 1:

1) Get Microsoft VC++ 2008 (this is the compiler you will need—it is free from Microsoft). You may get the 32-bit version (which will work on 64-bit) here:
Microsoft VC++ 2008

Where exactly on that page do I click to download Microsoft VC++ 2008 ?

Clearly the original link no longer exists and is redirected.

Again, the links on http://wiki.audacityteam.org/wiki/Developing_On_Windows are correct. It's up to Ed to ensure his links are correct. I agree we should not link to Ed's page until he rechecks it thoroughly.


Gale

Gale Andrews wrote:When I first did it I had VS2008 without SP1 but the first run of Windows Update after that offered me VS2008 SP1 and other fixes for it

Slightly off topic, but do you know the current status of the Microsoft Update for XP 100% cpu bug (http://answers.microsoft.com/en-us/wind ... 40c65acfa5) ? It seems that they fix it then within a few weeks it breaks again.

steve wrote:Do you know the current status of the Microsoft Update for XP 100% cpu bug (http://answers.microsoft.com/en-us/wind ... 40c65acfa5) ? It seems that they fix it then within a few weeks it breaks again.

This is Windows Update run in the web browser?

AFAICT from the end of that topic, the latest problem was that the update was choking trying to check legacy security updates for Internet Explorer which were irrelevant because the past updates were already cumulated into current updates.

So with the legacy updates deprecated, that problem should be fixed, and all should be OK assuming the user also has in place all other current IE fixes for issues that were causing their own hang.

I remember another gotcha now. Even if you download the VS2008 installer without SP1 which is itself only a few kb, the drive being downloaded to must have enough space to install VS even if you are not installing VS there. Otherwise, the installer hangs when you run it.


Gale

Gale Andrews wrote:This is Windows Update run in the web browser?

It also affects automatic update. Fixing the problem when it breaks is a pain, especially on single processor machines, because the computer just grinds to a halt as soon as the update service starts (which by default is automatic on start up). There are conspiracy theories about Microsoft doing it deliberately to drive users off XP, which don't sound at all far fetched if you experience the problem first hand

Gale Andrews wrote: It's up to Ed to ensure his links are correct. I agree we should not link to Ed's page until he rechecks it thoroughly.

Thanks for the heads up, Gale. I reworked the VC++ section improving the text and correcting the links.