Commandos: Behind Enemy Lines

Commandos: Behind Enemy Lines

MadLynx 12 AGO 2015 a las 8:00 a. m.
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.
Última edición por MadLynx; 3 DIC 2015 a las 8:50 a. m.
< >
Mostrando 1-15 de 57 comentarios
DJMS Hafidz 12 AGO 2015 a las 12:36 p. m. 
I can confirm this works with my Retail copy. Thanks for the info!!! :) Hope the devs will update the file by renaming it!
XxLaVaxX 12 AGO 2015 a las 3:17 p. m. 
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 17 AGO 2015 a las 4:44 a. m. 
Is this a troll post?!?
gustavo.reis.santos 17 AGO 2015 a las 6:03 p. m. 
Funcionou perfeitamente
ReiKaz 19 AGO 2015 a las 3:18 a. m. 
"comandos.exe" and renamed "commandos.exe" "I CAN NOT FIND DIRECTX 5" error.
Última edición por ReiKaz; 19 AGO 2015 a las 3:27 a. m.
MadLynx 19 AGO 2015 a las 4:06 a. m. 
Publicado originalmente por 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 21 AGO 2015 a las 12:06 a. m. 
Publicado originalmente por ml.redkov:
Publicado originalmente por 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!
Última edición por ReiKaz; 21 AGO 2015 a las 12:08 a. m.
jontsuba 21 AGO 2015 a las 12:06 p. m. 
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 21 AGO 2015 a las 1:21 p. m. 
This no worky for me...
ReiKaz 21 AGO 2015 a las 2:12 p. m. 
Publicado originalmente por 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 21 AGO 2015 a las 4:11 p. m. 
Worked for me thanks
jontsuba 21 AGO 2015 a las 5:10 p. m. 
Publicado originalmente por 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.
Última edición por jontsuba; 21 AGO 2015 a las 5:10 p. m.
ReiKaz 22 AGO 2015 a las 1:17 p. m. 
Publicado originalmente por jontsuba:
Publicado originalmente por 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 22 AGO 2015 a las 1:38 p. m. 
Publicado originalmente por ReiKaz:
Publicado originalmente por 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.
Última edición por MadLynx; 22 AGO 2015 a las 1:38 p. m.
MadLynx 22 AGO 2015 a las 1:41 p. m. 
Publicado originalmente por 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?
< >
Mostrando 1-15 de 57 comentarios
Por página: 1530 50