Just Solve the File Format Problem - User contributions [en]

ProDOS

2023-03-07T17:20:18Z

LostinlodosR: Clarified base on commentary

{|
|[[Software]]
| >
|[[Operating Systems]]
| >
|[[ProDOS]]
|}
'''ProDOS''' was a name used by multiple DOS, disk operating systems, in the 1980s and 1990s.
The most famous and remembered ProDOS (and Pro DOS) releases were:
* Apple ProDOS
*Norton
* Princeton (PPD)
* MIT (MDS)
* IBM (PC DOS Pro Dos 5+)
* Atari Pro DOS
* Commodore (Cdos/ProDOS)
* Apple (SOS)

Apple ProDOS existed in 2 incompatible but similar forms, for the Apple II computers. Apple SOS was also maintained internally as pro dos during development.

With the exclusion of Apple, the ProDOS platform was universally compatible with minor exceptions in command function calls.
The computer history museum and old software web sites contain extensive information and releases. As does way-back software and Old Software.

All non-Apple pro dos releases derive from Microsoft DOS 2.x

User talk:Dan Tobias

2023-02-19T05:46:58Z

LostinlodosR:

== CSS ==

We need to figure out how to deal with disambiguation pages. It is obvious that [[CSS]] can be either [[Cascading Style Sheets]] or [[Content Scramble System]], and I don't think this particular wiki should give preference to one known value over another if the abbreviation can be expanded to an unambiguous name. That's why I linked to [[CSS]] on the [[DVD]] page, rather than linking directly to [[Content Scramble System]]. Unless we plan to sort this out immediately, it might be best to leave that link in place, so that we don't lose track of it. Thoughts? [[User:Gphemsley|Gphemsley]] ([[User talk:Gphemsley|talk]]) 02:05, 29 November 2012 (UTC)
:Perhaps the current CSS article should be moved to Cascading Style Sheets, and a Content Scramble System article created, with [[CSS]] as a disambig article linking to both. But in that case, any specific links to a particular kind of CSS should link directly to the proper one of the articles, not the disambig one. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 02:18, 29 November 2012 (UTC)
:: Done. And created [[Template:Disambiguation]] to keep track of disambiguation pages. [[User:Gphemsley|Gphemsley]] ([[User talk:Gphemsley|talk]]) 16:00, 29 November 2012 (UTC)

== Interwiki links ==

Just a heads-up: You can link to Wikipedia (and a select number of other wikis) using the regular wikilinking syntax by using the relevant wikiprefix. For example: [[Wikipedia:User:GPHemsley]] or [[Wikipedia:Archive Team]]. That way you can differentiate more intimate links to Wikipedia from truly external links to other websites. [[User:Gphemsley|GPHemsley]] ([[User talk:Gphemsley|talk]]) 17:48, 17 December 2012 (UTC)

:Given this site's founder's opinions of Wikipedia, I'm not sure he'd like to get "more intimate" with it, but I'll keep that in mind anyway. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 23:07, 17 December 2012 (UTC)

Re: Wikipedia - I had a paid writing gig last year and in the guidlines there was a strict prohibition from using or citing Wikipedia.
They had good reasons for that... [[User:Cipher|Cipher]] ([[User talk:Cipher|talk]])
:It's still a useful reference if you take it with a big grain of salt. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 01:51, 26 January 2013 (UTC)
::If you take Wikipedia with a big grain of salt, then you must take every other wiki (including this one) with a whole salt mine. [[User:Gphemsley|GPHemsley]] ([[User talk:Gphemsley|talk]]) 15:07, 26 January 2013 (UTC)

== Sidebar ==

Another wikitip: You can change the links in the sidebar by editing [[MediaWiki:Sidebar]] (admins only). You might choose to remove "Current events" and "Help" and add some of the links from the Main page, for example. It takes a somewhat special syntax, though, so you'll probably want to consult [[mw:Manual:Interface/Sidebar]] for guidance. [[User:Gphemsley|GPHemsley]] ([[User talk:Gphemsley|talk]]) 22:26, 22 December 2012 (UTC)

:Thanks for the tips. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 23:40, 22 December 2012 (UTC)

== re [[Talk:Text-based_data]] ==

How do you feel about splitting the Markup languages section out of [[Document]] and a few of the file formats out of [[Text-based data]] into a [[Markup]] page/category? For instance [[textile]] and [[markdown]] have different ontologies but are more similar than not. I'm willing to move stuff over if you define the category. As you mentioned on [[Talk:Text-based data]], 'Categorization is getting pretty chaotic' [[User:Sethwoodworth|Sethwoodworth]] ([[User talk:Sethwoodworth|talk]]) 00:58, 18 January 2013 (UTC)

:A lot of stuff in the ontology probably needs rethinking... any attempt to categorize things starts to get messy and inconsistent after a while, and shows the biases of whoever set them up in the first place and whatever lines of thought they happened to be having at the time, which might not end up being relevant later. (See the Dewey Decimal System categories, for instance; it devotes lots of number space to different aspects of Christian churches, then shoves all "Other Religions" in a small section.) Yes, markup probably deserves its own category (though HTML then would belong there, but it's also in the Web category; should things be in just one category or multiple ones?) [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 02:01, 18 January 2013 (UTC)

:Hrrm, I see. Maybe things need multiple categories. The CDC's public health image library uses multiple ontologies pretty effectively [http://imgur.com/lqd6p] For now I wont sweat it too much. Search works pretty well. [[User:Sethwoodworth|Sethwoodworth]] ([[User talk:Sethwoodworth|talk]]) 16:14, 18 January 2013 (UTC)

:OK, I added a [[Markup]] page. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 15:58, 19 January 2013 (UTC)

== IPA ==

I noticed that you created [[IPA]] to describe some iOS/iTunes format that I'm not familiar with. However, IPA can also refer to the [[Wikipedia:International Phonetic Alphabet|International Phonetic Alphabet]], which probably falls under the text encoding/language script portion of this project. It should probably be disambiguated. [[User:Gphemsley|GPHemsley]] ([[User talk:Gphemsley|talk]]) 03:23, 3 February 2013 (UTC)

== Deletion request ==

Hey Dan, [[:Category:File_formats_with_extension_.dcs|this category was created in error]]. Would you mind nuking it for me? [[User:Lewis Collard|Lewis Collard]] ([[User talk:Lewis Collard|talk]]) 22:42, 16 March 2013 (UTC)

== Self-links ==

You may not be aware, but explicitly bolded "self-links" (like this - '''[[User talk:Dan Tobias]]''') aren't handled consistently by different web browsers. In some they are bold, and in some (IE, and sometimes Firefox) they are really-really bold. I don't think the wiki software expects you to do that.

:Yes, I've noticed that... I kind of like the font Firefox (sometimes) uses for this, which is what got me to start doing it (in imitation of somebody else who first started doing it here a while back; I don't remember who), but perhaps that's an unintended effect? On Firefox on a different machine it doesn't show up, so it seems to depend on system-specific things (like what fonts are installed maybe?). It would be good to be consistent in style, though, so how do you think main titles should be marked up? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 18:25, 4 January 2014 (UTC)

::I have no preference as to how they're marked up, but I do prefer to see them rendered as normal bold (like Wikipedia), not extra bold. [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 18:56, 4 January 2014 (UTC)
:::Fair enough. I think I'll do it that way from now on; my main concern is to stay consistent, not so much to favor one style or another. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 19:08, 4 January 2014 (UTC)

== SVG uploads ==

Hi,

As you have noticed i've been doing error codes, fault codes, and other messages and i have now come across [http://www.appliancepartspros.com/repair-help/kitchenaid-fault-codes.html#Kitchen%20Aid%20Cooktop%20Fault%20Codes%2030%20in this]. As you see there are icons displaying an indicator, but i wouldn't want to copy it from their site. I do think that it can be argued that simple shapes are not protected by copyright, but their quality is shit, and i have already recreated the display in SVG (proper SVG, not one of those 'picture-to-svg' things). However, when i attempt to upload it here i find that this wiki doesn't accept SVG at all, which is very strange.

You are the only active admin at the moment, and i was hoping you can help me with this or at least tell me who do i need to sexually gratify to allow me to help this project by uploading some circles )))

Thanks in advance. [[User:VolodyA! V Anarhist|VolodyA! V Anarhist]] ([[User talk:VolodyA! V Anarhist|talk]]) 15:36, 19 April 2015 (UTC)

:I don't think I have any way of changing that; at least, I don't see anything about it in the array of tools I can see as an admin. Maybe it's a sysadmin-level config thing requiring access to the server. Jason Scott is the owner of the site, but he doesn't show up here much. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 17:13, 19 April 2015 (UTC)

::Yeah, it is in the LocalSettings file... will ask Jason Scott for help. [[User:VolodyA! V Anarhist|VolodyA! V Anarhist]] ([[User talk:VolodyA! V Anarhist|talk]]) 19:13, 19 April 2015 (UTC)

