DOCSLIB.ORG

The Atari™ Compendium ©1992 Software Development Systems Written by Scott Sanders Not for Public Distribution

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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. For now you should know that I have mainly relied on five major sources of information: 1. Atari Developer Documentation, including, but not limited to, original OS docs, release notes, newsletters, and technical support. 2. Compute’s AES/TOS/VDI series. This series seems to be the most complete English reference available, however, its usage is limited by the fact it is only current as of TOS 1.02 3. Lattice C Atari Library Manual and Addendum 4. Atari Profibuch - Excellent German text. 5. Developer Roundtable on GEnie and Compuserve. How to Edit... Below are some simple suggestions as to how to notate any changes you would like to see made. I understand you are probably just as busy as I usually am so if you can’t take the time to follow these steps, ragged handwriting in the corner would be just as appreciated. Included in your package should be seven items: 1. This introduction letter. 2. A binder. 3. Revision notes 4. Looseleaf notebook paper. 5. Two highlighter pens 6. Dividers 7. The latest revision of the text If you are missing any items, please contact me. Each revision will be accompanied by a set of revision notes. These will highlight what to look for, what I already know is wrong and am planning to change, and what has changed since last time. The looseleaf notebook paper should be used to make general suggestions as to content, style (writing/typesetting), and so on.... When proofing the text use the blue highlighter to circle spelling, grammar, or style errors (any typo). The green highlighter is for blatant errors or misunderstandings where an explanation is necessary. Please notate the error and correction in the margins. If it is a very large misunderstanding beyond simply writing it down, please call me or E-Mail me. Also, as a part of the volume will be a listing of standard conventions. The following is a brief listing of conventions used in the book: Typestyle Meaning The quick brown fox.... Normal Text WORD appl_init(VOID) Function Definitions mode, flag, ap_id program/system variables WORD, TOS, WM_CLOSED macros, typedef’s, define’s, OS components typedef struct { Program listings/bindings A basic explanation is listed... Text in tables CTRL-G Keyboard keys OPCODE Headings Any questionable stray from the conventions should be notated as a possible error. Revision Schedule I would like to swap edited text with new revisions about every two weeks. The final revision should be approved by November 15th to try for a release date of December 15th. This schedule is not fixed and I will be in contact to find out what’s best for you. Thank You... Thank you for your time and effort. Your name will be credited if you desire and you should check for it in a final revision. SCOTT D. SANDERS, OWNER SOFTWARE DEVELOPMENT SYSTEMS i CONTENTS Foreword vii Chapter 1: Introduction to Atari Programming.........1.1 Atari Computer Hardware............................................................................. 1.3 Atari Computer Software............................................................................... 1.6 Atari GEM ..................................................................................................... 1.7 Third-Party System Software......................................................................... 1.8 Programming Languages............................................................................... 1.9 Conventions.................................................................................................. 1.10 Chapter 2: GEMDOS....................................................2.1 Overview ........................................................................................................ 2.3 The TOS File System ..................................................................................... 2.3 Memory Management .................................................................................... 2.8 GEMDOS Processes...................................................................................... 2.9 GEMDOS Vectors ....................................................................................... 2.13 MiNT............................................................................................................ 2.14 MiNT Interprocess Communication............................................................ 2.27 MiNT Debugging......................................................................................... 2.31 The MINT.CNF File..................................................................................... 2.33 GEMDOS Character Functions.................................................................. 2.34 GEMDOS Time & Date Functions.............................................................. 2.35 GEMDOS Function Calling Procedure...................................................... 2.35 GEMDOS Function Reference.................................................................... 2.37 Chapter 3: BIOS...........................................................3.1 Overview ........................................................................................................ 3.3 System Startup................................................................................................ 3.3 OS-Header ..................................................................................................... 3.4 Cookie Jar...................................................................................................... 3.8 BIOS Devices............................................................................................... 3.14 Media Change.............................................................................................. 3.15 BIOS Vectors ............................................................................................... 3.18 T HE ATARI COMPENDIUM ii – Contents The XBRA Protocol ......................................................................................3.20 BIOS Function Calling Procedure ..............................................................3.22 BIOS Function Reference............................................................................3.24 Chapter 4: XBIOS.........................................................4.1 Overview .........................................................................................................4.3 Video Control .................................................................................................4.3 The Falcon030 Sound System.........................................................................4.6 The DSP ..........................................................................................................4.8 User/Supervisor Mode..................................................................................4.12 MetaDOS.......................................................................................................4.12 Keyboard and Mouse Control ......................................................................4.12 Disk Functions..............................................................................................4.14 The Serial Port .............................................................................................4.16 Printer Control.............................................................................................4.18 Other XBIOS Functions...............................................................................4.18 XBIOS Function Calling Procedure............................................................4.19 XBIOS Function Reference .........................................................................4.21 Chapter 5: Hardware....................................................5.1 Overview .........................................................................................................5.3
Load more

Recommended publications
  • @ LATTICE,INC. It Is
    @ LATTICE,INC. P. O. BOX 3072 ·GLENÉLLYN·LLNOIS 60138· 3l2/858ñ9!5OU1NX9lO29l-2l9O TECHNICAL BULLETIN TB841101.001 DATE: November 1, 1984 PRODUCT: 8086/8088 C Compiler SUBjECT: Known Bugs in Version 2.14 Recently three bugs concerning the Version 2.14 libraries and startup modules have come to light. Two of these pertain to the sensing and use of the 8087 co-processor, and the other concerns the use of the "malloc'° and "getmem" functions under MS-DOS 1 in the s and P models of the compiler. In addition some code was oMtted from the file " main.c". 1. Floating Point Bugs (a) Sensing cjf the 8087 The technique employed in the run-time library to sense the presence of the 8087 co-processor does not work in V2.14 because the 8087 is not initialized prior to the test. Correcting this problem is rather easy. You need only add a line of code to the file °'c.asm" provided with the compiler and reassemble this to replace the current "c.obj". file In the file "c.asm" you will find a line: CALL JLAIN just prior to this line, insert the fcülowing line DB ODBh,OE3h ; FNINIT instruction Then reassemble "c.asm" for each of the memory models as follows: -- Copy "c.asm" to the appropriate model subdirectory (i.e., \lc\s, \lc\d, \lc\p, or \lc\l) so that is in the same directory as "dos.mac" for it the appropriate memory mcdel. -- Use the command 1 @ LATTICE,1NC. W P. O. BOX 3Q72 ·GL£N ELLYN ·ILLNO1S 60138 · 312/858-7950·TWX9lO291-2 masm c; to assemble "c.asm" into "c.obj".
    [Show full text]
  • DECEMBER 1984 Editorial
    SECRET UJUJUVC!JUJUJlb f5l5CBl!JWVU~ !D~~WCB~ Cf l!l U1 v ffil! f] Ill~(! ffi g 00 (!{il C!J l! '7 00 {iJ U1 ~ [1{iJ w~ NOV-DEC 1984 EO 1. 4. (c) P .L. 86- 36 . TRENDS IN HF COMMUNICATIONS (U) •••••••••••• • ••• J.._ ___---..._.1. \\:>............ 1 • SWITCHBOARD: • PAST, PRESENT AND FUTURE (U) •• ~ ............. I • • \ I .......... 5 \ OUT OF MY DEPTH (U) .......................•............•...; .. i .. \ ... ·........ 7 . • • • • • • • • • • • • • • • • • • • • • • ! I ...\ .......... s 1 EXPLORING A DOS DISKETTE (U)................... I ...... :; , ........ 12 HUMAN FACTORS (U) •••••••••••••••••••••••••••••• I l ........ 22 CAN YOU TOP THIS? (U) ........................... E. Leigh Sawyer ... , \~ ••••••• 24 PERSONAL COMPUTING IN A GROUP (U).............. • •••••• 25 FACTION LINE (U) ••• , •••••••••••••••••••••••• • ••• Cal Q. Lator •••••••••••••• • 35 NSA-CROSTIC NO. 59 (U) •••.•••••••••••••••••••••• D.H.W.;.,, ••••••••••••••••• 36 'flllS BOC\'.JMBNT <JONTl.INS <JOBl'JWORB MATl'JRIAh Ghi'tSSIFIEB BY tfSA/SSSM lH 2 SECRET BEGI:a\-SSIFY 0N. 0r igiriet iug Agency's Betezminatior:t Reqaized Declassified and Approved for Release by NSA on 'I 0- '16-2012 pursuant to E 0 . 13526, MOR Case # 54 77B OCID: 4009933 Published by Pl, Techniques and Standards EO 1. 4. ( c) P~L. 86-36 VOL. XI, No. 11-12 NOVEMBER-DECEMBER 1984 Editorial PUBLISHER BOARD OF EDITORS Edi.tor ...•••......_I _______ ... 1(963-3045s .) Product ion .•....•. I .(963-3369s) . : : : :· Collection .••••••..•••• i------.jc963-396ls) Computer Security •: ' •••••• 1 ,(859-6044) Cryptolinguist ics. l 963-1 f03s) Data Systems .•...•.•• ·l ., 963-4,953s) Information Science " • ..... I lc963-.5111s> Puzzles .......... David H. Williams'f(9637'Il03s) Special Research • ..•. Vera R. Filby;! C968'-7119s) Traffic Analysis •. Robert J. Hanyo!<f! (968-3888s) For subscript ions .. , send name and organizat~on to: I w14I i P.L.
    [Show full text]
  • Compiler and Library Tim Hunter, SAS Institute Inc.; Cary, NC
    An Overview of the SASle· Compiler and Library Tim Hunter, SAS Institute Inc.; Cary, NC ABSTRACT The Compiler This paper describes the major features of the SAS/C® compiler The compiler implemented the C language as described in the and library and discusses the development history oftha product. then definitive book on C, Kernighan and Ritchie's The C Pro­ The enhancements in the current production release are outlined. .gramming Language: Because the compiler was implemented for Some possible enhancements for future releases are described. IBM 370's, it included many features that were thought necessary for that architecture and for programmers who were used to working In that environment. The foliowing list describes some INTRODUCTION of these features: • The generated code IS fully reentrant, even allowing The SAS/C product has had four production reteases in its five modification of external variables. years of development. Each release included many new features and enhancements of existing features. Not only is the compiler • The compiler supports a number of built-in functions. used exclustve1y for Version 6 of the SA&!' System on ISM® main~ These are functions for which the compiler generates frame hosts, it is the leading C compiter in this market. Although instructions directly into the instruction stream, rather than the compiler and IIDrary is heavily orlented to use in large soft­ generating a call to a separately linked version of the ware systems, it is an efficient tool for any software project that function. In this release, the following functions were is written in the C langauge. implemented as built-in functions: The primary elements of the SASIC product are the the compiler strlen memcmpp ,b, strcpy memcP¥P ceil and run-time library.
    [Show full text]
  • CP/M-80 Kaypro
    $3.00 June-July 1985 . No. 24 TABLE OF CONTENTS C'ing Into Turbo Pascal ....................................... 4 Soldering: The First Steps. .. 36 Eight Inch Drives On The Kaypro .............................. 38 Kaypro BIOS Patch. .. 40 Alternative Power Supply For The Kaypro . .. 42 48 Lines On A BBI ........ .. 44 Adding An 8" SSSD Drive To A Morrow MD-2 ................... 50 Review: The Ztime-I .......................................... 55 BDOS Vectors (Mucking Around Inside CP1M) ................. 62 The Pascal Runoff 77 Regular Features The S-100 Bus 9 Technical Tips ........... 70 In The Public Domain... .. 13 Culture Corner. .. 76 C'ing Clearly ............ 16 The Xerox 820 Column ... 19 The Slicer Column ........ 24 Future Tense The KayproColumn ..... 33 Tidbits. .. .. 79 Pascal Procedures ........ 57 68000 Vrs. 80X86 .. ... 83 FORTH words 61 MSX In The USA . .. 84 On Your Own ........... 68 The Last Page ............ 88 NEW LOWER PRICES! NOW IN "UNKIT"* FORM TOO! "BIG BOARD II" 4 MHz Z80·A SINGLE BOARD COMPUTER WITH "SASI" HARD·DISK INTERFACE $795 ASSEMBLED & TESTED $545 "UNKIT"* $245 PC BOARD WITH 16 PARTS Jim Ferguson, the designer of the "Big Board" distributed by Digital SIZE: 8.75" X 15.5" Research Computers, has produced a stunning new computer that POWER: +5V @ 3A, +-12V @ 0.1A Cal-Tex Computers has been shipping for a year. Called "Big Board II", it has the following features: • "SASI" Interface for Winchester Disks Our "Big Board II" implements the Host portion of the "Shugart Associates Systems • 4 MHz Z80-A CPU and Peripheral Chips Interface." Adding a Winchester disk drive is no harder than attaching a floppy-disk The new Ferguson computer runs at 4 MHz.
    [Show full text]
  • 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]
  • Related Links History of the Radio Shack Computers
    Home Page Links Search About Buy/Sell! Timeline: Show Images Radio Shack TRS-80 Model II 1970 Datapoint 2200 Catalog: 26-4002 1971 Kenbak-1 Announced: May 1979 1972 HP-9830A Released: October 1979 Micral Price: $3450 (32K RAM) 1973 Scelbi-8H $3899 (64K RAM) 1974 Mark-8 CPU: Zilog Z-80A, 4 MHz MITS Altair 8800 RAM: 32K, 64K SwTPC 6800 Ports: Two serial ports 1975 Sphere One parallel port IMSAI 8080 IBM 5100 Display: Built-in 12" monochrome monitor MOS KIM-1 40 X 24 or 80 X 24 text. Sol-20 Storage: One 500K 8-inch built-in floppy drive. Hewlett-Packard 9825 External Expansion w/ 3 floppy bays. PolyMorphic OS: TRS-DOS, BASIC. 1976 Cromemco Z-1 Apple I The Digital Group Rockwell AIM 65 Compucolor 8001 ELF, SuperELF Wameco QM-1A Vector Graphic Vector-1 RCA COSMAC VIP Apple II 1977 Commodore PET Radio Shack TRS-80 Atari VCS (2600) NorthStar Horizon Heathkit H8 Intel MCS-85 Heathkit H11 Bally Home Library Computer Netronics ELF II IBM 5110 VideoBrain Family Computer The TRS-80 Model II microcomputer system, designed and manufactured by Radio Shack in Fort Worth, TX, was not intended to replace or obsolete Compucolor II the Model I, it was designed to take up where the Model I left off - a machine with increased capacity and speed in every respect, targeted directly at the Exidy Sorcerer small-business application market. Ohio Scientific 1978 Superboard II Synertek SYM-1 The Model II contains a single-sided full-height Shugart 8-inch floppy drive, which holds 500K bytes of data, compared to only 87K bytes on the 5-1/4 Interact Model One inch drives of the Model I.
    [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]
  • Latticemico32 Tutorial
    LatticeMico32 Tutorial June 2015 Copyright Copyright © 2015 Lattice Semiconductor Corporation. All rights reserved. This document may not, in whole or part, be reproduced, modified, distributed, or publicly displayed without prior written consent from Lattice Semiconductor Corporation (“Lattice”). Trademarks All Lattice trademarks are as listed at www.latticesemi.com/legal. Synopsys and Synplify Pro are trademarks of Synopsys, Inc. Aldec and Active-HDL are trademarks of Aldec, Inc. All other trademarks are the property of their respective owners. Disclaimers NO WARRANTIES: THE INFORMATION PROVIDED IN THIS DOCUMENT IS “AS IS” WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND INCLUDING WARRANTIES OF ACCURACY, COMPLETENESS, MERCHANTABILITY, NONINFRINGEMENT OF INTELLECTUAL PROPERTY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL LATTICE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (WHETHER DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL, INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OF OR INABILITY TO USE THE INFORMATION PROVIDED IN THIS DOCUMENT, EVEN IF LATTICE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME JURISDICTIONS PROHIBIT THE EXCLUSION OR LIMITATION OF CERTAIN LIABILITY, SOME OF THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. Lattice may make changes to these materials, specifications, or information, or to the products described herein, at any time without notice. Lattice makes no commitment to update this documentation. Lattice reserves the right to discontinue any product or service without notice and assumes no obligation to correct any errors contained herein or to advise any user of this document of any correction if such be made.
    [Show full text]
  • Application of Microcomputers 1N Bridge Design
    Transportation Research Record 1072 15 Application of Microcomputers 1n Bridge Design RONALD A. LOVE, FURMAN W. BARTON, and WALLACE T. McKEEL, Jr. ABSTRACT The use of microcomputers in bridge design activities in state transportation departments was evaluated through contacts with 32 state agencies. Although pres­ ent use of microcomputers was found to be 1 imi tea, subsequent research showed that the current generation of 16-bit machines offers significant advantages in complementing existing computing facilities in a manner that fully uses the power of both mainframe and microcomputer. The ability of microcomputers to run large bridge design applications in a stand-alone mode was demonstrated by successfully downloading and converting four mainframe programs. Running design and analysis programs in a stand-alone mode frees the mainframe CPU and increases access to software that can be run repetitively without consideration of mainframe costs. When access to larger applications on the mainframe is required, the microcomputer used as an intelligent terminal can process input data locally and send them to the mainframe for processing. Output data, in return, can be downloaded to the microcomputer and reviewed off-line or input into microcomputer applications such as spreadsheets or graphics packages for further processing. Computer applications in engineering design have had preferred alternative for using much of the bridge a dramatic effect on the analysis and design process design software available. In Virginia, as in many in general. Automating analysis and design proce­ other states, many bridge design activities have dures has relegated much of the computational burden been decentralized in district offices across the to machines, allowing the engineer more time to state.
    [Show full text]