http://fileformats.archiveteam.org/api.php?action=feedcontributions&user=Felix&feedformat=atomJust Solve the File Format Problem - User contributions [en]2024-03-28T19:22:07ZUser contributionsMediaWiki 1.19.2http://fileformats.archiveteam.org/wiki/Icon_libraryIcon library2016-09-12T16:34:59Z<p>Felix: Redirected page to New Executable</p>
<hr />
<div>#REDIRECT [[New Executable]]</div>Felixhttp://fileformats.archiveteam.org/wiki/Talk:Web_Audio_APITalk:Web Audio API2016-09-12T16:21:46Z<p>Felix: Created page with "Are there any sample files in this file format? ~~~~"</p>
<hr />
<div>Are there any sample files in this file format? [[User:Felix|felix]] ([[User talk:Felix|talk]]) 16:21, 12 September 2016 (UTC)</div>Felixhttp://fileformats.archiveteam.org/wiki/COFFCOFF2016-09-12T16:18:14Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Executables<br />
|extensions={{ext|o}}<br />
}}<br />
The '''Common Object File Format''' ('''COFF''') is a format used for object code and executables. It was originally developed for UNIX System V by AT&T. It was intended as a replacement for [[a.out]], adding features like shared libraries and relocation records, but it was shortly after replaced by the [[ELF]] format. The COFF format has many incompatible extensions.<br />
<br />
The [[Portable Executable]] format is based on COFF. COFF is also the native object format of the DJGPP toolchain; executables produced by it are COFF files with an [[MZ]] stub prepended.<br />
<br />
==References==<br />
* Texas Instruments has a nice [http://www.ti.com/lit/an/spraao8/spraao8.pdf overview] of the COFF format<br />
* Since DJGPP uses a variant of COFF, they also have a summary available [http://www.delorie.com/djgpp/doc/coff/ here]</div>Felixhttp://fileformats.archiveteam.org/wiki/COFFCOFF2016-09-12T16:17:56Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Executables<br />
}}<br />
The '''Common Object File Format''' ('''COFF''') is a format used for object code and executables. It was originally developed for UNIX System V by AT&T. It was intended as a replacement for [[a.out]], adding features like shared libraries and relocation records, but it was shortly after replaced by the [[ELF]] format. The COFF format has many incompatible extensions.<br />
<br />
The [[Portable Executable]] format is based on COFF. COFF is also the native object format of the DJGPP toolchain; executables produced by it are COFF files with an [[MZ]] stub prepended.<br />
<br />
==References==<br />
* Texas Instruments has a nice [http://www.ti.com/lit/an/spraao8/spraao8.pdf overview] of the COFF format<br />
* Since DJGPP uses a variant of COFF, they also have a summary available [http://www.delorie.com/djgpp/doc/coff/ here]</div>Felixhttp://fileformats.archiveteam.org/wiki/MS-DOS_EXEMS-DOS EXE2016-09-12T16:17:20Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Executables<br />
|extensions={{ext|exe}}<br />
|pronom={{PRONOM|x-fmt/409}}<br />
}}<br />
'''MZ''' (also called by its extension '''EXE''' and by other names) is an executable file format used mainly by [[MS-DOS]]; the format is a successor of [[DOS executable (.com)|COM]].<br />
<br />
Many other executable formats are extensions of MZ, including [[New Executable]] (used by 16-bit Windows), [[Portable Executable]] (newer Windows versions) and [[Linear Executable]] (OS/2). Files in these formats usually begin with a short MZ program (called a DOS stub) which, when executed by DOS, prints a message like "This program cannot be run in DOS mode" or "This program requires Microsoft Windows" and immediately exits. Some programs contain a more functional DOS stub, e.g. the Windows 9x registry editor.<br />
<br />
== Identification ==<br />
An MZ file begins with an ASCII signature of {{magic|'M' 'Z'}} (or, rarely, {{magic|'Z' 'M'}}), followed by a series of 16-bit fields. The field at offset 24 (the relocation table offset) is ''usually'' (but apparently not always) less than 64, and at least 28.<br />
<br />
== Links ==<br />
* [[Wikipedia:DOS MZ executable|Wikipedia article]]<br />
* [http://wiki.osdev.org/MZ MZ], from the OSDev Wiki<br />
* http://www.delorie.com/djgpp/doc/exe/<br />
* [http://www.textfiles.com/programming/FORMATS/exefs.pro DOS EXE format]<br />
* [http://www.mitec.cz/exe.html EXE Explorer utility]<br />
<br />
[[Category:Microsoft]]</div>Felixhttp://fileformats.archiveteam.org/wiki/FNT_(Windows_Font)FNT (Windows Font)2016-09-12T16:04:44Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Fonts<br />
|extensions={{ext|fnt}}<br />
}}<br />
'''FNT''' is a mostly-obsolete bitmap font format associated with Microsoft Windows. FNT-format fonts are most commonly found inside [[Windows resource|resources]] of [[New Executable]] (sometimes [[Portable Executable]]) files carrying the extension <code>.fon</code>; they may also appear standalone (without a container), where they have the extension <code>.fnt</code>.<br />
<br />
== Software ==<br />
* [http://www.seasip.info/Unix/PSF/ PSF Tools]<br />
<br />
== Links ==<br />
* [http://support.microsoft.com/kb/65123 Windows Developers Notes: Font-File Format] - Covers versions 2 and 3 of the format.<br />
* [http://www.os2museum.com/files/docs/win10sdk/windows-1.03-sdk-prgref-1986.pdf Windows 1.03 Programmer's Reference] (PDF) - Appendix C describes version 1 of the format.<br />
* [https://msdn.microsoft.com/en-us/library/cc250412.aspx MSDN: CharacterSet Enumeration] - Codes used by the ''dfCharSet'' field<br />
<br />
[[Category:Microsoft]]</div>Felixhttp://fileformats.archiveteam.org/wiki/New_ExecutableNew Executable2016-09-12T16:01:51Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Executables<br />
|extensions={{ext|cpl}}, {{ext|dll}}, {{ext|drv}}, {{ext|exe}}, {{ext|fon}}, {{ext|icl}}, {{ext|scr}}<br />
|pronom={{PRONOM|x-fmt/410}}<br />
}}<br />
'''New Executable''' ('''NE''') is an file format used by some versions of OS/2, MS-DOS and most commonly by 16-bit Microsoft Windows; it is used for executables, dynamically-linked libraries, drivers and as a container for [[Windows resource|resources]]. The NE format is an extension of [[MZ]]; it was succeeded by [[Portable Executable]] on Windows and [[Linear Executable]] on OS/2.<br />
<br />
NE is used as a container format for [[FNT (Windows Font)|FNT]] fonts (in files carrying the extension {{ext|fon}}) and for icon libraries (extension {{ext|icl}}).<br />
<br />
== Identification ==<br />
An NE file begins with the ASCII signature "<code>MZ</code>". At offset 60 is a 4-byte integer pointing to an "extended" header that begins with "<code>NE</code>". For more information, see [[MS-DOS EXE]].<br />
<br />
== Sample files ==<br />
* Lots of examples at [http://cd.textfiles.com/ cd.textfiles.com], such as<br />
** http://cd.textfiles.com/49games/49GAMES/ → .../*.EXE<br />
** http://cd.textfiles.com/aztechmb/<br />
** http://cd.textfiles.com/sbup/<br />
** http://cd.textfiles.com/waycool/GAMES/<br />
<br />
== See also ==<br />
* [[Dynamic-link library (Windows)]]<br />
<br />
== Links ==<br />
* [[Wikipedia:New Executable|Wikipedia article]]<br />
* [http://www.fileformat.info/format/exe/corion-ne.htm The NE EXE File Format]<br />
* [http://wiki.osdev.org/NE NE], from the OSDev Wiki<br />
* [http://www.csn.ul.ie/~caolan/pub/winresdump/winresdump/doc/winexe.txt Executable-File Header Format (3.1)]<br />
* [http://benoit.papillault.free.fr/c/disc2/exefmt.txt Executable-File Header Format (3.00)]<br />
* [http://www.mitec.cz/exe.html EXE Explorer utility]<br />
<br />
[[Category:Microsoft]]<br />
[[Category:OS/2]]</div>Felixhttp://fileformats.archiveteam.org/wiki/Dynamic-link_library_(Windows)Dynamic-link library (Windows)2016-09-12T15:54:03Z<p>Felix: this is not a file format</p>
<hr />
<div>"Dynamic-link library" is not a file format; it is a name for dynamically-loadable object files (shared objects) used on the Windows platform, where such files have various extensions, most commonly <code>[[:Category:File formats with extension .dll|.dll]]</code>. Dynamic-link libraries may be in any of the following formats:<br />
<br />
* [[New Executable]]<br />
* [[Portable Executable]]<br />
<br />
{{Disambiguation}}</div>Felixhttp://fileformats.archiveteam.org/wiki/EXEEXE2016-09-12T15:53:49Z<p>Felix: </p>
<hr />
<div>"<code>[[:Category:File formats with extension .exe|.exe]]</code>" is a file extension of various executable file formats, most of which are based on [[MZ]], the executable format of MS-DOS. The following formats use this extension:<br />
<br />
* [[MZ]]<br />
* [[Portable Executable]]<br />
* [[New Executable]]<br />
* [[Linear Executable]]<br />
<br />
{{Disambiguation}}</div>Felixhttp://fileformats.archiveteam.org/wiki/Security_CatalogSecurity Catalog2015-09-09T18:17:02Z<p>Felix: well, apart from this</p>
<hr />
<div>{{FormatInfo<br />
| formattype = electronic<br />
| subcat = Security<br />
| extensions = {{ext|cat}}<br />
}}<br />
[[Windows]] '''Security Catalog''' files store digital signatures for any collection of files and are used to verify device drivers.<br />
<br />
Catalog files are ordinary [[PKCS7|PKCS#7 signed-data messages]].<br />
<br />
== Software ==<br />
* [https://msdn.microsoft.com/en-us/library/aa386967.aspx MakeCat] (for creation)<br />
<br />
== Links ==<br />
* [https://msdn.microsoft.com/en-us/library/windows/hardware/ff537872%28v=vs.85%29.aspx Catalog Files and Digital Signatures] (general description)<br />
* [https://msdn.microsoft.com/en-us/library/windows/hardware/ff540177%28v=vs.85%29.aspx Creating a Catalog File for Test-Signing a Driver Package]<br />
* [https://support.microsoft.com/en-us/kb/287547 Microsoft-specific OIDs found in catalog files]<br />
<br />
[[Category:Microsoft]]</div>Felixhttp://fileformats.archiveteam.org/wiki/Security_CatalogSecurity Catalog2015-09-09T18:03:59Z<p>Felix: at this point you may wonder why does it have a separate page</p>
<hr />
<div>{{FormatInfo<br />
| formattype = electronic<br />
| subcat = Security<br />
| extensions = {{ext|cat}}<br />
}}<br />
[[Windows]] '''Security Catalog''' files store digital signatures for any collection of files and are used to verify device drivers.<br />
<br />
Catalog files are ordinary [[PKCS7|PKCS#7 signed-data messages]].<br />
<br />
== Software ==<br />
* [https://msdn.microsoft.com/en-us/library/aa386967.aspx MakeCat] (for creation)<br />
<br />
== Links ==<br />
* [https://msdn.microsoft.com/en-us/library/windows/hardware/ff537872%28v=vs.85%29.aspx Catalog Files and Digital Signatures] (general description)<br />
* [https://msdn.microsoft.com/en-us/library/windows/hardware/ff540177%28v=vs.85%29.aspx Creating a Catalog File for Test-Signing a Driver Package]<br />
<br />
[[Category:Microsoft]]</div>Felixhttp://fileformats.archiveteam.org/wiki/Talk:Quantum_computerTalk:Quantum computer2015-09-07T13:29:02Z<p>Felix: Created page with "I must say, what a load of rubbish. First of all, the word is ''superposition'', not "supposition". Secondly, the description is misleading, suggesting that quantum computers ..."</p>
<hr />
<div>I must say, what a load of rubbish. First of all, the word is ''superposition'', not "supposition". Secondly, the description is misleading, suggesting that quantum computers "try all solutions at once"; quantum computation is conducted by carefully manipulating the quantum state vector so that a later measurement gives the desired result with high probability. Next, a quantum computer is listed here as a "physical file format", which is stretching the definition of both "file" and "format" to the point of meaninglessness. Moreover, given the sheer difficulty of maintaining quantum states and a little something called the no-cloning theorem, nothing which could be meaningfully called long-term quantum information storage should be expected to appear, which means that the topic is simply irrelevant to what this wiki is purportedly set up to document. Lastly, even if it were relevant somehow, I see little value in pages about topics this speculative, especially if they consist of links to vague pop-sci articles, full of errors and misleading metaphors, instead of actual research into the field. — [[User:Felix|felix]] ([[User talk:Felix|talk]]) 13:29, 7 September 2015 (UTC)</div>Felixhttp://fileformats.archiveteam.org/wiki/RIFFRIFF2015-08-27T19:36:26Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Metaformats<br />
|locfdd={{LoCFDD|fdd000025}}<br />
|released=1991<br />
}}<br />
The '''Resource Interchange File Format''' (RIFF), is a wrapper or container format, originally developed by Microsoft and IBM. Formats based on the RIFF container include the widely used [[WAV]] (audio) and [[AVI]] (video) formats.<br />
<br />
== Identification ==<br />
RIFF files begin with the ASCII characters "<code>RIFF</code>".<br />
<br />
== Software ==<br />
* [http://www.schnarff.com/file-formats/riff/ RIFFPad]<br />
<br />
== Links ==<br />
* {{EGFF|riff|Microsoft RIFF File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]<br />
* [http://www.kk.iij4u.or.jp/~kondo/wave/mpidata.txt RIFF document issued jointly by IBM and Microsoft] August 1991<br />
* [[Wikipedia: Resource Interchange File Format]]<br />
<br />
[[Category:Audio and Music]]<br />
[[Category:Graphics]]<br />
[[Category:Video]]<br />
[[Category:RIFF based file formats]]<br />
[[Category:Microsoft]]<br />
[[Category:IBM]]</div>Felixhttp://fileformats.archiveteam.org/wiki/DOS_executable_(.com)DOS executable (.com)2015-08-27T18:56:56Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
| subcat = Executables<br />
| extensions = {{ext|com}}<br />
}}<br />
'''COM''' ("command file") is the native executable format of [[wikipedia:CP/M|CP/M]]. The format was inherited by the DOS family of operating systems; MS-DOS 1.0 introduced [[MS-DOS EXE|MZ]] as a replacement. COM files are raw, flat binaries without relocations; there are no identifying headers or magic numbers, except for a variant introduced in CP/M 3 which contains a 256-byte header.<br />
<br />
On PC computers, COM files are loaded at fixed offset 0x100 in an arbitrary [[wikipedia:x86 memory segmentation#Real mode|real mode memory segment]]. The entry point is located at the start of the file. Many COM files start with a jump instruction (opcode <code>0xe9</code> or <code>0xeb</code>), but this isn't required. Since the executable is limited to a single segment, the maximum size of a COM file is 65280 (0xff00) bytes.<br />
<br />
Some files carrying the <code>.com</code> extension are in fact in the [[MS-DOS EXE|MZ]] format: for example, the <code>COMMAND.COM</code> and <code>EDIT.COM</code> binaries distributed with Windows 95 and later are MZ executables. The DOS loader can detect this and load the file appropriately.<br />
<br />
== References ==<br />
* [[Wikipedia: COM file]]<br />
* [http://www.fileformat.info/format/com/corion.htm Entry] on fileformat.info</div>Felixhttp://fileformats.archiveteam.org/wiki/EBU_STLEBU STL2015-08-27T16:34:10Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
| extensions = {{ext|stl}}<br />
}}<br />
'''EBU STL''' is a subtitle format devised by the [[wikipedia:European Broadcasting Union|European Broadcasting Union]], specified in a standard named '''EBU Tech 3264'''. EBU STL files can be identified by the string {{magic|"STL25.01"}} or {{magic|"STL30.01"}} located three bytes into the file.<br />
<br />
[[EBU Timed Text]] is a successor to this format.<br />
<br />
== External links ==<br />
* [https://tech.ebu.ch/docs/tech/tech3264.pdf EBU Tech 3264]</div>Felixhttp://fileformats.archiveteam.org/wiki/EBU_Timed_TextEBU Timed Text2015-08-27T16:25:55Z<p>Felix: new</p>
<hr />
<div>{{FormatInfo<br />
| type = electronic<br />
}}<br />
'''EBU Timed Text''' ('''EBU-TT''') is a subtitle format developed by the [[wikipedia:European Broadcasting Union|European Broadcasting Union]] as a replacement for [[EBU STL]]. EBU-TT is an [[XML]]-based format.<br />
<br />
== External links ==<br />
* [https://tech.ebu.ch/docs/tech/tech3350.pdf EBU Tech 3350 specification]</div>Felixhttp://fileformats.archiveteam.org/wiki/EBU_STLEBU STL2015-08-27T16:20:43Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
| extensions = {{ext|stl}}<br />
}}<br />
'''EBU STL''' is a subtitle format devised by the [[wikipedia:European Broadcasting Union|European Broadcasting Union]], specified in a standard named '''EBU Tech 3264'''.<br />
<br />
[[EBU Timed Text]] is a successor to this format.<br />
<br />
== External links ==<br />
* [https://tech.ebu.ch/docs/tech/tech3264.pdf EBU Tech 3264]</div>Felixhttp://fileformats.archiveteam.org/wiki/Spruce_subtitle_formatSpruce subtitle format2015-08-27T16:19:11Z<p>Felix: new</p>
<hr />
<div>{{FormatInfo<br />
| extensions = {{ext|stl}}<br />
}}<br />
The '''Spruce subtitle format''' is a relatively simple text-based subtitle format developed by Spruce Technologies. Despite sharing the extension <code>.stl</code>, it's unrelated to the [[EBU STL]] format.<br />
<br />
== External links ==<br />
* [https://web.archive.org/web/20091028173024/http://geocities.com/McPoodle43/DVDMaestro/stl_format.html Format description]<br />
* [https://documentation.apple.com/en/dvdstudiopro/usermanual/chapter_19_section_13.html Description in the DVD Studio Pro manual]</div>Felixhttp://fileformats.archiveteam.org/wiki/EBU_3264EBU 32642015-08-27T16:12:44Z<p>Felix: Redirected page to EBU STL</p>
<hr />
<div>#REDIRECT [[EBU STL]]</div>Felixhttp://fileformats.archiveteam.org/wiki/EBU_Tech_3264EBU Tech 32642015-08-27T16:12:34Z<p>Felix: Redirected page to EBU STL</p>
<hr />
<div>#REDIRECT [[EBU STL]]</div>Felixhttp://fileformats.archiveteam.org/wiki/EBU_STLEBU STL2015-08-27T16:12:19Z<p>Felix: new</p>
<hr />
<div>{{FormatInfo<br />
| extensions = {{ext|stl}}<br />
}}<br />
'''EBU STL''' is a subtitle format devised by the [[wikipedia:European Broadcasting Union|European Broadcasting Union]], specified in a standard named '''EBU Tech 3264'''.<br />
<br />
[[EBU-TT]] is a successor to this format.<br />
<br />
== External links ==<br />
* [https://tech.ebu.ch/docs/tech/tech3264.pdf EBU Tech 3264]</div>Felixhttp://fileformats.archiveteam.org/wiki/MZMZ2015-08-26T08:46:01Z<p>Felix: Redirected page to MS-DOS EXE</p>
<hr />
<div>#REDIRECT [[MS-DOS EXE]]</div>Felixhttp://fileformats.archiveteam.org/wiki/UPS_(binary_patch_format)UPS (binary patch format)2015-06-22T18:50:32Z<p>Felix: I guess this is not applicable after all. This is a complete description.</p>
<hr />
<div>{{FormatInfo<br />
| subcat = Archiving<br />
| extensions = {{ext|ups}}<br />
}}<br />
'''UPS''' is a binary patch format. It was designed as a replacement for [[IPS (binary patch format)|IPS]].<br />
<br />
== Structure ==<br />
A UPS patch file starts with the magic number {{magic|"UPS1"}}, followed by the size of the source file and the size of the destination file, both stored as variable-width integers (see below).<br />
<br />
After that, a series of hunks follows. Each hunk consists of a variable-width integer indicating the number of bytes which should be skipped (copied verbatim from the source file), followed by a block of bytes which should be XORed with the source file to obtain a corresponding block of bytes in the destination file. The XOR block is terminated with a zero byte; the zero byte also counts against the file pointer. If the source and destination file sizes differ, the source file is treated as if it had an infinite number of zero bytes after its actual last byte.<br />
<br />
At the end of the file, there are three CRC32 checksums: of the source file, of the destination file, and of the patch (i.e. everything in the patch before this final checksum itself). Each checksum is stored as a little-endian 32-bit integer.<br />
<br />
=== Variable-width integers ===<br />
The following C function will read a single variable-width integer in UPS format. (Note lack of error checking; this is just a sample.)<br />
<pre><br />
static uintmax_t read_vuint(void) {<br />
uintmax_t result = 0, shift = 0;<br />
<br />
for (;;) {<br />
uint8_t octet = getchar();<br />
if (octet & 0x80) {<br />
result += (octet & 0x7f) << shift;<br />
break;<br />
}<br />
result += (octet | 0x80) << shift;<br />
shift += 7;<br />
}<br />
<br />
return result;<br />
}<br />
</pre><br />
<br />
== External links ==<br />
* [http://sourceforge.net/p/vbam/code/HEAD/tree/trunk/src/common/Patch.cpp?format=raw Patch.cpp in the VBA-M repository] (contains UPS and IPS patchers)<br />
* [http://www.romhacking.net/documents/392/ Specification at romhacking.net]</div>Felixhttp://fileformats.archiveteam.org/wiki/UPS_(binary_patch_format)UPS (binary patch format)2015-06-19T19:01:05Z<p>Felix: huh. only noticed it now.</p>
<hr />
<div>{{FormatInfo<br />
| subcat = Archiving<br />
| extensions = {{ext|ups}}<br />
}}<br />
'''UPS''' is a binary patch format. It was designed as a replacement for [[IPS (binary patch format)|IPS]].<br />
<br />
== Structure ==<br />
The following description is based on the source code of VBA-M; it may be incomplete.<br />
<br />
A UPS patch file starts with the magic number {{magic|"UPS1"}}, followed by the size of the source file and the size of the destination file, both stored as variable-width integers (see below).<br />
<br />
After that, a series of hunks follows. Each hunk consists of a variable-width integer indicating the number of bytes which should be skipped (copied verbatim from the source file), followed by a block of bytes which should be XORed with the source file to obtain a corresponding block of bytes in the destination file. The XOR block is terminated with a zero byte; the zero byte also counts against the file pointer. If the source and destination file sizes differ, the source file is treated as if it had an infinite number of zero bytes after its actual last byte.<br />
<br />
At the end of the file, there are three CRC32 checksums: of the source file, of the destination file, and of the patch (i.e. everything in the patch before this final checksum itself). Each checksum is stored as a little-endian 32-bit integer.<br />
<br />
=== Variable-width integers ===<br />
The following C function will read a single variable-width integer in UPS format. (Note lack of error checking; this is just a sample.)<br />
<pre><br />
static uintmax_t read_vuint(void) {<br />
uintmax_t result = 0, shift = 0;<br />
<br />
for (;;) {<br />
uint8_t octet = getchar();<br />
if (octet & 0x80) {<br />
result += (octet & 0x7f) << shift;<br />
break;<br />
}<br />
result += (octet | 0x80) << shift;<br />
shift += 7;<br />
}<br />
<br />
return result;<br />
}<br />
</pre><br />
<br />
== External links ==<br />
* [http://sourceforge.net/p/vbam/code/HEAD/tree/trunk/src/common/Patch.cpp?format=raw Patch.cpp in the VBA-M repository] (contains UPS and IPS patchers)<br />
* [http://www.romhacking.net/documents/392/ Specification at romhacking.net]</div>Felixhttp://fileformats.archiveteam.org/wiki/UPS_(binary_patch_format)UPS (binary patch format)2015-06-19T11:13:05Z<p>Felix: I wasn't sure how to name this. I don't want any clashes with other potential formats named UPS.</p>
<hr />
<div>{{FormatInfo<br />
| extensions = {{ext|ups}}<br />
}}<br />
'''UPS''' is a binary patch format. It was designed as a replacement for [[IPS (binary patch format)|IPS]].<br />
<br />
== Structure ==<br />
The following description is based on the source code of VBA-M; it may be incomplete.<br />
<br />
A UPS patch file starts with the magic number {{magic|"UPS1"}}, followed by the size of the source file and the size of the destination file, both stored as variable-width integers (see below).<br />
<br />
After that, a series of hunks follows. Each hunk consists of a variable-width integer indicating the number of bytes which should be skipped (copied verbatim from the source file), followed by a block of bytes which should be XORed with the source file to obtain a corresponding block of bytes in the destination file. The XOR block is terminated with a zero byte; the zero byte also counts against the file pointer. If the source and destination file sizes differ, the source file is treated as if it had an infinite number of zero bytes after its actual last byte.<br />
<br />
At the end of the file, there are three CRC32 checksums: of the source file, of the destination file, and of the patch (i.e. everything in the patch before this final checksum itself). Each checksum is stored as a little-endian 32-bit integer.<br />
<br />
=== Variable-width integers ===<br />
The following C function will read a single variable-width integer in UPS format. (Note lack of error checking; this is just a sample.)<br />
<pre><br />
static uintmax_t read_vuint(void) {<br />
uintmax_t result = 0, shift = 0;<br />
<br />
for (;;) {<br />
uint8_t octet = getchar();<br />
if (octet & 0x80) {<br />
result += (octet & 0x7f) << shift;<br />
break;<br />
}<br />
result += (octet | 0x80) << shift;<br />
shift += 7;<br />
}<br />
<br />
return result;<br />
}<br />
</pre><br />
<br />
== External links ==<br />
* [http://sourceforge.net/p/vbam/code/HEAD/tree/trunk/src/common/Patch.cpp?format=raw Patch.cpp in the VBA-M repository] (contains UPS and IPS patchers)</div>Felixhttp://fileformats.archiveteam.org/wiki/JPGJPG2015-06-15T09:03:49Z<p>Felix: Redirected page to JPEG</p>
<hr />
<div>#REDIRECT [[JPEG]]</div>Felixhttp://fileformats.archiveteam.org/wiki/Award_BIOS_logoAward BIOS logo2015-06-15T08:57:43Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|epa}}, {{ext|bmp}}<br />
}}<br />
'''Award BIOS logo''' (also known as '''EPA''' or '''AWBM''') is a family of image formats associated with Award BIOS firmware. These formats are used by those who wish to change the image shown on the boot screen of certain computers. The default image is usually an "Energy Star" logo.<br />
<br />
== Format ==<br />
There are at least two main versions of the format, sometimes called "version 1" and "version 2". Additionally, different versions of the BIOS have different restrictions on the size of the image, etc. There is evidence that different BIOS versions may even render the same file differently.<br />
<br />
=== Version 1 ===<br />
Version 1 images are rendered in text mode, by customizing the character graphics. Consequently, each 8×14 cell of pixels can only use two different colors.<br />
<br />
There is no identifying signature, but most files begin with {{magic|11 06}} or {{magic|11 09}}, based on the usual dimensions of the image in cells.<br />
<br />
{| class="wikitable"<br />
! Name !! Type and length !! Description<br />
|- <br />
| width<br />
| uint8_t (1 byte)<br />
| Image width in character cells. Usually 17 (0x11). Each cell is 8 dots (pixels) wide.<br />
|- <br />
| height<br />
| uint8_t<br />
| Image height in character cells. Usually 6 or 9. Each cell is 14 dots high.<br />
|-<br />
| cmap<br />
| ''width'' × ''height'' bytes<br />
| An array of foreground-background pairs for each character cell. Cells are stored row-by-row, each row stored left-to-right. The less significant nybble corresponds to the foreground colour.<br />
|-<br />
| bitmap<br />
| ''width'' × ''height'' × 14 bytes<br />
| An array of bitmaps for the character cells, stored in the same order as ''cmap''. Each character cell occupies 14 bytes; each byte corresponds to one row of dots, the first byte being the topmost row, and the most significant bit representing the leftmost dot in a row. Bits set to 1 in this bitmap are displayed with the foreground colour of the cell; bits set to 0 are displayed with the background colour.<br />
|-<br />
| logo<br />
| (3 × 2 - 1) × 14 = 70 bytes<br />
| A small (3x2 cells; in pixels, 24x28) monochrome Award Software logo. Stored in the same format as ''bitmap''. The top-left corner of the image is not stored and assumed to be empty. There is no corresponding colour map; the logo is always displayed blue-on-black.<br />
|}<br />
<br />
=== Version 2 ===<br />
Version 2 files begin with a signature of "<code>AWBM</code>". This is a more typical kind of image format, not based on character graphics. It appears in two variants: "planar 4-bit" and "packed 8-bit".<br />
<br />
All values are little-endian.<br />
{| class="wikitable"<br />
! rowspan="2" | Name<br />
! colspan="2" | Length and type<br />
! rowspan="2" | Description<br />
|-<br />
! 4-bit variant<br />
! 8-bit variant<br />
|-<br />
| magic<br />
| colspan="2" | 4 bytes<br />
| Always equal to <code>'A' 'W' 'B' 'M'</code> (i.e. <code>41 57 42 4d</code>)<br />
|-<br />
| width <br />
| colspan="2" | uint16_t<br />
| rowspan="2" | Image width and height in pixels. Common image dimensions include 136x84, 136x126 and 640x480.<br />
|-<br />
| height<br />
| colspan="2" | uint16_t<br />
|-<br />
| data<br />
| ''width'' + (7 - ''width'' mod 8) × ''height'' / 2 bytes<br />
| ''width'' × ''height'' bytes<br />
| The image data; a series of rows of pixels.<br />
* In the 4-bit variant, each row of pixels is stored as four "plane" bitmaps, each storing one bit of the pixel values, starting with the bitmap for the least significant bit. Within each bitmap, pixels are stored left-to-right, and the most significant bit is the leftmost one. If the image width is not a multiple of 8, each "plane" bitmap is separately padded to a multiple of 8 bits.<br />
* In the 8-bit variant, this is simply an array of pixel values, stored row-by-row, left-to-right.<br />
|-<br />
| palmagic<br />
| colspan="2" | 4 bytes<br />
| Always equal to <code>'R' 'G' 'B' ' '</code> (i.e. <code>52 47 42 20</code>). The palette data has been observed to be absent in some files in the 4-bit format; in that case, the [[wikipedia:Color Graphics Adapter#Color palette|CGA palette]] should be assumed.<br />
|-<br />
| paldata<br />
| 16 × 3 bytes<br />
| 256 × 3 bytes<br />
| EGA palette data: an array of triplets of bytes in range 0..63. In the 4-bit variant of the format, the basic colour intensities are normally stored in blue-green-red order, but a few files seem to use red-green-blue order instead ([http://flazh.de/inc/dl.php?dl=epa/polldog16.epa example]). In the 8-bit variant, they are stored as red-green-blue.<br />
|}<br />
<br />
== Specifications ==<br />
* [http://www.icehouse.net/ddawson/awardepa.html Award BIOS logo format (v1)]<br />
<br />
== Software ==<br />
* [[XnView]]<br />
* [[RECOIL]]<br />
* [http://www.blackfiveservices.co.uk/awbmtools.shtml AWBMTools] - Has source code to read and write (some) v2 files<br />
* [http://entropymine.com/deark/ Deark]<br />
<br />
== Sample files ==<br />
* [http://www.flazh.de/en/bios-epa-logos.htm BIOS EPA-Logos]<br />
* http://www.bios-mods.com/logo/index.php<br />
<br />
== Links ==<br />
* [http://www.drunkardswalk.dk/bios/Bioslogo.html Changing the EPA logo in Award BIOS]</div>Felixhttp://fileformats.archiveteam.org/wiki/Plain_textPlain text2015-06-04T08:07:59Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Document<br />
|extensions={{ext|txt}}, {{ext|doc}}, {{noext}}<br />
|mimetypes={{mimetype|text/plain}}<br />
|pronom={{PRONOM|x-fmt/111}}<br />
}}<br />
'''Plain text''' files (also known by the extension TXT) consist of characters encoded sequentially in some particular [[character encoding]]. Plain text files contain no formatting information other than white space characters. Some data formats (usually those intended to be human-readable) are based on plain text; see [[Text-based data]] for some structured formats that are stored in plain text (and hence can be opened in a plain text editor if no more specific program is available).<br />
<br />
Traditionally, [[ASCII]] was used much of the time for maximum interoperability, though many platform-specific character sets were also in use. For non-English text an encoding supporting a broader character repertoire is needed, often [[UTF-8]] nowadays. Note that if the file consists only of 7-bit ASCII characters, the bytes of the file are identical in us-ascii, ISO-8859-1, UTF-8, and a number of other encodings, so such a file can be identified as any of these depending on what is most convenient for a particular application. It is only when characters out of this repertoire are used that encoding-specific details need be considered. Some formats, such as [[HTML]] and [[XML]], provide some sort of escape sequences (such as ampersands used for character references and entities) allowing special characters to be referenced within the document while leaving the document itself entirely ASCII.<br />
<br />
Another point of contention or incompatibility in text-file formats is the conventions for line and paragraph breaks. Depending on what system the file was created on or intended to be viewed on, line breaks may be done as Carriage Return (ASCII 0D hex) and Linefeed (ASCII 0A hex) together (usually in that order, though in rare cases in the opposite order), or just one of those characters alone. Some text viewing or editing programs that are not cross-platform-friendly will really mess up badly in attempting to view/edit files using a different line break convention than the program expects, so you might see lines overwriting one another instead of going to the next line, or peculiar control characters show up within the file, or other strangeness. Files with linefeed alone are often referred to as "UNIX mode" (and the linefeed, in this context, referred to as NL for Newline), while files with carriage return alone are referred to as "Mac mode" (though it's also common in other early platforms such as the Apple II and Commodore 64, and no longer used in current Macs), while the CR+LF format is called "DOS" or "PC" or "Windows" mode (though it was used in various mainframes and network protocols as well).<br />
<br />
Files may also use hard line breaks to keep line length within a fixed number of columns (usually 80, but other values such as 40 or 65 are used sometimes), or just have line breaks at the end of paragraphs and expect systems to word-wrap long lines; encountering files of a different convention than you expect may result in lines running way off to the right of the screen and requiring horizontal scrolling, or else short, choppy lines. Many text editors have a "paragraph reformat" command to bring paragraphs into compliance with your desired conventions.<br />
<br />
Most operating systems include a simple text editor (e.g., Windows Notepad) which can open text files, but many other text editors exist (and computer people sometimes have "holy wars" over which one is best). Some of the common text editors are EMACS, vi, and UltraEdit. In the earlier days of computing, there was less distinction between text editors and word processors than there is now, as word processors generally used a format that was mostly plain text and could even be completely plain text if you refrained from using special embedded commands and features. However, modern word processors such as Microsoft Word default to using program-specific save formats that have little resemblance to plain text, unless you go out of your way to "Save As" .txt. A common "newbie error" is to attempt to create or edit plain text files in such a program, leaving the files as proprietarily-formatted in a way that messes up the operation of other programs that expect to find plain text.<br />
<br />
Creating artwork using text characters is known as [[ASCII Art]], or other variants such as [[ANSI Art]] if special control or escape codes are used in addition to the plain text characters.<br />
<br />
== See also ==<br />
* [[Text file creation software]]<br />
<br />
== Software ==<br />
* [http://textract.readthedocs.org/en/latest/ Textract: extract text from various document formats]<br />
<br />
== Links and References ==<br />
* [http://en.wikipedia.org/wiki/Text_file Text file (Wikipedia)]<br />
* [http://textfiles.com/ textfiles.com: a site full of old text files]<br />
* [http://www.greenwoodsoftware.com/less/index.html Less: a Unix/Linux text file pager (for viewing files)]<br />
* [http://www.webarchive.org.uk/wayback/archive/20120518233003/http://www.openplanetsfoundation.org/blogs/2011-08-16-scenario-discussion-text-files Scenario for discussion: Text files.]<br />
* [http://graydon2.dreamwidth.org/193447.html Always bet on text]</div>Felixhttp://fileformats.archiveteam.org/wiki/Windows_resourceWindows resource2015-06-03T15:35:11Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
| subcat = Executables<br />
| extensions = {{ext|res}}<br />
}}<br />
'''Resources''' are bits of data embedded inside Windows executable files, which may be then read at run time.<br />
<br />
Resources are commonly found in a section named <code>.rsrc</code> inside a [[Portable Executable]] or [[New Executable]] file. Resources may be also found in standalone files with the extension <code>.res</code>.<br />
<br />
== See also ==<br />
* [[Windows resource script]]<br />
<br />
== External links ==<br />
* [[Wikipedia: Resource (Windows)]]</div>Felixhttp://fileformats.archiveteam.org/wiki/PAM_(Portable_Arbitrary_Map)PAM (Portable Arbitrary Map)2015-06-02T11:41:42Z<p>Felix: Felix moved page PAM (Portable Arbitrary Map) to Portable Arbitrary Map</p>
<hr />
<div>#REDIRECT [[Portable Arbitrary Map]]</div>Felixhttp://fileformats.archiveteam.org/wiki/Portable_Arbitrary_MapPortable Arbitrary Map2015-06-02T11:41:42Z<p>Felix: Felix moved page PAM (Portable Arbitrary Map) to Portable Arbitrary Map</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|pam}}<br />
|mimetypes={{mimetype|image/x-portable-arbitrarymap}}<br />
|pronom={{PRONOM|fmt/405}}<br />
|released=2000<br />
}}<br />
'''PAM''' ('''Portable Arbitrary Map''') is one of the native image file formats of the [[Netpbm]] software. It is newer than the other [[Netpbm formats]] (PBM, PGM, PPM). The main advantages of PAM are that it supports transparency, and that new features can be added to it. The main disadvantage is that it is not as widely supported by third-party software.<br />
<br />
== Disambiguation ==<br />
Some sources incorrectly name this format "Portable Any Map". "Portable anymap" is [[Netpbm formats|PNM]], not PAM.<br />
<br />
== See also ==<br />
* [[Netpbm formats]]<br />
<br />
== Identification ==<br />
Files begin with ASCII characters "<code>P7</code>", followed by a newline (<code>0x0A</code>).<br />
<br />
Note that this is a little different from PBM/PGM/PPM format, in which the third byte does not have to be a newline.<br />
<br />
== Specifications ==<br />
* [http://netpbm.sourceforge.net/doc/pam.html PAM Format Specification]<br />
<br />
== Software ==<br />
* [[Netpbm]]<br />
* [[ImageMagick]]<br />
<br />
== Links ==<br />
* [[Wikipedia:PAM graphics format|Wikipedia: PAM graphics format]]</div>Felixhttp://fileformats.archiveteam.org/wiki/MultibootMultiboot2015-06-01T22:39:59Z<p>Felix: new</p>
<hr />
<div>{{FormatInfo<br />
| subcat = Executables<br />
}}<br />
'''Multiboot''' is a standard specifying a file format for bootable kernels and requirements for boot loaders that execute them. The specification is targeted primarily at x86-based PCs.<br />
<br />
Multiboot images are identified by the magic number {{magic|02 B0 AD 1B}} (0x1BADB002) in the first 8192 bytes of the file, followed by a 4-byte bitfield of flags and a checksum. Multiboot files may be simultaneously [[Executable and Linkable Format|ELF]] images.<br />
<br />
A second-generation Multiboot specification is under development.<br />
<br />
== External links ==<br />
* [https://www.gnu.org/software/grub/manual/multiboot/multiboot.html Multiboot specification]</div>Felixhttp://fileformats.archiveteam.org/wiki/OggOgg2015-06-01T22:26:18Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|subcat=Audio and Music<br />
|extensions={{ext|ogg}}, {{ext|ogx}}, {{ext|ogv}}, {{ext|oga}}, {{ext|spx}}, {{ext|ogm}}, {{ext|opus}}<br />
|mimetypes={{mimetype|application/ogg}}<br>{{mimetype|audio/ogg}}<br>{{mimetype|video/ogg}}<br />
|released=1993<br />
}}<br />
'''Ogg''' is a multimedia container format, most commonly used with [[Vorbis]] and other codecs developed by the Xiph.Org Foundation. Ogg files start with the magic number {{magic|"OggS"}}.<br />
<br />
Although the initial specification and IANA registration called for the .ogg extension and application/ogg MIME type, regardless of the type of media in the container, the September 2008 RFC 5334 changed that recommendation and registered audio/ogg and video/ogg MIME types with corresponding .oga and .ogv extensions for content that is primarily audio or video respectively. The .ogx extension was introduced for use with content that incorporated the OGG Skeleton and for which application/ogg remained appropriate. The .ogg extension was grandfathered to refer to OGG audio with a Vorbis audio encoding. The .spx extension should be used for an Ogg audio file using the Speex codec.<br />
<br />
Because OGG formats are free and open-source, not proprietary as many other formats are, they are preferred by many "free-media" projects including Wikipedia, but this causes some issues for people attempting to view/listen to them, since some devices (e.g., Apple's iOS devices) don't support the OGG formats, and others (e.g., Windows PCs) don't have "out-of-the-box" support until you install codecs, plug-ins, or software for it. Some of the proprietary formats have wider support in consumer devices in their default configurations.<br />
<br />
==Streams that can be placed in Ogg==<br />
* Audio<br />
** [[Speex]]<br />
** [[Vorbis]]<br />
** [[FLAC]]<br />
* Video<br />
** [[Dirac]]<br />
** [[Theora]]<br />
* Other<br />
** [[Kate]]<br />
<br />
== Software ==<br />
* [http://www.xiph.org/dshow/ Windows Media Player codecs for some OGG formats]<br />
* [http://xiph.org/quicktime/ OGG QuickTime components (OSX, Windows)]<br />
* [http://www.mirovideoconverter.com/ Miro Video Converter] (watch out for attempts to install annoying toolbars in installer, as is regretfully common these days)<br />
<br />
== Utilities ==<br />
* [http://www.oggconvert.com/ Online audio format converter]<br />
<br />
== References ==<br />
* [http://www.xiph.org/ogg/doc/ OGG documentation from xiph.org]<br />
* [http://www.xiph.org/ogg/doc/rfc3533.txt RFC 3533: The Ogg Encapsulation Format Version 0]<br />
* [http://www.xiph.org/ogg/doc/rfc5334.txt RFC 5334: Ogg Media types] Redefines application/ogg and registers video/ogg and audio/ogg.<br />
* [[Wikipedia: Ogg]]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000026.shtml Ogg File Format, from Library of Congress resource on Sustainability of Digital Formats]<br />
* [http://hardwarebug.org/2010/03/03/ogg-objections/ Ogg objections] and [https://people.xiph.org/~xiphmont/lj-pseudocut/o-response-1.html Chris Montgomery's response]<br />
<br />
[[Category:Video]]</div>Felixhttp://fileformats.archiveteam.org/wiki/OpusOpus2015-06-01T22:25:55Z<p>Felix: </p>
<hr />
<div>:''Not to be confused with the [[Opus-CBCS]] BBS software.''<br />
{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Audio and Music<br />
}}<br />
'''Opus''' is a lossy audio compression format designed by the Internet Engineering Task Force (IETF) for applications requiring high-quality, low-delay audio transmission (e.g. telephony or network music performance). It incorporates technology from Skype's [[SILK]] codec and Xiph.org's [[CELT]] codec.<br />
<br />
Opus-coded audio is usually found inside an [[Ogg]] container (where it carries the extension <code>.opus</code>) or in a [[WebM]] container.<br />
<br />
== Information ==<br />
<br />
* [http://tools.ietf.org/html/rfc6716 RFC 6716 - Definition of the Opus Audio Codec]<br />
* [http://tools.ietf.org/html/draft-ietf-codec-oggopus-00 Ogg Encapsulation for the Opus Audio Codec (draft-ietf-codec-oggopus-00)]<br />
* [http://tools.ietf.org/html/draft-spittka-payload-rtp-opus-03 RTP Payload Format for Opus Speech and Audio Codec (draft-spittka-payload-rtp-opus-03)]<br />
* [http://www.opus-codec.org/presentations/ Opus, the Swiss Army Knife of Audio Codecs] (Presentation at linux.conf.au 2012]<br />
<br />
== Software ==<br />
<br />
The [http://www.opus-codec.org/downloads/ Opus Codec downloads page] contains opus-tools (encode / inspect / decode) .opus files and opusfile, an API for developers.<br />
<br />
[http://www.foobar2000.org/ foobar2000] can play back and encode Opus files (with the [http://www.foobar2000.org/encoderpack Free Encoder Pack]<br />
<br />
== Links ==<br />
<br />
* [http://www.opus-codec.org/testvectors/opus_testvectors.tar.gz Bitstream conformance set]<br />
* [http://people.xiph.org/~greg/opus_testvectors/ The .opus test set] (including intentionally malformed files)<br />
<br />
== See Also ==<br />
<br />
* [[CELT]]<br />
* [[SILK]]</div>Felixhttp://fileformats.archiveteam.org/wiki/OggOgg2015-06-01T22:21:30Z<p>Felix: +</p>
<hr />
<div>{{FormatInfo<br />
|subcat=Audio and Music<br />
|extensions={{ext|ogg}}, {{ext|ogx}}, {{ext|ogv}}, {{ext|oga}}, {{ext|spx}}, {{ext|ogm}}<br />
|mimetypes={{mimetype|application/ogg}}<br>{{mimetype|audio/ogg}}<br>{{mimetype|video/ogg}}<br />
|released=1993<br />
}}<br />
'''Ogg''' is a multimedia container format, most commonly used with [[Vorbis]] and other codecs developed by the Xiph.Org Foundation. Ogg files start with the magic number {{magic|"OggS"}}.<br />
<br />
Although the initial specification and IANA registration called for the .ogg extension and application/ogg MIME type, regardless of the type of media in the container, the September 2008 RFC 5334 changed that recommendation and registered audio/ogg and video/ogg MIME types with corresponding .oga and .ogv extensions for content that is primarily audio or video respectively. The .ogx extension was introduced for use with content that incorporated the OGG Skeleton and for which application/ogg remained appropriate. The .ogg extension was grandfathered to refer to OGG audio with a Vorbis audio encoding. The .spx extension should be used for an Ogg audio file using the Speex codec.<br />
<br />
Because OGG formats are free and open-source, not proprietary as many other formats are, they are preferred by many "free-media" projects including Wikipedia, but this causes some issues for people attempting to view/listen to them, since some devices (e.g., Apple's iOS devices) don't support the OGG formats, and others (e.g., Windows PCs) don't have "out-of-the-box" support until you install codecs, plug-ins, or software for it. Some of the proprietary formats have wider support in consumer devices in their default configurations.<br />
<br />
==Streams that can be placed in Ogg==<br />
* Audio<br />
** [[Speex]]<br />
** [[Vorbis]]<br />
** [[FLAC]]<br />
* Video<br />
** [[Dirac]]<br />
** [[Theora]]<br />
* Other<br />
** [[Kate]]<br />
<br />
== Software ==<br />
* [http://www.xiph.org/dshow/ Windows Media Player codecs for some OGG formats]<br />
* [http://xiph.org/quicktime/ OGG QuickTime components (OSX, Windows)]<br />
* [http://www.mirovideoconverter.com/ Miro Video Converter] (watch out for attempts to install annoying toolbars in installer, as is regretfully common these days)<br />
<br />
== Utilities ==<br />
* [http://www.oggconvert.com/ Online audio format converter]<br />
<br />
== References ==<br />
* [http://www.xiph.org/ogg/doc/ OGG documentation from xiph.org]<br />
* [http://www.xiph.org/ogg/doc/rfc3533.txt RFC 3533: The Ogg Encapsulation Format Version 0]<br />
* [http://www.xiph.org/ogg/doc/rfc5334.txt RFC 5334: Ogg Media types] Redefines application/ogg and registers video/ogg and audio/ogg.<br />
* [[Wikipedia: Ogg]]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000026.shtml Ogg File Format, from Library of Congress resource on Sustainability of Digital Formats]<br />
* [http://hardwarebug.org/2010/03/03/ogg-objections/ Ogg objections] and [https://people.xiph.org/~xiphmont/lj-pseudocut/o-response-1.html Chris Montgomery's response]<br />
<br />
[[Category:Video]]</div>Felixhttp://fileformats.archiveteam.org/wiki/FLACFLAC2015-06-01T22:21:18Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Audio and Music<br />
|extensions={{ext|flac}}<br />
|pronom={{PRONOM|fmt/279}}<br />
}}<br />
'''FLAC''' is a Free Lossless Audio Codec. It can encode audio with a PCM bit resolution up to 32 bits per sample and sampling rates up to 640 kHz. FLAC-encoded audio is usually found either in a native container (which has the extension <code>.flac</code>), or in an [[Ogg]] container (when it's known as OggFLAC).<br />
<br />
The format is open and royalty-free. The reference implementation is cross-platform and dual-licensed, command-line utilities (e.g. encoder, decoder and metadata editor) use GNU GPL and code libraries use BSD.<br />
<br />
FLAC is suitable for archiving for many reasons:<br />
* open format<br />
* support for metadata tagging<br />
* lossless (no generation loss if you need to convert to another format)<br />
* disk size effective (audio is typically reduced to 50-60% of original size)<br />
* data integrity<br />
* error resistant (bit faults are contained within a frame, typically a fraction of a second)<br />
<br />
== Playback ==<br />
=== Hardware ===<br />
<br />
Many home stereo and portable hardware music players support the FLAC format. See the [http://flac.sourceforge.net/links.html FLAC links] page for an up-to-date list.<br />
<br />
=== Software ===<br />
<br />
A number of popular audio players support the FLAC format, including:<br />
<br />
* [http://amarok.kde.org/ Amarok] (cross-platform, open source)<br />
* [http://www.foobar2000.org/ foobar2000] (Windows, non-commercial)<br />
* [http://www.mediamonkey.com/ MediaMonkey] (Windows, commercial)<br />
* [http://www.getsongbird.com/ Songbird] (cross-platform, open source)<br />
* [http://www.videolan.org/vlc/index.html VLC] (cross-platform, open source)<br />
* [http://www.winamp.com/ Winamp] (Windows, commercial)<br />
<br />
For more software products which support FLAC, see the [http://flac.sourceforge.net/links.html FLAC links page]<br />
<br />
== Links ==<br />
* [http://flac.sourceforge.net/ Home of FLAC project]<br />
* [http://flac.sourceforge.net/format.html FLAC format description]<br />
* [https://xiph.org/flac/faq.html FLAC FAQ] (hey, that rhymes!)<br />
* [http://www.dustbury.com/archives/17227 Commentary about Audi car not playing high-bitrate FLACs]<br />
* [http://dericed.com/2013/flac-in-the-archives/ FLAC in the archives]</div>Felixhttp://fileformats.archiveteam.org/wiki/A.outA.out2015-06-01T16:37:24Z<p>Felix: </p>
<hr />
<div>{{DISPLAYTITLE:a.out}}{{FormatInfo<br />
| name = a.out<br />
| subcat = Executables<br />
| extensions = {{noext}}, {{ext|o}}, {{ext|so}}<br />
}}<br />
'''a.out''' is a file format formerly commonly used for executables, object code, shared libraries and core dumps on Unix-like systems. The name "a.out" stands for "assembler output"; it is derived from the default file name for the output of Unix assemblers.<br />
<br />
Most Unix-like systems have replaced the a.out format with [[Executable and Linkable Format|ELF]].<br />
<br />
== Structure ==<br />
An a.out file consists of a single header followed by the executable image's text (code) and data sections, relocation information, a symbol table and a string table (containing symbol names).<br />
<br />
The header starts with an identifier field (denoting whether the file is an executable or a core dump), followed by a series of lengths and addresses. The size and endianness of the header fields is, unfortunately, not very well-specified and architecture-dependent.<br />
<br />
== External links ==<br />
* [[Wikipedia: a.out]]<br />
* [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/uapi/linux/a.out.h a.out.h in the Linux kernel tree]</div>Felixhttp://fileformats.archiveteam.org/wiki/A.outA.out2015-06-01T16:37:00Z<p>Felix: new</p>
<hr />
<div>{{DISPLAYTITLE:a.out}}{{FormatInfo<br />
| subcat = Executables<br />
| extensions = {{noext}}, {{ext|o}}, {{ext|so}}<br />
}}<br />
'''a.out''' is a file format formerly commonly used for executables, object code, shared libraries and core dumps on Unix-like systems. The name "a.out" stands for "assembler output"; it is derived from the default file name for the output of Unix assemblers.<br />
<br />
Most Unix-like systems have replaced the a.out format with [[Executable and Linkable Format|ELF]].<br />
<br />
== Structure ==<br />
An a.out file consists of a single header followed by the executable image's text (code) and data sections, relocation information, a symbol table and a string table (containing symbol names).<br />
<br />
The header starts with an identifier field (denoting whether the file is an executable or a core dump), followed by a series of lengths and addresses. The size and endianness of the header fields is, unfortunately, not very well-specified and architecture-dependent.<br />
<br />
== External links ==<br />
* [[Wikipedia: a.out]]<br />
* [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/uapi/linux/a.out.h a.out.h in the Linux kernel tree]</div>Felixhttp://fileformats.archiveteam.org/wiki/Lock_fileLock file2015-06-01T10:05:28Z<p>Felix: somewhat less naïve description</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Temporary files<br />
|extensions={{ext|lck}}, {{ext|lock}}<br />
}}<br />
'''Lock files''' are used to prevent simultaneous access to a specific file, device, or to prevent an application from being started twice. Lock files are found in Unix-like systems under the directory <code>/var/lock</code> (or more recently, <code>/run/lock</code>).<br />
<br />
A lock file may be empty, but it usually contains the process ID of the program holding the lock.<br />
<br />
Not to be confused with a [[File lock]], although a lock file often has a file lock. <br />
<br />
== External links ==<br />
* [[wikipedia:Lock file|Lock files at Wikipedia]]</div>Felixhttp://fileformats.archiveteam.org/wiki/IPS_(binary_patch_format)IPS (binary patch format)2015-06-01T09:57:38Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
| subcat = Archiving<br />
| extensions = {{ext|ips}}<br />
| released = ≤ 1993<br />
}}<br />
'''IPS''' is a simple format for binary file patches, popular in the ROM hacking community. "IPS" allegedly stands for "International Patching System". The original author of the format is unknown.<br />
<br />
== Structure ==<br />
An IPS file starts with the magic number {{magic|"PATCH"}} (<code>50 41 54 43 48</code>), followed by a series of hunks and an end-of-file marker {{magic|"EOF"}} (<code>45 4f 46</code>). All numerical values are unsigned and stored big-endian.<br />
<br />
Regular hunks consist of a three-byte offset followed by a two-byte length of the payload and the payload itself. Applying the hunk is done by writing the payload at the specified offset.<br />
<br />
RLE hunks have their length field set to zero; in place of a payload there is a two-byte length of the run followed by a single byte indicating the value to be written. Applying the RLE hunk is done by writing this byte the specified number of times at the specified offset.<br />
<br />
As an extension, the end-of-file marker may be followed by a three-byte length to which the resulting file should be truncated. Not every patching program will implement this extension, however.<br />
<br />
== Limitations and pitfalls ==<br />
Due to its simplicity, the IPS format suffers from a number of problems:<br />
* Programs generating IPS files should avoid generating hunks with offset 0x454f46, as the byte encoding of this offset may be misinterpreted as the end-of-file marker. (One way to do it is to generate them with offset 0x454f45 and include the preceding byte.)<br />
* IPS patches are not reversible, unlike e.g. [[unified diff]]s: one cannot recover an unpatched binary from a patch file and a patched binary.<br />
* There are no integrity checks built into the IPS format. The responsibility to ensure that the patch is not corrupted, that the correct file is patched, and that the result of patching is valid falls upon the user.<br />
* The IPS format is next to impossible to extend in a backwards-compatible way; extending the format risks introducing misinterpretations which are often not even detectable by the patching software (given the above).<br />
* IPS patches cannot affect bytes beyond offset 16842750 (0x100fffe = 0xffffff + 0xffff); the IPS patch format may be therefore inadequate for files larger than 16 MiB.<br />
<br />
== External links ==<br />
* [http://romhack.wikia.com/wiki/IPS Format description at ROM Hack City]</div>Felixhttp://fileformats.archiveteam.org/wiki/Executable_and_Linkable_FormatExecutable and Linkable Format2015-06-01T09:01:42Z<p>Felix: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Executables<br />
|pronom={{PRONOM|fmt/688}}, {{PRONOM|fmt/689}}, {{PRONOM|fmt/690}}, {{PRONOM|fmt/691}}<br />
|extensions={{noext}}, {{ext|elf}}, {{ext|o}}, {{ext|so}}, {{ext|mod}}<br />
}}<br />
'''Executable and Linkable Format''' ('''ELF''') is a file format used for executables, shared (dynamically linked) libraries, object code and core dumps.<br />
<br />
[[Wikipedia:Executable and Linkable Format|The Wikipedia article]] has a long list of links to various specifications.<br />
<br />
== Format info ==<br />
* [http://imgur.com/a/MtQZv#0 Graphic showing header structure]<br />
* [http://linux.die.net/man/5/elf elf(5) manual page]<br />
<br />
== Software ==<br />
* [http://www.gnu.org/software/binutils/ GNU Binutils] → objdump<br />
* [http://www.gnu.org/software/binutils/ GNU Binutils] → readelf<br />
<br />
== Links ==<br />
* [https://github.com/corkami/pics/blob/master/ELF101.png ELF101 - a Linux executable walkthrough]</div>Felixhttp://fileformats.archiveteam.org/wiki/Category:File_formats_of_extensionless_filesCategory:File formats of extensionless files2015-06-01T09:00:38Z<p>Felix: Created page with " "</p>
<hr />
<div>[[Category:File formats by extension| ]]</div>Felixhttp://fileformats.archiveteam.org/wiki/Template:NoextTemplate:Noext2015-06-01T08:57:24Z<p>Felix: Created page with "none<includeonly>Category:File formats of extensionless files</includeonly><noinclude> This template displays "none" and categorises the page into [[:Category:File format..."</p>
<hr />
<div>none<includeonly>[[Category:File formats of extensionless files]]</includeonly><noinclude><br />
<br />
This template displays "none" and categorises the page into [[:Category:File formats of extensionless files]].<br />
<br />
It should be put in the <code>|extensions=</code> field of the [[Template:FormatInfo]] template.</div>Felixhttp://fileformats.archiveteam.org/wiki/PFF2PFF22015-06-01T08:43:21Z<p>Felix: +</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Fonts<br />
|extensions={{ext|pf2}}<br />
|released= [http://git.savannah.gnu.org/cgit/grub.git/commit/?id=1e901a7573970dadc8dff64403573cc8d64afb37 2009]<br />
}}<br />
'''PFF2''' is a bitmap font format invented for the GNU GRUB 2 bootloader. It is an [[IFF]]-like format.<br />
<br />
"PFF" stands for "PUPA Font Format"; PUPA was an experimental project which later developed into GRUB 2.<br />
<br />
PFF version 1 was never widely used and was only ever suitable for containing GNU Unifont; it did not support arbitrary font geometries.<br />
<br />
== Identification ==<br />
PFF2 files begin with {{magic|"FILE" 00 00 00 04 "PFF2"}}.<br />
<br />
== Sample files ==<br />
* [https://github.com/anak10thn/ign-bootloader/blob/master/ign-grub2/config/boot/grub/unicode.pf2 unicode.pf2]<br />
<br />
== Links ==<br />
* [http://grub.gibibit.com/New_font_format PFF2 font format]<br />
* [http://git.savannah.gnu.org/cgit/grub.git/plain/util/unifont2pff.rb?id=e507a2c14fcad9bcc9ecc862bfd9a3f45d8cd78d PFF version 1 conversion utility]</div>Felixhttp://fileformats.archiveteam.org/wiki/Gravis_Ultrasound_patchGravis Ultrasound patch2015-05-24T22:34:17Z<p>Felix: new</p>
<hr />
<div>{{FormatInfo<br />
| subcat = Audio and Music<br />
| extensions = {{ext|pat}}<br />
}}<br />
'''Gravis Ultrasound patch''' (GUS patch) files store instrument patches for MIDI synthesisers. GUS patch files start with {{magic|"GF1PATCH"}}.<br />
<br />
== Implementations ==<br />
* [http://sourceforge.net/p/timidity TiMidity++]<br />
* [http://www.mindwerks.net/projects/wildmidi/ WildMIDI]<br />
<br />
== External links ==<br />
* [http://www.onicos.com/staff/iz/formats/guspat.html Partial format description]</div>Felixhttp://fileformats.archiveteam.org/wiki/SoundFont_2.0SoundFont 2.02015-05-24T22:23:20Z<p>Felix: new</p>
<hr />
<div>{{FormatInfo<br />
| subcat = Audio and Music<br />
| extensions = {{ext|sf2}}<br />
}}<br />
'''SoundFont 2.0''' is a format used to store instrument patches for MIDI synthesisers. The SoundFont 2.0 format is based on [[RIFF]]; the RIFF type identifier is {{magic|"sfbk"}}.<br />
<br />
== Example files ==<br />
* http://freepats.zenvoid.org/sf2/acoustic_grand_piano_ydp_20080910.sf2<br />
* ftp://ftp.personalcopy.net/pub/Unison.sf2.gz</div>Felixhttp://fileformats.archiveteam.org/wiki/Game_Boy_SoundGame Boy Sound2015-05-20T18:54:38Z<p>Felix: update gbsplay link</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Audio and Music<br />
|extensions={{ext|gbs}}<br />
}}<br />
<br />
== Description ==<br />
<br />
Game Boy Sound (GBS) is an emulated audio file format, similar to [[SID]] or [[NES Sound Format]]. The files consist of code and data relevant to audio production which has been ripped from a [[GB|Game Boy]] or [[GBC|Game Boy Colour]] ROM image, combined with a header.<br />
<br />
== Information ==<br />
<br />
* [ftp://ftp.modland.com/pub/documents/format_documentation/Gameboy%20Sound%20System%20(.gbs).txt GBS File Specification v1.02]<br />
* [http://web.textfiles.com/games/gbspec.txt Everything You Always Wanted To Know About GAMEBOY but were afraid to ask] - playback of Game Boy Sound files requires emulation of some of the original hardware.<br />
<br />
== Software ==<br />
<br />
=== Playback ===<br />
<br />
* [https://github.com/mmitch/gbsplay gbsplay] (*nix, open source)<br />
* [http://audacious-media-player.org/ Audacious] (cross-platform, open source)<br />
* [http://www.bannister.org/software/ao.htm Audio Overload] (cross-platform)<br />
* [http://www.chipamp.org/ Chipamp] (bundle of Winamp plugins)<br />
* [http://hwm5.gyao.ne.jp/kobarin/ Kobarin Media Player] (Microsoft Windows, Japanese)<br />
* [http://en.wikipedia.org/wiki/MoonShell MoonShell] (Nintendo DS)<br />
* [http://offgao.no-ip.org/program/nezplug++.html NEZplug++] (Winamp / Kobarin plugin)<br />
* [http://shauninman.com/noisees/ Noise Entertainment System] (iPhone / iPod)<br />
<br />
== Links ==<br />
<br />
* [ftp://ftp.modland.com/pub/modules/Gameboy%20Sound%20System/ Example .gbs files]</div>Felixhttp://fileformats.archiveteam.org/wiki/GPTGPT2015-05-17T22:35:18Z<p>Felix: Redirected page to GUID Partition Table</p>
<hr />
<div>#REDIRECT [[GUID Partition Table]]</div>Felixhttp://fileformats.archiveteam.org/wiki/Talk:7-ZipTalk:7-Zip2015-05-17T22:08:23Z<p>Felix: </p>
<hr />
<div>Why is this here? Why is this labelled a "file format"? This isn't an archiving format, it's a piece of software that reads some of them. The native file format of this program already has its own page at [[7z]], as do other formats supported by it. This page is superfluous. [[User:Felix|felix]] ([[User talk:Felix|talk]]) 21:35, 17 May 2015 (UTC)<br />
<br />
:I don't understand your concern, but it is badly categorized. Its primary category should be Software, not Archiving. [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 22:04, 17 May 2015 (UTC)<br />
:: 7-Zip is not a software file format either. It's just one particular program. [[User:Felix|felix]] ([[User talk:Felix|talk]]) 22:08, 17 May 2015 (UTC)</div>Felixhttp://fileformats.archiveteam.org/wiki/IPS_(binary_patch_format)IPS (binary patch format)2015-05-17T22:04:27Z<p>Felix: new</p>
<hr />
<div>{{FormatInfo<br />
| extensions = {{ext|ips}}<br />
}}<br />
'''IPS''' is a simple format for binary file patches.<br />
<br />
== External links ==<br />
* [http://romhack.wikia.com/wiki/IPS Format description at ROM Hack City]</div>Felixhttp://fileformats.archiveteam.org/wiki/Codisk_Audio_FileCodisk Audio File2015-05-17T21:36:24Z<p>Felix: this is a generic MIME type</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Audio and Music<br />
|extensions={{ext|caf}}<br />
}}<br />
The Codisk Audio File format was used in the 1990's for high quality compressed and uncompressed audio by radio automation software "CompuRadio". Recording and playing the files required installation of an advanced audio card (of unknown origin).<br />
<br />
CompuRadio runs on [[MS-DOS]] and was developed in an advanced (unknown) version of [[QBASIC]]. The software was created by the Belgian company Van Rompaey - Devaro bvba, which was renamed Futurex.<br />
<br />
== Resources ==<br />
* [http://www.futurex.be/ Futurex corporate website]</div>Felix