DOCSLIB.ORG

IDK Basic Developer's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IDK Basic Developer's Guide Basic Developer’s Guide P/N UD 028155 The names, places, and/or events used in this publication are not intended to correspond to any individual, group, or association existing, living, or otherwise. Any similarity or likeness of the names, places, and/or events with the names of any individual, living or otherwise, or that of any group or association is purely coincidental and unintentional. NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. © 1993 Unisys Corporation. All rights reserved. RESTRICTED RIGHTS LEGEND Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 252.227–7013 and FARS 52.227–14 for commercial computer software. Attachmate and the Attachmate logo are registered trademarks of Attachmate Corporation in the United States and other countries. INFOConnect is a trademark and Unisys is a registered trademark of Unisys Corporation. All other trademarks and registered trademarks are property of their respective owners. The names, places, and/or events used in this publication are not intended to correspond to any individual, group, or association existing, living, or otherwise. Any similarity or likeness of the names, places, and/or events with the names of any individual, living or otherwise, or that of any group or association is purely coincidental and unintentional. NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. RESTRICTED RIGHTS LEGEND. Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 252.227–7013 and FARS 52.227–14 for commercial computer software. Correspondence regarding this publication may be forwarded using the Documentation Questionnaire supplied with this document, or may be addressed directly to Unisys Corporation, INFOConnect Development Group, Malvern Development Center, 2450 Swedesford Road, Room B101, Paoli, Pennsylvania, 19301. Borland products are trademarks or registered trademarks of Borland International, Inc. IBM is a registered trademark of International Business Machines Corporation. Microsoft is a registered trademark and Windows is a trademark of Microsoft Corporation. Novell is a registered trademark of Novell, Inc. Unisys and INFOConnect are trademarks of Unisys Corporation. UNIX AND UNIX System V are registered trademarks of UNIX System Laboratories. XVT is a trademark of XVT Software Inc. Contents About this Guide .......................................................................... xvii Section 1. Installation Windows Platform ....................................................... 1–1 System Requirements ......................................... 1–1 Package Contents ............................................... 1–3 Basic IDK Package ...................................... 1–3 Basic IDK Samples Package ....................... 1–9 Installing the IDK ................................................. 1–17 Environment Variables ........................................ 1–17 System Verification Checklist for Windows ......... 1–19 Preparing XVT for Use with INFOConnect ...................... 1–22 Section 2. An Introduction to INFOConnect Connectivity Services Architecture Diagram .................................................. 2–5 Terminology ............................................................... 2–6 Accessory API Functions ............................................. 2–15 Accessory API Events ................................................. 2–18 Section 3. Writing INFOConnect/Windows Applications Basic Procedures for Windows Applications .................. 3–2 Initializing INFOConnect Connectivity Services .... 3–2 Opening a Session and Allocating Buffers .......... 3–5 Transmitting a Buffer ........................................... 3–8 Receiving a Buffer ............................................... 3–12 Using Datacomm Buffers .................................... 3–15 Basic Error Handling ........................................... 3–17 Basic Status Handling ......................................... 3–22 Closing a Session ............................................... 3–26 Terminating your Application .............................. 3–28 4173 5408-000 v Contents Advanced Procedures for Windows Applications ............ 3–32 Canceling Pending Requests ............................. 3–32 Handling Data Communications Errors .............. 3–33 Advanced Status and Error Handling ................. 3–36 Encoding and Decoding ..................................... 3–38 Data Compression and Error Detection .............. 3–38 Running with Old Versions of INFOConnect ...... 3–39 Procedures for INFOConnect Accessories ..................... 3–41 Calling INFOConnect Accessories ..................... 3–41 Making your Application an INFOConnect Accessory ...................................................... 3–42 Compiling .................................................................. 3–44 Resource Files ............................................................ 3–46 Linking ................................................................... 3–51 IcWinApp - a Sample Windows Application .................... 3–53 CoupleW - a Windows Application that Connects Two INFOConnect Sessions ................................ 3–76 Section 4. Writing INFOConnect/XVT Applications Basic procedures for XVT Applications ......................... 4–2 Initializing INFOConnect Connectivity Services ......................................................... 4–2 Opening a Session and Allocating Buffers ......... 4–3 Transmitting a Buffer .......................................... 4–6 Receiving a Buffer .............................................. 4–8 Using Datacomm Buffers .................................... 4–10 Basic Error Handling ........................................... 4–12 Basic Status Handling ........................................ 4–16 Closing a Session ............................................... 4–19 Terminating your Application .............................. 4–20 Advanced Procedures for XVT Applications ................... 4–24 Canceling Pending Requests ............................. 4–24 Handling Data Communications Errors .............. 4–25 Advanced Status and Error Handling ................. 4–26 Using Event Hooks with XVT 3.0 ........................ 4–29 Using Keyboard and Event Hooks with XVT2.0 ... 4–30 Encoding and Decoding ..................................... 4–31 Data Compression and Error Detection .............. 4–32 Running with Old Versions of INFOConnect ...... 4–32 vi 4173 5408-000 Contents Procedures for INFOConnect Accessories ..................... 4–33 Calling INFOConnect Accessories ...................... 4–34 Making your Application an INFOConnect Accessory ....................................................... 4–34 Compiling .................................................................. 4–37 Windows Platform ............................................... 4–37 Compiler Errors ............................................ 4–39 Resource Files ............................................................ 4–39 Linking ................................................................... 4–40 Windows Platform ............................................... 4–40 IcXvtApp - A sample XVT application ............................. 4–44 Couple - An XVT Application that Connects Two INFOConnect Sessions ................................ 4–46 IcOpenAc - An XVT Application that Opens an INFOConnect Accessory .............................. 4–48 Section 5. Writing INFOConnect/DosLink Applications Basic Procedures for DosLink Applications ................... 5–3 Initializing INFOConnect Connectivity Services ......................................................... 5–3 Opening a Session .............................................. 5–4 Transmitting a Buffer ..........................................
Load more

