DOCSLIB.ORG

Communicator Software Tools

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Communicator Software Tools Communicator Software Tools Part No 0452,013 Issue 1 25 Aujiusl 1937 Copyright Acom Computers Limited 1987 Neither the whole nor any part or the inrormation contained in, or the product described in. this manual may be adapted or reproduced in any material rorm except with the prior written permission of Acorn Computers Limited. Withinthis publication the term 'BBC is used as an abbreviation for 'British Broadcasting Corporation'. The product described in this manual is subject to continuous developments and improvements. All particulars of the product and its use (including the information in this manual) are given by Acom Computers in good faith. In case of dilTiculty please contact your supplier. Every step is taken in ensure that the quality of sdtware and documentation is as high as possible. However,it should be noted that softwarecannot be written to be completely free of errors. To help Acom rectify future versions, suspected deficiencies in software and documentation should be notified in writing, using the Fault Report Form supplied, to the following address: Cuatonwr Servlcao Oepacttnent, Acorn Computora Limited, Fulbourn Road, Cherry Hinton, Cambridqe CBl 4JN All maintenance and service on the product must be carried out by Acom Computers' authorised dealers. Acom Computers can accept no liability whatsoever for any loss or damage caused by service or maintenance by unauthorised personnel. This manual is intended only to assist the reader in the use of the product,and therefore Acom Computersshall not be liable for any or damage whatsoeverarising from the use of any information or particulais in, or any eiror or omission in, this manual, or any incorrect use of the product. The approval of Communicator for connection to telephone networks is INVALIDATED if it is subject to any modificationin any material way not authorised by BABT or is used with, or connected to: (0 internal software that had not been formally accepted by BABT (ii) external control software or external control apparatus which causes the operation of the modem or associated call set-up equipment to contravene the requirements of the standards set out in BABT/SITS/82/D05S/D. Published by AcomComputers Limited, Fulboum Road,CherryHinton,Cambridge CBl 4JN Comnutideator Software Toob Cmttmumaaor Software Tools Contents . IntroducUon 1.1 1.1 Hardware 1.1 1.2 Software 13 1.3 Macro and Definition Files 13 1.4 BASIC Flies 13 1.S Documentation 1.4 1.6 Sarety and approvals 1.6 . Introduction to Cbmmunicator Programming 2.1 2.1 An Overview of CommunicatorSystems Software 2.1 2.1.1 Software Levels 2.1 2.1.2 Software Categories 2.2 2.1.3 The Menu Module 2.2 2.1.4 The Terminal Session Software 2.2 2.2 The Hardware 23 2.2.1 Proceasor 2.3 2.2.2 Memory 2.3 13 Using BBC BASIC 23 2.3.1 Extensions to BBC BASIC 23 2.3.2 Enhancement to the ON statement 13 23J The LIST IF construction. 13 23.4 The TIMES pseudo-variable 23 23.3 The EXT > statement 23 23.6 The COLOR siatemem 23 2.3.7 Extensions to the assembler 2.6 23.8 Improved LISTO formatting 2.6 23.9 Other minor changes 2.6 23.10 Running existing BASIC programs in 23.11 The @HELP procedure in 23.12 BASICprograms that call machine code in 23.13 Calling operating system functions in 23.14 Extensions to CALL and USR 2.8 23.15 Calling user machine code programs 2.9 2.4 Creating BASIC Programs 2.11 2.4.1 TWIN 2.11 2.4.2 Code compression 2.14 2.4.3 Module Support 2.16 2.3 Using assembly language 2.18 2.3.1 Programmer's modelof the 6SSC816 2.19 23.2 Regi.stcrdescriptions 120 23.3 6SSC8I6 addressing modes 2.21 2.3.4 The 65SC8I6 instruction set 2.28 2.3.3 General advice for programmers 2.49 23.6Bank-independent r^e 130 23.7Position iiidepcndent code 151 2.3.8 Jumping to OS entry points 134 2.6 Creating Assembler Programs 238 2.6.1 Creating AssemblerSource Files 238 2.6.2 Creating AssemblerObject files 159 2.6.3 Creating an Executable Module Image. 2.61 Commumcator Software Toots 2.6.4Summaiy 2.63 2.7 CodingConveiuions and Library Support 2.64 2.7.1 BASIC 2JM ' 1 2.7.2 Assembler 2.66 2.7 J KILL conventions 2.67 TWIN 3.1 3.1 Introduction 3.1 3.1.1 Facilities 3.1 3.1.2 How this chapteris ansnged 3.2 3.1J Conventions usedin this chapter 3.2 3.1.4 StarUng TWIN 3.4 3.1.5The screen layout 3.4 3.1.6 The keyboard 3.9 3.1.7LeavingTWIN 3.10 3.2 Working withTWIN 3.10 3.2.1 Types of file 3.10 3.2.2 Date stampingTWIN documents 3.11 323 TWIN and the operatingsystem 3.11 3.2.4 TWIN concurrency 3.13 33 Editing 3.14 3.3.1 Insert and overtype modes 3.14 3.33 Moving around the text 3.14 3.3.3 Changing the text 3.16 3.3.4 Clearing and restoring text 3.17 3.4 Finding and replacing text 3.17 3.4.1 Simple finding and replacing 3.18 3.4.2 Counting occurrences 3.19 3.4.3 Specifyinga target string 3.19 3.4.4 Specifying a replacementstring 332 33 Files 333 33.1 Saving and loading files 333 333 Printing files 336 33 TWIN function keys 336 3.7 Concurrency: a worked example 3.31 3.7.1 TWIN and AAsm. the ARM assembler 331 3.73 Using a task 3.33 3.8 Error messages 3.33 3.9 Tasks and events 3.34 3.10 MovingTWIN 3.34 3.11 TWIN caUed from ARM BASIC 3.35 . The External ROM ExpansionCard 4.1 4.1 Introduction 4.1 43 The External ROM Expansion Card 43 43.1 Inuoductioo 4.2 43.2 Connecting the External ROMExpansion Board 43 43.3 The Reset button 4.3 43.4 The External EPROM ZIF Sockets 4.3 43.5 The Internal RAM 4.4 43 The System Utilities 4.4 43.1 Introduction 4.4 ( y 433 Invoking the System Utilities 4.4 4.3.3The CBFREE UUIity 4.5 43A The HANDLES UUUty 4.5 Comauudcator Software Toots 4.3J The MAP UUIity 43 4.3.6 The MODULES UUIily 4.7 4.3.7 The IRQLIST Ulilily 4.9 4.4 The Trace Utility 4.10 4.4.1 Intiodticliai 4.10 4.4.2 Use of breakpoints and leporting 4.10 4.43 Looking at memory 4.14 4.4.4 Patching memory and registers 4.15 4.43 Memory protection 4.17 4.4.6 Real-time tracing 4.18 4.4.7 Miscellaneous 4.19 , Support Utilities 5.1 S.l Introduction 5.1 5.2 UNCOMMENT 5.1 5.3 EDCONVERT 5.1 5.4 TCRUNCH 53 5.5 MAKEMOD 5.2 5.6 ALOADER 53 . BlueScreen Software 6.1 6.1 Overview 6.1 62 Specification 6.2 63.1 Screen format 63 6.2.2 Help support 6.2 6.3 User interface 6.3 6.3.1 BlueScreen 6.3 6J3 Required interfaces 63 6.3.3 Invocation interfaces 6.5 6.4 Environment 6.9 63 Structure 6.9 6.6 Data strucutres 6.10 6.6.1 Textual data structures 6.10 6.7 Procedures 6.10 6.7.1 Utill routines 6.11 6.7.2 Usage 6.22 6.7.3 Util2 routines - must be provided by user 632 6.7.4 Machine code entry points 6.23 63 Source Code Management 6.23 6.9 Error Messages 6.24 6.10 OS calls required 6.24 Device Drivers 7.1 7.1 Introduction 7.1 7.2 Device Driver Module Reason Codes 73 7.3 Device Driver Control Streams 7.3 7.4 Device Driver Filenames and Handles 7.3 7.5 Writing Device Drivers 7.4 73.1 Device Driver Reason Codes 7.4 73.2 Reuuning Status 7.4 73.3 Device Driver Macros 73 7.5.4 Implementing a Device Driver 7.11 Communicator emulation modules 8.1 8.1 Overview 8.1 8.2 Software Interface 8.2 8.3 Environment 8.2 Communicalor Software Toots 8.4 Slnictuie 8.3 8.5 Data stiuctures 8.4 8.6 Procedures 8.5 8.6.1 RCODES 83 8.6.2 EMNAME 8.5 8.6.3 EMINIT 8.5 8.6.4 EMKILL 8.5 8.6.5 EMHELP 83 8.6.6 EMCGET 8.5 8.6.7 EMCPUT 8.5 8.6.8 chcckhandle 8.5 8.6.9 EMcrflags 8.6 8.6.10 EMOPEN 8.6 8.6.11 EMLALA 8.6 8.6.12 EMCLOSE 8.6 8.6.13 gdzero 8.6 8.6.14 nullroutine 8.6 8.7 OS calb required 8.7 8.8 Communicator BBC and Teletype emulation modules 8.8 8.8.1 Overview 8.8 8.8.2 TeletypeemulationSpecification 8.8 8.8.3 BBC emulation Specification 83 8.8.4 Data structures 8.9 8.8.5 Procedures 8.9 8.9 Communicator Videotex emulation module 8.11 8.9.1 Overview 8.11 8.9.2 Videotex emulatitm Specification 8.11 8.9J Data structures 8.12 8.9.4 Procedures 8.12 8.9.5 OS calls required 8.16 8.10 COnununicator VTIOO emulation module 8.16 8.10.1 Overview 8.16 8.10.2 Specification 8.17 8.10J Dm stiuctures 8.20 8.10.4 Procedures 8.23 8.11 OS calls required 8.34 9.
Load more

Recommended publications
  • Improving the Beaglebone Board with Embedded Ubuntu, Enhanced GPMC Driver and Python for Communication and Graphical Prototypes
    Final Master Thesis Improving the BeagleBone board with embedded Ubuntu, enhanced GPMC driver and Python for communication and graphical prototypes By RUBÉN GONZÁLEZ MUÑOZ Directed by MANUEL M. DOMINGUEZ PUMAR FINAL MASTER THESIS 30 ECTS, JULY 2015, ELECTRICAL AND ELECTRONICS ENGINEERING Abstract Abstract BeagleBone is a low price, small size Linux embedded microcomputer with a full set of I/O pins and processing power for real-time applications, also expandable with cape pluggable boards. The current work has been focused on improving the performance of this board. In this case, the BeagleBone comes with a pre-installed Angstrom OS and with a cape board using a particular software “overlay” and applications. Due to a lack of support, this pre-installed OS has been replaced by Ubuntu. As a consequence, the cape software and applications need to be adapted. Another necessity that emerges from the stated changes is to improve the communications through a GPMC interface. The depicted driver has been built for the new system as well as synchronous variants, also developed and tested. Finally, a set of applications in Python using the cape functionalities has been developed. Some extra graphical features have been included as example. Contents Contents Abstract ..................................................................................................................................................................................... 5 List of figures .........................................................................................................................................................................
    [Show full text]
  • The 6502 Instruction Set
    6502asm user guide – prerelease version A PRE-RELEASE VERSION OF 6502ASM... IT MAY NOT WORK ENTIRELY CORRECTLYTHIS IS YET. If you discover errors, please report them to me! 6502asm v0.04 user guide page 1 6502asm user guide – prerelease version Introduction 6502asm is a simple assembler for 6502 code. It supports a variety of assembler commands to control output and extend the 6502 instruction set. The instruction set provided is the legal NMOS 6502 set, and the CMOS 65C02 instruction set according to the Western Design Center W65C02S datasheet (not the MOS 65CE02 variant). The NMOS “undocumented” instructions are not supported. The command syntax is: 6502asm <input file> <output file> Purpose 6502asm is part of the Amélie project. It was written in order to allow the BIOS code to be written and compiled without requiring the use of a BBC microcomputer (or emulator). While it is primarily intended for this purpose, it is flexible enough to be used for the assembly of 6502 code for other environments, such as the BBC micro (or compatible) or other 6502-based devices. 6502asm fits in with Amélie’s philosophy of “keep it simple”. 6502asm assembles in two passes, much as code is usually assembled under BBC BASIC. Currently, 6502asm does not support macros or conditional assembly, though these features are “in planning”. If you are used to Acorn systems, you may be pleased to know that 6502asm considers ‘&’ to mean “this is a hex number”, which is one of the main reasons I wrote this instead of using one of the many other 6502 assemblers available.
    [Show full text]
  • Embedded Systems: Principles and Practice
    Embedded Systems: Concepts and Practices Part 2 Christopher Alix Prairie City Computing, Inc. ECE 420 University of Illinois April 22, 2019 Outline (Part 2) ⚫ ARM and DSP Architectures ⚫ Software challenges in Embedded Systems ⚫ Key decisions in ES software development ⚫ Low-cost ES Prototyping Platforms ⚫ Trends and opportunities in the ES industry Embedded System Definition • A dedicated computer performing a specific function as a part of a larger system • High-reliability systems operating in a resource-constrained environment (typically cost, space & power) • Essential Goal: Turn hardware problems into software problems. ARM Architecture Unifying ES Development 32-bit and 32/64-bit variants Started by Acorn Computers (UK) in 1983 ARM Holdings bought by Softbank in 2016 Core licensees (~500) (Include ARM CPUs on their chips) Architectural Licenses (~15) (Design their own CPUs based on the ARM instruction set) ARM Architecture Unifying ES Development Licensees include Analog Devices, Apple, AMD, Atmel, Broadcom, Qualcomm, Cypress, Huawei, NXP, Nvidia, Renesas, Samsung, STM, TI, Altera (Intel), Xilinx. 15 billion ARM-based chips sold per year (2016) Dominant market share Smartphones (95%) Computer peripherals (65%) Hard disks and SSDs (95%) Automotive (50% overall; 85% infotainment) ARM Architecture Unifying ES Development Brought order to a chaotic industry with dozens of different proprietary processor architectures Enabled a common set of tools, techniques and technologies to be shared across the ES industry (one Linux port, one gcc/g++
    [Show full text]
  • OF the 1980S
    THAT MADE THE HOME COMPUTER REVOLUTION OF THE 1980s 23 THAT MADE THE HOME COMPUTER REVOLUTION OF THE 1980s First published in 2021 by Raspberry Pi Trading Ltd, Maurice Wilkes Building, St. John’s Innovation Park, Cowley Road, Cambridge, CB4 0DS Publishing Director Editors Russell Barnes Phil King, Simon Brew Sub Editor Design Nicola King Critical Media Illustrations CEO Sam Alder with Brian O Halloran Eben Upton ISBN 978-1-912047-90-1 The publisher, and contributors accept no responsibility in respect of any omissions or errors relating to goods, products or services referred to or advertised in this book. Except where otherwise noted, the content of this book is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported (CC BY-NC-SA 3.0). Contents Introduction. 6 Research Machines 380Z. 8 Commodore PET 2001. 18 Apple II. 36 Sinclair ZX80 and ZX81. 46 Commodore VIC-20 . 60 IBM Personal Computer (5150). 78 BBC Micro . 90 Sinclair ZX Spectrum. 114 Dragon 32. 138 Commodore 64. 150 Acorn Electron . .166 Apple Macintosh . .176 Amstrad CPC 464. 194 Sinclair QL . .210 Atari 520ST. 222 Commodore Amiga. 234 Amstrad PCW 8256. 256 Acorn Archimedes . .268 Epilogue: Whatever happened to the British PC? . .280 Acknowledgements . 281 Further reading, further viewing, and forums. 283 Index . .286 The chapters are arranged in order of each computer’s availability in the UK, as reflected by each model’s date of review in Personal Computer World magazine. Introduction The 1980s was, categorically, the best decade ever. Not just because it gave us Duran Duran and E.T., not even because of the Sony Walkman.
    [Show full text]
  • From FORTRAN to Fireworkz
    From FORTRAN to Fireworkz One programmer’s voyage through the 1980s and 1990s Stuart Swales Formerly of Acornsoft and Colton Software September 2020 Sparking an interest • I first became interested in computer systems through electronics as a teenager • Various electronics magazines sampled • In 1976 I stumbled upon “Electronics Today International (ETI)” • Subscribed to ETI for many years ETI System 68 • A modular Eurocard-based system • Supported several microprocessors, with board designs for the Motorola 6800 and SC/MP • Designed principally by John Miller-Kirkpatrick • Articles ran from April 1977 • Sadly I had insufficient cash! • “The annotated listing of the monitor PROM is available on request”. Hmm... • 20p well spent — my first exposure to software! Still interesting, though • Motorola M6800 Microcomputer System Design Data guide A snip at £2.00 from NewBear Computing Store at the NEC BASIC at 300 baud • My maths teacher at school began an Open University course that year which involved some ‘online’ computing • We had an ASR-33 teletype (with punched paper tape of course) and a phone coupler • The Open University system was a Hewlett Packard (System 10?) located in Newcastle • The HP had a BASIC interpreter, and that was well documented in a HP manual supplied with the course material • School were happy for me to use it at lunchtime Increased potential • In 1978 I’d taken on a part-time job at Tesco (other supermarkets are available) stacking shelves • Cash was accumulating quite quickly • Could I buy a system now? Er, no. • Commodore PETs and Apple IIs had come on the scene but everything still seemed way out of my league Ohio Scientific Superboard II • And one day in early 1979 I spied an advert for this system..
    [Show full text]
  • Explicit Network Scheduling
    Explicit Network Scheduling Richard John Black Churchill College University of Cambridge A dissertation submitted for the degree of Do ctor of Philosophy December Abstract This dissertation considers various problems asso ciated with the scheduling and network IO organisation found in conventional op erating systems for eective supp ort for multimedia applications which require Quality of Service A solution for these problems is prop osed in a microkernel structure The pivotal features of the prop osed design are that the pro cessing of device interrupts is p erformed by userspace pro cesses which are scheduled by the system like any other that events are used for b oth inter and intra pro cess synchronisation and the use of a sp ecially develop ed high p erformance IO buer management system An evaluation of an exp erimental implementation is included In addition to solv ing the scheduling and networking problems addressed the prototyp e is shown to outp erform the Wanda system a lo cally develop ed microkernel on the same platform This dissertation concludes that it is p ossible to construct an op erating system where the kernel provides only the fundamental job of ne grain sharing of the CPU b etween pro cesses and hence synchronisation b etween those pro cesses This enables pro cesses to p erform task sp ecic optimisations as a result system per formance is enhanced b oth with resp ect to throughput and the meeting of soft realtime guarantees To my parents John and Marcella Preface Except where otherwise stated in the text this dissertation
    [Show full text]
  • Acorn Communicator User Guide
    (c) Copyright Acorn Computers limited 1986 This apparatus is intended for use when supplied with power from the above power supply. Other usage will invalidate any approval given to this Neither the whole or any part of the information contained in, or the apparatus if, as a result, it ceases to comply with BS6301: 1982. Do not use product described in, this manual may he adapted or reproduced in any the supply in conditions of extreme heat, cold, humidity, dust or m form form . except with the prior written permission of Acorn vibration. Computers Limited (Acorn Computers). There are no user-serviceable parts inside Communicator, which should Inst ructions for installing this apparatus are given in Appendix A of this not be disassembled. Guide. For maintenancq and service on the Communicator, contact your The mains power supply supplied with the Communicator is specified to supplier. operate as follows: The Acom Communicator is made in the United Kingdom by: Input 240 Volts a.c. 50Hz at 45W Output: 21 Volts a. c. 50Hz at 1.6A. Acorn Computers Ltd The power supply should be disconnected from the mains supply when the Fulbourn Road computer is not used for long periods. Cherry Hinton IMPORTANT: The wires in the mains lead for the power supply unit are Cambridge CB1 4JN coloured in accordance with the following code: BLUE – NEUTRAL BROWN–LIVE As the colours of the wires may not correspond with the coloured markings identifying the terminals in your plug, proceed as follows when replacing the plug. The approval of this modem for connection to telephone networks is INVALIDATED if the apparatus is subject to any modification in any The wire which is coloured blue must be connected to the terminal which material way not authorised by BABT or is used with, or connected to: is marked with the letter N, or coloured black or blue (though nor necessarily the same shade of that colour).
    [Show full text]
  • 2007 No. 1 One of the Most Dispiriting Things About Being the Editor of Eureka and a Member of the Arm Club Is the Lack of Communication Between Members
    Issue 60 - 2007 No. 1 One of the most dispiriting things about being the editor of Eureka and a member of The Arm Club is the lack of communication between members. In this day and age what methods of communication do we have? In the 15th century the main communication was by voice so communication was face to face or if you were very rich, and could write, a written communication could be sent. By the time of the Victorians one could communicate by voice, letter and the new fangled telegraph using morse code. The postal service was so good you could expect three or four deliveries per day. In the early 20th century the introduction of the telephone made communication for the masses achievable. What do we have today? Well, face to face verbal communication, the post, the telephone, email, blogs, chat rooms, newsgroups etc etc. One would think that it would have become easier with all these different communication methods. However for most members of The ARM Club this appears not to be so. A computer club surely exists so that members can pass on information and swap ideas. The amount of information swapping between members using Eureka appears to be approaching absolute zero. Surely someone has some useful knowledge about software or hardware they could pass on to other members? It can be just short snippets or whole articles. It becomes harder and harder to find enough material to fill a magazine. Soon you may end up with some very thin mags. However there is a ray of hope - a member has emailed Eureka with useful information, so for the first time in three years I can start a letters page! Let us hope it won’t be another three years before I get another one.
    [Show full text]
  • FROBNICATE ISSUE 12 - Spring 1997 Page 3 EDITORS PAGE
    ESSENTIAL FOR ALL THOSE ACORN TECHIE-TYPES OUT THERE... • ACORN MACHINES • AMIGA USERS • VCR CONTROLLER • STAR TREK SPOOF & more! Spring 1997 Issue 12 £0 123> Index: Page 2 . Index. Page 3 . Editors Page. Page 4 . Review of a dozen. Page 6 . Amiga Owners. Page 10 . Who’s standard? Page 11 . Currency. Page 12 . VCR controller. Page 14 . Acorn machines. Page 19 . Millenium. Page 20 . MTerm (A) r2v2. Page 21 . Santa? (and JAVA announcement). Page 22 . Ster Trak Credits: Editor . Richard Murray. Contributors . Richard Murray, Quintin Parker, Philip R. Banks. Santa article posted by Geoff Love. Java article posted by Stuart Halliday. Graphics . Richard Murray. You may print and/or distribute this document provided it is unaltered. The editor can be contacted by FidoNet netmail as “Richard Murray” at 2:254/86.1 or ‘[email protected]’. See back page for more information. Feel free to comment or send submissions. Back issues, stylesheets, notes, logos and omitted articles are available from Encina BBS — netmail editor if you are interested. The contents of this magazine are © Richard Murray for legal reasons. Full Full credit is given to the individual authors of each article. All copyrights and/or trademarks used are acknowledged. All opinions stated are those of the article author and do not necessarily represent the opinions of Frobnicate, BudgieSoft or Richard Murray. All reasonable care is taken in the production of this magazine, but we will not be legally liable for errors, or any loss arising from those errors. As this magazine is of a technical nature, don’t do anything you are unsure of.
    [Show full text]
  • Acorn Communicator Filestore Manager's Guide
    Acorn Communicator Acorn= choice of experience': CONTENTS 1 ABOUT THIS GUIDE 1 Introduction 1 Structure 1 2 THE FILESTORE MANAGER'S ROLE 3 Discs 3 Organisation of information 3 Directories 4 Logging on 6 The FileStore manager's role 7 Security 7 Coping with problems 8 Adding users 8 Removing users 8 Managing discs 8 Managing space 9 Availability 9 Keeping records 9 Maintenance tasks 9 Indicator lamps 10 3 MANAGEMENT FACILITIES 11 Introduction 11 Your facilities 11 Selecting NETMGR 11 Selecting maintenance mode 13 3 MANAGEMENT FACILITIES: ROUTINE TASKS 15 Logging on 15 Logging off 15 Starting up 16 Shutting down 17 Formatting discs 18 WARNING: THIS APPARATUS MUST BE EARTHED Important: Ventilation The wires in the mains lead for the FileStore are coloured in accordance Do not block the ventilation slots in the case — see text for details. with the following code: © Copyright Acorn Computers Limited 1986 Green and yellow Earth Blue Neutral Neither the whole or any part of the information contained in, or the Brown Live product described in, this manual may be adapted or reproduced in any material form except with the prior written approval of Acorn Computers The moulded plug must be used with the fuse and fuse carrier firmly in Limited (Acorn Computers). place. The fuse carrier is of the same basic colour (though not necessarily The product described in this manual and products for use with it, are the same shade of that colour) as the coloured insert in the base of the subject to continuous development and improvement. All information of plug.
    [Show full text]
  • Filestore Service Manual
    FileStore Service Manual Part no. 0482,001 Issue 1 21 Sept. 1989 © Copyright Acorn Computers Limited 1989 Neither the whole nor any pan of the information contained in, or the product described in this Manual may be adapted or reproduced in any material form except with the prior written approval of Acorn Computers Limited. The products described in this Manual and products for use with it are subject to continuous development and improvement. All information of a technical nature and particulars of the products and their use (including the information and particulars in this Manual) are given by Acorn Computers Limited in good faith. However, Acorn Computers Limited cannot accept any liability for any loss or damage arising from the use. of any information or particulars in this manual, or any incorrect use of the products. All maintenance and service on the products must be carried out by Acorn Computers‘ authorised dealers or Approved Service Centres. Acorn Computers Limited can accept no liability whatsoever for any loss or damage caused by service, maintenance or repair by unauthorised personnel. All correspondence should be addressed to: Customer Service Acorn Computers Limited Fulbourn Road Cherry Hinton Cambridge CB1 4JN Information can also be obtained from the Acorn Support Information Database (SID). This is an on-line viewdata system available to registered SID users. Initially, access SID on Cambridge (0223) 243642: this will allow you to inspect the system and use a response frame for registration. ACORN, ECONET and FILESTORE are trademarks of Acorn Computers Limited. Within this publication the term ‗BBC‘ is used as an abbreviation for ‗British Broadcasting Corporation‘.
    [Show full text]
  • Benchmarking Arm-Based Application
    BENCHMARKING ARM-BASED APPLICATION INTEGRATED SYSTEMS By SETH WILLIAMS Bachelor Science in Electrical Engineering Oklahoma State University Stillwater, Oklahoma 2011 Submitted to the Faculty of the Graduate College of the Oklahoma State University in partial fulfillment of the requirements for the Degree of MASTER OF SCIENCE IN ELECTRICAL ENGINEERING December, 2011 BENCHMARKING ARM-BASED APPLICATION INTEGRATED SYSTEMS Thesis Approved: Dr. James Stine Thesis Adviser Dr. Sohum Sohoni Dr. Weihua Sheng Dr. Sheryl Tucker Dean of the Graduate College ii TABLE OF CONTENTS Chapter Page TABLE OF CONTENTS .................................................................................................. III LIST OF TABLES ............................................................................................................. V LIST OF FIGURES .......................................................................................................... VI I. INTRODUCTION ........................................................................................................... 1 Objectives .................................................................................................................... 2 Contributions ............................................................................................................... 3 Summary ...................................................................................................................... 4 II. BACKGROUND ...........................................................................................................
    [Show full text]