== DISPLAYTITLE ==

Hi, i see you tried to add DISPLAYTITLE to [[C Sharp]] and noticed that it didn't work. Just wanted to explain why (if you are wondering). Basically the default MediaWiki settings only permit to change the display title if it was potentially possible to interpret title this way. For example, when you change the case of the first letter (that gets altered automatically) or when you change space into an underscore (because software would otherwise do the opposite). It is potentially possible to change [https://www.mediawiki.org/wiki/Manual:$wgRestrictDisplayTitle $wgRestrictDisplayTitle] to false, but that would open us to trolling and other bad things. [[User:VolodyA! V Anarhist|VolodyA! V Anarhist]] ([[User talk:VolodyA! V Anarhist|talk]]) 05:50, 12 May 2015 (UTC)

:OK, thanks. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 12:01, 12 May 2015 (UTC)

== FTM ==
Just came back to create those additional Family tree maker categories and found that you'd done it, Thank you [[User:Sam888|Sam888]] ([[User talk:Sam888|talk]]) 00:38, 9 March 2016 (UTC)
:You're welcome! [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 02:30, 9 March 2016 (UTC)
::Thanks again, lighting Dan :) [[User:Sam888|Sam888]] ([[User talk:Sam888|talk]]) 23:06, 29 April 2016 (UTC)

== Pages in multiple categories ==

Hey, I noticed you just created a [[Saved Games]] page. I assume any game save formats from the [[Game data files]] page should be moved over, but what about if a format falls into both of these categories? For example, [[Cities Skylines CRP]] files are used for both save games, as well as community made mods and maps. Can a page be in multiple subcategories, or should it remain in the category it fits best? I'm not really sure who to turn to on formatting issues, so hopefully im in the right place.
--[[User:Hamhock666|Hamhock666]] ([[User talk:Hamhock666|talk]]) 05:03, 25 September 2016 (UTC)

:That page has actually been there all along; I just added an entry to it for the newly created "orphan page" that wasn't linked anywhere but was in that category. Pages are sometimes in multiple categories, but the two game-related pages do cross-link to one another. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 05:27, 25 September 2016 (UTC)

== Thank You... ==

...for changing those links on the list page. I had completely forgotten about that. [[User:Effect2|Effect2]] ([[User talk:Effect2|talk]]) 07:06, 11 February 2019 (UTC) (06:27)
:No problem... I'm always loooking out for "orphan pages" being created without links in the index/list pages. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 14:18, 11 February 2019 (UTC)

== BlockHashLoc from ForensicsWiki ==

I am not sure whether or not to create a page here for this: https://web.archive.org/web/20190911115527/http://www.forensicswiki.org/wiki/BlockHashLoc . It seems to be a neat, but not necessarily widely (or at all) used idea someone came up with (and implemented). Your thoughts welcomed. [[User:JesseW|JesseW]] ([[User talk:JesseW|talk]]) 01:01, 26 October 2020 (UTC)
:Sure... we're not Wikipedia, and don't gatekeep for "notability"; anything that's been used as a file format somewhere is fair game. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 02:59, 26 October 2020 (UTC)
:: OK, will add it when I get a chance. [[User:JesseW|JesseW]] ([[User talk:JesseW|talk]]) 14:57, 26 October 2020 (UTC)
::: There's already a page for [[BlockHashLoc]]. I have created it about 1 month after I published the code on GitHub. Hope it's OK.
:::: Very much so -- that saves me the trouble, thank you! Not sure why I didn't find it earlier. [[User:JesseW|JesseW]] ([[User talk:JesseW|talk]]) 16:02, 28 October 2020 (UTC)

== Improve this page. ==

http://fileformats.archiveteam.org/wiki/Android_ADB_Backup

== iWork redux? ==
http://fileformats.archiveteam.org/wiki/Talk:IWork
Considering a rewrite. Any thoughts before I do so?[[User:LostinlodosR|LostinlodosR]] ([[User talk:LostinlodosR|talk]]) 19:32, 27 August 2022 (UTC)

== FM ==
Wow, i didn’t even consider FM radio. Too long has my head been in computers. Thanks[[User:LostinlodosR|LostinlodosR]] ([[User talk:LostinlodosR|talk]]) 05:46, 19 February 2023 (UTC)

XviD

2023-02-19T05:40:30Z

LostinlodosR: Typos

{{FormatInfo
|formattype=electronic
|subcat=Video
}}
'''XViD''' is a reverse engineered H262/H263 video codec used for AV files. Often it is pared with MP2, MP3, and later OGG audio in an XViD (AVI) container.

XViD was the end result of of a combination of insider stolen information and clean room reverse engineering. Occasionally found in contemporary file sharing circles it found the most use as XVCD format [[iso]] files: a bitrate variation of VCD. XViD found popularity with a few DVD compression programs such as RatDvD. The xvid file format was close enough that most VCD players and nearly all SVCD/EVCD player had no problems with playback of recorded discs. Changing the XViD extension to avi allow e playback on all contemporary operating systems that supported the avi format.
Xvcd uses XViD video and audio.

In the late 90s and early 20000s both BlockBuster and Family Video experimented with disposable rental discs that used the XViD/xvcd format. Self-degrading discs that could be rented from a kiosk and recycled curbside.
The XViD format was also a primary target in the SD card forms for pay once copy never distribution.

The XViD format in all its variations died with the combination of the death of Meganova and Mininova torrent sites and the much superior X264 format.
Itself replace by x265 and now AV1

Talk:ProDOS

2023-02-19T05:35:30Z

LostinlodosR:

Do you have a source for any of this? My recollection is that ProDOS is specifically an Apple II series OS, and the others listed here aren't related to it or given this name. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 19:31, 18 February 2023 (UTC)
> I have a copy of Norton ProDOS. I’ll upload the photo as soon as I find the box. I know there were others. Along with what I listed there was also PTS and XE was sold as Pro Dos in some packaging. Though I believe ProDOS should be separated to Pro DOS? The only two I have evidence for as not having a space is Apple and Norton.[[User:LostinlodosR|LostinlodosR]] ([[User talk:LostinlodosR|talk]]) 05:35, 19 February 2023 (UTC)

M3U

2023-02-18T13:45:24Z

LostinlodosR: Created page with "M3U is a plain text file listing of files for a play list. Originally ASCII later revisions use Unicode 8. M3U files are directory location listings of specific files on an ..."

M3U is a plain text file listing of files for a play list.
Originally ASCII later revisions use Unicode 8.

M3U files are directory location listings of specific files on an individual user’s computer.
Late MPX, occasionally mistyped as m3u files, point to internet address.

For advanced users, an mpu/m3u file can point to any file on any platform via any transmission method: the most common minority variable being FTP.

ProDOS

2023-02-18T13:38:53Z

LostinlodosR: Created page with "ProDOS was a name used by multiple DOS, disk operating systems, in the 1980s and 1990s. The most famous and remembered ProDOS releases were: Norton Princeton (PPD) MIT (MDS)..."

ProDOS was a name used by multiple DOS, disk operating systems, in the 1980s and 1990s.
The most famous and remembered ProDOS releases were:
Norton
Princeton (PPD)
MIT (MDS)
IBM (PC DOS 5+)
Atari
Commodore (Cdos/ProDOS)
Apple (SOS)

The ProDOS platform was universally compatible with minor exceptions in command function calls.
The computer history museum and old software web sites contain extensive information and releases. As does way back software.

All pro dos releases derive from Microsoft DOS 2.x

XviD

2023-02-18T13:25:09Z

LostinlodosR: Created page with "XViD is a reverse engineered H262/H263 video codec used for AV files. Often it is pared with MP2, MP3, and later OGG audio in an XViD (AVI) container. XViD was the end resul..."

XViD is a reverse engineered H262/H263 video codec used for AV files. Often it is pared with MP2, MP3, and later OGG audio in an XViD (AVI) container.

XViD was the end result of of a combination of insider stolen information and clean room reverse engineering. Occasionally found in contemporary file sharing circles it found the most use as XVCD format [[iso]] files: a bitrate variation of VCD. XViD found popularity with a few DVD compression programs such as RatDvD. The xvid file format was close enough that most VCD players and nearly all SVCD/EVCD player had no problems with playback of recorded discs. Changing the XViD extension to avi allow e playback on all contemporary operating systems that supported the avi format.
Xvcd uses XViD video and audio.

In the late 90s and early 20000s both BlockBuster and Family Video experimented with disposable rental discs that used the XViD/xvcd format. Self-degrading docs that could be rented from a kiosk and recycled curbside.
The XViD format was also a primary target in the SD card forms for pay once copy never distribution.

The XViD format in all its variations died with the combination of the death of Mega and Mininova torrent sites and the much superior X264 format.
Itself replace by x265 and now AV1

FM (Creative FM Blaster)

2023-02-18T13:08:27Z

LostinlodosR: Created page with ".FM is a radio transmission file delivered, and saved, by Creative FM Blaster. The file type is an RIFF container holding either a wav or a snd format audio file. The .FM e..."

