Group coded recording

In computer science, group coded recording or group code recording (GCR) refers to several distinct but related encoding methods for representing data on magnetic media. The first, used in 6250 bpi magnetic tape since 1973,[1][2] is an error-correcting code combined with a run-length limited (RLL) encoding scheme, belonging into the group of modulation codes.[3] The others are similar encoding methods used in mainframe hard disks or microcomputer floppy disks until the late 1980s. GCR is a modified form of a NRZI code, but necessarily with a higher transition density.[3]

Magnetic tape

[edit]

Group coded recording was first used for magnetic-tape data storage on 9-track reel-to-reel tape.[3] The term was coined during the development of the IBM 3420 Model 4/6/8 Magnetic Tape Unit[1] and the corresponding 3803 Model 2 Tape Control Unit,[4][1] both introduced in 1973.[1][5] IBM referred to the error correcting code itself as "group coded recording". However, GCR has come to refer to the recording format of 6250 bpi (250 bits/mm[3]) tape as a whole, and later to formats which use similar RLL codes without the error correction code.

In order to reliably read and write to magnetic tape, several constraints on the signal to be written must be followed. The first is that two adjacent flux reversals must be separated by a certain distance on the media, defined by the magnetic properties of the media itself. The second is that there must be a reversal often enough to keep the reader's clock in phase with the written signal; that is, the signal must be self-clocking and most importantly to keep the playback output high enough as this is proportional to the density of flux transitions. Prior to 6250 bpi tapes, 1600 bpi tapes satisfied these constraints using a technique called phase encoding (PE), which was only 50% efficient. For 6250 bpi GCR tapes, a (0, 2) RLL code is used, or more specifically a ⁠4/5⁠ (0, 2) block code[3] sometimes also referred to as GCR (4B-5B) encoding.[6] This code requires five bits to be written for every four bits of data.[3] The code is structured so that no more than two zero bits (which are represented by lack of a flux reversal) can occur in a row,[3] either within a code or between codes, no matter what the data was. This RLL code is applied independently to the data going to each of the nine tracks.

Of the 32 five-bit patterns, eight begin with two consecutive zero bits, six others end with two consecutive zero bits, and one more (10001) contains three consecutive zero bits. Removing the all-ones pattern (11111) from the remainder leaves 16 suitable code words.

The 6250 bpi GCR RLL code:[7][8][9][6]

4-bit value GCR code[7][8]
hex bin bin hex
0x0 0000 1.1001 0x19
0x1 0001 1.1011 0x1B
0x2 0010 1.0010 0x12
0x3 0011 1.0011 0x13
0x4 0100 1.1101 0x1D
0x5 0101 1.0101 0x15
0x6 0110 1.0110 0x16
0x7 0111 1.0111 0x17
4-bit value GCR code[7][8]
hex bin bin hex
0x8 1000 1.1010 0x1A
0x9 1001 0.1001 0x09
0xA 1010 0.1010 0x0A
0xB 1011 0.1011 0x0B
0xC 1100 1.1110 0x1E
0xD 1101 0.1101 0x0D
0xE 1110 0.1110 0x0E
0xF 1111 0.1111 0x0F

11 of the nibbles (other than xx00 and 0001) have their code formed by prepending the complement of the most significant bit; i.e. abcd is encoded as aabcd. The other five values are assigned codes beginning with 11. Nibbles of the form ab00 have codes 11baa, i.e. the bit reverse of the code for ab11. The code 0001 is assigned the remaining value 11011.

Because the all-ones code is not used in normal data, at most 8 one-bits can appear in a row. Sequences of 9 or more one-bits (in practice 14 all-ones codes, or 70 one-bits, were used) are used as a synchronization pattern.

Because of the extremely high density (for the time) of 6250 bpi tape, the RLL code is not sufficient to ensure reliable data storage. On top of the RLL code, an error-correcting code called the Optimal Rectangular Code (ORC) is applied.[10] This code is a combination of a parity track and polynomial code similar to a CRC, but structured for error correction rather than error detection. For every seven bytes written to the tape (before RLL encoding), an eighth check byte is calculated and written to the tape. When reading, the parity is calculated on each byte and exclusive-ORed with the contents of the parity track, and the polynomial check code calculated and exclusive-ORed with the received check code, resulting in two 8-bit syndrome words. If these are both zero, the data is error free. Otherwise, error-correction logic in the tape controller corrects the data before it is forwarded to the host. The error correcting code is able to correct any number of errors in any single track, or in any two tracks if the erroneous tracks can be identified by other means.

