DOCSLIB.ORG

Inside OS/2 Warp Server, Volume 1: Exploring the Core Components

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Inside OS/2 Warp Server, Volume 1: Exploring the Core Components SG24-4602-00 Inside OS/2 Warp Server, Volume 1: Exploring the Core Components March 1996 SG24-4602-00 IBML Inside OS/2 Warp Server, Volume 1: Exploring the Core Components March 1996 Take Note! Before using this information and the product it supports, be sure to read the general information under “Special Notices” on page xix. First Edition (March 1996) This edition applies to IBM OS/2 Warp Server Version 4. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. An ITSO Technical Bulletin Evaluation Form for reader's feedback appears facing Chapter 1. If the form has been removed, comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JN9B Building 045 Internal Zip 2834 11400 Burnet Road Austin, Texas 78758-3493 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1996. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Abstract This redbook provides information about the key components of the IBM OS/2 Warp Server product. Following on the heels of OS/2 Warp Connect, the integrated OS/2 client operating system, OS/2 Warp Server combines the refreshed OS/2 Warp and LAN Server with a wealth of functional enhancements in TCP/IP, Remote Access Services (LAN Distance), systems management (SystemView), backup and recovery and advanced print function. Each service or function can be selectively installed, allowing users to customize OS/2 Warp Server to meet their specific needs. This redbook describes hints and workarounds for various installation scenarios. The major enhancement to TCP/IP is the dynamic IP introduction. OS/2 Warp Server is the first product which has implemented Dynamic DNS (Domain Name System) together with DHCP (Dynamic Host Control Protocol). This redbook discusses the detail of this protocol and implementation on server and clients. Remote Access Services is equivalent to the existing LAN Distance connection server product but with several enhancements. This redbook describes not only the enhancements but also the basics of remote access services. This redbook intends to provide guidance on planning, installation and customization of the core components of OS/2 Warp Server. The components discussedinthisredbookaretheFileandPrintSharingfunctionwithOS/2and DOS/Windows/Windows 95 client, Adapter and Protocol Services, TCP/IP Services and Remote Access Services. For information on SystemView in OS/2 Warp Server, Backup and Recovery, and Advanced Print Services see the upcoming redbook, Inside OS/2 Warp Server, Volume 2: Using SystemView, Backup/Recovery and Advanced Print which is planned to be available in May/1996. Readers are assumed to have some knowledge of OS/2 Warp, IBM OS/2 LAN Server 4.0 and basics of TCP/IP protocol and products. (386 pages) Copyright IBM Corp. 1996 iii iv Inside OS/2 Warp Server, Volume 1 Contents Abstract .......................................... iii Special Notices ..................................... xix Preface ......................................... xxi How This Document is Organized ......................... xxi Related Publications ................................. xxii International Technical Support Organization Publications ........... xxii How Customers Can Get Redbooks and Other ITSO Deliverables ..... xxiii How IBM Employees Can Get Redbooks and ITSO Deliverables ....... xxiv Acknowledgments ................................... xxv Chapter 1. OS/2 Warp Server Version 4 Product Information .......... 1 1.1 A Powerful Server ................................. 1 1.2 For Businesses of All Sizes ............................ 2 1.3 Broad Client Support ................................ 2 1.4 Enhanced TCP/IP Connectivity .......................... 2 1.5 Sophisticated Systems Management Made Easy ............... 3 1.6 Carefree System Backup and Recovery .................... 4 1.7 Remote Access ................................... 4 1.8 Advanced Print Functionality ........................... 5 1.9 Two Versions of OS/2 Warp Server ....................... 5 Chapter 2. File and Print Sharing Services ..................... 7 2.1 Overview ....................................... 7 2.2 OS/2 Warp Server Domain Concept ....................... 10 2.3 Installation ...................................... 10 Installation Considerations ............................. 13 2.4 Configuration .................................... 13 2.5 OS/2 Warp Server Tuning Assistant ....................... 15 Running the Tuning Assistant on a Requester ................. 18 2.6 Sharing Resources with the Administration GUI ............... 19 Sharing Files with the Administration GUI .................... 20 Sharing Printers with the Administration GUI .................. 23 Support for Thousands of Aliases ......................... 24 2.7 Other Methods of Sharing Resources ...................... 25 Sharing Resources from the Desktop ....................... 25 Sharing Resources from the Command Line .................. 27 Sharing Resources from the Current Shares Window ............. 27 2.8 Preparing the Server for Client Installation .................. 28 2.9 Removing File and Print Sharing Services ................... 32 2.10 OS/2 Warp Server Gateway Services ..................... 32 Overview and Concepts ............................... 33 NetWare File and Print Gateway Services .................... 33 TCP/IP Services Interoperability .......................... 43 Chapter 3. File and Print Clients ........................... 49 3.1 What is a Requester? ............................... 50 3.2 OS/2 File and Print Client (OS/2 LAN Requester) ............... 50 Installation ....................................... 51 OS/2 Client Installation Considerations ...................... 57 Copyright IBM Corp. 1996 v Graphical User Interface .............................. 60 Connecting to Network Resources from the OS/2 File and Print Client ... 62 3.3 DOS File and Print Client (DOS LAN Services) ................ 64 New Features ..................................... 65 Installation ....................................... 66 Reduced Memory Requirements .......................... 77 Selecting the Redirector ............................... 79 Configuration ..................................... 80 Graphical User Interface .............................. 80 3.4 Windows File and Print Client (DOS LAN Services Windows Support) .. 81 Installation ....................................... 82 Configuration ..................................... 83 Customizing your DOS LAN Services Windows GUI .............. 83 DOS LAN Services Windows Shared Applications ............... 86 DOS LAN Services General Hints and Tips ................... 86 3.5 Windows 95 Client (DOS LAN Services for Windows 95) ........... 87 Installation ....................................... 88 Graphical User Interface .............................. 90 Accessing LAN Server Functions ......................... 90 The Windows 95 Network Neighborhood ..................... 91 Sharing Restrictions in non-NT Domains ..................... 91 3.6 Installing and Running DOS LAN Services on OS/2 ............. 91 Installing DOS LAN Services on OS/2 ....................... 92 3.7 Connecting to Network Resources from DOS LAN Services ........ 93 3.8 DOS LAN Services Logon Process ....................... 95 Local Logon ...................................... 96 3.9 Sharing Requester Resources with the Peer Service ............ 96 User Level Security ................................. 98 Peer Administration Considerations ....................... 100 Peer User Level Security APIs .......................... 101 3.10 Performance Tuning .............................. 103 3.11 DOS LAN Services Module Descriptions .................. 104 3.12 DOS LAN Services Common Configuration Scenarios .......... 105 Other Protocol .................................... 106 802.2 LAN Transport ................................ 106 TCPBEUI (Real-Mode) LAN Transport ...................... 106 TCPBEUI (Real-Mode) and IBM NetBEUI .................... 106 TCPBEUI (Windows Protect-Mode) LAN Transport .............. 107 TCPBEUI (Windows Protect-Mode) and IBM NetBEUI ............ 107 TCPBEUI Configuration .............................. 107 DOS LAN Services TCPBEUI Utilities ...................... 107 3.13 NETWORK.INI Configuration File Parameters ............... 110 NETWORK.INI Network Parameters ....................... 110 NETWORK.INI Messenger Parameters ..................... 113 NETWORK.INI Netpopup Parameter ....................... 113 NETWORK.INI Peer Parameters ......................... 113 Sample NETWORK.INI File ............................ 116 3.14 Password Coordination ............................ 116 Security Considerations .............................. 118 Installation ...................................... 119 Configuration .................................... 119 Using Password Coordination .......................... 122 Chapter 4. Adapter and Protocol Services .................... 125 4.1 Overview of Adapter and Protocol Services ................. 125 vi Inside OS/2 Warp Server, Volume 1 New Features ...................................
Load more

