Make a DOS Command

45,792

16

42

Introduction: Make a DOS Command

About: I live in Estes Park, Colorado. I like anything to do with science and I do a lot of sciency things.

Many people think that DOS is outdated, but I don't think so. You can do many things with DOS,and even Eric Wilhelm uses it! (See here) Some of the things you can do with DOS include giving yourself access to important files (good for hacking), deleting things, backing up things, showing all the files and folders in a folder, making simple but harmful viruses, and reformatting hard drives (!!). Unfortunately, when you want to run a program you made, you must type in the location if you want other information to be passed on to it. This instructable will teach you how to essentially make a command so you don't have to do this.

Step 1: Making the Program

Start by making a DOS executable. A DOS executable is a program that is run through CMD. These files can have six extensions: .exe, .com, .bat or .cmd .vbs or .vbe. Note that that you can use things passed into the program with %1, %2, %3 and so on.

When you have the program ready, rename it to the command you want, followed by its extension. Note that the command cannot contain spaces.

When ready, continue to step two.

Step 2: Transform It Into a Command

This is what turns it into a command. Copy the file into C:\WINDOWS\system32\. That is all you need to do. To test it, open cmd by typing "cmd" into start>Run and hitting enter. Test your command. Just type the name of the file, no extension. For example, if you want to go to instructables, just copy the attached file into C:\WINDOWS\system32, and then type "instructables" in cmd.

Note-The picture is making the icon for the program, which I did in .IcoFX

Step 3: How It Works

Press the windows button and pause/break on your keyboard. It will bring up a dialog called System Properties. Click the advanced tab. At the bottom, click environment variables. In the lower group box, scroll down to Path and PATHEXT. You will notice that the first thing in Path is C:\WINDOWS\system32. That is the directory that you put your command file in. Whenever you type in the command, it looks there for that file. In the PATHEXT variable, you will see the six main extensions you can use for your file, along with some others. If the file is in a directory that it is in the path variable, then you won't have to type a location. If its extension is in the PATHEXT variable, you won't have to type its extension. You will also notice that in C:\WINDOWS\system32, there are files like help.exe, xcopy.exe, and other DOS commands. They are being run the same way your command is run. You can prove this by opening CMD and typing your command. It will work. Then type "path ;" and hit enter. That will clear the path and make CMD look only in the current directory. Then, do CD and then another directory that is not C:\WINDOWS\system32. Now try your command again. It will not work. If you try a random DOS command, it might not work. For example, xcopy, help, attrib, cacls, chkdsk and taskkill will all not work anymore. That is because the path is cleared! This also means that if your program is in "C:\I am puffyfluff", then you could just add ;C:\I am puffyfluff to the end of the path variable, and you wouldn't have to copy it to C:\WINDOWS\system32.

Now you know how to make your own command!

Be the First to Share

    Recommendations

    • Mason Jar Speed Challenge

      Mason Jar Speed Challenge
    • Bikes Challenge

      Bikes Challenge
    • Remix Contest

      Remix Contest

    42 Discussions

    0
    microchip55
    microchip55

    10 years ago on Step 2

    you have to have admin permissions to though! is there a way without being a admin or making you on in cmd?

    0
    puffyfluff
    puffyfluff

    Reply 10 years ago on Introduction

    Yes, that's true, you need admin powers to access system32.  Of course, you can always just change the admin password using DOS...but that's probably something you shouldn't do.

    0
    chriskarr
    chriskarr

    Reply 10 years ago on Introduction

    Another method of accessing System32 is using Linux on an external drive and connecting it to the Windows box. You have full access to all of the system's files and the system administrator can do nothing about it! My friend, Tyler, does this and deletes system32 or renames it to profane names or things which are memes.

    0
    chriskarr
    chriskarr

    Reply 10 years ago on Introduction

    You would go about doing this by installing a linux partition on a USB hard disk, inserting the hard disk and, when the "select bootable hard disk' message appears, choose your removable disk. The computer will boot off of your disk and the entire hard disk of the system will be easily manipulated without restriction.

    Linux is an interesting OS. When you're using it on a harddrive also containing Windows, it says, "You know what? Go ahead and f*** this OS up; it's not me, so I don't care."
    When you try to access files in a Linux partition from a Windows partition or a different Linux partition, the one which you're trying to access says, "What do you think you're doing? These are mine, and I won't let you see them, a$$h***!"
    When you try to access the system files in a Linux OS which you own, it says, "Ummm...You need Root-Access to view these. Wait, what do you say? You have Root-Access? Well, I don't give a d***. If you want me dead, you'll have to do it my way."

    Doing anything to or from Windows OS', Windows says, "Can I help you with this? Perhaps I can bend over a little further."

    /me is visualizing the paperclip in Microsoft Office bending over past its elastic limit.

    0
    gryffn
    gryffn

    10 years ago on Step 2

     i got to system 32 with run.exe

    0
    raaams
    raaams

    11 years ago on Step 1

    byyyyyyyyyyyyyyyyyyyyyyyyyyt

    0
    puffyfluff
    puffyfluff

    Reply 11 years ago on Step 1

    ?
    Was that meant to be funny? If it was, it's just because I have a very bad sense of humor.

    0
    ranumm
    ranumm

    Reply 12 years ago on Introduction

    PowerShell is a new Command shell replacement for Windows. Object driven, and expandable using .NET Quite frankly it rocks. (let the windows bashing begin...)

    0
    iRule
    iRule

    Reply 11 years ago on Introduction

    vb is very good to .. it uses .NET if your using the program thing

    0
    iRule
    iRule

    Reply 11 years ago on Introduction

    cool .. lol its very good.

    0
    ranumm
    ranumm

    Reply 11 years ago on Introduction

    VB is ok, but if your serious about .NET, consider C#. Functionally, there is little that C# can do that VB cannot, but...C# is slightly more powerful, and much more consistent. Also, very much in demand right now...

    0
    iRule
    iRule

    Reply 11 years ago on Introduction

    i have the thing with vb, C,C++,dll, and all the others built into that program thing that makes it easier to write em.

    0
    puffyfluff
    puffyfluff

    Reply 11 years ago on Introduction

    I do everything in C++ now, whether it's console or GUI.

    0
    iRule
    iRule

    Reply 11 years ago on Introduction

    im no good at c++ so i dont try lol