DOCSLIB.ORG

Atari Copy Protection

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Atari Copy Protection Atari Floppy Disk Copy Protection By Jean Louis-Guérin (DrCoolZic) Revision 1.4 – June 24, 2015 Atari Floppy Disk Copy Protection Table of Contents Table of Contents ................................................................................................................ 2 Chapter 1. Presentation ................................................................................................... 4 Chapter 2. Copy protections detail description ............................................................. 5 2.1 Protections based on data .................................................................................................... 5 2.1.1 Number of tracks (NOT) ........................................................................................................... 6 2.1.2 Shifted tracks (SFT) ................................................................................................................. 7 2.1.3 Track Layout Pattern (TLP) ...................................................................................................... 9 2.1.4 Number of Sectors (NOS) ........................................................................................................ 9 2.1.5 Sector Sizes (SSZ) ................................................................................................................. 10 2.1.6 Invalid ID Field (IIF) ................................................................................................................ 10 2.1.7 Duplicate Sector Number (DSN) ............................................................................................ 12 2.1.8 Sector within sector (SWS) .................................................................................................... 13 2.1.9 Non Standard DAM (NSD) ..................................................................................................... 13 2.1.10 Sector with No ID (SNI) .......................................................................................................... 14 2.1.11 Sector with No Data (SND) .................................................................................................... 14 2.1.12 Data CRC Error (DCE) ........................................................................................................... 14 2.1.13 Data Track (DTT) ................................................................................................................... 15 2.1.14 Hidden Data into GAP (HDG) ................................................................................................ 15 2.1.15 Hidden data into nonstandard tracks (HDT) .......................................................................... 15 2.1.16 Invalid Data in Gap (IDG) ....................................................................................................... 16 2.1.17 Invalid Sync-mark Sequence (ISS) ........................................................................................ 16 2.1.18 Partially formatted track (PUT) ............................................................................................... 16 2.1.19 Fuzzy Sector (FZS) ................................................................................................................ 17 2.1.20 Fuzzy Track (FZT) .................................................................................................................. 17 2.2 Protections based on timing ............................................................................................... 18 2.2.1 Long / Short Sector (LGS & SHS) .......................................................................................... 18 2.2.2 Long/Short Track (LGT & SHT) ............................................................................................. 19 2.2.3 Sector Bit-rate Variation (SBV) .............................................................................................. 19 2.2.4 No Flux Area (NFA) ................................................................................................................ 20 Chapter 3. Preservation of Atari floppy disks ...............................................................21 3.1 Cleaning a floppy disk to create correct image ................................................................ 21 3.2 Why do we need several revolutions for preservation? .................................................. 21 3.3 Kryoflux short presentation ................................................................................................ 23 3.4 Supercard Pro short presentation ...................................................................................... 23 Chapter 4. Technical Information ...................................................................................24 4.1 Atari Low-Level Formats ..................................................................................................... 24 4.1.1 Format for 9/10/11 Sectors of 512 Bytes ............................................................................... 25 4.1.2 “Standard” 128-256-512-1024 Bytes / Sector Format ........................................................... 26 4.2 WD1772 DPLL Input Circuitry ............................................................................................. 27 4.2.1 Description ............................................................................................................................. 27 4.2.2 WD1772 Detection of Fuzzy Border Bits ............................................................................... 29 4.3 WD1772 MFM track language ............................................................................................. 30 4.4 WD1772 Synchronization (sync marks detection) ............................................................ 31 4.5 False sync mark detection .................................................................................................. 32 4.6 Overlapping Sync Mark ....................................................................................................... 32 4.6.1 Overlapping $4489-$4489 ($A1-$A1) .................................................................................... 32 4.6.2 Overlapping $5224-$4489 ($C2-$A1) .................................................................................... 33 4.6.3 Overlapping $4489-$5224 ($A1-$C2) .................................................................................... 33 4.6.4 Overlapping $5224-$5224 ($C2-$C2) .................................................................................... 33 4.6.5 Invalid Sync sequence ........................................................................................................... 33 4.7 WD1772 Bug in Read/Write Track commands .................................................................. 34 4.8 WD1772 CRC Information.................................................................................................... 35 4.8.1 CRC Computation .................................................................................................................. 35 4.8.2 Playing with the CRC ............................................................................................................. 35 4.9 No Flux Area on Disk ........................................................................................................... 37 4.9.1 Checking NFA with the WD1772 ........................................................................................... 37 Copyleft Jean Louis-Guérin (DrCoolZic) – Rev 1.4 - June 24, 2015 Page 2 / 77 Atari Floppy Disk Copy Protection 4.9.2 Special case of No Flux Area over index ............................................................................... 38 4.10 Unformatted Diskette / Track / Sector ................................................................................ 41 4.10.1 Presentation ........................................................................................................................... 41 4.10.2 Partially unformatted track ..................................................................................................... 42 4.10.3 Partially formatted Track ........................................................................................................ 44 4.10.4 Unformatted track detection ................................................................................................... 44 4.10.5 How to reproduce unformatted areas on Floppy Disks? ........................................................ 44 4.11 Fuzzy Bits ............................................................................................................................. 46 4.11.1 Flux Reversals in Ambiguous Area ........................................................................................ 46 4.11.2 MFM Flux Timing Violation..................................................................................................... 46 4.11.3 Weak Bit ................................................................................................................................. 47 4.12 Write Splices ......................................................................................................................... 48 4.12.1 Sector write splices ................................................................................................................ 48 4.12.2 Track write splices .................................................................................................................. 49 4.13 Hidden data
Load more

