DOCSLIB.ORG

Microsoft Visual C++ 6.0 Ide Tutorial Creating Win32 Console Mode

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Microsoft Visual C++ 6.0 Ide Tutorial Creating Win32 Console Mode Document 2002-31 MICROSOFT VISUAL C++ 6.0 IDE TUTORIAL Creating Win32 Console-Mode Applications Jeffrey S. Franzone, Assistant Professor Engineering Technology Department University of Memphis Abstract Microsoft Visual C++ is a commonly used programming language and application environment in many computer science and computer engineering technology programs. Visual C++ can be used to teach both C and C++ and it boasts a highly powerful, but easy to use, development environment. One of the strengths of the Visual C++ product is the different types of applications that can be generated. Visual C++ supports Windows applications, DLLs, and console-mode applications, to name just a few. Visual C++ 6.0 is currently used in the C/C++ programming curriculum in the Computer Engineering Technology Department at the University of Memphis. The department has chosen this product to teach C and C++ programming for three major reasons: 1) it is a professional and modern C/C++ programming application platform that is an industry standard, 2) it is relatively easy to use and its rich set of features and tools can be taught in parallel with C/C++ programming concepts and techniques, and 3) it supports console-mode programming. Visual C++’s console-mode support makes it an ideal application platform for teaching C/C++ programming fundamentals in lower division programming courses. It is believed by many (and supported by many C/C++ programming textbooks) that console-mode programming is an easier environment to teach, analyze, and learn fundamental C/C++ programming concepts and standard programming techniques. Many of these concepts and techniques, when taught in a console-mode environment, are also more portable to other computer platforms. The purpose of the Microsoft Visual C++ 6.0 IDE Tutorial is to support computer programming instructors who want to use the Visual C++ product to develop Win32 console-mode applications in introductory C/C++ programming courses without spending several weeks explaining the Visual C++ environment. The tutorial takes a visual, step-by-step approach in demonstrating how to create a Win32, console-mode application as well as covering introductory programming concepts such as the “edit, compile, link, and run” process and useful procedures such as printing source-code and program output. The tutorial is thorough and complete enough to be given as a lab or homework exercise or as a class exercise done in a laboratory setting. 7.861.1 Page Proceedings of the 2002 American Society for Engineering Education Annual Conference & Exposition Copyright Ó 2002, American Society for Engineering Education I. Introduction The Microsoft Visual C++ IDE Tutorial is organized under the following sections with a brief description of the concepts covered under each section. The complete tutorial is provided at the end of this paper. 1. OBJECTIVES A very brief general summary of the purpose of the tutorial. 2. RESOURCES YOU WILL NEED An outline of reader skills, materials, and software needed to successfully complete the tutorial. 3. INTRODUCTION TO C/C++ DEVELOPMENT This section briefly discusses the edit, compile, link, and run development process for C/C++ programs, the types of files generated by each step, and the meaning of “console-mode”. 4. CREATING A PROJECT & WORKSPACE This section uses visual screenshots to single-step the reader through the process of starting Visual C++ 6.0 and creating an empty Win32, console-mode application, an overview of the more important IDE commands and windows encountered in the development environment, the meaning of the terms “Project” and “Workspace”, and some of the important files generated by the creation of an empty Win32, console-mode application. 5. CREATING A SOURCE FILE This section uses visual screenshots to show the reader the steps necessary to create a blank C/C++ source file and include it in the current project. 6. USING THE IDE EDITOR This section instructs the reader to enter an example C program into the Document Window. Issues concerning saving files, opening and saving project files from a floppy-disk versus a hard disk, and generating a default workspace are also discussed. 7. COMPILING A PROGRAM This section instructs the reader on the steps needed to compile a C/C++ source file and the purpose of the Output Window. To demonstrate how the compiler detects syntax errors, an error is purposely entered into the example program to generate a compilation error. 8. LINKING A PROGRAM This section instructs the reader on the steps needed to link a C/C++ object file. Page 7.861.2 Page Proceedings of the 2002 American Society for Engineering Education Annual Conference & Exposition Copyright Ó 2002, American Society for Engineering Education 9. RUNNING A PROGRAM This section instructs the reader on the steps needed to run a C/C++ executable file from within the Visual C++ development environment. Visual screenshots are used to demonstrate the running of the example program. Also, instructions are given on the steps needed to run applications from a windowed-screen to a full-screen and vice- versa. 10. PRINTING SOURCE CODE & PROGRAM OUTPUT This section discusses the steps needed to print source code from within the Visual C++ development environment and how to use text or graphics screenshots to capture and print program output. 11. OTHER ITEMS OF INTEREST This section consists of several subsections that describe useful shortcuts in the development process and common questions that arise when developing Win32, console-mode applications for the first time. The subsections include: a). Reopening a Project. b). Where do I find my program’s executable file? c). Do I need Visual C++ to run my applications? d). Using the Build and Execute commands. e). IDE color schemes. 12. WHAT YOU HAVE LEARNED This section provides a summary of the major concepts covered in the tutorial. 13. SOME CLOSING THOUGHTS This section provides the reader with some helpful “wisdom” about learning the Visual C++ environment before undertaking serious study of C/C++ programming. The following list is a summary of the concepts and techniques that are learned after completing the Microsoft Visual C++ 6.0 IDE Tutorial. 1. The four major steps in writing a C/C++ program. 2. The meanings of the terms “Edit”, “Compile”, “Link”, and “Run”. 3. The meanings of the terms “source code”, “object file”, and “executable file” and the file extensions associated with them. 4. The meanings of the terms “console-mode” and “Win32 console-mode” programs. 5. The four major IDE screen areas. 6. The steps required to create an empty Project for a Win32 Console Application. 7. The meanings of the terms “Project” and “Workspace”. 8. The major files that are internally generated by Visual C++ when an empty Win32 Console Application Project is created. 9. The purpose, significance, and file extensions associated with the “Project file”, “Workspace file”, and “Workspace Options file”. 7.861.3 Page Proceedings of the 2002 American Society for Engineering Education Annual Conference & Exposition Copyright Ó 2002, American Society for Engineering Education 10. The name and location of the folder where a program’s executable and object files are stored. 11. How to create a new C/C++ source file and how to determine the appropriate file extension. 12. How to list project files in the Project Window and how to view the contents of project files in the Document Window. 13. How to manually enter a C/C++ source file into a blank document using the built-in editor. 14. The maximum line length that can be entered into a source document without text- clipping or word-wrapping when printed from the IDE. 15. How and when to save your source and Workspace files using the IDE. 16. The advantages of storing Project files on the local hard drive during development and when it is appropriate to store Project files on a floppy disk. 17. How to open a previously created Workspace from a floppy disk or local hard drive assuming all appropriate files exist and how to create a default Workspace when only the source file exists. 18. How to “compile” a C/C++ source file using the “Compile…” command. 19. The purpose of the Output Window and how it helps you detect syntax errors in your source code. 20. How to create an executable file by “linking” object code using the “Build…” command. 21. How to run your programs from within the IDE by using the “Execute…” command. 22. When the “Press any key to continue” message appears. 23. How to switch a running program from a “windowed” session to a “full-screen” session. 24. How to print a source file from within the IDE. 25. How to capture and print program output using a “text screenshot” or “graphics screenshot”. 26. How to open a previously created Project without first starting the IDE and executing menu commands. 27. The meaning and significance of an executable file (standalone application). 28. How to compile and link a program with a single command (Build…) and how to compile, link, and run a program with a single command (Execute…). 29. The three shortcut command icons that are used to compile, link, and execute programs from within the IDE. 30. How and where to change the color scheme of the IDE environment and the effect it has on other Windows applications. Many beginning C/C++ programming students who have used the tutorial in the Engineering Technology Department at the University of Memphis have provided valuable feedback to the effectiveness of the tutorial (and many have suggested additional screenshots and explanations that have been incorporated into the latest version). Many have commented positively on the tutorial’s “attention-to-detail”, leading the reader through a thorough, step-by-step process.
Load more

