NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Updated modular CLIB and DSAPI README FOR: LIBUPF.EXE NOVELL PRODUCTS and VERSIONS: IntranetWare for Small Business NetWare SFT III 4.1 NetWare 4.11 NetWare 4.1 IntranetWare ABSTRACT: This download file contains a released version of the Modular versions of CLIB and DSAPI. These versions are for 4.10, NW 4.10 for OS/2, 4.10 SFT3 , 4.11 NW 4.11 for OS2, 4.11 SFT3 and 4.11 SMP only. The .MSG files are not copied by the install script because they are not necessary at this time. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- ISSUE: Issues Fixed Since LIBUPE Issue: FTPserve processes may hang under heavy usage. The rest of the server is functional, although no new ftp connections can be established. May also apply to the hanging of other applications. Issue: The potential existed to get an "OpenFileSyncCheck" abend when unloading nlms. Issue: Watchdog would delete clib requester bindery connections, (connections established server to server by nlms), when the connection was not in use for log periods of time. Issue: Fixes a problem when unloading LPR_GWY.NLM while print jobs were still printing which would produce the error: "NLM unloaded without deleting all its semaphores" Self-Extracting File Name: LIBUPF.EXE Files Included Size Date Time ..\ LIBUPF.TXT (This file) ICMD.MSG 6298 8-26-97 6:32:06 pm ICMD.NLM 20794 8-26-97 6:32:38 pm LIBUP.IPS 4190 1-7-98 5:00:14 pm PI_INIT.NLM 1491 3-8-96 6:38:16 pm ..\4.X\ ..\4.X\CLIB\ CLIB.NLM 79958 12-15-97 5:08:20 pm FPSM.NLM 16486 12-15-97 5:08:38 pm MATHLIB.NLM 417 12-15-97 4:52:34 pm MATHLIBC.NLM 426 12-15-97 4:52:36 pm NIT.NLM 47772 12-15-97 5:08:06 pm NLMLIB.NLM 88271 12-15-97 5:07:52 pm REQUESTR.NLM 47352 12-15-97 5:07:36 pm THREADS.NLM 83916 12-15-97 5:07:24 pm ..\4.X\DSAPI\ AUDNLM32.NLM 9207 8-28-97 1:31:10 am CALNLM32.NLM 90288 8-28-97 1:22:28 am CLNNLM32.NLM 6416 8-28-97 12:50:26 am CLXNLM32.NLM 5853 8-28-97 1:30:00 am DSAPI.NLM 628 8-28-97 1:28:56 am DSEVENT.NLM 2226 8-28-97 1:31:18 am LOCNLM32.NLM 4441 8-28-97 12:48:50 am NCPNLM32.NLM 104693 8-28-97 1:07:00 am NETNLM32.NLM 168851 8-28-97 6:42:14 pm ..\4.X\NLS\ ..\4.X\NLS\4\ CLIB.MSG 4275 2-11-97 5:31:30 am FPSM.MSG 543 2-11-97 5:34:56 am NIT.MSG 957 2-11-97 5:40:56 am NLMLIB.MSG 3694 2-11-97 5:58:58 am REQUESTR.MSG 897 5-21-97 1:00:36 am THREADS.MSG 9047 2-11-97 6:25:42 am Installation Instructions: INSTALLATION OPTIONS: Method #1 With the INSTALL.NLM through the "Product Options." ** Method #2 Manually copying the file to the server. INSTALLATION INSTRUCTIONS: Method #1 ** 1. Run LIBUPF.EXE unzipping files into their appropriate subdirectories. 2. Copy unzipped file structure to floppy drive or workstation hard drive. 3. Load INSTALL.NLM on server to be updated. RCONSOLE can be used. 4. Go to "Product Options", "Install a product not listed", . 5. Select the drive. if installing from floppy on the file server or from a workstation using RCONSOLE. 6. Select the proper path containing the LIBUPF.EXE files. 7. Press to start the copy. *Note for SFT3 installation: 1. In order to install the files properly to both IO_ENGINE's they must both be up and functioning properly. 2. The INSTALL.NLM must be loaded in the MS_ENGINE System Console on the PRIMARY IO_ENGINE machine. 3. The install will copy the files to both the SYS:SYSTEM directory as well as the C:\NWSERVER directory on each IO_ENGINE. When doing so the dates of the files copied to the C:\NWSERVER directory will change to the date the copy was performed. Method #2 1. Flag old files to N. 2. Copy files to appropriate subdirectory. ( e.g. CLIB.NLM to SYS:SYSTEM ). 3. Flag copied files to RO SH. *Note on MATHLIB.NLM and MATHLIBC.NLM This version of CLIB.NLM does not require a MATHLIB.NLM or a MATHLIBC.NLM. There are some application that run on the server that will require these modules to be loaded. There has been a copy of MATHLIB.NLM and MATHLIBC.NLM that have been placed in the ..\CLIB directory that do nothing but satisfy the load requirement of the application. The application will run as usual. The DSAPI.NLM is a Stub only. The logic for DSAPI has been broken into the NLMs contained in the 4.x\DSAPI directory. DSAPI.NLM will autoload the necessary files. *** Note that the internal date displayed using the modules list on the server will not match the date of the actual physical file. This is normal and does not indicate a problem. ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------