DOCSLIB.ORG

Microsoft Windows Common Criteria Evaluation Security Target

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Microsoft Windows Common Criteria Evaluation Security Target Microsoft Common Criteria Security Target Microsoft Windows Common Criteria Evaluation Microsoft Windows 10 version 1903 (May 2019 Update) Microsoft Windows Server version 1903 (May 2019 Update) Security Target Document Information Version Number 0.04 Updated On July 19, 2019 Microsoft © 2019 Page 1 of 126 Microsoft Common Criteria Security Target Version History Version Date Summary of changes 0.01 March 23, 2019 Initial draft 0.02 June 18, 2019 Updates from evaluation, switched to GP OS PP 4.2.1 0.03 July 19, 2019 Final version for certification body 0.04 July 19, 2019 Version for publication Microsoft © 2019 Page 2 of 126 Microsoft Common Criteria Security Target 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 document 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. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. 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. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. © 2019 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Visual Basic, Visual Studio, Windows, the Windows logo, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Microsoft © 2019 Page 3 of 126 Microsoft Common Criteria Security Target TABLE OF CONTENTS SECURITY TARGET .........................................................................................................................1 VERSION HISTORY ..............................................................................................................................2 TABLE OF CONTENTS ........................................................................................................................4 LIST OF TABLES .................................................................................................................................7 1 SECURITY TARGET INTRODUCTION ......................................................................................9 1.1 ST REFERENCE ........................................................................................................................9 1.2 TOE REFERENCE......................................................................................................................9 1.3 TOE OVERVIEW ......................................................................................................................9 1.3.1 TOE TYPES ....................................................................................................................................... 9 1.3.2 TOE USAGE .................................................................................................................................... 10 1.3.3 TOE SECURITY SERVICES ................................................................................................................... 10 1.3.4 NON-TOE HARDWARE, SOFTWARE, FIRMWARE IN THE EVALUATION ....................................................... 12 1.4 TOE DESCRIPTION ................................................................................................................. 12 1.4.1 EVALUATED CONFIGURATIONS ........................................................................................................... 12 1.4.2 SECURITY ENVIRONMENT AND TOE BOUNDARY ................................................................................... 13 1.4.2.1 Logical Boundaries ...................................................................................................................... 13 1.4.2.2 Physical Boundaries .................................................................................................................... 13 1.5 PRODUCT DESCRIPTION .......................................................................................................... 15 1.6 CONVENTIONS, TERMINOLOGY, ACRONYMS ................................................................................ 15 1.6.1 CONVENTIONS ................................................................................................................................ 15 1.6.2 TERMINOLOGY ................................................................................................................................ 15 1.6.3 ACRONYMS..................................................................................................................................... 19 1.7 ST OVERVIEW AND ORGANIZATION ........................................................................................... 19 2 CC CONFORMANCE CLAIMS ............................................................................................... 20 3 SECURITY PROBLEM DEFINITION ........................................................................................ 21 3.1 THREATS TO SECURITY ............................................................................................................ 21 3.2 ORGANIZATIONAL SECURITY POLICIES ......................................................................................... 22 3.3 SECURE USAGE ASSUMPTIONS .................................................................................................. 22 4 SECURITY OBJECTIVES ....................................................................................................... 24 Microsoft © 2019 Page 4 of 126 Microsoft Common Criteria Security Target 4.1 TOE SECURITY OBJECTIVES ...................................................................................................... 24 4.2 SECURITY OBJECTIVES FOR THE OPERATIONAL ENVIRONMENT .......................................................... 25 5 SECURITY REQUIREMENTS ................................................................................................. 27 5.1 TOE SECURITY FUNCTIONAL REQUIREMENTS ............................................................................... 27 5.1.1 SECURITY AUDIT (FAU) .................................................................................................................... 29 5.1.1.1 Audit Data Generation (FAU_GEN.1) and FAU_GEN.1(WLAN) ................................................... 29 5.1.2 CRYPTOGRAPHIC SUPPORT (FCS) ....................................................................................................... 30 5.1.2.1 Cryptographic Support for GP OS PP .......................................................................................... 30 5.1.2.2 Cryptographic Support for WLAN Client EP ................................................................................ 33 5.1.3 USER DATA PROTECTION (FDP) ......................................................................................................... 35 5.1.4 IDENTIFICATION AND AUTHENTICATION (FIA)....................................................................................... 35 5.1.4.1 Identification and Authentication for GP OS PP ......................................................................... 35 5.1.4.2 Identification and Authentication for WLAN Client EP ............................................................... 37 5.1.5 SECURITY MANAGEMENT (FMT) ....................................................................................................... 37 5.1.5.1 Security Management for GP OS PP ........................................................................................... 37 5.1.5.2 Security Management for WLAN Client EP ................................................................................. 38 5.1.6 PROTECTION OF THE TSF (FPT) ......................................................................................................... 39 5.1.6.1 Protection of the TSF for GP OS PP ............................................................................................. 39 5.1.6.2 Protection of the TSF for WLAN Client EP ................................................................................... 40 5.1.7 TOE ACCESS (FTA) .......................................................................................................................... 41 5.1.7.1 TOE Access for GP OS PP ............................................................................................................
Load more