Recommended publications
  • Configuring DNS
    Configuring DNS The Domain Name System (DNS) is a distributed database in which you can map hostnames to IP addresses through the DNS protocol from a DNS server. Each unique IP address can have an associated hostname. The Cisco IOS software maintains a cache of hostname-to-address mappings for use by the connect, telnet, and ping EXEC commands, and related Telnet support operations. This cache speeds the process of converting names to addresses. Note You can specify IPv4 and IPv6 addresses while performing various tasks in this feature. The resource record type AAAA is used to map a domain name to an IPv6 address. The IP6.ARPA domain is defined to look up a record given an IPv6 address. • Finding Feature Information, page 1 • Prerequisites for Configuring DNS, page 2 • Information About DNS, page 2 • How to Configure DNS, page 4 • Configuration Examples for DNS, page 13 • Additional References, page 14 • Feature Information for DNS, page 15 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
    [Show full text]
  • Testing-Prepare.Pdf
    Prepare Update your system so you can connect to the staging server to perform testing – required for all users EXCEPT “new users.” If you are not certain how to complete the steps listed in Prepare, you should abort testing efforts. Breaking your “hosts” file may prevent applications that use the Internet, such as your Web browser, from functioning properly. Also note that this will make non-CMS www.ndsu.edu sites unavailable while you are testing until you perform the clean-up steps on page 11 of this packet. Windows XP 1. Close all browser windows 2. Open My Computer 3. Browse to Local Disk (C:) > WINDOWS > system32 > drivers > etc 4. Double-click hosts 5. In the Open With dialog window, select Notepad and click OK 6. At the end of the file, AFTER 127.0.0.1 localhost, add a new line with the following entry 134.129.111.243 www.ndsu.edu workspaces.ndsu.edu An example of what the file should look like follows these directions Note that if you usually sign in somewhere other than “workspaces.ndsu.edu” you should add that address to the end of this list, for example like 134.129.111.243 www.ndsu.edu workspaces.ndsu.edu english.ndsu.edu 7. Save the file Remember to complete the clean-up steps on page 11 of this packet when you are done testing Windows Vista 1. Close all browser windows 2. Click the Start menu > All Programs > Accessories > and RIGHT-CLICK Notepad 3. Choose Run as administrator 4. In the User Account Control dialog, click Continue or if you are not an administrator, provide a password for an administrator account and click OK 5.
    [Show full text]
  • With ANSIBLE Sessions
    SANOG32 bdNOG9 02-10 August, 2018 Dhaka, Bangladesh NETWORK Imtiaz Rahman AUTOMATION (NetDevOps) SBAC Bank Limited [email protected] https://imtiazrahman.com with ANSIBLE Sessions • Session 1: o 14:30 PM – 16:00 PM (Theory with example) • Session 2: o 16:30 PM – 18:00 PM (Configuration and hands on LAB) Today’s Talk 1. Devops/NetDevOps ? 6. Ansible Language Basics 2. Why automation ? 7. Ansible encryption decryption 3. Tools for automation 8. How to run 4. Why Ansible ? 9. Demo 5. Ansible introduction 10. Configuration & Hands on LAB DevOps >devops ? DevOps >devops != DevOps DevOps integrates developers and operations teams In order to improve collaboration and productivity by automating infrastructure, automating workflows and continuously measuring application performance Dev + Ops = DevOps NetDevOps NetDevOps = Networking + DevOps infrastructure as code Why automation ? Avoid Avoid repeated Faster Identical typographical task deployment configuration error (Typos) Tools for automation What is ANSIBLE? • Open source IT automation tool • Red hat Enterprise Linux, CentOS, Debian, OS X, Ubuntu etc. • Need python Why ANSIBLE? • Simple • Push model • Agentless Why ANSIBLE? Puppet SSL Puppet Puppet master Client/agent Ansible Agentless Controller SSH node Managed with ansible node’s How it works 1 2 3 4 Run playbook SSH SSH Laptop/Desktop/ Copy python Run Module Delete Module Server module on device from device Return result 5 What can be done?? • Configuration Management • Provisioning VMs or IaaS instances • Software Testing • Continuous
    [Show full text]
  • Kontron / ICS Advent SB586P(V) Manual (Pdf)
    Full-service, independent repair center -~ ARTISAN® with experienced engineers and technicians on staff. TECHNOLOGY GROUP ~I We buy your excess, underutilized, and idle equipment along with credit for buybacks and trade-ins. Custom engineering Your definitive source so your equipment works exactly as you specify. for quality pre-owned • Critical and expedited services • Leasing / Rentals/ Demos equipment. • In stock/ Ready-to-ship • !TAR-certified secure asset solutions Expert team I Trust guarantee I 100% satisfaction Artisan Technology Group (217) 352-9330 | [email protected] | artisantg.com All trademarks, brand names, and brands appearing herein are the property o f their respective owners. Find the Kontron / ICS Advent SB586PV at our website: Click HERE Model SB586P(V) Product Manual MANUAL NUMBER : 00431-027-3C Page - ii FOREWORD This product manual provides information to install, operate and or program the referenced product(s) manufactured or distributed by ICS Advent. The following pages contain information regarding the war- ranty and repair policies. Technical assistance is available at: 800-480-0044. Manual Errors, Omissions and Bugs: A "Bug Sheet" is included as the last page of this manual. Please use the "Bug Sheet" if you experience any problems with the manual that requires correction. The information in this document is provided for reference only. ICS Advent does not assume any liability arising from the application or use of the information or products described herein. This document may contain or reference information and products protected by copyrights or patents and does not convey any license under the patent rights of ICS Advent, nor the rights of others.
    [Show full text]
  • Cisco IOS Easy IP
    WHITE PAPER Cisco IOS Easy IP Summary • Conserve registered IP addresses Cisco IOS Easy IP enables transparent and dynamic IP • Maximize IP address manageability address allocation for hosts in remote environments via Remote networks have variable numbers of end systems that DHCP, reduces router configuration tasks via dynamic PPP/ need access to the Internet. Hence, ISPs are interested in IPCP address negotiation, conserves IP addresses via PAT, allocating just one IP address to each remote LAN. and minimizes Internet access costs for remote offices. In enterprise networks where telecommuter populations Cisco IOS Easy IP is a combination of the following are growing extremely fast, network administrators need functionality: solutions that ease configuration and management of remote • Port Address Translation (PAT), a subset of Network routers and provide conservation and dynamic allocation of Address Translation (NAT) IP addresses within their networks. Such solutions are • Dynamic PPP/IPCP WAN interface IP address negotiation especially important when network administrators • Cisco IOS DHCP Server implement large dialup user pools where ISDN plays a major This paper describes the features and benefits of Cisco IOS role. Easy IP, provides a technical discussion of how it works, As part of Cisco IOS software, the premier platform that including details on the Cisco IOS DHCP Server, and includes delivers network services and enables networked availability, packaging, and platform support information. applications, Cisco IOS Easy IP is a scalability/connectivity service that provides solutions for each of these challenges. It Introduction provides cost savings, scalability, conservation of registered Exponential growth in the remote access router market has IP addresses, and eases router deployment by nontechnical created new challenges for Internet service providers (ISPs) users.
    [Show full text]
  • KUNCI JAWABAN CHAPTER 2 CCNA-RS-ITN-SIM-1 Configuring a Network Operating System Chapter 2 Exam
    KUNCI JAWABAN CHAPTER 2 CCNA-RS-ITN-SIM-1 Configuring a Network Operating System Chapter 2 Exam Mandar 3 Oktober 2016 CCNA-RS-ITN-SIM-Ganjil-2016 MANDAR 3 OKTOBER 2016 KUNCI JAWABAN CHAPTER 2 1. Which two features are characteristics of flash memory? (Choose two.) Flash provides nonvolatile storage. The contents of flash may be overwritten. 2. A network administrator is planning an IOS upgrade on several of the head office routers and switches. Which three questions must be answered before continuing with the IOS selection and upgrade? (Choose three.) What models of routers and switches require upgrades? Do the routers and switches have enough RAM and flash memory for the proposed IOS versions? What features are required for the devices? 3. Which procedure is used to access a Cisco 2960 switch when performing an initial configuration in a secure environment? Use the console port to locally access the switch from a serial or USB interface of the PC. 4. A network administrator needs to keep the user ID, password, and session contents private when establishing remote CLI connectivity with a switch to manage it. Which access method should be chosen? SSH 5. A router has a valid operating system and a configuration stored in NVRAM. When the router boots up, which mode will display? user EXEC mode 6. Which two functions are provided to users by the context-sensitive help feature of the Cisco IOS CLI? (Choose two.) displaying a list of all available commands within the current mode determining which option, keyword, or argument is available for the entered command 7.
    [Show full text]
  • SOS Internals
    Understanding a Simple Operating System SOS is a Simple Operating System designed for the 32-bit x86 architecture. Its purpose is to understand basic concepts of operating system design. These notes are meant to help you recall the class discussions. Chapter 1 : Starting Up SOS 3 Registers in the IA-32 x86 Architecture BIOS (Basic Input/Ouput System) Routines Real Mode Addressing Organization of SOS on Disk and Memory Master Boot Record SOS Startup A20 Line 32-bit Protected Mode Addressing Privilege Level Global Descriptor Table (GDT) More on Privilege Levels The GDT Setup Enabling Protected Mode Calling main() Chapter 2 : SOS Initializations 10 In main() Disk Initialization Display Initialization Setting Up Interrupt Handlers Interrupt Descriptor Table (IDT) A Default Interrupt Handler Load IDT The Programmable Interrupt Controller (PIC) The Keyboard Interrupt Handler Starting the Console Putting It All Together Chapter 3: SOS1 – Single-tasking SOS 16 Running User Programs GDT Entries Default Exception Handler User Programs Executable Format System Calls Creating User Programs The run Command Understanding a Simple Operating System The DUMB Memory Manager Program Address Space Process Control Block Switching to a User Program Kernel-Mode Stack Chapter 4 : SOS2 – Multi-tasking SOS 24 Running Multiple User Programs NAÏVE Memory Manager Programmable Interval Timer (PIT) Process States Timer Interrupt Handler Sleep System Call The run Command Process Queue The Scheduler The Complete Picture ps Command Chapter 5 : SOS3 – Paging in SOS 31
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • The Arcos Network Operating System
    AT-A-GLANCE The ArcOS TM Network Operating System History has repeatedly proven that large industries transition from The ArcOS Advantage vertical integration to best-in-class horizontal segmentation as the urgent business need for innovation outstrips the ability/intent of the incumbents to deliver. The networking industry is in exactly such Agile situation, but it lags the compute and, to a large extent, the storage tiers in terms of this transition. Network operations teams are hampered by inflexible, proprietary systems that are expensive to build, operate, Automated processes accelerate and manage. This model does not fit well into today’s digital business and streamline network expectations of a more agile and innovation-friendly smart infrastructure. provisioning, operations, and deployment. Built-in YANG/ Recently, there has been an explosion of networking merchant silicon OpenConfig support simplifies options in the market that continue to redefine what is possible. integration into existing Additionally, the networking hardware ecosystem continues to evolve frameworks. with a proliferation of readily available leading-edge network platforms from multiple ODMs. But the fundamental problem has been the lack of a modern, scalable, and viable software network operating system that enables the transition from a proprietary, closed approach to an open integration approach. Elastic Arrcus addresses this problem by delivering ArcOS, an independent, open, Linux-based network operating system, as a high-quality alternative Modular software on white box/ to vertically integrated OEMs, to meet and exceed the modern smart brite box network hardware network infrastructure requirements. maximizes flexibility in building a scale-out architecture for a variety of network environments A Modern Network Operating System for the Data Center, (physical, virtual, cloud).
    [Show full text]
  • The Bootstrap the Where Are Wenow?
    Dedicated Operating System March2011 Prof. Dr.Antônio AugustoFröhlich http://www.lisha.ufsc.br/Guto Getting ready for the OS for the ready Getting [email protected] LISHA/UFSC The Boot: The March 2011 (http://www.lisha.ufsc.br) 1 Dedicated Operating System March2011 ● ● ● BIOSgot the system ready for BIOSbrought the system on ● Lots of “jmp” so far, no calls, why? ● First instruction fetched ● initializedBIOS a complex architecture Where the stack?Where is 0x7c00 BIST, POST, hooks The Bootstrap Where are we now? we are Where (http://www.lisha.ufsc.br) =>Today class 2 EPOS Bootstrap: m src/boot/pc_boot.S e t ; CONSTANTS s ;============================================================ y ; PHYSICAL MEMORY MAP S ; 0x0000 0000 -+-----------------------+ BOOT_IDT ; | IDT (4 K) | g ; 0x0000 1000 -+-----------------------+ BOOT_GDT ; | GDT (4 K) | n i ; 0x0000 2000 -+-----------------------+ t ; : : a ; | BOOT STACK (23 K) | r ; 0x0000 7c00 -+-----------------------+ BOOTSTRAP_STACK e ; | BOOT CODE (512 b) | BOOTSTRAP_CODE p ; 0x0000 7e00 -+-----------------------+ ; | RESERVED (512 b) | O ; 0x0000 8000 -+-----------------------+ DISK_IMAGE ; | DISK IMAGE (608 K) | d ; : : e ; | | t ; 0x000a 0000 -+-----------------------+ a ; | UNUSED (384K) | c ; : : i ; | | d ; 0x000f f000 -+-----------------------+ e D March 2011 (http://www.lisha.ufsc.br) 3 EPOS Bootstrap: Notes m e t s Code to be ran at real mode (16 bits) y S Interrupts (IDT) ● g At real mode, always at 0x0000 n ● i At protected mode, anywhere (IDTR) t a Segmentation (GDT) r ● e Always
    [Show full text]
  • 1. Introduction
    Network Operating Systems Partha Dasgupta Department of Computer Science and Engineering Arizona State University Tempe AZ 85287-5406 USA [email protected] [Note: Written in 1997, Appeared in Encyclopedia of Electrical Engineering] 1. Introduction Network Operating Systems extend the facilities and services provided by computer operating systems to support a set of computers, connected by a network. The environment managed by a network operating system consists of an interconnected group of machines that are loosely connected. By loosely connected, we mean that such computers possess no hardware connections at the CPU – memory bus level, but are connected by external interfaces that run under the control of software. Each computer in this group run an autonomous operating system, yet cooperate with each other to allow a variety of facilities including file sharing, data sharing, peripheral sharing, remote execution and cooperative computation. Network operating systems are autonomous operating systems that support such cooperation. The group of machines comprising the management domain of the network operating system is called a distributed system. A close cousin of the network operating system is the distributed operating system. A distributed operating system is an extension of the network operating system that supports even higher levels of cooperation and integration of the machines on the network (features include task migration, dynamic resource location, and so on) (1,2). An operating system is low-level software controlling the inner workings of a machine. Typical functions performed by an operating system include managing the CPU among many concurrently executing tasks, managing memory allocation to the tasks, handling of input and output and controlling all the peripherals.
    [Show full text]
  • Computing :: Operatingsystems :: DOS Beyond 640K 2Nd
    DOS® Beyond 640K 2nd Edition DOS® Beyond 640K 2nd Edition James S. Forney Windcrest®/McGraw-Hill SECOND EDITION FIRST PRINTING © 1992 by James S. Forney. First Edition © 1989 by James S. Forney. Published by Windcrest Books, an imprint of TAB Books. TAB Books is a division of McGraw-Hill, Inc. The name "Windcrest" is a registered trademark of TAB Books. Printed in the United States of America. All rights reserved. The publisher takes no responsibility for the use of any of the materials or methods described in this book, nor for the products thereof. Library of Congress Cataloging-in-Publication Data Forney, James. DOS beyond 640K / by James S. Forney. - 2nd ed. p. cm. Rev. ed. of: MS-DOS beyond 640K. Includes index. ISBN 0-8306-9717-9 ISBN 0-8306-3744-3 (pbk.) 1. Operating systems (Computers) 2. MS-DOS (Computer file) 3. PC -DOS (Computer file) 4. Random access memory. I. Forney, James. MS-DOS beyond 640K. II. Title. QA76.76.063F644 1991 0058.4'3--dc20 91-24629 CIP TAB Books offers software for sale. For information and a catalog, please contact TAB Software Department, Blue Ridge Summit, PA 17294-0850. Acquisitions Editor: Stephen Moore Production: Katherine G. Brown Book Design: Jaclyn J. Boone Cover: Sandra Blair Design, Harrisburg, PA WTl To Sheila Contents Preface Xlll Acknowledgments xv Introduction xvii Chapter 1. The unexpanded system 1 Physical limits of the system 2 The physical machine 5 Life beyond 640K 7 The operating system 10 Evolution: a two-way street 12 What else is in there? 13 Out of hiding 13 Chapter 2.
    [Show full text]