https://www.discferret.com/w/api.php?action=feedcontributions&user=Balrog&feedformat=atomDiscFerret - User contributions [en]2024-03-29T09:16:01ZUser contributionsMediaWiki 1.30.0https://www.discferret.com/w/index.php?title=Apple_DiskCopy_4.2&diff=422Apple DiskCopy 4.22018-01-21T05:59:41Z<p>Balrog: </p>
<hr />
<div>[[Category:Disc image files]]<br />
<br />
'''Attribution: This article was sourced from the 68kMLA Wiki at http://68kmla.org/wiki/DiskCopy_4.2_format_specification. Permission was given in IRC by Balrog and Lord Nightmare to copy the article here for safe-keeping.'''<br />
<br />
This article describes the '''file format for Apple Disk Copy 4.2''' .image files<br />
<br />
Much information comes from the [[CiderPress]] and [[Mini vMac]] source codes. More authoritative information comes from [http://www.nulib.com/library/FTN.e00005.htm nulib.com]. Some info on tags from [http://www.pagetable.com/?p=50 Inside Macintosh, 1st ed. page II-212]. This format is also used in DiskCopy 4.1. DiskCopy 6.3.3 uses a variant with tags omitted. DART is a variant which adds compression.<br />
<br />
==Resource fork notes==<br />
Disk Copy 4.2 files have a [[resource fork]], but it only contains a copy of the data and tag checksums and can be safely ignored; files without the fork will still work perfectly.<br />
<br />
* Disk copy 4.2 images have a type of 'dImg' and creator of 'dCpy', without these the program will not recognize the file; they can be easily added to images missing them with resedit.<br />
<br />
{| border="1" cellpadding="2"<br />
|+DC42 File format Overview<br />
|-<br />
!offset !! type/size !! contents<br />
|-<br />
|0x00||byte||Length of image name string ('Pascal name length')<br />
|-<br />
|0x01-0x3F||63 bytes||Image name, in ascii, padded with NULs<br />
|-<br />
|0x40-0x43||BE_UINT32||Data size in bytes (of block starting at 0x54)<br />
|-<br />
|0x44-0x47||BE_UINT32||Tag size in bytes (of block starting after end of Data block)<br />
|-<br />
|0x48-0x4B||BE_UINT32||Data Checksum<br />
|-<br />
|0x4C-0x4F||BE_UINT32||Tag Checksum<br />
|-<br />
|0x50||byte||Disk encoding<br />
|-<br />
|0x51||byte||Format Byte<br />
|-<br />
|0x52-0x53||BE_UINT16||'0x01 0x00' ('Private Word') AKA Magic Number<br />
|-<br />
|0x54-...||variable||Image data<br />
|-<br />
|...-EOF||variable||Tag data<br />
|}<br />
<br />
== Specifics of data fork sections ==<br />
=== 0x00: Length of image name string ===<br />
Technically this is part of the 0x01-0x3f area, as pascal strings apparently store their length as their first byte. Effectively the address of the last non-NUL byte of the image name. bytes after the end address are ignored, and sometimes are used to hold extra information, or hold garbage (in the case of the 1.44mb system 6.0.8 startup disk, this is leftovers in memory from the System Additions disk, so the string ends up being System Startupns)<br />
* Note: A special (bug) case happens when the disk name is "-not a Macintosh disk", which the name is set to when using dc42 on non-mac diskettes. In that case, the length is set one byte too high; this is probably a bug in dc42 that was just never fixed.<br />
<br />
=== 0x01-0x3F: Image name ===<br />
This is the image name string. It is copied from the volume name of the disk or diskette being imaged.<br />
<br />
=== 0x40-0x43: Data block size in bytes ===<br />
This has one of 4 values on most diskettes:<br />
00 06 40 00 (409600 bytes) for 400k GCR disks<br />
00 0c 80 00 (819200 bytes) for 800k GCR disks<br />
00 0b 40 00 (737280 bytes) for 720k MFM disks<br />
00 16 80 00 (1474560 bytes) for 1440k MFM disks<br />
<br />
=== 0x44-0x47: Tag size in bytes ===<br />
This is typically 12 bytes for every 512 bytes in the image, apparently stored in the data mark in each sector on the media. The format for Tag data is described at the bottom of the document, and is important for repairing damaged disks using disk doctor. It is also very important on Lisa Diskettes (according to LisaEM source).<br />
00 00 25 80 (9600 bytes) for 400k disks w/tags<br />
00 00 4b 00 (19200 bytes) for 800k disks w/tags<br />
00 00 00 00 for diskettes with no tags<br />
<br />
=== 0x48-0x4B: Data Checksum ===<br />
The algorithm for this is: start with 00000000, add each consecutive 16 bit Big Endian word of the section, then rotate the 32 bit result right by 1 bit.<br />
<br />
=== 0x4c-0x4F: Tag Checksum ===<br />
The algorithm for this is the same as for the data, however the first 12 bytes of the tag section, if present, are skipped (probably due to a bug in an older disk copy version and kept for compatibility).<br />
* Tag Checksum is 00 00 00 00 if no tag data is present.<br />
<br />
=== 0x50: Disk encoding ===<br />
This byte describes the encoding used for the disk the data was imaged from, from a 'what type of disk is this?' perspective.<br />
00 = GCR CLV ssdd (400k)<br />
01 = GCR CLV dsdd (800k)<br />
02 = MFM CAV dsdd (720k)<br />
03 = MFM CAV dshd (1440k)<br />
Other encodings may exist, as DC42 was originally designed to be able to image HD20 disks.<br />
<br />
=== 0x51: Format Byte ===<br />
This byte has one of two meanings, depending on whether the disk is GCR format 400k or 800k, or MFM format. The byte is completely ignored for the rare GCR-on-HD format (which always has a 1:1 interleave and is always 2 sided).<br />
* If disk is GCR format 400k or 800k:<br />
This byte is a copy of the GCR format nybble (6 bits),<br />
which appears in the headers of every GCR sector.<br />
$02 = Mac 400k<br />
$12 = Lisa 400k (observed, documentation error claims this is for mac 400k disks, but this is wrong)<br />
$22 = Disk formatted as Mac 800k<br />
$24 = Disk formatted as Prodos 800k (AppleIIgs format)<br />
$96 = INVALID (Disk was misformatted or had GCR 0-fill (0x96 which represents data of 0x00)<br />
written to its format byte)<br />
Values for bitfield:<br />
76543210<br />
||||||||<br />
|||\\\\\- These 5 bits are sector interleave factor:<br />
||| setting of 02 means 2:1 interleave: 0 8 1 9 2 10 3 11 4 12 5 13 6 14 7 15<br />
||| setting of 04 means 4:1 interleave: 0 4 8 12 1 5 9 13 2 6 10 14 3 7 11 15<br />
||\------ This bit indicates whether a disk is 2 sided or not. 0 = 1 sided, 1 = 2 sided.<br />
\\------- always 0, as GCR nybbles are only 6 bits<br />
*If disk is MFM format:<br />
This byte is used to define MFM sector size and whether the disk is<br />
two sided or not.<br />
Interleave is ALWAYS 1:1 for these formats.<br />
$22 = double-sided MFM diskettes with 512 byte sectors<br />
Values for bitfield:<br />
76543210<br />
||||||||<br />
|||\\\\\- These 5 bits are sector size as a multiple of 256 bytes<br />
||| i.e. 02 = 2*256 = 512 bytes per sector<br />
||\------ This bit indicates whether a disk is 2 sided or not. 0 = 1 sided, 1 = 2 sided.<br />
\\------- unused, always 0<br />
<br />
=== 0x52-0x53: Private Word/Magic Number ===<br />
This is more or less the 'magic number' of any DC42 format file; if it is not $01 $00, it is not a DC42 format file.<br />
<br />
=== 0x54-...: Image data ===<br />
The size in bytes of the data stored here is the value at 0x40-0x43.<br />
<br />
=== ...-EOF: Tag data ===<br />
The size in bytes of the data stored here is the value at 0x44-0x47.<br />
<br />
== Tag Data format ==<br />
The tag data is 12 bytes per 512-byte disk sector, and is stored, like the Image data, in sector order.<br />
The actual format for each 12-byte block of the Tag data differs for Lisa, MFS and HFS disks,<br />
and for MFS or HFS any of them may be wrong or absent! be warned!<br />
* The Tag format for Lisa 400k or 800k disks is currently unknown, but without tags the disks will not function.<br />
*For MFS filesystems the Tag format is as follows:<br />
BE WARNED: when reading tag data, if the bit at 00 40 00 00 of any of the 3 32 bit words of the tag is set, the tag<br />
data for the sector it is part of is trashed and can be ignored. There IS a puprose to the data written when 0x40 is set, I'm just not sure what it is.<br />
offset type/size contents<br />
0x00 BE_UINT32 File number on disk, within MFS filesystem<br />
0x04 BE_UINT16 Flags bitfield:<br />
FEDCBA98 76543210<br />
|||||||| ||||||||<br />
|||||||| |||\\\\\- unknown, seems unused<br />
|||||||| ||\------ If set, Tag for this sector is not valid.<br />
|||||||| \\------- unknown<br />
|||||||\---------- sector content type: 0: system file; 1: user file (guessed)<br />
||||||\----------- sector is part of a: 0: data fork; 1: resource fork<br />
|\\\\\------------ unknown<br />
\----------------- unknown, sometimes set on the last few sectors of a data or resource fork<br />
0x06 BE_UINT16 Logical block number within the file<br />
0x08 BE_UINT32 Time of last modification, in seconds since 0:00:00, 1/1/1904<br />
Note that the last mod time may be different on the final sector of a file; this may indicate something special.</div>Balroghttps://www.discferret.com/w/index.php?title=Merlin2&diff=420Merlin22012-07-17T01:09:31Z<p>Balrog: </p>
<hr />
<div>Merlin 2 is the next-generation analysis software. Work on it is slated to start soon.<br />
<br />
The initial version will be focused on acquiring and decoding unprotected/standard-format disks, since this is what most people need. It should be easy to use — the user should not need to be an expert.<br />
<br />
The intended goal of the software (not the initial release) is for analyzing more difficult disks — whether slightly damaged, copy protected, of an unknown format, or whatnot.<br />
<br />
Current planned features:<br />
<br />
* There should be an easy way of loading one or more DFI (or other) flux images. Direct acquisition from the device should also be supported<br />
* It should be possible to select multiple tracks to work on at a time, and to mask/filter unwanted tracks.<br />
* Charts should be available, much like in the current Merlin1 prototype. It should be possible to "layer" multiple reads or multiple tracks, to correlate them (this would be useful for weak-bit protection as well as spiral-track protection, as well as for failing disks).<br />
* A hex viewer should be available, showing the on-disk data using the selected decoder.<br />
** Since the decode pipeline has multiple steps, it should be possible to view the "data" at any of these. So for example, GCR nybbles should be viewable, as well as decoded headers+data.<br />
* Multiple data separator algorithms should be available (I believe philpem did some work on this).<br />
** As a starting point: Naive (windowing), Adaptive Windowing, PJL-DPLL<br />
* It should be relatively easy to add a new format decoder (use a scripting language maybe, python?).<br />
<br />
* Tool must be cross platform and easy enough to use — run on Windows, Mac, and Linux, as well as other POSIX-compliant operating systems.<br />
** Current plan is to use a cross platform toolkit like wxWidgets, perhaps using wxPython — need feedback here.</div>Balroghttps://www.discferret.com/w/index.php?title=Merlin2&diff=419Merlin22012-06-26T17:33:03Z<p>Balrog: </p>
<hr />
<div>Merlin 2 is the next-generation analysis software. Work on it is slated to start soon.<br />
<br />
The initial version will be focused on acquiring and decoding unprotected/standard-format disks, since this is what most people need. It should be easy to use — the user should not need to be an expert.<br />
<br />
This is for analyzing more difficult disks — whether slightly damaged, copy protected, of an unknown format, or whatnot.<br />
<br />
Current planned features:<br />
<br />
* There should be an easy way of loading one or more DFI (or other) flux images. Direct acquisition from the device should also be supported<br />
* It should be possible to select multiple tracks to work on at a time, and to mask/filter unwanted tracks.<br />
* Charts should be available, much like in the current Merlin1 prototype. It should be possible to "layer" multiple reads or multiple tracks, to correlate them (this would be useful for weak-bit protection as well as spiral-track protection, as well as for failing disks).<br />
* A hex viewer should be available, showing the on-disk data using the selected decoder.<br />
** Since the decode pipeline has multiple steps, it should be possible to view the "data" at any of these. So for example, GCR nybbles should be viewable, as well as decoded headers+data.<br />
* Multiple data separator algorithms should be available (I believe philpem did some work on this).<br />
** As a starting point: Naive (windowing), Adaptive Windowing, PJL-DPLL<br />
* It should be relatively easy to add a new format decoder (use a scripting language maybe, python?).<br />
<br />
* Tool must be cross platform and easy enough to use — run on Windows, Mac, and Linux, as well as other POSIX-compliant operating systems.<br />
** Current plan is to use a cross platform toolkit like wxWidgets, perhaps using wxPython — need feedback here.</div>Balroghttps://www.discferret.com/w/index.php?title=Apple_II_GCR&diff=417Apple II GCR2012-05-20T01:03:30Z<p>Balrog: added rwts18 format interleave info</p>
<hr />
<div>The Apple II provides very fine-grained control of the drive from software, so various kinds of schemes were devised.<br />
<br />
A discussion of how the Disk II works: http://www.metafilter.com/114962/jmp-TRIGSPIKES#4301468<br />
<br />
There are two "standard" Apple II GCR formats, 13-sector and 16-sector. Both are explained in detail in Beneath Apple DOS.<br />
<br />
http://www.classiccmp.org/cini/pdf/Apple/Beneath%20Apple%20DOS.pdf<br />
<br />
<br />
Prince of Persia and other software used a format called RWTS18, designed by Roland Gustafsson to pack the maximum possible data onto a disk. Some details can be seen here:<br />
<br />
http://pastie.org/private/mivibuirv3nomrqndjblcw<br />
<br />
Not everything in that old cracking guide is accurate. For example, normal-speed drives were used to write RWTS18 disks.<br />
<br />
RWTS18 disks interleave the GCR 6+2 data to make it possible to stream the bytes, without having to use a buffer to decode. Apparently Tangled Tales used the same format (probably stolen RWTS18 routines, though possibly licensed). See the Tangled Tales guide at http://www.textfiles.com/apple/CRACKING/tangled.txt for details.<br />
<br />
More will be added soon.<br />
<br />
<br />
[[Category:Disc formats]]</div>Balroghttps://www.discferret.com/w/index.php?title=Merlin2&diff=416Merlin22012-05-20T00:56:34Z<p>Balrog: </p>
<hr />
<div>Merlin 2 is the next-generation analysis software. Work on it is slated to start soon.<br />
<br />
Current planned features:<br />
<br />
<br />
Merlin2 analysis software:<br />
<br />
This is for analyzing more difficult disks — whether slightly damaged, copy protected, of an unknown format, or whatnot.<br />
<br />
There should be an easy way of loading one or more DFI (or other) flux images. Direct acquisition from the device should also be supported<br />
It should be possible to select multiple tracks to work on at a time, and to mask/filter unwanted tracks.<br />
Charts should be available, much like in the current Merlin1 prototype. It should be possible to "layer" multiple reads or multiple tracks, to correlate them (this would be useful for weak-bit protection as well as spiral-track protection, as well as for failing disks).<br />
A hex viewer should be available, showing the on-disk data using the selected decoder.<br />
:Since the decode pipeline has multiple steps, it should be possible to view the "data" at any of these. So for example, GCR nybbles should be viewable, as well as decoded headers+data.<br />
Multiple data separators should be available (I believe philpem did some work on this).<br />
It should not be too difficult to add a new decoder (use a scripting language maybe, python?).<br />
<br />
Tool must be cross platform and easy enough to use — run on Windows, Mac, and Linux, as well as other POSIX-compliant operating systems.<br />
Current plan is to use a cross platform toolkit like wxWidgets, perhaps using wxPython — need feedback here.</div>Balroghttps://www.discferret.com/w/index.php?title=Merlin2&diff=415Merlin22012-05-20T00:55:15Z<p>Balrog: </p>
<hr />
<div>Merlin 2 is the next-generation analysis software. Work on it is slated to start soon.<br />
<br />
Current planned features:<br />
<br />
<br />
Merlin2 analysis software:<br />
<br />
This is for analyzing more difficult disks — whether slightly damaged, copy protected, of an unknown format, or whatnot.<br />
<br />
There should be an easy way of loading one or more DFI (or other) flux images. Direct acquisition from the device should also be supported<br />
It should be possible to select multiple tracks to work on at a time, and to mask/filter unwanted tracks.<br />
Charts should be available, much like in the current Merlin1 prototype. It should be possible to "layer" multiple reads or multiple tracks, to correlate them (this would be useful for weak-bit protection as well as spiral-track protection, as well as for failing disks).<br />
A hex viewer should be available, showing the on-disk data using the selected decoder.<br />
:Since the decode pipeline has multiple steps, it should be possible to view the "data" at any of these. So for example, GCR nybbles should be viewable, as well as decoded headers+data.<br />
Multiple data separators should be available (I believe philpem did some work on this).<br />
It should not be too difficult to add a new decoder (use a scripting language maybe, python?).<br />
<br />
Tool must be cross platform and easy enough to use — run on Windows, Mac, and Linux, as well as other POSIX-compliant operating systems.</div>Balroghttps://www.discferret.com/w/index.php?title=Merlin2&diff=414Merlin22012-05-20T00:54:41Z<p>Balrog: </p>
<hr />
<div>Merlin 2 is the next-generation analysis software. Work on it is slated to start soon.<br />
<br />
Current planned features:<br />
<br />
<br />
Merlin2 analysis software:<br />
<br />
This is for analyzing more difficult disks — whether slightly damaged, copy protected, of an unknown format, or whatnot.<br />
<br />
There should be an easy way of loading one or more DFI (or other) flux images. Direct acquisition from the device should also be supported<br />
It should be possible to select multiple tracks to work on at a time, and to mask/filter unwanted tracks.<br />
Charts should be available, much like in the current Merlin1 prototype. It should be possible to "layer" multiple reads or multiple tracks, to correlate them (this would be useful for weak-bit protection as well as spiral-track protection, as well as for failing disks).<br />
A hex viewer should be available, showing the on-disk data using the selected decoder.<br />
Since the decode pipeline has multiple steps, it should be possible to view the "data" at any of these. So for example, GCR nybbles should be viewable, as well as decoded headers+data.<br />
Multiple data separators should be available (I believe philpem did some work on this).<br />
It should not be too difficult to add a new decoder (use a scripting language maybe, python?).<br />
<br />
Tool must be cross platform and easy enough to use — run on Windows, Mac, and Linux, as well as other POSIX-compliant operating systems.</div>Balroghttps://www.discferret.com/w/index.php?title=Merlin2&diff=413Merlin22012-05-20T00:54:28Z<p>Balrog: Created page with "Merlin 2 is the next-generation analysis software. Work on it is slated to start soon. Current planned features: Merlin2 analysis software: This is for analyzing more difficu..."</p>
<hr />
<div>Merlin 2 is the next-generation analysis software. Work on it is slated to start soon.<br />
<br />
Current planned features:<br />
<br />
<br />
Merlin2 analysis software:<br />
<br />
This is for analyzing more difficult disks — whether slightly damaged, copy protected, of an unknown format, or whatnot.<br />
<br />
There should be an easy way of loading one or more DFI (or other) flux images. Direct acquisition from the device should also be supported<br />
It should be possible to select multiple tracks to work on at a time, and to mask/filter unwanted tracks.<br />
Charts should be available, much like in the current Merlin1 prototype. It should be possible to "layer" multiple reads or multiple tracks, to correlate them (this would be useful for weak-bit protection as well as spiral-track protection, as well as for failing disks).<br />
A hex viewer should be available, showing the on-disk data using the selected decoder.<br />
- Since the decode pipeline has multiple steps, it should be possible to view the "data" at any of these. So for example, GCR nybbles should be viewable, as well as decoded headers+data.<br />
Multiple data separators should be available (I believe philpem did some work on this).<br />
It should not be too difficult to add a new decoder (use a scripting language maybe, python?).<br />
<br />
Tool must be cross platform and easy enough to use — run on Windows, Mac, and Linux, as well as other POSIX-compliant operating systems.</div>Balroghttps://www.discferret.com/w/index.php?title=DiscFerret&diff=410DiscFerret2012-05-01T05:35:46Z<p>Balrog: </p>
<hr />
<div>'''The first prototypes of the DiscFerret hardware are now in the hands of developers -- we're aiming for full production around mid-Summer or early Autumn! Keep checking back, and feel free to join us in [http://webchat.freenode.net/?channels=discferret #discferret on irc.freenode.net]'''<br />
<br />
'''If you're interested in developing software for the DiscFerret, or even just testing it and providing us with feedback, please contact Phil at phil@discferret.com. Parts are being procured, and several Limited Pre-production (LPP) units will be assembled for sale within the coming weeks. Get your orders in early, they're sure to sell out fast!'''<br />
<br />
DiscFerret is a combination of hardware and software that allows a standard desktop computer to read, analyse and decode the data on almost any floppy disc, and most MFM and RLL hard disc drives. This includes standard formats like PC DOS, but also more unusual formats like AmigaDOS, Apple (II and Mac GCR), Commodore 64, and also more esoteric formats like those used on the Intel MDS/ISIS, Northstar and Sirius-Victor 9000 platforms. Imaging is performed at the lowest possible level -- that of magnetic transitions, which allows everything which can be represented on-disc to be imaged for later analysis.<br />
<br />
The source code and CAD files for the DiscFerret design are completely open-sourced: the hardware and software are released under the GNU GPL (in the case of the [http://hg.discferret.com/hardware/file/tip/LICENSE board], [http://hg.discferret.com/microcode/file/tip/COPYING microcode], and [http://hg.discferret.com/firmware/file/tip/COPYING firmware]) or the Apache Public Licence (in the case of the [http://hg.discferret.com/C-API/file/tip/LICENSE DiscFerret Hardware Access Library]).<br />
<br />
An IRC channel for support and development has been established. Please join us in [irc://irc.freenode.net/#discferret #discferret on irc.freenode.net].<br />
<br />
<br />
[[File:Discferret_board_component_side_HD_c.png|center|600px|DiscFerret board]]<br />
<br />
== News ==<br />
2012-APR-17 -- We've been helping out the Prince of Persia Source Code Recovery Project! The DiscFerret Project supplied a DiscFerret 1A24 prototype unit, which successfully produced images of several source code disks. We're now hard at work analysing and decoding the contents of these images... See the '[https://twitter.com/#!/search/%23popsource #popsource]' hash-tag on Twitter for more information! -- [[User:Philpem|Philpem]] 22:30, 17 April 2012 (BST)<br />
<br />
2012-JAN-11 -- DiscFerret Microcode 0028 and C API v1.5 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. These releases fix several critical microcode bugs -- users should update to these releases as soon as possible. --[[User:Philpem|Philpem]] 21:50, 11 January 2012 (GMT)<br />
<br />
2011-DEC-31 -- DiscFerret Microcode 0026 and C API v1.3 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. [[User:Philpem|Philpem]] 21:43, 31 December 2011 (GMT)<br />
<br />
2011-DEC-23 -- DiscFerret development has now resumed after a "brief" hiatus. Microcode updates are on the [[DiscFerret:Downloads|Downloads]] page, and the source code is available from the usual place (http://hg.discferret.com/). --[[User:Philpem|Philpem]] 02:44, 23 December 2011 (GMT)<br />
<br />
2011-MAR-21 -- The DiscFerret now supports 8-inch disc drives. Support has been added to Microcode 0x0021; the source code for this is in the "microcode" repository. -- [[User:Philpem|Philpem]] 01:22, 21 March 2011 (GMT)<br />
<br />
== Links ==<br />
<br />
* [[DiscFerret:FAQ|FAQ]]<br />
* [[DiscFerret:Downloads|Downloads]]<br />
<br />
* [[:Category:Disc formats|Disc format documentation]]<br />
* [[:Category:Disc image files|Image file format documentation]]</div>Balroghttps://www.discferret.com/w/index.php?title=DFI_image_format_revision&diff=407DFI image format revision2012-04-26T04:17:00Z<p>Balrog: /* EA IFF 1985 */ added documentation</p>
<hr />
<div>'''Comments below are based on the [http://www.discferret.com/DFIFileFormat_20120331.pdf March 31, 2012 version].'''<br />
<br />
== EA IFF 1985 ==<br />
<br />
* Is there existing documentation readily available on the format?<br />
<br />
http://www.digitalpreservation.gov/formats/fdd/fdd000115.shtml<br />
http://www.martinreddy.net/gfx/2d/IFF.txt<br />
<br />
== 6.1. EIGHTCC code descriptor ==<br />
<br />
* '''Safe to copy flag''': what is the use case as defining something as not safe to copy?<br />
<br />
== METADATA chunk ==<br />
<br />
* Should allow for arbitrary user-defined metadata elements in addition to predefined set</div>Balroghttps://www.discferret.com/w/index.php?title=Apple_II_GCR&diff=400Apple II GCR2012-04-21T13:48:22Z<p>Balrog: </p>
<hr />
<div>The Apple II provides very fine-grained control of the drive from software, so various kinds of schemes were devised.<br />
<br />
A discussion of how the Disk II works: http://www.metafilter.com/114962/jmp-TRIGSPIKES#4301468<br />
<br />
There are two "standard" Apple II GCR formats, 13-sector and 16-sector. Both are explained in detail in Beneath Apple DOS.<br />
<br />
http://www.classiccmp.org/cini/pdf/Apple/Beneath%20Apple%20DOS.pdf<br />
<br />
<br />
Prince of Persia and other software used a format called RWTS18, designed by Roland Gustafsson to pack the maximum possible data onto a disk. Some details can be seen here:<br />
<br />
http://pastie.org/private/mivibuirv3nomrqndjblcw<br />
<br />
Not everything in that old cracking guide is accurate. For example, normal-speed drives were used to write RWTS18 disks.<br />
<br />
More will be added soon.<br />
<br />
<br />
[[Category:Disc formats]]</div>Balroghttps://www.discferret.com/w/index.php?title=Apple_II_GCR&diff=399Apple II GCR2012-04-21T13:48:04Z<p>Balrog: </p>
<hr />
<div>The Apple II provides very fine-grained control of the drive from software, so various kinds of schemes were devised.<br />
<br />
A discussion of how the Disk II works: http://www.metafilter.com/114962/jmp-TRIGSPIKES#4301468<br />
<br />
There are two "standard" Apple II GCR formats, 13-sector and 16-sector. Both are explained in detail in Beneath Apple DOS.<br />
<br />
http://www.classiccmp.org/cini/pdf/Apple/Beneath%20Apple%20DOS.pdf<br />
<br />
<br />
Prince of Persia and other software used a format called RWTS18, designed by Roland Gustafsson to pack the maximum possible data onto a disk. Some details can be seen here:<br />
<br />
http://pastie.org/private/mivibuirv3nomrqndjblcw<br />
<br />
Not everything in that old cracking guide is accurate. For example, normal-speed drives were used to write RWTS18 disks.<br />
<br />
More will be added soon.<br />
<br />
<br />
[[Category:Disc_Formats]]</div>Balroghttps://www.discferret.com/w/index.php?title=Apple_II_GCR&diff=398Apple II GCR2012-04-21T13:47:40Z<p>Balrog: </p>
<hr />
<div>The Apple II provides very fine-grained control of the drive from software, so various kinds of schemes were devised.<br />
<br />
A discussion of how the Disk II works: http://www.metafilter.com/114962/jmp-TRIGSPIKES#4301468<br />
<br />
There are two "standard" Apple II GCR formats, 13-sector and 16-sector. Both are explained in detail in Beneath Apple DOS.<br />
<br />
http://www.classiccmp.org/cini/pdf/Apple/Beneath%20Apple%20DOS.pdf<br />
<br />
<br />
Prince of Persia and other software used a format called RWTS18, designed by Roland Gustafsson to pack the maximum possible data onto a disk. Some details can be seen here:<br />
<br />
http://pastie.org/private/mivibuirv3nomrqndjblcw<br />
<br />
Not everything in that old cracking guide is accurate. For example, normal-speed drives were used to write RWTS18 disks.<br />
<br />
More will be added soon.<br />
<br />
<br />
[[Category:Disc Formats]]</div>Balroghttps://www.discferret.com/w/index.php?title=Apple_II_GCR&diff=397Apple II GCR2012-04-21T13:46:32Z<p>Balrog: Created page with "The Apple II provides very fine-grained control of the drive from software, so various kinds of schemes were devised. A discussion of how the Disk II works: http://www.metafilte..."</p>
<hr />
<div>The Apple II provides very fine-grained control of the drive from software, so various kinds of schemes were devised.<br />
<br />
A discussion of how the Disk II works: http://www.metafilter.com/114962/jmp-TRIGSPIKES#4301468<br />
<br />
There are two "standard" Apple II GCR formats, 13-sector and 16-sector. Both are explained in detail in Beneath Apple DOS.<br />
<br />
http://www.classiccmp.org/cini/pdf/Apple/Beneath%20Apple%20DOS.pdf<br />
<br />
<br />
Prince of Persia and other software used a format called RWTS18, designed by Roland Gustafsson to pack the maximum possible data onto a disk. Some details can be seen here:<br />
<br />
http://pastie.org/private/mivibuirv3nomrqndjblcw<br />
<br />
Not everything in that old cracking guide is accurate. For example, normal-speed drives were used to write RWTS18 disks.<br />
<br />
More will be added soon.</div>Balroghttps://www.discferret.com/w/index.php?title=DiscFerret&diff=396DiscFerret2012-04-18T17:53:32Z<p>Balrog: </p>
<hr />
<div>'''The first prototypes of the DiscFerret hardware are now in the hands of developers -- we're aiming for full production around mid-Summer or early Autumn! Keep checking back, and feel free to join us in [http://webchat.freenode.net/?channels=discferret #discferret on irc.freenode.net]'''<br />
<br />
'''If you're interested in developing software for the DiscFerret, please get in touch! Several Limited Pre-production (LPP) units are being assembled and will be available shortly!'''<br />
<br />
DiscFerret is a combination of hardware and software that allows a standard desktop computer to read, analyse and decode the data on almost any floppy disc, and most MFM and RLL hard disc drives. This includes standard formats like PC DOS, but also more unusual formats like AmigaDOS, Apple (II and Mac GCR) and also more esoteric formats like those used on the Intel MDS/ISIS, Northstar and Sirius-Victor 9000 platforms. Imaging is performed at the lowest possible level -- that of magnetic transitions, which allows everything which can be represented on-disc to be imaged for later analysis.<br />
<br />
The source code and CAD files for the DiscFerret design are completely open-sourced: the hardware and software are released under the GNU GPL (in the case of the [http://hg.discferret.com/hardware/file/tip/LICENSE board], [http://hg.discferret.com/microcode/file/tip/COPYING microcode], and [http://hg.discferret.com/firmware/file/tip/COPYING firmware]) or the Apache Public Licence (in the case of the [http://hg.discferret.com/C-API/file/tip/LICENSE DiscFerret Hardware Access Library]).<br />
<br />
An IRC channel for support and development has been established. Please join us in [irc://irc.freenode.net/#discferret #discferret on irc.freenode.net].<br />
<br />
<br />
[[File:Discferret_board_component_side_HD_c.jpg|center|600px|DiscFerret board]]<br />
<br />
== News ==<br />
2012-APR-17 -- We've been helping out the Prince of Persia Source Code Recovery Project! The DiscFerret Project supplied a DiscFerret 1A24 prototype unit, which successfully produced images of several source code disks. We're now hard at work analysing and decoding the contents of these images... See the '[https://twitter.com/#!/search/%23popsource #popsource]' hash-tag on Twitter for more information! -- [[User:Philpem|Philpem]] 22:30, 17 April 2012 (BST)<br />
<br />
2012-JAN-11 -- DiscFerret Microcode 0028 and C API v1.5 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. These releases fix several critical microcode bugs -- users should update to these releases as soon as possible. --[[User:Philpem|Philpem]] 21:50, 11 January 2012 (GMT)<br />
<br />
2011-DEC-31 -- DiscFerret Microcode 0026 and C API v1.3 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. [[User:Philpem|Philpem]] 21:43, 31 December 2011 (GMT)<br />
<br />
2011-DEC-23 -- DiscFerret development has now resumed after a "brief" hiatus. Microcode updates are on the [[DiscFerret:Downloads|Downloads]] page, and the source code is available from the usual place (http://hg.discferret.com/). --[[User:Philpem|Philpem]] 02:44, 23 December 2011 (GMT)<br />
<br />
2011-MAR-21 -- The DiscFerret now supports 8-inch disc drives. Support has been added to Microcode 0x0021; the source code for this is in the "microcode" repository. -- [[User:Philpem|Philpem]] 01:22, 21 March 2011 (GMT)<br />
<br />
== Links ==<br />
<br />
* [[DiscFerret:FAQ|FAQ]]<br />
* [[DiscFerret:Downloads|Downloads]]<br />
<br />
* [[:Category:Disc formats|Disc format documentation]]<br />
* [[:Category:Disc image files|Image file format documentation]]</div>Balroghttps://www.discferret.com/w/index.php?title=DiscFerret&diff=395DiscFerret2012-04-18T17:53:04Z<p>Balrog: </p>
<hr />
<div>'''The first prototypes of the DiscFerret hardware are now in the hands of developers -- we're aiming for full production around mid-Summer or early Autumn! Keep checking back, and feel free to join us in [irc://irc.freenode.net/#discferret #discferret on irc.freenode.net]'''<br />
<br />
'''If you're interested in developing software for the DiscFerret, please get in touch! Several Limited Pre-production (LPP) units are being assembled and will be available shortly!'''<br />
<br />
DiscFerret is a combination of hardware and software that allows a standard desktop computer to read, analyse and decode the data on almost any floppy disc, and most MFM and RLL hard disc drives. This includes standard formats like PC DOS, but also more unusual formats like AmigaDOS, Apple (II and Mac GCR) and also more esoteric formats like those used on the Intel MDS/ISIS, Northstar and Sirius-Victor 9000 platforms. Imaging is performed at the lowest possible level -- that of magnetic transitions, which allows everything which can be represented on-disc to be imaged for later analysis.<br />
<br />
The source code and CAD files for the DiscFerret design are completely open-sourced: the hardware and software are released under the GNU GPL (in the case of the [http://hg.discferret.com/hardware/file/tip/LICENSE board], [http://hg.discferret.com/microcode/file/tip/COPYING microcode], and [http://hg.discferret.com/firmware/file/tip/COPYING firmware]) or the Apache Public Licence (in the case of the [http://hg.discferret.com/C-API/file/tip/LICENSE DiscFerret Hardware Access Library]).<br />
<br />
An IRC channel for support and development has been established. Please join us in [irc://irc.freenode.net/#discferret #discferret on irc.freenode.net].<br />
<br />
<br />
[[File:Discferret_board_component_side_HD_c.jpg|center|600px|DiscFerret board]]<br />
<br />
== News ==<br />
2012-APR-17 -- We've been helping out the Prince of Persia Source Code Recovery Project! The DiscFerret Project supplied a DiscFerret 1A24 prototype unit, which successfully produced images of several source code disks. We're now hard at work analysing and decoding the contents of these images... See the '[https://twitter.com/#!/search/%23popsource #popsource]' hash-tag on Twitter for more information! -- [[User:Philpem|Philpem]] 22:30, 17 April 2012 (BST)<br />
<br />
2012-JAN-11 -- DiscFerret Microcode 0028 and C API v1.5 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. These releases fix several critical microcode bugs -- users should update to these releases as soon as possible. --[[User:Philpem|Philpem]] 21:50, 11 January 2012 (GMT)<br />
<br />
2011-DEC-31 -- DiscFerret Microcode 0026 and C API v1.3 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. [[User:Philpem|Philpem]] 21:43, 31 December 2011 (GMT)<br />
<br />
2011-DEC-23 -- DiscFerret development has now resumed after a "brief" hiatus. Microcode updates are on the [[DiscFerret:Downloads|Downloads]] page, and the source code is available from the usual place (http://hg.discferret.com/). --[[User:Philpem|Philpem]] 02:44, 23 December 2011 (GMT)<br />
<br />
2011-MAR-21 -- The DiscFerret now supports 8-inch disc drives. Support has been added to Microcode 0x0021; the source code for this is in the "microcode" repository. -- [[User:Philpem|Philpem]] 01:22, 21 March 2011 (GMT)<br />
<br />
== Links ==<br />
<br />
* [[DiscFerret:FAQ|FAQ]]<br />
* [[DiscFerret:Downloads|Downloads]]<br />
<br />
* [[:Category:Disc formats|Disc format documentation]]<br />
* [[:Category:Disc image files|Image file format documentation]]</div>Balroghttps://www.discferret.com/w/index.php?title=DiscFerret&diff=394DiscFerret2012-04-17T23:15:45Z<p>Balrog: /* News */</p>
<hr />
<div>'''The first prototypes of the DiscFerret hardware are now in the hands of developers -- we're aiming for full production around mid-Summer or early Autumn! Keep checking back, and feel free to join us in #discferret on irc.freenode.net!'''<br />
<br />
'''If you're interested in developing software for the DiscFerret, please get in touch! Several Limited Pre-production (LPP) units are being assembled and will be available shortly!'''<br />
<br />
DiscFerret is a combination of hardware and software that allows a standard desktop computer to read, analyse and decode the data on almost any floppy disc, and most MFM and RLL hard disc drives. This includes standard formats like PC DOS, but also more unusual formats like AmigaDOS, Apple (II and Mac GCR) and also more esoteric formats like those used on the Intel MDS/ISIS, Northstar and Sirius-Victor 9000 platforms. Imaging is performed at the lowest possible level -- that of magnetic transitions, which allows everything which can be represented on-disc to be imaged for later analysis.<br />
<br />
The source code and CAD files for the DiscFerret design are completely open-sourced: the hardware and software are released under the GNU GPL (in the case of the [http://hg.discferret.com/hardware/file/tip/LICENSE board], [http://hg.discferret.com/microcode/file/tip/COPYING microcode], and [http://hg.discferret.com/firmware/file/tip/COPYING firmware]) or the Apache Public Licence (in the case of the [http://hg.discferret.com/C-API/file/tip/LICENSE DiscFerret Hardware Access Library]).<br />
<br />
An IRC channel for support and development has been established. Please join us in [irc://irc.freenode.net/#discferret #discferret on irc.freenode.net].<br />
<br />
<br />
[[File:Discferret_board_component_side_HD_c.jpg|center|600px|DiscFerret board]]<br />
<br />
== News ==<br />
2012-APR-17 -- We've been helping out the Prince of Persia Source Code Recovery Project! The DiscFerret Project supplied a DiscFerret 1A24 prototype unit, which successfully produced images of several source code disks. We're now hard at work analysing and decoding the contents of these images... See the '[https://twitter.com/#!/search/%23popsource #popsource]' hash-tag on Twitter for more information! -- [[User:Philpem|Philpem]] 22:30, 17 April 2012 (BST)<br />
<br />
2012-JAN-11 -- DiscFerret Microcode 0028 and C API v1.5 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. These releases fix several critical microcode bugs -- users should update to these releases as soon as possible. --[[User:Philpem|Philpem]] 21:50, 11 January 2012 (GMT)<br />
<br />
2011-DEC-31 -- DiscFerret Microcode 0026 and C API v1.3 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. [[User:Philpem|Philpem]] 21:43, 31 December 2011 (GMT)<br />
<br />
2011-DEC-23 -- DiscFerret development has now resumed after a "brief" hiatus. Microcode updates are on the [[DiscFerret:Downloads|Downloads]] page, and the source code is available from the usual place (http://hg.discferret.com/). --[[User:Philpem|Philpem]] 02:44, 23 December 2011 (GMT)<br />
<br />
2011-MAR-21 -- The DiscFerret now supports 8-inch disc drives. Support has been added to Microcode 0x0021; the source code for this is in the "microcode" repository. -- [[User:Philpem|Philpem]] 01:22, 21 March 2011 (GMT)<br />
<br />
== Links ==<br />
<br />
* [[DiscFerret:FAQ|FAQ]]<br />
* [[DiscFerret:Downloads|Downloads]]<br />
<br />
* [[:Category:Disc formats|Disc format documentation]]<br />
* [[:Category:Disc image files|Image file format documentation]]</div>Balroghttps://www.discferret.com/w/index.php?title=DiscFerret&diff=389DiscFerret2012-04-05T19:18:33Z<p>Balrog: added license links</p>
<hr />
<div>DiscFerret is a combination of hardware and software that allows a standard desktop computer to read, analyse and decode the data on just about any floppy disc, and some MFM and RLL hard disc drives. This includes standard formats like PC DOS, but also more unusual formats like AmigaDOS and the Intel MDS M2FM format. Imaging is performed at the lowest possible level -- that of magnetic transitions, which allows everything which can be represented on-disc to be imaged.<br />
<br />
The source code and CAD files for the DiscFerret design are completely open-sourced: the hardware and software are released under the GNU GPL (in the case of the [http://hg.discferret.com/hardware/file/tip/LICENSE board], [http://hg.discferret.com/microcode/file/tip/COPYING microcode], and [http://hg.discferret.com/firmware/file/tip/COPYING firmware]) or the Apache Public Licence (in the case of the [http://hg.discferret.com/C-API/file/tip/LICENSE API]).<br />
<br />
An IRC channel for support and development has been established. Please join at [irc://irc.freenode.net/#discferret #discferret] on irc.freenode.net.<br />
<br />
<br />
[[File:Discferret_board_component_side_HD_c.jpg|center|600px|DiscFerret board]]<br />
<br />
== News ==<br />
2012-JAN-11 -- DiscFerret Microcode 0028 and C API v1.5 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. These releases fix several critical microcode bugs -- users should update to these releases as soon as possible. --[[User:Philpem|Philpem]] 21:50, 11 January 2012 (GMT)<br />
<br />
2011-DEC-31 -- DiscFerret Microcode 0026 and C API v1.3 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. [[User:Philpem|Philpem]] 21:43, 31 December 2011 (GMT)<br />
<br />
2011-DEC-23 -- DiscFerret development has now resumed after a "brief" hiatus. Microcode updates are on the [[DiscFerret:Downloads|Downloads]] page, and the source code is available from the usual place (http://hg.discferret.com/). --[[User:Philpem|Philpem]] 02:44, 23 December 2011 (GMT)<br />
<br />
2011-MAR-21 -- The DiscFerret now supports 8-inch disc drives. Support has been added to Microcode 0x0021; the source code for this is in the "microcode" repository. -- [[User:Philpem|Philpem]] 01:22, 21 March 2011 (GMT)<br />
<br />
== Links ==<br />
<br />
* [[DiscFerret:FAQ|FAQ]]<br />
* [[DiscFerret:Downloads|Downloads]]<br />
<br />
* [[:Category:Disc formats|Disc format documentation]]<br />
* [[:Category:Disc image files|Image file format documentation]]</div>Balroghttps://www.discferret.com/w/index.php?title=DFI_image_format&diff=387DFI image format2012-01-16T01:45:40Z<p>Balrog: </p>
<hr />
<div>[[Category:Disc image files]]<br />
<br />
'''Format originator:''' DiscFerret software.<br />
<br />
== Overall format ==<br />
<br />
All integers in this file format are stored in big-endian form.<br />
<br />
The DFI file consists of a 4-byte magic string, followed by a series of disc sample blocks.<br />
<br />
The magic string is "DFER" for old-style DiscFerret images, or "DFE2" for new-style DiscFerret images.<br />
<br />
Each sample block has a header --<br />
<nowiki><br />
uint16_be cylinder;<br />
uint16_be head;<br />
uint16_be sector;<br />
uint32_be data_length;<br />
</nowiki><br />
<br />
The cylinder number starts at zero and counts up to the number of cylinders on the disk. The head number follows the same rule (starts at zero, increments for each additional head). The sector number is optional, and only used for hard-sectored discs. For soft-sectored discs, it is set to zero. Data_length indicates the number of bytes of data which follow.<br />
<br />
== Decoding data ==<br />
<br />
=== Old-style images ===<br />
<nowiki><br />
carry = 0<br />
For every byte in the stream:<br />
if (byte AND 0x7f) == 0x00:<br />
carry = carry + 127<br />
else:<br />
emit((byte AND 0x7f) + carry)<br />
carry = 0<br />
if carry > 0:<br />
emit(carry)<br />
</nowiki><br />
<br />
=== New-style images ===<br />
<nowiki><br />
carry = 0<br />
For every byte in the stream:<br />
if ((byte AND 0x7f) == 0x7f): // if lower 7 bit value is 0x7f<br />
carry = carry + 127<br />
else if (byte AND 0x80) != 0: // if high bit set in byte<br />
carry = carry + (byte & 0x7F) // add lower 7 bit value to carry<br />
add_index_position(carry) // add high bit to carry<br />
else: // here byte < 0x7f<br />
emit((byte AND 0x7f) + carry) // report carry + byte<br />
carry = 0 // reset carry<br />
if carry > 0: // <br />
emit(carry) // report carry<br />
<br />
// emit() stores the timing value<br />
// add_index_position() stores the timing position of an index pulse<br />
// <br />
</nowiki></div>Balroghttps://www.discferret.com/w/index.php?title=DFI_image_format&diff=386DFI image format2012-01-15T22:54:26Z<p>Balrog: Added comments, thanks fjkraan!</p>
<hr />
<div>[[Category:Disc image files]]<br />
<br />
'''Format originator:''' DiscFerret software.<br />
<br />
== Overall format ==<br />
<br />
All integers in this file format are stored in big-endian form.<br />
<br />
The DFI file consists of a 4-byte magic string, followed by a series of disc sample blocks.<br />
<br />
The magic string is "DFER" for old-style DiscFerret images, or "DFE2" for new-style DiscFerret images.<br />
<br />
Each sample block has a header --<br />
<nowiki><br />
uint16_be cylinder;<br />
uint16_be head;<br />
uint16_be sector;<br />
uint32_be data_length;<br />
</nowiki><br />
<br />
The cylinder number starts at zero and counts up to the number of cylinders on the disk. The head number follows the same rule (starts at zero, increments for each additional head). The sector number is optional, and only used for hard-sectored discs. For soft-sectored discs, it is set to zero. Data_length indicates the number of bytes of data which follow.<br />
<br />
== Decoding data ==<br />
<br />
=== Old-style images ===<br />
<nowiki><br />
carry = 0<br />
For every byte in the stream:<br />
if (byte AND 0x7f) == 0x00:<br />
carry = carry + 127<br />
else:<br />
emit((byte AND 0x7f) + carry)<br />
carry = 0<br />
if carry > 0:<br />
emit(carry)<br />
</nowiki><br />
<br />
=== New-style images ===<br />
<nowiki><br />
carry = 0<br />
For every byte in the stream:<br />
if ((byte AND 0x7f) == 0x7f): // if lower 7 bit value is 0x7f<br />
carry = carry + 127<br />
else if (byte AND 0x80) != 0: // if high bit set in byte<br />
carry = carry + (byte & 0x7F) // add lower 7 bit value to carry<br />
add_index_position(carry) // add high bit to carry<br />
else: // here byte < 0x7f<br />
emit((byte AND 0x7f) + carry) // ?? the AND 0x7f is superfluous here. report carry + byte<br />
carry = 0 // reset carry<br />
if carry > 0: // <br />
emit(carry) // report carry<br />
<br />
// emit() looks like a written value<br />
// add_index_position() is just setting the high bit of the last data value <br />
// <br />
</nowiki></div>Balroghttps://www.discferret.com/w/index.php?title=DiscFerret&diff=385DiscFerret2012-01-15T20:17:01Z<p>Balrog: Added photo of board</p>
<hr />
<div>DiscFerret is a combination of hardware and software that allows a standard desktop computer to read, analyse and decode the data on just about any floppy disc, and some MFM and RLL hard disc drives. This includes standard formats like PC DOS, but also more unusual formats like AmigaDOS and the Intel MDS M2FM format. Imaging is performed at the lowest possible level -- that of magnetic transitions, which allows everything which can be represented on-disc to be imaged.<br />
<br />
The source code and CAD files for the DiscFerret design are completely open-sourced: the hardware is licensed under a semi-permissive licence, while the software is released under the GNU GPL (in the case of the microcode and firmware) or the Apache Public Licence (in the case of the API).<br />
<br />
An IRC channel for support and development has been established. Please join at [irc://irc.freenode.net/#discferret #discferret] on irc.freenode.net.<br />
<br />
<br />
[[File:Discferret_board_component_side_HD_c.jpg|center|600px|DiscFerret board]]<br />
<br />
== News ==<br />
2012-JAN-11 -- DiscFerret Microcode 0028 and C API v1.5 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. These releases fix several critical microcode bugs -- users should update to these releases as soon as possible. --[[User:Philpem|Philpem]] 21:50, 11 January 2012 (GMT)<br />
<br />
2011-DEC-31 -- DiscFerret Microcode 0026 and C API v1.3 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. [[User:Philpem|Philpem]] 21:43, 31 December 2011 (GMT)<br />
<br />
2011-DEC-23 -- DiscFerret development has now resumed after a "brief" hiatus. Microcode updates are on the [[DiscFerret:Downloads|Downloads]] page, and the source code is available from the usual place (http://hg.discferret.com/). --[[User:Philpem|Philpem]] 02:44, 23 December 2011 (GMT)<br />
<br />
2011-MAR-21 -- The DiscFerret now supports 8-inch disc drives. Support has been added to Microcode 0x0021; the source code for this is in the "microcode" repository. -- [[User:Philpem|Philpem]] 01:22, 21 March 2011 (GMT)<br />
<br />
== Links ==<br />
<br />
* [[DiscFerret:FAQ|FAQ]]<br />
* [[DiscFerret:Downloads|Downloads]]<br />
<br />
* [[:Category:Disc formats|Disc format documentation]]<br />
* [[:Category:Disc image files|Image file format documentation]]</div>Balroghttps://www.discferret.com/w/index.php?title=File:Discferret_board_component_side_HD_c.jpg&diff=384File:Discferret board component side HD c.jpg2012-01-15T20:10:16Z<p>Balrog: DiscFerret board</p>
<hr />
<div>DiscFerret board</div>Balroghttps://www.discferret.com/w/index.php?title=DiscFerret&diff=383DiscFerret2012-01-15T19:37:04Z<p>Balrog: </p>
<hr />
<div>DiscFerret is a combination of hardware and software that allows a standard desktop computer to read, analyse and decode the data on just about any floppy disc, and some MFM and RLL hard disc drives. This includes standard formats like PC DOS, but also more unusual formats like AmigaDOS and the Intel MDS M2FM format. Imaging is performed at the lowest possible level -- that of magnetic transitions, which allows everything which can be represented on-disc to be imaged.<br />
<br />
The source code and CAD files for the DiscFerret design are completely open-sourced: the hardware is licensed under a semi-permissive licence, while the software is released under the GNU GPL (in the case of the microcode and firmware) or the Apache Public Licence (in the case of the API).<br />
<br />
An IRC channel for support and development has been started. Please join at [irc://irc.freenode.net/#discferret #discferret] on irc.freenode.net.<br />
<br />
== News ==<br />
2012-JAN-11 -- DiscFerret Microcode 0028 and C API v1.5 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. These releases fix several critical microcode bugs -- users should update to these releases as soon as possible. --[[User:Philpem|Philpem]] 21:50, 11 January 2012 (GMT)<br />
<br />
2011-DEC-31 -- DiscFerret Microcode 0026 and C API v1.3 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. [[User:Philpem|Philpem]] 21:43, 31 December 2011 (GMT)<br />
<br />
2011-DEC-23 -- DiscFerret development has now resumed after a "brief" hiatus. Microcode updates are on the [[DiscFerret:Downloads|Downloads]] page, and the source code is available from the usual place (http://hg.discferret.com/). --[[User:Philpem|Philpem]] 02:44, 23 December 2011 (GMT)<br />
<br />
2011-MAR-21 -- The DiscFerret now supports 8-inch disc drives. Support has been added to Microcode 0x0021; the source code for this is in the "microcode" repository. -- [[User:Philpem|Philpem]] 01:22, 21 March 2011 (GMT)<br />
<br />
== Links ==<br />
<br />
* [[DiscFerret:FAQ|FAQ]]<br />
* [[DiscFerret:Downloads|Downloads]]<br />
<br />
* [[:Category:Disc formats|Disc format documentation]]<br />
* [[:Category:Disc image files|Image file format documentation]]</div>Balroghttps://www.discferret.com/w/index.php?title=DiscFerret&diff=382DiscFerret2012-01-15T19:18:18Z<p>Balrog: added irc channel</p>
<hr />
<div>DiscFerret is a combination of hardware and software that allows a standard desktop computer to read, analyse and decode the data on just about any floppy disc, and some MFM and RLL hard disc drives. This includes standard formats like PC DOS, but also more unusual formats like AmigaDOS and the Intel MDS M2FM format. Imaging is performed at the lowest possible level -- that of magnetic transitions, which allows everything which can be represented on-disc to be imaged.<br />
<br />
The source code and CAD files for the DiscFerret design are completely open-sourced: the hardware is licensed under a semi-permissive licence, while the software is released under the GNU GPL (in the case of the microcode and firmware) or the Apache Public Licence (in the case of the API).<br />
<br />
An IRC channel for support and development has been started. Please join at #discferret on irc.freenode.net.<br />
<br />
== News ==<br />
2012-JAN-11 -- DiscFerret Microcode 0028 and C API v1.5 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. These releases fix several critical microcode bugs -- users should update to these releases as soon as possible. --[[User:Philpem|Philpem]] 21:50, 11 January 2012 (GMT)<br />
<br />
2011-DEC-31 -- DiscFerret Microcode 0026 and C API v1.3 have been released and are on the [[DiscFerret:Downloads|Downloads]] page. [[User:Philpem|Philpem]] 21:43, 31 December 2011 (GMT)<br />
<br />
2011-DEC-23 -- DiscFerret development has now resumed after a "brief" hiatus. Microcode updates are on the [[DiscFerret:Downloads|Downloads]] page, and the source code is available from the usual place (http://hg.discferret.com/). --[[User:Philpem|Philpem]] 02:44, 23 December 2011 (GMT)<br />
<br />
2011-MAR-21 -- The DiscFerret now supports 8-inch disc drives. Support has been added to Microcode 0x0021; the source code for this is in the "microcode" repository. -- [[User:Philpem|Philpem]] 01:22, 21 March 2011 (GMT)<br />
<br />
== Links ==<br />
<br />
* [[DiscFerret:FAQ|FAQ]]<br />
* [[DiscFerret:Downloads|Downloads]]<br />
<br />
* [[:Category:Disc formats|Disc format documentation]]<br />
* [[:Category:Disc image files|Image file format documentation]]</div>Balroghttps://www.discferret.com/w/index.php?title=DiscFerret&diff=365DiscFerret2011-12-23T05:57:40Z<p>Balrog: fixed Downloads page link</p>
<hr />
<div>DiscFerret is a combination of hardware and software that allows a standard desktop computer to read, analyse and decode the data on just about any floppy disc, and some MFM and RLL hard disc drives. This includes standard formats like PC DOS, but also more unusual formats like AmigaDOS and the Intel MDS M2FM format. Imaging is performed at the lowest possible level -- that of magnetic transitions, which allows everything which can be represented on-disc to be imaged.<br />
<br />
The source code and CAD files for the DiscFerret design are completely open-sourced: the hardware is licensed under a semi-permissive licence, while the software is released either under the GNU GPL or the Apache Public Licence.<br />
<br />
== News ==<br />
2011-DEC-23 -- DiscFerret development has now resumed after a "brief" hiatus. Microcode updates are on the [[DiscFerret:Downloads|Downloads]] page, and the source code is available from the usual place (http://hg.discferret.com/). --[[User:Philpem|Philpem]] 02:44, 23 December 2011 (GMT)<br />
<br />
2011-MAR-21 -- The DiscFerret now supports 8-inch disc drives. Support has been added to Microcode 0x0021; the source code for this is in the "microcode" repository. -- [[User:Philpem|Philpem]] 01:22, 21 March 2011 (GMT)<br />
<br />
== Links ==<br />
<br />
* [[DiscFerret:FAQ|FAQ]]<br />
* [[DiscFerret:Downloads|Downloads]]<br />
<br />
* [[:Category:Disc formats|Disc format documentation]]<br />
* [[:Category:Disc image files|Image file format documentation]]</div>Balrog