Recommended publications
  • Devpac 3 for the Atari ST/STE/TT/Falcon030
    Devpac 3 for the Atari ST/STE/TT/Falcon030 By HiSoft Copyright © 1992 HiSoft. All rights reserved. Program: designed and programmed by HiSoft. Manual: written by Alex Kiernan, David Nutkins and Keith Wilson. This guide and the Devpac 3 program diskettes contain proprietary information which is protected by copyright. No part of the software or the documentation may be reproduced, transcribed, stored in a retrieval system, translated into any language or transmitted in any form without express prior written consent of the publisher and copyright holder(s). HiSoft shall not be liable for errors contained in the software or the documentation or for incidental or consequential damages in connection with the furnishing, performance or use of the software or the documentation. HiSoft reserves the right to revise the software and/or the documentation from time to time and to make changes in the content thereof without the obligation to notify any person of such changes. Published by HiSoft The Old School, Greenfield, Bedford MK45 5DE UK First Edition, August 1992-ISBN 0 948517 59 X CHAPTER I - INTRODUCTION 9 Introduction 9 Devpac 3 Disk Contents 9 Making a Working Copy 10 Registration Card 11 The README File 11 Installation 11 How to use the Manual 12 A Course for the Beginner 12 A Course for Seasoned Assembler Programmers 12 Devpac Version 2 Users 13 System Requirements 13 Typography 13 Acknowledgements 14 A Quick Tutorial 15 CHAPTER 2 - USING THE EDITOR 18 Introduction 18 A word about pop-up menus and dialogs 18 The Editor's windows 22 Switching
    [Show full text]
  • The Atari™ Compendium ©1992 Software Development Systems Written by Scott Sanders Not for Public Distribution
    The Atari™ Compendium ©1992 Software Development Systems Written by Scott Sanders Not for Public Distribution Introduction The following pages are a work in progress. The Atari™ Compendium (working title) is designed to be a comprehensive reference manual for Atari software and hardware designers of all levels of expertise. At the very least, it will (hopefully) be the first book available that documents all operating system functions, including any modifications or bugs that were associated with them, from TOS 1.00 to whatever the final release version of Falcon TOS ends up being. GEMDOS, BIOS, XBIOS (including sound and DSP calls), VDI, GDOS, LINE-A, FSM, AES, MetaDOS, AHDI and MiNT will be documented. Hardware information to the extent that information is useful to a software programmer will also be covered. This volume will not include hardware specifications used in the creation of hardware add-ons, a programming introduction designed for beginners, or an application style guide. All of the aforementioned exclusions will be created separately as demand for them arise. In addition, I also plan to market a comprehensive spiral- bound mini-reference book to complement this volume. By providing early copies of the text of this volume I hope to accomplish several goals: 1. Present a complete, error-free, professionally written and typeset document of reference. 2. Encourage compatible and endorsed programming practices. 3. Clear up any misunderstandings or erroneous information I may have regarding the information contained within. 4. Avoid any legal problems stemming from non-disclosure or copyright questions. A comprehensive Bibliograpy will be a part of this volume.
    [Show full text]
  • History of Operating Systems
    System Architecture History of Operating Systems Some slides from A. D. Joseph, University of Berkeley See also: www.osdata.com/kind/history.htm www.armory.com/~spectre/tech.html courses.cs.vt.edu/~cs1104/VirtualMachines/OS.1.html en.wikipedia.org/wiki/History_of_operating_systems © 2008 Universität Karlsruhe (TH), System Architecture Group 1 Moore’s Law Drives OS Change 1981 2006 Factor CPU MHz, 10 3200x4 1,280 Cycles/inst 3—10 0.25—0.5 6—40 DRAM capacity 128KB 4GB 32,768 Disk capacity 10MB 1TB 100, 000 Net bandwidth 9600 b/s 1 Gb/s 110,000 # addr bits 16 32 2 #users/machine 10 1 0.1 Price $25,000 $4,000 0.2 Typical academic computer 1981 vs 2006 © 2008 Universität Karlsruhe (TH), System Architecture Group 2 Moore’s Law Effects Nothing like this in any other area of business Transportation in over 200 years: Only 2 orders of magnitude from horseback @10mph to Concorde @1000mph Computers do this every decade What does this mean for us? Techniques have to vary over time to adapt to changing tradeoffs Let’s place a lot more emphasis on principles The key concepts underlying computer systems Less emphasis on facts that are likely to change over the next few years… Let’s examine the way changes in $/MIP has radically changed how OS’s work © 2008 Universität Karlsruhe (TH), System Architecture Group 3 Dawn of Time ENIAC: (1945-55) “The machine designed by Eckert and Mauchly was a monstrosity. When it was finished, the ENIAC filled an entire room, weighed 30 tons, and consumed 200 kilowatts of power.” http://ei.cs.vt.edu/~history/ENIAC.Richey.HTML © 2008 Universität Karlsruhe (TH), System Architecture Group 4 History Phase 1: 19481948--7070 Expensive Hardware Cheap Humans © 2008 Universität Karlsruhe (TH), System Architecture Group 5 History of Systems History OS: Evolution Step 0 APP OS Hardware Simple OS: One program, one user, one machine: examples: early computers, early PCs, embedded controllers such as Nintendo, cars, elevators OS just a library of standard services, e.g.
    [Show full text]
  • Computer Games Plus
    \ Ordering Info: Visa, MasterCard or COD. No personal Checks No surcharge for credit cards. COD add $4.00. Ohio add 5.5% tax. No cash refunds· Return products for Credit or Replacement only. Shipping Info: Free shipping on Orders over $100, in the continental USA. APO & FPO actual freight.We ship UPS. International: Actual freight. megs - Mega STe 1- $659 wllh chips 2.$1\1- $1$7 4~f- 5229 Adspeed STE- $249 Z-Ram/2.5- 520 ST- $75 BI(DS i5'C(·6P(daJ • $995 Autoswitch Overscan· 5109 Priuter or Modem • $7 wllh chi". 2.91- $147 Blitz cable w/software - 546.95 Star NXI001 ·5155 2mrg.ISOBDIlAI\I Floppy • Z-Ram/Mega 11- 4Megs - $75 , wllh chips 2.91- $147 D.E.K.A. intert'ace- 595 Star NX·2420· $249 ST Book & FalCon- !!CALL!! • 1 Meg Chips $4.50 ea Drive Master - 532 ST/time (under rom clock) - $43 STe SIMMS Imeg each - $40 •..••. Simms - $40ea Drive cable 6 ft $13.95 Supercharger W/IMeg - $289 SM147 14"· $199 • ..• JRl Board (uses simms)- $99 DVf·VCR hd backup· $69.95 Synchro 11- $59 SC1224 - $200 ••.•.••.••.• Xtra RAM ST Deluxe- $79 .. ""nllnv., lID TEC (Tos extension card)· 5135 Haud Scanner Mlg .. ph· lEC Mega bus- 51SS SC1435 14" color - $349 ').' (uses simms) Hand Scanner GoI4e"I",,,e 5llS :" TOS 2.06 • $70 1.4Meg floppy kit· $139 .: (I@JuU"JOJilUij UP Des~et 500 printer· $469 , .... , Puwl!r (Cor WM enu~alon)' ICD Adscsi Plus - 593.77 .,. Trackball(Krall)' 559 "aster ~ ~'!!!J ICD Adscsi (no clock) - 583.77 : •••• • Trackball(cordless)· $88 • • Master 5S (5.25") - $199 Adscsi Micro (Mega's) - 5": Turbo 20· 5299 SCSI dual drive cabl~ - $10 .: .
    [Show full text]
  • Debian GNU/Linux Installation Guide Debian GNU/Linux Installation Guide Copyright © 2004, 2005 the Debian Installer Team
    Debian GNU/Linux Installation Guide Debian GNU/Linux Installation Guide Copyright © 2004, 2005 the Debian Installer team This document contains installation instructions for the Debian GNU/Linux 3.1 system (codename “sarge”), for the Motorola 680x0 (“m68k”) architecture. It also contains pointers to more information and information on how to make the most of your new Debian system. Note: Although this installation guide for m68k is mostly up-to-date, we plan to make some changes and reorganize parts of the manual after the official release of sarge. A newer version of this manual may be found on the Internet at the debian-installer home page (http://www.debian.org/devel/debian-installer/). You may also be able to find additional translations there. This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License. Please refer to the license in Appendix E. Table of Contents Installing Debian GNU/Linux 3.1 For m68k.................................................................................viii 1. Welcome to Debian ......................................................................................................................... 1 1.1. What is Debian?................................................................................................................... 1 1.2. What is GNU/Linux? ........................................................................................................... 2 1.3. What is Debian GNU/Linux?..............................................................................................
    [Show full text]
  • Emutos and Atari 16/32 Bit Machines
    EMUTOS AND ATARI 16/32 BIT MACHINES Very briefly ;-) Christian Zietz – September 2020 1985 Atari ST • 68000 CPU @ 8 MHz • Initially 512 kB RAM, later up to 4 MB • 2 color modes and a high-res (640 x 400) monochrome mode • Initially separate floppy drive, later builtin 720k drive • MIDI Atari 1040STF – © Bill Bertram, 2006 1985 TOS • GEM UI and GEMDOS originally licensed from Digital Research • But independently developed further by Atari • Entirely in ROM • Single-task • GUI with desktop metaphor • Text mode for command line applications also available 1989 1990/1991 1992 Atari STE Atari TT & MegaSTE Atari Falcon • More colors • Workstations • 68030 • PCM sound • MegaSTE: 16 MHz, • DSP • TOS 1.06/1.62 FPU, VME bus • True-color graphics • TT: 68030, FPU, more • TOS 4 RAM, VME bus, high- res up to 1280 x 960 • TOS 2 & 3 Sea Of Colour demo by Dead Hackers Society on Atari STE Atari TT – by Tim Kovack Atari Falcon – © Wikipedia user LosHawlos 1996 1999 2001 Atari Corp. ceases Caldera releases PC EmuTOS development operations GEM under GPL begins • IP rights go to game • Shares a common • Born out of necessity: company Hasbro / ancestor with TOS bundle a legal TOS Infogrames / Atari with emulators • But they diverged • Atari TOS is still • Based on PC GEM copyrighted • E.g. restrictions code imposed by an Apple lawsuit • Own development of low level BIOS/XBIOS for Atari HW • Many improvements since! 2020: EMUTOS 1.0 What makes EmuTOS special? Supports all Atari computers and some non-Atari machines (even Amiga!) Also great for emulators, e.g., API to Aranym and Hatari Provided in many variants (ROM & RAM versions) in several languages Built-in hard disk driver with PC (FAT16) partition and filesystem support Built-in command line interface (EmuCON) Support for 3rd party hardware, e.g.
    [Show full text]
  • Evoluzione Dei Sistemi Operativi – Prof
    EEvvoolluuzziioonnee ddeeii SSiisstteemmii OOppeerraattiivvii prof. Claudio Maccherani - 2008 Anni '40, assenza di SO, "programmatore-operatore" Inizialmente, tra il 1945 e il 1955, quando gli elaboratori elettronici erano costituiti da valvole termoioniche, occupavano intere stanze, erano lentissimi e costosissimi - li potevano avere solo grossi centri di ricerca o Università, e inaffidabili (a causa delle valvole che si rompevano molto frequentemente), non esiste il concetto di Sistema Operativo. Il programmatore inseriva il programma, scritto in linguaggio macchina, attraverso primitivi lettori di schede perforate e i risultati venivano inviati alla stampante. Un primo abbozzo di SO si è avuto con la messa a disposizione di tutti i programmatori dei sottoprogrammi di I/O e con l’avvento del linguaggio simbolico Assembler. Anni '50, i primi Sistemi Operativi, Sistemi Batch [I generazione] Tra il 1955 e il 1965, grazie alla rivoluzionaria invenzione del transistor gli elaboratori - chiamati Mainframe - divennero affidabili e furono costruiti in serie, pur restando macchine grosse e costosissime. Gli acquirenti possibili erano Centri di Calcolo, le Università e le banche. L’alto costo rendeva inaccettabile l’uso dell’elaboratore da parte di una sola persona alla volta (con conseguente inattività del computer mentre il programmatore pensava al da farsi) e l’avvento del linguaggio ad alto livello Fortran, nel 1955, apre le porte ad un numero crescente di programmatori. Il primo SO fu prodotto dalla General Motors per il proprio IBM 701. Non essendo stata ancora introdotta la tecnologia di accesso diretto alla memoria (DMA) tutte le operazioni di input/output erano a carico della CPU, con conseguente rallentamento dell’esecuzione vera e propria.
    [Show full text]
  • HISTORY of OPERATING SYSTEMS Timeline of The
    HISTORY OF OPERATING SYSTEMS Timeline of the events in the history of computer operating system:- Ubuntu Releases after 2000 2004-10 Ubuntu 4.10 (first released version) 2005-04 Ubuntu 5.04 2005-10 Ubuntu 5.10 2006-06 Ubuntu 6.06 (LTs) 2006-10 Ubuntu 6.10 2007-04 Ubuntu 7.04 2007-10 Ubuntu 7.10 2008-04 Ubuntu 8.04 2008-10 Ubuntu 8.10 2009-04 Ubuntu 9.04 2009-10 Ubuntu 9.10 2010-04 Ubuntu 10.04 MICROSOFT WINDOWS AFTER 2000:- 2000-02 Windows 2000 (first of the Windows server operating systems to drop the ©NT© marketing) 2000-09 Windows Me (last of the Windows 9x line of operating systems to be produced and sold) 2001-10 Windows XP (succeeded Windows Me and Windows 2000, successfully merging the ©professional© NT line of desktop operating systems with the ©home© 9x line of operating systems) 2002 Windows XP 64-bit Edition 2002-09 Windows XP Service Pack 1 2003-03 Windows XP 64-bit Edition, Version 2003 2003-04 Windows Server 2003 2004-08 Windows XP Service Pack 2 2005-03 Windows Server 2003 Service Pack 1, Windows XP Professional x64 Edition 2006-03 Windows Server 2003 R2 2006-11 Windows Vista 2007-03 Windows Server 2003 Service Pack 2 2007-11 Windows Home Server 2008-02 Windows Vista Service Pack 1, Windows Server 2008 2008-04 Windows XP Service Pack 3 2009-05 Windows Vista Service Pack 2 2009-10 Windows 7(22 occtober 2009), Windows Server 2008 R2 EVENT IN HISTORY OF OS SINCE 1954:- 1950s 1954 MIT©s operating system made for UNIVAC 1103 1955 General Motors Operating System made for IBM 701 1956 GM-NAA I/O for IBM 704, based on General Motors
    [Show full text]
  • Janus Manual.Pdf
    Table of contents 1 Table of contents General information 3 1.1 Information about Janus 3 Janus in the overview 3 Scope of supply of the January US package 4 1.2 Hardware prerequisites 5 Request of the PC 5 Configuration possibilities of Janus 5 1.3 Kundenunterstiitzung for problems 6 1.4 Update of the JANUS software 7 15 Legal 7 Guaranty on hardware 7 Guaranty on software 8 Copyrights • 8 Registered trade mark . 9 Installation 11 2.1 Installation of the JANUS card 11 2.1.1 Equipment of the JANUS card 11 Structure of the card 12 Janus Hardware: Janus und Installation of the TOS EPROMs 13 Janus 020 - Revision 1.03 Installation of the memory SIMMs 14 The Janus 020 Upgrade kits 15 Janus Treiber-Software: Version 1.40 2.1.2 Installation of the JANUS card into the PC 18 What do, wenn's doesn't do? 20 2.2 Installation of the driver software 24 Contents of the JANUS diskette 24 Documentation: 6. Auflage Installation of JANUS.EXE 24 Stand: 8. April 1995 General information 3 Table of contents 2 1 General information The Atari in your PC 27 3.1 The driver software JANUS.EXE 27 3.1 Set different modes 27 1.1 Information about Janus Dissolutions of diagram of the PC 29 The local modes (compatibility mode) 30 The dual modes 30 Janus in the overview Memory test 31 3.2 Use of the PC peripheral device 32 The Janus US card transforms your PC into a Atari processor, which you can use 3.2.1 Keyboard 32 parallel to DOS and Windows applications.
    [Show full text]
  • Atari Hard Disk File Systems Reference Guide
    ATARI HARD DISK FILE SYSTEMS REFERENCE GUIDE Jean Louis-Guérin (DrCoolZic) Version 1.2b September 2014 Table of Content How to Read this Document ............................................................................................... 5 PART I – ATARI HARD DISK FILE SYSTEM PARTITIONING GUIDE ............................... 7 Chapter 1. Partitioning Information ................................................................................. 8 1.1 Hardware Consideration .......................................................................................................... 8 1.2 Hard Disk File System Primer ................................................................................................. 8 1.3 Preparing a Drive ..................................................................................................................... 9 Chapter 2. Types of Partition used on Atari ..................................................................10 2.1 TOS Partitions ....................................................................................................................... 10 2.2 DOS/FAT Partitions ............................................................................................................... 10 2.2.1 Type and Limit of DOS/FAT Partitions .............................................................................. 10 2.2.2 Small DOS/FAT Partitions ................................................................................................. 10 2.2.3 Large DOS/FAT Partitions ................................................................................................
    [Show full text]
  • GEMDOS Function Reference
    GEMDOS Function Reference T HE ATARI COMPENDIUM Cauxin() - 2.39 Cauxin() WORD Cauxin( VOID ) Cauxin() waits for the next available data byte from GEMDOS handle 2 (normally device ‘aux:’) and when available, returns it in the low byte of the returned WORD. OPCODE 3 (0x03) AVAILABILITY All GEMDOS versions. BINDING move.w #$3,-(sp) trap #1 addq.l #2,sp RETURN VALUE The WORD value contains the retrieved byte in the lower eight bits. The contents of the upper 8 bits are currently undefined. CAVEATS This function can cause flow control problems. When using this function while its handle is redirected, an end-of-file condition will hang the system. GEMDOS version 0.30 and all MiNT versions correct this bug. MiNT returns MINT_EOF (0xFF1A) when the end-of-file is reached. In addition, if this handle is redirected to something other than ‘aux:’, an end-of- file will hang the system. Besides these known bugs, this function is used by many ‘C’ compilers to redirect standard error messages. It is therefore advisable to use Bconin() instead. SEE ALSO Cauxis(), Cauxout(), Bconin() Cauxis() WORD Cauxis( VOID ) Cauxis() indicates whether GEMDOS handle 2 (normally device ‘aux:’) has at least one character waiting. OPCODE 18 (0x12) AVAILABILITY All GEMDOS versions. BINDING move.w #$12,-(sp) T HE ATARI COMPENDIUM 2.40 – GEMDOS Function Reference trap #1 addq.l #2,sp RETURN VALUE The return value will be DEV_READY (-1) if at least one character is available for reading or DEV_BUSY (0) if not. CAVEATS When using this function while its handle is redirected, an end-of-file condition will hang the system.
    [Show full text]
  • The Atari™ Compendium ©1992 Software Development Systems Written by Scott Sanders Not for Public Distribution
    atariforge.org dev-docs.atariforge.org The Atari™ Compendium ©1992 Software Development Systems Written by Scott Sanders Not for Public Distribution Introduction The following pages are a work in progress. The Atari™ Compendium (working title) is designed to be a comprehensive reference manual for Atari software and hardware designers of all levels of expertise. At the very least, it will (hopefully) be the first book available that documents all operating system functions, including any modifications or bugs that were associated with them, from TOS 1.00 to whatever the final release version of Falcon TOS ends up being. GEMDOS, BIOS, XBIOS (including sound and DSP calls), VDI, GDOS, LINE-A, FSM, AES, MetaDOS, AHDI and MiNT will be documented. Hardware information to the extent that information is useful to a software programmer will also be covered. This volume will not include hardware specifications used in the creation of hardware add-ons, a programming introduction designed for beginners, or an application style guide. All of the aforementioned exclusions will be created separately as demand for them arise. In addition, I also plan to market a comprehensive spiral- bound mini-reference book to complement this volume. By providing early copies of the text of this volume I hope to accomplish several goals: 1. Present a complete, error-free, professionally written and typeset document of reference. 2. Encourage compatible and endorsed programming practices. 3. Clear up any misunderstandings or erroneous information I may have regarding the information contained within. 4. Avoid any legal problems stemming from non-disclosure or copyright questions. A comprehensive Bibliograpy will be a part of this volume.
    [Show full text]