TITLE: NetWare Lite v1.1 and OS/2 v2.x DOCUMENT ID: TID1200395 DOCUMENT REVISION: 2 DATE: 11Apr95 ALERT STATUS: Yellow README FOR: NA NOVELL PRODUCT and VERSION: NETWARE LITE V1.1 ABSTRACT: NA --------------------------------------------------------------------- DISCLAIMER: THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEAN 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: NetWare Lite 1.1 and OS/2 2.x Novell, Inc. and IBM Corp. do not support running NetWare Lite 1.0 or 1.1 on the OS/2 operating system. This document provides information for one system configuration that has appeared to work in a test environment. It is being provided as a courtesy to Novell's users who may wish to experiment with using NetWare Lite under OS/2. This is a "read and try at your risk" document. No telephone, written, or online support of any kind will be provided for using NetWare Lite with OS/2, nor will Novell or IBM provide clarification of any information contained in this courtesy document. The information that follows describes only one possible method of using NetWare Lite 1.1 with OS/2; other methods may be possible. If you decide to experiment with NetWare Lite on OS/2, Novell strongly recommends doing regular backups of your data, which would be appropriate in any environment but even more so in a configuration for which no technical support can be obtained. Please note that your normal NetWare Lite support policy applies whenever you encounter difficulties or have questions with NetWare Lite when OS/2 is not involved. This includes situations in which you are booting DOS off a floppy diskette or when using OS/2 Dual Boot and entering DOS by itself before loading NetWare Lite. Whenever you boot into OS/2 then enter DOS from OS/2 and load NetWare Lite client or server, this means you are running NetWare Lite with OS/2, which is the configuration that is not supported. Support for using the Novell NetWare OS/2 Requester (when NetWare Lite is not involved) can be obtained from Novell resellers or through 1-800-NETWARE. The normal NetWare OS/2 Requester support policy and charges apply for any support provided. The following information describes one method for setting up OS/2 2.x, NetWare Lite 1.1, and the Novell NetWare Requester for OS/2 2.01. This information has generally been successful in a test environment; however, as previously noted, Novell does not guarantee that this configuration will work, and no clarification or support is available on these instructions. The Novell NetWare Requester for OS/2 2.01 is needed to provide the Novell ODI driver support that NetWare Lite 1.1 needs for network communication. The NetWare Requester provides the ODI support to NetWare Lite 1.1 at the OS/2 2.x level, and this is the fastest method of running NetWare Lite 1.1 with OS/2 2.x. However, you could use a virtual image file created from a boot disk to boot a virtual 8086 machine (this process is explained later on). This, in most cases, makes it possible to run the normal DOS ODI drivers in this DOS session and access the network. This would not require the use of the NetWare requester; however, it can be extremely slow compared to using the requester's native OS/2 drivers. Also, access to the network board would be restricted to that DOS session where the DOS ODI drivers are loaded. The NetWare requester allows the whole OS/2 environment to have access to the network board in case you are doing other activities on the network. Remember that NetWare Lite is limited to that DOS session that it is running in and that it does not provide the OS/2 environment with network access or functionality. This limitation in the OS/2 environment is discussed later. The Novell NetWare Requester for OS/2 2.01 is available from Novell, Inc. or through its resellers. The set up and settings listed below is one configuration in which NetWare Lite 1.1 and OS/2 2.x have worked together. These settings may be adjusted further for better optimization depending on the system configuration being used. Running NetWare Lite SERVER.EXE in a DOS SESSION or DOS BOX as shown in Example 2 will cause a multiple NetWare Lite server environment to be slower in responding to commands such as LOGIN, MAP, CAPTURE, and other similar circumstances. This means that when a NetWare Lite command is executed, other Lite servers may need to respond. Therefore, a NetWare Lite server running on a DOS BOX in OS/2 will respond slower because of the time slicing and slow the whole network response time down. Running NetWare Lite as CLIENT.EXE only should cause no network slow down, because this would only be a client machine accessing other servers on the network. This eliminates the slow down of clients accessing a server that is being preempted by OS/2. This configuration of NetWare Lite and OS/2 does not provide GLOBAL support through out OS/2. In other words, a NetWare Lite 1.1 mapped drive letter in the discussed DOS SESSION or DOS BOX does not show up as an available drive in any other OS/2 or DOS sessions. If an ARCNET, TOKEN RING, or other type of network board that uses an upper memory address range, such as D000-D3FF, is used, then the MEM_EXCLUDE_REGIONS setting under the DOS SETTINGS of the DOS SESSION must include that memory area. This is not a requirement of OS/2 but of the DOS SESSION in which you are running the NetWare Lite 1.1 network. A little known fact is that many EGA and VGA boards use INTERRUPT 2; therefore, machines with these video boards should set up the network board with an interrupt other than 2. Additionally, PORT addresses of network boards should be 300 or greater and not at 360, which could conflict with LPT1. REQUIREMENT 1: Getting SERVER and CLIENT to work under OS/2 requires the Novell NetWare Requester for OS/2 2.01 be installed. REQUIREMENT 2: SERVER and CLIENT must be started from a unique DOS SESSION and environment. The DOS SESSION, which SERVER and CLIENT must be started under, must be run from an image file. This image file is created from a bootable DOS diskette. The image file is create by using the OS/2 utility called VMDISK.EXE that is located in the OS2\MDOS subdirectory. This DOS diskette should also contain the following files: COMMAND.COM--from the DOS that created the boot disk, from the root of the boot disk. DOSVIPX.SYS--from the NetWare subdirectory created by the Requester. FSFILTER.SYS--from the OS2\MDOS subdirectory created by OS/2. CONFIG.SYS--set up like shown in Example 1. AUTOEXEC.BAT--set up like shown in Example 2. REQUIREMENT 3: The DOS session's "DOS SETTINGS" should be set up as follows: *DOS session's default settings *1. COM HOLD set to OFF *2. DOS_BACKGROUND_EXECUTION set to ON *3. DOS_BREAK set to OFF *4. DOS_DEVICE empty 5. DOS_FCBS set to 0 6. DOS_FCBS_KEEP set to 0 *7. DOS_FILES set to 40 (OS/2 has problems with DOS_FILES being greater that 45.) 8. DOS_HIGH set to OFF 9. DOS_LASTDRIVE M (Note: This must be any letter other than Z, which is the default.) *10. DOS_RMSIZE set to 640 11. DOS_SHELL should be empty 12. DOS_STARTUP_DRIVE C:\drdos.img (Note: The drive letter and image file name should be what you called it and where you put the image file.) *13. DOS_UMB set to OFF *14. DOS_VERSION nothing selected 15. DPMI_DOS_API DISABLED 16. DPMI_MEMORY_LIMIT set to 0 *17. DPMI_NETWORK_BUFF_SIZE set to 8 18. EMS_FRAME_LOCATION set to NONE 19. EMS_HIGH_OS_MAP_REGION set to 0 20. EMS_LOW_OS_MAP_REGION set to 0 21. EMS_MEMORY_LIMIT set to 0 *22. HW_NOSOUND set to OFF *23. HW_ROM_TO_RAM set to OFF 24. HW_TIMER set to ON 25. IDLE_SECONDS set to 1 (Note: Must not be set to zero. ) 26. IDLE_SENSITIVITY set to 30 (Note: Must not be much greater than 30 or the CPU usage will start peaking. Use the PULSE icon to view OS/2 CPU usage.) *27. KBD_ALTHOME_BYPASS set to OFF *28. KBD_BUFFER_EXTEND set to ON *29. KBD_CTRL_BYPASS set to NONE *30. KBD_RATE_LOCK set to OFF *31. MEM_EXCLUDE_REGIONS empty (Note: You may need to set this option if your network board has a memory address that needs to be excluded.) *32 MEM_INCLUDE_REGIONS empty *33 MOUSE_EXCLUSIVE_ACCESS set to OFF 34 NETWARE_RESOURCES set to NONE *35 PRINT_TIMEOUT set to 15 *36 VIDEO_FASTPASTE set to OFF *37 VIDEO_MODE_RESTRICTION set to NONE *38 VIDEO_ONDEMAND_MEMORY set to ON *39 VIDEO_RETRACE_EMULATION set to ON *40 VIDEO_ROM_EMULATION set to ON *41 VIDEO_SWITCH_NOTIFICATION set to OFF *42 VIDEO_WINDOW_REFRESH set to 1 *43 VIPX_ENABLED 44 XMS_HANDLES set to 0 45 XMS_MEMORY_LIMIT set to 0 *46 XMS_MINIMUM_HMA set to 0 NetWare Lite 1.1 and OS/2 2.x EXAMPLE 1: The CONFIG.SYS of the DOS SESSION should be as follows: device=fsfilter.sys shell=command.com /p /e:512 files=50 buffers=20 device=dosvipx.sys lastdrive=m EXAMPLE 2: The AUTOEXEC.BAT of the DOS SESSION should be as follows: prompt $p$g path c:\drdos;c:\nwlite; share c: cd\nwlite server.exe client.exe EXAMPLE 3: The NET.CFG is in the NWLITE subdirectory on the C: drive if NetWare Lite was set up as a server or client/server, or it would possibly be found on some other drive letter if NetWare Lite was set up as a client only. The parameters in the NET.CFG found in the NWLITE subdirectory (an example is show below) will not be used in the OS/2-NetWare Lite set up; however, it is a good idea to leave it in the NWLITE subdirectory because the SERVER and CLIENT in some cases will use parameters that have been specified in this NET.CFG. # Setup the NE2000 card Link driver NE2000 INT 5 PORT 300 EXAMPLE 4: The NET.CFG that must manually be created during the NetWare Requester installation is located in the OS/2 2.x root directory. This is used by the requester, when OS/2 is booting up, to set up the network board and its environment. The following configuration is an example of a NET.CFG for an NE2000 board. Note that with the NetWare Requester 2.01, which is NetWare 2.x, 3.x and 4.x compatible, has a default frame type of Ethernet_802.2. Therefore, the NET.CFG should contain a frame type definition of Ethernet 802.3, since this is the default of NetWare Lite. Link Driver NE2000 INT 5 PORT 300 frame ethernet_802.3 Protocol Stack IPX SOCKETS 100 EXAMPLE 5: The CONFIG.SYS of the OS/2 2.x environment. The section of the NetWare Requester was added by the Requester installation process. The lines that have "<<<< NEED CHANGING" by them, should have the REMARKing change made to them only if this is a NetWare Lite network only. If native NetWare is involved, then leave them the same (no REMARK). If those lines have been disabled by REMARK, then you will not see a NETWARE RESOURCES line in the DOS SESSION's SETTING options. PROTSHELL=D:\OS2\PMSHELL.EXE SET USER_INI=D:\OS2\OS2.INI SET SYSTEM_INI=D:\OS2\OS2SYS.INI SET OS2_SHELL=D:\OS2\CMD.EXE SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS SET RUNWORKPLACE=D:\OS2\PMSHELL.EXE SET COMSPEC=D:\OS2\CMD.EXE LIBPATH=.;D:\OS2\DLL;D:\OS2\MDOS;D:\;D:\OS2\APPS\DLL;D:\NETWARE; SET PATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2;D:\OS2\INSTALL; D:\;D:\OS2\MDOS;D:\OS2\APPS;L:\OS2;P:\OS2;D:\NETWARE;y:; SET DPATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2; D:\OS2\INSTALL;D:\;D:\OS2\BITMAP;D:\OS2\MDOS;D:\OS2\APPS; D:\NETWARE; SET PROMPT=$i[$p] SET HELP=D:\OS2\HELP;D:\OS2\HELP\TUTORIAL; SET GLOSSARY=D:\OS2\HELP\GLOSS; PRIORITY_DISK_IO=YES FILES=40 DEVICE=D:\OS2\TESTCFG.SYS DEVICE=D:\OS2\DOS.SYS DEVICE=D:\OS2\PMDD.SYS BUFFERS=30 IOPL=YES DISKCACHE=128,LW MAXWAIT=3 MEMMAN=SWAP,PROTECT SWAPPATH=D:\OS2\SYSTEM 4096 6144 BREAK=OFF THREADS=256 PRINTMONBUFSIZE=134,134,134 COUNTRY=001,D:\OS2\SYSTEM\COUNTRY.SYS SET KEYS=ON REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512; BASEDEV=PRINT01.SYS BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD BASEDEV=OS2DASD.DMD SET BOOKSHELF=D:\OS2\BOOK SET EPATH=D:\OS2\APPS PROTECTONLY=NO SHELL=D:\OS2\MDOS\COMMAND.COM D:\OS2\MDOS /P FCBS=16,8 RMSIZE=640 DEVICE=D:\OS2\MDOS\VEMM.SYS DEVICE=D:\OS2\MDOS\VMOUSE.SYS DOS=LOW,NOUMB DEVICE=D:\OS2\MDOS\VDPX.SYS DEVICE=D:\OS2\MDOS\VXMS.SYS /UMB DEVICE=D:\OS2\MDOS\VDPMI.SYS DEVICE=D:\OS2\MDOS\VWIN.SYS DEVICE=D:\OS2\MDOS\VCDROM.SYS DEVINFO=SCR,VGA,D:\OS2\VIOTBL.DCP SET VIDEO_DEVICES=VIO_VGA SET VIO_VGA=DEVICE(BVHVGA) DEVICE=D:\OS2\MDOS\VVGA.SYS DEVICE=D:\OS2\POINTDD.SYS DEVICE=D:\OS2\MOUSE.SYS SERIAL=COM1 DEVICE=D:\OS2\COM.SYS DEVICE=D:\OS2\MDOS\VCOM.SYS CODEPAGE=437,850 DEVINFO=KBD,US,D:\OS2\KEYBOARD.DCP REM --- NetWare Requester statements BEGIN --- DEVICE=D:\NETWARE\LSL.SYS RUN=D:\NETWARE\DDAEMON.EXE DEVICE=D:\NETWARE\NE2000.SYS DEVICE=D:\NETWARE\IPX.SYS DEVICE=D:\NETWARE\SPX.SYS RUN=D:\NETWARE\SPDAEMON.EXE REM DEVICE=D:\NETWARE\NWREQ.SYS <<<< NEED CHANGING REM IFS=D:\NETWARE\NWIFS.IFS <<<< NEED CHANGING REM RUN=D:\NETWARE\NWDAEMON.EXE <<<< NEED CHANGING rem DEVICE=D:\NETWARE\NETBIOS.SYS rem RUN=D:\NETWARE\NBDAEMON.EXE DEVICE=D:\NETWARE\VIPX.SYS REM DEVICE=D:\NETWARE\VSHELL.SYS <<<< NEED CHANGING REM --- NetWare Requester statements END --- --------------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ---------------------------------------------------------------------