So, because almost everyone wrote bad answers, I'll address the mistakes.
@Robert C
"Download a C+ compiler and decompile the files."
Huh? You take a compiler and decompile with it? Are you insane? As the name suggests, you *compile* with a compiler, not the reverse.
@MJ
"exes are usually encrypted"
No. Exes are not encrypted. Then the OS wouldn't understand them.
@Rose D
"What you saw was probably the assembly language"
No. What he saw was gibberish. Assembly language still needs to be compiled down to machine code. He isn't seeing any assembly language with a deassembler.
@Gene M
"Machine code is what the OS passes to the CPU where it becomes real binary."
Machine code *is* binary.
@Harsh
"There is no other editor designed to show us the machine code developed by the compiler from a higher level programming language."
Try a hex editor.
@Justin
"To read the 'machine code' (by which I think you are meaning the ones and zeros bitstream) and to recover source code, you need a decompiler."
No. Machine code doesn't need to be decompiled. Just open the file in a binary viewer like a hex editor or DOS's DEBUG or something.
So, Twist of Fate, you need to view the exe in a hex editor. Try XVI32 (http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm ) or Google for more options. But as OR1234 asked, what do you expect to do with this machine code? It's really nothing more than 1s and 0s. You might catch signs of string tables or the like, but seriously, if you can't open up an exe file properly, I bet you wouldn't even know what to do with the deassembled output. Try picking up a programming language if that's the direction you want to head in.