Executables

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Macros or automated scripting)
(Shared libraries, chained files, etc.)
 
(One intermediate revision by one user not shown)
Line 37: Line 37:
 
(can't be run by themselves, but are used at runtime by other executables)
 
(can't be run by themselves, but are used at runtime by other executables)
  
 +
* [[AIL real mode driver]] (.adv)
 
* [[Borland Graphics Interface]] (.bgi)
 
* [[Borland Graphics Interface]] (.bgi)
 +
* [[DIGPAK sound driver]]
 
* [[DOS device driver]] (.sys)
 
* [[DOS device driver]] (.sys)
 
* [[Dynamic library (OS X or iOS)]] (.dylib)
 
* [[Dynamic library (OS X or iOS)]] (.dylib)

Latest revision as of 15:29, 10 May 2024

File Format
Name Executables
Ontology

{{{caption}}}

Container formats for machine executable code. These often define different sections to be loaded into memory. Some formats may be compatible with different CPU architectures.

Contents

[edit] Directly executable

[edit] Shared libraries, chained files, etc.

(can't be run by themselves, but are used at runtime by other executables)

[edit] Interpreted program files

[edit] Resource data used by executables and sometimes embedded in them

See Resources.

[edit] Meta-info files used in execution of programs/packages

[edit] Virtual machine code

(see Wikipedia:UVC-based preservation for use of virtual machines in archival preservation)

[edit] Macros or automated scripting

For additional formats, see Programming Languages.

See also Executable envelopes#Compiled scripts.

[edit] Executable compression

Refer to Executable compression.

[edit] Executable envelopes

(Generated executables: self-extracting archives and installers, executable documents, etc.)

Refer to Executable envelopes.

[edit] See also

[edit] Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox