home *** CD-ROM | disk | FTP | other *** search
- ******************************************************************************
- Communicating with TechniLib Via Electronic Mail
- ******************************************************************************
-
- You can communicate with TechniLib via CompuServe electronic mail. Direct
- mail to account 74730,167.
- XLIB may also be registered through CompuServe. Use GO SWREG (shareware
- registration). The program identification number is 1423. The program title
- is XLIB 2.0. After registering, TechniLib will contact you to give you a
- registration number and to determine if you want a printed copy of the user
- manual.
-
- ******************************************************************************
- Quick Start with XLIB
- ******************************************************************************
-
- The user manual is largely dedicated to cover specifics of XLIB which will
- rarely be of concern to the typical programmer.
- If all you need is protected-mode execution within an assembly language
- program, then the introductory chapter will tell you nearly all that you need
- to know. You might also familiarize yourself with the predefined descriptors
- and selectors in XLIB by studying Chapter 2.
- If you need to place data in extended memory, then examine the GETMEM and
- PMGETMEM procedures in Chapter 7.
- C programmers wishing to use inline protected-mode execution should study
- the inline mode switch procedures in Chapter 5.
-
- ******************************************************************************
- Improvements in XLIB Version 2.0
- ******************************************************************************
-
- 1) Procedures enabling protected-mode programming in C using inline assembly.
- 2) Protected-mode file routines which can transfer extended memory to files
- or files to extended memory. Sequential and random access are supported.
- 3) Better interrupt management services.
- 4) User-defined descriptors.
- 5) More descriptors. XLIB 2.0 can be used to create protected-mode libraries
- for nearly all language products.
- 6) More configurability.
- 7) Minor bug fixes
- 8) Better documentation.
-
- ******************************************************************************
- Instructions for Constructing Protected-Mode Libraries
- ******************************************************************************
-
- The following batch file uses Microsoft LIB to combine an OBJ file with
- XLIB.LIB to produce a protected-mode library. Call the batch file using the
- base name of the OBJ file as the argument. This base name will also be given
- to the library. It is assumed that all files, including LIB.EXE, are in the
- current directory.
-
- @echo on
- del %1.lib
- lib %1.lib/noi +%1.obj+xlib.lib;
-
-
- The following batch file uses Microsoft LINK and LIB to combine an OBJ
- file with XLIB.LIB to produce a protected-mode library and quick library for
- Microsoft BASIC 7.0. Call the batch file using the base name of the OBJ
- file as the argument. This base name will also be given to the library and
- the quick library. It is assumed that all files, including LINK.EXE and
- LIB.EXE, are in the current directory. The current directory must also
- contain the file QBXQLB.LIB (included in the BASIC distribution disks).
-
- @echo on
- del %1.qlb
- del %1.lib
- link /q/nopackf xlib.lib+%1.obj,%1.qlb,,qbxqlb.lib;
- lib %1.lib +xlib.lib+%1.obj+qbxqlb.lib;
-
- ******************************************************************************
- Explanation of PMPRINT.ASM
- ******************************************************************************
-
- Since protected-mode debuggers are hard to find, a programmer is greatly
- assisted by a set of screen management routines when preparing such code. The
- file PMPRINT.INC includes a set of basic screen routines for protected-mode.
- Programmers using monochrome monitors will have to change the base address for
- the screen. This file is included for your convenience.
-