I am getting This program cannot be run in DOS mode
up vote
0
down vote
favorite
In some Windows OS, every command line program works fine, but in some Windows OS, such as WinXP, This program cannot be run in DOS mode error occurs.
How do I avoid this problem?
windows windows-xp command-line command-line-tool
|
show 2 more comments
up vote
0
down vote
favorite
In some Windows OS, every command line program works fine, but in some Windows OS, such as WinXP, This program cannot be run in DOS mode error occurs.
How do I avoid this problem?
windows windows-xp command-line command-line-tool
What program are you trying to run that causes that?
– Synetech
Sep 18 '12 at 23:21
nmap, pwdump and etc. (zenmap is not working also, in graphical side) but calc.exe works and other built-in exe's, so I am going like, what the hell is this?
– user41648
Sep 18 '12 at 23:28
Hmm, that’s strange because it sounds like a permission issue, but that wouldn’t be the error for permissions.
– Synetech
Sep 18 '12 at 23:38
Could this be DEP?
– user3463
Sep 18 '12 at 23:45
@RandolphWest, I can’t imagine that DEP would throw that error. The only reasons I can think of for that specific error would be either running it in DOS, or if the executable is corrupt.
– Synetech
Sep 18 '12 at 23:49
|
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In some Windows OS, every command line program works fine, but in some Windows OS, such as WinXP, This program cannot be run in DOS mode error occurs.
How do I avoid this problem?
windows windows-xp command-line command-line-tool
In some Windows OS, every command line program works fine, but in some Windows OS, such as WinXP, This program cannot be run in DOS mode error occurs.
How do I avoid this problem?
windows windows-xp command-line command-line-tool
windows windows-xp command-line command-line-tool
edited Oct 2 '12 at 5:58
HackToHell
5,80222962
5,80222962
asked Sep 18 '12 at 23:14
user41648
25126
25126
What program are you trying to run that causes that?
– Synetech
Sep 18 '12 at 23:21
nmap, pwdump and etc. (zenmap is not working also, in graphical side) but calc.exe works and other built-in exe's, so I am going like, what the hell is this?
– user41648
Sep 18 '12 at 23:28
Hmm, that’s strange because it sounds like a permission issue, but that wouldn’t be the error for permissions.
– Synetech
Sep 18 '12 at 23:38
Could this be DEP?
– user3463
Sep 18 '12 at 23:45
@RandolphWest, I can’t imagine that DEP would throw that error. The only reasons I can think of for that specific error would be either running it in DOS, or if the executable is corrupt.
– Synetech
Sep 18 '12 at 23:49
|
show 2 more comments
What program are you trying to run that causes that?
– Synetech
Sep 18 '12 at 23:21
nmap, pwdump and etc. (zenmap is not working also, in graphical side) but calc.exe works and other built-in exe's, so I am going like, what the hell is this?
– user41648
Sep 18 '12 at 23:28
Hmm, that’s strange because it sounds like a permission issue, but that wouldn’t be the error for permissions.
– Synetech
Sep 18 '12 at 23:38
Could this be DEP?
– user3463
Sep 18 '12 at 23:45
@RandolphWest, I can’t imagine that DEP would throw that error. The only reasons I can think of for that specific error would be either running it in DOS, or if the executable is corrupt.
– Synetech
Sep 18 '12 at 23:49
What program are you trying to run that causes that?
– Synetech
Sep 18 '12 at 23:21
What program are you trying to run that causes that?
– Synetech
Sep 18 '12 at 23:21
nmap, pwdump and etc. (zenmap is not working also, in graphical side) but calc.exe works and other built-in exe's, so I am going like, what the hell is this?
– user41648
Sep 18 '12 at 23:28
nmap, pwdump and etc. (zenmap is not working also, in graphical side) but calc.exe works and other built-in exe's, so I am going like, what the hell is this?
– user41648
Sep 18 '12 at 23:28
Hmm, that’s strange because it sounds like a permission issue, but that wouldn’t be the error for permissions.
– Synetech
Sep 18 '12 at 23:38
Hmm, that’s strange because it sounds like a permission issue, but that wouldn’t be the error for permissions.
– Synetech
Sep 18 '12 at 23:38
Could this be DEP?
– user3463
Sep 18 '12 at 23:45
Could this be DEP?
– user3463
Sep 18 '12 at 23:45
@RandolphWest, I can’t imagine that DEP would throw that error. The only reasons I can think of for that specific error would be either running it in DOS, or if the executable is corrupt.
– Synetech
Sep 18 '12 at 23:49
@RandolphWest, I can’t imagine that DEP would throw that error. The only reasons I can think of for that specific error would be either running it in DOS, or if the executable is corrupt.
– Synetech
Sep 18 '12 at 23:49
|
show 2 more comments
2 Answers
2
active
oldest
votes
up vote
1
down vote
Are you using Command.com or Cmd.exe? Try Cmd.
Also if you're using a shortcut to get to the command prompt, make sure you've not messed with the program's settings, especially those related to Memory or Compatibility (note: screenshots sourced from random site, do not configure as shown since those are probably not all default settings):


That’s what I thought of first, but it shouldn’t matter; it would still run Windows executables (remember, there do exist 16-bit Windows programs).
– Synetech
Sep 18 '12 at 23:39
1
@Synetech: No harm in checking. Maybe some setting such as Protected etc. is causing 32-bit EXEs to fail, thinking that the environment is actual DOS.
– Karan
Sep 18 '12 at 23:42
add a comment |
up vote
0
down vote
I have just encountered the same problem and found a solution that will probably work for you too.
I assume that you have used ftp via command line to get the files onto the machine that you are trying to run the exe on.
To fix the problem download the files again but remember to turn on binary mode. I did that and now the exes run no problem.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Are you using Command.com or Cmd.exe? Try Cmd.
Also if you're using a shortcut to get to the command prompt, make sure you've not messed with the program's settings, especially those related to Memory or Compatibility (note: screenshots sourced from random site, do not configure as shown since those are probably not all default settings):