Recommended publications
  • 31295004054614.Pdf (10.42Mb)
    TOWARD PIN m^ SIECI£ EMANCIPATION: THE DEVELOPMENT OF INDEPENDENCE IN THOMAS HARDY'S WESSEX WOMEN by MARTHA LUAN CARTER BRUN30N, B.S., M.A. A DISSSr.TATION IN ENGLISH Submitted to the Graduate Faculty of Texas Technoloc:ical College in Partial Fulfillment of the Requirements for the Degree of DOCTOR OP PHILOSOPHY Approved AC 90) ACKN j^yLL-roM;- NTS I am deeply Indebted to Dr. Roger L, Brooks for aerving as director of this disserfefitloa and for his con- atant assistance end encouragement over T;he past several yearStt I am also grateful to the other members of my com-» mittee^ Dr» J« T, HcCullen and rr# Jacqueline Collins, for their generous aid anri interest. ii TABL:^ OF CONTENTS Page ACKHOWLED(H^<NTS •«.... ii TVT ONE INTFiODUCTION •.. 1 ?^nT -TWO HAPDY»S WOMEN RiilACT TO SJCIAL CO?^V..IiTIul^S Chapter I Conventional Reaction in uhe Early ^.lovels ••••••••••15 Chapter II Rebels Hevolt. Others Conio/m: The HldfUe Ifovels • • 1^.6 Chapter III A Finer Dividing Line for Con­ ventions: The Mayor of Caster- bridge and The Woodlanders • . • 35 Chapter IV The New Compounds: teas of the D<Jrbervilles, Jude the oFscurej and The Well-Beloved • • • . • 11? PART TiAih^:: CO'ICLUSION ••••••• •...••• 1U9 BIBLIOG APrlY • • 159 iii PART ONE INTPODUCTI.N Critics, even though they do not consistently inter­ pret his oharaoterizations, consider among the foremost of Thomas Hardy*s achievements his characterization of women* One does not have to go beyond major critical studies, how­ ever, to find ample comment on the women as well as to estab­ lish the
    [Show full text]
  • Free Pascal Runtime Library Reference Guide.Pdf
    Run-Time Library (RTL) : Reference guide. Free Pascal version 2.2.2: Reference guide for RTL units. Document version 2.1 June 2008 Michaël Van Canneyt Contents 0.1 Overview........................................ 93 1 Reference for unit ’BaseUnix’ 94 1.1 Used units........................................ 94 1.2 Overview........................................ 94 1.3 Constants, types and variables............................. 94 1.3.1 Constants.................................... 94 1.3.2 Types...................................... 116 1.4 Procedures and functions................................ 131 1.4.1 CreateShellArgV................................ 131 1.4.2 FpAccess.................................... 132 1.4.3 FpAlarm.................................... 132 1.4.4 FpChdir..................................... 133 1.4.5 FpChmod.................................... 133 1.4.6 FpChown.................................... 135 1.4.7 FpClose..................................... 136 1.4.8 FpClosedir................................... 136 1.4.9 FpDup..................................... 136 1.4.10 FpDup2..................................... 137 1.4.11 FpExecv.................................... 138 1.4.12 FpExecve.................................... 139 1.4.13 FpExit...................................... 140 1.4.14 FpFcntl..................................... 140 1.4.15 fpfdfillset.................................... 141 1.4.16 fpFD_CLR................................... 141 1.4.17 fpFD_ISSET.................................. 142 1.4.18 fpFD_SET..................................
    [Show full text]
  • Jejening BULLETM Guarantees Advertlaera Aorangl , , 2IU.: ....Sept
    HWIHIIIHIIIIIIIIIIIUIHmilllllHOllWWI, ' yv?f: !Paily WOMEN READ THE ADS AND BUY THE GOODS STEAMER TABLE, The local merchant needt a From Ban Francisco! 1 paper that reachea the Mongolia . f. .'. j.SodL 1 ' ..... greateat number of H Ventura i. Sept. (J, people In their For 8n Francisco: ' hornet. Manchuria Sept. 8 i f3f THE .' Alameda..: ...Sept 20 P- - St EVENING BULLETIN g Korea t Sept. 22 fills the evening field and From Vancouver: JEjENING BULLETM guarantees advertlaera Aorangl , , 2IU.: ....Sept. both quantity and qual- For Vancouver: ity of circulation. " " " " Mlowera Sept. 20, THE BULLETIN IS HONOLULU'S HOME PAPER fSD O'CLOCK EDITION mmmmmms Voi XII No. 3169 HONOLULU. TERRITORY OjP HAWAII. MONDAY, SEPTEMBER i, 1905 Pbiob 6 Cknts. Some Straight Talk LABOR PEACE TOMORROW While tl i Outing At Pearl Harbor Waiting For Quorum I BASEBALITODAY Y IS MI a Calls Crowd To m FINAL SHOTS ARE Peninsula AIIWA CENTRAL COMMITTEE'S UNOFFICIAL IDEAS D. A. CS AND ELKS IIS TERRITORY OFFICERS REST, FOR CHAMPIONSHIP The Republican Territorial Central (Lane "To smooth things over." -- "COUNTY SERVANTS TOIL Committee met at Republican head- Clarke "To go to I, hear" he has a jGood Property Will Soon FIRED AT FRONT now " quarters Saturday evening to hoar o WEATHER REPORTED FINE AT lane, Interrupting "Ko doubt the GOOD WEATHER PROMISED FOR PARK KAM3 AND MAILES report of on revi- Be Opened For the reports back on tho mainland were DASEQALL, GAME9 AND EX- PLAY FIR8T FOR TAIL- - of Less sion party rules. than halt a stretched a bit; tho reporters must CURSIONDANCING AT ENDERS.
    [Show full text]
  • Programmer's Guide
    Free Pascal Programmer’s Guide Programmer’s Guide for Free Pascal, Version 3.0.0 Document version 3.0 November 2015 Michaël Van Canneyt Contents 1 Compiler directives 13 1.1 Introduction....................................... 13 1.2 Local directives..................................... 14 1.2.1 $A or $ALIGN : Align Data.......................... 14 1.2.2 $A1, $A2,$A4 and $A8 ............................ 14 1.2.3 $ASMMODE : Assembler mode (Intel 80x86 only)............... 15 1.2.4 $B or $BOOLEVAL : Complete boolean evaluation.............. 15 1.2.5 $C or $ASSERTIONS : Assertion support................... 15 1.2.6 $BITPACKING : Enable bitsize packing................... 16 1.2.7 $CALLING : Specify calling convention.................... 16 1.2.8 $CHECKPOINTER : Check pointer values................... 16 1.2.9 $CODEALIGN : Set the code alignment.................... 17 1.2.10 $COPERATORS : Allow C like operators................... 18 1.2.11 $DEFINE or $DEFINEC : Define a symbol.................. 18 1.2.12 $ELSE : Switch conditional compilation................... 18 1.2.13 $ELSEC : Switch conditional compilation................... 19 1.2.14 $ELSEIF or $ELIFC : Switch conditional compilation........... 19 1.2.15 $ENDC : End conditional compilation..................... 19 1.2.16 $ENDIF : End conditional compilation.................... 19 1.2.17 $ERROR or $ERRORC : Generate error message............... 20 1.2.18 $ENDREGION: End of a collapsible region.................. 20 1.2.19 $EXTENDEDSYM: Ignored........................... 20 1.2.20 $EXTERNALSYM: Ignored........................... 20 1.2.21 $F : Far or near functions........................... 20 1.2.22 $FATAL : Generate fatal error message.................... 21 1.2.23 $FPUTYPE : Select coprocessor type..................... 21 1.2.24 $GOTO : Support Goto and Label ...................... 22 1.2.25 $H or $LONGSTRINGS : Use AnsiStrings.................. 22 1.2.26 $HINT : Generate hint message.......................
    [Show full text]
  • System Tools Reference Manual for Filenet Image Services
    IBM FileNet Image Services Version 4.2 System Tools Reference Manual SC19-3326-00 IBM FileNet Image Services Version 4.2 System Tools Reference Manual SC19-3326-00 Note Before using this information and the product it supports, read the information in “Notices” on page 1439. This edition applies to version 4.2 of IBM FileNet Image Services (product number 5724-R95) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 1984, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this manual 17 Manual Organization 18 Document revision history 18 What to Read First 19 Related Documents 19 Accessing IBM FileNet Documentation 20 IBM FileNet Education 20 Feedback 20 Documentation feedback 20 Product consumability feedback 21 Introduction 22 Tools Overview 22 Subsection Descriptions 35 Description 35 Use 35 Syntax 35 Flags and Options 35 Commands 35 Examples or Sample Output 36 Checklist 36 Procedure 36 May 2011 FileNet Image Services System Tools Reference Manual, Version 4.2 5 Contents Related Topics 36 Running Image Services Tools Remotely 37 How an Image Services Server can hang 37 Best Practices 37 Why an intermediate server works 38 Cross Reference 39 Backup Preparation and Analysis 39 Batches 39 Cache 40 Configuration 41 Core Files 41 Databases 42 Data Dictionary 43 Document Committal 43 Document Deletion 43 Document Services 44 Document Retrieval 44 Enterprise Backup/Restore (EBR)
    [Show full text]
  • FCL Reference Guide
    Free Component Library (FCL): Reference guide. Reference guide for FCL units. Document version 3.2.2 May 2021 Michaël Van Canneyt Contents 0.1 Overview........................................ 88 1 Reference for unit ’ascii85’ 89 1.1 Used units........................................ 89 1.2 Overview........................................ 89 1.3 Constants, types and variables............................. 89 1.3.1 Types...................................... 89 1.4 TASCII85DecoderStream................................ 90 1.4.1 Description................................... 90 1.4.2 Method overview................................ 90 1.4.3 Property overview............................... 90 1.4.4 TASCII85DecoderStream.Create........................ 90 1.4.5 TASCII85DecoderStream.Decode....................... 91 1.4.6 TASCII85DecoderStream.Close........................ 91 1.4.7 TASCII85DecoderStream.ClosedP....................... 91 1.4.8 TASCII85DecoderStream.Destroy....................... 91 1.4.9 TASCII85DecoderStream.Read........................ 92 1.4.10 TASCII85DecoderStream.Seek........................ 92 1.4.11 TASCII85DecoderStream.BExpectBoundary................. 92 1.5 TASCII85EncoderStream................................ 92 1.5.1 Description................................... 92 1.5.2 Method overview................................ 93 1.5.3 Property overview............................... 93 1.5.4 TASCII85EncoderStream.Create........................ 93 1.5.5 TASCII85EncoderStream.Destroy....................... 93 1.5.6 TASCII85EncoderStream.Write.......................
    [Show full text]
  • 51. Graphical User Interface Programming
    Brad A. Myers Graphical User Interface Programming - 1 51. Graphical User Interface Programming Brad A. Myers* Human Computer Interaction Institute Carnegie Mellon University 5000 Forbes Avenue Pittsburgh, PA 15213 [email protected] http://www.cs.cmu.edu/~bam (412) 268-5150 FAX: (412) 268-1266 *This paper is revised from an earlier version that appeared as: Brad A. Myers. “User Interface Software Tools,” ACM Transactions on Computer-Human Interaction. vol. 2, no. 1, March, 1995. pp. 64-103. Draft of: January 27, 2003 To appear in: CRC HANDBOOK OF COMPUTER SCIENCE AND ENGINEERING – 2nd Edition, 2003. Allen B. Tucker, Editor-in-chief Brad A. Myers Graphical User Interface Programming - 2 51.1. Introduction Almost as long as there have been user interfaces, there have been special software systems and tools to help design and implement the user interface software. Many of these tools have demonstrated significant productivity gains for programmers, and have become important commercial products. Others have proven less successful at supporting the kinds of user interfaces people want to build. Virtually all applications today are built using some form of user interface tool [Myers 2000]. User interface (UI) software is often large, complex and difficult to implement, debug, and modify. As interfaces become easier to use, they become harder to create [Myers 1994]. Today, direct manipulation interfaces (also called “GUIs” for Graphical User Interfaces) are almost universal. These interfaces require that the programmer deal with elaborate graphics, multiple ways for giving the same command, multiple asynchronous input devices (usually a keyboard and a pointing device such as a mouse), a “mode free” interface where the user can give any command at virtually any time, and rapid “semantic feedback” where determining the appropriate response to user actions requires specialized information about the objects in the program.
    [Show full text]
  • Cross-Platform 1 Cross-Platform
    Cross-platform 1 Cross-platform In computing, cross-platform, or multi-platform, is an attribute conferred to computer software or computing methods and concepts that are implemented and inter-operate on multiple computer platforms.[1] [2] Cross-platform software may be divided into two types; one requires individual building or compilation for each platform that it supports, and the other one can be directly run on any platform without special preparation, e.g., software written in an interpreted language or pre-compiled portable bytecode for which the interpreters or run-time packages are common or standard components of all platforms. For example, a cross-platform application may run on Microsoft Windows on the x86 architecture, Linux on the x86 architecture and Mac OS X on either the PowerPC or x86 based Apple Macintosh systems. A cross-platform application may run on as many as all existing platforms, or on as few as two platforms. Platforms A platform is a combination of hardware and software used to run software applications. A platform can be described simply as an operating system or computer architecture, or it could be the combination of both. Probably the most familiar platform is Microsoft Windows running on the x86 architecture. Other well-known desktop computer platforms include Linux/Unix and Mac OS X (both of which are themselves cross-platform). There are, however, many devices such as cellular telephones that are also effectively computer platforms but less commonly thought about in that way. Application software can be written to depend on the features of a particular platform—either the hardware, operating system, or virtual machine it runs on.
    [Show full text]
  • Ornl ORNL-6879
    ,i*s<t$v> ornl ORNL-6879 OAK RIDGE FUSION ENERGY NATIONAL DIVISION LABORATORY ntAfWTtiV MARIETTA PROGRESS REPORT Period from January 1, 1992, to December 31, 1994 MANAGED BY MARTIN MARIETTA ENERGY SYSTEMS, INC. FOR THE UNITED STATES Dl«TRJBUTiON OF THIS DOCUMENT IS UNLII^JTEO DEPARTMENT OF ENERGY This report has been reproduced directly from the best available copy. Available to DOE and DOE contractors from the Office of Scientific and Techni• cal Information, P.O. Box 62, Oak Ridge, TN 37831; prices available from (615) 576-8401, FTS 626-8401. Available to the public from the National Technical Information Service, U.S. Department of Commerce, 5285 Port Royal Rd., Springfield, VA 22161. This report was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor any agency thereof, nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, com• pleteness, or usefulness of any information, apparatus, product, or process dis• closed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily consti• tute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or any agency thereof. DISCLAIMER Portions of this document may be illegible electronic image products, images are produced from the best available original document.
    [Show full text]
  • FCL Reference Guide
    Free Component Library (FCL): Reference guide. Reference guide for FCL units. Document version 2.1 November 2010 Michaël Van Canneyt Contents 0.1 Overview........................................ 54 1 Reference for unit ’ascii85’ 55 1.1 Used units........................................ 55 1.2 Overview........................................ 55 1.3 Constants, types and variables............................. 55 1.3.1 Types...................................... 55 1.4 TASCII85DecoderStream................................ 55 1.4.1 Description................................... 55 1.4.2 Method overview................................ 56 1.4.3 Property overview............................... 56 1.4.4 TASCII85DecoderStream.Create........................ 56 1.4.5 TASCII85DecoderStream.Decode....................... 56 1.4.6 TASCII85DecoderStream.Close........................ 57 1.4.7 TASCII85DecoderStream.ClosedP....................... 57 1.4.8 TASCII85DecoderStream.Destroy....................... 57 1.4.9 TASCII85DecoderStream.Read........................ 57 1.4.10 TASCII85DecoderStream.Seek........................ 58 1.4.11 TASCII85DecoderStream.BExpectBoundary................. 58 1.5 TASCII85EncoderStream................................ 58 1.5.1 Method overview................................ 58 1.5.2 Property overview............................... 58 1.5.3 TASCII85EncoderStream.Create........................ 58 1.5.4 TASCII85EncoderStream.Destroy....................... 59 1.5.5 TASCII85EncoderStream.Write........................ 59 1.5.6 TASCII85EncoderStream.Width.......................
    [Show full text]
  • Competition Environment
    Competition Environment Contents 1 General 2 2 Hardware 2 3 Linux 2 4 Windows 4 1 CEOI 2003, Germany Competition environment 1 General Please first check the general information about the competition programming environment from the Competition Rules. The main environment for the contest is Linux. Linux is available as a programming environment (specifications below) and also the servers and evaluation (grading) runs on Linux. However, we provide the contestants with dual-boot computers where you can program either in Linux or in Windows environment. The evaluation is based on source-code submission and the evaluation system compiles the sub- mitted source code. As a consequence, also the programs written in the Windows environment are re-compiled for evaluation in Linux (using the same compiler). This is something that all contes- tants using Windows must be aware of. For example, uninitialized variables may cause undefined behavior when executing for the evaluation. We favor fairly standard operating system installations, but we may modify the installations for hardware support and security fixes. The compilers used in the competition are GCC for C and C++ programs and Freepascal for Pascal programs. Generally, the installations are designed for the following main alternatives: 1. Pascal as the programming language, Freepascal compiler, Freepascal IDE or RHIDE IDE. 2. C/C++ as the programming language, GCC compiler, RHIDE IDE. 3. Editors (emacs, vim, ...), command-line compilation/debugging, a graphical front end ddd for debugging. Option 3 is targeted primarily for Linux, although it is possible to use Windows Edit and command- line compilation. 2 Hardware The competition computers have Pentium III/650 MHz or better processor, 128 MB or more RAM, a standard UK keyboard, a mouse, and a color screen.
    [Show full text]
  • Loan Application Documents Thank You for Choosing Us for Your Home Financing. Please Call Us at 502.223-1638 Or 1-888-818-3372
    Loan Application Documents Thank you for choosing us for your home financing. Please call us at 502.223-1638 or 1-888-818-3372 if you have questions. Either drop off or mail completed forms to us at PO Box 535, Frankfort, KY 40602 or fax to us at 502.223-7136. TO PROTECT YOUR PERSONAL FINANCIAL INFORMATION, PLEASE DO NOT EMAIL YOUR COMPLETED APPLICATION OR OTHER FORMS WITH SENSITIVE INFORMATION. The following documents are included in this packet. Note that the items with a must be returned : - UNIFORM RESIDENTIAL LOAN APPLICATION (9 pages). If applying for joint credit with someone with whom you share financial information (such as a spouse), the other borrower must complete the UNIFORM RESIDENTIAL LOAN APPLICATION-ADDITIONAL BORROWER (4 pages). If the other borrower does not share your financial information, he or she should complete another 9-page UNIFORM RESIDENTIAL LOAN APPLICATION. This longer form was introduced on March 1, 2021 and is much different from applications you may have completed before. Your loan officer would be glad to help with completion, or you can find instructions at https://singlefamily.fanniemae.com/delivering/uniform- mortgage-data-program/uniform-residential-loan-application - BORROWER’S SIGNATURE AUTHORIZATION FORM-EVIDENCE OF AUTHORIZATION - DELIVERY OF ELECTRONIC INFORMATION AND NOTICE OF AVAILABILITY OF PAPER RECORDS. If you would like to communicate with us by sending and receiving non-sensitive customer information by email, please make sure you have provided us with a valid email address and sign and submit this form. - 3/1 EARLY ARM DISCLOSURE STATEMENT. We provide this disclosure because it is the most popular adjustable-rate product.
    [Show full text]