http://fileformats.archiveteam.org/api.php?action=feedcontributions&feedformat=atom&user=Nitro2k01 2026-05-18T21:01:23Z User contributions MediaWiki 1.19.2 http://fileformats.archiveteam.org/wiki/Talk:Graphics 2012-11-12T12:41:22Z

<p>Nitro2k01: </p> <hr /> <div>in this list (http://justsolve.archiveteam.org/index.php/Graphics) JPG is listed as a BMP format. I would argue its not a bit mapped image format. Raster yes, bmp no....<br /> <br /> :Does 'Raster' need to be a separate category then? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 07:36, 12 November 2012 (UTC)<br /> <br /> :Is this distinction (which I understand from a technical point of view, I should add) really relevant enough to warrant a separate category? Perhaps the solution is to rename the whole category to raster graphics formats? --[[User:Nitro2k01|Nitro2k01]] ([[User talk:Nitro2k01|talk]]) 12:41, 12 November 2012 (UTC)</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Talk:Graphics 2012-11-12T12:41:11Z

<p>Nitro2k01: </p> <hr /> <div>in this list (http://justsolve.archiveteam.org/index.php/Graphics) JPG is listed as a BMP format. I would argue its not a bit mapped image format. Raster yes, bmp no....<br /> <br /> :Does 'Raster' need to be a separate category then? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 07:36, 12 November 2012 (UTC)<br /> <br /> :Is this distinction (which I understand from a technical point of view, I should add) really relevant enough to warrant a separate category? Perhaps the solution is to rename the whole category to raster graphics formats?</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/HLP_(WinHelp) 2012-11-08T05:29:35Z

<p>Nitro2k01: </p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |[[Help files]]<br /> | &gt;<br /> |[[HLP (WinHelp)]]<br /> |}<br /> <br /> == Description ==<br /> <br /> WinHelp is a help file format based on [[RTF]] created by Microsoft that exists in several versions and was used in Windows 3.0 up to Windows 95 and NT. Starting with Windows Vista, the format can not be opened without additional software downloads. The format was abandoned to encourage use of the newer [[CHM]] (compiled HTML) help format.<br /> <br /> == See also ==<br /> <br /> * [[CHM]]<br /> <br /> == Resources ==<br /> <br /> * [http://en.wikipedia.org/wiki/WinHelp Wikipedia article]<br /> * [http://www.help-info.de/en/home.htm Resource page for Windows help formats]<br /> * [http://www.help-info.de/en/Help_Info_WinHelp/hw.htm Subpage on the site linked above with a list of links to software and information about the WinHelp format]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/HLP_(WinHelp) 2012-11-08T05:29:25Z

<p>Nitro2k01: Created page with &quot;{| |File Formats | &gt; |Electronic File Formats | &gt; |Help files | &gt; |HLP (WinHelp) |} == Description == WinHelp is a help file format based on RTF created ...&quot;</p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |[[Help files]]<br /> | &gt;<br /> |[[HLP (WinHelp)]]<br /> |}<br /> <br /> == Description ==<br /> <br /> WinHelp is a help file format based on [[RTF]] created by Microsoft that exists in several versions and was used in Windows 3.0 up to Windows 95 and NT. Starting with Windows Vista, the format can not be opened without additional software downloads. The format was abandoned to encourage use of the newer [[CHM]] (compiled HTML) help format.<br /> <br /> == See alson ==<br /> <br /> * [[CHM]]<br /> <br /> == Resources ==<br /> <br /> * [http://en.wikipedia.org/wiki/WinHelp Wikipedia article]<br /> * [http://www.help-info.de/en/home.htm Resource page for Windows help formats]<br /> * [http://www.help-info.de/en/Help_Info_WinHelp/hw.htm Subpage on the site linked above with a list of links to software and information about the WinHelp format]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Help_files 2012-11-08T05:27:31Z

<p>Nitro2k01: </p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |[[Help files]]<br /> |}<br /> <br /> Formats specific to the storage and transmission of Help files.<br /> <br /> * [[HLP (WinHelp)]]<br /> * [[CHM]] (Microsoft Compiled HML Help)<br /> * Whatever weird hypertext format qbasic used<br /> * [[texinfo]]<br /> * [[Man pages]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Help_files 2012-11-08T05:23:52Z

<p>Nitro2k01: </p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |[[Help files]]<br /> |}<br /> <br /> Formats specific to the storage and transmission of Help files.<br /> <br /> * [[HLP (WinHelp)]]<br /> * [[chm]] (Microsoft Compiled HML Help)<br /> * Whatever weird hypertext format qbasic used<br /> * [[texinfo]]<br /> * [[Man pages]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Help_files 2012-11-08T05:18:48Z

<p>Nitro2k01: </p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |Help files<br /> |}<br /> <br /> Formats specific to the storage and transmission of Help files.<br /> <br /> * [[HLP (WinHelp)]]<br /> * [[chm]] (Microsoft Compiled HML Help)<br /> * Whatever weird hypertext format qbasic used<br /> * [[texinfo]]<br /> * [[Man pages]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Development 2012-11-06T02:00:35Z

<p>Nitro2k01: </p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |[[Development]]<br /> |}<br /> <br /> File formats concerning compilers, interpreters, linkers, IDEs, etc.<br /> <br /> See also: [[Source code]], [[Executables]]<br /> <br /> == Project ==<br /> * [[DSP]] (Developer Studio project)<br /> * [[DSW]] (Developer Studio workspace)<br /> * [[NCB]] (Visual Studio no compile browser file)<br /> * [[SLN]] (Visual Studio solution file)<br /> * [[SUO]] (Visual Studio solution options file)<br /> * [[VCPROJ]] (Visual Studio project file)<br /> * [[VDPROJ]] (Visual Studio deployment project file)<br /> <br /> == Compiling ==<br /> * [[BSC]] (Browser code file)<br /> * [[IDB]] (State file)<br /> * [[IDL]] (Interface definition language file)<br /> * [[SBR]] (Visual Studio source browser intermediate file)<br /> <br /> == Debug ==<br /> * [[GDB]] (GNU debugger file)<br /> * [[PDB]] (Program debug database)<br /> * [[Precompiled header file]] (.gch, .pch)<br /> <br /> == Intermediate ==<br /> * [[CLASS]] (Java bytecode)<br /> * [[LIB]] (Static library file)<br /> * [[Object file format]] (.o, .obj)<br /> * [[PYC]] (Python bytecode)<br /> * [[S19]] (SREC)<br /> <br /> == Linking ==<br /> * [[IIK]] (Incremental link file)<br /> * [[MAP]] (Memory map link information)<br /> <br /> == Resource ==<br /> * [[Resource script file]] (.rc, .rc2)</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/ISO_646 2012-11-06T00:21:28Z

<p>Nitro2k01: Only one bracket on each side for external URLs</p> <hr /> <div>ISO 646 was a set of 7-bit encodings designed to internationalize ASCII. The control characters, digits, letters, and some punctuation are the same in all variants, but some other ASCII characters are replaced by characters needed in particular languages. It is equivalent to the [http://www.itu.int/rec/T-REC-T.50-199209-I/en ISO T.50] International Reference Alphabet.</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Macintosh_encodings 2012-11-06T00:21:06Z

<p>Nitro2k01: Only one bracket on each side for external URLs</p> <hr /> <div>The Macintosh &quot;Classic&quot; OS (before OS X) used a number of 8-bit encodings for various locales. These are supersets of ASCII but don't resemble any other standard encoding in the range from 128 to 255. MacSymbol and MacDingbats are graphic character sets that are completely different from ASCII.<br /> <br /> Text encoded with the Macintosh fonts often uses just CR (0X0D) for a line ending, without LF (0X0A).<br /> <br /> Code tables as given by non-Apple sources:<br /> * [http://msdn.microsoft.com/en-us/library/cc195079.aspx MacCE]<br /> * [http://msdn.microsoft.com/en-us/library/cc195078.aspx MacCyrillic]<br /> * [http://msdn.microsoft.com/en-us/library/cc195077.aspx MacGreek]<br /> * [http://www.kreativekorp.com/charset/encoding.php?file=macgujarati.kte MacGujarati]<br /> * [http://www.kreativekorp.com/charset/encoding.php?file=macgurmukhi.kte MacGurMukhi]<br /> * [http://msdn.microsoft.com/en-us/library/cc195080.aspx MacIcelandic]<br /> * [http://msdn.microsoft.com/en-us/library/cc195076.aspx MacRoman]<br /> * [http://www.kreativekorp.com/charset/encoding.php?file=macromanian.kte MacRomania]<br /> * [http://www.kreativekorp.com/charset/encoding.php?file=macsymbol.kte MacSymbol]<br /> * [http://www.kreativekorp.com/charset/encoding.php?file=macthai.kte MacThai]<br /> * [http://msdn.microsoft.com/en-us/library/cc195081.aspx MacTurkish]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/VISCII 2012-11-06T00:19:47Z

<p>Nitro2k01: Only one bracket on each side for external URLs</p> <hr /> <div>VISCII is the Vietnamese Standard Code for Information Interchange. It is an 8-bit encoding which is compatible with the printable code range of ASCII but replaces some control codes (in the range 0-31) with printable characters.<br /> <br /> [http://www.trichlor.org/what-is-viscii.htm VISCII code table]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/MS-DOS_encodings 2012-11-06T00:19:26Z

<p>Nitro2k01: Only one bracket on each side for external URLs</p> <hr /> <div>MS-DOS used a family of 8-bit extensions of ASCII. All code positions 0X20-0XFF are used to represent printable characters. MS-DOS Latin US is still the default encoding built into many PC ROMs. <br /> <br /> * MS-DOS Latin US (Microsoft Code Page 437) [http://msdn.microsoft.com/en-us/library/cc195060.aspx code table]<br /> * MS-DOS Greek (Microsoft Code Page 737) [http://msdn.microsoft.com/en-us/library/cc195062.aspx code table]<br /> * MS-DOS Baltic Rim (Microsoft Code Page 775) [http://msdn.microsoft.com/en-us/library/cc195063.aspx code table]<br /> * MS-DOS Latin-1 (Microsoft Code Page 850) [http://msdn.microsoft.com/en-us/library/cc195064.aspx code table]<br /> * MS-DOS Greek 1 (Microsoft Code Page 851) [http://msdn.microsoft.com/en-us/library/cc195065.aspx code table]<br /> * MS-DOS Latin-2 (Microsoft Code Page 852) [http://msdn.microsoft.com/en-us/library/cc195066.aspx code table]<br /> * MS-DOS Cyrillic (Microsoft Code Page 855 [http://msdn.microsoft.com/en-us/library/cc195067.aspx code table]<br /> * MS-DOS Turkish (Microsoft Code Page 857 [http://msdn.microsoft.com/en-us/library/cc195068.aspx code table]<br /> * MS-DOS Portuguese (Microsoft Code Page 860) [http://msdn.microsoft.com/en-us/library/cc195069.aspx code table]<br /> * MS-DOS Icelandic (Microsoft Code Page 861) [http://msdn.microsoft.com/en-us/library/cc195070.aspx code table]<br /> * MS-DOS Hebrew (Microsoft Code Page 862) [http://msdn.microsoft.com/en-us/library/cc195071.aspx code table]<br /> * MS-DOS French Canada (Microsoft Code Page 863) [http://msdn.microsoft.com/en-us/library/cc195072.aspx code table]<br /> * MS-DOS Arabic Microsoft Code Page 864) [http://www.ascii.ca/cp864.htm code table]<br /> * MS-DOS Nordic (Microsoft Code Page 865) [http://msdn.microsoft.com/en-us/library/cc195073.aspx code table]<br /> * MS-DOS Cyrillic CIS 1 (Microsoft Code Page 866) [http://msdn.microsoft.com/en-us/library/cc195074.aspx code table]<br /> * MS-DOS Greek 2 (Microsoft Code Page 869) [http://msdn.microsoft.com/en-us/library/cc195075.aspx code table]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/ARMSCII 2012-11-06T00:18:08Z

<p>Nitro2k01: Only one bracket on each side for external URLs</p> <hr /> <div>ARMSCII (Armenian Standard Code for Information Interchange) is a family of Armenian character encodings. These have been almost entirely superseded by more recent encodings. The most widely used was the 8-bit ARMSCII-8.<br /> <br /> [http://manpages.ubuntu.com/manpages/lucid/man7/armscii-8.7.html Ubuntu ARMSCII manpage]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Adobe_Standard_Encoding 2012-11-06T00:17:21Z

<p>Nitro2k01: Only one bracket on each side for external URLs</p> <hr /> <div>Adobe Standard Encoding is an 8-bit encoding extended from ASCII, used as the default encoding for many PostScript fonts. Codes 32-126 and 161-251 are used. <br /> <br /> [http://www.ascii.ca/adobestd.htm Adobe Standard Encoding vector]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/UTF-7 2012-11-06T00:16:57Z

<p>Nitro2k01: Only one bracket on each side for external URLs</p> <hr /> <div>UTF-7 is a 7-bit encoding of Unicode which is intended for use in transports (e.g., some email gateways) that cannot safely transfer character codes with the high bit set (0X80 through 0XFF). It is compatible with ASCII except that the character &quot;+&quot; is used as a shift code.<br /> <br /> [http://www.rfc-ref.org/RFC-TEXTS/2152/chapter4.html UTF-7 definition]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Baudot_code 2012-11-06T00:16:33Z

<p>Nitro2k01: Only one bracket on each side for external URLs</p> <hr /> <div>The 5-bit Baudot code was the first widely used binary character encoding. Émile Baudot developed it in 1870 for use in telegraph and teletypewriter applications. In order to accommodate 26 letters, 10 digits, and some punctuation in five bits, it used shift codes to switch between the &quot;letters&quot; set and the &quot;figures&quot; set of characters. This technique is still used in some modern character encodings. Several variants of Baudot, including the CCITT-approved ITA2, were used over the next century.<br /> <br /> [http://nemesis.lonestar.org/reference/telecom/codes/baudot.html Baudot character code reference]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Talk:Audio_and_Music 2012-11-05T22:42:27Z

<p>Nitro2k01: </p> <hr /> <div>I'm not sure how formal this whole effort is in terms of rules / guidelines, but I figure I should take a minute to explain how I intend to organise this page. If anyone has a better system I'm happy to talk about implementing that instead.<br /> <br /> We're obviously going to have massive trouble with ambiguity, given the relatively small number of filenames and the vast number of different kinds of files (to pick just one example, a &quot;.ps&quot; file might be a PostScript document or an Amiga module created by Paul Shields).<br /> <br /> For the Audio section, as you can see, I've picked up from whoever started it and kept on with the format [[FILE EXTENSION]] (Brief Description). For the most part, I intend to create new pages simply at [[FILE EXTENSION]]. When ambiguity arises, I've been turning [[FILE EXTENSION]] into a disambiguation page and creating new pages using [[Brief Description]], then altering the links on the main page to &quot;Brief Description|FILE EXTENSION&quot; - see &quot;PSF&quot; for example.<br /> <br /> Anway, that was boring, but I thought I should explain my thinking.<br /> --[[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 19:56, 28 October 2012 (UTC)<br /> <br /> : I'm functioning as Final Editor on this project (unlike most Wikis), so there's a solid voice and less time spent bickering. Your system makes sense, and that's how we've been doing it for everything. The intent is to use Categories to help people coming in from sideways issues, like &quot;I have a pile of cartridges, what is on these&quot; or &quot;I have a floppy disk, what kind of floppy disk could it possibly be&quot;.<br /> <br /> : --[[User:Jason Scott|Jason Scott]] ([[User talk:Jason Scott|talk]]) 22:46, 28 October 2012 (UTC)<br /> <br /> : Sounds good. Any chance you could knock together some basic editing guidelines for us, Jason? I've been limiting myself to just basic scaffolding at this point, imitating what you had already put up. -- [[User:Rhetoric X|Rhetoric X]] ([[User talk:Rhetoric X|talk]]) 22:50, 28 October 2012 (UTC)<br /> <br /> :: &lt;strike&gt;I was wondering what the feeling is on pulling in extant documents and wikifying them? I've been linking to various file format specs, but I'm concerned that those links have an expiry date. It would be nice to take them and stick them in a sub-page (e.g. S3M/Specification) just so we've got a backup.&lt;/strike&gt; ETA: This has been clearly addressed in the [[FAQ]] --[[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 02:16, 29 October 2012 (UTC)<br /> <br /> Worth noting that there's a separate category for music files, and that many of these formats seem to be more like music files than audio files. [[MOD]] being one example but there are many more.<br /> <br /> : I think this is definitely something that will need sorted shortly - for now, I have literally hundreds more formats to add many of which I am unsure of beyond that they contain audio / music data of some kind. For that reason, I'm going to keep adding them here for consistency - we can always move them to the appropriate section later on. --[[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 20:53, 1 November 2012 (UTC)<br /> <br /> : I agree with the notion that audio files should be separated from music files, eventually. There's room for an even finer categorization, audio stream, sample formats (such as xi, rex and other containing specific metadata), modules (self contained files containing samples), music software documents (predominantly note data, eg mid, or Cubase etc documents), music files for specific hardware, not containing samples (nsf, gbs, sid etc). --[[User:Nitro2k01|Nitro2k01]] ([[User talk:Nitro2k01|talk]]) 22:42, 5 November 2012 (UTC)</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/ROM_and_memory_images 2012-11-05T21:14:32Z

<p>Nitro2k01: </p> <hr /> <div>== Atari game consoles ==<br /> <br /> === Atari 2600 ===<br /> * [[A26]]<br /> * [[BIN]]<br /> * [[ROM]]<br /> <br /> === Atari 5200 ===<br /> * [[A52]]<br /> * [[BIN]]<br /> <br /> === Atari 7800 ===<br /> * [[A78]]<br /> * [[BIN]]<br /> <br /> === Atari Jaguar ===<br /> * [[BIN]]<br /> * [[JAG]]<br /> * [[ROM]]<br /> <br /> === Atari Lynx ===<br /> * [[COM]]<br /> * [[LNX]]<br /> * [[LYX]]<br /> * [[O]]<br /> <br /> == Nintendo game consoles ==<br /> <br /> === NES / Famicom / Famicom Disk System ===<br /> * [[FAM]]<br /> * [[FDS]]<br /> * [[FFE]]<br /> * [[NES]]<br /> * [[Pasofami]] (Needs to be confirmed)<br /> * [[UNF]]<br /> <br /> === Nintendo 64 ===<br /> * [[BIN]] (Binary image)<br /> * [[JAP]] (Region specific)<br /> * [[N64]] (Little Endian (CD64?))<br /> * [[PAL]] (Region specific)<br /> * [[ROM]] (Binary image?)<br /> * [[U64]] (Binary image?)<br /> * [[USA]] (Region specific)<br /> * [[V64]] (Doctor V64 - Little Endian - Byteswapped)<br /> * [[Z64]] (Mr. Backup Z64 - Big Endian)<br /> <br /> === Nintendo DS ===<br /> * [[NDS]]<br /> <br /> === Nintendo Game Boy / Game Boy Color ===<br /> * [[GB]]<br /> * [[GBC]]<br /> * [[GB#SAV|SAV]]<br /> <br /> === Nintendo Game Boy Advance ===<br /> * [[GBA]]<br /> <br /> === Super NES / Super Famicom ===<br /> * [[048]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[058]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[068]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[078]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[AUS]] (Region specific)<br /> * [[BIN]] (Binary image)<br /> * [[BS]] (BS-X Satellaview)<br /> * [[BSX]] (BS-X Satellaview)<br /> * [[DX2]] (Super Wildcard DX2)<br /> * [[EUR]] (Region specific)<br /> * [[FIG]] (Super Pro Fighter)<br /> * [[GD3]] (Bung Game Doctor SF3)<br /> * [[GD7]] (Bung Game Doctor SF7)<br /> * [[JAP]] (Region specific)<br /> * [[JMA]] (nsrt LZMA container)<br /> * [[MGD]] (Multi Game Doctor 2)<br /> * [[MGH]] (Multi Game Hunter)<br /> * [[SF2]] (Professor SF II)<br /> * [[SFC]] (Nintendo)<br /> * [[SMC]] (Super Magicom)<br /> * [[ST]] (Sufami Turbo)<br /> * [[SWC]] (Super Wildcard DX)<br /> * [[UFO]] (Super UFO)<br /> * [[USA]] (Region specific)<br /> <br /> === Nintendo Virtual Boy ===<br /> * [[BIN]]<br /> * [[VB]]<br /> <br /> == Sega gane consoles ==<br /> <br /> === Sega Game Gear ===<br /> * [[GG]]<br /> <br /> === Sega Genesis / Mega Drive / 32X ===<br /> * [[32X]]<br /> * [[BIN]]<br /> * [[GEN]]<br /> * [[MD]]<br /> * [[SMD]]<br /> <br /> === Sega Master System / Mark III ===<br /> * [[SMS]]<br /> <br /> === Sega SG-1000 ===<br /> * [[SG]]<br /> <br /> === Sega SC-3000 ===<br /> * [[SC]]<br /> <br /> == Misc game consoles ==<br /> <br /> === Bally Astrocade ===<br /> * [[BIN]]<br /> <br /> === Bandai Wonderswan / Bandai Wonderswan Color ===<br /> * [[WS]]<br /> * [[WSC]]<br /> <br /> === Casio PV-1000 ===<br /> * [[BIN]]<br /> <br /> === ColecoVision ===<br /> * [[COL]]<br /> * [[CV]]<br /> * [[ROM]]<br /> <br /> === Emerson Arcadia 2001 ===<br /> * [[BIN]]<br /> <br /> === Fairchild Channel F ===<br /> * [[BIN]]<br /> <br /> === Funtech Super A'Can ===<br /> * [[BIN]]<br /> <br /> === GCE Vectrex ===<br /> * [[BIN]]<br /> * [[GAM]]<br /> * [[VEC]]<br /> * [[VEX]]<br /> <br /> === Magnavox Oddysey 2 ===<br /> * [[BIN]]<br /> <br /> === Mattel Intellivision ===<br /> * [[BIN]]<br /> * [[INT]]<br /> * [[ITV]]<br /> * [[ROM]]<br /> <br /> === NEC TurboGrafx-16 / PC Engine ===<br /> * [[PCE]]<br /> <br /> === Neo Geo Pocket / Neo Geo Pocket Color ===<br /> * [[NGP]]<br /> * [[NGC]]<br /> * [[NPC]]<br /> <br /> == Non-game memory formats ==<br /> <br /> === Sharp X68000 ===<br /> * [[2HD]]<br /> * [[88D]]<br /> * [[D88]]<br /> * [[DIM]]<br /> * [[HDM]]<br /> * [[HDS]]<br /> * [[X68]]<br /> * [[XDF]]<br /> <br /> === TI Calculators ===<br /> * [[89u]]<br /> * [[8xu]]<br /> * [[92u]]<br /> * More<br /> <br /> === Container formats ===<br /> * [[SREC]] / S-Record<br /> * [[Intel HEX]]<br /> * [[BIN44]] (very rare, comes from Nortel, ask [[User:Chronomex]])</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Physical_File_Formats 2012-11-05T21:07:25Z

<p>Nitro2k01: Add link to ROM and memory images</p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Physical File Formats]]<br /> |}<br /> <br /> Like the rest, this will be split down further.<br /> <br /> === Traditional ===<br /> * [[Clay tablets]]<br /> * [[Parchment]]<br /> * [[Paper]]<br /> * [[Papyrus]]<br /> * [[Stone carving]]<br /> * [[Quipu]]<br /> <br /> === Capacitive ===<br /> * [[CED]]<br /> * [[VHD]]<br /> <br /> === Electronical ===<br /> * [[Game cartridge]]<br /> * [[ROM and memory images]] — Category page listing specific ROM image formats used for game cartridges and other memory images.<br /> * [[Thumb drive]]<br /> <br /> === Magnetic ===<br /> * [[Audio Cassette]]<br /> * [[Drum memory]]<br /> * [[Floppy disk]]<br /> * [[Hard disk]]<br /> * [[Magnetic stripe card]]<br /> * [[Magnetic tape]]<br /> * [[Magneto-optical drive]] <br /> * [[Videotape]]<br /> * [[Wire recording]]<br /> <br /> === Mechanical ===<br /> ==== Groove media ====<br /> * [[Dictabelt]]<br /> * [[Gramophone record]]<br /> * [[Phonograph cylinder]]<br /> ==== Point based media ====<br /> * [[Music box]]<br /> * [[Piano Rolls]]<br /> * [[Punched card]]<br /> * [[Punched tape]]<br /> <br /> === Optical ===<br /> * [[Bar codes]]<br /> * [[Holography]]<br /> * [[LaserDisc]]<br /> * [[Magneto-optical drive]] <br /> * [[Microform]]<br /> * [[Optical Disc]]<br /> * [[Photographic film]]<br /> * [[Photographic paper]]<br /> * [[Photographic plates]]<br /> * [[Television Electronic Disc]]<br /> * [[Transparency (projection)]]<br /> * [[QR codes]]<br /> <br /> === Misc/unsorted ===<br /> * [[Clothing]] (Doubtful if it qualifies as a file format)<br /> * [[Disk cartridge]] (Ambiguous; specify further)<br /> * [[Thomson CSF system]]<br /> * [[X-ray]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Physical_File_Formats 2012-11-05T21:03:17Z

<p>Nitro2k01: First attempt at a categorization</p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Physical File Formats]]<br /> |}<br /> <br /> Like the rest, this will be split down further.<br /> <br /> === Traditional ===<br /> * [[Clay tablets]]<br /> * [[Parchment]]<br /> * [[Paper]]<br /> * [[Papyrus]]<br /> * [[Stone carving]]<br /> * [[Quipu]]<br /> <br /> === Capacitive ===<br /> * [[CED]]<br /> * [[VHD]]<br /> <br /> === Electronical ===<br /> * [[Game cartridge]]<br /> * [[Thumb drive]]<br /> <br /> === Magnetic ===<br /> * [[Audio Cassette]]<br /> * [[Drum memory]]<br /> * [[Floppy disk]]<br /> * [[Hard disk]]<br /> * [[Magnetic stripe card]]<br /> * [[Magnetic tape]]<br /> * [[Magneto-optical drive]] <br /> * [[Videotape]]<br /> * [[Wire recording]]<br /> <br /> === Mechanical ===<br /> ==== Groove media ====<br /> * [[Dictabelt]]<br /> * [[Gramophone record]]<br /> * [[Phonograph cylinder]]<br /> ==== Point based media ====<br /> * [[Music box]]<br /> * [[Piano Rolls]]<br /> * [[Punched card]]<br /> * [[Punched tape]]<br /> <br /> === Optical ===<br /> * [[Bar codes]]<br /> * [[Holography]]<br /> * [[LaserDisc]]<br /> * [[Magneto-optical drive]] <br /> * [[Microform]]<br /> * [[Optical Disc]]<br /> * [[Photographic film]]<br /> * [[Photographic paper]]<br /> * [[Photographic plates]]<br /> * [[Television Electronic Disc]]<br /> * [[Transparency (projection)]]<br /> * [[QR codes]]<br /> <br /> === Misc/unsorted ===<br /> * [[Clothing]] (Doubtful if it qualifies as a file format)<br /> * [[Disk cartridge]] (Ambiguous; specify further)<br /> * [[Thomson CSF system]]<br /> * [[X-ray]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/GB 2012-11-05T20:32:19Z

<p>Nitro2k01: /* SAV */</p> <hr /> <div>== GB ==<br /> <br /> === Description ===<br /> <br /> A Nintendo Game Boy cartridge contains a ROM chip, for the most times a memory bank controller (MBC) and optionally a battery backed SRAM chip which may contain save game data. Files are typically using the GB file extension, or occasionally GBC if it's a Game Boy Color compatible game or program. <br /> <br /> The file contains a header in the area $0100-$014F. This header contains information about the the program and the cartridge, such as title, ROM size, RAM size, type of MBC, which hardware it supports and checksums. <br /> <br /> === Resources ===<br /> <br /> [http://nocash.emubase.de/pandocs.htm#thecartridgeheader Pan Docs section about the ROM header]<br /> <br /> == SAV ==<br /> <br /> A file containing the information from the SRAM of a Game Boy cartridge is typically given the file extension SAV. The standard sizes for the cartridge SRAM are 512 x 4 bits (for MBC2, see below for details), 2 KiB, 8 KiB, 32 KiB and 128 KiB. The MBC3 chip offers an RTC (real time clock) using a 32768 Hz crystal oscillator. See below for conventions on how to store this data in a sav file.<br /> <br /> === MBC2 battery save format ===<br /> MBC2 ram consists of 256 bytes which are accessible as the low 4 bits of a 512 bytes address range, $a000-$a1ff. The upper 4 bits always read high ($f0).<br /> <br /> BGB saves this as a 512 bytes file, which directly maps to this address area. the upper 4 bits in the file are undefined. other emulators may save 256 bytes, packing the bits. I chose to not do this, because this allows for ambiguity between emulators: which bits go in the low bits/high bits? a 512 bytes file can only be interpreted in one way. I also choose to save in this 512 byte format for compatibility with generic SRAM emulation (not emulating MBC2 correctly)<br /> <br /> I've seen sav files circulating that were saved by an old BGB, possibly version 1.02 (the files are from 2005), here: [http://www.fantasyanime.com/saga/fflsaves.htm final fantasy legend save files]. They are 8192 bytes in size, because the BGB from that time did not accurately implement MBC2 ram. They work in current BGB because it ignores save data past the size it expects.<br /> <br /> (Specification described by beware, author of [[BGB]]. Originally published [http://bgb.bircd.org/mbc2save.html here] and reproduced with permission.)<br /> <br /> === MBC3 RTC save format ===<br /> <br /> The RTC data is appended after the sav file, 44 or 48 bytes. You can detect its presence by the save data being 44 or 48 bytes bigger than the cart's ram size, or 44 or 48 bytes bigger than a multiple of 8192.<br /> <br /> Old VBA (from 2005) saves the 44 bytes version, and can load both the 44 and 48 bytes version.<br /> <br /> VBA-M saves the 48 bytes version, and can *only* load the 48 bytes version.<br /> <br /> One should load both types, and always save the 48 bytes version.<br /> <br /> The data consists entirely of little endian (Intel order) DWORDs. as the registers are bytes, it's in the first byte of the field, the other bytes should always be 0.<br /> <br /> Time is the internal &quot;hidden&quot; version. Latched time is what you're reading from the registers.<br /> <br /> The unix timestamp is UTC seconds since 1970-01-01 00:00, a very common standard on internet. Again, the lowest byte goes first.<br /> <br /> offset size desc<br /> 0 4 time seconds<br /> 4 4 time minutes<br /> 8 4 time hours<br /> 12 4 time days<br /> 16 4 time days high<br /> 20 4 latched time seconds<br /> 24 4 latched time minutes<br /> 28 4 latched time hours<br /> 32 4 latched time days<br /> 36 4 latched time days high<br /> 40 4 unix timestamp when saving<br /> 44 4 0 (probably the high dword of 64 bits time), absent in the 44 bytes version <br /> <br /> (Specification described by beware, author of [[BGB]]. Originally published [http://bgb.bircd.org/rtcsave.html here] and reproduced with permission.)<br /> <br /> <br /> === Little Sound Dj sav format ===<br /> <br /> The Game Boy music creation software Little Sound Dj (LSDj) is using SRAM to store song data. It can use cartridges with between 32 KiB and 128 KiB of SRAM. The lower 32 KiB will always hold the currently active song. If more than 32 KiB of SRAM is present, LSDj can optionally store up to 32 compressed song files in a simple file system in the upper portion of the memory. <br /> <br /> * [http://littlesounddj.wikia.com/wiki/.sav_structure Description of the LSDj song data format]<br /> * [http://littlesounddj.wikia.com/wiki/File_Management_Structure Description of the LSDj compression and file system structure]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/GB 2012-11-05T20:25:10Z

<p>Nitro2k01: TYPOS!</p> <hr /> <div>== GB ==<br /> <br /> === Description ===<br /> <br /> A Nintendo Game Boy cartridge contains a ROM chip, for the most times a memory bank controller (MBC) and optionally a battery backed SRAM chip which may contain save game data. Files are typically using the GB file extension, or occasionally GBC if it's a Game Boy Color compatible game or program. <br /> <br /> The file contains a header in the area $0100-$014F. This header contains information about the the program and the cartridge, such as title, ROM size, RAM size, type of MBC, which hardware it supports and checksums. <br /> <br /> === Resources ===<br /> <br /> [http://nocash.emubase.de/pandocs.htm#thecartridgeheader Pan Docs section about the ROM header]<br /> <br /> == SAV ==<br /> <br /> A file containing the information from the SRAM of a Game Boy cartridge is typically given the file extension SAV. The standard sizes for the cartridge SRAM are 512 x 4 bits (for MBC2, see below for details), 2 KiB, 8 KiB, 32 KiB and 128 KiB. The MBC3 chip offers an RTC (reak time clock) using a 32768 Hz crystal oscillator. See below for conventions on how to store this data in a sav file.<br /> <br /> === MBC2 battery save format ===<br /> MBC2 ram consists of 256 bytes which are accessible as the low 4 bits of a 512 bytes address range, $a000-$a1ff. The upper 4 bits always read high ($f0).<br /> <br /> BGB saves this as a 512 bytes file, which directly maps to this address area. the upper 4 bits in the file are undefined. other emulators may save 256 bytes, packing the bits. I chose to not do this, because this allows for ambiguity between emulators: which bits go in the low bits/high bits? a 512 bytes file can only be interpreted in one way. I also choose to save in this 512 byte format for compatibility with generic SRAM emulation (not emulating MBC2 correctly)<br /> <br /> I've seen sav files circulating that were saved by an old BGB, possibly version 1.02 (the files are from 2005), here: [http://www.fantasyanime.com/saga/fflsaves.htm final fantasy legend save files]. They are 8192 bytes in size, because the BGB from that time did not accurately implement MBC2 ram. They work in current BGB because it ignores save data past the size it expects.<br /> <br /> (Specification described by beware, author of [[BGB]]. Originally published [http://bgb.bircd.org/mbc2save.html here] and reproduced with permission.)<br /> <br /> === MBC3 RTC save format ===<br /> <br /> The RTC data is appended after the sav file, 44 or 48 bytes. You can detect its presence by the save data being 44 or 48 bytes bigger than the cart's ram size, or 44 or 48 bytes bigger than a multiple of 8192.<br /> <br /> Old VBA (from 2005) saves the 44 bytes version, and can load both the 44 and 48 bytes version.<br /> <br /> VBA-M saves the 48 bytes version, and can *only* load the 48 bytes version.<br /> <br /> One should load both types, and always save the 48 bytes version.<br /> <br /> The data consists entirely of little endian (Intel order) DWORDs. as the registers are bytes, it's in the first byte of the field, the other bytes should always be 0.<br /> <br /> Time is the internal &quot;hidden&quot; version. Latched time is what you're reading from the registers.<br /> <br /> The unix timestamp is UTC seconds since 1970-01-01 00:00, a very common standard on internet. Again, the lowest byte goes first.<br /> <br /> offset size desc<br /> 0 4 time seconds<br /> 4 4 time minutes<br /> 8 4 time hours<br /> 12 4 time days<br /> 16 4 time days high<br /> 20 4 latched time seconds<br /> 24 4 latched time minutes<br /> 28 4 latched time hours<br /> 32 4 latched time days<br /> 36 4 latched time days high<br /> 40 4 unix timestamp when saving<br /> 44 4 0 (probably the high dword of 64 bits time), absent in the 44 bytes version <br /> <br /> (Specification described by beware, author of [[BGB]]. Originally published [http://bgb.bircd.org/rtcsave.html here] and reproduced with permission.)<br /> <br /> <br /> === Little Sound Dj sav format ===<br /> <br /> The Game Boy music creation software Little Sound Dj (LSDj) is using SRAM to store song data. It can use cartridges with between 32 KiB and 128 KiB of SRAM. The lower 32 KiB will always hold the currently active song. If more than 32 KiB of SRAM is present, LSDj can optionally store up to 32 compressed song files in a simple file system in the upper portion of the memory. <br /> <br /> * [http://littlesounddj.wikia.com/wiki/.sav_structure Description of the LSDj song data format]<br /> * [http://littlesounddj.wikia.com/wiki/File_Management_Structure Description of the LSDj compression and file system structure]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/ROM_and_memory_images 2012-11-05T20:22:48Z

<p>Nitro2k01: /* Nintendo Game Boy / Game Boy Color */</p> <hr /> <div>== Atari 2600 ==<br /> * [[A26]]<br /> * [[BIN]]<br /> * [[ROM]]<br /> <br /> == Atari 5200 ==<br /> * [[A52]]<br /> * [[BIN]]<br /> <br /> == Atari 7800 ==<br /> * [[A78]]<br /> * [[BIN]]<br /> <br /> == Atari Jaguar ==<br /> * [[BIN]]<br /> * [[JAG]]<br /> * [[ROM]]<br /> <br /> == Atari Lynx ==<br /> * [[COM]]<br /> * [[LNX]]<br /> * [[LYX]]<br /> * [[O]]<br /> <br /> == Bally Astrocade ==<br /> * [[BIN]]<br /> <br /> == Bandai Wonderswan / Bandai Wonderswan Color ==<br /> * [[WS]]<br /> * [[WSC]]<br /> <br /> == Casio PV-1000 ==<br /> * [[BIN]]<br /> <br /> == ColecoVision ==<br /> * [[COL]]<br /> * [[CV]]<br /> * [[ROM]]<br /> <br /> == Emerson Arcadia 2001 ==<br /> * [[BIN]]<br /> <br /> == Fairchild Channel F ==<br /> * [[BIN]]<br /> <br /> == Funtech Super A'Can ==<br /> * [[BIN]]<br /> <br /> == GCE Vectrex ==<br /> * [[BIN]]<br /> * [[GAM]]<br /> * [[VEC]]<br /> * [[VEX]]<br /> <br /> == Magnavox Oddysey 2 ==<br /> * [[BIN]]<br /> <br /> == Mattel Intellivision ==<br /> * [[BIN]]<br /> * [[INT]]<br /> * [[ITV]]<br /> * [[ROM]]<br /> <br /> == NEC TurboGrafx-16 / PC Engine ==<br /> * [[PCE]]<br /> <br /> == NES / Famicom / Famicom Disk System ==<br /> * [[FAM]]<br /> * [[FDS]]<br /> * [[FFE]]<br /> * [[NES]]<br /> * [[Pasofami]] (Needs to be confirmed)<br /> * [[UNF]]<br /> <br /> == Neo Geo Pocket / Neo Geo Pocket Color ==<br /> * [[NGP]]<br /> * [[NGC]]<br /> * [[NPC]]<br /> <br /> == Nintendo 64 ==<br /> * [[BIN]] (Binary image)<br /> * [[JAP]] (Region specific)<br /> * [[N64]] (Little Endian (CD64?))<br /> * [[PAL]] (Region specific)<br /> * [[ROM]] (Binary image?)<br /> * [[U64]] (Binary image?)<br /> * [[USA]] (Region specific)<br /> * [[V64]] (Doctor V64 - Little Endian - Byteswapped)<br /> * [[Z64]] (Mr. Backup Z64 - Big Endian)<br /> <br /> == Nintendo DS ==<br /> * [[NDS]]<br /> <br /> == Nintendo Game Boy / Game Boy Color ==<br /> * [[GB]]<br /> * [[GBC]]<br /> * [[GB#SAV|SAV]]<br /> <br /> == Nintendo Game Boy Advance ==<br /> * [[GBA]]<br /> <br /> == Nintendo Virtual Boy ==<br /> * [[BIN]]<br /> * [[VB]]<br /> <br /> == Sega Game Gear ==<br /> * [[GG]]<br /> <br /> == Sega Genesis / Mega Drive / 32X ==<br /> * [[32X]]<br /> * [[BIN]]<br /> * [[GEN]]<br /> * [[MD]]<br /> * [[SMD]]<br /> <br /> == Sega Master System / Mark III ==<br /> * [[SMS]]<br /> <br /> == Sega SG-1000 ==<br /> * [[SG]]<br /> <br /> == Sega SC-3000 ==<br /> * [[SC]]<br /> <br /> == Sharp X68000 ==<br /> * [[2HD]]<br /> * [[88D]]<br /> * [[D88]]<br /> * [[DIM]]<br /> * [[HDM]]<br /> * [[HDS]]<br /> * [[X68]]<br /> * [[XDF]]<br /> <br /> == Super NES / Super Famicom ==<br /> * [[048]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[058]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[068]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[078]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[AUS]] (Region specific)<br /> * [[BIN]] (Binary image)<br /> * [[BS]] (BS-X Satellaview)<br /> * [[BSX]] (BS-X Satellaview)<br /> * [[DX2]] (Super Wildcard DX2)<br /> * [[EUR]] (Region specific)<br /> * [[FIG]] (Super Pro Fighter)<br /> * [[GD3]] (Bung Game Doctor SF3)<br /> * [[GD7]] (Bung Game Doctor SF7)<br /> * [[JAP]] (Region specific)<br /> * [[JMA]] (nsrt LZMA container)<br /> * [[MGD]] (Multi Game Doctor 2)<br /> * [[MGH]] (Multi Game Hunter)<br /> * [[SF2]] (Professor SF II)<br /> * [[SFC]] (Nintendo)<br /> * [[SMC]] (Super Magicom)<br /> * [[ST]] (Sufami Turbo)<br /> * [[SWC]] (Super Wildcard DX)<br /> * [[UFO]] (Super UFO)<br /> * [[USA]] (Region specific)<br /> <br /> == TI Calculators ==<br /> * [[89u]]<br /> * [[8xu]]<br /> * [[92u]]<br /> * More<br /> <br /> == Container formats ==<br /> * [[SREC]] / S-Record<br /> * [[Intel HEX]]<br /> * [[BIN44]] (very rare, comes from Nortel, ask [[User:Chronomex]])</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/GB 2012-11-05T20:21:01Z

<p>Nitro2k01: Created page with &quot;== GB == === Description === A Nintendo Game Boy cartridge contains a ROM chip, for the most times a memory bank controller (MBC) and optionally a battery backed SRAM chip w...&quot;</p> <hr /> <div>== GB ==<br /> <br /> === Description ===<br /> <br /> A Nintendo Game Boy cartridge contains a ROM chip, for the most times a memory bank controller (MBC) and optionally a battery backed SRAM chip which may contain save game data. Files are typically using the GB file extension, or occasionally GBC if it's a Game Boy Color compatible game or program. <br /> <br /> The file contains a header in the area $0100-$014F. This header contains information about the the program and the cartridge, such as title, ROM size, RAM size, type of MBC, which hardware it supports and checksums. <br /> <br /> === Resources ===<br /> <br /> [http://nocash.emubase.de/pandocs.htm#thecartridgeheader Pan Docs section about the ROM header]<br /> <br /> == SAV ==<br /> <br /> A file containing the information from the SRAM of a Game Boy cartridge is typically given the file extension SAV. The standard sizes for the cartridge SRAN are 512 x 4 bits (for MBC2, see below for details), 2 KiB, 8 KiB, 32 KiB and 128 KiB. The MBC3 chip offers an RTC (reak time clock) using a 32768 Hz crystal oscillator. See below for conventions on how to store this data in a sav file.<br /> <br /> === MBC2 battery save format ===<br /> MMB2 ram consists of 256 bytes which are accessible as the low 4 bits of a 512 bytes address range, $a000-$a1ff. The upper 4 bits always read high ($f0).<br /> <br /> BGB saves this as a 512 bytes file, which directly maps to this address area. the upper 4 bits in the file are undefined. other emulators may save 256 bytes, packing the bits. I chose to not do this, because this allows for ambiguity between emulators: which bits go in the low bits/high bits? a 512 bytes file can only be interpreted in one way. I also choose to save in this 512 byte format for compatibility with generic SRAM emulation (not emulating MBC2 correctly)<br /> <br /> I've seen sav files circulating that were saved by an old BGB, possibly version 1.02 (the files are from 2005), here: [http://www.fantasyanime.com/saga/fflsaves.htm final fantasy legend save files]. They are 8192 bytes in size, because the BGB from that time did not accurately implement MBC2 ram. They work in current BGB because it ignores save data past the size it expects.<br /> <br /> (Specification described by beware, author of [[BGB]]. Originally published [http://bgb.bircd.org/mbc2save.html here] and reproduced with permission.)<br /> <br /> === MBC3 RTC save format ===<br /> <br /> The RTC data is appended after the sav file, 44 or 48 bytes. You can detect its presence by the save data being 44 or 48 bytes bigger than the cart's ram size, or 44 or 48 bytes bigger than a multiple of 8192.<br /> <br /> Old VBA (from 2005) saves the 44 bytes version, and can load both the 44 and 48 bytes version.<br /> <br /> VBA-M saves the 48 bytes version, and can *only* load the 48 bytes version.<br /> <br /> One should load both types, and always save the 48 bytes version.<br /> <br /> The data consists entirely of little endian (Intel order) DWORDs. as the registers are bytes, it's in the first byte of the field, the other bytes should always be 0.<br /> <br /> Time is the internal &quot;hidden&quot; version. Latched time is what you're reading from the registers.<br /> <br /> The unix timestamp is UTC seconds since 1970-01-01 00:00, a very common standard on internet. Again, the lowest byte goes first.<br /> <br /> offset size desc<br /> 0 4 time seconds<br /> 4 4 time minutes<br /> 8 4 time hours<br /> 12 4 time days<br /> 16 4 time days high<br /> 20 4 latched time seconds<br /> 24 4 latched time minutes<br /> 28 4 latched time hours<br /> 32 4 latched time days<br /> 36 4 latched time days high<br /> 40 4 unix timestamp when saving<br /> 44 4 0 (probably the high dword of 64 bits time), absent in the 44 bytes version <br /> <br /> (Specification described by beware, author of [[BGB]]. Originally published [http://bgb.bircd.org/rtcsave.html here] and reproduced with permission.)<br /> <br /> <br /> === Little Sound Dj sav format ===<br /> <br /> The Game Boy music creation software Little Sound Dj (LSDj) is using SRAM to store song data. It can use cartridges with between 32 KiB and 128 KiB of SRAM. The lower 32 KiB will always hold the currently active song. If more than 32 KiB of SRAM is present, LSDj can optionally store up to 32 compressed song files in a simple file system in the upper portion of the memory. <br /> <br /> * [http://littlesounddj.wikia.com/wiki/.sav_structure Description of the LSDj song data format]<br /> * [http://littlesounddj.wikia.com/wiki/File_Management_Structure Description of the LSDj compression and file system structure]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Talk:ROM_Images 2012-11-05T19:32:45Z

<p>Nitro2k01: Nitro2k01 moved page Talk:ROM Images to Talk:ROM and memory images: Changed the name of the article to be inclusive of memory structures that are stored in static RAM.</p> <hr /> <div>#REDIRECT [[Talk:ROM and memory images]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Talk:ROM_and_memory_images 2012-11-05T19:32:44Z

<p>Nitro2k01: Nitro2k01 moved page Talk:ROM Images to Talk:ROM and memory images: Changed the name of the article to be inclusive of memory structures that are stored in static RAM.</p> <hr /> <div>==Categorization==<br /> Many of these formats (the X68000 ones) are in fact disk image formats and should be moved to [[Disk Image Formats]]. Also, I think that all plain ROM files can be moved to a single format, because it really doesn't matter which system a ROM file comes from if it contains only plain data. The only ROM formats that should be listed seperately are those that have some kind of header. Just my 2 cents... --[[User:Darkstar|Darkstar]] ([[User talk:Darkstar|talk]]) 11:08, 5 November 2012 (UTC)<br /> <br /> :I think the best thing to do is to leave the links to the pages, but also link them under [[Disk Image Formats]]. It's reasonable someone would say &quot;I have a pile of amiga disks&quot; or &quot;I have a pile of disks, some of which might be Amiga&quot;. --[[User:Jason Scott|Jason Scott]] ([[User talk:Jason Scott|talk]]) 11:57, 5 November 2012 (UTC)</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/ROM_Images 2012-11-05T19:32:44Z

<p>Nitro2k01: Nitro2k01 moved page ROM Images to ROM and memory images: Changed the name of the article to be inclusive of memory structures that are stored in static RAM.</p> <hr /> <div>#REDIRECT [[ROM and memory images]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/ROM_and_memory_images 2012-11-05T19:32:44Z

<p>Nitro2k01: Nitro2k01 moved page ROM Images to ROM and memory images: Changed the name of the article to be inclusive of memory structures that are stored in static RAM.</p> <hr /> <div>== Atari 2600 ==<br /> * [[A26]]<br /> * [[BIN]]<br /> * [[ROM]]<br /> <br /> == Atari 5200 ==<br /> * [[A52]]<br /> * [[BIN]]<br /> <br /> == Atari 7800 ==<br /> * [[A78]]<br /> * [[BIN]]<br /> <br /> == Atari Jaguar ==<br /> * [[BIN]]<br /> * [[JAG]]<br /> * [[ROM]]<br /> <br /> == Atari Lynx ==<br /> * [[COM]]<br /> * [[LNX]]<br /> * [[LYX]]<br /> * [[O]]<br /> <br /> == Bally Astrocade ==<br /> * [[BIN]]<br /> <br /> == Bandai Wonderswan / Bandai Wonderswan Color ==<br /> * [[WS]]<br /> * [[WSC]]<br /> <br /> == Casio PV-1000 ==<br /> * [[BIN]]<br /> <br /> == ColecoVision ==<br /> * [[COL]]<br /> * [[CV]]<br /> * [[ROM]]<br /> <br /> == Emerson Arcadia 2001 ==<br /> * [[BIN]]<br /> <br /> == Fairchild Channel F ==<br /> * [[BIN]]<br /> <br /> == Funtech Super A'Can ==<br /> * [[BIN]]<br /> <br /> == GCE Vectrex ==<br /> * [[BIN]]<br /> * [[GAM]]<br /> * [[VEC]]<br /> * [[VEX]]<br /> <br /> == Magnavox Oddysey 2 ==<br /> * [[BIN]]<br /> <br /> == Mattel Intellivision ==<br /> * [[BIN]]<br /> * [[INT]]<br /> * [[ITV]]<br /> * [[ROM]]<br /> <br /> == NEC TurboGrafx-16 / PC Engine ==<br /> * [[PCE]]<br /> <br /> == NES / Famicom / Famicom Disk System ==<br /> * [[FAM]]<br /> * [[FDS]]<br /> * [[FFE]]<br /> * [[NES]]<br /> * [[Pasofami]] (Needs to be confirmed)<br /> * [[UNF]]<br /> <br /> == Neo Geo Pocket / Neo Geo Pocket Color ==<br /> * [[NGP]]<br /> * [[NGC]]<br /> * [[NPC]]<br /> <br /> == Nintendo 64 ==<br /> * [[BIN]] (Binary image)<br /> * [[JAP]] (Region specific)<br /> * [[N64]] (Little Endian (CD64?))<br /> * [[PAL]] (Region specific)<br /> * [[ROM]] (Binary image?)<br /> * [[U64]] (Binary image?)<br /> * [[USA]] (Region specific)<br /> * [[V64]] (Doctor V64 - Little Endian - Byteswapped)<br /> * [[Z64]] (Mr. Backup Z64 - Big Endian)<br /> <br /> == Nintendo DS ==<br /> * [[NDS]]<br /> <br /> == Nintendo Game Boy / Game Boy Color ==<br /> * [[GB]]<br /> * [[GBC]]<br /> <br /> == Nintendo Game Boy Advance ==<br /> * [[GBA]]<br /> <br /> == Nintendo Virtual Boy ==<br /> * [[BIN]]<br /> * [[VB]]<br /> <br /> == Sega Game Gear ==<br /> * [[GG]]<br /> <br /> == Sega Genesis / Mega Drive / 32X ==<br /> * [[32X]]<br /> * [[BIN]]<br /> * [[GEN]]<br /> * [[MD]]<br /> * [[SMD]]<br /> <br /> == Sega Master System / Mark III ==<br /> * [[SMS]]<br /> <br /> == Sega SG-1000 ==<br /> * [[SG]]<br /> <br /> == Sega SC-3000 ==<br /> * [[SC]]<br /> <br /> == Sharp X68000 ==<br /> * [[2HD]]<br /> * [[88D]]<br /> * [[D88]]<br /> * [[DIM]]<br /> * [[HDM]]<br /> * [[HDS]]<br /> * [[X68]]<br /> * [[XDF]]<br /> <br /> == Super NES / Super Famicom ==<br /> * [[048]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[058]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[068]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[078]] (Multi Game Doctor 2 - Multi-part file)<br /> * [[AUS]] (Region specific)<br /> * [[BIN]] (Binary image)<br /> * [[BS]] (BS-X Satellaview)<br /> * [[BSX]] (BS-X Satellaview)<br /> * [[DX2]] (Super Wildcard DX2)<br /> * [[EUR]] (Region specific)<br /> * [[FIG]] (Super Pro Fighter)<br /> * [[GD3]] (Bung Game Doctor SF3)<br /> * [[GD7]] (Bung Game Doctor SF7)<br /> * [[JAP]] (Region specific)<br /> * [[JMA]] (nsrt LZMA container)<br /> * [[MGD]] (Multi Game Doctor 2)<br /> * [[MGH]] (Multi Game Hunter)<br /> * [[SF2]] (Professor SF II)<br /> * [[SFC]] (Nintendo)<br /> * [[SMC]] (Super Magicom)<br /> * [[ST]] (Sufami Turbo)<br /> * [[SWC]] (Super Wildcard DX)<br /> * [[UFO]] (Super UFO)<br /> * [[USA]] (Region specific)<br /> <br /> == TI Calculators ==<br /> * [[89u]]<br /> * [[8xu]]<br /> * [[92u]]<br /> * More<br /> <br /> == Container formats ==<br /> * [[SREC]] / S-Record<br /> * [[Intel HEX]]<br /> * [[BIN44]] (very rare, comes from Nortel, ask [[User:Chronomex]])</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/GBC 2012-11-05T19:31:01Z

<p>Nitro2k01: Redirected page to GB</p> <hr /> <div>#REDIRECT [[GB]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Archiving 2012-11-05T18:17:37Z

<p>Nitro2k01: /* Compression only */</p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |[[Compression]]<br /> |}<br /> <br /> (Lossless, for generic data + file archives)<br /> <br /> __NOTOC__<br /> <br /> == Compression + archiving ==<br /> (Multiple files =&gt; 1 file, makes it smaller)<br /> <br /> * [[7ZIP]] (.7z)<br /> * [[ACE]] (.ace)<br /> * [[ARC]] (.arc) <br /> * [[ARC (Web Archiving)]] (.arc.gz)<br /> * [[Apple Disk Image]] (.dmg)<br /> * [[ARJ]] (.arj)<br /> * [[BRU]] (RSX-11M backup)<br /> * [[Cabinet]] (.cab)<br /> * [[DWC]] (.dwc)<br /> * [[IMP]] (.imp)<br /> * [[LHAv]] (.lzh, .lha)<br /> * [[RAR]] (.rar)<br /> * [[Spark]] (.spk)<br /> * [[Stuffit]] (.sit)<br /> * [[Stuffit X]] (.sitx)<br /> * [[WARC]] (.warc.gz)<br /> * [[ZIP]] (.zip)<br /> * [[ZOO]] (.zoo)<br /> <br /> == Archiving only ==<br /> (many files =&gt; 1 file, no compression attempted)<br /> <br /> * [[BinHex]] (.hqx)<br /> * [[LBR]] (.lbr)<br /> * [[Tape Archive]] (.tar)<br /> * [[AR]] file format (.a, .lib) -- Unix Archiver (ar) format as used by various compilers/linkers<br /> * [[CPIO]] (.cpio)<br /> <br /> == Stream compression formats ==<br /> <br /> A stream format takes a stream of bytes, and outputs a different, hopefully smaller, stream of bytes. These compression formats are often used internally in other data structures to compress data, as well as in network protocols, such as http. Used stand-alone, a stream compression format does not offer archiving capability, however in the UNIX doctrine, an archiver like [[tar]] can be combined with an archive format to produce a proper compressed archive.<br /> <br /> * [[BZIP2]] (.bz2)<br /> * [[Crunch]] (.?Z?)<br /> * [[GZIP]] (.gz)<br /> * [[Error Code Modeler]] (.ecm)<br /> * [[LZMA]] (.lzma)<br /> * [[Squeeze/SQ]] (.?Q?)<br /> * [[XZ]] (.xz)<br /> * [[LZIP]] (.lz)<br /> * [[LZOP]] (.lzop)<br /> * [[LZW]] (.Z)<br /> <br /> == Uncategorized ==<br /> <br /> * [[7zX]] (.s7z)<br /> * [[9CDR]] (Amiga FileImploder Clone)<br /> * [[AFA]] (.afa)<br /> * [[ALZip]] (.alz)<br /> * [[APX]] (.apx)<br /> * [[ARCFS]] (ArcFS ArchivePacker)<br /> * [[ArchiveLib]] (GreenLeaf)<br /> * [[BlakHole]] (.bh)<br /> * [[Compact File Set]] (.cfs)<br /> * [[Compact Pro]] (.cpt)<br /> * [[DGCA]] (.dgc)<br /> * [[Disk Archiver]] (.dar)<br /> * [[DiskDoubler]] (.dd)<br /> * [[DMS]] (.dms; Amiga Disk Masher compressed file)<br /> * [[DUPA]] (Amiga FileImploder Clone)<br /> * [[DVDisaster Error Correction File]] (.ecc)<br /> * [[FIMP]] (Amiga FileImploder)<br /> * [[Freeze/Melt]] (.F)<br /> * [[GCA]] (.gca)<br /> * [[HA]] (.ha)<br /> * [[Huffman Encoding]] (.z)<br /> * [[ICE]] (.ice)<br /> * [[IFHC]] (Amiga FileImploder Clone)<br /> * [[IMP]] (Amiga FileImploder)<br /> * [[Inflate]] (.infl)<br /> * [[Jar]] (.j, .jar) =&gt; this is just a renamed zip file with some mandatory files<br /> * [[KGB Archiver]] (.kgb)<br /> * [[KiriKiri]] (.xp3)<br /> * [[LZX]] (.lzx)<br /> * [[LNX]] (.lnx; Lynx archive, used on Commodore 64)<br /> * [[Mozilla Archive]] (.mar)<br /> * [[MS-DOS Compression]] (.??_)<br /> * [[PackIt]] (.pit)<br /> * [[PAK]] (.pak)<br /> * [[PAQ]] (.paq6, .paq7, .paq8)<br /> * [[Parchive File]] (.par, .par2)<br /> * [[PartImage]] (.partimg)<br /> * [[PeaZip]] (.pea)<br /> * [[PerfectCompress]] (.uca)<br /> * [[PIM]] (.pim)<br /> * [[Quadruple D]] (.qda)<br /> * [[RK]] (.rk)<br /> * [[RZIP]] (.rzip)<br /> * [[SCIFER]] (.ba)<br /> * [[Scifer]] (.sen)<br /> * [[Self Dissolving ARChive]] (.sda)<br /> * [[Self-Extracting Archive]] (.sea)<br /> * [[Self-Extracting Archive]] (.sfx)<br /> * [[sfArk]] (.sfark)<br /> * [[Shell Archive]] (.shar)<br /> * [[SQX]] (.sqx)<br /> * [[UHarc]] (.uha)<br /> * [[UltraCompressor II]] (.uc, .uc0, .uc2, .ucn, .ur2, .ue2)<br /> * [[Unix Archiver]] (.ar)<br /> * [[Windows Image]] (.wim)<br /> * [[WinHKI]] (.hki)<br /> * [[WinRK]] (.rk)<br /> * [[XAR]] (.xar)<br /> * [[YZ1]] (.yz1)<br /> * [[Zzip]] (.zz)</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Tar 2012-11-05T18:16:42Z

<p>Nitro2k01: Redirected page to Tape Archive</p> <hr /> <div>#REDIRECT [[Tape Archive]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Tape_Archive 2012-11-05T17:55:03Z

<p>Nitro2k01: Created page with &quot;{| |File Formats | &gt; |Electronic File Formats | &gt; |Compression | &gt; |Tape Archive |} == Description == Tape Archive, or tar, is a traditional UNIX archive...&quot;</p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |[[Compression]]<br /> | &gt;<br /> |[[Tape Archive]]<br /> |}<br /> <br /> == Description ==<br /> <br /> [[Tape Archive]], or tar, is a traditional UNIX archive format, defined in POSIX.1-1988 and later POSIX.1-2001. Its original purpose was to archive files on backup tapes. While tar itself does not offer any compression, it's frequently used together with an stream compression format such as [[GZIP]], [[BZIP2]] and sometimes [[XZ]] to provide file archiving plus compression. The tar command line utility, present in UNIX/Linux systems, offers built-in support for this combined operation by using a modifier such as z (GZip) or j (BZip2). Files compressed this way should have a dual file extension such a .tar.gz or tar.bz2.<br /> <br /> == Examples ==<br /> <br /> Compressing two files into a .tar.gz archive<br /> <br /> tar cvf output.tar.gz inputfile1 inputfile2<br /> <br /> Extracting a .tar.gz archive to the current directory.<br /> <br /> tar xvf output.tar.gz<br /> <br /> == References ==<br /> <br /> [http://linux.die.net/man/1/tar Linux man page for tar]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Editing 2012-11-05T17:32:40Z

<p>Nitro2k01: </p> <hr /> <div>__NOTOC__<br /> These are some general guidelines for editing on this Just Solve the Problem Wiki. Since a wall of text is less likely to get read, these are a relatively small set of hints or suggestions for working on the various entries.<br /> <br /> == Content guidelines ==<br /> <br /> === Enumeration is more important than Beauty ===<br /> <br /> The primary concern is missing out on existing file formats, and having no entry for them. Therefore, the priority should be to track down and acknowledge the existence of these formats, instead of slaving away making a well-known format's entry as beautiful as possible. This priority over beauty also exists when discussing where a file format goes - it is much easier to decide to shift a format from one list to another than to know that format ever existed.<br /> <br /> === Electronic is more important than any other ===<br /> <br /> The primary focus of the Wiki are electronic file formats, as those are the most fleeting and most likely to be non-evident. It's good people are thinking out of the box and adding a range of other formats, but if you're into your tenth hour of describing boat flags and hieroglyphs, perhaps some attention to the more online-oriented entries would be appreciated. <br /> <br /> === What a good Entry should look like ===<br /> <br /> A good entry for a format should ultimately have, where possible: A short description of the format (created anew, not copy-pasted from another source), a link to an example of that format, links to other listings of that format, links to any web pages about that format. Ultimately, it would be good to have code for reading that format, but unless that already exists, then it may be something that comes later.<br /> <br /> === Cross-Linking is your Friend ===<br /> <br /> Use lots of cross-linking in the entries so that related items that aren't necessarily connected otherwise (say, Filesystems to Floppy Disks) get those needed connections. Which leads to the last suggestion.<br /> <br /> === Remember Who This is For ===<br /> <br /> Ultimately, this wiki will be of the best use to people who either know something is a file format, or who are trying to determine what possible format this file could be in. They might know it was made by some application, or that it has a certain file extension, or that just that the file was on a floppy disk from 1983 next to some machine called a PET. When putting together entries, remember these people; they're the ones who need this most.<br /> <br /> == Wiki formatting guidelines/tips and tricks ==<br /> <br /> === Put brackets around linkable words, even in its own article ===<br /> <br /> If you mention a word which has an article, do not hesitate to put brackets around it to make it linkable. MediaWiki will automatically produce the appropriate HTML: a link if mentioned in a different article, or just bold text if self-referential. For example, &lt;nowiki&gt;[[Editing]]&lt;/nowiki&gt; produces the this: [[Editing]] inside this article, but the same wiki markup would produce a link if mentioned in a different article.<br /> <br /> This is especially relevant in breadcrumbs, where the leaf should appropriately be wiki-linked, so the code can be copied without having to manually add &lt;nowiki&gt;[[&lt;/nowiki&gt; and &lt;nowiki&gt;]]&lt;/nowiki&gt; each time you add a new sub item. For example, on the compression page, the markup should appropriately look like this:<br /> <br /> &lt;nowiki&gt;{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |[[Compression]]<br /> |}&lt;/nowiki&gt;<br /> <br /> and not like this:<br /> <br /> &lt;nowiki&gt;{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |Compression<br /> |}&lt;/nowiki&gt;</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Archiving 2012-11-05T17:19:56Z

<p>Nitro2k01: </p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |[[Compression]]<br /> |}<br /> <br /> (Lossless, for generic data + file archives)<br /> <br /> __NOTOC__<br /> <br /> == Compression + archiving ==<br /> (Multiple files =&gt; 1 file, makes it smaller)<br /> <br /> * [[7ZIP]] (.7z)<br /> * [[ACE]] (.ace)<br /> * [[ARC]] (.arc) <br /> * [[ARC (Web Archiving)]] (.arc.gz)<br /> * [[Apple Disk Image]] (.dmg)<br /> * [[ARJ]] (.arj)<br /> * [[BRU]] (RSX-11M backup)<br /> * [[Cabinet]] (.cab)<br /> * [[DWC]] (.dwc)<br /> * [[IMP]] (.imp)<br /> * [[LHAv]] (.lzh, .lha)<br /> * [[RAR]] (.rar)<br /> * [[Spark]] (.spk)<br /> * [[Stuffit]] (.sit)<br /> * [[Stuffit X]] (.sitx)<br /> * [[WARC]] (.warc.gz)<br /> * [[ZIP]] (.zip)<br /> * [[ZOO]] (.zoo)<br /> <br /> == Archiving only ==<br /> (many files =&gt; 1 file, no compression attempted)<br /> <br /> * [[BinHex]] (.hqx)<br /> * [[LBR]] (.lbr)<br /> * [[Tape Archive]] (.tar)<br /> * [[AR]] file format (.a, .lib) -- Unix Archiver (ar) format as used by various compilers/linkers<br /> * [[CPIO]] (.cpio)<br /> <br /> == Compression only ==<br /> (1 file =&gt; 1 file, makes it smaller)<br /> <br /> * [[BZIP2]] (.bz2)<br /> * [[Crunch]] (.?Z?)<br /> * [[GZIP]] (.gz)<br /> * [[Error Code Modeler]] (.ecm)<br /> * [[LZMA]] (.lzma)<br /> * [[Squeeze/SQ]] (.?Q?)<br /> * [[XZ]] (.xz)<br /> * [[LZIP]] (.lz)<br /> * [[LZOP]] (.lzop)<br /> * [[LZW]] (.Z)<br /> <br /> <br /> == Uncategorized ==<br /> <br /> * [[7zX]] (.s7z)<br /> * [[9CDR]] (Amiga FileImploder Clone)<br /> * [[AFA]] (.afa)<br /> * [[ALZip]] (.alz)<br /> * [[APX]] (.apx)<br /> * [[ARCFS]] (ArcFS ArchivePacker)<br /> * [[ArchiveLib]] (GreenLeaf)<br /> * [[BlakHole]] (.bh)<br /> * [[Compact File Set]] (.cfs)<br /> * [[Compact Pro]] (.cpt)<br /> * [[DGCA]] (.dgc)<br /> * [[Disk Archiver]] (.dar)<br /> * [[DiskDoubler]] (.dd)<br /> * [[DMS]] (.dms; Amiga Disk Masher compressed file)<br /> * [[DUPA]] (Amiga FileImploder Clone)<br /> * [[DVDisaster Error Correction File]] (.ecc)<br /> * [[FIMP]] (Amiga FileImploder)<br /> * [[Freeze/Melt]] (.F)<br /> * [[GCA]] (.gca)<br /> * [[HA]] (.ha)<br /> * [[Huffman Encoding]] (.z)<br /> * [[ICE]] (.ice)<br /> * [[IFHC]] (Amiga FileImploder Clone)<br /> * [[IMP]] (Amiga FileImploder)<br /> * [[Inflate]] (.infl)<br /> * [[Jar]] (.j, .jar) =&gt; this is just a renamed zip file with some mandatory files<br /> * [[KGB Archiver]] (.kgb)<br /> * [[KiriKiri]] (.xp3)<br /> * [[LZX]] (.lzx)<br /> * [[LNX]] (.lnx; Lynx archive, used on Commodore 64)<br /> * [[Mozilla Archive]] (.mar)<br /> * [[MS-DOS Compression]] (.??_)<br /> * [[PackIt]] (.pit)<br /> * [[PAK]] (.pak)<br /> * [[PAQ]] (.paq6, .paq7, .paq8)<br /> * [[Parchive File]] (.par, .par2)<br /> * [[PartImage]] (.partimg)<br /> * [[PeaZip]] (.pea)<br /> * [[PerfectCompress]] (.uca)<br /> * [[PIM]] (.pim)<br /> * [[Quadruple D]] (.qda)<br /> * [[RK]] (.rk)<br /> * [[RZIP]] (.rzip)<br /> * [[SCIFER]] (.ba)<br /> * [[Scifer]] (.sen)<br /> * [[Self Dissolving ARChive]] (.sda)<br /> * [[Self-Extracting Archive]] (.sea)<br /> * [[Self-Extracting Archive]] (.sfx)<br /> * [[sfArk]] (.sfark)<br /> * [[Shell Archive]] (.shar)<br /> * [[SQX]] (.sqx)<br /> * [[UHarc]] (.uha)<br /> * [[UltraCompressor II]] (.uc, .uc0, .uc2, .ucn, .ur2, .ue2)<br /> * [[Unix Archiver]] (.ar)<br /> * [[Windows Image]] (.wim)<br /> * [[WinHKI]] (.hki)<br /> * [[WinRK]] (.rk)<br /> * [[XAR]] (.xar)<br /> * [[YZ1]] (.yz1)<br /> * [[Zzip]] (.zz)</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Executables 2012-11-04T00:13:45Z

<p>Nitro2k01: &quot;PE executable&quot; is exe</p> <hr /> <div>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.<br /> <br /> <br /> * [[a.out]]<br /> * [[COM]] — DOS executable<br /> * [[ELF]]<br /> * [[Intel HEX]]<br /> * [[PE executable]] — The format used for exe and dll files in DOS and Windows.</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Executables 2012-11-04T00:13:12Z

<p>Nitro2k01: </p> <hr /> <div>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.<br /> <br /> * [[a.out]]<br /> * [[COM]] — DOS executable<br /> * [[ELF]]<br /> * [[Intel HEX]]<br /> * [[PE executable]] — The format used for exe and dll files in DOS and Windows.</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Talk:Executables 2012-11-03T21:17:25Z

<p>Nitro2k01: </p> <hr /> <div>What category would tokenized BASIC programs (as stored in various types of early personal computer) fit into? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 21:06, 3 November 2012 (UTC)<br /> :Perhaps a new category for source code. Or perhaps serialization. Or both. Nothing really stops a format from appearing in multiple categories. Todo for the future, I have an idea about assigning a format two categories, which might be called &quot;usage type&quot; and &quot;data type&quot;. Usage type might be image format, audio format, or text document format (for example MS Word doc would end up here.) Data type would be stuff like XML based format, proprietary binary, plain text, etc. I need to polish that suggestion. Anyway, I recommend a new category for source code. [[User:Nitro2k01|Nitro2k01]] ([[User talk:Nitro2k01|talk]]) 21:17, 3 November 2012 (UTC)</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Intel_HEX 2012-11-03T20:35:12Z

<p>Nitro2k01: Created page with &quot;Intel HEX is a format that stores binary data as hexadecimal digits in ASCII. It's often used for simple memory images, for example data meant to be stored on EEPROM chips, an...&quot;</p> <hr /> <div>Intel HEX is a format that stores binary data as hexadecimal digits in ASCII. It's often used for simple memory images, for example data meant to be stored on EEPROM chips, and microcontroller code.<br /> <br /> http://en.wikipedia.org/wiki/Intel_HEX</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Electronic_File_Formats 2012-11-03T20:26:29Z

<p>Nitro2k01: </p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |Electronic File Formats<br /> |}<br /> <br /> Formats based on electronic/online media.<br /> <br /> * [[3D and CAD/CAM Models]]<br /> * [[Address books and contacts]]<br /> * [[Audio]]<br /> * [[Bibliographic data]] - Catalogues, Finding aids and Reference lists<br /> * [[Calendars]]<br /> * [[Cameras and Digital Image Sensors]]<br /> * [[Character Encoding]]<br /> * [[Compression]]<br /> * [[Database]]<br /> * [[Disk Image Formats]]<br /> * [[Document]] - Word Processing, Spreadsheet, Presentation<br /> * [[E-Mail, newsgroups, and forums]]<br /> * [[Electronic Publishing formats]]<br /> * [[Encryption]]<br /> * [[Executables]]<br /> * '''[[Filesystem]]''' - File systems are the protocols by which multiple files are stored and organized by an operating system<br /> * [[Genealogical data]]<br /> * [[Geospatial]]<br /> * [[Graphics]]<br /> * [[Help files]]<br /> * [[Interactive Fiction]]<br /> * [[Machine Embroidery]]<br /> * [[Mind maps, Topic maps etc]]<br /> * [[Music]] - for musical notation and musical-instrument control, rather than audio files<br /> * [[Personal Digital Assistant formats]]<br /> * [[Saved Games]]<br /> * [[Scientific Data formats]]<br /> * [[Security]]<br /> * [[Serialization]]<br /> * [[Text-based data]]<br /> * [[Video]]<br /> * [[Web]]<br /> <br /> === Temporary Categories ===<br /> <br /> As the ontology grows quickly, some formats and concepts of formats are harder to easily classify - they'll temporarily be here during a quick debate.<br /> <br /> * [[Binary Data]] (&lt;- Move some or all of these to other categories)<br /> * [[Resource Fork]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Executables 2012-11-03T20:25:45Z

<p>Nitro2k01: Created page, added a few formats</p> <hr /> <div>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.<br /> <br /> * [[a.out]]<br /> * [[COM]] — DOS executable<br /> * [[ELF]]<br /> * [[Intel HEX]]<br /> * [[PE executable]] — The format used for exe and dll files in DOS and Windows.</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Filesystem 2012-11-03T20:23:41Z

<p>Nitro2k01: dashdash -&gt; emdash</p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |[[Electronic File Formats]]<br /> | &gt;<br /> |Filesystem<br /> |}<br /> <br /> Filesystems are [[Electronic_File_Formats|Electronic Formats]] that are a prerequisite to being able to read any file off a digital medium — you have to be able to mount the filesystem, and thus read it, in order to be able to read a file.<br /> <br /> * [[ADFS]] (Acorn MOS, RISC OS)<br /> * [[BFS]] (BeOS)<br /> * [[btrfs]]<br /> * [[CP/M file system]]<br /> * [[exFAT]] (Microsoft, for flash memory)<br /> * [[ext]] (developed for Linux, previously used MINIX fs)<br /> * [[ext2]], [[ext3]], [[ext4]] (these are all just variants of each other)<br /> * [[FAT12]]<br /> * [[FAT16]]<br /> * [[FAT32]]<br /> * [[FFS]] (Amiga Fast File System)<br /> * [[Files-11]] (VMS)<br /> * [[Fossil]] (Plan 9)<br /> * [[HAMMER]] (DragonflyBSD)<br /> * [[HFS]]<br /> * [[HFS+]]<br /> * [[HPFS]] (OS/2 native file system)<br /> * [[ISO 9660]]<br /> * [[JFFS2]]<br /> * [[MDR]] (audio instrument format close to MSDOS)<br /> * [[MFS]] (ancient Macintosh filesystem)<br /> * [[MINIX file system]]<br /> * [[NTFS]]<br /> * [[QFS]]<br /> * [[ReiserFS]]<br /> ** [[Reiser4]]<br /> * [[squashfs]]<br /> * [[UDF]]<br /> * [[UFS]] (Unix Files System, Solaris and BSD)<br /> ** [[UFS2]]<br /> * [[VxFS]]<br /> * [[WAFL]] (NetApp's commercial file system)<br /> * [[Xiafs]] (Linux, dropped in favour of ext2)<br /> * [[XFS]] (SGI)<br /> * [[YAFFS]]<br /> * [[ZFS]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Electronic_File_Formats 2012-11-03T20:17:20Z

<p>Nitro2k01: </p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |Electronic File Formats<br /> |}<br /> <br /> Formats based on electronic/online media.<br /> <br /> * [[3D and CAD/CAM Models]]<br /> * [[Address books and contacts]]<br /> * [[Audio]]<br /> * [[Bibliographic data]] - Catalogues, Finding aids and Reference lists<br /> * [[Binary Data]] (&lt;- Move some or all of these to other categories)<br /> * [[Calendars]]<br /> * [[Cameras and Digital Image Sensors]]<br /> * [[Character Encoding]]<br /> * [[Compression]]<br /> * [[Database]]<br /> * [[Disk Image Formats]]<br /> * [[Document]] - Word Processing, Spreadsheet, Presentation<br /> * [[E-Mail, newsgroups, and forums]]<br /> * [[Electronic Publishing formats]]<br /> * [[Encryption]]<br /> * [[Executables]]<br /> * '''[[Filesystem]]''' - File systems are the protocols by which multiple files are stored and organized by an operating system<br /> * [[Genealogical data]]<br /> * [[Geospatial]]<br /> * [[Graphics]]<br /> * [[Help files]]<br /> * [[Interactive Fiction]]<br /> * [[Machine Embroidery]]<br /> * [[Mind maps, Topic maps etc]]<br /> * [[Music]] - for musical notation and musical-instrument control, rather than audio files<br /> * [[Personal Digital Assistant formats]]<br /> * [[Saved Games]]<br /> * [[Scientific Data formats]]<br /> * [[Security]]<br /> * [[Serialization]]<br /> * [[Text-based data]]<br /> * [[Video]]<br /> * [[Web]]<br /> <br /> === Temporary Categories ===<br /> <br /> As the ontology grows quickly, some formats and concepts of formats are harder to easily classify - they'll temporarily be here during a quick debate.<br /> <br /> * [[Resource Fork]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Electronic_File_Formats 2012-11-03T20:16:25Z

<p>Nitro2k01: </p> <hr /> <div>{|<br /> |[[File Formats]]<br /> | &gt;<br /> |Electronic File Formats<br /> |}<br /> <br /> Formats based on electronic/online media.<br /> <br /> * [[3D and CAD/CAM Models]]<br /> * [[Address books and contacts]]<br /> * [[Audio]]<br /> * [[Bibliographic data]] - Catalogues, Finding aids and Reference lists<br /> * [[Binary Data]] (&lt;- Move some or all of these to other categories)<br /> * [[Calendars]]<br /> * [[Cameras and Digital Image Sensors]]<br /> * [[Character Encoding]]<br /> * [[Compression]]<br /> * [[Database]]<br /> * [[Disk Image Formats]]<br /> * [[Document]] - Word Processing, Spreadsheet, Presentation<br /> * [[E-Mail, newsgroups, and forums]]<br /> * [[Electronic Publishing formats]]<br /> * [[Encryption]]<br /> * '''[[Filesystem]]''' - File systems are the protocols by which multiple files are stored and organized by an operating system<br /> * [[Genealogical data]]<br /> * [[Geospatial]]<br /> * [[Graphics]]<br /> * [[Help files]]<br /> * [[Interactive Fiction]]<br /> * [[Machine Code]]<br /> * [[Machine Embroidery]]<br /> * [[Mind maps, Topic maps etc]]<br /> * [[Music]] - for musical notation and musical-instrument control, rather than audio files<br /> * [[Personal Digital Assistant formats]]<br /> * [[Saved Games]]<br /> * [[Scientific Data formats]]<br /> * [[Security]]<br /> * [[Serialization]]<br /> * [[Text-based data]]<br /> * [[Video]]<br /> * [[Web]]<br /> <br /> === Temporary Categories ===<br /> <br /> As the ontology grows quickly, some formats and concepts of formats are harder to easily classify - they'll temporarily be here during a quick debate.<br /> <br /> * [[Resource Fork]]</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/JustSolve:To_Do 2012-11-03T00:34:21Z

<p>Nitro2k01: /* Stuff That Would Be Good To Do */</p> <hr /> <div>== Stuff That Would Be Good To Do ==<br /> <br /> These are tasks large and small that could be good to do. If you think you want one, sign your name to it (with a timestamp) and get cracking. If you fall idle, you'll be pinged and maybe overtaken. Or you'll finish it and be a hero!<br /> <br /> * '''Just keep adding new formats and sub-headings'''. Right now the priority is to mostly get a good skeleton going. As we go, we're cleaning up hierarchies (especially when there's duplicates in two different sub-trees), but for the moment, we're trying to expand out in every direction.<br /> <br /> * '''The Navigation of the Various Heirarchies''' is sub-par and could use beautification. Some nice layout for FIRSTLEVEL =&gt; SECONDLEVEL =&gt; ITEM would be good.<br /> ** Would this work more easily if we switched to using [http://www.mediawiki.org/wiki/Help:Categories Categories] for the main hierarchy? Does the UI autogenerate? Would it be okay? Anyone mind if I try it out? [[User:AndyJackson|AndyJackson]] ([[User talk:AndyJackson|talk]]) 15:47, 29 October 2012 (UTC)<br /> *** I would like to keep the direct-linked hierarchy we are building and encourage that people build massive amounts of categories to allow cross-discipline linking that otherwise would be confusing to others. --[[User:Jason Scott|Jason Scott]] ([[User talk:Jason Scott|talk]]) 21:34, 29 October 2012 (UTC)<br /> **** Good plan - I've started adding some simple navigation. [[User:AndyJackson|AndyJackson]] ([[User talk:AndyJackson|talk]]) 00:07, 30 October 2012 (UTC)<br /> <br /> * '''Rank articles by completeness.''' Highlight articles that are excellent, as well as those that are &quot;decent&quot;, (above stub level). This is probably best done with categories, which will make all pages appear in a central place based on the categorization. Actually, categories are useful for a lot of stuff. TBC... [[User:Nitro2k01|Nitro2k01]] ([[User talk:Nitro2k01|talk]]) 00:34, 3 November 2012 (UTC)</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Template:CenterGreyBox 2012-11-03T00:22:59Z

<p>Nitro2k01: </p> <hr /> <div>&lt;center&gt;<br /> {| style=&quot;border:solid #111100 1px; margin-top:1.2em; background-color:#DFDDDF; padding:5px 5px 5px 5px; text-align:center;width:700px;&quot;<br /> |{{GreyTitle|{{{1}}}}}<br /> {{{2}}}<br /> |}&lt;/center&gt;</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Template:GreyTitle 2012-11-03T00:22:28Z

<p>Nitro2k01: Created page with &quot;&lt;SPAN style=&quot;color:#334433;font-weight:bold;font-size:18pt&quot;&gt;{{{1}}}&lt;/SPAN&gt;&quot;</p> <hr /> <div>&lt;SPAN style=&quot;color:#334433;font-weight:bold;font-size:18pt&quot;&gt;{{{1}}}&lt;/SPAN&gt;</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Template:CenterGreyBox 2012-11-03T00:14:23Z

<p>Nitro2k01: </p> <hr /> <div>&lt;center&gt;<br /> {| style=&quot;border:solid #111100 1px; margin-top:1.2em; background-color:#DFDDDF; padding:5px 5px 5px 5px; text-align:center;width:700px;&quot;<br /> |&lt;SPAN style=&quot;color:#334433;font-weight:bold;font-size:18pt&quot;&gt;{{{1}}}&lt;/SPAN&gt;<br /> {{{2}}}<br /> |}&lt;/center&gt;</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/Template:CenterGreyBox 2012-11-03T00:02:04Z

<p>Nitro2k01: Created page with &quot;&lt;center&gt; {| style=&quot;border:solid #111100 1px; margin-top:1.2em; background-color:#DFDDDF; padding:5px 5px 5px 5px; text-align:center;width:700px;&quot; |&lt;SPAN style=&quot;color:#334433;f...&quot;</p> <hr /> <div>&lt;center&gt;<br /> {| style=&quot;border:solid #111100 1px; margin-top:1.2em; background-color:#DFDDDF; padding:5px 5px 5px 5px; text-align:center;width:700px;&quot;<br /> |&lt;SPAN style=&quot;color:#334433;font-weight:bold;font-size:18pt&quot;&gt;{{{1}}}&lt;/SPAN&gt;<br /> <br /> {{{2}}}<br /> <br /> |}&lt;/center&gt;</div>

Nitro2k01 http://fileformats.archiveteam.org/wiki/FAQ 2012-11-02T23:24:29Z

<p>Nitro2k01: Changed formatting of titles</p> <hr /> <div>Here are some answers to either frequently asked questions or to important aspects of this project; the ground rules.<br /> <br /> ==What is the purpose of this Wiki and this project?==<br /> <br /> The purpose of this wiki is to &quot;Solve the File Format Problem&quot;.<br /> <br /> The File Format Problem in this context is that over the last century, many types of electronic information have been presented in formats that are non-intuitive and subject to the rapidly-shifting interests of what is newest and best. As a result, thousands of programs, documents, images and binary files are in danger of being unreadable to later generations as no readily available information about accessing them is to be found. Various projects have been launched in the last 20 years to deal with this problem, but they all lack a groundswell of directed volunteers working to once and for all get all the disparate information into one place and easily referenced by all. This is the goal of this project.<br /> <br /> The project will have 30 days of running, from November 1st to November 30th, 2012. All are invited to register and contribute. At the end of the 30 days, the project may continue by volunteers, but the goal is to have a massive bulk of knowledge in one place for all to use and incorporate into other similar directories and sites, providing a needed resource for generations to come.<br /> <br /> ==What IS a file format, anyway?==<br /> <br /> That is an excellent, excellent question.<br /> <br /> For the purposes of this Wiki, a file format is the description of any self-contained information. While some formats are self-evident, many are more obscure references to pre-known information, or collections of bytes and items that can be misleading or hard to decipher. File formats can also be embedded in each other - on this wiki, each format gets its own entry. For example, a [[JPG]] image file might be on a [[FAT]] filesystem on a [[floppy disk]]. All of these get individual entries.<br /> <br /> The nature of such a wide description is that some entries will skirt the edge of reason, or a file format will not be clear as to where it should be filed. This is understandable and will be dealt with, but the most important priority is to declare the file format exists, and then link it from the locations it should be at.<br /> <br /> ==Some of these classifications (Organic, for example) are strange. Who'd want that?==<br /> <br /> Part of the goals of this project are to extend out past the more limited realms of similar projects. Because of funding, direction, and preference, the multiple other sites are usually focused on a sub-set of all potential file formats, because who'd have time to deal with them? If this project gains more and more contributors, then there's not much more effort required to go after items on the fuzzy lines of what constitutes file formats. Or, for that matter, discern the reason they're file formats. So we have many items like [[DNA]] and [[Piano Rolls]] that can also be included and worked on. Priority-wise, however, it's probably best to stick with electronic file forms, especially ones lacking any links or documentation - they could really use your efforts.<br /> <br /> ==Why is it public domain?==<br /> <br /> Making the information here public domain provides the most flexibility for institutions and individuals who want to benefit from the project down the line. With no official license for the main site, the efforts can be re-absorbed into a mass of other projects without needless negotiations over &quot;licenses&quot; and &quot;rights&quot; and provenance. The one large advantage with declaring this work public domain is that in countries where Public Domain doesn't necessarily work or flow, the information can be re-licensed into more restrictive or compatible containers to go with those efforts. For example, you can take this work and license it CC0, the Creative Commons public domain, and use it that way.<br /> <br /> As a result, please refrain from copy-pasting prose and paragraphs from other sources that are not public domain. (For example, Wikipedia. Sketch out a differently-written summary of the information, and then link to the original information you're interested in having included. People who find compatibility with rewriting extant material can therefore take these links and create a new work for the Just Solve wiki. Duplicating lists and names of formats is OK - make use of the work of others to track down lists of obscure file types to include in this wiki.<br /> <br /> ==What happens in the event of disagreement and conflict?==<br /> <br /> Please try and work together as best you can - the goal of this project is to absorb an enormous amount of information and arguing about a point of order doesn't help anyone. Unlike Wikipedia's need for a distinct voice, there is nothing stopping people from making a second paragraph set to explain an alternate overview of a format, or to add a set of other links that the entry didn't have before. It's understandable we're going to have issues about arrangement of materials, like whether a certain format is a &quot;written&quot; or &quot;text&quot; format. It's more important to get the existence of that format in, because the use of Categories and links as we best put them together will make sure the effort is not wasted.<br /> <br /> In cases where an impasse is reached, Jason Scott will serve as editor. In the event Jason Scott appears to be unreasonable, a separate discussion can ensue on the talk page. The goal, again, is to get the information in, past prettiness, preciousness and perfection. Cleaning is a much easier process than acquiring and enumerating at this stage.<br /> <br /> ==How can I help? I don't like to ______ and everyone seems to have that under control anyway.==<br /> <br /> The way I see it, there are two kinds of tasks that the Wiki encourages: tasks involving finding items for the Wiki (be they formats or information about them) and making the Wiki &quot;better&quot; in terms of organization and presentation.<br /> <br /> For the tasks of finding items, going to the [[Sources]] page and you will find a wide variety of locations and directories that will always need another set of eyes to find gems. The individual pages for the formats will have links to other examples or directories that reference that format specifically - those could always use more additions. Linking to an already-researched page that has an eye to describing and improving access to a format completely trumps creating such a page on the Wiki - the huge span of formats out there is the daunting part. So search far and wide and bring back knowledge!<br /> <br /> For the task of the Wiki itself, there are a lot of cases where formatting could be improved, design could look nicer, and classification could be clearer. We expect the look of the place to change significantly over the month as people include MediaWiki Templates and other tricks to make it easier to browse and find information. Short, informative blurbs about each format help people find what they're looking for. Check it out.</div>

Nitro2k01