DOCSLIB.ORG

Axesbrain Motion System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Axesbrain Motion System Volume 1 AxesBrain Motion System Motion system A x e s B r a i n Motion system AB&T Tecnologie Informatiche Via dell’About, 2/A • 10015 Ivrea Fax +39 0125 234397 www.bausano.net [email protected] Legal notice The information in this document, including URLs and other references to the Internet website, can be changed without prior notification. Unless otherwise indicated, references to companies, organizations, products, persons and events are completely fictitious and unrelated to real companies, organizations, products, persons and events. AB&T Tecnologie Informatiche is entitled to register, license, apply for copyright or trade marks and affirm its intellectual property rights with regard to all the topics dealt with in this document. Without limiting entitlements under copyright, no part of this document can be reproduced, modified, or transmitted in any form and using any media (electronic, mechanical, photocopy, recording, or other) without the prior express authorization of AB&T Tecnologie Informatiche . Except in the case of written agreements with AB&T Tecnologie Informatiche the fact of being supplied with this document shall not authorize any party to register, grant licenses, apply for copyright or trade marks or affirm its intellectual property rights with respect to the subjects dealt with herein. AxesBrain , VisAlgo , ScadaMERCURIO are registered trade marks AxesBrain, VisAlgo are covered by copyright ActiveX, DirectX, JScript, Microsoft, Microsoft Press, MS-DOS, Visual Basic, Visual C++, Win32, Win32s, Windows, WDM, Windows NT, Windows 2000 and Windows Me are products or trade marks registered by Microsoft Corporation in the U.S.A. and/or in other Countries. The names of companies and products quoted in this document may be trade marks that have been duly registered by their owners. Contents Introduction i Synchronization instructions 7 Indication instructions 8 CHAPTER 1–Motion system - Service instructions 9 Architecture 1 Intructions for integrtation with foreign Interface devices 2 environments 10 Services (DCOM) 3 Coordinates and anti-collision systems 4 CHAPTER 4 – CNC (AxesBrainISO)- Plant configuration 5 Architecture 1 Sampling 6 Physical axes link 2 OEM Capability 7 Work plane 3 User interface 8 Motion functions 4 Integration with vision inspection 9 G functions 5 M functions 6 CHAPTER 2–AxesBrainServer services - T functions 7 Basic system functions 1 F, S and O functions 8 Axes and spindles functions 2 Program control instructions 9 Functions for signals 3 Subsystem functions 5 CHAPTER 5 - PLC(AxesBrainAWL) - Plant indication functions 6 Architecture 1 System configuration functions 7 Types of data and addressing modes 2 Server events 8 Contact instructions 3 Access with AxesBrainBase (DLL library) 9 Timer and counter instructions 4 and AxesBrainCom (OCX library) Mathematical instructions 5 Increment and transfer instructions 6 CHATPER 3 – Automation (AxesBrainL)- Program control instructions 7 Architecture 1 Logic stack instructions 8 Language syntax 2 Boolean instructions 9 Global and local variables 3 Multitasking and anti-collision systems Mathematical logic instructions 5 Control instructions 6 Motion instrucitons 7 I/O instructions 8 CHAPTER 6 Environment APPENDIX A (AxesBrainStudio)- Virual axes Architecture 1 APPENDIX B Basic applications 2 Ganrty axes OCX applications 3 APPENDIX C HTML applications 4 Axis control with handwheel APPENDIX D Electronic cams APPENDIX E Continuous motion APPENDIX F Integration with vision inspection Introduction AxesBrain motion system The AxesBrain system was developed to offer motion control services to user applications, utilizing “DCOM” technology, thus making it possible to provide access to the services not only from the PC in question, but also from PCs networked in LANs and connected over the Internet. here are essentially two approaches to be taken in order to utilize motion control services, either using the functions directed to axes and spindle resources and I/O signals, or making use of programmed cycles. Axes path and manipulation and processing task cycles or procedures are T defined by means programming languages; in our case we have three languages at our disposal: AxesBrainL, AxesBrainISO and AxesBrainAWL, which the user can adopt depending on the type of application in question. It is also possible to integrate, as a library, functionalities or even processes for the management of work cycles that are tailored to meet specific needs, completely developed by the user. The motion control services are as follows: • Direct FUNCTIONS o commands transmitted to axes and to I/O signals o acquisition of field values, reading of axes, I/O, transducers, etc. o programming of modes for trajectories, acquisitions, etc. • processing and manipulation CYCLES programmed by means of o AxesBrainL – Proprietary language suitable for describing manipulation cycles for generic automations o AxesBrainISO – ISO standard language suitable for describing the processing cycles typically associated with milling, boring and turning operations. o AxesBrainAWL – AWL language to describe PLC cycles • Special “OEM” FUNCTIONS • processing and manipulation CYCLES with programming of special “OEM” procedures 4 AxesBrain is structured as a series of functional modules in such a way as to achieve the maximum flexibility in terms of management of devices, user interface characteristics, and performance features. AxesBrain is divided as follows: • “AxesBrainOpenEnviroment” module for driving interface devices; in addition to the management of several ranges of commercial devices, this module was developed in an open architecture system so as to allow the devices to be expanded in accordance with changing requirements of users. • “AxesBrainServer” basic module, supplier of system services in “DCOM” technology. • “AxesBrainOpenTemplate” basic classes module to allow the user to develop new performances, both in terms of functions and procedures. • “AxesBrainBase” interface module for connection with services for applications in Visual Basic or Visual C++ • “AxesBrainCom” interface module for connection with services for HTML user pages or for applications compiled in any of the various programming languages. • “AxesBrainStudio” user interface environment, this module allows the creation of highly personalized user interfaces. 5 AxesBrain architecture 64 Axes 32 Spindles 1024 Digital inputs 1024 Digital outputs 128 Analog inputs 128 Analog outputs 128 Counters Images for measurements and 128 Timers recognition 1-Carriers+IP Industrial Pack 2-USB Controller 1-PC Axis Board 1-Frame grabber PCX 200 3-Encoder 2-OEM Encoder + Analog DAC 2-Frame grabber P610 4-Analog DAC 3-OEM 1394 Axis controller 4-OEM Axis controller 5-USB SEB I/O VisAlgo OpenEnviroment access and pilot Driver AxesBrainOpenEviroment - Driving of interface devices Functions and cycles for AxesBrainOpenTemplate AxesBrainL AxesBrainISO AxesBrainAWL image data processing and Automation CNC PLC - OEM Capability analysis Remote or Programmed motion cycles Local VisAlgo Connection OEM capabilities Direct commands and Programmed cycles 1 - VisAlgoBase DLL Library Access Functions system resources and instructions access 2 – VisAlgoCom OCX Library access function functions AxesBrainServer DCOM - Handling system services Remote or Local Connection AxesBrainBase DLL Library AxesBrainCom OCX User Cycles Library Basic Applications Visual Basic User Applications OCX User HTML User Applications Applications HTML User Applications Visual C++ / Visual C# User Applications AxesBrainStudio – Applications and User Cycles Container Environment Figure 1 6 Chapter 1 Motion system The motion system is the controller of all the resources and the supervisor of the motion functionalities requested either directly or by way of processing cycles programmed utilizing the three programming languages; in addition, it can integrate, in the form of a library, functionalities and the work cycles management processes, completely developed by the Customer. During the desoign stage, particular attention was devoted to the scalability of the system in terms of devices, functions, plant and user interface. The requirements of the environment in which a handling system is installed are numerous, ranging from: • the type of motors: dc motors, stepper motors, brushless motors, linear motors, etc. • the motor control system: analog drives, digital drives, etc. • the type of electronic devices that make it possible to access the motor drives: PCAxisBoard, PCFieldBus, PCEncoderBoard, PCAnalogBoard , etc. • the type of PC bus: PCI, AT, 104, CompactPCI, etc • the type of operating system Windows 98, Windows Me, Windows 2000 The AxesBrain system is designed to introduce the maximum flexibility into the scenario described above, creating a layer denominated AxesBrainOpenEnviroment , which contains a series of modules designed to drive various commercial devices, and a basic class in order to facilitate the development and integration of new devices. This makes it possible also to separate the driver environment from the applications. 7 A basic requisite of a motion control system is that it must be able to supply its services to a plurality of users, potentially resident on remote PCs; this requirement is filled by the Distributed Component Object Module (DCOM) technology utilized in the implementation of the AxesBrainServer . Although the system provides a broad band of functionalities, it is impractical to be able to develop responses for the entire range of
Load more

