Commandos: Behind Enemy Lines

Commandos: Behind Enemy Lines

MadLynx Aug 12, 2015 @ 8:00am
Workaround for DirectX 5 issue on Windows 10
It seems that Windows 10 has some kind of auto-compatibility mechanism for running older games and it is based on the game executable file recognition. Therefore just rename the "comandos.exe" in your SteamApp game directory to the "commandos.exe" (one "m" is missing because of spanish speed fix). Then you can run the game from this renamed file, but not from the steam library -- it will say the file is missing. So this is temporary solution to run the Commandos: BEL waiting for a fix from support team.

ADD: see the Ryan2333's post for a helpful hint about running the game through Steam.
Last edited by MadLynx; Dec 3, 2015 @ 8:50am
< >
Showing 1-15 of 57 comments
DJMS Hafidz Aug 12, 2015 @ 12:36pm 
I can confirm this works with my Retail copy. Thanks for the info!!! :) Hope the devs will update the file by renaming it!
XxLaVaxX Aug 12, 2015 @ 3:17pm 
Holycrap this does work .

the other fix is compatibility to win95 & Reduced colormode 16bit run as admin ,
but i just also tried this what op post

Rename the "comandos.exe" in your game
directory to "commandos.exe"
(one "m" is missing ).
Then you can run the game from this renamed file,
but not from the steam library
[PHNX]Kordarus Aug 17, 2015 @ 4:44am 
Is this a troll post?!?
Funcionou perfeitamente
ReiKaz Aug 19, 2015 @ 3:18am 
"comandos.exe" and renamed "commandos.exe" "I CAN NOT FIND DIRECTX 5" error.
Last edited by ReiKaz; Aug 19, 2015 @ 3:27am
MadLynx Aug 19, 2015 @ 4:06am 
Originally posted by ReiKaz:
"comandos.exe" and renamed "commandos.exe" "I CAN NOT FIND DIRECTX 5" error.
Windows 10 x64, build 10240. Just checked it again and renaming works fine. Do you have DirectPlay installed from Legacy Components?

You can also try another fix from above post: set Compatibility to win95 or win98 & Reduced colormode 16bit. The game will start windowed.
ReiKaz Aug 21, 2015 @ 12:06am 
Originally posted by ml.redkov:
Originally posted by ReiKaz:
"comandos.exe" and renamed "commandos.exe" "I CAN NOT FIND DIRECTX 5" error.
Windows 10 x64, build 10240. Just checked it again and renaming works fine. Do you have DirectPlay installed from Legacy Components?

You can also try another fix from above post: set Compatibility to win95 or win98 & Reduced colormode 16bit. The game will start windowed.

Windows 10 Home x64 build 10240. DirectPlay enabled.
Renamed to "commandos.exe", compatibility to "Windows 95" - game working! :) you can add about compatibility to your solution :) Thanks!
Last edited by ReiKaz; Aug 21, 2015 @ 12:08am
jontsuba Aug 21, 2015 @ 12:06pm 
In my case, ever opening it from the SteamApps folder, it'll try to execute from Steam and say the file is missing... What did I do wrong? (DirectPlay enabled, windows 95, 16 bits)
manholecover55 Aug 21, 2015 @ 1:21pm 
This no worky for me...
ReiKaz Aug 21, 2015 @ 2:12pm 
Originally posted by jontsuba:
In my case, ever opening it from the SteamApps folder, it'll try to execute from Steam and say the file is missing... What did I do wrong? (DirectPlay enabled, windows 95, 16 bits)
Not from Steam, run renamed "commandos.exe".
adrian.rocks Aug 21, 2015 @ 4:11pm 
Worked for me thanks
jontsuba Aug 21, 2015 @ 5:10pm 
Originally posted by ReiKaz:
Not from Steam, run renamed "commandos.exe".

No, no. What I mean is that opening the executable from the windows explorer, directly, will promptly open Steam and then say he didn't find the executable.
Last edited by jontsuba; Aug 21, 2015 @ 5:10pm
ReiKaz Aug 22, 2015 @ 1:17pm 
Originally posted by jontsuba:
Originally posted by ReiKaz:
Not from Steam, run renamed "commandos.exe".

No, no. What I mean is that opening the executable from the windows explorer, directly, will promptly open Steam and then say he didn't find the executable.

Interesting. First time, same to me - didn't find the executable (i even pos it, but later edited post), but some how in later tries was "I CAN NOT FIND DIRECTX 5" error. then i try compatibility.
MadLynx Aug 22, 2015 @ 1:38pm 
Originally posted by ReiKaz:
Originally posted by ml.redkov:
Windows 10 x64, build 10240. Just checked it again and renaming works fine. Do you have DirectPlay installed from Legacy Components?

You can also try another fix from above post: set Compatibility to win95 or win98 & Reduced colormode 16bit. The game will start windowed.

Windows 10 Home x64 build 10240. DirectPlay enabled.
Renamed to "commandos.exe", compatibility to "Windows 95" - game working! :) you can add about compatibility to your solution :) Thanks!

My guess it may be hardware dependent because I haven't used any additional tricks beside the file renaming to run the game.
Last edited by MadLynx; Aug 22, 2015 @ 1:38pm
MadLynx Aug 22, 2015 @ 1:41pm 
Originally posted by jontsuba:
In my case, ever opening it from the SteamApps folder, it'll try to execute from Steam and say the file is missing... What did I do wrong? (DirectPlay enabled, windows 95, 16 bits)
Check your filepath. It should be smth like this: C:\Program Files (x86)\Steam\SteamApps\common\Commandos Behind Enemy Lines

Maybe you've renamed a link not an exe?
< >
Showing 1-15 of 57 comments
Per page: 1530 50