Cmd commands not working

By BlackScarlet
Oct 17, 2013
Post New Reply
  1. I have been trying to launch various cmd commands, but none of them are working.

    A while back I used the 'convert.exe' option to change a USB drive from FAT to NTFS.

    I typed 'convert X: /fs:ntfs' and it worked fine -- I've done that before. (X represents variable drive letter)
    Now I am trying to do the same thing, but it is saying "'convert' is not recognized as an internal or external command, operable program, or batch file".

    It dawned on me that it was doing the same thing when I was trying unsuccessfully to launch apktool.

    So I decided to go more basic than that. I did a simple "ping www.google.ca" and I got the same error.

    Why are my cmd commands not working?



    Operating System
    Windows 7 Ultimate (x64) Service Pack 1 (build 7601)

    Processor
    3.20 gigahertz Intel Core i5-3470
    128 kilobyte primary memory cache
    1024 kilobyte secondary memory cache
    6144 kilobyte tertiary memory cache
    64-bit ready
    Multi-core (4 total)
    Not hyper-threaded

    Board:
    Gigabyte Technology Co., Ltd. H77M-D3H
    Bus Clock: 100 megahertz
    BIOS: American Megatrends Inc. F5 03/29/2012

    RAM:
    Slot 'ChannelB-DIMM0' has 8192 MB

    Display:
    NVIDIA GeForce GTX 660 [Display adapter]
    Samsung SyncMaster [Monitor] (24.0"vis, s/n YCUYHVDZ702086, July 2010)

    Audio:
    NVIDIA High Definition Audio
    VIA High Definition Audio
  2. gbhall

    gbhall TechSpot Chancellor Posts: 2,335   +49

    A command window opens in a location which is defined in the properties of the way you start cmd.exe. You need to make sure it starts from somewhere where the command you wish to execute can be found. In your case, you wish to execute 'convert.exe'. That is to be found in c:\windows\system32 by default - and so are most other useful commands - so you want the cmd.exe window to open in c:\windows\system32

    A lot depends on how you launch cmd.exe. Do that now and check if you are greeted by ''c:\windows\system32>'' If not there is your problem in a nutshell.

    I'll assume you start it by pressing the windows key and typing cmd into the search box. Before you press enter, up should pop 6 or 7 options, of which cmd.exe should be at the top of the list. Right-click on that item in the list and click on 'properties' and look at the value 'start in'. If necessary, change it to %HOMEDRIVE%%HOMEPATH%

    I've completely ignored a string of other possibilities concerning system paths, user permissions, malware invasion and so forth, that we can get to if we need to.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.