| /haiku/src/system/runtime_loader/ |
| H A D | pe.cpp | aa4b5749d64af0c0573513c27296af16f4680367 Wed Jan 08 01:29:15 UTC 2014 Alexander von Gluck IV <kallisti5@unixzen.com> runtime_loader: Detect and trigger on PE binaries
* Previously PE binaries would trigger the "incorrectly
executable" dialog. Now we get a special message for
B_LEGACY_EXECUTABLE and B_UNKNOWN_EXECUTABLE
* Legacy at the moment is a R3 x86 PE binary. This could
be extended to gcc2 binaries someday far, far, down the
road though
* The check for legacy is based on a PE flag I see
set on every R3 binary (that isn't set on dos ones)
* Unknown is something we know *is* an executable, but
can't do anything with (such as an MSDOS or Windows
application)
* No performance drops as we do the PE scan last
* Tested on x86 and x86_gcc2
|
| H A D | pe.h | aa4b5749d64af0c0573513c27296af16f4680367 Wed Jan 08 01:29:15 UTC 2014 Alexander von Gluck IV <kallisti5@unixzen.com> runtime_loader: Detect and trigger on PE binaries
* Previously PE binaries would trigger the "incorrectly
executable" dialog. Now we get a special message for
B_LEGACY_EXECUTABLE and B_UNKNOWN_EXECUTABLE
* Legacy at the moment is a R3 x86 PE binary. This could
be extended to gcc2 binaries someday far, far, down the
road though
* The check for legacy is based on a PE flag I see
set on every R3 binary (that isn't set on dos ones)
* Unknown is something we know *is* an executable, but
can't do anything with (such as an MSDOS or Windows
application)
* No performance drops as we do the PE scan last
* Tested on x86 and x86_gcc2
|
| H A D | runtime_loader.cpp | aa4b5749d64af0c0573513c27296af16f4680367 Wed Jan 08 01:29:15 UTC 2014 Alexander von Gluck IV <kallisti5@unixzen.com> runtime_loader: Detect and trigger on PE binaries
* Previously PE binaries would trigger the "incorrectly
executable" dialog. Now we get a special message for
B_LEGACY_EXECUTABLE and B_UNKNOWN_EXECUTABLE
* Legacy at the moment is a R3 x86 PE binary. This could
be extended to gcc2 binaries someday far, far, down the
road though
* The check for legacy is based on a PE flag I see
set on every R3 binary (that isn't set on dos ones)
* Unknown is something we know *is* an executable, but
can't do anything with (such as an MSDOS or Windows
application)
* No performance drops as we do the PE scan last
* Tested on x86 and x86_gcc2
|
| H A D | Jamfile | aa4b5749d64af0c0573513c27296af16f4680367 Wed Jan 08 01:29:15 UTC 2014 Alexander von Gluck IV <kallisti5@unixzen.com> runtime_loader: Detect and trigger on PE binaries
* Previously PE binaries would trigger the "incorrectly
executable" dialog. Now we get a special message for
B_LEGACY_EXECUTABLE and B_UNKNOWN_EXECUTABLE
* Legacy at the moment is a R3 x86 PE binary. This could
be extended to gcc2 binaries someday far, far, down the
road though
* The check for legacy is based on a PE flag I see
set on every R3 binary (that isn't set on dos ones)
* Unknown is something we know *is* an executable, but
can't do anything with (such as an MSDOS or Windows
application)
* No performance drops as we do the PE scan last
* Tested on x86 and x86_gcc2
|
| /haiku/headers/private/system/ |
| H A D | pe_common.h | aa4b5749d64af0c0573513c27296af16f4680367 Wed Jan 08 01:29:15 UTC 2014 Alexander von Gluck IV <kallisti5@unixzen.com> runtime_loader: Detect and trigger on PE binaries
* Previously PE binaries would trigger the "incorrectly
executable" dialog. Now we get a special message for
B_LEGACY_EXECUTABLE and B_UNKNOWN_EXECUTABLE
* Legacy at the moment is a R3 x86 PE binary. This could
be extended to gcc2 binaries someday far, far, down the
road though
* The check for legacy is based on a PE flag I see
set on every R3 binary (that isn't set on dos ones)
* Unknown is something we know *is* an executable, but
can't do anything with (such as an MSDOS or Windows
application)
* No performance drops as we do the PE scan last
* Tested on x86 and x86_gcc2
|
| /haiku/headers/build/os/support/ |
| H A D | Errors.h | aa4b5749d64af0c0573513c27296af16f4680367 Wed Jan 08 01:29:15 UTC 2014 Alexander von Gluck IV <kallisti5@unixzen.com> runtime_loader: Detect and trigger on PE binaries
* Previously PE binaries would trigger the "incorrectly
executable" dialog. Now we get a special message for
B_LEGACY_EXECUTABLE and B_UNKNOWN_EXECUTABLE
* Legacy at the moment is a R3 x86 PE binary. This could
be extended to gcc2 binaries someday far, far, down the
road though
* The check for legacy is based on a PE flag I see
set on every R3 binary (that isn't set on dos ones)
* Unknown is something we know *is* an executable, but
can't do anything with (such as an MSDOS or Windows
application)
* No performance drops as we do the PE scan last
* Tested on x86 and x86_gcc2
|
| /haiku/headers/os/support/ |
| H A D | Errors.h | aa4b5749d64af0c0573513c27296af16f4680367 Wed Jan 08 01:29:15 UTC 2014 Alexander von Gluck IV <kallisti5@unixzen.com> runtime_loader: Detect and trigger on PE binaries
* Previously PE binaries would trigger the "incorrectly
executable" dialog. Now we get a special message for
B_LEGACY_EXECUTABLE and B_UNKNOWN_EXECUTABLE
* Legacy at the moment is a R3 x86 PE binary. This could
be extended to gcc2 binaries someday far, far, down the
road though
* The check for legacy is based on a PE flag I see
set on every R3 binary (that isn't set on dos ones)
* Unknown is something we know *is* an executable, but
can't do anything with (such as an MSDOS or Windows
application)
* No performance drops as we do the PE scan last
* Tested on x86 and x86_gcc2
|
| /haiku/src/kits/tracker/ |
| H A D | FSUtils.cpp | aa4b5749d64af0c0573513c27296af16f4680367 Wed Jan 08 01:29:15 UTC 2014 Alexander von Gluck IV <kallisti5@unixzen.com> runtime_loader: Detect and trigger on PE binaries
* Previously PE binaries would trigger the "incorrectly
executable" dialog. Now we get a special message for
B_LEGACY_EXECUTABLE and B_UNKNOWN_EXECUTABLE
* Legacy at the moment is a R3 x86 PE binary. This could
be extended to gcc2 binaries someday far, far, down the
road though
* The check for legacy is based on a PE flag I see
set on every R3 binary (that isn't set on dos ones)
* Unknown is something we know *is* an executable, but
can't do anything with (such as an MSDOS or Windows
application)
* No performance drops as we do the PE scan last
* Tested on x86 and x86_gcc2
|