Command interpreter; Can it execute any file?
- Thread starter ebo0763
- Start date
First of all what operating system are you running there? On a dos system you would change from the root directory where you are there if that is a dos prompt manually and enter the name of the executable file. That will usually see an "exe" three digit file extension on it. Some others like com. bat, ini are essential system files.
In newer NT based OSs the command interpreter is not intended for starting ptograms as a rule but more for imanual access to drives and repairs when Windows won't run normally. System utilities can be started there easily as part of a repair process. All Windows based programs will need Windows running in order to start.
In newer NT based OSs the command interpreter is not intended for starting ptograms as a rule but more for imanual access to drives and repairs when Windows won't run normally. System utilities can be started there easily as part of a repair process. All Windows based programs will need Windows running in order to start.
Hrmph. Umm... Well...
I will give you the real answer which is simply this. That prompt means that the system cannot find the command interpreter, which is command.com. You have to tell it where to find that file in order to be able to execute any programs. If you create a boot disk from Windows, it will put that file on the disk automatically. Otherwise, you will find it under C:\Windows\system32 in Windows XP.
I will give you the real answer which is simply this. That prompt means that the system cannot find the command interpreter, which is command.com. You have to tell it where to find that file in order to be able to execute any programs. If you create a boot disk from Windows, it will put that file on the disk automatically. Otherwise, you will find it under C:\Windows\system32 in Windows XP.
Real answer?
Command line interpreter
From Wikipedia, the free encyclopedia
Jump to: navigation, search
A command line interpreter is a computer program which reads lines of text that the user types and interprets them in the context of a given operating system or programming language.
Command interpreters as user interfaces
Command line interpreters allow users to issue various commands in a very efficient (and often terse) way. This requires the user to know the names of the commands and their parameters, and the syntax of the language that is interpreted. From the 1960s onwards, user interaction with computers was primarily by means of command line interfaces.
In the 1970s, researchers began to develop graphical user interfaces (GUIs) to provide an alternative user interface for computers, whereby commands were represented by pictorial operations, rather than as textual descriptions. Since they are easier to learn than command line interfaces, they have become the most common way of interacting with a computer. However, command line interpreters remain widely used in conjunction with GUIs. For some complex tasks, the latter are less effective because of the large number of menus and dialog boxes presented and because of the innate difficulty of representing the underlying task graphically.
Scripting
Most command line interpreters support scripting, to various extents. (They are, after all, interpreters of an interpreted programming language, albeit that in many cases the language is unique to the particular command line interpreter.) They will interpret scripts (variously termed shell scripts or batch files) written in the language that they interpret. Some command line interpreters also incorporate the interpreter engines of other languages, such as REXX, in addition to their own, allowing the executing of scripts, in those languages, directly within the command line interpreter itself.
Conversely, scripting programming languages, in particular those with an eval function (such as REXX, Perl, Python, or Jython), can be used to implement command line interpreters. For a few operating systems, most notably DOS, such a command interpreter provides a more flexible Command line interface than the one supplied. In other cases, such a command interpreter can present a highly customised user interface employing the user interface and input/output facilities of the language. http://en.wikipedia.org/wiki/Command_line_interpreter
"The command.com is the command interpreter for MS-DOS and is required for the majority of Microsoft's Operating Systems. Without command.com the computer running a Microsoft Operating System would be unable to boot.
When running Windows NT there are two versions of the command interpreter, command.com and cmd.exe. Cmd offers additional environment variables than command.com; however, it is recommend if you are attempting to run a MS-DOS utility that you utilize the command.com. To use command.com, click Start / Run and type command." http://www.computerhope.com/commandh.htm
Well that's very good. You can use Wikipedia. I'm impressed.
Unfortunately, as usual, you didn't read the OP properly and you gave him an answer that didn't answer his question accurately. You seem to do that a lot. It's almost like you get too far ahead of yourself or you don't comprehend the OP at all.
We don't need the answer of what a command line interpreter is to answer his question. Thank you for all your hard work to search Wikipedia, but it's irrelevant. All he needs to know is that he needs to execute it before he can execute programs, and the reason it is giving him that prompt is because command.com is not on the floppy or in the path like it's supposed to be.
Unfortunately, as usual, you didn't read the OP properly and you gave him an answer that didn't answer his question accurately. You seem to do that a lot. It's almost like you get too far ahead of yourself or you don't comprehend the OP at all.
We don't need the answer of what a command line interpreter is to answer his question. Thank you for all your hard work to search Wikipedia, but it's irrelevant. All he needs to know is that he needs to execute it before he can execute programs, and the reason it is giving him that prompt is because command.com is not on the floppy or in the path like it's supposed to be.
What you don't seem to understand is that ebo0763 hasn't had an opportunity to answer the question of what OS is this on? Is it dos, a 9X-ME, or NT, 2000, XP type with an NTFS partition? To simply things,
Command shell overview
The command shell is a separate software program that provides direct communication between the user and the operating system. The non-graphical command shell user interface provides the environment in which you run character-based applications and utilities. The command shell executes programs and displays their output on the screen by using individual characters similar to the MS-DOS command interpreter Command.com. The Windows XP command shell uses the command interpreter Cmd.exe, which loads applications and directs the flow of information between applications, to translate user input into a form that the operating system understands.
You can use the command shell to create and edit batch files (also called scripts) to automate routine tasks. For example, you can use scripts to automate the management of user accounts or nightly backups. You can also use the Windows Script Host, CScript.exe, to run more sophisticated scripts in the command shell. You can perform operations more efficiently by using batch files than you can by using the user interface. Batch files accept all commands that are available at the command line. For more information about batch files and scripting, see Using batch files
You can customize the command prompt window for easier viewing and to increase control over how you run programs. For more information about customizing the command prompt window, see To configure the command prompt http://www.microsoft.com/resources/...docs/en-us/ntcmds_shelloverview.mspx?mfr=true
It doesn't matter a damn what OS, as long as it's a Microsoft product (which it obviously is...command.com is exclusive to Microsoft). Like I said, you're getting carried away. Simplify your thought process. Start thinking like a computer and start reading the posts in their entirety and ask questions if you don't comprehend what the author is trying to get at. Command.com exists in every single Windows and DOS operating system, including Windows Vista.
Oh, and by the way, it is very clearly DOS that is making the call for the command interpreter.
Oh, and by the way, it is very clearly DOS that is making the call for the command interpreter.
Last edited:
"What you don't seem to understand is that ebo0763 hasn't had an opportunity to answer"
"What you don't seem to understand is that ebo0763 hasn't had an opportunity to answer"
"What you don't seem to understand is that ebo0763 hasn't had an opportunity to answer"
"What you don't seem to understand is that ebo0763 hasn't had an opportunity to answer"
Try booting with a dos or even 9X-ME boot floppy and see "A:>" with no request for a command interpreter. A Linux boot disk however will. If something is missing on a boot floppy made through Windows you then see a request there. [Which version of Windows = which OS is being used]
Just so that you know what you are talking about in the future, PC eye, here are some links for you:
http://www.easydesksoftware.com/news/news11.htm
http://www.google.ca/search?hl=en&q=Type+name+of+the+command+interpreter&meta=
http://www.easydesksoftware.com/news/news11.htm
http://www.google.ca/search?hl=en&q=Type+name+of+the+command+interpreter&meta=
You mean you are just now finding out about Setpoint. Download Set Point Version 1.4.06 - For Windows Millennium and XP only
Selected for Microsoft's Shareware Hall of Fame by and www.microsoft.com/windows98/downloads.This is the tool Microsoft forgot to include in Windows XP and ME. It does exactly what Windows left
out of System Restore : automate the creating of System Restore points. More information. http://www.easydesksoftware.com/down.htm#Point
But the one that you should actually be looking at is
"DOS is dead, long live the command line
Before proceeding further, I wish to clear up a common misconception that the command prompt in Windows XP is the same as DOS. Even some experts who know better sometimes refer to the command prompt as a “DOS window”. In fact, Microsoft itself isn't always careful about the distinction. There are some superficial resemblances and some commands with the same name but in fact the old 16-bit DOS is dead. All remnants of DOS are totally gone from the Windows XP kernel (there is a DOS emulator for legacy programs). Windows XP is a 32-bit protected memory system with a totally different approach from the DOS/9X/Me family. The command line in XP has many more capabilities and none of the 16-bit limitations like the restriction to the DOS 8.3 file name format. The augmented capabilities make the command line a powerful tool." http://commandwindows.com/command1.htm
Selected for Microsoft's Shareware Hall of Fame by and www.microsoft.com/windows98/downloads.This is the tool Microsoft forgot to include in Windows XP and ME. It does exactly what Windows left
out of System Restore : automate the creating of System Restore points. More information. http://www.easydesksoftware.com/down.htm#Point
But the one that you should actually be looking at is
"DOS is dead, long live the command line
Before proceeding further, I wish to clear up a common misconception that the command prompt in Windows XP is the same as DOS. Even some experts who know better sometimes refer to the command prompt as a “DOS window”. In fact, Microsoft itself isn't always careful about the distinction. There are some superficial resemblances and some commands with the same name but in fact the old 16-bit DOS is dead. All remnants of DOS are totally gone from the Windows XP kernel (there is a DOS emulator for legacy programs). Windows XP is a 32-bit protected memory system with a totally different approach from the DOS/9X/Me family. The command line in XP has many more capabilities and none of the 16-bit limitations like the restriction to the DOS 8.3 file name format. The augmented capabilities make the command line a powerful tool." http://commandwindows.com/command1.htm
What the hell does that have to do with anything? Again... you are not applying the proper concepts or listening to what people are telling you. You sure the command prompt in Windows XP isn't DOS?? No shit?? 
How that is relevant I have no idea, but you obviously have made some kind of connection there.. I must say it beats the hell out of me.. lol
Nobody said command.com is DOS.. Most certainly that is not true. It is AVAILABLE in DOS, but you appear to not be able to make the distinction. It is merely a command interpreter, nothing more. All Microsoft operating systems have it for obvious reasons.
In this case, once more in hopes that you will get it, it is a DOS (a disk operating system. It doesn't matter which one) that is making the call to the command interpreter, but can't find it in the path.
How that is relevant I have no idea, but you obviously have made some kind of connection there.. I must say it beats the hell out of me.. lol
Nobody said command.com is DOS.. Most certainly that is not true. It is AVAILABLE in DOS, but you appear to not be able to make the distinction. It is merely a command interpreter, nothing more. All Microsoft operating systems have it for obvious reasons.
In this case, once more in hopes that you will get it, it is a DOS (a disk operating system. It doesn't matter which one) that is making the call to the command interpreter, but can't find it in the path.
"Nobody said command.com is DOS." ? When you tranfer the system to a drive from an old 9X or ME boot floppy the "sys C:" command at the dos prompt copies the command.com onto the drive at the root of the then C:>command.com. In Fat16 and Fat32 versions after Windows is installed that file is then seen in the Windows directory. 2000 and XP are NT not Fat cored OSs. So where are you getting this crap about: "All Microsoft operating systems have it for obvious reasons."?
I know what sys c: does.. Umm.. I have used every version of DOS and Windows that has ever been released.
You don't have to do a sys command unless you want to make the drive bootable. Otherwise, just format it and install windows. Simple. I also know where command.com is located in windows.. I'm pretty damn sure I already stated where it was in this thread.
All Microsoft operating systems have it for obvious reasons because it is needed for executing executable programs from a prompt, whether that be from a shell, such as is seen in Windows NT based operating system, or from DOS, such as in MSDOS 6.22. That functionality is required to execute commands such as netsh, netsnd, ipconfig, call, set, testing out programs and batch files that you are coding and the like. It is also very handy for working with the file system manually as required. There is good reason for it to be there... CMD for enhanced functionality, COMMAND for basic functionality and 16 bit support.
You don't have to do a sys command unless you want to make the drive bootable. Otherwise, just format it and install windows. Simple. I also know where command.com is located in windows.. I'm pretty damn sure I already stated where it was in this thread.
All Microsoft operating systems have it for obvious reasons because it is needed for executing executable programs from a prompt, whether that be from a shell, such as is seen in Windows NT based operating system, or from DOS, such as in MSDOS 6.22. That functionality is required to execute commands such as netsh, netsnd, ipconfig, call, set, testing out programs and batch files that you are coding and the like. It is also very handy for working with the file system manually as required. There is good reason for it to be there... CMD for enhanced functionality, COMMAND for basic functionality and 16 bit support.
Last edited:
And by the way, wininit.ini and system.ini have NOTHING to do with this. They are initialization files. They have nothing to do with executing programs.
Glad you got that figured out!
And command.com is still not in the "C:\Windows\" directory is it? Not quite! Try the "C:\Windows\system32" folder there.