It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Any hints on how to get Wilderness Missions to launch on Windows 10? I installed Incubation to C:\GOG Games\ via direct download (that is, NOT via GOG Galaxy), then, thanks to a previous poster, solved the launch crash by replacing SOUND.DLL with an updated version. Incubation runs great in D3D or Glide, but launching Wilderness Missions from the shortcut with the –addons just results in an instance of Incubation running in the background consuming 50% CPU but no game displayed. How can I tell if Wilderness Missions files are properly installed? What does the –addons switch do? Any hints would be much appreciated!
No posts in this topic were marked as the solution yet. If you can help, add your reply
avatar
SCircuit: Any hints on how to get Wilderness Missions to launch on Windows 10? I installed Incubation to C:\GOG Games\ via direct download (that is, NOT via GOG Galaxy), then, thanks to a previous poster, solved the launch crash by replacing SOUND.DLL with an updated version. Incubation runs great in D3D or Glide, but launching Wilderness Missions from the shortcut with the –addons just results in an instance of Incubation running in the background consuming 50% CPU but no game displayed. How can I tell if Wilderness Missions files are properly installed? What does the –addons switch do? Any hints would be much appreciated!
Hi
I own the original incubation and incubation wilderness cds and just got it running on my Win 10 64 Bit system. This is how it worked for me:

- First I copied all the files from the Wilderness CD in a folder on my hd which I named incubation mission.

- Then I created a desktop shortcut from the wilderness setup.exe of my hd (i.e. from my newly created wilderness-hd-folder: C:\incubation mission\install).

- Now I started this desktop-shortcut in win 95/administrator-mode and voilá - wilderness installs in a seperate folder named c:\bluebyte\incubation...

At last I created a desktop-shortcut of the file incubation.exe (from my hand-copied folder C:\ incubation mission!) I started this shortcut in win95 mode and with administrator rights, result: the game runs perfectly.

Btw: I left the CD in the drive all the time. I got two DVD drives, in the first one is the original game, (don´t know if thats important too), but without the wilderness cd inserted in my second DVD drive the game won´t start). Btw I didn´t change any folders during the installation. Before the wilderness installation I got the original game installed and running in exact the same way.
So if you just got the files, it might be worth a try to burn them on a cd before you try to install and start the game. My incubation wilderness has got 372 MB and is named: Incubation_MP (don´t know if thats important or if there is any copy protection)
Good luck
Post edited December 18, 2016 by Klingelingeling
Thanks, Klingelingeling, for the detailed instructions on installing Wilderness Missions on Win 10. I too still have my original CDs and may give it a try. I still have an old XP computer with the Wilderness Missions installed but it’s a real pain to switch back to the old computer just for one game. I just played through Incubation for my second time. I’d like to keep going with Wilderness missions despite the reviews I’ve read that it’s a grueling campaign! I’d still be interested in hearing from anyone who is successfully running the GOG version of Wilderness Missions on Windows 10.
I forgot to mention: I also installed Oracle VM Virtual Box and you can install any old OS including nearly any old game inside this program,.

So I installed my old win xp into this virtual engine. Now, when I want to play a non-win 10-compatible older game, I simply install and start it inside Virtual Box - in which runs Win xp. This works with any old win xp game including Incubation. So it should also work for your GOG version.
And best of all: The fantastic Oracle VM Virtual Box costs nothing, you can download it anywhere for free
Post edited January 11, 2017 by Klingelingeling
If you look thoroughly sound.dll and audio.dll in the game directory are exactly the same files. The sound.dll is needed to run the original game and the audio.dll is needed to run the Wilderness Missions. So, to run the add-on you need to replace (copy with renaming) existing audio.dll with the same sound.dll you've just placed in order to run the original game in Windows 10.
Post edited May 23, 2017 by MadLynx
avatar
MadLynx: If you look thoroughly sound.dll and audio.dll in the game directory are exactly the same files. The sound.dll is needed to run the original game and the audio.dll is needed to run the Wilderness Missions. So, to run the add-on you need to replace (copy with renaming) existing audio.dll with the same sound.dll you've just placed in order to run the original game in Windows 10.
...and that helped....thanks a lot...WM working like charm....
avatar
MadLynx: If you look thoroughly sound.dll and audio.dll in the game directory are exactly the same files. The sound.dll is needed to run the original game and the audio.dll is needed to run the Wilderness Missions. So, to run the add-on you need to replace (copy with renaming) existing audio.dll with the same sound.dll you've just placed in order to run the original game in Windows 10.
Thank You for this. Your post is much appreciated to apply the fix for the Wilderness Missions!