DOCSLIB.ORG

Download Program Files X86 Program Files

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

download program files x86 Program files. Program files may refer to any of the following: 1. When used as a singular noun, an application file or program file describes a file which stores the code to run a program. This type of file is commonly referred to as an executable file. When referring to more than one file, program files are all of the different files that allow a software program to run on your computer. Most programs have different types of files (e.g., DLL files, data files, etc.) used in conjunction with the executable file. Related program files pages. 2. Program Files is a folder first found in Microsoft Windows 95 and included in all later versions of Microsoft Windows that stores the software programs installed on the computer. How to open Program Files folder. By default, the Program Files folder is found on the root directory of the primary hard drive, with the C:\Program Files path. To open this folder on your computer, follow the steps below. Open File Explorer. Select This PC or Computer . Open the C: drive . Open the Program Files or Program Files (x86) folder. What programs should be in the Program Files folder? The Program Files folder and Program Files (x86) folders should contain the folders of the software programs that are installed on the computer. Can I delete Program Files or Program Files (x86)? No. While it may be possible to delete these folders they are both part of Windows and default locations where Windows installs your program files. If you delete either of these folders, all installed programs contained in the folder are also deleted. If you want to delete these folders to recover hard drive space, we suggest uninstalling programs and not deleting these folders. For help with uninstalling programs, see: How to uninstall software in Windows. What is the progra. With early versions of MS-DOS and Windows that only supported the 8.3 file naming format, the "Program Files" directory was too long. For backward compatibility, the "Programs Files" directory would appear as "progra. 1" (a maximum of eight characters). Today, because all operating systems support long files this directory name is rarely seen. Program Files translations. If you're using a version of Windows that isn't English, this directory may be translated into a different name, as shown in the examples below. AutoIt Downloads. You can download the main AutoIt package and other related scripting tools from this page. The current version of AutoIt has works on the following operating systems: Windows XP and Windows Server 2003 Windows Vista and Windows Server 2008/2008 R2 Windows 7 Windows 8 (desktop mode) Windows 10 (desktop mode) Current Versions. Here you can download AutoIt and related files. The AutoIt installer and executables have been digitally signed by AutoIt Consulting Ltd . If you get a Microsoft SmartScreen warning after downloading the installer please see the SmartScreen and AutoIt page for more details. AutoIt program files, documentation and examples. Aut2Exe – Script to executable converter. Convert your scripts into standalone .exe files! AutoItX – DLL/COM control. Add AutoIt features to your favorite programming and scripting languages! Also features a C# assembly and PowerShell CmdLets. Editor – A cut down version of the SciTE script editor package to get started. Download the package below for the full version! v3.2.12.1 – Last version to support Windows 95 and Windows NT 4.0. v3.3.8.1 – Last version to support Windows 2000. Script Editors. Programming and writing scripts in Notepad can be a pain. The AutoIt team has created a custom version of SciTe that has the following features and tools included: Syntax highlighting and code completion Code prettifier Syntax checker And much much more… The homepage for the AutoIt version of SciTe can be found here. Other Text Editors. If you don’t want to use SciTe or have your own favorite text editor then AutoIt comes with syntax files for the following editors “out of the box”: The syntax files for these are stored in the Extras \ Editors directory of the AutoIt installation. Why do I have two Program Files folders? Since 2005, Microsoft has offered both 32-bit and 64-bit versions of its Windows operating system. If you're running a 64-bit version of Microsoft Windows, there are two separate folders where your Program Files are kept: Program Files , which contains 64-bit programs and applications, and Program Files (x86) , which contains 32-bit programs and applications. So what's the difference? 64-bit applications are compiled specifically for use on a 64-bit computer. They make use of system features specific to a 64-bit architecture, and they access 64-bit versions of the Windows software libraries. 32-bit applications are legacy applications or modern programs compiled for 32-bit processing. 64-bit versions of Windows can still run these programs, though, using a compatibility layer called WOW64 (which stands for W indows32 o n W indows 64 ). Is it bad to run a 32-bit program on 64-bit Windows? Not at all. The WOW64 layer does a good job of emulating a 32-bit environment, and any performance loss is generally not noticeable. The emulated programs may actually have an advantage, because WOW64 can allocate the maximum amount of RAM (4 GB) to the application. On a real 32-bit system, some of that RAM would be allocated to the operating system kernel and other running programs. So, why are 64-bit and 32-bit programs kept in separate folders? Convenience: it's an easy way to tell them apart. It reduces the chances of a conflict if, for example, you install both a 32-bit and 64-bit version of the same program on one system. It increases the chance that older programs work properly, reducing the chance that they will interact with 64-bit software accidentally. Why is the 32-bit folder called "(x86)"? x86 is another way to refer to 32-bit processors. Originally, 16-bit processors — specifically, the 8086 and 8088 processor architectures — were referred to as "x86". This name was later extended to include the 32-bit 80386 and 80486 processor family. When 64-bit processors were introduced, they were referred to as x64 to distinguish them from the older processor lines. If I manually move programs from one folder to the other, will they still work? In theory, there's no reason why a 32-bit program won't work if you manually install it to your Program Files folder, and vice versa — 64-bit programs should work fine if you install them to the Program Files (x86) folder. It's a better idea to leave them right where Windows wants them, however. If you're having trouble locating a program in the Program Files folder, try looking in the Program Files (x86) folder as well. Download program files x86. If you’re using a Microsoft Windows operating system, then most likely you’ve come across the program files and program files (x86) folders on your hard drive. While they both seem to serve the same purpose, there is a slight difference, and that creates the question ‘Why?’ Definitions. A software identified as 32-bit, and so Program Files (x86) was automated to be its default directory for installation. Program Files. The ‘Program Files’ is the default name of a folder in a Microsoft Windows operating system. It is where applications that aren’t part of the system files (operating system applications and drivers) are usually installed. Most of the applications installed under the ‘Program Files’ automatically create a subdirectory (subfolder) for its application-specific resources. An accurate example would be ‘C:\Program Files\Adobe\’, the folder ‘Adobe’ here, is the said subdirectory created. In a standard form of installation in Windows, the directory is typically at %SystemDrive%\Program Files . The %SystemDrive% will reflect on which drive your operating system was installed, on (C:\, D:\, or E:\). Either you are using a 32-bit or a 64-bit Windows operating system, but the default name always will be ‘Program Files’. However, if you are using the 64-bit version, there’s an additional folder named ‘Program Files (x86), and this can be confusing. It is somewhat similar to your ‘Program Files’, but it contains installed applications with a different instruction set, the 32-bit. Program Files x86. As with the ‘Program Files’, the ‘Program Files (x86) is the default name of a folder in a Microsoft Windows operating system, where applications are usually installed. Only with ‘Program Files (x86)’, the folder name is only created when running on a 64-bit operating system. This means it does not, or should not exist when running a 32-bit operating system. This is because the ‘Program Files (x86)’ was created to simply provide you the location of your 32-bit software on your 64-bit operating system. One other folder, the ‘Program Files’ also exists, although it serves a different purpose, and that’s providing a location for your 64-bit software. To simplify, the ‘Program Files (x86) only exists on a 64-bit Windows operating system to separate the different architecture types of your installed applications. Now here’s what you should know: while most Windows users think that the ‘Program Files (x86)’ exists to easily identify which ones are 32-bit and 64-bit applications, it exists for a much bigger reason. With the way Windows manages their Dynamic Linked Libraries (the popular error- popping *DLL files), the separate ‘Program Files’ folders make it easy for redirecting requests from 32-bit applications to 32-bit DLLs.
Recommended publications
  • Xilinx XAPP545 Statistical Profiler for Embedded IBM Powerpc, Application Note

    Xilinx XAPP545 Statistical Profiler for Embedded IBM Powerpc, Application Note

    Product Not Recommended for New Designs Application Note: Virtex-II Pro R Statistical Profiler for Embedded IBM PowerPC XAPP545 (v1.0) September 15, 2004 Author: Njuguna Njoroge Summary This application note describes how to generate statistical profiling information from the IBM PowerPC 405D, which is embedded in some Virtex-II Pro™ FPGAs. Specifically, the application note details how to convert trace output files generated from the Agilent Technologies Trace Port Analyzer into a gprof (GNU profiler) readable format. The gprof tool is capable of generating a histogram of a program's functions and a call-graph table of those functions. Introduction Profiling allows a programmer to assess where a program is spending most of its time and how frequently functions are being called. With this information, a programmer can gain insight as to what optimizations to make. In some cases, a programmer can identify bugs that would be otherwise undetectable. Using the RISCWatch application is a first step in profiling a program. Nonetheless, manually mulling through approximately 350 MB (or 8 million cycles) of trace data to discern the run-time profile of the program is a fruitless endeavor. In fact, the designers of RISCWatch realized this, so they standardized the trace output format to enable post processing of the trace. The regular format of the trace files allows scripts to parse through the trace and convert it to the gprof format. By converting the trace files into the gprof format, the widespread use of gprof in the profiling community
  • Tanium™ Client Deployment Guide

    Tanium™ Client Deployment Guide

    Tanium™ Client Deployment Guide Version 6.0.314.XXXX February 05, 2018 The information in this document is subject to change without notice. Further, the information provided in this document is provided “as is” and is believed to be accurate, but is presented without any warranty of any kind, express or implied, except as provided in Tanium’s customer sales terms and conditions. Unless so otherwise provided, Tanium assumes no liability whatsoever, and in no event shall Tanium or its suppliers be liable for any indirect, special, consequential, or incidental damages, including without limitation, lost profits or loss or damage to data arising out of the use or inability to use this document, even if Tanium Inc. has been advised of the possibility of such damages. Any IP addresses used in this document are not intended to be actual addresses. Any examples, command display output, network topology diagrams, and other figures included in this document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Please visit https://docs.tanium.com for the most current Tanium product documentation. Tanium is a trademark of Tanium, Inc. in the U.S. and other countries. Third-party trademarks mentioned are the property of their respective owners. © 2018 Tanium Inc. All rights reserved. © 2018 Tanium Inc. All Rights Reserved Page 2 Table of contents Overview 8 What is the Tanium Client? 8 Registration 9 Client peering 9 File distribution 11 Prerequisites 14 Host system requirements 14 Admin account 15 Network connectivity and firewall 16 Host system security exceptions 16 Deployment options summary 18 Using the Tanium Client Deployment Tool 21 Methods 21 Before you begin 21 Install the Client Deployment Tool 23 Deploy the Tanium Client 25 Check for Tanium Client updates 32 Troubleshooting 33 Logs 34 Advanced settings 34 Deploying the Tanium Client to Windows endpoints 36 Step 1: Create the installer 36 Step 2: Execute the installer 37 © 2018 Tanium Inc.
  • An Efficient and Portable SIMD Algorithm for Charge/Current Deposition in Particle-In-Cell Codes✩

    An Efficient and Portable SIMD Algorithm for Charge/Current Deposition in Particle-In-Cell Codes✩

    Computer Physics Communications 210 (2017) 145–154 Contents lists available at ScienceDirect Computer Physics Communications journal homepage: www.elsevier.com/locate/cpc An efficient and portable SIMD algorithm for charge/current deposition in Particle-In-Cell codesI H. Vincenti a,b,∗, M. Lobet a, R. Lehe a, R. Sasanka c, J.-L. Vay a a Lawrence Berkeley National Laboratory, 1 Cyclotron Road, Berkeley, CA, USA b Lasers Interactions and Dynamics Laboratory (LIDyL), Commissariat À l'Energie Atomique, Gif-Sur-Yvette, France c Intel Corporation, OR, USA a r t i c l e i n f o a b s t r a c t Article history: In current computer architectures, data movement (from die to network) is by far the most energy Received 9 January 2016 consuming part of an algorithm (≈20 pJ=word on-die to ≈10,000 pJ/word on the network). To increase Received in revised form memory locality at the hardware level and reduce energy consumption related to data movement, 10 August 2016 future exascale computers tend to use many-core processors on each compute nodes that will have Accepted 19 August 2016 a reduced clock speed to allow for efficient cooling. To compensate for frequency decrease, machine Available online 19 September 2016 vendors are making use of long SIMD instruction registers that are able to process multiple data with one arithmetic operator in one clock cycle. SIMD register length is expected to double every four years. As Keywords: Particle-In-Cell method a consequence, Particle-In-Cell (PIC) codes will have to achieve good vectorization to fully take advantage OpenMP of these upcoming architectures.
  • Bapco® Eecomark V2 User Guide

    Bapco® Eecomark V2 User Guide

    BAPCo® EEcoMark v2 User Guide BAPCo is a U.S. Registered Trademark of the Business Applications Performance Corporation. EEcoMark is a U.S. Registered Trademark of the Business Applications Performance Corporation. Copyright © 2012 Business Applications Performance Corporation. All other brand and product names are trademarks or registered trademarks of their respective holders Contents 1.0 General .................................................................................................................................................... 4 1.1 Terminology ........................................................................................................................................ 4 2.0 Setup ....................................................................................................................................................... 5 2.1 Minimum System Requirements ........................................................................................................ 5 2.2 Hardware Setup .................................................................................................................................. 5 2.3 Software Setup .................................................................................................................................... 6 3.0 Configuration .......................................................................................................................................... 7 3.1 Guidelines ..........................................................................................................................................
  • Perceptive – Installing Imagenow Client on a Workstation

    Perceptive – Installing Imagenow Client on a Workstation

    Perceptive – Installing ImageNow client on a workstation Installing the ImageNow client on a workstation PURPOSE – Any computer that is going to be used to scan or import documents into Avatar will need ImageNow installed. Monterey is hosted by Netsmart and requires that VPN Checkpoint be established prior to initiating ‘Launch POS Scan’ from within Avatar. 1. Installing the ImageNow Client • Open the ImageNow Client Build 6.7.0 (Patch Build 3543) > right click and select “run as Administrator” even if you use your $ account. Avatar – After hitting “launch POS” it should auto connect to the Sunflower screen but if it does not. Error msg = “Failed to load image now client”, it could be that it was installed incorrectly. If installed incorrectly, Uninstall program from control panel and then reinstall the ImageNow Client 6.7.0 (Patch Build 3543).exe • On the Welcome to the Installation Wizard dialog, click Next. • Enable the following icons to be installed: o ImageNow Client Files o Demo Help o Administrator Help o Support for Viewing Non-graphic Data o ImageNow Printer (this is not selected by default) Note: the picture below does not have the ImageNow Printer selected. • On the License Agreement window, scroll down to the bottom of the License Agreement and accept the terms of the License Agreement to activate the Next button. • All sub features will be installed on the local hard drive, click Next. • On the Default connection Profile window, enter the following information and then click Next. o Name: Monterey PROD o Server ID: montereyimagenow.netsmartcloud.com o Server Type: Test o Port Number: 6000 The default information entered above creates the connection profiles below: Monterey Perceptive - Installing ImageNow v3 0(Installing the ImageNow Client onto a workstation) 1 | Page Plexus Foundations Perceptive – Installing ImageNow client on a workstation • Select the Next twice, and then Install.
  • PG-FP5 Flash Memory Programmer User's Manual

    PG-FP5 Flash Memory Programmer User's Manual

    User’s Manual User’s PG-FP5 Flash Memory Programmer User’s Manual All information contained in these materials, including products and product specifications, represents information on the product at the time of publication and is subject to change by Renesas Electronics Corp. without notice. Please review the latest information published by Renesas Electronics Corp. through various means, including the Renesas Electronics Corp. website (http://www.renesas.com). www.renesas.com Rev. 5.00 Dec, 2011 Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples. You are fully responsible for the incorporation of these circuits, software, and information in the design of your equipment.
  • Framework Visualizing of 32-Bit System Updates Response to Use

    Framework Visualizing of 32-Bit System Updates Response to Use

    al and Com tic pu re ta o t e io h n T a f l o S l c a i Journal of Theoretical & Computational e n n r c u e o J ISSN: 2376-130X Science Short Communication Framework Visualizing of 32-Bit System Updates Response to use 64-Bit Apps Operations Implications Based on System Troubles and Apps Updates and Errors/Framework Visualizing of 32-Bit System Updates Issues with use 64-Bit Apps Updating and Operations Al Hashami Z*, CS Instructor, Oman-Muscat SHORT COMMUNICATION AIMS AND OBJECTIVES The development of the systems versions is dramatic based on The aims of this research is to identify the implications of the buses lanes, memory and registers. As known in the updating operating system especially if it 32-bit under use of 64- computing the general rule that if the RAM is under 4GB, don’t bit applications operations a trouble face the users in case of that need a 64-bit CPU but if the RAM more than 4GB it need. users use many 64-bit applications. It is Identification of 32-bit Some users find that a 32-bit is enough memory and good system updating troubles under operations and updating of 64- performance, in contrast to huge size applications that need bit applications. Also identify of updating implications of 64-bit more memory and fast processing should use faster processor. software that working under 32-bit system implications. Some applications used for processing images, videos and 3D Usual users face many troubles in case of updates of systems rendering utilities need faster CPU like 64-bit system.
  • Assembly Language Programming

    Assembly Language Programming

    Experiment 3 Assembly Language Programming Every computer, no matter how simple or complex, has a microprocessor that manages the computer's arithmetical, logical and control activities. A computer program is a collection of numbers stored in memory in the form of ones and zeros. CPU reads these numbers one at a time, decodes them and perform the required action. We term these numbers as machine language. Although machine language instructions make perfect sense to computer but humans cannot comprehend them. A long time ago, someone came up with the idea that computer programs could be written using words instead of numbers and a new language of mnemonics was de- veloped and named as assembly language. An assembly language is a low-level programming language and there is a very strong (generally one-to-one) correspondence between the language and the architecture's machine code instructions. We know that computer cannot interpret assembly language instructions. A program should be developed that performs the task of translating the assembly language instructions to ma- chine language. A computer program that translates the source code written with mnemonics into the executable machine language instructions is called an assembler. The input of an assembler is a source code and its output is an executable object code. Assembly language programs are not portable because assembly language instructions are specific to a particular computer architecture. Similarly, a different assembler is required to make an object code for each platform. The ARM Architecture The ARM is a Reduced Instruction Set Computer(RISC) with a relatively simple implementation of a load/store architecture, i.e.
  • Input and Output (I/O) in 8086 Assembly Language Each Microprocessor Provides Instructions for I/O with the Devices That Are

    Input and Output (I/O) in 8086 Assembly Language Each Microprocessor Provides Instructions for I/O with the Devices That Are

    Input and Output (I/O) in 8086 Assembly Language Each microprocessor provides instructions for I/O with the devices that are attached to it, e.g. the keyboard and screen. The 8086 provides the instructions in for input and out for output. These instructions are quite complicated to use, so we usually use the operating system to do I/O for us instead. The operating system provides a range of I/O subprograms, in much the same way as there is an extensive library of subprograms available to the C programmer. In C, to perform an I/O operation, we call a subprogram using its name to indicate its operations, e.g. putchar(), printf(), getchar(). In addition we may pass a parameter to the subprogram, for example the character to be displayed by putchar() is passed as a parameter e.g. putchar(c). In assembly language we must have a mechanism to call the operating system to carry out I/O. In addition we must be able to tell the operating system what kind of I/O operation we wish to carry out, e.g. to read a character from the keyboard, to display a character or string on the screen or to do disk I/O. Finally, we must have a means of passing parameters to the operating subprogram. Introduction to 8086 Assembly Language Programming Section 2 1 In 8086 assembly language, we do not call operating system subprograms by name, instead, we use a software interrupt mechanism An interrupt signals the processor to suspend its current activity (i.e.
  • TO 53 Field Inspection Tool Users Guide

    TO 53 Field Inspection Tool Users Guide

    Appendix B – Troubleshooting This page is intentionally left blank. National Flood Mitigation Data Collection Tool User’s Guide Main Menu Function Problem – The installation seems to have been successful, but when I click one of the functions from the main menu, nothing happens. Solution – While the NT uses common Microsoft Library routines, sometimes the reference files are not properly installed or registered on the user’s machine. Below is a list of all of the reference files used by the NT that might need to be installed or registered, and instructions on how to register them. Files C:\Windows\System32\ (Note: the Windows folder may be named WINNT) ComDLG32.OCX MsComm32.OCX OlePrn.DLL PlugIn.OCX ScrRun.DLL StdOle2.TLB C:\Program Files\NFMDCT\ MSADOX.DLL C:\Program Files\Common Files\Microsoft Shared\DAO\ DAO360.DLL C:\Program Files\Common Files\Microsoft Shared\Officexx\ (xx is either 10 or 11 based on the version of Microsoft Office you are using.) MSO.DLL C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\ VBE6.DLL C:\Program Files\Common Files\System\ADO\ MSADO15.DLL MSADOR15.DLL C:\Program Files\Microsoft Office\Officexx\ (xx is either 10 or 11 based on the version of Microsoft Office you are using.) MSACC.OLB Instructions 1. Ensure all of the files listed above are located on your PC in the appropriate directories. If any of the above noted files is missing, copy it from the support folder on the installation CD to the appropriate directory. 2. Register the files above ending in DLL or OCX. To register a DLL or OCX file: B-1 May 2005 National Flood Mitigation Data Collection Tool User’s Guide A.
  • ARM Developer Suite Compilers and Libraries Guide

    ARM Developer Suite Compilers and Libraries Guide

    ARM® Developer Suite Version 1.2 Compilers and Libraries Guide Copyright © 1999-2001 ARM Limited. All rights reserved. ARM DUI 0067D ARM Developer Suite Compilers and Libraries Guide Copyright © 1999-2001 ARM Limited. All rights reserved. Release Information The following changes have been made to this book. Change History Date Issue Change October 1999 A Release 1.0 March 2000 B Release 1.0.1 November 2000 C Release 1.1 November 2001 D Release 1.2 Proprietary Notice Words and logos marked with ® or ™ are registered trademarks or trademarks owned by ARM Limited. Other brands and names mentioned herein may be the trademarks of their respective owners. Neither the whole nor any part of the information contained in, or the product described in, this document may be adapted or reproduced in any material form except with the prior written permission of the copyright holder. The product described in this document is subject to continuous developments and improvements. All particulars of the product and its use contained in this document are given by ARM in good faith. However, all warranties implied or expressed, including but not limited to implied warranties of merchantability, or fitness for purpose, are excluded. This document is intended only to assist the reader in the use of the product. ARM Limited shall not be liable for any loss or damage arising from the use of any information in this document, or any error or omission in such information, or any incorrect use of the product. ii Copyright © 1999-2001 ARM Limited. All rights reserved. ARM DUI 0067D Contents ARM Developer Suite Compilers and Libraries Guide Preface About this book ...........................................................................................
  • Lab 1: Assembly Language Tools and Data Representation

    Lab 1: Assembly Language Tools and Data Representation

    COE 205 Lab Manual Lab 1: Assembly Language Tools - page 1 Lab 1: Assembly Language Tools and Data Representation Contents 1.1. Introduction to Assembly Language Tools 1.2. Installing MASM 6.15 1.3. Displaying a Welcome Statement 1.4. Installing the Windows Debugger 1.5. Using the Windows Debugger 1.6. Data Representation 1.1 Introduction to Assembly Language Tools Software tools are used for editing, assembling, linking, and debugging assembly language programming. You will need an assembler, a linker, a debugger, and an editor. These tools are briefly explained below. 1.1.1 Assembler An assembler is a program that converts source-code programs written in assembly language into object files in machine language. Popular assemblers have emerged over the years for the Intel family of processors. These include MASM (Macro Assembler from Microsoft), TASM (Turbo Assembler from Borland), NASM (Netwide Assembler for both Windows and Linux), and GNU assembler distributed by the free software foundation. We will use MASM 6.15. 1.1.2 Linker A linker is a program that combines your program's object file created by the assembler with other object files and link libraries, and produces a single executable program. You need a linker utility to produce executable files. Two linkers: LINK.EXE and LINK32.EXE are provided with the MASM 6.15 distribution to link 16-bit real-address mode and 32-bit protected-address mode programs respectively. We will also use a link library for basic input-output. Two versions of the link library exist that were originally developed by Kip Irvine.