.FM is a radio transmission file delivered, and saved, by Creative FM Blaster.
The file type is an RIFF container holding either a wav or a snd format audio file.

The .FM extension was used by Creative for recorded files saved from live stream broadcasts via the FM Blaster radio card; a popular PCI and ISA format radio reception card in the 1990s before internet radio was commonplace.
The FM format name is a misnomer as the files recorded not just FM radio but AM, Short wave, marine, and ham radio transmission. Later TV blaster cards recorder audio only as FM as well. The video and audio format extension being .tv and .CTV

Most extension agnostic programs will open the .FM files as their native format.

RISC OS

2023-02-18T00:09:35Z

LostinlodosR: Created page with "{| |Software | > |Operating Systems | > |Risc OS |} '''RISC OS''' is a windowed operating system release first in 1987 by ARM. It uses the reduced instruction set ..."

{|
|[[Software]]
| >
|[[Operating Systems]]
| >
|[[Risc OS]]
|}
'''RISC OS''' is a windowed operating system release first in 1987 by ARM. It uses the reduced instruction set computing architecture.

Risc OS is a graphical desktop environment, [[GUI]], that runs programs in windows.
Version 5, 32-bit, is open source. Version 6 is proprietary. RISC OS runs on ARM-32 and ARM-64 machines and most ARM compatible derivatives.

== Links ==
* [[Wikipedia:Risc OS|Wikipedia article]]

[[Category:Operating Systems]]

Visual Basic

2023-02-17T00:10:25Z

LostinlodosR: Visual Basic for applications is used across all office programs.

{{FormatInfo
|formattype=Languages
|subcat=Programming Languages
|extensions={{ext|vb}}
|pronom={{PRONOM|fmt/1088}}
|released=1991
}}
'''Visual Basic''' is a Microsoft programming language based on [[BASIC]], but evolved far enough from early BASICs to be pretty much unrecognizable to anybody acquainted with such languages as [[Applesoft BASIC tokenized file|Applesoft BASIC]]. It has an event-driven structure and support for graphical user interfaces.

Visual Basic for Applications (VBA) is a variant of Visual Basic that is used embedded in an application software package; this is what is used for [[Microsoft Office]] macros in [[XLM]], [[XLSM]], and [[XLTM]] files, etc.

== See also ==
* [[Visual Basic project file]]
* [[VBScript]]