That’s what I thought of first, but it shouldn’t matter; it would still run Windows executables (remember, there do exist 16-bit Windows programs).
– Synetech
Sep 18 '12 at 23:39
1
@Synetech: No harm in checking. Maybe some setting such as Protected etc. is causing 32-bit EXEs to fail, thinking that the environment is actual DOS.
– Karan
Sep 18 '12 at 23:42
add a comment |
up vote
1
down vote
Are you using Command.com or Cmd.exe? Try Cmd.
Also if you're using a shortcut to get to the command prompt, make sure you've not messed with the program's settings, especially those related to Memory or Compatibility (note: screenshots sourced from random site, do not configure as shown since those are probably not all default settings):


That’s what I thought of first, but it shouldn’t matter; it would still run Windows executables (remember, there do exist 16-bit Windows programs).
– Synetech
Sep 18 '12 at 23:39
1
@Synetech: No harm in checking. Maybe some setting such as Protected etc. is causing 32-bit EXEs to fail, thinking that the environment is actual DOS.
– Karan
Sep 18 '12 at 23:42
add a comment |
up vote
1
down vote
up vote
1
down vote
Are you using Command.com or Cmd.exe? Try Cmd.
Also if you're using a shortcut to get to the command prompt, make sure you've not messed with the program's settings, especially those related to Memory or Compatibility (note: screenshots sourced from random site, do not configure as shown since those are probably not all default settings):


Are you using Command.com or Cmd.exe? Try Cmd.
Also if you're using a shortcut to get to the command prompt, make sure you've not messed with the program's settings, especially those related to Memory or Compatibility (note: screenshots sourced from random site, do not configure as shown since those are probably not all default settings):


answered Sep 18 '12 at 23:38
Karan
48.8k1486156
48.8k1486156
That’s what I thought of first, but it shouldn’t matter; it would still run Windows executables (remember, there do exist 16-bit Windows programs).
– Synetech
Sep 18 '12 at 23:39
1
@Synetech: No harm in checking. Maybe some setting such as Protected etc. is causing 32-bit EXEs to fail, thinking that the environment is actual DOS.
– Karan
Sep 18 '12 at 23:42
add a comment |
That’s what I thought of first, but it shouldn’t matter; it would still run Windows executables (remember, there do exist 16-bit Windows programs).
– Synetech
Sep 18 '12 at 23:39
1
@Synetech: No harm in checking. Maybe some setting such as Protected etc. is causing 32-bit EXEs to fail, thinking that the environment is actual DOS.
– Karan
Sep 18 '12 at 23:42
That’s what I thought of first, but it shouldn’t matter; it would still run Windows executables (remember, there do exist 16-bit Windows programs).
– Synetech
Sep 18 '12 at 23:39
That’s what I thought of first, but it shouldn’t matter; it would still run Windows executables (remember, there do exist 16-bit Windows programs).
– Synetech
Sep 18 '12 at 23:39
1
1
@Synetech: No harm in checking. Maybe some setting such as Protected etc. is causing 32-bit EXEs to fail, thinking that the environment is actual DOS.
– Karan
Sep 18 '12 at 23:42
@Synetech: No harm in checking. Maybe some setting such as Protected etc. is causing 32-bit EXEs to fail, thinking that the environment is actual DOS.
– Karan
Sep 18 '12 at 23:42
add a comment |
up vote
0
down vote
I have just encountered the same problem and found a solution that will probably work for you too.
I assume that you have used ftp via command line to get the files onto the machine that you are trying to run the exe on.
To fix the problem download the files again but remember to turn on binary mode. I did that and now the exes run no problem.
add a comment |
up vote
0
down vote
I have just encountered the same problem and found a solution that will probably work for you too.
I assume that you have used ftp via command line to get the files onto the machine that you are trying to run the exe on.
To fix the problem download the files again but remember to turn on binary mode. I did that and now the exes run no problem.
add a comment |
up vote
0
down vote
up vote
0
down vote
I have just encountered the same problem and found a solution that will probably work for you too.
I assume that you have used ftp via command line to get the files onto the machine that you are trying to run the exe on.
To fix the problem download the files again but remember to turn on binary mode. I did that and now the exes run no problem.
I have just encountered the same problem and found a solution that will probably work for you too.
I assume that you have used ftp via command line to get the files onto the machine that you are trying to run the exe on.
To fix the problem download the files again but remember to turn on binary mode. I did that and now the exes run no problem.
answered Mar 16 at 0:20
Jason
111
111
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f476808%2fi-am-getting-this-program-cannot-be-run-in-dos-mode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What program are you trying to run that causes that?
– Synetech
Sep 18 '12 at 23:21
nmap, pwdump and etc. (zenmap is not working also, in graphical side) but calc.exe works and other built-in exe's, so I am going like, what the hell is this?
– user41648
Sep 18 '12 at 23:28
Hmm, that’s strange because it sounds like a permission issue, but that wouldn’t be the error for permissions.
– Synetech
Sep 18 '12 at 23:38
Could this be DEP?
– user3463
Sep 18 '12 at 23:45
@RandolphWest, I can’t imagine that DEP would throw that error. The only reasons I can think of for that specific error would be either running it in DOS, or if the executable is corrupt.
– Synetech
Sep 18 '12 at 23:49