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

×
Allright with 5 steps above I got rid of DX5 error, but at this moment I'm experiencing short freezes every couple seconds, no matter which resolution is running. Does anyone know Is this a common "trait" on 64bit Win10?
I tried different settings with dgVoodoo2 but it seems to be utterly pointless, granted I probbably didn't try every single one combination, but frankly I got tired of this.
And there is also issue of missing videos - while I can play videos outisde the game within it theyr'e just gone.
Maybe someone more patient than me figured out how to compel the game to runing smoothly.
avatar
Mmugi: Thanks very much for the inputs, but it didnt work.
Tried all compatibility modes, no succes (still "DIRECTX 5 NOT FOUND")

Hvala/Thanks!

Edit: I fixed it by reinstalling the game and changing the name of commandos.exe and deactivated all compatibilty mode settings. I had to deactivate "run as administrator" option too.

Now the game start on full screen mode correctly. seems working fine
avatar
x5129119: - I installed COMMANDOS: Behind Enemy Lines few mins ago. I only renamed the file "commandos" to "commandos.exe" and that worked. Did nothing else. On Windows 10 PC.
This worked for me! Thanks!!
Hey all,

ive got a problem. I have done everything. Changing the file name, installing patches, installing dx9. But still nothing works. I can see to Commandos logo and suddenly game stops working and it ends on windows desktop. W10 with all patches/fixes.

Please any help? I have to play this game again...and again :)
avatar
corman: Hey all,

ive got a problem. I have done everything. Changing the file name, installing patches, installing dx9. But still nothing works. I can see to Commandos logo and suddenly game stops working and it ends on windows desktop. W10 with all patches/fixes.

Please any help? I have to play this game again...and again :)
Run the game as administrator and in compatibility mode for WinXP SP3.
It doesnt work. Still the game starts - i see logo - and than back to desktop. Reinstallation was made 10 times etc. Game just wont start:(


PS. Found the solution. Bit Defender was blocking the game. You have to turn the game on in firewall.
Post edited May 02, 2018 by corman
Thanks for the post, Corman! I had the same issue also with Bitdefender. Had a lot of frustration.
Now it works after deblocking it in Bitdefender :D
avatar
melmangog: 1.
rename comandos.exe to commandos.exe.
2.
open cmd.exe as admin
3.
go to path where commandos is installt.
4.
enter mklink comandos.exe commandos.exe
5.
Play in GoGGalaxy
This is the right solution. It works.
It worked, yeah, but holy shit what kind of bootleg bullcrap is this? :D Thank god for these forums, even tho finding them wasn't obvious either. Robin Hood worked like a charm, then I saw Commandos for pennies, mean why not? It's a childhood classic. Didn't have to bother with cmd fortunately. Simply renaming stuff worked, don't care about galaxy.

And this happens. :D
Post edited June 05, 2019 by MrStrangerPL
avatar
F4LL0UT: Actually this solved the problem on two of my systems running Windows 7 64 bit, a friend also said that it worked for him. No idea why it didn't do the trick for you.
avatar
skeletonbow: As mentioned in other threads the reason that works on Windows 10 is because the OS has a compatibility database that has an entry for that game which is broken, so renaming it bypasses the compatibility entry. Windows 7 also has such a database, and I have it open in Microsoft Application Compatibility Toolkit right now and there is no entry for that game present. GOG also supplies databases with some of their games for Microsoft ACT (Dracula, Dracula 2 being a couple examples), but Commandos does not appear to have an entry.

So on my system, I do not see any evidence the binary is being handled specially by Windows, and I can confirm that renaming it to abcdefghijklmnop.exe did not stop the DX5 error from popping up. If it worked for you and you're using the same OS then there is obviously something different between our two systems for sure. :/
you have to rename both the executable program, like a 3 meg file, to commandos as well as changing the text in the GoG .info file to Commandos. doing just one or the other doesnt work.
None of that works.

It only runs if color mode is set to 16bit, and then only works windowed.

Also, the briefings are mute.
Post edited July 21, 2019 by BWFM
avatar
Jwrath: Ok it works by renaming Comandos.exe to Commandos.exe, but where are the videos? There's no intro video or any other cutscene. How can I fix that?
I know I'm replying to a really old post, but were you able to fix this? Videos won't play for me either. I've tried everything I could think of.
avatar
melmangog: 1.
rename comandos.exe to commandos.exe.
2.
open cmd.exe as admin
3.
go to path where commandos is installt.
4.
enter mklink comandos.exe commandos.exe
5.
Play in GoGGalaxy
It seems this won't work in the Galaxy 2.0 launcher. Well it isn't for me anyways. I'll just have to launch it from the folder for now.
avatar
Jwrath: Ok it works by renaming Comandos.exe to Commandos.exe, but where are the videos? There's no intro video or any other cutscene. How can I fix that?
I know this is really old and you proably won't see it, but I fixed it and I want to leave it here in case someone else has this issue.
If your videos are not showing and you have K-lite codec pack (or any other that uses LAV Video codecs) go to the LAV Video properties, and on the "Formats" tab, disable the cinepak codec (that's the one this game uses).
Hope this helps someone.
Ok so i download it on windows 10 and im getting direct x 5 not found error wtf :)
Solution: Go to where did you install your game and change the letters for example Commandos.exe into Commmandos.exe (just change one letter)that will get rid of direct x5 error not found :) working great on windows 10 64bit pro after this fix

Videos are working fine on my end :)