In newer IBM half-inch 18-track tape drives recording at 24000 bpi, ⁠4/5⁠ (0, 2) GCR was replaced by a more efficient ⁠8/9⁠ (0, 3) modulation code, mapping eight bits to nine bits.[3]

Hard disks

[edit]

In the mid-1970s, Sperry Univac, ISS Division was working on large hard drives for the mainframe business using group coding.[11]

Floppy disks

[edit]

Like magnetic tape drives, floppy disk drives have physical limits on the spacing of flux reversals (also called transitions, represented by one-bits).

Micropolis

[edit]

Offering GCR-compatible diskette drives and floppy disk controllers (like the 100163-51-8 and 100163-52-6[12]), Micropolis endorsed data encoding with group coded recording[13] on 5¼-inch 100 tpi 77-track diskette drives to store twelve 512-byte sectors per track since 1977 or 1978.[14][15][16][17]

Micro Peripherals

[edit]

Micro Peripherals, Inc. (MPI) marketed double-density 5¼-inch disk drives (like the single-sided B51 and double-sided B52 drives) and a controller solution implementing GCR since early 1978.[18][19]

Durango

[edit]

The Durango Systems F-85 (introduced in September 1978[20][21]) used single-sided 5¼-inch 100 tpi diskette drives providing 480 KB utilizing a proprietary high-density 4/5 group coded encoding. The machine was using a Western Digital FD1781 floppy disk controller, designed by a former Sperry ISS engineer,[17] with 77-track Micropolis drives.[22] In later models such as the Durango 800[23] series this was expanded to a double-sided option for 960 KB (946 KB formatted[23][nb 1]) per diskette.[21][24][22][14]

Apple

[edit]

For the Apple II floppy drive, Steve Wozniak invented a floppy controller which (along with the Disk II drive itself) imposed two constraints:

  • Between any two one bits, there may be a maximum of one zero bit.
  • Each 8-bit byte must start with a one bit.

The simplest scheme to ensure compliance with these limits is to record an extra "clock" transition before each data bit according to differential Manchester encoding or (digital) FM (frequency modulation). Known as 4-and-4 encoding, the resulting Apple implementation allowed only ten 256-byte sectors per track to be recorded on a single-density 5¼-inch floppy. It uses two bytes for each byte.

Close to a month prior to the shipment of the disk drive in spring 1978,[26] Wozniak realized that a more complex encoding scheme would allow each eight-bit byte on disk to hold five bits of useful data rather than four bits. This is because there are 34 bytes which have the top bit set and no two zero bits in a row. This encoding scheme became known as 5-and-3 encoding, and allowed 13 sectors per track; it was used for Apple DOS 3.1, 3.2, and 3.2.1, as well as for the earliest version of Apple CP/M [de]:[27]

Reserved GCR-codes: 0xAA and 0xD5.[27]

Wozniak called the system "my most incredible experience at Apple and the finest job I did".[26]

Later, the design of the floppy drive controller was modified to allow a byte on disk to contain up to one pair of zero bits in a row. This allowed each eight-bit byte to hold six bits of useful data, and allowed 16 sectors per track. This scheme is known as 6-and-2 encoding,[27] and was used on Apple Pascal, Apple DOS 3.3[27] and ProDOS,[29] and later with Apple FileWare drives in the Apple Lisa and the 400K and 800K 3½-inch disks on the Macintosh and Apple II.[30][31] Apple did not originally call this scheme "GCR", but the term was later applied to it[31] to distinguish it from IBM PC floppies which used the MFM encoding scheme.

Reserved GCR-codes: 0xAA and 0xD5.[27][29]

Commodore

[edit]

Independently, Commodore Business Machines (CBM) created a group coded recording scheme for their Commodore 2040 floppy disk drive (launched in the spring of 1979). The relevant constraints on the 2040 drive were that no more than two zero bits could occur in a row; the drive imposed no special constraint on the first bit in a byte. This allowed the use of a scheme similar to that used in 6250 bpi tape drives. Every four bits of data are translated into five bits on disk, using the same 5-bit codes as IBM to ensure there are never more than two zero bits in a row, but in a different order:

