DOCSLIB.ORG

Measuring and Reporting Temperature

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Measuring and Reporting Temperature How to Monitor and Report Temperature with a USB Sensor by John Chamberlain ThermoHID is a small Windows program written by Steve Timms (http://www.thermohid.co.uk) to interface with the simple and inexpensive TEMPer devices. ThermoHID allows one to use the temperature reading capabilities of the TEMPer devices for real- time monitoring, recording, and even alarm-generating, and upload the results to a web server for monitoring from anywhere. Although setting up everything can be rather intimidating, once you get it running, it works reliably and transparently while you use your computer for your normal work. Below I describe the steps to run invisibly in the background, and upload the resulting report to a web server. See Change the Chart below for the routine seasonal change to the chart scale. Required Steps • Step 1. Connect the TEMPer device (via USB cable) to a continuously running, internet connected Windows computer. • Step 2. Run ThermoHID manually to set up the program parameters and resulting graph appearance. (Optional: Install and use TeeChart Office to configure the graph, saved in a configuration file, e.g., default.tee.) • Step 3. To enable ThermoHID to run in the background in Windows: a) Create a secondary Windows user, and b) Create a scheduled task to run the ThermoHID program, assigned to our secondary user. Advantage: This will run the program in the background anytime the computer is ON (not require someone to be logged on). • Step 4. Finally, to share the data, upload the output of the reporting program to a convenient server at regular intervals. ThermoHID includes a ftp service, but I prefer a more secure file transfer program also run as a scheduled task. The first two steps above are covered well in the TEMPer and ThermoHID documentation. So, here’s a little more detail for the latter two steps. Step 3. Run ThermoHID in the Background We want the ThermoHID to run invisibly day and night. To accomplish that we 1) install everything to run on an Internet-connected computer that can be left on 24/7, and 2) run it (start/restart) as a scheduled task with a secondary user (which avoids any interference with primary users using the computer, e.g., during office hours). 1. Running 24/7. In Windows Control Panel, Power Options, Change Plan Settings (for the currently selected power plan), Put the computer to sleep: Choose “Never.” There are several — 1 — ways to get to this setting, but the goal is for the CPU of the computer to NEVER go to sleep on its own. Obviously, YOU can still shut down/power down the computer manually. Power Failures. If you want the computer to recover itself after a power failure, you probably must modify the BIOS settings. In the BIOS in Advanced Power Management (APM) look for an option like “After AC power loss: [always OFF| always ON| last state].” Choose “Always ON”, “Save and Exit” the BIOS settings, which will restart the system. 2. Run ThermoHID on Startup. I originally had ThermoHID running as a Windows Service, but that was rather tedious and arcane to set up. A somewhat easier way is to create a secondary local Windows user (e.g., “ThermoHID” with a simple password, no need for network privileges, etc.). Then start Task Scheduler and create a new Task entry, with these settings: a. General tab: Name: Enter a name like “Start ThermoHID at startup” or similar. Select “Run whether user is logged on or not.” And “Change User”: type your secondary user name, and Check Names, select the found user entry, and OK. Supply password. b. Triggers: Click New, select to begin the task “At startup,” and OK. c. Actions: Click New, select to “Start a program,” browse to find the fully qualified location of “ThermoHID.exe”, copy/paste the drive and folder information into the “Start in” box, and OK. d. Settings: Verify that “Do not start a new instance” is selected e. Save by clicking OK, and supply the password for the new user you created above. f. Run now: right-click the new task, and select Run. The program should begin running in the background, which can be verified by either watching the files change periodically in the ThermoHID folder, or running Windows Task Manager (Ctrl-Alt-Del), and seeing the ThermoHID process in the list. You should also verify that it runs when you restart the computer, too. (You can also “End” ThermoHID from the right-click menu, too.) Step 4. Automatically upload to a web server ThermoHID includes its own ftp capability, but I prefer a more secure and versatile file transfer program: WinSCP, which can run a script to upload the web page and graph to a web server. Upload of files via a Script. Below is a WinSCP script (plain text) file (upload_ThermoHID_files.txt), located in the WinSCP folder, that will be run by WinSCP to: 1) connect to MyServer, 2) “put” our two updated ThermoHID files into the existing /office folder, and 3) Exit. (Replace MyServer and /office with your own server and folder names. MyServer must exist with the required login information in WinSCP.) # Automatically answer all prompts negatively # so not to stall the script on errors option batch on # Disable overwrite warnings/confirmations option confirm off # Connect to MyServer using saved session settings open MyServer # Change remote directory cd /office # Upload files (and rename html) to the current working directory put "c:\program files\ThermoHID\ThermoHID.htm" index.html put "c:\program files\ThermoHID\TempHIDGraph.jpg" # Disconnect close # Exit WinSCP exit — 2 — Note: This script copies (renames) the ThermoHID.htm file to “index.html,” so simply browsing to a URL like http://myserver.com/office will display the current ThermoHID web page and graph. HINT: Try out this script from the WinSCP folder, and watch for successful responses. At the command line, type: winscp /script=upload_ThermoHID_files.txt Automatically Upload. To keep the web page up-to-date, periodically perform this upload. Create another Windows Scheduled Task (in Control Panel) that runs the script in the background. 1. Right-click My Computer, Manage, under System Tools, see Task Scheduler, and the Task Scheduler Library. (If you made a folder for the Step 3 ThermoHID tasks, open and save this new task there, too.) 2. Right-click and Create Task. a. General tab: Name: Enter a name like “Upload files every few minutes” or similar. Select “Run whether user is logged on or not.” And “Change User”: type your secondary user name, Check Names, select the found user entry, and OK. Supply password. b. Triggers: Click New, select to begin the task “At startup,” check “Repeat Task every”, specify “5 minutes”, Enabled, and OK. And in case something stops this task, add a second: click New, begin “On a schedule”, change the time to midnight (12AM), Daily, and again, “Repeat task every 5 minutes,” Enabled, and OK. c. Actions: Click New, select to “Start a program,” browse to find the fully qualified location of “WinSCP.com”, copy/paste the drive and folder information into the “Start in” box. Now, very important: in the “Add arguments” box, paste: “/script=upload_ThermoHID_files.txt” (or whatever you named the WinSCP script) and click OK. d. Settings: Verify that “Do not start a new instance” is selected e. Save: click OK, and again supply the user password. f. Run now: Right-click the new task, and select Run. The program should briefly execute in the background and every 5 minutes thereafter. This can be verified by closely watching the Windows Task Manager (Ctrl-Alt-Del), and seeing the Win SCP process briefly appear in the list, and/or you can verify that updated files are indeed uploaded to your web server. Verify that it runs when you restart the computer, too. Customize ThermoHID Above we configured ThermoHID to automatically run in the background. Occasionally you may wish to make changes to the program and output. For example, to change: • The web page template, as defined by ThermoHID.txt. (ThermoHID.htm is generated using ThermoHID.txt.) • The chart layout, defined by a tee file (usually default.tee) in the ThermoHID folder. Chart formatting changes can be made in the ThermoHID program or with TeeChart Office. • The ThermoHID program operation itself, by altering the INI file or while running the EXE. In all these cases, changes will take effect the next time ThermoHID is started. But since you probably have it always running, you must: 1) stop the program, 2) make your changes, and 3) restart the program. — 3 — Stop/ReStart ThermoHID 1. You can log in as the secondary user, and Exit the running ThermoHID program (right click the task-bar icon, and Exit). Or, to avoid switching users, you can use the Windows Task Manager (Ctrl-Alt-Del), scroll down to find the ThermoHID process, right-click and End Process. (Cross your fingers and hope that no file corruption occurs!) 2. Now, to make changes to ThermoHID set up, start ThermoHID.exe, right-click the task- bar icon and Restore, make desired changes in configuration, and End the program (right- click the task-bar icon, and Exit) to save the changes. 3. Then restart the task: Open up the Task Scheduler list, right-click the ThermoHID task in the list, and select Run. ThermoHID should be listed in the Windows Task Manager. Below are some typical changes you might wish to make to ThermoHID in Step 2 above. Change the Chart The most common need for change will be to adjust the chart, e.g., the range of outdoor temperatures (y-axis) in summer versus winter.
Load more

Recommended publications
  • 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
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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 ..........................................................................................................................................
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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 ...........................................................................................
    [Show full text]
  • 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.
    [Show full text]