README.TXT          NOVLIB 3.30 Release Notes                 98.07.31
------------------------------------------------------------------------------

 Welcome to NOVLIB  3.30. Some changes have been made to NOVLIB since the
 printed documentation, so please read the following sections carefully,
 and study the new sections in the Windows help file NOVLIB.HLP, before
 calling technical support.

 Contents

 1.  General Notes
 2.  32 bit support for Windows 95
 3.  Additional and Changed NOVLIB Functions
 4.  Additional static libraries
 5.  Watcom C/C++ Notes
 6.  Delphi Notes
 7.  Visual Basic Notes
 8.  CA-Visual Objects Notes
 9.  CA-Clipper Notes
 10. Credits

 1. General Notes

 When using NOVLIB with NetWare 4.x, the user must be logged in using
 Bindery Emulation mode.

 i.e. login /b username

 2. 32 bit support for Windows 95

 NOVLIB 3.30 does NOT currently support 32 bit programming under the
 Windows NT operating system.

 NOVLIB 3.30 supports 32 bit programs running on the Windows 95 platform
 built using the following tools:

 Microsoft Visual C++ 2.0 and later
 Borland C++ 4.5 and later
 Microsoft Visual Basic 4.0 and later (32 bit version)
 Borland Delphi 2.0 and later

 Other 32 bit tools may also be able to call NOVLIB functions if they can
 call stdcall C functions in a DLL.

 The following DLLs are all required at program runtime by all 32 bit
 programs that use NOVLIB:

 NOVLIB95.DLL
 NL95FT32.DLL
 NL95FT16.DLL
 NOVLIB.DLL
 NWCALLS.DLL (if using FSWSLoginNW() - see below)

 Import libraries are provided for Microsoft C/C++ (32 bit) and Borland
 C/C++ (32 bit) and are named NOVMVC95.LIB and NOVBCC95.LIB respectively.
 Generally you add a reference to one of these to your project, but if
 you are linking 'by hand', add the filename to your link script or pass
 the filename on the command line to the linker.

 The Microsoft import library is in COFF format, the Borland import
 library is in standard OMF (object module format).

 If you are using a 32 bit C compiler other than Microsoft or Borland you
 may be able to use one or the other of these import libraries, but may
 prefer to create your own import library using tools supplied by your
 compiler vendor to ensure compatability.

 3. Additional and Changed Functions

 The following functions are not described in the printed documentation,
 but are documented in NOVLIB.HLP:

 FSWSLoginNW() (Windows Only)

 To resolve some difficulties logging into NetWare 4.1x servers, please
 use this function in preference to FSWSLogin(). This function will also
 login to 3.x servers.

 This function is only available when using the NOVLIB DLLs, and requires
 the NWCALLS.DLL in order to execute. NWCALLS.DLL can be found in the NOVLIB
 LIB subdirectory on your installation disk.

 Please note that Windows 95 appears to delete NWCALLS.DLL from the
 WIN95\SYSTEM directory when changing Clients from Microsoft to Novell
 and vice-versa. For this reason we recommend installing NWCALLS.DLL in
 the application directory with your .EXE file(s).

 FSDateGet() / FSDateSet() (Y2K issue)

 These two functions have been modified to circumvent a problem in the
 NetWare APIs that was causing these functions to return an incorrect
 date when getting or setting the server date to a date on or after
 01/01/2000.

 FSFileSalvage()

 Salvages (undeletes) a deleted file on a netware volume.

 IPXAddressGet()

 Returns the network address of the station that sent the packet most
 recently received by IPXPacketGet().

 IPXBufferCountGet()

 Returns the number of buffers (4-32) that NOVLIB is using for IPX
 communications.

 IPXBufferCountSet()

 Sets the number of buffers (ECBs) that NOVLIB will use for IPX
 communications. The default is 4, the maximum is 32. If your program
 receives packets very frequently, or appears to miss packets, increase
 this setting.

 IPXEventCountGet()

 Returns the number of IPX packets that have been received by NOVLIB that
 are awaiting retrieval (using IPXPacketGet()).

 NWGetErrorGet() / NWSetErrorGet()

 Certain NOVLIB functions perform a 'get' and 'set' operation - for
 example UsrFullNameSet() returns the current full name of a user, and
 then sets the name to a specified value. NWGetErrorGet() and
 NWSetErrorGet() allow you to determine the NetWare error code if either
 of these operations fail.

 QueAddGet() / QueAddSet()

 Contrary to the printed documentation, the names of these functions are
 actually QueAddStateGet() and QueAddStateSet(). For CA-Clipper the names
 are QueAddStaGet() and QueAddStaSet().

 QueFileAdd()

 Contrary to the printed documentation, QueFileAdd() can be used to add
 local files to a print queue in addition to files residing on a network
 drive.

 QueServerGet() / QueServerSet()

 Contrary to the printed documentation, the names of these functions are
 actually QueServiceStateGet() and QueServiceStateSet(). For CA-Clipper
 the names are QueSrvStaGet() and QueSrvStaSet().

 UsrCurConsoleOperatorTest()

 Determine if the current logged in user is a console operator on the
 current fileserver.

 Changes since NOVLIB 3.10

 WSListFileConn() previously only returned the first 70 connections that
 had the specified file open. This has been corrected.

 CapSetupStringSet() & CapResetStringSet() can now reset the setup string
 to a null string.

 FSUserAdd() Now creates the bindery ACCOUNT_BALANCE item correctly.

 WSMessageSend() was returning FALSE when successful - it now returns
 TRUE as documented.

 IPX system now buffers received IPX packets. (See above)

 Memory leak in IPX system corrected.

 IPXPacketSend() previously could not send packets to a station on a
 different network segment. This has been corrected.

 IPXSocketOpen() was not reversing the high and low bytes of the socket
 number before opening a socket (as required by Netware). In the case
 that the socket number was NOVLIB's default (0x5555) this caused no
 problems. If you were using a socket other than 0x5555 you would have found
 it necessary to reverse the socket number portion of the address passed
 to IPXPacketSend(). This effectively caused NOVLIB to use the wrong
 socket number. This has been corrected, and the socket number portion of
 the address sent to IPXPacketSend() should no longer be reversed.

 FSDateSet() - when called from CA-Clipper (FSDTESET()), this function
 was incorrectly expecting a string type parameter for the date to set.
 This has been corrected to take a DATE type parameter.

 QJBDeferDateSet() - when called from CA-Clipper (QJBDEFDTESET()), this
 function was incorrectly expecting a string type parameter for the date.
 This has been corrected to take a DATE type parameter.

 4. Additional 16 bit Libraries

 Two 16 bit library files are provided that are not mentioned in the
 printed documentation - NOVDOS.LIB and NOVWIN.LIB. If your program is
 linked with the static library file NOVLIB.LIB, you must also link
 NOVDOS.LIB if your program is a DOS program, or NOVWIN.LIB if your
 program is a Windows program. If your program uses NOVLIB.DLL, it is not
 necessary (and you should not) link either of these libraries.

 5. Watcom C/C++ Notes

 16 bit Watcom C/C++ users who are using the static libraries must link
 the file NWATCOM.OBJ, which can be found in the C\OBJ directory of the
 installation directory.

 6. Delphi Notes

 For 16 bit Delphi - the install program places 16 bit version of
 NOVLIB.DCU in the DELPHI\16BIT subdirectory of the NOVLIB installation
 directory. Please copy NOVLIB.DCU and NOVLIB.PAS into your Delphi\Lib
 directory.

 For 32 bit Delphi - the install program places the 32 bit version of
 NOVLIB.DCU in the DELPHI\32BIT subdirectory of the NOVLIB installation
 directory. Please copy NOVLIB.DCU and NOVLIB.PAS into your Delphi\Lib
 directory. If you are using Delphi 3.0 or later, recompile NOVLIB.PAS
 using the batch file (make.bat) in the DELPHI\32BIT subdirectory.

 7. Visual Basic Notes

 For 16 bit Visual Basic - the install program places NOVLIB.BAS in the
 VB\16BIT subdirectory of the NOVLIB installation directory. If required,
 it should be manually copied to your VB directory.

 For 32 bit Visual Basic - the install program places NOVLIB.BAS in the
 VB\32BIT subdirectory of the NOVLIB installation directory. If required,
 it should be manually copied to your VB directory.

 The Visual Basic demonstration programs are saved in Visual Basic 3.0
 format. Visual Basic 4.0 will import and convert these files as requried
 to the new format.

 8. CA-Visual Objects 1.x Notes

 Two AEF's are supplied for CA-Visual Objects, NOVLIBS.AEF which uses
 'strict' syntax and NOVLIB.AEF which uses 'relaxed' or 'Clipper' syntax.
 If you choose to use the 'relaxed' syntax, your program will require
 NOVLIBVO.DLL at runtime, in addition to NOVLIB.DLL. If you choose the
 'strict' syntax, your program will require only NOVLIB.DLL.

 If you are upgrading from NOVLIB 3.00, please note that the library
 names for both NOVLIB libraries have changed slightly (the version
 number is no longer part of the library name). You will have to change
 the properties of your NOVLIB applications to reflect this.

 9. CA-Clipper and Blinker Notes

 NOVLIB 3.30 is fully compatible with Blinker in real mode, dual mode and
 protected mode.

 NOVLIB 3.30 is 99% overlayable when linked with Blinker in real mode, the
 non-overlayable modules are involved with IPX/SPX events and are very
 similar to interrupt handlers. Please use the supplied link script
 (LIB\NOVLIBCL.LNK) when overlaying NOVLIB to force these modules into
 the root of your program.

 If you are using IPX, SPX or print server functions in a CA-Exospace
 protected mode program, please note the following directions:

 NOVLIB 3.3 requires the IPX package be specified when linking with
 CA-Exospace 1.0d and earlier - add the following line to your Exospace
 link script:

 EXOSPACE PACKAGE IPX

 There is a problem in the Exospace IPX package that affects some SPX
 communications functions. For best results we recommend linking with
 Exospace 1.0e or higher when using SPX or printserver functions.
 Computer Associates have corrected the problem in the 1.0e version of
 Exospace by incorporating a new package called IPXCT. If you are using
 Exospace 1.0e add the following line to your Exospace link script in
 place of the line above:

 EXOSPACE PACKAGE IPXCT

 10. Credits

 Blink, Inc
 P.O. Box 29858,
 Richmond,
 VA 23242
 USA.
 Tel (804) 784-2087
 Fax (804) 784-2357
 WWW: http://www.blinkinc.com

 Tech Support email : novlibsupport@blinkinc.com
 Sales email        : sales@blinkinc.com