== Links ==
* [[Wikipedia:Visual Basic|Wikipedia article]]
* [http://msdn.microsoft.com/en-us/vstudio/ms788229.aspx Visual Basic resources]

[[Category:Microsoft]]

MIDI

2022-09-17T00:24:20Z

LostinlodosR:

{{FormatInfo
|subcat=Audio and Music
|extensions={{ext|mid}}, {{ext|midi}}
|mimetypes={{mimetype|audio/midi}} {{mimetype|audio/mid}} {{mimetype|audio/x-midi}} {{mimetype|audio/m}} {{mimetype|application/x-midi}}
|locfdd={{LoCFDD|fdd000102}} {{LoCFDD|fdd000119}}
|pronom={{PRONOM|x-fmt/230}}
}}
'''Musical Instrument Digital Interface''' ('''MIDI''') is an industry specification that permits digital musical instruments, computers and other related devices to connect and communicate with one another. The MIDI Specification was published in August 1983, and is widely used in electronic music.

For many, the name "MIDI" is associated with music synthesized with cheesy, lifeless software instruments from the 90's. There is considerable confusion resulting in the conflation of several things:

* The core MIDI protocol, which is a real-time messaging format that encodes musical events such as note on/note off, velocity, tempo, controls, etc.
* The '''General MIDI''' sub-specification of MIDI, which associates MIDI program numbers with a specific bank of 175 instruments such as oboes, pianos, drums, and so forth.
* The MIDI file format, officially '''SMF''' (Standard MIDI Format), which is simply a score of timed MIDI messages. MIDI files may or may not be intended for interpretation as General MIDI.
* The synthesis methods used to realize MIDI and/or General MIDI as audio, which run the whole spectrum from cheesy to non-cheesy.

Back in the day, high-quality audio files were a bit large to send over the Internet, so nerds would listen to MIDI file renditions instead. Since MIDI itself does not specify how program numbers map to instruments, General MIDI ensures that the Third Eye Blind song you send to your buddy over AOL will not inexplicably have bagpipes in it. Nowadays, MIDI files are used primarily as a storage and interchange format for music producers rather than an consumers. In music production, the synthesizer associated with a given MIDI channel is generally known ''a priori'', so the interopability of General MIDI is less useful. The ghost of bad General MIDI synthesizers nevertheless persists in the public view of MIDI.

"Black MIDI" is a style of MIDI music that has notes so densely placed that a graphical rendition has large patches of solid black.

== Alternative formats ==
As well as the standard MIDI specification, a number of (often proprietary) MIDI clones and variants have been created over the years. These include:

== Sound Fonts ==
Originally created and used by Emu and Creative Labs software and equipment, [[SoundFont_1.0|sound fonts]] are instrument description extensions, or voice files, used, usually, for a cleaner high quality sound. Sound fonts are available from and for: Rolland, Yamaha, Allen Organ, and Wurlitzer, among others.

* [[Compact MIDI]]
* [[GMD]]
* [[HMI]]
* [[HMP]]
* [[HMZ]]
* [[KAR]]
* [[MIDS]]
* [[MIZ]]
* [[MSS (MIDI)|MSS]]
* [[RIFF MIDI]]
* [[Scalable Polyphony MIDI]]
* [[Synthetic Music Application Format]]
* [[Doom MUS]]

== External links ==
* [[Wikipedia:MIDI]]
* [http://localhostr.com/file/LJUEw0K/midiformat.pdf Standard MIDI-File Format Spec. 1.1]
* [http://www.midi.org/techspecs/midispec.php The Complete MIDI 1.0 Detailed Specification] Available for purchase from MMA (MIDI Manufacturers Association)
* [http://www.blitter.com/~russtopia/MIDI/~jglatt/tech/midispec.htm The MIDI Specification] Not the official specification, but an adaptation.
* [http://www.digitalpreservation.gov/formats/fdd/fdd000102.shtml MIDI Sequence Data, from Library of Congress resource on Sustainability of Digital Formats]
* [http://www.digitalpreservation.gov/formats/fdd/fdd000119.shtml Standard MIDI File Format, from Library of Congress resource on Sustainability of Digital Formats]
* [ftp://ftp.modland.com/pub/documents/format_documentation/MIDI%20(General%20MIDI%20Level%201%20Spec)%20(.mid).txt Brief Overview of Proposed General MIDI Level 1 Spec]
* [ftp://ftp.modland.com/pub/documents/format_documentation/MIDI%20(Sample%20Dump%20Standard)%20(.mid).txt MIDI Sample Dump Standard]
* [ftp://ftp.modland.com/pub/documents/format_documentation/MIDI%20(The%20Usenet%20MIDI%20Primer)%20(.mid).txt The USENET MIDI Primer]
* [https://www.techdirt.com/blog/innovation/articles/20130412/09091522689/heres-another-inventor-who-willingly-gave-his-greatest-idea-away-order-to-establish-it-as-global-standard.shtml Inventor of MIDI willingly gave idea away to establish it as a standard]
* [http://rhizome.org/editorial/2013/sep/23/impossible-music-black-midi/ The impossible music of black MIDI]
* [https://www.youtube.com/watch?v=FqjSYtKWyX8 Black MIDI songs will kill your brain and your computer]

Numbers

2022-09-12T20:04:25Z

LostinlodosR:

{{FormatInfo
|formattype=electronic
|subcat=Document
|subcat2=Spreadsheet
|extensions={{ext|numbers}}, {{ext|numbers.zip}}
|pronom={{PRONOM|fmt/825}}
|released=2005
}}
:''This article is about the spreadsheet format. For number formats, see [[:Category:Number formats]].''

'''Numbers''' is part of [[iWork]], an Apple application suite available as apps for OS-X and iOS as well as in a cloud-based version on iCloud. It is a spreadsheet program.

The web-based cloud version can be run in a browser (Not all browsers are fully supported; when you try it in Firefox, it says that it is an unsupported browser, but seems to work anyway, though it is possible some features aren't fully functional), and is free for iCloud users. The app is currently free across all Apple devices. it will sync automatically with iCloud to access cloud-stored documents.

The current version can load and save the corresponding Microsoft Excel [[XLS]] file type (using, apparently, the 2003 file version). It can also save as [[PDF]], producing a static document that can be useful for viewing, but not so much for editing or import into other software. And then there is the native iWork format, bearing a .numbers extension, or a double extension .numbers.zip when saved in a [[ZIP]] file.

iWork files, when saved under Mac OS-X, are in a [[Bundle file (OS X)|bundle format]] that is actually a directory/folder. Saved in other systems, or exported as e-mail attachments, they are ZIPped and use the double extension as noted above.

== File format info ==

The basic file format is consistent across the iWork suite, and is documented more fully in the [[iWork]] article. In the 2013 version of the format, the different apps mostly differ in what [[IWA]] files are stored in the <code>Index.zip</code> file (a ZIP within the bundle).

Numbers (2013) files include <code>DocumentStylesheet.iwa</code>, <code>ThemeStylesheet.iwa</code>, <code>Document.iwa</code>, <code>Metadata.iwa</code>, <code>CalculationEngine.iwa</code>, and <code>AnnotationAuthorStorage.iwa</code>. The <code>Tables</code> subdirectory has <code>DataList.iwa</code> and a series of numbered files like <code>DataList-1.iwa</code>, <code>DataList-2.iwa</code>, and so on. There is also <code>HeaderStorageBucket.iwa</code>, <code>HeaderStorageBucket-1.iwa</code>, etc., and <code>Tile-iwa</code>, <code>Tile-1.iwa</code>, etc.

===Compatibility===

* Numbers version 2.6 released on Oct 15, 2015 added compatibility with Numbers ’08 documents

== See also ==
* [[Pages]]
* [[Keynote]]

== Sample files ==
* [https://www.dan.info/sampledata/iwork/TestSpreadsheet.numbers.zip TestSpreadsheet.numbers.zip]

== Links ==
* [[Wikipedia:Numbers (spreadsheet)|Wikipedia article]]
* [https://apps.apple.com/us/app/numbers/id409203825?mt=12 Mac App Store Download & Version History]
* [http://apple.stackexchange.com/questions/142356/why-does-numbers-hide-a-huge-png-file-in-exported-excel-sheets Why does Numbers hide a huge PNG file in exported Excel sheets?]

[[Category:Apple]]
[[Category:Apple bundle files]]

QuickTime

2022-09-04T01:57:52Z

LostinlodosR:

{{FormatInfo
|formattype=electronic
|subcat=Video
|extensions={{ext|mov}}
|mimetypes={{mimetype|video/quicktime}}
|pronom={{PRONOM|x-fmt/384}}
|wikidata={{wikidata|Q942350}}
}}
:''"MOV" redirects here. For another MOV format, see [[Electronic Arts MOV]]. For movie formats in general, see [[Video]].''

'''QuickTime''' is a container format developed by Apple Computer, Inc. It is usually used to wrap video content, but can also be used to wrap sound and still image data.

The QuickTime format was used as the basis for the international standard [[MPEG-4]] format.

A now-deprecated related format for still images taken from a QuickTime video is [[QTIF]].

==History==

QuickTime was originally released in 1991 following years of internal development.
QuickTime exists in 7 minor format releases from 1991 (1.x) through 2016 (7.x).
A major upgrade to the platform occurred in 2009 with QuickTime X.
The current version of classic QuickTime is 7.7.9 as of 2016.
QuickTime X is At version 10.5

== Format ==
See [[boxes/atoms format]]. Starting in 2004, the QuickTime movie file specification has been based on [[ISO Base Media File Format]], with a brand of "<code>qt  </code>".

== Quicktime VR ==
In the past, the Quicktime format has been used as a container for so called Virtual Reality (or rather, 360 degree panorama) data. Not clear how to identify. File extensions usually just .mov, but may be .qt or more specifically .qvr (possibly .qtvr?).

* [http://www.mactech.com/articles/mactech/Vol.12/12.05/QTVRTutorial/index.html Getting started with QuickTime VR] - tutorial from February, 1996.]
** Mentions "creator/file type of the downloaded movie to QuickTime VR’s 'vrod'/'MooV'", which may be the type?
** ffprobe shows "Stream #0:1(eng): Data: none (pano / 0x6F6E6170), 0 kb/s", so I presume 'pano' is the ftyp/FourCC?
** "The media type of the panorama track is 'pano'." from Quicktime file format specification, page 289.
* [http://www.synthetic-ap.com/qtvr/qtvrsamp.html Example Quicktime VR files]

== Specifications ==

* [https://developer.apple.com/standards/classic-quicktime/ QuickTime File Format Specification (classic, 2001)]
* [https://developer.apple.com/library/content/documentation/QuickTime/QTFF/ QuickTime File Format Specification (current version)]

== Metaformat files ==

* {{Synalysis|qt}}

== Software ==
* [[Konvertor]]
* [http://archive.org/download/PowerPlay0597/PowerPlay0597.iso01.iso/TOOLS/Qtime/QT32INST.EXE QuickTime 2.1.2 for Windows (c. 1997)]
* [http://www.apple.com/quicktime/download/ Current QuickTime download]
* [[FFmpeg]]

== Sample files ==
* [http://support.apple.com/kb/HT1425 Apple's sample QuickTime files in several encodings]
* https://telparia.com/fileFormatSamples/video/mov/
* http://samples.mplayerhq.hu/mov/

== See also ==
* [[Boxes/atoms format]]
* [[ISO Base Media File Format]]
* [[MPEG-4]]
* [[PICT]]
* [[QTIF]]
* [[QuickTime Animation]]

== Links and references ==

* [http://www.apple.com/quicktime/ Official site]
* [[Wikipedia:QuickTime|QuickTime : Wikipedia]]
* {{EGFF|quicktime|QuickTime File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]
* [http://scarygoround.com/index.php?date=20110408 Even comic-strip people can have trouble getting those things to play...]

[[Category:Apple]]
[[Category:Box file format]]

Talk:QuickTime Animation

2022-09-04T01:38:11Z

LostinlodosR:

I think information about QuickTime-the-software could reasonably go in the [[QuickTime]]-the-format article, but I don't think it belongs here. -[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 13:53, 3 September 2022 (UTC)
: yep. Dropped into the wrong page. My bad. Good catch![[User:LostinlodosR|LostinlodosR]] ([[User talk:LostinlodosR|talk]]) 01:38, 4 September 2022 (UTC)

QuickTime Animation

2022-09-04T01:37:22Z

LostinlodosR:

{{FormatInfo
|formattype=electronic
|subcat=Video
}}
'''QuickTime Animation''', also called '''QuickTime RLE''', is a compressed video format. It is typically used with the [[QuickTime]] container format.

== Identifiers ==
In QuickTime-related formats, QuickTime Animation is identified by the [[FourCC]] "<code>rle </code>".

== Specifications ==
* [http://multimedia.cx/qtrle.txt Description of the Apple Quicktime Animation (RLE) Format], by Mike Melanson

== Software ==
* [[FFmpeg]]

== Sample files ==
* http://samples.libav.org/V-codecs/QTRLE/
* [https://github.com/openpreserve/format-corpus/blob/master/video/Quicktime/animation.mov animation.mov]

== Links ==
* [[Wikipedia:QuickTime Animation]]
* [http://wiki.multimedia.cx/index.php?title=Apple_QuickTime_RLE MultimediaWiki: QuickTime RLE]

[[Category:Apple]]

Talk:QuarkXPress

2022-09-03T01:29:22Z

LostinlodosR:

I’m not sure if the new QX compressed bundle is limited to the trial version or is a standard practice today. The file only appears as such in my APFS volume. A default save to another file system (Apple, etc) saves normal files.[[User:LostinlodosR|LostinlodosR]] ([[User talk:LostinlodosR|talk]]) 01:29, 3 September 2022 (UTC)

Talk:QuarkXPress

2022-09-03T01:29:02Z

LostinlodosR: Created page with "I’m not sure if the new QX compressed bundle is limited to the trial version or is a standard practice today. The file only appears as such in my APFS volume. A default save..."

QuarkXPress

2022-09-03T01:25:48Z

LostinlodosR:

{{FormatInfo
|formattype=electronic
|subcat=Document
|subcat2=Desktop Publishing
|extensions={{ext|qxp}}, {{ext|qxd}}, others
|mimetypes={{mimetype|application/vnd.quark.quarkxpress}}
|pronom={{PRONOM|x-fmt/182}}, {{PRONOM|fmt/652}}, {{PRONOM|fmt/685}}, {{PRONOM|fmt/651}}
|wikidata={{wikidata|Q678036}}
|type code={{Type Code|XDOC}}
|released=1987
}}
'''QuarkXPress''' is a desktop publishing application.

== Identifiers ==

* QXD - QuarkXPress legacy Document (Version 3.1 - 5)
* QXT - QuarkXPress legacy Template (Version 3.1 - 5)
* QWD - QuarkXPress Web Document
* QWT - QuarkXPress Web Template
* QXL - QuarkXPress Library
* QXB - QuarkXPress Book
* QXP - QuarkXPress Project (Version 6 - 15)
* QPT - QuarkXPress Project Template (Version 6 - 15)
* QCD - QuarkXPress Article

Current versions may creat a QX [[bundle]] file on MacOS, which is a multi-file directory.

== Identification ==
Files have "{{magic|IIXPR}}" or "{{magic|MMXPR}}" at offset 2.

QuarkXPress legacy documents (QuarkXPress 3, 4, 5 and 6) need to be converted to the new format (QuarkXPress 9.1) in order to be opened by QuarkXPress 10 and newer. [https://www.quark.com/documentation/quarkxpress/2020/english/QXP_2020_Getting_Started/_D360942A496540CCA7ACB2F8BBA080AF_14.html Free software is available.]

===Versions===
QuarkXPress file versions can be determined by hex values offset 8 or 9<ref>https://gerrit.libreoffice.org/plugins/gitiles/libqxp/+/master/src/lib/QXPHeader.h</ref>.

{| class="wikitable"
! Version !! Extension !! Year !! Hex !! PRONOM
|-
|QuarkXPress 1 || || 1987 || 001C001C ||
|-
|QuarkXPress 2 || || 1989 || 00260026 ||
|-
|QuarkXPress 3.0 || || 1990 || 00360036 ||
|-
|QuarkXPress 3.1 Mac || '''.QXD''' || 1992 || 0x39* || {{PRONOM|fmt/1317}}
|-
|QuarkXPress 3.1 Win || '''.QXD''' || 1992 || 0x3e* || {{PRONOM|fmt/1317}}
|-
|QuarkXPress 3.2 Mac<ref>https://books.google.com/books?id=-zoEAAAAMBAJ&lpg=PA8&ots=cOmG8ELjlG&dq=quarkxpress%203.2%20windows&pg=PA8#v=onepage&q=quarkxpress%203.2%20windows&f=false</ref> || '''.QXD''' || 1993 || 0x3c ||
|-
|QuarkXPress 3.3 || '''.QXD''' || 1996 || 0x3f || {{PRONOM|fmt/1318}}
|-
|QuarkXPress 4 || '''.QXD''' || 1997 || 0x40 or 0x41 || {{PRONOM|fmt/1319}}
|-
|QuarkXPress 5 || '''.QXD''' || 2002 || 0x42 || {{PRONOM|fmt/1320}}
|-
|QuarkXPress 6 || '''.QXP''' || 2003 || 0x43 || {{PRONOM|fmt/652}}
|-
|QuarkXPress 7 || '''.QXP''' || 2006 || 0x44 || {{PRONOM|fmt/1321}}
|-
|QuarkXPress 8 || '''.QXP''' || 2008 || 0x45 || {{PRONOM|fmt/1322}}
|-
|QuarkXPress 9 || '''.QXP''' || 2011 || 0x46 || {{PRONOM|fmt/685}}
|-
|QuarkXPress 9.1 || '''.QXP''' || 2011 || 0x47 || {{PRONOM|fmt/1323}}
|-
|QuarkXPress 9.2 || '''.QXP''' || 2011 || 0x48 ||
|-
|QuarkXPress 10 || '''.QXP''' || 2014 || 0x49 || {{PRONOM|fmt/651}}
|-
|QuarkXPress 10.1 || '''.QXP''' || 2014 || 0x4a || {{PRONOM|fmt/1446}}
|-
|QuarkXPress 11 || '''.QXP''' || 2015 || 0x4b || {{PRONOM|fmt/1324}}
|-
|QuarkXPress 12.1 || '''.QXP''' || 2016 || 0x4c || {{PRONOM|fmt/1325}}
|-
|QuarkXPress 13.2 || '''.QXP''' || 2018 || 0x4d || {{PRONOM|fmt/1326}}
|-
|QuarkXPress 14 || '''.QXP''' || 2018 || 0x4e || {{PRONOM|fmt/1327}}
|-
|QuarkXPress 15 || '''.QXP''' || 2019 || 0x4f || {{PRONOM|fmt/1328}}
|-
|QuarkXPress 16 || '''.QXP''' || 2020 || 0x50 || {{PRONOM|fmt/1494}}
|-
|QuarkXPress 17 || '''.QXP''' || 2021 || 0x51 || {{PRONOM|fmt/1495}}
|}

<nowiki>*</nowiki> QuarkXPress version 3.1 may have values of 0x39, 0x3A, 0x3B, 0x3D, 0x3E

== Software ==
* [http://www.quark.com/Products/QuarkXPress/ QuarkXPress]
* [https://github.com/renyxa/re-lab Re-lab / OLE Toy] - Appears to have some support for parsing the format
* [https://wiki.documentfoundation.org/DLP/Libraries/libqxp Libqxp library for LibreOffice, currenly only reads QuarkXPress versions 3-4]

== Sample files ==
* https://telparia.com/fileFormatSamples/document/quarkXPress/

== Links ==
* [[Wikipedia: QuarkXPress]]
* [http://www.quark.com/Products/QuarkXPress/ QuarkXPress website]
* [http://www.planetquark.com/ Planet Quark]
* [https://www.online-convert.com/file-format/qxp QXP File Format & Sample File]

== References ==
<references/>

[[Category:File formats with too many extensions]]

QuickTime Animation

2022-09-03T01:14:15Z

LostinlodosR:

{{FormatInfo
|formattype=electronic
|subcat=Video
}}
'''QuickTime Animation''', also called '''QuickTime RLE''', is a compressed video format. It is typically used with the [[QuickTime]] container format. QuickTime was originally released in 1991 following years of internal development.
QuickTime exists in 7 minor format releases from 1991 (1.x) through 2016 (7.x).
A major n upgrade to the platform occurred in 2009 with QuickTime X.
The current version of classic QuickTime is 7.7.9 as of 2016.
QuickTime X is At version 10.5

== Identifiers ==
In QuickTime-related formats, QuickTime Animation is identified by the [[FourCC]] "<code>rle </code>".

== Specifications ==
* [http://multimedia.cx/qtrle.txt Description of the Apple Quicktime Animation (RLE) Format], by Mike Melanson

== Software ==
* [[FFmpeg]]

== Sample files ==
* http://samples.libav.org/V-codecs/QTRLE/
* [https://github.com/openpreserve/format-corpus/blob/master/video/Quicktime/animation.mov animation.mov]

== Links ==
* [[Wikipedia:QuickTime Animation]]
* [http://wiki.multimedia.cx/index.php?title=Apple_QuickTime_RLE MultimediaWiki: QuickTime RLE]

[[Category:Apple]]

Talk:IWork

2022-08-31T07:07:59Z

LostinlodosR:

I’m looking at a potential rewrite. All versions of iWork files post 2013 can be extracted (from .pages or .pages.zip, etc or from a folder bundle, down to the bare components.
Both Keka (MacOS) and 7Zip (cross platform) can extract iWork files. Recovery there being a bit of tedious but not difficult, per se, editing of the xml.
NeoOffice, the commercial mod of OO/LO appears to have little trouble opening older iWork files back to the early teens with just an extension change. Albeit with some minor formatting issues.
A plug-in for Calibre exists for the earlier editions, abandoned, but working.
Also, some Mac PDF editors with one-click conversion can transfer iWork to multi-layer PDF files. Such as PDFExpert. These allow a two program conversion. Loading the PDF in a viewer/editor with output filters (Calibre, Acrobat) allow the PDF to be converted to Office Open or Open Office quite accurately.
 
All said, Apple’s unique fandom that can attach itself to specific hardware or OS versions… has made official formats easily convertible.
Any thoughts before I attempt a re-edit here.
[[User:LostinlodosR|LostinlodosR]] ([[User talk:LostinlodosR|talk]]) 19:30, 27 August 2022 (UTC)

* Are you looking to just add a section for recovery or alternative render solutions, or are you wanting to re-write all the info? It's important to know the different versions released and when they changed from folder bundles and ZIP containers, when certain features were added, etc, but Apple still maintains the software. So maybe just a section on non-Mac OS solutions? --[[User:Thorsted|Thorsted]] ([[User talk:Thorsted|talk]]) 16:50, 29 August 2022 (UTC)

** I’m not sure. Something about the article just, bothers me, the way it’s done now. I’m not sure what it is. Guess I’ll make a sandbox and copy it for an edit attempt and see what people think? [[User:LostinlodosR|LostinlodosR]] ([[User talk:LostinlodosR|talk]]) 07:07, 31 August 2022 (UTC)

Talk:IWork

2022-08-29T19:00:56Z

LostinlodosR:

User talk:Dan Tobias

2022-08-27T19:32:26Z

LostinlodosR:

Talk:IWork

2022-08-27T19:30:29Z

LostinlodosR: Created page with "I’m looking at a potential rewrite. All versions of iWork files post 2013 can be extracted (from .pages or .pages.zip, etc or from a folder bundle, down to the bare componen..."

Just Solve the File Format Problem:Community portal

2022-08-23T20:44:39Z

LostinlodosR: Greetings

: ''please add your signature by typing <nowiki>~~~~</nowiki> if you add or reply

== Open issues ==

Below is a list of "issues" which would ordinarily be in a ticketing system of some kind, but are here on the Wiki instead, because that's how we roll. As things are resolved, they will be moved to the Discussion page. If there's an appeal or an issue, the conversation can continue there - this page will be for open issues.

Use of case in URLS / links. I went through all the electronic format types pages, and tried to normalise all the pages where I could (there was a mix of link structures - I've tried to get them all (apart from animation - I've been at it all day!) so they are [[file extension]] - [[file type name]].
I notice that we have a mix of upper and lower case file extension through out. This means we may have 2 links which should point to the same URL (e.g. [[mix]] and [[MIX]]) is this a known issue with the current layout? --[[User:JaygattusoNLNZ|JaygattusoNLNZ]] ([[User talk:JaygattusoNLNZ|talk]]) 01:32, 20 November 2012 (UTC)
:Since you're linking both the extension and the name, does that mean that there are supposed to be separate articles for each? I don't know if there's really a need for "mainspace" articles by extension, since there are already categories for that purpose; you can browse them through [[:Category:File formats by extension]]. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 02:12, 20 November 2012 (UTC)
::I just copied the most common model that I found on the formats pages. The problem is, if you don't homogenize the method, the linking/crosslinking doesn't work properly. All instances of .doc (for example) should point to the same resource page / disambiguation page. If someone has linked to only format in one place (e.g. [[MS Word]] (.doc)), and someone else the extension (MS Word - [[doc]]), we can't makes sure they point to the same place. The problem occurs because format names and extensions are used interchangeably. You raise an interesting question about the relationship between the ext and the format name. I would argue they are not equal (1:1), nor (1:many) / (many:1) so it makes sense to protect both aspects as definable things - the extension because that's whats most commonly searched for and referred to by users and 'format name' because its more accurate. How is the [[:Category:File formats by extension]] populated? --[[User:JaygattusoNLNZ|JaygattusoNLNZ]] ([[User talk:JaygattusoNLNZ|talk]]) 18:31, 20 November 2012 (UTC)
:::The categories are inserted when you use the ext template in the infobox. My preference is to have articles by actual format name and use multiple navigation aids (menus, cats, etc.) to get to them. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 01:38, 21 November 2012 (UTC)

== Article naming convention ==

As mentioned above, there's some dispute over whether to name articles after the full name of a format or its file extension. If using full names, you then get into issues of whether to use the full technical name or a shorter thing that's more popularly used, and in some cases that's even the same as the extension (GIF, for instance). And you also get into tricky issues of capitalization: all-caps like an acronym, all-lowercase like filenames are often done (though this is OS-dependent; some, like MS-DOS, use all-uppercase), or mixed case (proper names capitalized)? And then there's the disambiguation issue of how to name articles on different things that have the same name, which happens sometimes even with long official names, but even more often with short acronyms and file extensions. But there's also yet another issue of which things get separate articles and which are combined, like formats that have had many different versions, etc.

Currently you have things like [[CI]] and [[CT]], recently-created articles that represent two different file types within the data of one type of music tracker. The spec document they link to is the same one, which documents all the file types used in that tracker. Unless there's going to be really a lot to say about each of the specific file types, my own preference would be to have one article called [[CyberTracker]] that discusses all the formats used by the program in question, with subheaders within the article for the different file types, and all the extensions listed in the infobox (and hence in associated categories). If any other indices by extension are built up, they'd also have entries for both CI and CT. For instance, when I documented [[Softdisk Family Tree]], I covered all the various file formats in one article, though there are several versions and multiple files for each. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:39, 21 November 2012 (UTC)
: I realise I'm as guilty of this as anyone, having used both forms at some point (e.g. [[Surprise! Adlib Tracker v2.0]] and [[CI]]). Indeed, the two articles - [[CI]] and [[CT]] - you refer to were created by me. I guess in general I would favour using a descriptive page name rather than simply the file extension - that seems to be something that's being taken care of by infoboxes and categories.

:On the issue of what gets a separate page and what doesn't, I guess that just comes down to individual discretion. There will be instances where a format has undergone a number of minor revisions over time or has a number of minor variants (e.g. the variant forms of Chaos Music Composer's [[CMC]]) where it would make sense to keep them all to a single page, while a major revision would necessitate a multi-page approach (e.g. the shift with Capella from the binary [[CAP]] to the XML-based [[CapXML]] format).

:However, I'm not sure I agree with [[CI]] and [[CT]] having a single [[CyberTracker]] page. While both link to the same spec document and both are used by the same program, they are different formats serving different purposes. I think in general we should try and distinguish between program and file format - [[S3M]] doesn't belong on the [[ScreamTracker]] page, although each should link to the other. [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 14:04, 21 November 2012 (UTC)

:Since the purpose of the wiki is to document file formats, I think it's good that as many formats as possible are listed in the category pages and that you can browse these pages for format extensions. Sometimes it might be better to link multiple extension to the same article (e.g. a specific application), but not always. I think it is difficult to come up with a strict rule for this (but maybe recommendations and, even better, good examples). --[[User:PN|PN]] ([[User talk:PN|talk]]) 15:08, 21 November 2012 (UTC)

::It's a judgment call, certainly. It depends on how the files are typically encountered, distributed, used, etc., and how they're thought of by people who use them; if a bunch of file types related to a particular program are usually found together as part of a larger data set, they most likely belong together in one article (with subsections to describe the function of the particular files), but if they're distinct entities with their own particular treatment (like separate areas of file trading sites for enthusiasts) they should have separate articles, though more descriptive names like "CyberTracker instrument file" might be better than a cryptic and likely ambiguous CI. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 15:46, 21 November 2012 (UTC)
::And then, somebody has also used a robot to create pages in a separate namespace devoted to file extensions, like [[Ext:cin]]. That's yet another navigational system for getting to information by extension, though those pages oddly don't actually have direct links to the normal pages here about those file formats. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 15:56, 21 November 2012 (UTC)
::: Yes, that was me with Bender the bot. Still experimenting with it and working on creating a list of all pages in relation to extensions. [[User:Maurice.de.rooij|Maurice.de.rooij]] ([[User talk:Maurice.de.rooij|talk]]) 15:22, 22 November 2012 (UTC)
::What I'd like to avoid is the messy format somebody did to a few index pages like [[Compression]], where each line has separately hyperlinked format names and extensions (not always in a consistent order) where often one or the other is a redlink, or one redirects to the other, or one is just a disambiguation page, making a somewhat confusing hodgepodge. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:22, 21 November 2012 (UTC)
:::I've started rearranging the Compression page to be a little less messy. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:56, 22 November 2012 (UTC)

== So now what? ==
The official month of this project is now over... what are the plans for the site now? It's made a good start at documenting file formats, but has a good long way to go yet. (A project like this can never possibly be "finished", since there are always more file formats coming out of the woodwork, both new ones that are introduced, and old ones that are discovered.) [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 05:10, 1 December 2012 (UTC)
: This is an awesome project and I will stay committed to it. Of course this first month is just a start. Let's roll people! [[User:Maurice.de.rooij|Maurice.de.rooij]] ([[User talk:Maurice.de.rooij|talk]]) 23:22, 3 December 2012 (UTC)

== Anybody else still around? ==
Everybody else seems to have vanished around the middle of December... I'm the only one editing here lately. I hate to put more effort into improving a ghost town... anyone else even reading this? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 23:16, 2 January 2013 (UTC)

: I will be editing more once I get back to work - still don't have a home internet connection and working from the local library computers / girlfriend's netbook over public wi-fi is a pain. It would be nice to see more contributions from others - you can see how much work is left to do on the music section alone, and I've really only been creating stub entries for most things. [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 13:51, 3 January 2013 (UTC)

:Well, I still stop by on occasion, and I've vowed to use the site as my first stop when I come across a file format I don't recognize, but I never made any substantial additions, so I'm not sure if that gives you any useful information. (My edits were mostly technical or editorial.) [[User:Gphemsley|GPHemsley]] ([[User talk:Gphemsley|talk]]) 00:18, 13 January 2013 (UTC)

:I'll be editing from time-to-time. Currently a bit snowed under with other work, but planning to do more later in the year. Would also like to review the InfoBox(es) at some point, to ensure the information on this site can be reliably linked up to other information sources. [[User:AndyJackson|AndyJackson]] ([[User talk:AndyJackson|talk]]) 12:10, 18 January 2013 (UTC)

:I'm here. Like Andy, my workload is quite high, but I'll be popping in and out. --[[User:Rhetoric X|Rhetoric X]] ([[User talk:Rhetoric X|talk]]) 12:31, 18 January 2013 (UTC)

:Hi there! I sometimes add a word here or there. I must say this Wiki is pretty good now. Popular formats are nicely described and niche formats are just niche formats so it's sometimes hard to add anything about them. I think that maybe it would be helpful to start adding images to posts. An image explaining format details or a screenshot of an image editor may be a nice addition. What about algorithms in pseudo-code? --[[User:Tekkno|Tekkno]] ([[User talk:Tekkno|talk]]) 0:28, 7 September 2018 (UTC)

::A description of file formats and pseudo-codes would be helpful (although you do not necessarily need a picture). --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 05:19, 5 May 2019 (UTC)

== Spam ==

I see the spammers have found the site, as I worried would happen; I run a wiki myself ([http://mpedia.dan.info/ MPedia], about things related to Mensa) and have to constantly play whack-a-mole with them; even adding such annoyances (for legitimate users) as a captcha and e-mail confirmation seem to only slightly slow the spammers down. I don't know the solution. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 12:59, 18 January 2013 (UTC)

:...but "learn-to-read-Korean-in-15-minutes" is a legitimate addition, going to a comic strip explaining the [[Hangul]] writing system, which is in fact a legitimate article here since "file formats" is interpreted expansively to include human written languages. That link ''sounds'' a bit spammy, but if it was from a spammer, it would go to some page selling a dodgy language-learning tool, not a free-to-read resource! (It can start to get tricky distinguishing spam from legitimate stuff when you've got such a wide range of topics here to begin with! Once there's a huge flood of spam to get rid of, there's some danger of legitimate users getting caught in the net too.) [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:03, 18 January 2013 (UTC)

::Yes, it's incumbent on me to make sure we can have people sign up, and be a part of it, without getting spammers. We'll keep exploring. At least bots can't take us on.... I think.... --[[User:Jason Scott|Jason Scott]] ([[User talk:Jason Scott|talk]]) 19:28, 18 January 2013 (UTC)

:::If you've got some tips about how to configure MediaWiki to have open signups but not get the flood of spambots, let me know; that would help me with my own wiki. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 12:56, 22 January 2013 (UTC)

== Orphaned / Blank Pages ==

I've been making an attempt to clear up some of the orphaned pages, but there are a few I'm not sure of - maybe Dan or someone could sort them out?

* [[Emulation]]
* [[FAQ:File Format]]
* [[File format extensions list]] (seems to be used for the "ext:" pages but hasn't been updated)
* [[Library]]
* [[Original Plan]]
* [[RAD Game Tools]] (should probably have the individual formats moved to appropriate sections)
* [[Statistica]] (clearly belongs in Scientific Data formats, but I'm not sure where)

I've also come across a few pages that should probably be deleted - either because they've been blanked at some point (I know I did this to a few pages) or because they contain data duplicated elsewhere.

* [[AA]]
* [[Compressed executable (.com)]]
* [[SAP]]
* [[Barnes & Noble Fixed-layout Format]]

[[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 10:41, 22 January 2013 (UTC)

:OK, I deleted those last three; I'll look at the others. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 12:58, 22 January 2013 (UTC)
:I put Statistica under "Mathematics" in the science category. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:02, 22 January 2013 (UTC)

Hi Dan, got another one for you - I merged the info from [[ODS files created by Microsoft Office 2007 SP2]] into the main [[OpenDocument Spreadsheet]] page. [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 13:59, 25 February 2013 (UTC)

Added Barnes & Noble to the list (made a bit of a mess and forgot about the rename feature) [[User:Johanvanderknijff|Johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 19:05, 21 April 2016 (UTC)

== Permissions for user pages ==

Is there any way we can get permission to delete sub-pages of our own user pages? I've been using mine to draft articles bit by bit, rather than release half-finished articles into the wild, and it would be nice to be able to remove the drafts once complete [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 12:43, 3 October 2013 (UTC)

:I'm not sure, but as an admin I can delete anything you ask. It might also be possible to use the Move function to move it directly into the intended place. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:45, 3 October 2013 (UTC)

== cd.textfiles.com ==
All the files on http://cd.textfiles.com/ disappeared a few days ago, breaking about a million links on this wiki. Does anyone have any information about that? [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 18:48, 25 January 2015 (UTC)

:As I recall from Jason's Twitter feed, he had some server problems, with most of his sites going down at least temporary, and most of them eventually coming back up, but maybe that one had a harder crash. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 19:50, 25 January 2015 (UTC)

== Broken image in footer ==
The "Creative Commons 0" image at the bottom of every page (https://www.mediawiki.org/w/skins/common/images/cc-0.png) is broken. Can that be fixed? [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 00:06, 10 July 2015 (UTC)
:Still broken 5 years later... Is this place even maintained? [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 23:23, 12 March 2021 (UTC)
::Ok so it appears it should probably be [https://licensebuttons.net/l/zero/1.0/88x31.png this image], it matches the 88x31px that the HTML claims the image would be if it was there. Who maintains this site so it can be fixed? [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 00:01, 13 March 2021 (UTC)
:::I guess that would be Jason Scott. I'm an admin, but if I have any ability to edit that part of the site I have no idea how. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 01:31, 13 March 2021 (UTC)

== Wikipedia links ==
At least in my geographical area, Wikipedia has been redirecting "http:" links to "https:". So, all of the <nowiki>[[Wikipedia:...]]</nowiki> links in this wiki are getting redirected. Could/should we change these links to use "https:" directly?

The magic "RFC" links like RFC 822 could also use https:, though the http: links still work. [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 00:10, 10 July 2015 (UTC)

== Google Code ==
We still have around 50 articles that link to Google Code. My understanding is that the next phase of Google Code's shutdown process will happen on 2016-01-25 (two weeks from today). It would be good to update as many of these as possible before then.
* [http://fileformats.archiveteam.org/index.php?title=Special%3ALinkSearch&target=http%3A%2F%2Fcode.google.com&namespace= links to http://code.google.com]
* [http://fileformats.archiveteam.org/index.php?title=Special%3ALinkSearch&target=https%3A%2F%2Fcode.google.com&namespace= links to https://code.google.com]
[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 21:05, 11 January 2016 (UTC)

== Cleanup of top-level categories ==
(Call for objections.) I want to do some cleanup of the [[:Category:Top Level Categories|top-level categories]], and make sure there's at least one category for virtually every article. (See [[Special:UncategorizedPages]].) My plans:
* A new "Meta" category, for articles about the File Formats Wiki (e.g. [[FAQ]], [[Original Plan]], [[Statement of Project]], [[Main Page]], ...).
* Rename the [[:Category:Geek humor|Geek humor]] category to "Humor"
* Remove the [[:Category:Computer facts|Computer facts]] category
* A new "Information" category, for relevant informative articles ([[Ontology]], [[Patents]], ...) that don't have a more suitable top-level category.
* Maybe someday: A category named "Devices", or "Hardware", or even "Things". Most computers and [[Networked devices]] just aren't formats, IMHO. (But I'm not going to delete the infobox from all the "Networked devices" articles. If we can't figure out a way to have infoboxes for nonformats, then I'll leave them be.)
[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 15:56, 1 June 2017 (UTC)

[[Category:Meta]]

== Love It! ==
Hi there, kudos to all you guys who helped create this valuable resource. Wikipedia is such a snob when it comes to detailed technical documentation so this wiki is a lifesaver. I added a few things to:

* [[SWF#Software]]
* [[FLA#Software]]
* [[BSON#Libraries]]

Thanks again!

PS: Can the "thumbs up" icon be changed to something better? Do you want me to design a possible logo?

[[User:Hgupta|Hgupta]] ([[User talk:Hgupta|talk]]) 05:42, 17 August 2017 (UTC)

:Nice work! As for the thumb icon, you'd have to ask Jason Scott, the owner of this site (and the one who put the thumb up). [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:02, 17 August 2017 (UTC)

:I support the idea of changing the logo. [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 16:08, 18 August 2017 (UTC)

== What time is it? ==
I'm making this edit at 17:10 UTC, but the timestamp is: [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 17:25, 2 May 2018 (UTC)
:"Does anybody really know what time it is; does anybody really care?" -- Chicago
[posted at 01:20 UTC; let's see when it thinks it is] [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 01:36, 3 May 2018 (UTC)

== Type / Creator codes ==

Curious what everyone's thoughts are on collecting Type/Creator Codes for Macintosh formats. There seems to be a few attempts at doing this around the webs. Is there a way here to gather them all into one area of the wiki? --[[User:Thorsted|Thorsted]] ([[User talk:Thorsted|talk]]) 17:46, 4 May 2019 (UTC)

* [[Wikipedia:Type_code|Type Code : Wikipedia]]
* [[Wikipedia:Creator_code|Creator Code : Wikipedia]]
* [http://www.lacikam.co.il/tcdb/ TCDBx unmaintained]
* [https://vintageapple.org/macprogramming/pdf/The_Programmers_Apple_Mac_Sourcebook_1989.pdf The Programmers Apple Mac Sourcebook]
* [https://www.macdisk.com/macsigen.php Mac Signatures]

:Maybe do it similar to how file extensions are handled, as an item in the infobox that links to a category? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 19:09, 4 May 2019 (UTC)

::An article for Mac type/creator codes has been on my to-do list for a while, so we could at least do that, and see if there's any interest in listing lots of codes there. Should it be one article, or two? FormatInfo already has a "type code" param that is supposed to be for the Mac code. Maybe we are supposed to make a "Type Code" template to go along with it, so we can do like "<nowiki>|type code={{Type Code|XXXX}}</nowiki>". [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 21:07, 4 May 2019 (UTC)

:::If they were listed in a single article as opposed to a series of categories, I don't see what there would be for a template would do. In that case, the text on the left side of the infobox could link to the list page (although this might be ugly). (It would be convenient if there was something between the complexity of the MediaWiki category system and a list page, but I don't think anything like that exists in a plain Mediawiki installation.) [[User:Effect2|Effect2]] ([[User talk:Effect2|talk]]) 21:30, 4 May 2019 (UTC)

::Even if they went into the infobox, the category system could potentially be left out out, as is currently done with FOURCCs and MIMETypes (the latter links to an external database, but whether anything is there is based on luck more than anything else, as there are so many unregistered mimetypes). These can still be found with the wiki's search feature. [[User:Effect2|Effect2]] ([[User talk:Effect2|talk]]) 21:13, 4 May 2019 (UTC)

:::And there's also the Creator Code, as noted above; that refers to what program created the file, so there might be several associated with one file type code (and several file type codes associated with one creator). Perhaps there needs to be a section of the article listing all the code values associated with a given format and/or program (depending on what's covered by the article). [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 21:44, 4 May 2019 (UTC)

::I like the idea of at least a uniform template for using codes within format descriptions. Since most of the files from the early macintosh days don't have an extension, unless they were cross platform and the Windows extension is used, then the only way to identify the file is from its Type/Creator code. I don't think Apple ever released the full registry, but some estimates are well over 50,000 entries.--[[User:Thorsted|Thorsted]] ([[User talk:Thorsted|talk]]) 03:24, 5 May 2019 (UTC)

== Reverse engineering formats ==
I am trying to reverse engineer some formats. Sometimes successfully, sometimes not. My most recent attempt is:
* http://fileformats.archiveteam.org/wiki/DGI_(Digi-Pic)

Maybe we can do this together instead of everyone here focusing on different things? Also is there a better way to discuss things than writing here?
[[User:Tekkno|Tekkno]] ([[User talk:Tekkno|talk]]) 01:39, 9 May 2019 (UTC)

:You should set up a NNTP for reverse engineering file formats discussions (if there isn't already the appropriaate newsgroup). (I had done some of my own reverse engineering file formats too, but I have not set up a NNTP to discuss them. I do have a NNTP server, so you can suggest newsgroups there if wanted, I suppose) --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 21:26, 23 August 2021 (UTC)

== CAPTCHA ==

AT is no longer on EFnet: https://archiveteam.org/index.php?title=Archiveteam:IRC#Special_ArchiveTeam_IRC_rules [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 02:57, 8 November 2020 (UTC)

: This is a pretty serious problem. Are there any plans to fix it? -[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 16:22, 12 November 2020 (UTC)

:: <del>Seems like it has been fixed, by removing the CAPTCHA altogether.</del> [2021-12-30 edit: I spoke too soon; still 'efnet'.] Let's all keep a keen eye out for spamdalism. [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 03:33, 23 November 2020 (UTC)

== [[special:interwiki]] ==
don't see it at [[special:specialpages]]? [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 02:57, 8 November 2020 (UTC)

== List of my idea what maybe should be added on ==
My idea of what things I think that probably should be added on (when someone has the information of it to add):
* TRON character encoding
* TRON Application Databus
* BANCStar
* C67 (music)
(I might add a few others later if I will remember some more later, too) --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 09:30, 31 July 2021 (UTC)

==Hello==
I’ve joined and made a few edits. Starting with the Linux page by modification of the attribution of Linux to iOS, which is BSD.
Mad a few tweaks to HLP by creating a page for the source file.
As a retro tech enthusiast I think I could help a bit on some of the older files. Especially tape and disk formats; then, and their modern emulation files. As well as format info.
You can take a look at the original writeup I did here [http://wiki.digital-digest.com/index.php?title=History_of_AV]. Thought it has errors and is considerably lacking many formats.

IPF (OS/2)

2022-08-23T20:29:54Z

LostinlodosR: Create page

{{FormatInfo
|formattype=electronic
|subcat=Help files
|extensions={{ext|ipf}}
}}

'''IPF'''
is the raw source markup for INF, CHM, and HLP files used in OS/2 and Dos-based Windows.
The format uses a variation of [[HTML]], which is then “compiled” into an indexed self contained web site that can be read offline.
The format is an early form of [[e-book]].

==Concerns==
The markup document itself can be compiled by any version of the supporting application. However, the Help format output changes slightly between Windows and OS/2. Further, each version of the used operating system includes minor changes to the Help Viewer and Info. General compatibility appears consistent though minor errors may occur when using an HLP, INF, or CHM file of another operating system version.
Backwards compatibility is often complete, however forward compatibility, using a newer file on an older version, will often result in garbage text appearing where tags are unknown.

[[Category:Hypermedia]]
[[Category:OS/2]]
[[Category:Windows]]

Linux

2022-08-23T20:06:17Z

LostinlodosR: /* Who uses Linux? */ adjustment

{|
|[[Software]]
| >
|[[Operating Systems]]
| >
|[[Linux]]
|}

'''Linux''' [https://www.linux.com/] is an operating system (OS) closely related to '''Unix''' [http://www.unix.org/]. Or, more technically, it's the kernel at the core of an operating system; it isn't of much use by itself without the various utility programs that are typcially packaged with the kernel, many of which came from the GNU project, so some tech people regard '''GNU/Linux''' as the proper term for the operating system as a whole. (Major "religious wars" get fought over this stuff.) Linux is an Open Source OS which means that anyone can access the original source code and modify it to suit their purposes. This has resulted in the many different flavors of Linux referred to as '''Distributions''' (distros) [http://distrowatch.com/]. Linux is noted for being supported by many free software packages that replace the proprietary software used in many operating systems. There are free and open source word processors for example.

== History: ==

Linux started as the '''GNU Project''' [https://www.gnu.org/] which produced many software/utility packages for a future OS they wished to develop. Linus Torvalds created the Linux kernal, the heart of the OS, in 1991. Torvalds combined his kernal with the GNU software and Linux was born. [https://www.cs.cmu.edu/~awb/linux.history.html] There are purists who say that the resulting operating system should properly be referred to as '''GNU/Linux''' instead of just Linux, in order to acknowledge its heritage.

== Who uses Linux? ==

Linux is a very small fraction (about 2%) of desktop computers worldwide, however it is a leader in cellphones and tablets, it being the core of the Android, which is the most used OS in the world overall. The [[Android]] mobile operating system and the related [[iOS|Apple iOS]], a BSD derivative, are the two major players in these markets. Additionally, the server market, in particular Internet Service Providers, is dominated by Unix and Linux machines with about 60% of that market.

== Linux as Utility ==

Many technicians supporting '''Microsoft Windows''' operating systems use a bootable '''Linux LiveCD/DVD''' [http://livecdlist.com/] to access hard drives to perform repairs and retrieve data that may be lost if their repair efforts require them to format and reinstall Windows. In addition, there are distros of Linux made and used to do computer forensic work, these are used by experienced computer security people to examine and clean up computers infected with viruses or malware.

== Pros and Cons of running Linux ==

'''PROS:'''
Linux, due to its architecture, doesn't require defragging. Being a very small part of the overall market share for desktop computers, there are few Linux viruses to contend with, the virus writers concentrate on the Windows platform. Linux installs are generally much smaller than Windows installs and can run on much older hardware. Many old Windows XP machines that cannot handle Windows 7 and beyond do well with a Linux install. Linux is a free OS, there is no direct cost to the user. It is a very stable OS.

'''CONS:'''
While many modern distros are user friendly out of the box, there is a significant learning curve with Linux. Many basic operations work differently and are a bit more complex on Linux. Additionally, there are some software packages, not many, that are unavailable for Linux users. There has been significant improvement in gaming for Linux of late, but many games are simply not available. There is a Windows compatibility layer for Linux, '''[[Wine]]''', [http://www.winehq.org/] but Windows software run in Wine doesn't always perform as well as it would in a native Windows environment (although sometimes they work better than a native Windows environment). There are also some hardware driver issues for Linux users that require advanced expertise at times to overcome. '''To put it in short, the main problem is you need to know what your doing.'''

== Links ==
* [https://www.kernel.org/ The Linux Kernel Archives]
* [http://archive.org/details/linux_distributions Archive of historical Linux distributions]
* [http://arstechnica.com/information-technology/2013/10/the-navys-newest-warship-is-powered-by-linux/ The Navy’s newest warship is powered by Linux]
* [http://www.extremetech.com/extreme/124287-the-worlds-slowest-linux-pc The world’s slowest Linux PC]
* [https://dmitry.gr/index.php?r=05.Projects&proj=07.%20Linux%20on%208bit Linux on an 8-bit micro]

[[Category:Operating Systems]]
[[Category:Software]]