Unified Emulator Format
From Just Solve the File Format Problem
(Difference between revisions)
DavidBoddie (Talk | contribs) (Changed the link to UEFtrans to refer directly to its home page.) |
DavidBoddie (Talk | contribs) |
||
| Line 10: | Line 10: | ||
* [http://mdfs.net/Docs/Comp/BBC/FileFormat/UEFSpecs.htm UEF specs] | * [http://mdfs.net/Docs/Comp/BBC/FileFormat/UEFSpecs.htm UEF specs] | ||
* [[Wikipedia:Unified Emulator Format|Wikipedia article]] | * [[Wikipedia:Unified Emulator Format|Wikipedia article]] | ||
| + | * [http://beebwiki.jonripley.com/Acorn_cassette_format Acorn cassette format] - covers physical and signal layers in addition to describing the block layer relevant to UEF images | ||
== Software == | == Software == | ||
* [http://www.boddie.org.uk/david/Projects/Emulation/UEFtrans UEFtrans: Python script to handle UEF data] | * [http://www.boddie.org.uk/david/Projects/Emulation/UEFtrans UEFtrans: Python script to handle UEF data] | ||
Revision as of 15:12, 7 January 2013
The Unified Emulator Format (UEF) is a format used to store raw tape, disk, and ROM data from Acorn computers, inclduing Kansas City Standard data cassettes, in a computer file suitable for storage and transfer on modern systems and networks. Since some other computer systems (e.g., the SOL-20) also use the Kansas City standard for cassettes, this format will also serve to archive cassette data for them, similarly to how a Tap file encodes Commodore cassettes.
References
- UEF specs
- Wikipedia article
- Acorn cassette format - covers physical and signal layers in addition to describing the block layer relevant to UEF images
