DOCSLIB.ORG

Objective Is

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Objective Is Lehigh Preserve Institutional Repository Design of a microprocessor-based emulsion polymerization process control facility Dimitratos, John N. 1987 Find more at https://preserve.lib.lehigh.edu/ This document is brought to you for free and open access by Lehigh Preserve. It has been accepted for inclusion by an authorized administrator of Lehigh Preserve. For more information, please contact [email protected]. Design of a Microprocessor-based Emulsion Polymerization Process Control Facility A research report written in partial fulfillment of the requirements for the degree of Master of Science in Chemical F:ngim·ering, Lehigh University, Bethlehem, Pennsylvania by John N. Dimitratos June 1987 ,. Design of a Microprocessor-based Emulsion Polymerization .. ,_.,,-•• ·, ,, -i •:>:.·.:':' Process Control Facility ' A research report written in partial fulfillment of the requirements for the degree of Master of Science in Chemical Engineering, Lehigh University, Bethlehem, Pennsylvania by John N. Dimitratos June 1987 •1 to my father and my brother there art times when it is hard to decide what should be chosen at what price, and what endured in return for what reward. Perhaps it is still harder to stick to the decision Aristotle (384-322 B.C) Ethics, Book Ill. Abstract The explosion of microcomputer technology and the recent developments in software and hardware products introduce a new horizon of capabilities for the process control engineer. However, taking advantage of this new technology is not something easily done. H the process control engineer has to undertake such a project soon he will have to deal with the different languages the software engineer and the plant operator use. Specific knowledge and understanding of the new concepts that the evolving microprocessor technology introduces 1s required. Besides, the industrial standards, experience and operator terminology are necessary for the implementation of process control computer system application. A process control microcomputer system for emulsion polymerization reactor control was designed and implemented. The process control objective is to produce emulsion copolymers with prerequisite "tailor-made" properties, and the computer facility will be used to implement and test different control strategies for this purpose. The real-time design considerations for the necessary process control software and hardware are presented in this work. The properties of microcomputer real-time operating systems are discussed along with essential features of the programming environment, high-level languages and special A survey of the available multitasking executive application software. environments was carried out and their general hardware requirements and computing capabilities are presented. Strategies for input/output operations and interfacing techniques are summarized. A plethora of information concerning microprocessor-based interfaces and programmable controllers which became available during the implementation of the process computer control system is also included. Acknowledgments The specific application is presented , which demonstrates that employing a distributed intelligence architecture . , microprocessors can be effi ec t'1ve Iy used for There are no words to describe my debt I owe to my beloved brother for th e dcs1gn of a mic rocomputer process control system . Carefully selected process his love, support and dedication and I really now feel poor without it. He was control software verifies the I genera trend, that microcomputers can become the one who strongly encouraged me in flying overseas and start my studies va Iuable and cost effective . partners m process control app 1·1cat1ons. • here and to whom I owe so much. I would like to thank my mother for her understanding, patience and strength all these years I am abroad and for everything she did for me. Many thanks to my advisors Dr. C. Georgakis, Dr. M. El-Aasser and Dr. A. Klein, who were motivating and encouraging me all this time, providing all the technical assistance and knowledge which put "flesh and bones" in this project. I really appreciate their support and understanding in the difficult moments of my stay here. Many thanks also to Dr. Cordeiro for sharing with me his concerns and experience and to the Process Modeling and Control Center (PMC) and Emulsion Polymers Institute (EPI) for their financial support. I would like also to thank our technicians Ken Earhart, Jack Williams, Mathew Chaumers ("Scotty"), and Gil Kauffman whose advice throughout the course of this project was really valuable, and all those people in the Chemical Engineering Department, PMC and EPI offices, who had to deal with my demanding requests everyday. Finally ] owe many thanks to my special friends D. and S. Vlassopoulos, ) D. and M. Lagoudas, T. Alevizos, J. and A. Michopoulos for making my stay here an enjoyable one. To all my friends in EPI and PMC. ! \. I Table of Contents 1. Introduction 6 2. Software Considerations for ProceSB Control Applications 9 2.1 Operating Systems and Real-time Design Considerations 9 2.2 Programming Languages 17 2.3 Application Programs and Facilities 20 2.4 Expert Systems 25 3. Operating Systems for the Microcomputer-based Environment 27 3.1 The UNIX Operating System 29 3.2 UNIX Versions for the IBM PC Family 30 3.3 The UNIX-alike operating systems 32 3.4 The non-UNIX Multitasking Operating Systems 36 4. The Process Computer Interface 43 4.1 Basics of 1/0 Operation 44 4.1.1 Serial Interfacing 46 4.1.2 Analog Interfacing 49 4.1.3 Parallel Interfacing 51 4.2 Strategies for Input/Output Data Control 52 4.3 Microprocessor-based Interfaces for Process Control Applications 53 4.4 Programmable Controllers 61 5. A Distributed Intelligence Computer System for Real-time 67 Control of a Polymerization Reactor 5.1 Hardware Components 70 5.1.1 Process-related Peripheral Equipment 70 5.1.2 Interface Hardware 71 5.2 Software Support 75 5.2.1 Development of Communication and Interfacing Software 77 6. Conclusion 84 Appendix A. Software Vendors 86 Appendix B. Programmable Controllers and Manufacturers 90 Appendix C. Computer Interface Manufacturers 102 Appendix D. Standard RS-232C Pins and Signal Definitions 105 - •: ~ List of Figures List of Tables Figure 2-1: The Code Reentrancy phenomenon 16 Table 2-1: Real-time High-level Languages 19 Figure 2-2: Process control application software. 22 Table 3-1: AT&T Versions of UNIX 31 Figure 5-1: Process Control Computer Sy~te'}'l Configuration. 73 Table 3-2: UNIX-alike Operating Systems 33 Figure 5-2: Process Flowsheet with Dynamically Refreshed Real-time 76 Table 3-3: Concurrent Environments for the IBM PC 37 Data Table 4-1: Third party programming and documentation software 65 Figure 5-3: Graphic Display of Controller Faceplates for Different 76 for programmable controllers. Control Loops Figure 5-4: Main Program on the µMAC-5000. 78 Figure 5-5: Interrupt Handler Module on the µMAC-5000 79 Figure 5-6: Procedure ONSPEC_SUPPORT on the µMAC-5000 80 Figure 5-7: Procedure HP3392A COMM on the µMAC-5000, 81 continued. / ,, / f j Chapter 1 Introduction The experience which has been gained during the last two decades on computer process control shows that the digital computer has a promising role to play in this field. Process computers have successfully replaced conventional control systems and application of advanced control concepts such as multivariable control, adaptive control, and dynamic optimization proved that remarkable process improvements are possible. Although, there is no doubt about the genuine role the computers can play in the process control environment, the difficult to trace explosion in hardware and software development over the last few years leads rapidly to redefinition of the overall process control computer system architecture and design. Much of industrial process controls is still being done from a central control room, which from the cost/performance standpoint is an ideal target for a large, central computer. With the availability of relatively inexpensive, dedicated front-ends, embedded computers, microprocessor-based interfaces, integral programming stations and local supervisory micro-computers a new philosophy towards distributed control architectures and local area networks is emerging. The goal of industry is to network all units and segments of the factory, and integrate information with the business environment. ,\ part from questions involved with overall computer system design, there are many questions to be answered in the specification of hardware components and software tools for a local microcomputer based process control system. It is clear that all the partners in the process control environment have to work together under a coordinated discipline and their internal time-scales have to be 6 "~- -~-_;- "-("·. matched with the process time-scales, and not the other way around. Thus, reconfigured with mm1mum cost and work, while it will require only in-house computer applications in the industrial process control environment require as a maintainance. An operating system must be installable on this microcomputer starting basis, real-time processing which by definition is a computer operation which must support a variety of real-time functions, must be interfaceable to a involving a well-timed interaction with the physical world. The solution to the high-level or problem-oriented language, must be transportable and readily real-time processing is embodied in both the available software and the implementable involving a minimum of tedious assembly language programming hardware components for a specific application. and must support multiple-task execution. The most important issue in this case The major decision facing an engineer who wants to install a computer is that the user should not at least have to develop the fundamental operating process control system, is whether to buy a packaged system provided by a system. Communication and interface software for peripheral equipment support suitable vendor or to buy a general purpose mm1 or microcomputer and develop is also necessary along with application packages and proper man-machine a special application software package in-house.
Load more