Recommended publications
  • Interaction Between Web Browsers and Script Engines
    IT 12 058 Examensarbete 45 hp November 2012 Interaction between web browsers and script engines Xiaoyu Zhuang Institutionen för informationsteknologi Department of Information Technology Abstract Interaction between web browser and the script engine Xiaoyu Zhuang Teknisk- naturvetenskaplig fakultet UTH-enheten Web browser plays an important part of internet experience and JavaScript is the most popular programming language as a client side script to build an active and Besöksadress: advance end user experience. The script engine which executes JavaScript needs to Ångströmlaboratoriet Lägerhyddsvägen 1 interact with web browser to get access to its DOM elements and other host objects. Hus 4, Plan 0 Browser from host side needs to initialize the script engine and dispatch script source code to the engine side. Postadress: This thesis studies the interaction between the script engine and its host browser. Box 536 751 21 Uppsala The shell where the engine address to make calls towards outside is called hosting layer. This report mainly discussed what operations could appear in this layer and Telefon: designed testing cases to validate if the browser is robust and reliable regarding 018 – 471 30 03 hosting operations. Telefax: 018 – 471 30 00 Hemsida: http://www.teknat.uu.se/student Handledare: Elena Boris Ämnesgranskare: Justin Pearson Examinator: Lisa Kaati IT 12 058 Tryckt av: Reprocentralen ITC Contents 1. Introduction................................................................................................................................
    [Show full text]
  • Taking Advantage of the SAS System on Windows NT
    Taking advantage of the SAS System on Windows NT Mark W. Cates, SAS Institute Inc., Cary, NC ABSTRACT Unless specified, all the SAS System products and features are provided on both Windows NT Windows NT is fast becoming the universal Workstation and Windows NT Server. This desktop client operating system as well as an paper assumes the current release of Windows important file and compute server for mission NT is Version 4.0. For brevity, the abbreviation critical applications. This paper presents a NT will be used for Windows NT. discussion of the state of Windows NT and how the SAS System Release 6.12 for Windows takes advantage and integrates with the operating Windows Family - Single Executable Image system. Areas such as the user interface, OLE and Web integration are presented. Data access Windows NT is now in its full 3rd generation, and Microsoft BackOffice integration, and with the release of Windows NT Workstation hardware considerations are also presented. 4.0 and Windows NT Server 4.0. NT Workstation and NT Server share the same microkernel, and is portable to several RISC INTRODUCTION platforms, including DEC Alpha AXP, and the PowerPC Prep Platforms. The MIPS chip Microsoft Windows NT sales grew dramatically is no longer supported by Windows NT. The in 1996, as many corporations which have been majority of NT installations still run on the Intel investigating Windows NT have now begun to Pentium® and Pentium Pro® processor. The deploy Windows NT for the client desktop. SAS System Release 6.12 only supports the Intel Many of these deployments were replacing platform, and the Pentium Pro processor is ® Windows 3.1 and Windows 95 .
    [Show full text]
  • 9.4 Flight Operations Data
    REPORT DOCUMENTATION PAGE Form Approved OMB No. 0704-0188 Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. 1. AGENCY USE ONLY (Leave blank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVERED August 1995 Final Report Jan 93 - Aug 95 4. TITLE AND SUBTITLE 5. FUNDING NUMBERS Integrated Noise Model (INM) Version 5.0 User's Guide DTFA01-93-C-00078 6. AUTHOR(S) Task Orders 2 and 5 ATAC Olmstead, Bryan, Jeng, Mirsky, Rajan* VNTSC Fleming, D'Aprile, Gerbi*, Rickley*, Turner* FA565/A5012 LeTech Le, Le, Chen * subcontractors FAA Plante, Gulding (Prog. Mgr.), Vahovich, Warren 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING ORGANIZATION ATAC Corporation DOT/VNTSC LeTech, Inc. REPORT NUMBER 757 N. Mary Ave. DTS-75, Kendall Sq. 5400 Shawnee Rd #202 Sunnyvale, CA 94086 Cambridge, MA 02142 Alexandria, VA 22312 9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING/MONITORING U.S. Department of Transportation AGENCY REPORT NUMBER Federal Aviation Administration Office of Environment and Energy, AEE-120 FAA-AEE-95-01 800 Independence Ave.
    [Show full text]
  • NET Framework
    Advanced Windows Programming .NET Framework based on: A. Troelsen, Pro C# 2005 and .NET 2.0 Platform, 3rd Ed., 2005, Apress J. Richter, Applied .NET Frameworks Programming, 2002, MS Press D. Watkins et al., Programming in the .NET Environment, 2002, Addison Wesley T. Thai, H. Lam, .NET Framework Essentials, 2001, O’Reilly D. Beyer, C# COM+ Programming, M&T Books, 2001, chapter 1 Krzysztof Mossakowski Faculty of Mathematics and Information Science http://www.mini.pw.edu.pl/~mossakow Advanced Windows Programming .NET Framework - 2 Contents The most important features of .NET Assemblies Metadata Common Type System Common Intermediate Language Common Language Runtime Deploying .NET Runtime Garbage Collection Serialization Krzysztof Mossakowski Faculty of Mathematics and Information Science http://www.mini.pw.edu.pl/~mossakow Advanced Windows Programming .NET Framework - 3 .NET Benefits In comparison with previous Microsoft’s technologies: Consistent programming model – common OO programming model Simplified programming model – no error codes, GUIDs, IUnknown, etc. Run once, run always – no "DLL hell" Simplified deployment – easy to use installation projects Wide platform reach Programming language integration Simplified code reuse Automatic memory management (garbage collection) Type-safe verification Rich debugging support – CLR debugging, language independent Consistent method failure paradigm – exceptions Security – code access security Interoperability – using existing COM components, calling Win32 functions Krzysztof
    [Show full text]
  • Windows 95 & NT
    Windows 95 & NT Configuration Help By Marc Goetschalckx Version 1.48, September 19, 1999 Copyright 1995-1999 Marc Goetschalckx. All rights reserved Version 1.48, September 19, 1999 Marc Goetschalckx 4031 Bradbury Drive Marietta, GA 30062-6165 tel. (770) 565-3370 fax. (770) 578-6148 Contents Chapter 1. System Files 1 MSDOS.SYS..............................................................................................................................1 WIN.COM..................................................................................................................................2 Chapter 2. Windows Installation 5 Setup (Windows 95 only)...........................................................................................................5 Internet Services Manager (Windows NT Only)........................................................................6 Dial-Up Networking and Scripting Tool....................................................................................6 Direct Cable Connection ..........................................................................................................16 Fax............................................................................................................................................17 Using Device Drivers of Previous Versions.............................................................................18 Identifying Windows Versions.................................................................................................18 User Manager (NT Only) .........................................................................................................19
    [Show full text]
  • Microsoft Palladium
    Microsoft Palladium: A Business Overview Combining Microsoft Windows Features, Personal Computing Hardware, and Software Applications for Greater Security, Personal Privacy, and System Integrity by Amy Carroll, Mario Juarez, Julia Polk, Tony Leininger Microsoft Content Security Business Unit June 2002 Legal Notice This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred.
    [Show full text]
  • Abusing Windows Management Instrumentation (WMI) to Build a Persistent, Asyncronous, and Fileless Backdoor Matt Graeber
    Abusing Windows Management Instrumentation (WMI) to Build a Persistent, Asyncronous, and Fileless Backdoor Matt Graeber Black Hat 2015 Introduction As technology is introduced and subsequently deprecated over time in the Windows operating system, one powerful technology that has remained consistent since Windows NT 4.01 and Windows 952 is Windows Management Instrumentation (WMI). Present on all Windows operating systems, WMI is comprised of a powerful set of tools used to manage Windows systems both locally and remotely. While it has been well known and utilized heavily by system administrators since its inception, WMI was likely introduced to the mainstream security community when it was discovered that it was used maliciously as one component in the suite of exploits and implants used by Stuxnet3. Since then, WMI has been gaining popularity amongst attackers for its ability to perform system reconnaissance, AV and VM detection, code execution, lateral movement, persistence, and data theft. As attackers increasingly utilize WMI, it is important for defenders, incident responders, and forensic analysts to have knowledge of WMI and to know how they can wield it to their advantage. This whitepaper will introduce the reader to WMI, actual and proof-of-concept attacks using WMI, how WMI can be used as a rudimentary intrusion detection system (IDS), and how to perform forensics on the WMI repository file format. WMI Architecture 1 https://web.archive.org/web/20050115045451/http://www.microsoft.com/downloads/details.aspx?FamilyID=c17 4cfb1-ef67-471d-9277-4c2b1014a31e&displaylang=en 2 https://web.archive.org/web/20051106010729/http://www.microsoft.com/downloads/details.aspx?FamilyId=98A 4C5BA-337B-4E92-8C18-A63847760EA5&displaylang=en 3 http://poppopret.blogspot.com/2011/09/playing-with-mof-files-on-windows-for.html WMI is the Microsoft implementation of the Web-Based Enterprise Management (WBEM)4 and Common Information Model (CIM)5 standards published by the Distributed Management Task Force (DMTF)6.
    [Show full text]
  • Document Object Model †DOM‡ Level 1 Specification
    Document Object Model (DOM) Level 1 Specification REC-DOM-Level-1-19981001 Document Object Model (DOM) Level 1 Specification Version 1.0 W3C Recommendation 1 October, 1998 This version http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001 http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/DOM.ps http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/DOM.pdf http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/DOM.tgz http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/DOM.zip http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/DOM.txt Latest version http://www.w3.org/TR/REC-DOM-Level-1 Previous versions http://www.w3.org/TR/1998/PR-DOM-Level-1-19980818 http://www.w3.org/TR/1998/WD-DOM-19980720 http://www.w3.org/TR/1998/WD-DOM-19980416 http://www.w3.org/TR/WD-DOM-19980318 http://www.w3.org/TR/WD-DOM-971209 http://www.w3.org/TR/WD-DOM-971009 WG Chair Lauren Wood, SoftQuad, Inc. Editors Vidur Apparao, Netscape Steve Byrne, Sun Mike Champion, ArborText Scott Isaacs, Microsoft Ian Jacobs, W3C Arnaud Le Hors, W3C Gavin Nicol, Inso EPS Jonathan Robie, Texcel Research Robert Sutor, IBM Chris Wilson, Microsoft Lauren Wood, SoftQuad, Inc. Principal Contributors Vidur Apparao, Netscape Steve Byrne, Sun (until November 1997) Mike Champion, ArborText, Inc. 1 Status of this document Scott Isaacs, Microsoft (until January, 1998) Arnaud Le Hors, W3C Gavin Nicol, Inso EPS Jonathan Robie, Texcel Research Peter Sharpe, SoftQuad, Inc. Bill Smith, Sun (after November 1997) Jared Sorensen, Novell Robert Sutor, IBM Ray Whitmer, iMall Chris Wilson, Microsoft (after January, 1998) Status of this document This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation.
    [Show full text]
  • Getting Started Guide
    Getting Started Guide P/N 066450-004 EZBuilder Intermec Technologies Corporation 6001 36th Avenue West P.O. Box 4280 Everett, WA 98203-9280 U.S. technical and service support: 1-800-755-5505 U.S. media supplies ordering information: 1-800-227-9947 Canadian technical and service support: 1-800-687-7043 Canadian media supplies ordering information: 1-800-267-6936 Outside U.S. and Canada: Contact your local Intermec service supplier. The information contained herein is proprietary and is provided solely for the purpose of allowing customers to operate and/or service Intermec manufactured equipment and is not to be released, reproduced, or used for any other purpose without written permission of Intermec. Information and specifications in this manual are subject to change without notice. 2000 by Intermec Technologies Corporation All Rights Reserved The word Intermec, the Intermec logo, EZBuilder, JANUS, IRL, Trakker Antares, Adara, Duratherm, Precision Print, PrintSet, Virtual Wedge, and CrossBar are either trademarks or registered trademarks of Intermec Technologies Corporation. Microsoft, Active X, Visual C++, Windows, Win32s, the Windows logo, and Windows NT are either trademarks or registered trademarks of Microsoft Corporation. Throughout this manual, trademarked names may be used. Rather than put a trademark (™ or ®) symbol in every occurrence of a trademarked name, we state that we are using the names only in an editorial fashion, and to the benefit of the trademark owner, with no intention of infringement. EZBuilder Getting Started Guide Welcome to EZBuilder EZBuilder™ is a fast, easy-to-use development tool for creating applications that run on Trakker Antares®, T2090, and 6400 terminals.
    [Show full text]
  • DLCC Software Catalog
    Daniel's Legacy Computer Collections Software Catalog Category Platform Software Category Title Author Year Media Commercial Apple II Integrated Suite Claris AppleWorks 2.0 Claris Corporation and Apple Computer, Inc. 1987 800K Commercial Apple II Operating System Apple IIGS System 1.0.2 --> 1.1.1 Update Apple Computer, Inc. 1984 400K Commercial Apple II Operating System Apple IIGS System 1.1 Apple Computer, Inc. 1986 800K Commercial Apple II Operating System Apple IIGS System 2.0 Apple Computer, Inc. 1987 800K Commercial Apple II Operating System Apple IIGS System 3.1 Apple Computer, Inc. 1987 800K Commercial Apple II Operating System Apple IIGS System 3.2 Apple Computer, Inc. 1988 800K Commercial Apple II Operating System Apple IIGS System 4.0 Apple Computer, Inc. 1988 800K Commercial Apple II Operating System Apple IIGS System 5.0 Apple Computer, Inc. 1989 800K Commercial Apple II Operating System Apple IIGS System 5.0.2 Apple Computer, Inc. 1989 800K Commercial Apple II Reference: Programming ProDOS Basic Programming Examples Apple Computer, Inc. 1983 800K Commercial Apple II Utility: Printer ImageWriter Toolkit 1.5 Apple Computer, Inc. 1984 400K Commercial Apple II Utility: User ProDOS User's Disk Apple Computer, Inc. 1983 800K Total Apple II Titles: 12 Commercial Apple Lisa Emulator MacWorks 1.00 Apple Computer, Inc. 1984 400K Commercial Apple Lisa Office Suite Lisa 7/7 3.0 Apple Computer, Inc. 1984 400K Total Apple Lisa Titles: 2 Commercial Apple Mac OS 0-9 Audio Audioshop 1.03 Opcode Systems, Inc. 1992 800K Commercial Apple Mac OS 0-9 Audio Audioshop 2.0 Opcode Systems, Inc.
    [Show full text]
  • Microsoft Windows for MS
    Month Year Version Major Changes or Remarks Microsoft buys non-exclusive rights to market Pattersons Quick & Dirty Operating System from December 1980 QDOS Seattle Computer Products (Developed as 86-DOS) (Which is a clone of Digital Researches C P/M in virtually every respect) Microsoft buys all rights to 86-DOS from Seattle Computer Products, and the name MS-DOS is July 1981 86-DOS adopted for Microsoft's purposes and IBM PC- DOS for shipment with IBM PCs (For Computers with the Intel 8086 Processor) Digital Research release CP/M 86 for the Intel Q3 1981 CP/M 86 8086 Processer Pre-Release PC-DOS produced for IBM Personal Mid 1981 PC-DOS 1.0 Computers (IBM PC) Supported 16K of RAM, ~ Single-sided 5.25" 160Kb Floppy Disk OEM PC-DOS for IBM Corporation. (First August 1982 PC-DOS 1.1 Release Version) OEM Version for Zenith Computer Corporation.. (Also known as Z-DOS) This added support for September 1982 MS-DOS 1.25 Double-Sided 5.25" 320Kb Floppy Disks. Previously the disk had to be turned over to use the other side Digital Research release CP/M Plus for the Q4 1982 CP/M Plus Intel 8086 Processer OEM Version For Zenith - This added support for IBM's 10 MB Hard Disk, Directories and Double- March 1983 MS-DOS 2.0 Density 5.25" Floppy Disks with capacities of 360 Kb OEM PC-DOS for IBM Corporation. - Released March 1983 PC-DOS 2.0 to support the IBM XT Microsoft first announces it intention to create a GUI (Graphical User Interface) for its existing MS-DOS Operating System.
    [Show full text]
  • Novell Appnotes September 2002
    Novell, Inc. 464-000063-009 Novell AppNotes • September 2002 Novell AppNotes Order Desk PO Box 14530 Fremont, CA 94539 USA Novell AppNotes® Tel 925 463 7391 Tel 800 395 7135 Novell Research www.novell.com Call 1-800-395-7135 for subscriptions SEPTEMBER 2002 Novell’s Technical Journal for Implementing, Managing, and Programming to one Net Spotlight on Troubleshooting APPNOTES 4 Troubleshooting Novell MEDIA MAIL iChain 2.1 Authentication U.S. Postage Issues PAID Fremont, CA 29 Managing Windows 2000 Permit# 774 Group Policies with Novell Appnotes Returns ZENworks for Desktops 3 c/o Zomax, Inc. Troubleshooting Spotlight on 47 How to Use the Alarm 1640 Berryessa Rd, Suite B Management System of San Jose, CA 95133 ZENworks for Servers 3 USA DEVELOPER NOTES CHANGE SERVICE REQUESTED 59 A Methodology for Troubleshooting DirXML 79 Implementing a Utility for Searching Windows Executable Files on NetWare 87 How to Build J2EE Applications Using Novell Technologies: Part 5 SECTIONS 95 Net Management 105 Net Support 116 Code Break 127 Viewpoints AppNotes ® Novell’s Technical Journal for Implementing, Managing, and Programming to one Net September 2002 Volume 13, Number 9 Editor-in-Chief Gamal B. Herbon Novell AppNotes® (formerly Novell Application Notes, ISSN# 1077-0321, and now including the former Novell Developer Notes) is published monthly by Novell, 1800 S. Managing Editor Ken Neff Novell Place, Provo, UT 84606. The material in the AppNotes is based on actual field experience and technical research performed by Novell personnel, covering topics
    [Show full text]