1. #1
    Unregistered

    "Missing command interpreter" in HP desktop running windows XP

    I came across an error "Missing command interpreter" in my HP desktop running windows XP. Please let me know the causes for the same so that I can try to resolve the error.



  2. #2
    expert Array
    Join Date
    May 2012
    Posts
    1,791

    Re: "Missing command interpreter" in HP desktop running windows XP

    This error message is quite common in windows systems and can be due to several reasons. Some of the most common reasons for this error are listed below.
    • It can be due to a non bootable CD or else diskette in drive
    • Boot option may be setup improperly.
    • The command.com, io.sys, msdos.sys, or else drvspace.bin may be missing or corrupted.
    • It can be due to bad hard drive, as well
    You can check for these issues to get a solution for the same.

  3. #3
    deva Array
    Join Date
    Aug 2012
    Location
    hyd,ecil,jAI JAWAN COLONY
    Posts
    17

    Re: "Missing command interpreter" in HP desktop running windows XP

    History: Days before it crashed it started to bog down and then it restarted its self and would not load past blue Hp boot menu.

    I thought I solved the problem since it acted like it was over heating at first, so I cleaned the Mother Board, Graphics Card, Fans, Ram Cards, and Processor and then It worked great until it ran as normal for about 20 hours and then started to bog again. This time though it would not start all the way back up.

    I have a repair disc from Iolo Technologys (2008) version and when it boots it give me this error: "bad or missing command interpreter enter the full shell command line: command.com /P /E:256"

    I have done my research and the majority of other peoples problems are with leaving the repair cds in after fixing them, but mine hasn't even repaired anything and I have my BIOS setup as default which I hope is set to cd because if not I can't get the boot BIOS setting screen because it wont react to anything but a cd in the dri
    Subscribe
    449 videos










  4. #4
    Aniruddha Array
    Join Date
    Jul 2012
    Posts
    2,178

    Re: "Missing command interpreter" in HP desktop running windows XP

    hi,
    a few reasons are responsible for the state you are currently in:

    1. an operating system runs from a computers hard drive or c: drive that has a number of sequences, commands and directives that is known as booting, options of which may have altered due to reasons known or unknown to you.

    2. a number of vital files those are lifeline to a system to run, namely command.com, io.sys,msdos.sys takes control from BIOS to establish communication channels between machine and the user.Those files can be damaged to display the caution that you are getting.

    3. those vital files are usually written while getting installed, in the c drive or your hard drive. Now these drives time and again gets corrupted which technically called "bad track / bad sector ", anything which is/was written on these bad areas tend to get lost which disables the whole software from running, which can be a cause of your getting the message.


    4. a cd or dikette can be there in a drive which is found by the detection system of your computer by its pre booting commands stored in BIOS which refuse to search for bootable if it finds any other drive occupied by diskettes, causing a halt in booting process.

    Correct those errors and it will be fine. If problem still persists do a reinstallation of windows.
    Thank you.

  5. #5
    Abhishek Chauhan Array
    Join Date
    May 2012
    Posts
    899

    Re: "Missing command interpreter" in HP desktop running windows XP

    Hello,

    There are many causes for the error.

    Cause


    1. Non bootable CD or diskette in drive.
    2. Boot option setup improperly.
    3. The command.com, msdos.sys, io.sys or drvspace.bin is missing or corrupted.
    4. Bad hard drive.

    Solution

    Non bootable CD or diskette in drive
    It is possible that the computer may be attempting to boot from a device other than your hard drive. Verify that no floppy diskette or CD is in the computer.

    Boot option setup improperly

    Verify that the boot options are setup properly within CMOS. We recommend that the boot options be similar to:


    1. Floppy
    2. Hard Drive
    3. CD-ROM
    4. Network

    -Regards

  6. #6
    ROYAL SAINI Array
    Join Date
    Aug 2012
    Posts
    193

    Re: "Missing command interpreter" in HP desktop running windows XP



    hy friends;;;
    it my be many reasons why this problem occur please check out the bellow one:-

    @ it may be occur due to your hard drive problem

    @ or command , io.sys , msdos may be deleted or missing or corrupted in your window

    @ my dear another reason is that the CD drive of your pc will be spoiled

    @ these are the some such reasons why this problem occur

    @ please saw the given video to solve this error

    <span style="color:#ff0000;"><font size="3">



  7. #7
    anuj patel Array
    Join Date
    Aug 2012
    Posts
    168

    Re: "Missing command interpreter" in HP desktop running windows XP

    dear friend...

    this is one type of common error in computer. this is massage error

    this can be due to..........

    1. Insertion of unbootable CD
    2. Unbootable computer hardware
    3. Improper boot setup
    4. Bad hard dirve

    hope this info is sufficient for you
    thank you

  8. #8
    ajay569 Array
    Join Date
    Aug 2012
    Posts
    245

    Re: "Missing command interpreter" in HP desktop running windows XP

    DEAR::

    Invalid Boot Disk .

    Floppy left in floppy drive during boot/cd left in cd-rom during boot

    Failing hard drive


    Inaccessible boot device

    Corrupted boot volume

    Corrupted device drivers

    Boot Sector virus


    Missing NTLDR

    Reference: computer hope

    Solutions for each problem can be found at this site as well

    Computer is booting from a non-bootable source.

    Computer hard disk drive is not properly setup in BIOS.

    Corrupt NTLDR and/or NTDETECT.COM file.

    Misconfiguration with the boot.ini file.

    Attempting to upgrade from a Windows 95, 98, or ME computer that is using FAT32.

    New hard disk drive being added.

    Corrupt boot sector / master boot record.

    Seriously corrupted version of Windows 2000 or Windows XP.

    Loose or Faulty IDE/EIDE hard disk drive cable.


    Bad or Missing Command Interpreter

    Reference: Microsoft

    Windows 95 or the MS-DOS command interpreter (COMMAND.COM) is missing or has become corrupted.
    Troubleshooting Windows Issues

    Windows Protection Errors - This typically is caused by the type or speed of the RAM installed in the system.

    Bad or Missing COMMAND.COM - This means that the OS is unable to locate the file COMMAND.COM. To fix this problem use the make sure that the necessary boot files are located on the hard drive. If not, boot with the startup disk and enter the command SYS C:\ which will copy the system files to the hard drive(Windows 9x only).

    HIMEM.SYS not loaded - Check the CONFIG.SYS file and make sure that the line Device=C:\HIMEM.SYS exists and that the path specified to the file is where the file actually is.

    Error in CONFIG.SYS line XX - This error is usually caused by a syntax error in the CONFIG.SYS or AUTOEXEC.BAT file where XX will be the line number that the error occurred.

    Operating system not found - A common cause of this error is booting a system with a non-bootable floppy in the floppy drive. It can also be caused by missing boot files. To correct this, boot with the startup disk and enter the command SYS C:\ which will copy the system files to the hard drive(Windows 9x only).

    General Protection Faults(GPF) - Can be caused by software or hardware. GPFs can be caused by damaged core files which may need to be replaced or by a corrupt registry which can be restored from backup. They can be caused by running an application that is not designed for the operating system you are using. The Dr Watson utility will write information about these errors to DRWATSON.LOG which can be viewed for more information.

    Illegal Operation - Usually caused when 2 or more application attempt to use the same memory space. Incorrectly installed applications and software bugs. Try reinstalling the application and if the errors persist, check with the software vendor for patches/updates to the software.

    System locks up - Typically, this is caused by an application that is hung and can be corrected by ending the task. To end a task press CTRL + ALT + DEL and find the application that is not responding. ALT + F4 can also be used to close active windows. In Windows NT/2000/XP the CTRL + ALT + DEL or CTRL + SHIFT + ESC keys can be used to access Task Manager.

    Application will not start - Make sure that the file that is executed has a .EXE, .BAT or .COM extension. If attempting to run the application from a shortcut, make sure in the shortcut properties that the path to the application is correct.

  9. #9
    Deepu Array
    Join Date
    Sep 2012
    Posts
    140

    Re: "Missing command interpreter" in HP desktop running windows XP

    Hiiiiiiiiii
    This error message can occur when the Windows 95 or the MS-DOS command interpreter (COMMAND.COM) is missing or has become corrupted. Note that the Junkie virus is known to infect the COMMAND.COM and WIN.COM files. When the COMMAND.COM file is infected, its file size increases to 93,187 or 93,907 bytes.
    Replace the new MSDOS.SYS file with the backup copy.you can resolve the problem.

  10. #10
    firefox Array
    Join Date
    Jun 2012
    Posts
    913

    Re: "Missing command interpreter" in HP desktop running windows XP




    dear friend,

    When the command.com or win.com files gets corrupted/damaged then you can see the error.

    Follow these steps to solve this issue-

    Click on the Start button.
    Click on the Run icon-it'll open the Run window.
    Type cmd in the edit field & press enter-command prompt will open.
    Type the following instructions one by one in the command prompt & press consecutive enters.
    Wait till next command line approaches after finishing the previous task-

    To make a backup of present msdos.sys file-

    c:
    cd\windows\command
    attrib c:\msdos.sys -r -s -h
    ren c:\msdos.sys msdos.xxx

    To transfer the system files from start-up disc to the hard disc

    a:
    sys c:


    To replace the msdos.sys file with the backup copy-

    c:
    cd\windows\command
    attrib c:\msdos.sys -r -s -h
    del c:\msdos.sys
    ren c:\msdos.xxx msdos.sys
    attrib c:\msdos.sys +r +s +h


    Here c:\ is the drive name in which you've installed the windows OS.

    Restart your computer & check for the error.

    Hope these will help you a lot.

  11. #11
    mahhiads Array
    Join Date
    Oct 2012
    Posts
    264

    Re: "Missing command interpreter" in HP desktop running windows XP

    Hello Friend,

    If Your Boot Manager Missing From The OS Than Following Steps Are :

    1. Firstly Make The Bootable DVD Of OS Or Bootable Pen Drive
    2. Than Insert Pen Drive Or DVD Of OS But Make The BIOS Setting First If You Use The Pen Drive Than, Restart The PC
    3. Than Press Any Key In The Restarting Time When They Ask For Key So Press Any Key From The Keyboard Than Goes In The Installation Process For OS
    4. After That Installed The OS But First Format That Drive Than Start The Installation Than They Work Fine After That.

    I Hope That Info Is Usefully

  12. #12
    sumitnath Array
    Join Date
    Jan 2013
    Posts
    394

    Re: "Missing command interpreter" in HP desktop running windows XP

    Re: "Missing command interpreter" in HP desktop running windows XP

    hi friends,

    1. an operating system runs from a computers hard drive or c: drive that has a number of sequences, commands and directives that is known as booting options.
    2. a number of vital files those are lifeline to a system to run, namely command.com, io.sys,msdos.sys takes control from BIOS to establish communication channels between machine and the user.Those files can be damaged to display the caution that you are getting.
    3. those vital files are usually written while getting installed, in the c drive or your hard drive. Now these drives time and again gets corrupted which technically called "bad track / bad sector ", anything which is/was written on these bad areas tend to get lost which disables the whole software from running, which can be a cause of your getting the message
    4. a cd or dikette can be there in a drive which is found by the detection system of your computer by its pre booting commands stored in BIOS which refuse to search for bootable if it finds any other drive occupied by diskettes, causing a halt in booting process.

+ Reply to Thread

Similar Threads

  1. Replies: 5
    Last Post: 17-01-2013, 10:24 PM
  2. Replies: 2
    Last Post: 05-10-2012, 10:27 PM
  3. Replies: 2
    Last Post: 26-09-2012, 06:13 PM
  4. Replies: 3
    Last Post: 14-09-2012, 04:11 PM
  5. Replies: 4
    Last Post: 23-07-2012, 08:20 PM