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

×
Trying to run this game on Windows 7 64 Bit. Won't even start. Goes to a black screen and then cuts back to windows and a message saying "DIRECTX 5 NOT FOUND." I tried installing DirectX 9 since I heard sometimes you need to do that on top of DirectX 11 for older games but it didn't work. I can get it to start in a windowed mode if I set the whole desktop to 16 bit color, but that seems like kind of a pain.

I also tried several of the unofficial hacks BEL Loader and the other one.

I thought GOG's whole thing was getting stuff to run on new computers. Seems like they should have this worked out. Is there some way to get it running better?
I have the same issue.
Post edited July 01, 2015 by NWOD
yep, this doesn't work correctly and GOG wont do anything about it.

As mentioned by the OP, you can run the program in 16 bit colour mode, but you will only get it in a windowed mode, which doesn't work correctly as your mouse will not scroll and instead goes on to your windows desktop.

Very disappointing as I had heard good things about GOG and I see they are still selling the game regardless.
Same issue here with win10 (final build) x64
First, install DirectX 9.0c from here: http://www.microsoft.com/en-us/download/details.aspx?id=8109

Then try extracting the BEL/BtCoD Ultimate Fix (overwrite when prompted): http://www.mediafire.com/download/7vmmwaaoqgoo1oy/Commandos_BEL_BCD_Ultimate_Fixes.rar

NOTE:
For BEL, you need these files from that RAR: comandos.exe, wargame.dir
For BtCoD, you need these files from that RAR: coman_mp.exe, war_mp.dir
Post edited August 03, 2015 by Plokite_Wolf
avatar
Plokite_Wolf: First, install DirectX 9.0c from here: http://www.microsoft.com/en-us/download/details.aspx?id=8109

Then try extracting the BEL/BtCoD Ultimate Fix (overwrite when prompted): http://www.mediafire.com/download/7vmmwaaoqgoo1oy/Commandos_BEL_BCD_Ultimate_Fixes.rar

NOTE:
For BEL, you need these files from that RAR: comandos.exe, wargame.dir
For BtCoD, you need these files from that RAR: coman_mp.exe, war_mp.dir
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
Post edited August 03, 2015 by Mmugi
Hi :)

GoG must to do something... or communicate...

I've the same issue under Windows 10 x64.

Thanks Mmugi, that's works!!!! ;-)
Post edited August 05, 2015 by modlife
On windows 10, after following the instructions on this thread: problems_launching_the_game_please_come_in_and_have_a_seat of rainbow six(sorry I cannot post a link to the thread directly), that fellow spacekiltro described the use of dgVoodoo to emulate DX1-7 using DX11, I tried the same method here, I also made a copy of the executable commandos.exe to commandos1.exe to remove any compatibility settings. The game run in a window as expected and then I clicked the game icon in the taskbar and turned fullscreen without any problem.

EDIT: You can also make the game run from GOG Galaxy if you change the executable filename inside the goggame-XXXXXXXXXX.info file. (the Xs are a number I have no idea about, possibly the game id) in the line:
"path" : "Comandos.exe",
Post edited August 29, 2015 by maxstrax
high rated
I had the same issue with commandos: Behind Enemy Lines. The solution i found for this game was to rename the comanos.exe to commandos.exe. It fixed the problem. Now i am looking for a way to find a solution for commandos Beyond call of duty.
avatar
DEADPOOLgr: The solution i found for this game was to rename the comanos.exe to commandos.exe. It fixed the problem.
This. Too bad this was not a question thread so people will probably keep missing your answer.
Renaming comandos.exe fixed it for me as well. Looks like Windows is forcing some sort of compatibility setting down the games throat based on the name of the exe.


And yes, changing the "path" : "comandos.exe" in the goggame info file to the new filaname enables it to work through gog galaxy.
Post edited February 04, 2016 by JohnCaboose
avatar
JohnCaboose: Renaming comandos.exe fixed it for me as well. Looks like Windows is forcing some sort of compatibility setting down the games throat based on the name of the exe.
That is beyond stupid. But hey, it works now. Thanks everyone.
avatar
JohnCaboose: Renaming comandos.exe fixed it for me as well. Looks like Windows is forcing some sort of compatibility setting down the games throat based on the name of the exe.
avatar
vaalc4r: That is beyond stupid. But hey, it works now. Thanks everyone.
Yes, it's a bit weird, but worked for me, too. I changed comandos.exe to commandos.exe (double 'm'), as well as edited the info file to reflect the change and it started through GOG Galaxy.

Thanks!
avatar
vaalc4r: That is beyond stupid. But hey, it works now. Thanks everyone.
avatar
mlech: Yes, it's a bit weird, but worked for me, too. I changed comandos.exe to commandos.exe (double 'm'), as well as edited the info file to reflect the change and it started through GOG Galaxy.

Thanks!
Thanks for tips everyone.

I copied the comandos.exe binary to the same directory and running the copied version with the new filename worked for me.

No need to do any of the other steps in this thread. I just renamed the file and it fixed the directx 5 not found message i was getting.

Windows 10 64 Bit.
avatar
F4LL0UT: This. Too bad this was not a question thread so people will probably keep missing your answer.
Which is ok because that doesn't work on Windows 7 64bit, only on Windows 10 apparently. I've tried every fix for this DIRECTX 5 issue mentioned in every thread in the forums and not one of them works on Windows 7 64bit for me yet. :/

Looks like the only way to run this game might be in a virtual machine using Windows 98SE or XP perhaps.


(Also want to note that the original poster had the problem on Windows 7 64bit and never returned to comment indicating he ever managed to get it to work either.)
Post edited October 04, 2016 by skeletonbow