answersLogoWhite

0

AllQ&AStudy Guides
Best answer

At least two major reasons, 3 when you consider Linux runs on far more architectures than Windows:

1. Windows and Linux use completely different binary formats: Windows uses a poor excuse of a COFF-format ripoff called PE (Portable Executable, a name that has no meaning whatsoever because NO PE binaries are portable, and not all of them are executable.), Linux uses the almost universally standard format used by everyone and their dog except WINDOWS called ELF (Executable and Linkable Format, a name that actually is accurate to what the format actually is, executable or linkable. Note that even your PS3s and Wiis use ELF.)

2. They're two completely different operating systems! You can't expect them to have matching APIs or ABIs at all, and those are two things any kind of binary has to rely on to work. Thus, even if you get a binary in ELF format, just because it works in Linux A, doesn't necessarily mean it'll work on Linux B, especially if Linux B is on a different architecture or uses a different library set.

3. (Applies only in some cases.) You're trying to run a 32-bit Windows PE-executable on a 64-bit SPARC port of a Linux distribution, where the binary itself is not even going to be anything the system understands without emulation.

This answer is:
Related answers

At least two major reasons, 3 when you consider Linux runs on far more architectures than Windows:

1. Windows and Linux use completely different binary formats: Windows uses a poor excuse of a COFF-format ripoff called PE (Portable Executable, a name that has no meaning whatsoever because NO PE binaries are portable, and not all of them are executable.), Linux uses the almost universally standard format used by everyone and their dog except WINDOWS called ELF (Executable and Linkable Format, a name that actually is accurate to what the format actually is, executable or linkable. Note that even your PS3s and Wiis use ELF.)

2. They're two completely different operating systems! You can't expect them to have matching APIs or ABIs at all, and those are two things any kind of binary has to rely on to work. Thus, even if you get a binary in ELF format, just because it works in Linux A, doesn't necessarily mean it'll work on Linux B, especially if Linux B is on a different architecture or uses a different library set.

3. (Applies only in some cases.) You're trying to run a 32-bit Windows PE-executable on a 64-bit SPARC port of a Linux distribution, where the binary itself is not even going to be anything the system understands without emulation.

View page

Grand chase is ran by a EXE which is executable format ubuntu does not run EXE format

View page

EXE is not a format it is a file extension. The formal format of an EXE file in Windows is the Program Executable (PE) format and, these days, will either be in the PE32 or PE32+ format, the latter denoting a 64-bit executable.

However, EXE files are already encoded in native machine code. No conversion is required. If you want to render the code in a human readable form, use a disassembler. If you want to look at the raw code, use a hex editor.

View page

under you're bonnet in the engine

View page

If it's already in your PATH variable, then simply the name of the executable would do. If not, then use the full path of the executable or navigate to the directory of the executable and then ./executable where "executable" is the name of the executable.

View page
Featured study guide
📓
See all Study Guides
✍️
Create a Study Guide
Search results