4-bit value GCR code[32]
hex bin bin hex
0x0 0000 0.1010 0x0A
0x1 0001 0.1011 0x0B
0x2 0010 1.0010 0x12
0x3 0011 1.0011 0x13
0x4 0100 0.1110 0x0E
0x5 0101 0.1111 0x0F
0x6 0110 1.0110 0x16
0x7 0111 1.0111 0x17
4-bit value GCR code[32]
hex bin bin hex
0x8 1000 0.1001 0x09
0x9 1001 1.1001 0x19
0xA 1010 1.1010 0x1A
0xB 1011 1.1011 0x1B
0xC 1100 0.1101 0x0D
0xD 1101 1.1101 0x1D
0xE 1110 1.1110 0x1E
0xF 1111 1.0101 0x15

Like the IBM code, at most eight one bits in a row are possible, so Commodore used sequences of ten or more one bits in a row as a synchronization sequence.

This more efficient GCR scheme, combined with an approach at constant bit-density recording by gradually increasing the clock rate (zone constant angular velocity, ZCAV) and storing more physical sectors on the outer tracks than on the inner ones (zone bit recording, ZBR), enabled Commodore to fit 170 KiB on a standard single-sided single-density 5.25-inch floppy, where Apple fit 140 KiB (with 6-and-2 encoding) or 114 KiB (with 5-and-3 encoding) and an FM-encoded floppy held only 88 KiB.

Sirius/Victor

[edit]

Similar, the 5.25-inch floppy drives of the Victor 9000 aka Sirius 1, designed by Chuck Peddle in 1981/1982, used a combination of GCR and zone bit recording by gradually decreasing a drive's rotational speed for the outer tracks in nine zones while increasing the number of sectors per track[33] to achieve formatted capacities of 606 KiB (single sided) / 1188 KiB (double-sided) on 96 tpi media.[34][35][36][37] The GCR code is identical to the Commodore one.[38]

Brother

[edit]

Starting around 1985, Brother introduced a family of dedicated word processor typewriters with integrated 3.5-inch 38-track[nb 2] diskette drive. Early models of the WP and LW series [de] used a Brother-specific group-coded recording scheme with twelve 256-byte sectors to store up to 120 KB[nb 3] on single-sided and up to 240 KB[nb 3] on double-sided double-density (DD) diskettes.[17][39][40][41] Reportedly, prototypes were already shown at the Internationale Funkausstellung 1979 (IFA) in Berlin.

Sharp

[edit]

In 1986, Sharp introduced a turnable 2.5-inch pocket disk drive solution (drives: CE-1600F, CE-140F; internally based on the FDU-250 chassis; media: CE-1650F) for their series of pocket computers with a formatted capacity of 62464 bytes per side (2× 64 kB nominal, 16 tracks, 8 sectors/track, 512 bytes per sector, 48 tpi, 250 kbit/s, 270 rpm) with GCR (4/5) recording.[42][43]

Other uses

[edit]

GCR was also evaluated for a possible use in bar code encoding schemes (packing efficiency, timing tolerances, amount of storage bytes for timing information, and DC output level).[44]

See also

[edit]

Notes

[edit]
  1. ^ The product flyer for the Durango 800 series documents a formatted "on-line capacity" of 1.892 MB for the diskette drives. The system, however, was equipped with two 5¼-inch Micropolis 100 tpi 77-track floppy drives by default, and 1.892 MB is about twice as large as the physical drive capacity documented in various other sources (480 KB per side), therefore, by "on-line capacity" they must have meant the available storage capacity available to users for the combination of two drives.
  2. ^ The sources give slightly contradicting parameters regarding the Brother diskette formats. 12 sectors á 256 bytes would give 120 KB per side on a 40-track drive, but one source claims the drives were 38-track only.
  3. ^ a b The following Brother models are known to support a 120 KB diskette format (incomplete list): WP-1 (1985/1987), WP-5 (1987/1989), WP-6 (1989), WP-55 (1987/1989), WP-500 (1987/1989). The following models are known to support a 240 KB format (incomplete list): WP-70, WP-75 (1989), WP-80 (1985/1989), WP-3400, WP-3410, WP-3550, WP-3650D, WP-760D, WP-760D+, LW-1 (1989), LW-20, LW-30, LW-100, LW-400.

References

