DOCSLIB.ORG

~ ARTISAN® with Experienced Engineers and Technicians on Staff

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Full-service, independent repair center -~ ARTISAN® with experienced engineers and technicians on staff. TECHNOLOGY GROUP ~I We buy your excess, underutilized, and idle equipment along with credit for buybacks and trade-ins. Custom engineering Your definitive source so your equipment works exactly as you specify. for quality pre-owned • Critical and expedited services • Leasing / Rentals/ Demos equipment. • In stock/ Ready-to-ship • !TAR-certified secure asset solutions Expert team I Trust guarantee I 100% satisfaction Artisan Technology Group (217) 352-9330 | [email protected] | artisantg.com All trademarks, brand names, and brands appearing herein are the property o f their respective owners. Find the Measurement Computing / CEC PC-488 at our website: Click HERE Program and documentation copyrighted 1986, 1998, 2003 by Capital Equipment Corporation (CEC). The software interpreter contained in EPROM/ROM is copyrighted and all rights are reserved by Capital Equipment Corporation. Copying or duplicating this product is a violation of law. Application software libraries provided on disk are copyrighted by Capital Equipment Corporation. The purchaser is granted the right to include portions of this software in products which use one of CEC's IEEE-488 interface boards (including those sold through resellers such as Keithley Instruments, etc.). The software may not be distributed other than for the application just mentioned. Purchasers of this product may copy and use the programming examples contained in this book. No other parts of this book may be reproduced or transmitted in any form or by any means, electronic, optical, or mechanical, including photocopying and recording, or by any information storage and retrieval system, without permission in writing from Capital Equipment Corporation. For CEC contact information, please go to http://www.cec488.com on the World Wide Web Part number 370966A-01 November 2003 Warranty and other information All products are warranted against defective materials and workmanship for a period of one year from the date of delivery to the original purchaser. Any product that is found to be defective within the warranty period will, at the option of the manufacturer, be repaired or replaced. This warranty does not apply to products damaged by improper use. CEC and CEC resellers assume no liability for damages consequent to the use of this product. This product is not designed for use in life support applications. Information furnished by the manfacturer is believed to be accurate and reliable. However, CEC and CEC resellers assume no responsibility for the use of such information nor for any infringements of patents or other rights of third parties that may result from its use. No license is granted by implication or otherwise under any patent rights of Keithley Instruments or CEC. Table of Contents Introduction and Installation 1-1 Step 1: Install the Software............................................................... 1-3 Step 2: Install the Hardware ............................................................. 1-5 Step 3: Test the Interface.................................................................. 1-6 Step 4: Applications ......................................................................... 1-8 IEEE-488 Tutorial 2-1 GPIB Concepts ................................................................................. 2-2 About the IEEE-488 Standard.......................................................... 2-4 GPIB Device Addresses ................................................................... 2-5 Controllers, Listeners and Talkers.................................................... 2-6 Data Transfers .................................................................................. 2-7 GPIB Commands.............................................................................. 2-8 Programming IEEE-488 Interfaces 3-1 Beginning your program................................................................... 3-2 Initializing the GPIB......................................................................... 3-5 Sending Data to a Device ................................................................. 3-6 GPIB Addresses - Primary and Secondary....................................... 3-7 Reading Data from a Device ............................................................ 3-8 Checking the Device Status - Service Request................................. 3-13 Testing for the Presence of a Device................................................ 3-16 Testing for the Presence of the GPIB Board .................................... 3-17 Checking Hardware Features of the GPIB Board ............................ 3-18 Low-level GPIB Control using Transmit ......................................... 3-20 Sending a Device Clear Command................................................... 3-32 Sending a Device Trigger Command ............................................... 3-33 The Receive Routine ........................................................................ 3-34 Binary Data Transfers....................................................................... 3-36 Data Formats .................................................................................... 3-39 High Speed Data Transfers............................................................... 3-40 Configuring Board Parameters ......................................................... 3-42 Configuration Files........................................................................... 3-47 Advanced Programming 4-1 The Computer as a GPIB Device ..................................................... 4-2 Passing Control................................................................................. 4-18 Interrupt Processing.......................................................................... 4-19 Using Multiple Boards ..................................................................... 4-24 Programming Examples 5-1 BASICA/GWBASIC Examples ....................................................... 5-3 Turbo Pascal Examples .................................................................... 5-8 C Examples....................................................................................... 5-12 Technical Reference 6-1 Introduction ...................................................................................... 6-2 Electrical Specifications ................................................................... 6-4 Handshake Timing Sequence ........................................................... 6-5 Mechanical Specifications................................................................ 6-7 Bus Line Definitions......................................................................... 6-8 Cabling Information ......................................................................... 6-9 BASICA and GWBASIC Language Interface A-1 IEEE-488 Subroutine calls ............................................................... A-2 Examples .......................................................................................... A-8 QuickBASIC, QBASIC, and Visual BASIC Language Interface B-1 IEEE-488 Subroutine calls ............................................................... B-3 Using Tarray and Rarray with strings in DOS QuickBASIC........... B-9 Examples - QuickBASIC or QBASIC.............................................. B-10 Examples - Visual BASIC................................................................ B-11 Turbo Pascal and Delphi Language Interface C-1 IEEE-488 Subroutine calls ............................................................... C-2 Examples .......................................................................................... C-7 C and C++ Language Interface D-1 IEEE-488 Subroutine calls ............................................................... D-3 Examples .......................................................................................... D-8 FORTRAN Language Interface E-1 IEEE-488 Subroutine calls ............................................................... E-3 Examples .......................................................................................... E-9 Assembler and other language interfacing F-1 IEEE-488 Subroutine calls ............................................................... F-2 Examples .......................................................................................... F-10 OS/2 and IEEE-488 G-1 Troubleshooting I-1 Checklist for Solving 488 Programming Problems .......................... I-2 Hardware Configuration J-1 PC488 ............................................................................................... J-2 PC488 (revision C and earlier) ......................................................... J-6 488EX (16-bit ISA bus card)........................................................... J-11 PCI488 (PCI bus board) .................................................................. J-14 PS488 (Microchannel, PS/2 board) ................................................. J-15 Differences from earlier versions K-1 ASCII character table & GPIB codes L-1 Using PRINT and INPUT for GPIB control M-1 HP-style universal language driver O-1 Using the CECHP driver .................................................................. O-2 Converting old HP computer programs to use CECHP.................... O-3 Commands........................................................................................ O-5 Examples .........................................................................................
Recommended publications
  • A Beginner's Guide to Freebasic

    A Beginner's Guide to Freebasic

    A Beginner’s Guide to FreeBasic Richard D. Clark Ebben Feagan A Clark Productions / HMCsoft Book Copyright (c) Ebben Feagan and Richard Clark. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". The source code was compiled under version .17b of the FreeBasic compiler and tested under Windows 2000 Professional and Ubuntu Linux 6.06. Later compiler versions may require changes to the source code to compile successfully and results may differ under different operating systems. All source code is released under version 2 of the Gnu Public License (http://www.gnu.org/copyleft/gpl.html). The source code is provided AS IS, WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Microsoft Windows®, Visual Basic® and QuickBasic® are registered trademarks and are copyright © Microsoft Corporation. Ubuntu is a registered trademark of Canonical Limited. 2 To all the members of the FreeBasic community, especially the developers. 3 Acknowledgments Writing a book is difficult business, especially a book on programming. It is impossible to know how to do everything in a particular language, and everyone learns something from the programming community. I have learned a multitude of things from the FreeBasic community and I want to send my thanks to all of those who have taken the time to post answers and examples to questions.
  • Powerbasic Console Compiler 603

    Powerbasic Console Compiler 603

    1 / 2 PowerBasic Console Compiler 603 Older DOS tools may still be fixed and/or enhanced, but newer command line tools, if any, will ... BAS source code recompilation requires PowerBASIC 3.1 DOS compiler, while .MOD source ... COM 27 603 29.09.03 23:15 ; 9.6s -- no bug LIST.. PowerBASIC Console Compiler for Windows. Create Windows applications with a text mode user interface. Published by PowerBASIC. Distributed by .... Код: Выделить всё: #compile exe ... http://rl-team.net/1146574146-powerbasic-for-windows-v-1003-powerbasic-console-compiler-v-603.html.. This collection includes 603 Hello World programs in as many more-or-less well ... Hello World in Powerbasic Console Compiler FUNCTION PBMAIN () AS .... 16 QuickBASIC/PowerBASIC Console I/O .. ... Register Port A Port B Port C Port D Port E Port F IOConf Address 0x600 0x601 0x602 0x603 0x604 0x605 0x606 ... Similar functions (and header files) are available for other C compilers and .... 48. asm11_77.zip, A DOS based command-line MC68HC11 cross-assembler ... 139. compas3e.zip, COMPAS v3.0 - Compiler from Pascal for educational ... 264. fce4pb24.zip, FTP Client Engine v2.4 for Power Basic, 219742, 2004-06-10 10:11:19 ... 603. reloc100.zip, Relocation Handler v1.00 by Piotr Warezak, 10734 .... PowerBASIC Console Compiler v6.0. 2 / 3415. Table of contents ... Error 603 - Incompatible with a Dual/IDispatch interface ............................ 214. Error 605 .... PowerBasic Console Compiler 6.03link: https://cinurl.com/1gotz8. 603-260-8480 Software provider to use compile and work where and when? ... Get wired for power. Basic large family enjoy fun nights like that. ... Report diagnosis code as an application from console without writing any custom duty or ...
  • Turbo Chameleon 64 Draft Version! (BETA-9)

    Turbo Chameleon 64 Draft Version! (BETA-9)

    Turbo Chameleon 64 VGA, turbo, freezer and memory expansion for the Commodore-64 The Programmers Manual Peter Wendrich [email protected] February 11, 2014 Draft version! (BETA-9) 1 Contents 1 Introducing the Chameleon core 5 1.1 Turbo Chameleon Cartridge for the C64 . .5 1.2 Standalone Mode . .5 1.3 Docking Station . .5 2 Configuration Mode 5 2.1 Detecting a Chameleon . .5 2.2 Activating Configuration Mode . .6 2.3 Reconfigure the FPGA core . .6 2.4 Force menu mode . .6 2.5 Force reset from software . .6 3 Core version information 6 3.1 Version Registers . .7 4 Memory 7 4.1 Allocated memory ranges . .7 4.1.1 32 MByte Layout . .7 4.2 MMU Registers . .8 4.3 Memory Overlays (6510 CPU) . 10 5 Buttons 10 5.1 Buttons Configuration Register . 11 5.2 Last Button Pressed . 11 6 VGA Output 11 6.1 VGA Sync . 11 6.2 Frame buffers . 12 6.3 Scaling modes . 12 6.4 Scanline emulation . 12 6.5 VGA Registers . 13 6.6 Palette Registers . 14 6.7 Fixed Palette Entries . 14 7 VGA Status Lines 14 7.1 VGA Status Configuration Register . 15 8 Cartridge Emulation 16 8.1 Freezer Logic . 16 8.2 Clock port . 16 8.3 Simple ROM cartridges . 16 8.4 MMC64 . 17 8.4.1 MMC64 additional SPI devices . 17 8.5 RAM expansions . 17 8.5.1 REU (Ram Expansion Unit) 1700, 1750, 1764 . 18 8.5.2 REU Emulated Quirks . 18 8.5.3 REU Registers . 19 8.5.4 GeoRAM registers .
  • Direct Memory Access

    Direct Memory Access

    International Journal of Research in Science And Technology http://www.ijrst.com (IJRST) 2014, Vol. No. 4, Issue No. III, Jul-Sep ISSN: 2249-0604 DIRECT MEMORY ACCESS LokeshMadan1, KislayAnand2and Bharat Bhushan3 1Department of Computer Science, Dronacharya College of Engineering, Gurgaon, India 2Department of Computer Science, Dronacharya College of Engineering, Gurgaon, India 3Department of Computer Science, Dronacharya College of Engineering, Gurgaon, India ABSTRACT Direct Memory Access (DMA) is a feature in all modern computers that allow devices to be able to move large blocks of data without any interaction with the processor. This can be useful, as you may have already seen from the floppy programming chapter. While the device transfers the block of data, the processor is free to continue running the software without worry about the data being transferred into memory, or to another device. The basic idea is that we can schedule the DMA device to perform the task on its own. Different buses and architecture designs have different methods of performing direct memory access. KEYWORDS: Processor register,cyclestealing,busmastering,countregisters,interleaved,c ache invalidation, schematics, gigabit Ethernet. INTRODUCTION A DMA controller can generate memory addresses and initiate memory read or write cycles. It contains several processor registers that can be written and read by the CPU. These include a memory address register, a byte count register, and one or more control registers. The control registers specify the I/O port to use, the direction of the transfer (reading from the I/O device or writing to the I/O device), the transfer unit (byte at a time or word at a time), and the number of bytes to transfer in one burst.
  • PDQ Manual.Pdf

    PDQ Manual.Pdf

    CRESCENT SOFTWARE, INC. P.D.Q. A New Concept in High-Level Programming Languages Version 3.13 Entire contents Copyright © 1888-1983 by Ethan Winer and Crescent Software. P.D.Q. was conceived and written by Ethan Winer, with substantial contributions [that is, the really hard parts) by Robert L. Hummel. The example programs were written by Ethan Winer, Don Malin, and Nash Bly, with additional contributions by Crescent and Full Moon customers. The floating point math package was written by Paul Passarelli. This manual was written by Ethan Winer. The section that describes how to use P.O.Q. with assembly language was written by Hardin Brothers. Full Moon Software 34 Cedar Vale Drive New Milford, CT 06776 Sales: 860-350-6120 Support: 860-350-8188 (voice); 860-350-6130 [fax) Sixth printing. LICENSE AGREEMENT Crescent Software grants a license to use the enclosed software and printed documentation to the original purchaser. Copies may be made for back-up purposes only. Copies made for any other purpose are expressly prohibited, and adherence to this requirement is the sole responsibility of the purchaser. However, the purchaser does retain the right to sell or distribute programs that contain P.D.Q. routines, so long as the primary purpose of the included routines is to augment the software being sold or distributed. Source code and libraries for any component of the P.D.Q. program may not be distributed under any circumstances. This license may be transferred to a third party only if all existing copies of the software and documentation are also transferred.
  • Tcss 422: Operating Systems

    Tcss 422: Operating Systems

    TCSS 422 A – Fall 2018 12/6/2018 School of Engineering and Technology, TCSS 422: OPERATING SYSTEMS Beyond Physical Memory, I/O Devices Wes J. Lloyd School of Engineering and Technology, University of Washington - Tacoma TCSS422: Operating Systems [Fall 2018] December 5, 2018 School of Engineering and Technology, University of Washington - Tacoma FEEDBACK FROM 12/3 Program 3 Write to a proc file? Once we have a reference to a process, we then traverse pages on that process? TCSS422: Operating Systems [Fall 2018] December 5, 2018 L19.2 School of Engineering and Technology, University of Washington - Tacoma FEEDBACK - 2 Which I/O Devices work better with interrupts (other than keyboard)? Interrupt driven I/O - - is off-loaded from the CPU . Via Directory Memory Access (DMA) controller . CPU non involved in the data transfer . Interrupts enable a context-switch to notify data is available . Examples: ISA, PCI bus Polled I/O is - - programmed I/O Data transfers fully occupy CPU for entire data transfer CPU unavailable for other work Examples: ATA (parallel ports), legacy serial/parallel ports, PS/2 keyboard/mouse, MIDI, joysticks TCSS422: Operating Systems [Fall 2018] December 5, 2018 L19.3 School of Engineering and Technology, University of Washington - Tacoma Slides by Wes J. Lloyd L19.1 TCSS 422 A – Fall 2018 12/6/2018 School of Engineering and Technology, FEEDBACK - 3 Does the mouse use interrupts, polling, or a hybrid of both? . Interrupts . Where is the polling (BUSY) process? (see top –d .1) TCSS422: Operating Systems [Fall 2018] December 5, 2018 L19.4 School of Engineering and Technology, University of Washington - Tacoma CLOUD AND DISTRIBUTED SYSTEMS RESEARCH L19.5 CLOUD AND DISTRIBUTED SYSTEMS LAB WES LLOYD, [email protected], HTTP://FACULTY.WASHINGTON.EDU/WLLOYD Serverless Computing (FaaS): How should cloud native applications be composed from microservices to optimize performance and cost? Code structure directly influences hosting costs.
  • Setting up MPU-401 and Compatible Cards on Your PC

    Setting up MPU-401 and Compatible Cards on Your PC

    ® Supplemental RAP-10 ®ÂØÒňΠRoland Audio Producer Notes May 21, 1996 Installing the RAP-10 in Windows 95 These notes are designed to help you install the Roland Audio Production Card (RAP-10) and configure it for use in Windows 95. This process will consist of the following four steps: I. First, we will look at computers and peripherals and how they work together. See “Typical Hardware Setup”. II. Second, we will prepare the RAP-10 for installation. See “Changing Hardware Settings”. III. Third, we will install the Windows software. See “Installing the Roland Audio Tools Software”. IV. Finally, we will test the RAP-10 to make sure it has been installed properly. See “Testing the RAP-10 Card”. If you were previously using the RAP-10 successfully under Windows 3.1 in the same computer, you can skip the first two steps and go directly to Section III. I. Typical Hardware Setup Interrupts and Addresses IBM-compatible computers can be expanded to accept many different devices such as a mouse, modem, printer, sound card, or MIDI card. Your computer uses interrupts (also called IRQs) and port addresses (or I/O addresses) to distinguish between these different devices. Since this guide is not intended to explain the concepts of IBM computers in detail, we will not jump into the particular definitions of IRQs and addresses. Just remember that the IRQ and port address numbers must be unique for EVERY device in your computer. DMA Channels The RAP-10 card also uses two DMA channels (Direct Memory Access) for the recording and playback of digital audio.
  • Computer Service Technician- CST Competency Requirements

    Computer Service Technician- CST Competency Requirements

    Computer Service Technician- CST Competency Requirements This Competency listing serves to identify the major knowledge, skills, and training areas which the Computer Service Technician needs in order to perform the job of servicing the hardware and the systems software for personal computers (PCs). The present CST COMPETENCIES only address operating systems for Windows current version, plus three older. Included also are general common Linux and Apple competency information, as proprietary service contracts still keep most details specific to in-house service. The Competency is written so that it can be used as a course syllabus, or the study directed towards the education of individuals, who are expected to have basic computer hardware electronics knowledge and skills. Computer Service Technicians must be knowledgeable in the following technical areas: 1.0 SAFETY PROCEDURES / HANDLING / ENVIRONMENTAL AWARENESS 1.1 Explain the need for physical safety: 1.1.1 Lifting hardware 1.1.2 Electrical shock hazard 1.1.3 Fire hazard 1.1.4 Chemical hazard 1.2 Explain the purpose for Material Safety Data Sheets (MSDS) 1.3 Summarize work area safety and efficiency 1.4 Define first aid procedures 1.5 Describe potential hazards in both in-shop and in-home environments 1.6 Describe proper recycling and disposal procedures 2.0 COMPUTER ASSEMBLY AND DISASSEMBLY 2.1 List the tools required for removal and installation of all computer system components 2.2 Describe the proper removal and installation of a CPU 2.2.1 Describe proper use of Electrostatic Discharge
  • 2D-Spieleprogrammierung in Freebasic

    2D-Spieleprogrammierung in Freebasic

    Dieser Abschnitt behandelt QuickBASIC und dessen abgespeckte Version QBASIC gleichermaßen; der Einfachheit halber wird nur von QuickBASIC gesprochen. Wer noch nie mit QuickBASIC in Berührung gekommen ist, kann den Abschnitt getrost überspringen – er ist eher für Programmierer interessant, die von QuickBASIC zu FreeBASIC wechseln wollen. Trotz hoher Kompatibilität zu QuickBASIC gibt es eine Reihe von Unterschieden zwischen beiden BASIC-Dialekten. Einige davon beruhen auf der einfachen Tatsache, dass QuickBASIC für MS-DOS entwickelt wurde und einige Elemente wie beispielsweise direkte Hardware-Zugriffe unter echten Multitaskingsystemen wie höhere Windows- Systeme oder Linux nicht oder nur eingeschränkt laufen. Des Weiteren legt FreeBASIC größeren Wert auf eine ordnungsgemäße Variablendeklaration, womit Programmierfehler leichter vermieden werden können. Hinweis: Mit der Compiler-Option -lang qb kann eine größere Kompatibilität zu QuickBASIC erzeugt werden. Verwenden Sie diese Option, um alte Programme zum Laufen zu bringen. Mehr dazu erfahren Sie im Kapitel ??, S. ??. • Nicht explizit deklarierte Variablen (DEF###) In FreeBASIC müssen alle Variablen und Arrays explizit (z. B. durch DIM) deklariert werden. Die Verwendung von DEFINT usw. ist nicht mehr zulässig. • OPTION BASE Die Einstellung der unteren Array-Grenze mittels OPTION BASE ist nicht mehr zulässig. Sofern die untere Grenze eines Arrays nicht explizit angegeben wird, verwendet FreeBASIC den Wert 0. • Datentyp INTEGER QuickBASIC verwendet 16 Bit für die Speicherung eines Integers. In FreeBASIC sind es, je nach Compilerversion, 32 bzw. 64 Bit. Verwenden Sie den Datentyp SHORT, wenn Sie eine 16-bit-Variable verwenden wollen. • Funktionsaufruf Alle Funktionen und Prozeduren, die aufgerufen werden, bevor sie definiert wurden, müssen mit DECLARE deklariert werden. Der Befehl CALL wird in FreeBASIC nicht mehr unterstützt.
  • Freebasic-Einsteigerhandbuch

    Freebasic-Einsteigerhandbuch

    FreeBASIC-Einsteigerhandbuch Grundlagen der Programmierung in FreeBASIC von S. Markthaler Stand: 11. Mai 2015 Einleitung 1. Über das Buch Dieses Buch ist für Programmieranfänger gedacht, die sich mit der Sprache FreeBASIC beschäftigen wollen. Es setzt keine Vorkenntnisse über die Computerprogrammierung voraus. Sie sollten jedoch wissen, wie man einen Computer bedient, Programme installiert und startet, Dateien speichert usw. Wenn Sie bereits mit Q(uick)BASIC gearbeitet haben, finden Sie in Kapitel 1.3 eine Zusammenstellung der Unterschiede zwischen beiden Sprachen. Sie erfahren dort auch, wie Sie Q(uick)BASIC-Programme für FreeBASIC lauffähig machen können. Wenn Sie noch über keine Programmiererfahrung verfügen, empfiehlt es sich, die Kapitel des Buches in der vorgegebenen Reihenfolge durchzuarbeiten. Wenn Ihnen einige Konzepte bereits bekannt sind, können Sie auch direkt zu den Kapiteln springen, die Sie interessieren. 2. In diesem Buch verwendete Konventionen In diesem Buch tauchen verschiedene Elemente wie Variablen, Schlüsselwörter und besondere Textabschnitte auf. Damit Sie sich beim Lesen schnell zurechtfinden, werden diese Elemente kurz vorgestellt. Befehle und Variablen, die im laufenden Text auftauchen, werden in nichtproportionaler Schrift dargestellt. Schlüsselwörter wie PRINT werden in Fettdruck geschrieben, während für andere Elemente wie variablenname die normale Schriftstärke eingesetzt wird. Quelltexte werden vollständig in nichtproportionaler Schrift gesetzt und mit einem Begrenzungsrahmen dargestellt. Auch hier werden Schlüsselwörter fett gedruckt. Der Dateiname des Programms wird oberhalb des Quelltextes angezeigt. Quelltext 1.1: Hallo Welt ’ Kommentar: Ein gewoehnliches Hallo-Welt-Programm CLS PRINT "Hallo FreeBASIC-Welt!" SLEEP 5 END ii Einleitung Es empfiehlt sich, die Programme abzutippen und zu testen. Die meisten Programme sind sehr kurz und können schnell abgetippt werden – auf der anderen Seite werden Sie Codebeispiele, die Sie selbst getippt haben, leichter behalten.
  • Download, Including1 17N REU, Ramlink Partition, Jimymon-64 (ML Monitor)

    Download, Including1 17N REU, Ramlink Partition, Jimymon-64 (ML Monitor)

    C 0 T E T S ISSUE Published June 1996 COMMODORE WORLD 6 Wheels-Laying More Than A Patch THE NEWS MAGAZINE FOR COMMODORE 64 » 1'■ I 1J',[ K1. Bruce Thonuu 14 GOFA-A Modulap- Pcogpamming System Fob The Coeimodore 64 http://wviw.cmiweb.am/cwhtme.hlml George Flanagan General Manager Chinks ft Christiansen ♦ Editor Review; Doug Cot Ion ♦ 24 Software: Centipede 126 E>r Gaelwe R. Gasson Advegtisinq Sales A Look ai ihe Newesi Commodore I2S BBS Program Charles A. Christiansen (413) 525-0023 ♦ Graphic Acts Doug Cotton .UMN! '♦ 26 Jusr Fob Starters by Jason Compton Electronic Pre-Press & Pointing Maiuir/Holden Helpful Hints for Handling Disk Drives ♦ 30 Graphic Interpretation by Bruce Thomas Cover Design by Doug Cotton GEOS: For ti Good lime... 32 Carrier Detect by Gaelyne B. Gasson Tclecommunicationi News & Updates 36 S16 Beat by Mark Fellows Things to Look Out For When Program/Hint- the 65X16 Commodore1" and [he respective Commodore producl names are trademarks or registered trademarks of Commodore, a 38 Over The Edge by Jeffrey L. Jones division of Tulip Compulers. Commodore World is in no way aftiliated wilrtthe owner n! ".he Commodore logo ana technology. Commodore Programming in a SuperCPU World Commodore Worla (ISSN 1078-2515) is published 8 limos annually by Creative Micro Designs. Inc.. 15 Benton Drive, Easl Longrneadow MA 01028-0646. Secono-Class Postage Paid at EasL Longmeaflow MA. (USPS «)n-801| Annual subscnpiion rale is USS29.95 fci U.S. addresses. USS35.95(orC3nada0'Maiico.USSJS.95!orallECCounlnB5. Department paymanlsmusl be provided in U S. Dollars. Mail subscriptions 2 From the Editor to CW Subscriptions, do Crestiva Micro Designs.
  • Ada User Journal

    Ada User Journal

    ADA Volume 27 USER Number 4 December 2006 JOURNAL Contents Page Editorial Policy for Ada User Journal 194 Editorial 195 News 197 Conference Calendar 232 Forthcoming Events 239 Articles J-C Mahieux, B Maudry, A Foster “Using CORBA to Bring New Life to Legacy Ada Software: an Experience Report” 244 J Klein, D Sotirovski “The Publisher Framework” 248 Ada-Europe 2006 Sponsors 256 Ada-Europe Associate Members (National Ada Organizations) Inside Back Cover Ada User Journal Volume 27, Number 4, December 2006 194 Editorial Policy for Ada User Journal Publication Original Papers Commentaries Ada User Journal – The Journal for the Manuscripts should be submitted in We publish commentaries on Ada and international Ada Community – is accordance with the submission software engineering topics. These published by Ada-Europe. It appears guidelines (below). may represent the views either of four times a year, on the last days of individuals or of organisations. Such March, June, September and All original technical contributions are articles can be of any length – December. Copy date is the first of the submitted to refereeing by at least two inclusion is at the discretion of the month of publication. people. Names of referees will be kept Editor. confidential, but their comments will Opinions expressed within the Ada Aims be relayed to the authors at the discretion of the Editor. User Journal do not necessarily Ada User Journal aims to inform represent the views of the Editor, Ada- readers of developments in the Ada The first named author will receive a Europe or its directors. programming language and its use, complimentary copy of the issue of the general Ada-related software Journal in which their paper appears.