LAN Server, Warp Server and DSS provide support for both 16-bit and 32-bit applications. Support for both types of applications allows a gradual change of LAN Server APIs into 32-bit worker routines without requiring 32-bit applications to change.

The new APIs were created with pure 32-bit programming in mind. In most cases, however, the 32-bit API is an entry point to 16-bit code. This implies that you must use a compiler, such as IBM C Set/2, with these characteristics:

• It can cause the addresses in the process's Local Descriptor Table to be tiled, allowing simple conversion from flat addressing to selector:offset and back.

• It allocates memory objects (such as data buffers) to prevent them from crossing 64KB memory boundaries.

The second characteristic has a further implication. Just as in the 16-bit world, buffer sizes are limited to 64KB in length. No matter how large a buffer you supply, an API rarely returns more than 64KB of data at a time. The exceptions are Net32AliasEnum and Net32UserEnum (OS/2 only), which can return more than 64KB of data.

Note: In DSS, all Net32User and Net32Group APIs support buffers larger than 64KB.

A 32-bit application that uses the Net32 or the Dos32 APIs must define the constant PURE_32 (not INCL_32) before including any LAN Server header files. The constant INCL_32 is for mixed-model programs only. The 32-bit API interfaces are slightly different from the 16-bit interfaces. The main highlights of the new APIs are:

• Parameters

  • The number of parameters is the same for both versions, except that a pszReservedX parameter has been added to the 32-bit APIs in the following categories: ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³CATEGORY ³APISUSINGpszReservedX ³
    ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
    ³ Alias ³ Net32AliasXXXX ³
    ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
    ³ Application ³ Net32AppXXXX ³
    ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
    ³ Group ³ Net32GroupXXXX ³
    ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
    ³ User ³ Net32UserXXXX ³
    ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
    

  • All variables declared char in LAN Server Version 3.0 are now unsigned char for Version 4.0.

  • All Version 3.0 pointers to char are now pointers to unsigned char.

    Note: Applications must be compiled with the compiler option that defaults char to unsigned char.

    -
    Most (but not all) short integers, whether signed or unsigned, have become unsigned long integers in the 32-bit version. This includes reserved parameters.
    -
    All pointers to short integers, signed or unsigned, have become pointers to unsigned long integers in the 32-bit version. This includes reserved parameters.
    
    Data structures

    All data structures and their alignment are unchanged (except that char becomes unsigned char). Some 4-byte elements might be aligned on 16-bit WORD boundaries rather than 32-bit DWORD boundaries. This is a compromise between the speed of execution of the API code and application code.

    
    Names

    • The names of the Mailslot APIs are changed from 16-bit DosXXX to 32-bit Dos32XXX. The 16-bit NetXXX APIs are changed to Net32XXX for the 32-bit names. The NetBiosXXX APIs are named NetBios32XXX for 32-bit, and the UPMXXX APIs are U32XXX for 32-bit applications.

    • The names of the data structures are the same for all. This means that for a given data structure, you cannot not mix pure 16-bit and 32-bit code. You can, however, write programs that use the mixed model (INCL_32 defined) in one file and pure 32-bit code (PURE_32 defined for OS/2) in another. You must choose only one type (pure 16-bit, mixed, or pure 32-bit) for each program file.
    
    Return Codes

    The Net32XXX APIs return 16-bit return codes.

    Note: Not all 16-bit APIs have 32-bit entry points. For example, because 16- and 32-bit file handles are incompatible, there are no Net32Handle APIs. In addition, all the APIs in the following categories have no thunked counterparts:

    Named Pipe Print Destination
    Print Job
    Print Queue
    Spooler

    ---

    [Back] [Next]