NETWARE CLIENT FOR OS/2 VERSION 2.12 README August 2, 1996 ===================================================================== Table Of Contents 1. RUNNING NETWARE ADMINISTRATOR UNDER OS/2 2. USING THE MAKEDISK.CMD PROGRAM 3. USING THE "SPX SEND TIMEOUT" SETTING 4. USING "INT_DURING_IO" WIN-OS/2 SETTING 5. USING VIDEO_SWITCH_NOTIFICATION WIN-OS/2 SETTING 6. DISABLING CACHE BUFFERS 7. USING FNETX AND NETX 8. LOGGING OUT OF DOS SESSIONS 9. REINSTALLING NETWARE CLIENT FOR OS/2 10. SETTING FRAME TYPES 11. USING AUTO LOGIN 12. USING THE IBM REMOTE INSTALL FEATURE 13. SETTING THE "NETWARE DIRECTORY OFF" PARAMETER 14. USING IPX CHECKSUMS ===================================================================== 1. RUNNING NETWARE ADMINISTRATOR UNDER OS/2 NetWare 4.1 does not have a native OS/2 version of NetWare Administrator. To run NetWare Administrator under OS/2, use a Global DOS/Win-OS/2 session. 2. USING THE MAKEDISK.CMD PROGRAM To make diskettes of NetWare Client for OS/2 software, type MAKEDISK.CMD at a DOS prompt on a DOS machine. (MAKEDISK.CMD will not work from a DOS session in OS/2.) 3. USING "SPX SEND TIMEOUT" SETTING The default and ranges for the SPX SEND TIMEOUT NET.CFG setting in NetWare Client for OS/2 are: Default = 500 milliseconds Minimum = 100 milliseconds Maximum = 6000 milliseconds 4. USING THE "INT_DURING_IO" WIN-OS/2 SETTING ISSUE: When launching a network application in a WIN-OS/2 session, OS/2 appears to launch a DOS box and then return to the WIN-OS/2 session without launching the application. CAUSE: When Global or Private DOS or WIN-OS/2 sessions are running and a file open is requested on the network, the request is redirected through NETX.EXE. When the INT_DURING_IO WIN-OS/2 setting is set to ON, OS/2 sends read and write requests directly to the OS/2 kernel. The OS/2 kernel is unaware that the file has been opened through the shell. The WIN-OS/2 session cannot read the file and fails to load the application. SOLUTION Do any or all of the following: 1. Set the INT_DURING_IO WIN-OS/2 setting to OFF. 2. Do not load NETX.EXE in the AUTOEXEC.BAT for that session. 3. Run the application locally. 5. USING VIDEO_SWITCH_NOTIFICATION WIN-OS/2 SETTING ISSUE: If a WIN-OS/2 IPX/SPX application is launched in full screen mode and the VIDEO_SWITCH_NOTIFICATION WIN-OS/2 setting is set to OFF, the application loses the SPX connection. CAUSE: The context switch does not appear to give any process time when the VIDEO_SWITCH_NOTIFICATION DOS setting is set to OFF and the full screen WIN-OS/2 application is in background. Because of this, no SPX Watchdog packets are responded to and the connection is lost. SOLUTION Set the VIDEO_SWITCH_NOTIFICATION DOS or WIN-OS/2 setting to ON. 6. DISABLING CACHE BUFFERS Caching does not work in NetWare Client for OS/2. The following line should be added to your NET.CFG file under the NETWARE REQUESTER option: NETWARE REQUESTER CACHE BUFFERS 0 7. USING FNETX AND NETX Use NETX if you are using legacy applications where bindery calls are necessary. NETX works at approximately one half the speed of FNETX and it does not support load balanced DOS sessions. Under certain circumstances, NETX can cause on global DOS session to receive a large share of the CPU bandwidth. If you are experiencing significant system slow down when running multiple DOS sessions, try using FNETX instead of NETX. FNETX may work with your legacy applications, but extensive testing of legacy applications was not possible for this release. FNETX is almost as fast as OS/2 file transfer speeds. FNETX supports load balancing for multiple DOS sessions and other enhancements that might improve performance in your environment. FNETX may not be suitable for all applications. 8. LOGGING OUT OF DOS SESSIONS Do not log out from a global DOS session! All connections will be lost and you will not be able to find LOGIN.EXE to log in again. To work around this problem: 1. Log into the network from an OS/2 session. 2. In a DOS session, use the following command: P:MAP INS S1:=P: This will put the NetWare DOS utilities back into your path. IBM is aware of a memory leak problem with the DOS COMMAND.COM that can cause problems in DOS sessions. Contact IBM for an updated COMMAND.COM. You cannot use the CAPTURE /EC command in a DOS session. Ports captured through the VLM API will not sync up with the NETX API. 9. REINSTALLING NETWARE CLIENT FOR OS/2 You might have problems if you are using ODI LAN drivers with IBM's TCP/IP and ODINSUP if you don't choose the "Don't Update Driver" option during the installation. If you allow the installation program to update the ODINSUP driver, you will need edit your CONFIG.SYS file to reenable ODINSUP. (Make a backup copy of your CONFIG.SYS file before reinstalling.) This version of NetWare Client for OS/2 allows you to install to the same drive the installation source files are coming from. For example, you can install from C:\INSTALL\NWCLIENT to C:\NETWARE or other similar paths. The message "Can't Install To The Same Drive" no longer appears. 10. SETTING FRAME TYPES IPX binds to the first frame type listed unless a specific PROTOCOL line is added. 11. USING AUTO LOGIN Do not set up the client for automatic login. If automatic login is set in your CONFIG.SYS file and you have set "DISCONNECT ON" in your NET.CFG file, your machine might hang. If you are not connected to the network and "DISCONNECT" is off, your machine will eventually time out, but it is very slow. 12. USING THE IBM REMOTE INSTALL FEATURE The IBM remote installation features is not supported on the ODI protocol. You should use NDIS instead. 13. SETTING THE "NETWARE DIRECTORY OFF" PARAMETER The "NETWARE DIRECTORY OFF" setting under the NetWare Requester option in the NET.CFG file turns off NDS. All network connections will be in bindery mode. If you use this setting, you must also get the bindery mode NETWARE.DRV to run Windows. 14. USING IPX CHECKSUMS Checksum are done only if the server requires it. There is not NET.CFG setting that supports this feature. ----------------------------------------------------------------- DISCLAIMER Novell, Inc., makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of recreating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell. ------------------------------------------------------------------- TRADEMARKS Novell TradeMarks Novell and NetWare are registered trademarks of Novell, Inc. NetWare Client, NetWare DOS Requester, Novell DOS, Packet Burst, ODI, and SFT III are trademarks of Novell, Inc. Third-Party Trademarks Compaq is a registered trademark of Compaq Computer Corporation. IBM and OS/2 are a registered trademark of International Business Machines Corporation. Microsoft is a registered trademark of Microsoft Corporation. PostScript is a registered trademark of Adobe Systems Incorporated.