TNT DOS-Extender Windows接口指南：构建图形用户界面详解

需积分: 9 29 浏览量更新于2024-07-26 收藏 963KB PDF 举报

TNT DOS-Extender 是一款由 Phar Lap 公司开发的著名 DOS 扩展器，专为 MS-DOS 或 PC-DOS 环境下的程序提供了一个32位 x86 保护模式运行环境。这款扩展器支持多线程程序在 DOS 下的实时运行，如微软 Foxpro 的 32 位版本，可以无缝执行所有功能。它针对当时高性能处理器（如 386, 486, Pentium 及更高）设计，需要至少 2MB 内存扩展和 10MB 的硬盘空间。支持的编译器包括 Borland C++, Visual C++, Watcom C/C++ 和 Open Watcom C/C++，推荐使用后者。 TNT DOS-Extender Reference Manual 是核心文档，详细介绍了保护模式环境和编程需求，以及如何利用这些工具来构建程序。此外，还有针对不同编译器的指导，如 Microsoft Visual C/C++、MetaWare High C/C++ 和 Open-Watcom C/C++32。该扩展器还包含了库和系统调用参考文档，如 DOSX32.LIB 和 DOS32.LIB，以及对 Win32 API 和 register-based software interrupt 接口的完整文档。特别值得关注的是 Windows Interface Guide，它阐述了如何利用 Phar Lap 的 WinPipe Application Program Interface (API) 来创建 TNT DOS-Extender 应用程序的图形用户界面，以适应 Windows 3.1 系统。这对于开发者来说是至关重要的，因为它允许将 DOS 程序与 Windows 界面相结合，提升用户体验。对于调试支持，TNT DOS-Extender 提供了 CodeView Source Code Debugger 和 386|SRCBug 调试器的参考手册，帮助开发者诊断和修复 32 位保护模式程序中的问题。此外，还有 386|ASM 宏汇编参考手册，用于深入理解 Phar Lap 的宏汇编技术。值得注意的是，所有文档都受到版权保护，未经 VenturCom, Inc. 的书面许可，不得复制或传输。同时，VenturCom 对于因文档错误、遗漏或声明引起的任何损失或损害不承担任何责任，且不保证产品或系统的适用性。 TNT DOS-Extender 是一个功能强大的工具包，它不仅提供了32位保护模式环境，还包含了丰富的开发文档、调试工具和与 Windows 环境集成的方法，是当时 IT 开发人员开发高性能 DOS 应用的宝贵资源。

Chapter 2

typedef struct DosAp

{

DWORD ToDosQueueHandle;

DWORD FromDosQueueHandle;

WORD WindowsTask;

WORD DosInstance;

WORD DosIsDead;

struct DosAp _far *next;

} DosAp;

typedef DosAp _far *PDOSAP;

DWORD, LPSTR, UINT, WORD, and BYTE are convenient shorthand for

frequently-used C data types; this is the same terminology used in Windows

3.1 (and Windows NT) APIs. Using this terminology facilitates writing code

that has to work with both 16-bit Visual Basic and 32-bit protected-mode C.

DosAp is a structure defined to contain the information needed to manage

the communication between a Windows program and a DOS application.

There is a DosAp structure allocated for each such pair of communicating

programs. In most cases, a Visual Basic program will be communicating

with a single DOS application. However, there may be circumstances under

which the Visual Basic program has to communicate with multiple DOS

programs — if, for example, you’ve written a single interface to control a

suite of applications. In this case, there must be a unique bi-directional

communication path between Visual Basic and each DOS application.

Additionally, your Visual Basic program must also declare a DosAp

structure specifying the communication paths for each DOS application that

it calls.

All the information within a DosAp structure is used internally by the

WinPipe API. However, the data structure must be declared in the Visual

Basic application because the Visual Basic/C interface does not currently

provide a convenient way for returning the address of memory allocated by

the C program.

PDOSAP is defined as a far pointer to a DosAp structure. This must be a far

pointer because the data is shared between the WinPipe DLL and the Visual

Basic Program.

8 Windows Interface Guide

The WinPipe API

That describes the interface in C, but how do we describe it in Visual Basic?

Table 7.2 in Chapter 7, “Variables, Constants, and Data Types,” of the

Microsoft Visual Basic Programming System for Windows Programmer’s Guide

describes the fundamental data types of Visual Basic. If you read this

chapter, you will learn that if you do not explicitly declare variables in Visual

Basic, they are of type Variant. The Variant data type is very flexible and

works well within Visual Basic. However, this flexibility can cause conflicts

when interfacing with a DLL written in C. Because a variable of type Variant

can hold many different kinds of data, ranging from integers to strings, the

amount of storage allocated is determined dynamically at run time. In order

to be sure that the data structures in Visual Basic and C line up correctly, the

Visual Basic data objects should be declared to be an equivalent type to that

in the corresponding C declaration. Section 3.3 contains several examples of

these shared data structures.

We use the same convention for line continuation as that used in the Visual

Basic documentation: lines too long to fit on one line in this manual may be

continued on the next line using a line-continuation character (). We thus

have the following declarations in Visual Basic:

Declare Function LoadDosAp Lib "winside.dll" (ByVal DosApName As String,

DosAp As DosApHandle, ByVal ShowWindow As Integer,

ByVal QueueSize As Integer) As Long

Declare Function SendToDos Lib "winside.dll" (DosApPtr As

DosApHandle,

DataPtr As Any, ByVal DataCount As Integer) As Long

Declare Function SendStringToDos Lib "winside.dll" (DosApPtr As

DosApHandle,

ByVal MessageString As String) As Long

Declare Function SendStrucAndStringToDos Lib "winside.dll"

(DosApPtr As DosApHandle, DataPtr As Any, ByVal DataCount As Integer,

MessageString As Any) As Long

Declare Function GetFromDos Lib "winside.dll" (DosApPtr As DosApHandle,

DataPtr As Any, ByVal DataCount As Integer, RetLength As Long) As Long

Declare Function UnloadDosAp Lib "winside.dll" (DosApPtr As DosApHandle,

DataPtr As Any, ByVal DataCount As Integer) As Long

The default in Visual Basic is to pass all parameters by reference. This is the

opposite from C where the default is to pass by value. The ByVal keyword

in Visual Basic is used to specify that the following parameter is to be passed

by value. If the formal parameter in the C function is a pointer (such as those

Windows Interface Guide 9

剩余160页未读，继续阅读

wiseye

粉丝: 1
资源: 8

TNT DOS-Extender Windows接口指南：构建图形用户界面详解

TNT DOS-Extender Reference Manual（参考手册）

TNT-API:将包裹信息发送到TNT以获取准确的费率和运输时间信息

TNT DOS-Extender库与系统调用详析

TNT DOS-Extender工具参考手册：32位保护模式环境与实用程序详解

如何在TNT DOS-Extender环境下为DOS应用程序集成图形用户界面？请详细说明集成步骤并提供相关代码示例。

如何在使用 TNT DOS-Extender 时，为保护模式下的 DOS 应用程序添加图形用户界面？请提供具体步骤和示例代码。

minter-explorer-extender

FIMFiction-Emote-Extender

Obsidian-Portal-Extender

VNDB-Extender-2020:VNDB Extender的更新版本

最新资源