I seem to be the only one with that issue.
When I try to start Settlers 3 via the link, the single.exe starts and takes 50p CPU capacity (i.e. a full core, the maximum a program can take here). And then nothing happens.
When I try to start the S3.exe, or the S3 multiplayer, then the explorer.exe takes 50p CPU and hangs up.
In the editor, View Map In-Game also hangs it up.

Also, in the setup file, I can not turn off CD audio or use a colored mouse cursor, both settings are reset upon leaving the setup file.

Windows XP, SP3 here.

EDIT: Tried a bit around, same issue with a very old installation from CD. Also it does not matter if virus scanner (MS Security Essentials) is on or off.

Starts if the file is renamed to Siedler3.exe, i.e. to what it says is its original file name! This error only seems to happen on Windows XP SP3!

Can GOG please fix that? Maybe have the file name be Siedler3.exe by default or something.

EDIT, October 2016:
Windows 8+ fix: Rename or delete winmm.dll in the game directory. Now everything works fine! This might also work (instead renaming) on Windows XP and Windows 7, but I can't test that.

I've just bought the game and had the same issue on both of my XP SP3 computers, while the game runs perfectly on my Windows 7 laptop. Your solution worked perfectly for XP, thank you =)

Good to know I'm not alone on that. Thanks!

By the way, I've also noticed, that if you rename S3.exe to Siedler3.exe, then the multiplayer options give a error (tried a LAN game between my two PCs and it crashed after loading the map on both PCs).
But if you rename S3_multi.exe to Siedler3.exe, then both the campaign and multiplayer options work without crashing, so using the "multiplayer" file seems like a better choice.

EDIT: Somewhy the game doesn't save the serial, so I have to input it every time I run the game on XP.
This problem doesn't occur on Windows 7.

EDIT 2: Today the game doesn't ask for serial anymore, so there are no more problems so far.

You are not the only one!
We XP lepers are left in the lurch again :)

I had the same trouble with Psychonauts, which was fixed by re-installing it to C:\.

I tried that with S3 & the same hang happened as you experienced, both with internal & external drive installations.

I shall now try renaming to die siedler and see if all becomes well again.

I did have to chuckle that the newer "Good Old Games" seem to have trouble with "Good Old Operating Systems" :)

No offence GOG !
Your success rate is about 99.9% with first time runs, so there's nothing to complain about when the odd install is troublesome. A patch would be nice though ....

Ta

Many Thanks.

Siedler3.exe appears to do the trick, at least until a patch is issued.

This seems to be a good workaround for XP users.

_________

I just bought and I get the same problem with Settlers III on XP Pro SP3

Please try renaming your S3.exe file to Siedler3.exe and start that file.

That works.
Thanks.

Hi,

I have the same issue and I'm running Windows 10. Any of you who has an idea how to resolve it ?

Hi,

I also use Windows 10 and can't get S3 running. Renaming doesn't help.
I bought this game on GOG and do really hope to find a solution !!
:-(

Guys, this post is an old one for Windows XP. Windows 10 has a different issue with Settlers 3.

You have to find the file (in the folder where you installed the game) called winmm.dll and rename that to anything.

Thanks,
I will try that !!

This worked!

Thank you!

Windows 10 Fix :)

Hello there,
Do you mean the file in an errorlog?
Cant find any other winmm.dll except in the win sys.
Andvekr