Recommended publications
  • Use of Microsoft Visual Studio Express Edition and Directx to Simulate Movements of a Colony of Penguins That Must Be Tagged for a Science Mission Education
    Use of Microsoft Visual Studio Express Edition and DirectX to Simulate Movements of a Colony of Penguins that must be tagged for a Science Mission Education Sandy Harrison (WSSU), Tushar Majithia (Mentor), Spencer Weeks- Jamieson, Jasmin Rivers (ECSU), Terrance Mason (MVSU), Dr. Arvin Agah (Mentor) (KU) igloos to the snow, the game itself displays a Abstract- type of climate that some penguins live in. In developing this game, the team is specifying, Students begin to take a general interest designing, implementing, and testing the in becoming scientists or engineers at early stages software. Some of the programs that the team in their life, such as the middle school level. It is utilized were C++, VC++ Express 2005 Edition imperative that they are targeted at this point in compiler, and Microsoft Platform SDK their lives to be encouraged to pursue their (Software Development Kit). This project education in science, technology, engineering, and mathematics (STEM) fields. The dilemma is how consisted of upgrading a previously developed to get young scholars interested in STEM areas? game. While using C++ in the aspect of Our proposed tool is an educational and programming, we modified the previous entertaining video game, as a vast number of young program's features with realistic graphics. This students tend to play video games everyday. Our modification would enrich it with a realistic goal is to combine education and fun into a game in perspective that would better serve our primary order to teach the players about polar research. objective. To validate if middle school students The objective of this URE Summer project is to would enjoy this game, we used the 2007 enhance an existing video game to educate young CReSIS Middle School Program students as students on the Polar Regions including challenges that scientists face.
    [Show full text]
  • Using Microsoft Visual Studio to Create a Graphical User Interface ECE 480: Design Team 11
    Using Microsoft Visual Studio to Create a Graphical User Interface ECE 480: Design Team 11 Application Note Joshua Folks April 3, 2015 Abstract: Software Application programming involves the concept of human-computer interaction and in this area of the program, a graphical user interface is very important. Visual widgets such as checkboxes and buttons are used to manipulate information to simulate interactions with the program. A well-designed GUI gives a flexible structure where the interface is independent from, but directly connected to the application functionality. This quality is directly proportional to the user friendliness of the application. This note will briefly explain how to properly create a Graphical User Interface (GUI) while ensuring that the user friendliness and the functionality of the application are maintained at a high standard. 1 | P a g e Table of Contents Abstract…………..…………………………………………………………………………………………………………………………1 Introduction….……………………………………………………………………………………………………………………………3 Operation….………………………………………………….……………………………………………………………………………3 Operation….………………………………………………….……………………………………………………………………………3 Visual Studio Methods.…..…………………………….……………………………………………………………………………4 Interface Types………….…..…………………………….……………………………………………………………………………6 Understanding Variables..…………………………….……………………………………………………………………………7 Final Forms…………………....…………………………….……………………………………………………………………………7 Conclusion.…………………....…………………………….……………………………………………………………………………8 2 | P a g e Key Words: Interface, GUI, IDE Introduction: Establishing a connection between
    [Show full text]
  • Designing Microsoft ASP.NET Applications by Douglas J
    Designing Microsoft ASP.NET Applications by Douglas J. Reilly ISBN: 0735613486 Microsoft Press © 2002 (402 pages) Move beyond simple ASP scripting --and learn how to build sophisticated Web applicatons with ASP.NET. Companion Web Site Table of Contents Designing Microsoft ASP.NET Applications Acknowledgments Introduction Chapter 1 - Introduction to ASP.NET Development Chapter 2 - Managed Code and the Common Language Runtime Chapter 3 - The .NET Framework Objects and Languages Chapter 4 - ASP.NET Development 101 Chapter 5 - Web Forms Chapter 6 - Creating ASP.NET Components Chapter 7 - Balancing Server and Client Functionality Chapter 8 - Time to Get the Data Chapter 9 - Data and ASP.NET Forms Chapter 10 - XML Web Services Appendix A - Configuring ASP.NET Applications in IIS Appendix B - What You Need to Know About HTML to Use This Book Index List of Figures List of Tables List of Listings List of Sidebars Designing Microsoft ASP.NET Applications Douglas J. Reilly PUBLISHED BY Microsoft Press A Division of Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 Copyright © 2002 by Douglas J. Reilly All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Library of Congress Cataloging-in-Publication Data Reilly, Douglas J. Designing Microsoft ASP.NET Applications / Douglas J. Reilly. p. cm. Includes index. ISBN 0-7356-1348-6 1. Internet programming. 2. Active server pages. 3. Web servers. I. Title. QA76.625 .R45 2001 005.2’76—dc21 2001051310 Printed and bound in the United States of America.
    [Show full text]
  • Practical ASP.NET Web API
    Practical ASP.NET Web API Badrinarayanan Lakshmiraghavan Practical ASP.NET Web API Copyright © 2013 by Badrinarayanan Lakshmiraghavan This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Exempted from this legal reservation are brief excerpts in connection with reviews or scholarly analysis or material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the work. Duplication of this publication or parts thereof is permitted only under the provisions of the Copyright Law of the Publisher’s location, in its current version, and permission for use must always be obtained from Springer. Permissions for use may be obtained through RightsLink at the Copyright Clearance Center. Violations are liable to prosecution under the respective Copyright Law. ISBN-13 (pbk): 978-1-4302-6175-9 ISBN-13 (electronic): 978-1-4302-6176-6 Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights.
    [Show full text]
  • Command Line Interface User Guide for Version 11.0 Copyright © 1994-2017 Dell Inc
    Command Line Interface User Guide for Version 11.0 Copyright © 1994-2017 Dell Inc. or its subsidiaries. All Rights Reserved. Contact Information RSA Link at https://community.rsa.com contains a knowledgebase that answers common questions and provides solutions to known problems, product documentation, community discussions, and case management. Trademarks For a list of RSA trademarks, go to www.emc.com/legal/emc-corporation-trademarks.htm#rsa. License Agreement This software and the associated documentation are proprietary and confidential to EMC, are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice below. This software and the documentation, and any copies thereof, may not be provided or otherwise made available to any other person. No title to or ownership of the software or documentation or any intellectual property rights thereto is hereby transferred. Any unauthorized use or reproduction of this software and the documentation may be subject to civil and/or criminal liability. This software is subject to change without notice and should not be construed as a commitment by EMC. Third-Party Licenses This product may include software developed by parties other than RSA. The text of the license agreements applicable to third-party software in this product may be viewed on the product documentation page on RSA Link. By using this product, a user of this product agrees to be fully bound by terms of the license agreements. Note on Encryption Technologies This product may contain encryption technology. Many countries prohibit or restrict the use, import, or export of encryption technologies, and current use, import, and export regulations should be followed when using, importing or exporting this product.
    [Show full text]
  • CA Plex C# Best Practices
    CA Plex C# Best Practices Example Document Creating packages and code libraries and managing C# source code and application artifacts CA Plex version 6.1 Created by: In collaboration with IIDEA Solutions and CCH, and assistance from CA. Published with the kind permission of the South Carolina Judicial Department . Packages and .NET Assemblies Best Practices for CA Plex. Contents 1. Introduction ......................................................................................................................................... 3 2. Use of assemblies and modules when creating code libraries ............................................................. 3 3. Creating and using assemblies ............................................................................................................. 4 4. Considerations when packaging your model ....................................................................................... 5 5. Software required on the build server .................................................................................................. 6 6. Modelling C# Code Libraries in Plex .................................................................................................. 7 7. Setting up the build server and installing Cruise Control .................................................................. 10 8. Development life cycle ...................................................................................................................... 20 Appendix ..................................................................................................................................................
    [Show full text]
  • Programming with Windows Forms
    A P P E N D I X A ■ ■ ■ Programming with Windows Forms Since the release of the .NET platform (circa 2001), the base class libraries have included a particular API named Windows Forms, represented primarily by the System.Windows.Forms.dll assembly. The Windows Forms toolkit provides the types necessary to build desktop graphical user interfaces (GUIs), create custom controls, manage resources (e.g., string tables and icons), and perform other desktop- centric programming tasks. In addition, a separate API named GDI+ (represented by the System.Drawing.dll assembly) provides additional types that allow programmers to generate 2D graphics, interact with networked printers, and manipulate image data. The Windows Forms (and GDI+) APIs remain alive and well within the .NET 4.0 platform, and they will exist within the base class library for quite some time (arguably forever). However, Microsoft has shipped a brand new GUI toolkit called Windows Presentation Foundation (WPF) since the release of .NET 3.0. As you saw in Chapters 27-31, WPF provides a massive amount of horsepower that you can use to build bleeding-edge user interfaces, and it has become the preferred desktop API for today’s .NET graphical user interfaces. The point of this appendix, however, is to provide a tour of the traditional Windows Forms API. One reason it is helpful to understand the original programming model: you can find many existing Windows Forms applications out there that will need to be maintained for some time to come. Also, many desktop GUIs simply might not require the horsepower offered by WPF.
    [Show full text]
  • For Mac OS X
    C More on Stata for Mac Contents C.1 Using Stata datasets and graphs created on other platforms C.2 Exporting a Stata graph to another document C.3 Stata and the Notification Manager C.4 Stata(console) for Mac OS X C.1 Using Stata datasets and graphs created on other platforms Stata will open any Stata .dta dataset or .gph graph file, regardless of the platform on which it was created, even if it was a Windows or Unix system. Also, Stata for Windows and Stata for Unix users can use any files that you create. Remember that .dta and .gph files are binary files, not text (ASCII) files, so they need no translation; simply copy them over to your hard disk as is. Files created on other platforms can be directly opened in the Command window; for example, you can load a dataset by typing use filename or by double-clicking on the file in the Finder. C.2 Exporting a Stata graph to another document Suppose that you wish to export a Stata graph to a document created by your favorite word processor or presentation application. You have two main choices for exporting graphs: you may copy and paste the graph by using the Clipboard, or you may save the graph in one of several formats and import the graph into the application. C.2.1 Exporting the graph by using the Clipboard The easiest way to export a Stata graph into another application is to use drag and drop. You can select the graph in the Graph window and drag it to the location you would like it in another open application.
    [Show full text]
  • C Add Web Reference to Console Application
    C Add Web Reference To Console Application Opposed Taylor escalading observantly while Frederic always garner his gyrations parody similarly, he pledging so impudently. Heliolithic and nihilism Zak gelatinizes her polyclinics blueing elect and triturated palewise. Liable Morse preplanned irretrievably, he territorializes his Leto very man-to-man. And once provided project reference is added we can extract the debugger and. Using the Web Service from Code Microsoft Visual C NET. Hi i am on console application i want to footing the wsdl file without service reference or web reference This XML file does then appear to. Net objects before actual visual studio with odata web services? Visual studio c console application template Code Example. You can reference and to add web reference console application project? Add bleed and assembly references in C Interactive. Using client certificates in much part 5 working with client. Visual basic code example. C Copy using System using SystemIO Renders a report located on. And web reference to create drive location. Now welcome you want are doing HTTP requests in another console application in NET 4 then I. Azure SQL Azure-IoT c-sharp C Cloud Cloud Computing Cloud DataBase csharp CSS. In business Solution Explorer right-click on YourSolutionYourProjectReferences Select permanent Service Reference. Visual C using System using SystemData using MySqlDataMySqlClient. I have added a method CheckArgs which checks if the application is called with command line parameters. C Windows AzureWebSitesnet. The WSDL document actually tells a client application what consider the types. Comen-usdotnetcoreadditional-toolswcf-web-service-reference-guide I'm. NET Client C 11242017 7 minutes to read 11 In quality article by Mike Wasson and Rick Anderson.
    [Show full text]
  • Installation Manual for Oracle Application Server 10.1.3.3 on Unix for Agile E6.1
    Oracle® Agile Engineering Data Management Installation Manual for Oracle Application Server 10.1.3.3 on Unix for Agile e6.1 Part No. E13352-02 February 2009 Installation Manual for Oracle Application Server 10.1.3.3 on Unix for Agile e6.1 Copyright and Trademarks Copyright © 1995, 2009, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Console Command Line Shell Guide
    Red Hat Gluster Storage 3 Console Command Line Shell Guide A guide for installing and using the Command Line Shell for Red Hat Storage Console. Last Updated: 2017-10-18 Red Hat Gluster Storage 3 Console Command Line Shell Guide A guide for installing and using the Command Line Shell for Red Hat Storage Console. Pavithra Srinivasan Red Hat Engineering Content Services [email protected] Legal Notice Copyright © 2013-2014 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent.
    [Show full text]
  • Application Programming Interfaces
    ERserver zSeries Application Programming Interfaces SB10-7030-06 Level 06a, November 2004 ER s er ver zSeries Application Programming Interfaces SB10-7030-06 Level 06a, November 2004 Level 06a, November 2004 Note! Before using this information and the product it supports, be sure to read the general information under Appendix F, “Notices,” on page F-1. Seventh Edition (October 2004) ™ ® | This edition, SB10-7030-06, applies to zSeries Processors and S/390 Processors. | This edition replaces SB10-7030-05 and -05a. A technical change to the text or illustration is indicated by a vertical line to the left of the change. ™ There may be a newer version of this document in PDF format available on Resource Link . Go to http://www.ibm.com/servers/resourcelink and click on Library on the Navigation bar. A newer version is indicated by a lower-case, alphabetic letter following the form number suffix (for example: 00a, 00b, 01a, 01b). © Copyright International Business Machines Corporation 2000, 2004. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Level 06a, November 2004 Contents Safety and Environmental Notices . vii Laser Safety Information . vii Laser Compliance . vii Environmental Notices . vii Product Recycling and Disposal . vii Refrigeration . vii Battery Return Program . vii IBM Cryptographic Adapter Card Return Program . viii Cable Warning . viii Preface . .ix Message Event Notification . .x Load Command Support . .x Hardware Message Refresh Command Support . .x Hardware Message Event Data . .x Activation Profile Support . .x Hardware Message Delete Command Support . .x Reset Clear Command Support . .xi || Security Log Event Support .
    [Show full text]