Recommended publications
  • Cobia Database Articles Final Revision 2.0, 2-1-2017
    Revision 2.0 (2/1/2017) University of Miami Article TITLE DESCRIPTION AUTHORS SOURCE YEAR TOPICS Number Habitat 1 Gasterosteus canadus Linné [Latin] [No Abstract Available - First known description of cobia morphology in Carolina habitat by D. Garden.] Linnaeus, C. Systema Naturæ, ed. 12, vol. 1, 491 1766 Wild (Atlantic/Pacific) Ichthyologie, vol. 10, Iconibus ex 2 Scomber niger Bloch [No Abstract Available - Description and alternative nomenclature of cobia.] Bloch, M. E. 1793 Wild (Atlantic/Pacific) illustratum. Berlin. p . 48 The Fisheries and Fishery Industries of the Under this head was to be carried on the study of the useful aquatic animals and plants of the country, as well as of seals, whales, tmtles, fishes, lobsters, crabs, oysters, clams, etc., sponges, and marine plants aml inorganic products of U.S. Commission on Fisheries, Washington, 3 United States. Section 1: Natural history of Goode, G.B. 1884 Wild (Atlantic/Pacific) the sea with reference to (A) geographical distribution, (B) size, (C) abundance, (D) migrations and movements, (E) food and rate of growth, (F) mode of reproduction, (G) economic value and uses. D.C., 895 p. useful aquatic animals Notes on the occurrence of a young crab- Proceedings of the U.S. National Museum 4 eater (Elecate canada), from the lower [No Abstract Available - A description of cobia in the lower Hudson Eiver.] Fisher, A.K. 1891 Wild (Atlantic/Pacific) 13, 195 Hudson Valley, New York The nomenclature of Rachicentron or Proceedings of the U.S. National Museum Habitat 5 Elacate, a genus of acanthopterygian The universally accepted name Elucate must unfortunately be supplanted by one entirely unknown to fame, overlooked by all naturalists, and found in no nomenclator.
    [Show full text]
  • Common Errors in English by Paul Brians [email protected]
    Common Errors in English by Paul Brians [email protected] http://www.wsu.edu/~brians/errors/ (Brownie points to anyone who catches inconsistencies between the main site and this version.) Note that italics are deliberately omitted on this page. What is an error in English? The concept of language errors is a fuzzy one. I'll leave to linguists the technical definitions. Here we're concerned only with deviations from the standard use of English as judged by sophisticated users such as professional writers, editors, teachers, and literate executives and personnel officers. The aim of this site is to help you avoid low grades, lost employment opportunities, lost business, and titters of amusement at the way you write or speak. But isn't one person's mistake another's standard usage? Often enough, but if your standard usage causes other people to consider you stupid or ignorant, you may want to consider changing it. You have the right to express yourself in any manner you please, but if you wish to communicate effectively you should use nonstandard English only when you intend to, rather than fall into it because you don't know any better. I'm learning English as a second language. Will this site help me improve my English? Very likely, though it's really aimed at the most common errors of native speakers. The errors others make in English differ according to the characteristics of their first languages. Speakers of other languages tend to make some specific errors that are uncommon among native speakers, so you may also want to consult sites dealing specifically with English as a second language (see http://www.cln.org/subjects/esl_cur.html and http://esl.about.com/education/adulted/esl/).
    [Show full text]
  • 12/04/13 1. Einleitung 1
    12/04/13 1. Einleitung 1 1. Einleitung − Was ist Systemadministration? ============================================= 12/04/13 1. Einleitung 2 System Administration: It’s a dirty job, but someone said I had to do it. Aufgaben eines Sysadmin gestern und heute: Früher Heute − Einrichten von neuen Nutzern Auch heute gibt es neue User per Hand mit Scripte, Oberflächen automatisiert − Druckermanagment Tonerpatrone Wechseln, Druckerjobs canceln, Drucker reaktivieren, Nutzer beruhigen, Das ist immer noch so. "Der Drucker druckt nicht, ich habe nichts gemacht." − Fragen beantworten: "Wie kann ich ....?" Die Nutzer lesen immer Das "Dialog−Manual" noch keine Manuals. − Prozesse killen Auch heute sollen Prozesse noch endlos laufen. 12/04/13 1. Einleitung 3 Früher Heute − Prozesse/Daemone nach Möglich, aber es gibt Absturz neu starten auch Überwachungstools − Tastaturen aktivieren kommt seltener vor − Backups veranlassen Die Datenmengen sind (zeitzyklisch, häufig) nur viel größer. − Restore von Files Auch heute löschen Nutzer ihre Files unabsichtlich. − "Mein Rechner macht nichts mehr!!!!" Passiert seltener, da die Monitoring/Tracing Rechner schneller sind und mehr Prozessoren haben, gibt es dieses Problem nicht so oft. − Rebooting von Systemen Alle zwei bis drei Jahre kommt bei Fehlern so etwas noch vor. − Speicherplatz auf Platten schaffen Jeder erfüllte Wunsch erzeugt Hilferuf: "Ich kann nichts mehr viele neue kleine Wünsche speichern!!!!" − Sicherheitslöcher finden und Schlimmer als je zuvor, beseitigen, Einbrecher suchen dank Internet und verfolgen 12/04/13 1. Einleitung 4 Früher Heute − Passwörter prüfen Nicht mehr nötig dank neuer Technologien − Programme installieren Es soll auch heute noch neue Programme geben. Einheitliche Verfahren erleichtern aber die Arbeit. − Betriebssystemupdates Vereinfacht. − Konfiguration des Rechnernetzes ja − Installieren neuer Rechner.
    [Show full text]
  • Computers&Electronics
    Computers&Electronics EPTEMBER 1983 formerly Popular Electronics $1 75 Improving Timex/Sinclair Data -Tape Loading Sony's New Personal Desktop Computer System Computerized Video Drawings Made Easy One -Shot Testing of Multiple Circuit Points 11-11,.# 1 1 1 .\\I. 1 r1 I A i f - .... f-7'I '1TTTT7 . II 1 ] _P .I- P _ 1 110S6 t!J OtJI1ndn7 210 OCOr131121nW 0519 0 N21060 é't 113N)121y0 1 o 1,873O OTbT T60W0S19 )1210 260i0^z view 140 14 7 1t ating System Simplified BUY A BANANA. SAVE A BUNCH. Meet the Banana',"the very business reports, etc.) tractor tough, versatile, portable, and feed (for precise alignment and reliable dot-matrix printer from quick loading), parallel or serial Gorilla:" interface (take your pick), self - At $249.95 retail it's an ideal inking ribbon cassette (for long and inexpensive companion for life and easy installation), 10 personal computers like Apple portable pounds in weight, and (or Apple"look alikes'such as compatibility with so many of the Franklin""orAlbern, most popular personal computers Commodore; "I'll S-80,` Kaypro;" on the market. Timex," Osborne;'etc. Plus its print head features a After that, it's merely com- unique single -hammer design that parable to other printers that can eliminates a lot of moving parts, to cost up to three times as much: eliminate a lot of annoying repairs. 10" carriages (to handle standard That's the Banana: silly name, 9'/2" paper), 80 columns, graphics serious service. It's everything capability, 10 characters per inch the expensive dot-matrix printers (expandable to 5 cpi) draft -quality are..
    [Show full text]
  • The Art of Unix Programming Next the Art of Unix Programming
    The Art of Unix Programming Next The Art of Unix Programming Eric Steven Raymond Thyrsus Enterprises <[email protected]> Copyright © 2003 Eric S. Raymond Revision History Revision 0.0 1999 esr Public HTML draft, first four chapters only. Revision 0.1 16 November 2002 esr First DocBook draft, fifteen chapters. Released to Mark Taub at AW. Revision 0.2 2 January 2003 esr First manuscript walkthrough at Chapter 7. Released to Dmitry Kirsanov at AW production. Revision 0.3 22 January 2003 esr First eighteen-chapter draft. Manuscript walkthrough at Chapter 12. Limited release for early reviewers. Revision 0.4 5 February 2003 esr Release for public review. Revision 0.41 11 February 2003 esr Corrections and additions to Mac OS case study. A bit more about binary files as caches. Added cite of Butler Lampson. Additions to history chapter. Note in futures chapter about C and exceptions. Many typo fixes. Revision 0.42 12 February 2003 esr Add fcntl/ioctl to things Unix got wrong. Dedication To Ken Thompson and Dennis Ritchie, because you inspired me. Table of Contents Requests for reviewers and copy-editors Preface Who Should Read This Book How To Use This Book Related References Conventions Used In This Book Our Case Studies Author's Acknowledgements I. Context 1. Philosophy Culture? What culture? The durability of Unix The case against learning Unix culture What Unix gets wrong What Unix gets right Open-source software Cross-platform portability and open standards The Internet The open-source community Flexibility in depth Unix is fun to hack The lessons of Unix can be applied elsewhere Basics of the Unix philosophy Rule of Modularity: Write simple parts connected by clean interfaces.
    [Show full text]
  • Massachusetts Institute of Technology Bulletin
    d 7I THE DEAN OF SCIEN<C OCT 171972 MASSACHUSETTS INSTITUTE OF TECHNOLOGY BULLETIN REPORT OF THE PRESIDENT 1971 MASSACHUSETTS INSTITUTE OF TECHNOLOGY BULLETIN REPORT OF THE PRESIDENT FOR THE ACADEMIC YEAR 1970-1971 MASSACHUSETTS INSTITUTE OF TECHNOLOGY BULLETIN VOLUME 107, NUMBER 2, SEPTEMBER, 1972 Published by the Massachusetts Institute of Technology 77 MassachusettsAvenue, Cambridge, Massachusetts, five times yearly in October, November, March, June, and September Second class postage paid at Boston, Massachusetts. Issues of the Bulletin include REPORT OF THE TREASURER REPORT OF THE PRESIDENT SUMMER SESSION CATALOGUE PUBLICATIONS AND THESES and GENERAL CATALOGUE Send undeliverable copies and changes of address to Room 5-133 Massachusetts Institute of Technology Cambridge,Massachusetts 02139. THE CORPORATION Honorary Chairman:James R. Killian, Jr. Chairman:Howard W. Johnson President:Jerome B. Wiesner Chancellor: Paul E. Gray Vice Presidentand Treasurer:Joseph J. Snyder Secretary:John J. Wilson LIFE MEMBERS Bradley Dewey, Vannevai Bush, James M. Barker, Thomas C. Desmond, Marshall B. Dalton, Donald F. Carpenter, Thomas D. Cabot, Crawford H. Greenewalt, Lloyd D. Brace, William A. Coolidge, Robert C. Sprague, Charles A. Thomas, David A. Shepard, George J. Leness, Edward J. Hanley, Cecil H. Green, John J. Wilson, Gilbert M. Roddy, James B. Fisk, George P. Gardner, Jr., Robert C. Gunness, Russell DeYoung, William Webster, William B. Murphy, Laurance S. Rockefeller, Uncas A. Whitaker, Julius A. Stratton, Luis A. Ferr6, Semon E. Knudsen, Robert B. Semple, Ir6n6e du Pont, Jr., Eugene McDermott, James R. Killian, Jr. MEMBERS Albert H. Bowker, George P. Edmonds, Ralph F. Gow, Donald A. Holden, H. I. Romnes, William E.
    [Show full text]
  • Reviewing Real-Time Performance of Nuclear Reactor Safety Systems
    NUREG/CR-6083 UCRL-ID-114565 Reviewing Real-Time Performance of Nuclear Reactor Safety Systems Prepared by G. G. Preckshot Lawrence Livermore National Laboratory Prepared for U.S. Nuclear Regulatory Commission AVAILABIUTY NOTICE Availability of Reference Materials Cited in NRC Publications Most documents cited In NRC publications will be available from one of the following sources: I, The NRC Public Document Room, 2120 L Street, NW, Lower Level. Washington, DC 20555-0001 2. The Superintendent of Documents, U.S. Government Printing Office, Mall Stop SSOP, Washington. DC 20402-9328 3. The National Technical Information Service, Springfield, VA 22161 Although the Hating that follows represents the majority of documents cited in NRC publications, it Is not intended to be exhaustive. Referenced documents available for inspection and copying for a fee from the NRC Public Document Room Include NRC correspondence and Internal NRC memoranda; NRC Office of Inspection and Enforcement bulletins, circulars, Information notices, Inspection and investigation notices: Licensee Event Reports; ven- dor reports and correspondence; Commission papers; and applicant and licensee documents and corre- spondence. The following documents In the NUREG series are available for purchase from the GPO Sales Program: formal NRC staff and contractor reports, NRC-sponsored conference proceedings, and NRC booklets and brochures. Also available are Regulatory Guides. NRC regulations In the Code of Federal Regulations, and Nuclear Regulatory Commission Issuances. Documents available from the National Technical Information Service Include NUREG series reports and technical reports prepared by other federal agencies and reports prepared by the Atomic Energy Commis- sion, forerunner agency to the Nuclear Regulatory Commission. Documents available from public and special technical libraries Include all open literature items, such as books, Journal and periodical articles, and transactions.
    [Show full text]
  • Operating System Support Matrix
    Operating System Win Win Win Win Win Win Win Win THEOS Product Description Win Win Win Win Windows Win XP Win XP Server Server Server Server Server Server Win 7 Win 7 Win 8 Win 8 Server Server Win 8.1 Win 8.1 Corona DOS Win 3.x Win NT4 Win 95 Win 98 Win 98SE Win Me Win 2000 Server Server Vista Vista Thin a Mac 8.6+ QNX 6.2 THEOS SCO 5.07 SCO 6.0 32 64 2003 2003 R2 2003 R2 2008 2008 2008 R2 32 64 32 64 2012 2012 R2 32 64 Linux Ver. 5.0 2000 2003 64 32 64 Client 32 32 64 32 64 64 64 64 PL182 USB-Serial Links USB-Serial Link 2-232-DB9 Two RS-232, 9-pin DB-9s USB-Serial Link 4-232-DB9 Four RS-232, 9-pin DB-9s USB-Serial Link 4-232-DB9 Cabled Four RS-232, 9-pin DB-9s with fan-out cable Serial PCIe SSerial-PCIe One 25-pin port, 16550 UART SSerial-PCIe/LP One 25-pin port, 16550 UART, low-profile DSerial-PCIe Two 9-pin ports, 16550 UARTs DSerial-PCIe/LP Two 9-pin ports, 16550 UARTs, low-profile Quattro-PCIe Four 9-pin ports, 16550 UARTs Serial PCI SSerial-PCI One 9-pin port, 16550 UART ? SSerial-PCI/LP One 25-pin port, 16550 UART, low-profile ? RS422 SS-PCI One 9-pin port, 16550 UART, RS-422 pinout ? LavaPort-650 One 9-pin port, 16650 UART ? DSerial-PCI Two 9-pin ports, 16550 UARTs
    [Show full text]
  • Comparing UNIX with Other Systems
    Comparing UNIX with other systems Timothy DO' Chase Corporate Computer systems, Inc. 33 West Main Street Holmdel, New Jersey he original concept behind this article was to make a grand comparison between UNIX Tand several other well known systems. This was to beall encompassing and packed with vital information summarized in neat charts, tables and graphs. As the work began, the realization settled in that this was not only difficult to do, but would result in a work so boring as to beincomprehensible. The reader, faced with such awealth ofinformation would be lost at best. Conclusions would be difficult to draw and, in short, the result would be worthless. Mtertearfully filling my waste basket with the initial efforts, I regrouped and began by as­ king myself why would anyone be interested in comparing UNIX with another operating system? There appears to be only two answers. First, one might hope to learn something about UNIX by analogy. IfI understand the file system on MPEN and someone tells me that UNIX is like that except for such and so, then I might be more quickly able to under­ stand UNIX. This I felt was an unlikely motivation. After all, there are much simpler ways to learn UNIX. Instead, the motivation for comparing UNIX to other systems must come from a need to evaluate UNIX. Ifwe are aware of the features or short comings ofother systems, then we can benefit by evaluating UNIX relative to those systems. Choosing an operating system or computer is a major decision which we can benefit from or be stuck with for a long time.
    [Show full text]
  • Flexconfigure User Guide
    P/I Enterprise Manager Version: 1.4 FlexConfigure User Guide Pitney Bowes1 is making this document available to you, free of charge, for use with the software, in order to make your experience more convenient. Every effort has been made to ensure the accuracy and usefulness of this document reflecting our experience. Product information may change after publication without notice. This document is being distributed on an "as is" basis and we make no representations or warranties, express or implied, with respect to its accuracy, reliability or completeness and the entire risk of its use shall be assumed by you. In no event shall we be liable to you or any other person, regardless of the cause, for the effectiveness or accuracy of this document or for any special, indirect, incidental or consequential damages arising from or occasioned by your use, even if advised of the possibility of such damages. All software described in this document is either our software and/or our licensed property. No license either expressed or implied is granted for the use of the software by providing this document and/or content. Under copyright law, neither this document nor the software may be copied, photocopied, reproduced, transmitted, or reduced to any electronic medium or machine-readable form, in whole or in part, without our prior written consent. We will continue to maintain this document and we welcome any clarifications or additional information regarding its content. Address comments concerning the content of this publication to: Pitney Bowes Building 600 6 Hercules Way Leavesden Watford WD25 7GS United Kingdom We may use or distribute the information supplied in any way we deem appropriate without incurring any obligation to the submitter of the information 1 Copyright © Pitney Bowes Software.
    [Show full text]
  • Partition Types
    Partition Types Partition Types The number on the right is in Hexadecimal. 01 DOS 12-bit fat 02 XENIX root 03 XENIX /usr 04 DOS 3.0+ 16-bit FAT (up to 32M) 05 DOS 3.3+ Extended Partition 06 DOS 3.31+ 16-bit FAT (over 32M) 07 OS/2 IFS (e.g., HPFS) 07 Advanced Unix 07 Windows NT NTFS 07 QNX2.x (pre-1988) 08 OS/2 (v1.0-1.3 only) 08 AIX boot partition 08 SplitDrive 08 DELL partition spanning multiple drives 08 Commodore DOS 08 QNX 1.x and 2.x ("qny") 09 AIX data partition 09 Coherent filesystem 09 QNX 1.x and 2.x ("qnz") 0a OS/2 Boot Manager 0a Coherent swap partition 0a OPUS 0b WIN95 OSR2 32-bit FAT 0c WIN95 OSR2 32-bit FAT, LBA-mapped 0e WIN95: DOS 16-bit FAT, LBA-mapped 0f WIN95: Extended partition, LBA-mapped 10 OPUS (?) 11 Hidden DOS 12-bit FAT 12 Compaq config partition 14 Hidden DOS 16-bit FAT <32M 16 Hidden DOS 16-bit FAT >=32M 17 Hidden IFS (e.g., HPFS) 18 AST SmartSleep Partition 19 Unused (Claimed for Willowtech Photon COS) 1b Hidden WIN95 OSR2 32-bit FAT 1c Hidden WIN95 OSR2 32-bit FAT, LBA-mapped 1e Hidden WIN95 16-bit FAT, LBA-mapped 20 Unused 21 Reserved 21 Unused 22 Unused 23 Reserved 24 NEC DOS 3.x 26 Reserved 31 Reserved 32 NOS 33 Reserved 34 Reserved 35 JFS on OS/2 or eCS 36 Reserved 38 THEOS ver 3.2 2gb partition 39 Plan 9 partition 39 THEOS ver 4 spanned partition 3a THEOS ver 4 4gb partition 3b THEOS ver 4 extended partition 3c PartitionMagic recovery partition 3d Hidden NetWare 40 Venix 80286 41 Linux/MINIX (sharing disk with DRDOS) 41 Personal RISC Boot 41 PPC PReP (Power PC Reference Platform) Boot 42 Linux swap (sharing
    [Show full text]
  • Netpages White.Pdf
    White NetPages NetPages™ is a directory for the Internet modeled after the phone book—with blue, white, and yellow pages sections. In the printed version, all three sections are together. In the e-book version, the White Netpages are one book and the Blue and Yellow NetPages are one book. To access the Blue and Yellow NetPages, send mail to [email protected] for sites. Directory of email addresses for individuals & businesses on the Internet How to Make a White NetPages Listing To add your name to NetPages, send this information to [email protected]. Last name: First name: Email address: Organization name: Job title: City: State: Country: Email address used for business, per- sonal, or both: Your listing will be sent to you via email for verification publishing. Yellow NetPages listings are available for business or organizations. Contact Aldea for pricing. If you have any questions or comments, write to [email protected] or call 1-800-TO ALDEA (619-943-0101). All listees will be notified of the electronic Internet “pickup” spot after its publication. How to get more information about NetPages NetPages is published in March and September. Hardcopy NetPages are distributed at major trade shows and by U.S. mail. Electronic versions are available online (locations to be advised). •General Aldea information [email protected] •Distribution information [email protected] •Add yourself to NetPages [email protected] •Remove yourself from NetPages [email protected] •Receive a copy of frequently asked questions (FAQ) [email protected] •Request a hardcopy of NetPages from: Aldea Communications, Inc.
    [Show full text]