Recommended publications
  • Validators Report
    National Information Assurance Partnership ® TM Common Criteria Evaluation and Validation Scheme Validation Report IBM Global Security Kit (GSKit) 8.0.14 Report Number: CCEVS-VR-VID10394-2011 Dated: 2012-03-06 Version: 1.0 National Institute of Standards and Technology National Security Agency Information Technology Laboratory Information Assurance Directorate 100 Bureau Drive 9800 Savage Road STE 6740 Gaithersburg, MD 20899 Fort George G. Meade, MD 20755-6740 ACKNOWLEDGEMENTS Validation Team Jim Brosey Orion Security Fort Meade, Maryland Jandria S. Alexander Aerospace Fort Meade, Maryland Vicky Ashby The MITRE Corporation McLean, Virginia Evaluation Team Alejandro Masino, Trang Huynh, Courtney Cavness atsec Information Security Corporation Austin, Texas Table of Contents 1. EXECUTIVE SUMMARY ........................................................................................................................................ 4 2. IDENTIFICATION .................................................................................................................................................... 4 3. CLARIFICATION OF SCOPE ................................................................................................................................. 6 3.1. PHYSICAL SCOPE ................................................................................................................................................... 6 3.2. LOGICAL SCOPE ....................................................................................................................................................
    [Show full text]
  • Cen Workshop Agreement Cwa 14722-3
    CEN CWA 14722-3 WORKSHOP August 2004 AGREEMENT ICS 35.240.15 Supersedes CWA 14722-3:2004 English version Embedded financial transactional IC card reader (embedded FINREAD) - Part 3: Functional and Security Specifications This CEN Workshop Agreement has been drafted and approved by a Workshop of representatives of interested parties, the constitution of which is indicated in the foreword of this Workshop Agreement. The formal process followed by the Workshop in the development of this Workshop Agreement has been endorsed by the National Members of CEN but neither the National Members of CEN nor the CEN Management Centre can be held accountable for the technical content of this CEN Workshop Agreement or possible conflicts with standards or legislation. This CEN Workshop Agreement can in no way be held as being an official standard developed by CEN and its Members. This CEN Workshop Agreement is publicly available as a reference document from the CEN Members National Standard Bodies. CEN members are the national standards bodies of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG Management Centre: rue de Stassart, 36 B-1050 Brussels © 2004 CEN All rights of exploitation in any form and by any means reserved worldwide
    [Show full text]
  • Part 3: Security Assurance Components
    Common Criteria for Information Technology Security Evaluation Part 3: Security assurance components September 2012 Version 3.1 Revision 4 CCMB-2012-09-003 Foreword This version of the Common Criteria for Information Technology Security Evaluation (CC v3.1) is the first major revision since being published as CC v2.3 in 2005. CC v3.1 aims to: eliminate redundant evaluation activities; reduce/eliminate activities that contribute little to the final assurance of a product; clarify CC terminology to reduce misunderstanding; restructure and refocus the evaluation activities to those areas where security assurance is gained; and add new CC requirements if needed. CC version 3.1 consists of the following parts: Part 1: Introduction and general model Part 2: Security functional components Part 3: Security assurance components Trademarks: UNIX is a registered trademark of The Open Group in the United States and other countries Windows is a registered trademark of Microsoft Corporation in the United States and other countries Page 2 of 233 Version 3.1 September 2012 Legal Notice: The governmental organisations listed below contributed to the development of this version of the Common Criteria for Information Technology Security Evaluation. As the joint holders of the copyright in the Common Criteria for Information Technology Security Evaluation, version 3.1 Parts 1 through 3 (called “CC 3.1”), they hereby grant non- exclusive license to ISO/IEC to use CC 3.1 in the continued development/maintenance of the ISO/IEC 15408 international standard. However, these governmental organisations retain the right to use, copy, distribute, translate or modify CC 3.1 as they see fit.
    [Show full text]
  • WIN-911 7.17 & WEB-911 Xtools 7.13 System Requirements
    WIN-911 7.17 & WEB-911 XTools 7.13 System Requirements WIN-911 • Personal computer with 2.1 GHz Pentium 4 processor or higher • Microsoft Windows XP Service Pack 3, Microsoft Windows Server 2003 Service Pack 1 or later, Microsoft Windows 2003 R2, Microsoft Windows 7 Service Pack 1, Microsoft Windows Server 2008 Service Pack 2, Microsoft Server 2008 R2 Service Pack 1, Microsoft Windows 8 & 8.1, Microsoft Server 2012, Microsoft Server 2012 R2, Windows 10. (Only US Versions of Windows) *** TAPI Voice Calls are NOT SUPPORTED in Windows 10 Version 1903 *** • 2GB of RAM. Additional RAM is recommended if additional programs are to be run simultaneously. • 2 GB of hard disk space • Optional Notification Hardware: Dial-out Paging Data fax modem and a dedicated analog phone line Voice Dial-outs/ins Dialogic telephonic card or a TAPI voice modem and a dedicated analog phone line. *** TAPI is NOT SUPPORTED in Windows 10 Version 1903 *** SMS Text Messaging GSM, CDMA or HSPA modem with an activated cellular account. Email Broadband always-on internet connection. Local Announcer Sound card and audio output source. Printing Dot Matrix printer or a printer capable of printing a "line-at-a-time" is recommended. WEB-911 Service • Must be installed on the same machine as WIN-911 • Microsoft .NET 4.0 and Internet Information Services (IIS) are also required • Microsoft Windows XP Service Pack 3, Microsoft Windows Server 2003 Service Pack 1 or later, Microsoft Windows 2003 R2, Microsoft Windows 7 Service Pack 1, Microsoft Windows Server 2008 Service Pack 2, Microsoft Server 2008 R2 Service Pack 1, Microsoft Windows 8 & 8.1, Microsoft Server 2012, Microsoft Server 2012 R2, Windows 10.
    [Show full text]
  • Administrative Guide for Windows 10 and Windows Server Fall Creators Update (1709)
    Operational and Administrative Guidance Microsoft Windows 10 and Windows Server Common Criteria Evaluation for Microsoft Windows 10 and Windows Server Version 1903 (May 2019 Update) General Purpose Operating System Protection Profile © 2019 Microsoft. All rights reserved. Microsoft Windows 10 GP OS Administrative Guidance Copyright and disclaimer 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 document 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. This work is licensed under the Creative Commons Attribution-NoDerivs-NonCommercial VLicense (which allows redistribution of the work). To view a copy of this license, visithttp://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. 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. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred.
    [Show full text]
  • Cygwin User's Guide
    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
    [Show full text]
  • Ccdb-2009-03-001
    Supporting Document Mandatory Technical Document Application of Attack Potential to Smartcards March 2009 Version 2.7 Revision 1 CCDB-2009-03-001 Foreword This is a supporting document, intended to complement the Common Criteria version 3 and the associated Common Evaluation Methodology for Information Technology Security Evaluation. Supporting documents may be “Guidance Documents”, that highlight specific approaches and application of the standard to areas where no mutual recognition of its application is required, and as such, are not of normative nature, or “Mandatory Technical Documents”, whose application is mandatory for evaluations whose scope is covered by that of the supporting document. The usage of the latter class is not only mandatory, but certificates issued as a result of their application are recognized under the CCRA. Technical Editor: BSI Document History: V2.7 March 2009 (technical update of rating categories and update on usage of open samples based upon corresponding JIL document version 2.7) V2.5 December 2007 (explicit statements added that the points for identification and exploitation have to be added at the end to achieve the final attack potential value, references updated) V2.3 April 2007 (evaluation time guideline and rules regarding the use of open samples added and updated for use with both CC version 2 and 3) V2.1 April 2006 (classification as mandatory technical document, several updates to the tables) V1.1, July 2002 (draft indicator deleted, references updated, same content as V1.0) General purpose: The security properties of both hardware and software products can be certified in accordance with CC. To have a common understanding and to ensure that CC is used for hardware integrated circuits in a manner consistent with today’s state of the art hardware evaluations, the following chapters provide guidance on the individual aspects of the CC assurance work packages in addition to the Common Evaluation Methodology [CEM].
    [Show full text]
  • Microsoft Windows Common Criteria Evaluation Security Target
    Windows 10, Server 2012 R2 Security Target Microsoft Windows Common Criteria Evaluation Microsoft Windows 10 Microsoft Windows Server 2012 R2 Security Target Document Information Version Number 1 Updated On March 17, 2016 Microsoft © 2016 Page 1 of 97 Windows 10, Server 2012 R2 Security Target 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 document 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. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. 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. The example companies, organizations, products, people and events depicted herein are fictitious.
    [Show full text]
  • 3 Adquisición De Bienes Y Servicios Código Bs – Fr – 025 Formato
    PROCESO Versión: 3 CÓDIGO ADQUISICIÓN DE BIENES Y SERVICIOS BS – FR – 025 FORMATO Estudios Previos – Procesos Públicos De Selección Página 1 de 101 1. DESCRIPCIÓN DE LA NECESIDAD QUE LA ENTIDAD ESTATAL PRETENDE SATISFACER CON EL PROCESO DE CONTRATACIÓN (Art. 2.2.1.1.2.1.1 Numeral 1 Decreto 1082 de 2015). 1.2 JUSTIFICACIÓN DE 1.1. Justificación de la necesidad LA CONTRATACIÓN De acuerdo con lo establecido en la Ley 1967 de 2019, el objetivo del Ministerio es formular, adoptar, dirigir, coordinar, inspeccionar, vigilar, controlar y ejecutar la política pública, planes, programas y proyectos en materia del deporte, la recreación, el aprovechamiento del tiempo libre y la actividad física para promover el bienestar, la calidad de vida, así como contribuir a la salud pública, a la educación, a la cultura, a la cohesión e integración social, a la conciencia nacional y a las relaciones internacionales, a través de la participación de los actores públicos y privados. Aunado a lo anterior el inciso segundo del artículo 8 de la Ley 1967 de 2019 expresamente señala: “Los servidores públicos que a la entrada en vigencia de la presente ley se encontraban vinculados al Ministerio quedarán automáticamente incorporados en la planta de personal del Ministerio del Deporte”. Y el artículo 10 de la misma Ley también dice: “Contratos y convenios vigentes. Los contratos y convenios vigentes suscritos por el continuarán ejecutándose por el Ministerio del Deporte, sin que para ello sea necesario suscripción de documento adicional alguno diferente a la comunicación a los respectivos contratistas. Para todos los efectos contractuales, el Ministerio del Deporte asume los derechos y obligaciones del Departamento Administrativo del Deporte, la Recreación, la Actividad Física y el Aprovechamiento del Tiempo Libre (Coldeportes).
    [Show full text]
  • Microsoft Windows Common Criteria Evaluation Security Target
    Microsoft Common Criteria Security Target Microsoft Windows Common Criteria Evaluation Microsoft Windows 10 version 1809 (October 2018 Update) Microsoft Windows Server 2019 (October 2018 Update) Security Target Document Information Version Number 0.05 Updated On June 18, 2019 Microsoft © 2019 Page 1 of 126 Microsoft Common Criteria Security Target Version History Version Date Summary of changes 0.01 June 27, 2018 Initial draft 0.02 December 21, 2018 Updates from security target evaluation 0.03 February 21, 2019 Updates from evaluation 0.04 May 6, 2019 Updates from GPOS PP v4.2.1 0.05 June 18, 2019 Public version Microsoft © 2019 Page 2 of 126 Microsoft Common Criteria Security Target 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 document 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. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.
    [Show full text]
  • Download Windows 10 Update 1809 Windows 10: Continue Support for Versions 1803 and Onward
    download windows 10 update 1809 Windows 10: continue support for versions 1803 and onward. I have a question for the Windows team. I want to know if it is possible to continue support for Windows 10 version 1803 and onward? I am using 1809. I am asking is because when 1903 comes out someday, my device might not be able to work with it. I would like to use it but do not want to spend $$ buying a new device. 1809 is a good version. It seems like Microsoft will end support for different versions of Windows 10 different times. Subscribe Subscribe to RSS feed. Report abuse. Replies (6) Support for version 1809 ends on May 12, 2020. All this means is that you will not receive updates for that version, it does not mean that your Windows will cease to function, it will continue working as it always has . If your device cannot take the 1903 update, then it will refuse to install, that is all that will happen, you have nothing to worry about . Power to the Developer! MSI GV72 - 17.3", i7-8750H (Hex Core), 32GB DDR4, 4GB GeForce GTX 1050 Ti, 256GB NVMe M2, 2TB HDD. Report abuse. Was this reply helpful? Sorry this didn't help. Great! Thanks for your feedback. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. How satisfied are you with this reply? Thanks for your feedback. I mean continue support for versions like 1803, 1809 and onward. I don't think anyone want the versions to end support.
    [Show full text]
  • Windows System Error Codes and What They Mean
    Windows system error codes and what they mean This information was gathered from: https://msdn.microsoft.com/en-us/library/windows/desktop/ ms681382(v=vs.85).aspx You can find additional error codes and messages in the above website. Code Description: 0 The operation completed successfully. 1 Incorrect function. 2 The system cannot find the file specified. 3 The system cannot find the path specified. 4 The system cannot open the file. 5 Access is denied. 6 The handle is invalid. 7 The storage control blocks were destroyed. 8 Not enough storage is available to process this command. 9 The storage control block address is invalid. 10 The environment is incorrect. 11 An attempt was made to load a program with an incorrect format. 12 The access code is invalid. 13 The data is invalid. 14 Not enough storage is available to complete this operation. 15 The system cannot find the drive specified. 16 The directory cannot be removed. 17 The system cannot move the file to a different disk drive. 18 There are no more files. 19 The media is write protected. 20 The system cannot find the device specified. 21 The device is not ready. 22 The device does not recognize the command. 23 Data error (cyclic redundancy check). 24 The program issued a command but the command length is incorrect. 25 The drive cannot locate a specific area or track on the disk. 26 The specified disk or diskette cannot be accessed. 27 The drive cannot find the sector requested. 28 The printer is out of paper.
    [Show full text]