[edit]
  1. ^ a b c d CW staff (1973-03-14). "6,250 Byte/In. Density – IBM 3420 Storage More Than Tripled". Computerworld. VII (11). White Plains, New York, USA: 1–2. Retrieved 2017-03-23. IBM added three new models to the 3420 magnetic tape system than can record data at the "densest recording capability yet offered", according to the company. Using a new method called Group Coded Recording (GCR), the IBM drives can handle tapes containing a data density of 6,250 byte/in. compared with 1,600 byte/in. on earlier models of the 3420. [...] An upgraded control unit was also announced – the 3803 Model 2 – which operates with both the earlier and latest 3420 tape units. The Model 2 includes the capability of correcting errors in one or two tracks "simultaneously while the tape is in motion", IBM said. [...] The GCR method segments data written on tape into groups of characters to which a special coding character is added. And the higher density is based on a combination of a modified coding scheme, a smaller interrecord gap (called an interblock gap) and modified electronics and electromechanical components, IBM said. Installed 3803/3420 tape systems can be converted to the higher densities in the field. [...]
  2. ^ FIPS PUB 50/ANSI X3.54-1976: Recorded Magnetic Tape for Information Interchange (6250 CPI, Group-Coded Recording) (PDF) (American National Standard). ANSI. 1976. Retrieved 2024-07-19.
  3. ^ a b c d e f g h Patel, Arvind Motibhai (1988). "5. Signal and Error-Control Coding". In Mee, C. Denis; Daniel, Eric D. (eds.). Magnetic Recording. Vol. II: Computer Data Storage (1st ed.). McGraw-Hill Book Company. ISBN 0-07-041272-3.
  4. ^ "The Gallery of Old Iron". 2004. Archived from the original on 2008-12-25. [...] I moved to the lab at Poughkeepsie in 1958 [...] I later was Lead designer and architect for the 2802 Tape Control Unit and a few years after that, Lead Designer and Architect of the 3803 which was a very large modification based on the 2802. Three of us shared a Corporate Award for the 3803 and I, along with Planner Charlie Von Reyn, came up with the name "Group Coded Recording (GCR)" as the name of the recording method. [...] (NB. An anonymous comment by one of the developers on the origin of the name "Group Coded Recording".)
  5. ^ Harris, John P.; Phillips, William B.; Wells, Jack F.; Winger, Wayne D. (September 1981). "Innovations in the Design of Magnetic Tape Subsystems". IBM Journal of Research and Development. 25 (5). International Business Machines Corporation: 691–700. CiteSeerX 10.1.1.83.2700. doi:10.1147/rd.255.0691.
  6. ^ a b Geffroy, Jean-Claude; Motet, Gilles (2013-03-09) [2002]. "15.12 Exercise GCR (4B – 5B) code". Design of Dependable Computing Systems. Toulouse, France: Springer Science+Business Media, B.V. / Kluwer Academic Publishers. pp. 426, 591. ISBN 978-1-4020-0437-7. LCCN 2002-284974. ISBN 94-015-9884-3. Retrieved 2021-11-18. (672 pages)
  7. ^ a b c Keong, Kwoh Chee, Computer Peripherals (PDF), School of Computer Engineering, Nanyang Technological University, Singapore, Chapter 7. Magnetic Recording Fundamentals, archived (PDF) from the original on 2017-03-23, retrieved 2017-03-23
  8. ^ a b c Watkinson, John (1990). "3.4. Group codes". Coding for Digital Recording. Stoneham, MA, USA: Focal Press. pp. 51–61. ISBN 0-240-51293-6.
  9. ^ Savard, John J. G. (2018) [2006]. "Digital Magnetic Tape Recording". quadibloc. Archived from the original on 2018-07-02. Retrieved 2018-07-16.
  10. ^ Patel, Arvind Motibhai; Hong, Se June (1974). "Optimal Rectangular Code for High Density Magnetic Tapes". IBM Journal of Research and Development. 18 (6): 579–588. doi:10.1147/rd.186.0579. Archived from the original on 2017-11-04. Retrieved 2017-03-21.
  11. ^ Jacoby, George V. (2003-01-06) [September 1977]. "A new look-ahead code for increased data density". IEEE Transactions on Magnetics. 13 (5). Sperry Univac, ISS Division, Cupertino, CA, USA: IEEE: 1202–1204. doi:10.1109/TMAG.1977.1059670. (NB. This article about the 3PM code was also presented at the Intermag 1977 in June 1977.)
  12. ^ "Micropolis 100163 Intelligent Controller". Micropolis. Retrieved 2022-06-26.)
  13. ^ US 4261019, McClelland, S. Barry, "Compatible Digital Magnetic Recording System", published 1981-04-07, assigned to Micropolis Corporation  (NB. Application Number: US 06/098381)
  14. ^ a b "NCC Preview: OEMs at NCC – Micropolis Corp". Computerworld. XII (22). CW Communications, Inc.: P/50. 1978-05-28. Retrieved 2017-06-12. [...] Micropolis has extended the capacity of 5.25-in. floppy disk subsystems via double-sided models with formatted file storage of up to nearly 2 million bytes [...] The Megafloppy series also features an intelligent controller that facilitates interconnection of four subsystems to a common host interface for a total on-line storage capacity of more than 15M bytes [...] Double-sided versions of the product line will be implemented first in two OEM series – Model 1015 and Model 1055 [...] The Model 1015 is an unpackaged drive designed for the manufacturer who integrates floppy disk storage into his own system enclosure. A range of storage capacities from 143,000 to 630,000 bytes per drive is available [...] Model 1015 customers have the option of using the Micropolis intelligent controller and Group Code Recording (GCR) method to further expand file space up to 946,000 bytes [...] Offering GCR and a microprocessor-based controller as standard features, the Model 1055 5.25-in. floppy has four soft-sectored formats for each of its 77 tracks, yielding a maximum capacity of 1,892,000 bytes of file space on its double-sided version [...] An add-on module available for the 1055 is comprised of two read/write heads and two drives, sharing a common controller. The subsystem capacity (formatted) with the module is 3,784,000 bytes [...] Up to four 1055s, each with an add-on module, can be daisy-chained to a common host for a maximum on-line storage capacity of more than 15M bytes [...]
  15. ^ Micropolis Maintenance Manual Floppy Disk Subsystem (PDF) (revision 1, 1st ed.). Micropolis Corporation. February 1979. 1082-04. Archived (PDF) from the original on 2017-06-12. Retrieved 2017-06-12. (NB. Micropolis 100163-51-8 and 100163-52-6 are GCR-based.)
  16. ^ "InfoNews/Hardware: Hardware/Briefs". InfoWorld. 2 (2): 19. 1980-03-03. Retrieved 2017-06-12. [...] Four new 96 tracks-per-inch products have been added to Micropolis' current line of 100 tpi single-sided and double-sided floppy disks. The 96 tpi drives offer 70 tracks-per-side, as opposed to the 77 offered by the MegaFloppy line. The four models are: 1) The 1015-V: 436 KB, unformatted, FM/MFM recording [...] 2) The 1016-V: 532 KB unformatted, Group Coded Recording (GCR) [...] 3) The 1015-VI: a two-head version of the MFM drive, 872 KB [...] 4) The 1016-VI: also a two-head drive, 1.064 MB GCR encoding [...]
  17. ^ a b c Guzis, Charles "Chuck" P. (2015-09-20). "Multi-platform distribution format". Sydex. Archived from the original on 2017-06-14. Retrieved 2017-06-14. [...] At the same time Micropolis was working a 5.25" drive that could hold about as much as an 8", using some tricks. The Micropolis drive was 100 tpi, 77 track and, by using GCR, could hold 12 512-byte sectors per track. That's 462 KiB. This was about 1977–78. [...] The [...] drive and controller implementation (ours was done by a guy we'd recruited from Sperry ISS) was [...] complex and expensive [...] Brother WP disks [...] are 38 track, single-sided, Brother-encoded GCR that hold [...] 120K on 2D floppies. [...]
  18. ^ Allen, David (February 1978). "A Minifloppy Interface" (PDF). BYTE. 3 (2). Kansas City, USA: 114, 116–118, 120, 122, 134–125. Archived from the original (PDF) on 2017-06-14. Retrieved 2017-06-14. [...] Of the alternative codes used to achieve double density, GCR (Group Coded Recording) looks quite attractive. Micro Peripherals Inc has implemented double density using GCR in a full size floppy disk and controller system currently being marketed. [...] GCR is nothing more than the old standby NRZ with its attendant advantages, but, since ordinary NRZ has no clocking information and a potentially high DC content during long strings of ones or zeros, the data is reformatted to eliminate the long strings. The reformatting converts each four bit group of original data into five bits of group coded data; the five bits in the encoded version will always have a mix of ones and zeros, even if the real data is all in one state. Reformatting in GCR can be accomplished in software, as opposed to MFM, etc, which almost unavoidably must be encoded and decoded in hardware. Thus, GCR has good possibilities as a low cost, high reliability scheme for achieving double density. [...][1]
  19. ^ "Floppies Claim Improved Performance". Computerworld. XIII (7). CW Communications, Inc.: 90. 1979-02-12. Retrieved 2017-06-14.
  20. ^ Schultz, Brad (1978-10-02). "Business Mini Weighs 65 Pound – What is Durango?". Computerworld. XII (40). CW Communications, Inc.: 1, 4. Retrieved 2017-06-13.
  21. ^ a b Comstock, George E. (2003-08-13). "Oral History of George Comstock" (PDF). Interviewed by Hendrie, Gardner. Mountain View, California, USA: Computer History Museum. CHM X2727.2004. Archived (PDF) from the original on 2017-03-23. Retrieved 2017-03-23.
  22. ^ a b Guzis, Charles "Chuck" P. (2009-09-13). "Durango GCR". Sydex. Archived from the original on 2017-11-04. Retrieved 2017-03-25.
  23. ^ a b "800 Technical Summary – 800 Series Business Computer System" (PDF). San Jose, CA, USA: Durango Systems, Inc. Archived (PDF) from the original on 2017-03-23. Retrieved 2017-03-23.
  24. ^ Guzis, Charles "Chuck" P. (October 2006). "The Durango F-85 Computer". Sydex. Archived from the original on 2017-03-23. Retrieved 2017-03-23.
  25. ^ a b c d e f g h Copy II Plus Version 9 – ProDOS/DOS Utilities – Data Recovery, File Management, Protected Software Backup (PDF). 9.0. Central Point Software, Inc. 1989-10-31 [1982]. Archived from the original (PDF) on 2017-05-07. Retrieved 2017-03-21.
  26. ^ a b Williams, Gregg; Moore, Rob (January 1985). "The Apple Story / Part 2: More History and the Apple III". BYTE (interview): 166. Archived from the original on 2012-02-12. Retrieved 2013-10-26. [2] (NB. Interview with Steve Wozniak, where he describes creating the Apple version of GCR.)
  27. ^ a b c d e f g h i j k Worth, Don D.; Lechner, Pieter M. (May 1982) [1981]. Beneath Apple DOS (4th printing ed.). Reseda, CA, USA: Quality Software. Retrieved 2017-03-21. [3] [4] [5] Archived 9 March 2016 at the Wayback Machine
  28. ^ a b c d e f Sather, James Fielding (1983). Understanding the Apple II – A Learning Guide and Hardware Manual for the Apple II Computer (1st ed.). Chatsworth, CA, USA: Quality Software. pp. 9–26, 9–27. ISBN 0-912985-01-1. Retrieved 2017-03-21.
  29. ^ a b c d e f Worth, Don D.; Lechner, Pieter M. (March 1985) [1984]. Beneath Apple ProDOS – For Users of Apple II Plus, Apple IIe and Apple IIc Computers (PDF) (2nd printing ed.). Chatsworth, CA, USA: Quality Software. ISBN 0-912985-05-4. LCCN 84-61383. Archived (PDF) from the original on 2017-03-21. Retrieved 2017-03-21. [6]
  30. ^ a b c d e Feichtinger, Herwig (1987). Arbeitsbuch Mikrocomputer (in German) (2 ed.). Munich, Germany: Franzis-Verlag GmbH. pp. 223–224. ISBN 3-7723-8022-0.
  31. ^ a b Apple Computer, Inc. (February 1982) [1978]. Integrated Woz Machine (IWM) Specification (PDF) (19 ed.). DigiBarn Computer Museum. Archived (PDF) from the original on 2016-08-06. Retrieved 2016-08-06.
  32. ^ a b Hildon, Karl J. H. (March 1985). "GCR codes". The Complete Commodore Inner Space Anthology (PDF). Milton, Ontario, Canada: Transactor Publishing Incorporated. p. 49. ISBN 0-9692086-0-X. Archived (PDF) from the original on 2017-03-23. Retrieved 2017-03-23. [7] (NB. Commodore GCR codes—but this reference erroneously claims that a 1-bit indicates a lack of a transition.)
  33. ^ "victor9k". FluxEngine documentation. Retrieved 2024-07-19.
  34. ^ "Victor 9000/Sirius 1 Specification" (PDF). commodore.ca. Archived (PDF) from the original on 2017-03-23. Retrieved 2017-03-23.
  35. ^ "Supplemental Technical Reference Material". Revision 0 (1st printing ed.). Scotts Valley, CA, USA: Victor Publications. 1983-03-23. Application Note: 002. [...] Single-sided floppy drive offers 80 tracks at 96 TPI [...] Double-sided floppy drive offers 160 tracks at 96 TPI [...] Floppy drives have 512 byte sectors; utilising a GCR, 10-bit recording technique. [...] Although the Victor 9000 uses 5 1/4-inch minifloppies of a similar type to those used in other computers, the floppy disks themselves are not readable on other machines, nor can the Victor 9000 read a disk from another manufacturers machine. The Victor 9000 uses a unique recording method to allow the data to be packed as densely as 600 kbytes on a single-sided single-density minifloppy; this recording method involves the regulation of the speed at which the floppy rotates, explaining the fact that the noise from the drive sometimes changes frequency.
  36. ^ "Chapter 7. Disk Drive Assembly". Victor 9000 Technical Reference Manual (PDF). Victor Business Products, Inc. June 1982. pp. 7–1..7–9. 710620. Archived (PDF) from the original on 2017-03-23. Retrieved 2017-03-23. [...] Track density is 96 tracks per inch, and recording density is maintained at approximately 8000 bits per inch on all tracks. [...] The VICTOR 9000 uses an encoding technique called group code recording (GCR) to convert the data from internal representation to an acceptable form. GCR converts each (4-bit) nibble into a 5-bit code that guarantees a recording pattern that never has more than two zeros together. Then data is recorded on the disk by causing a flux reversal for each "one" bit and no flux reversal for each "zero" bit. [...]
  37. ^ Sargent III., Murray; Shoemaker, Richard L.; Stelzer, Ernst H. K. (1988). Assemblersprache und Hardware des IBM PC/XT/AT (in German) (1 ed.). Addison-Wesley Verlag (Deutschland) GmbH / Addison-Wesley Publishing Company. ISBN 3-89319-110-0. . VVA-Nr. 563-00110-4.
  38. ^ "Victor 9000 format". DiscFerret wiki. Retrieved 2024-07-19.
  39. ^ Gieseke, Hans-Werner (2003-08-27). "Brother WP-1" (in German). Archived from the original on 2017-06-14. Retrieved 2017-06-14. (NB. Reportedly, the Brother WP-1 technical data was derived from page 109 of the user manual.)
  40. ^ French, Mick (2002-09-13). "Brother WP-6". Archived from the original on 2017-11-22. Retrieved 2017-06-14. [...] The 3.5" 240Kb disk drive is a single head Brother part no.13194989 and is connected with a 15 pin ribbon. [...] it initializes (formats) the disk to a capacity of 236.5Kb. [...]
  41. ^ Cotgrove, Michael S. (2009-02-26). "archaic floppy disc format". Retrieved 2017-06-14. [...] There were several 3.5" Brother disks that are completely nonstandard. [...] One had 1296 byte sectors and another had 12 x 256 byte GCR sectors [...]
  42. ^ "Model CE-1600F". Sharp PC-1600 Service Manual (PDF). Yamatokoriyama, Japan: Sharp Corporation, Information Systems Group, Quality & Reliability Control Center. July 1986. pp. 98–104. Archived (PDF) from the original on 2017-05-07. Retrieved 2017-03-23. GCR is an abbreviation of Group Coded Recording. A single byte, 8 bits, data are divided into two 4-bit data which is also converted onto a 5-bit data. Thus, a single byte (8 bits) is recorded on the media as a 10-bit data.
  43. ^ Sharp Service Manual Model CE-140F Pocket Disk Drive (PDF). Sharp Corporation. 00ZCE140F/SME. Archived (PDF) from the original on 2017-03-11. Retrieved 2017-03-11.
  44. ^ Moseley, Robin C. (April 1979). "Technical Forum: A Comparison of Bar Code Encoding Schemes" (PDF). BYTE. 4 (4). Andover, MA, USA: 50, 52. Retrieved 2017-06-14.

Further reading

[edit]
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Group_coded_recording&oldid=1255959806"