NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Coexistence with Windows for Workgroups DOCUMENT ID: TID014925 DOCUMENT REVISION: A DATE: 25MAY94 ALERT STATUS: Yellow INFORMATION TYPE: Issue README FOR: NA NOVELL PRODUCT and VERSION: PERSONAL NetWare 1.0 ABSTRACT: This document describes what configuration changes need to be made for PERSONAL NetWare and Windows for Workgroups to coexist. ------------------------------------------------------------------ DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS 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 NOTE: Novell recommends making and verifying a backup of all files on your machine before making any changes. This document describes two methods for allowing Windows for Workgroups and PERSONAL NetWare to coexist. Method 1 is more manual oriented. The second method is performed through more of the Windows configuration utilities. ***************************************************************** Method 1 ***************************************************************** To configure Windows for Workgroups 3.11 with PERSONAL NetWare 1.0, perform the following steps in the order listed: 1. Install Novell DOS 7 (Novell DOS 7 is not required). 2. Install PERSONAL NetWare 1.0. 3. Install Windows For Workgroups 3.11. When Windows for Workgroups 3.11 asks for the Network type, select [ODI/NDIS3]. When Windows for Workgroups asks if you want to update the device drivers, select NO. After the installations are complete, perform the following steps: 1. REM out the SMARTDRV.EXE line in the AUTOEXEC.BAT. 2. Move the NET START and ODIHLP.EXE lines in the AUTOEXEC.BAT to after PERSONAL NetWare's CALL STARTNET line. 3. If the network interface card was running on Frame Ethernet 802.3 before installing Windows for Workgroups 3.11, change the FRAME line in the NET.CFG to the following: ---> FRAME ETHERNET_802.2 4. Run the Novell DOS 7/PERSONAL NetWare SETUP. Answer yes to the question of updating the files for the Windows directory. Install the Novell DOS 7/PERSONAL NetWare diskettes as directed. 5. In the C:\WINDOWS directory, make the following modifications or additions under the appropriate heading, as indicated, to the SYSTEM.INI file: [boot] network.drv=wfwnet.drv secondnet.drv=netware.drv [boot.description] network.drv=Microsoft Windows Network (version 3.11) secondnet.drv=Novell Personal NetWare v1.0 [386enh] network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386 secondnet=vnetware.386, vipx.386 ***************************************************************** Method 2 ***************************************************************** First, you need to get Windows for Workgroups functioning without NetWare or PERSONAL NetWare installed. To do this, complete the following steps: 1. Install and configure Windows for Workgroups 3.11 so that it will run on the ODI shell using IPX. See your Windows for Workgroups documentation for instructions. 2. Verify that it is working (for example, map a drive, print to a shared printer, use the chat program). Next, get the PERSONAL NetWare piece working by completing the following steps: 1. Remark (REM) the following lines that were added by Windows for Workgroups: CONFIG.SYS - the IFSHLP.SYS line AUTOEXEC.BAT - the NET START and ODIHLP.EXE lines 2. Install and configure PERSONAL NetWare to run. See your PERSONAL NetWare documentation for instructions. 3. Verify that PERSONAL NetWare is working from DOS (for example, map a drive, print to a shared printer, use the network diagnostics). Finally, get the two networks to work together by performing the following steps: 1. Verify that the C:\NWCLIENT directory is before the C:\WINDOWS directory on the PATH line in the AUTOEXEC.BAT file. Both networks ship with a NET.EXE utility. Windows for Workgroups needs to run its NET once to start the network. You should specify the full path to it in the AUTOEXEC.BAT to avoid confusion with PERSONAL NetWare. Because PERSONAL NetWare needs to run the NET utility often, C:\NWCLIENT should be first in the PATH. 2. Take the remark statements off the NET START and ODIHLP.EXE lines in the AUTOEXEC.BAT and the IFSHLP.SYS line in the CONFIG.SYS file. 3. Verify that the NET START line contains the full path to the Windows for Workgroups NET command (for example, C:\WINDOWS\NET START). 4. Restart the computer and load both networks. 5. Run Windows. 6. Go into the Windows for Workgroups Network Setup utility. This can be done by opening the Windows Setup icon in the Main program group, and selecting "Change Network Settings..." from the options menu; or by opening the Network Setup icon in the Network program group. 7. Select the "Networks" button. Verify that the "Install Microsoft Windows Network:" radio button is selected. Verify that the "Other:" radio button is selected and that it indicates "Novell NetWare (Workstation Shell 4.0 and above)" as the other network. Then select "OK". 8. Select the "Sharing" button. Verify that the pieces you wish to share with the other workstations on the network are selected. Then select "OK". 9. Select the "Drivers" button. 10. Verify that the proper network interface card (NIC) driver is in place. 11. Verify that the "IPX/SPX Compatible Transport" or the "IPX/SPX Compatible Transport with NetBIOS" driver is loading. 12. Verify that the "Microsoft NetBEUI" driver is loading. 13. Select IPX/SPX as the default protocol. Then select "OK". 14. Select "OK" to close the Network Setup utility and save the changes. You should not replace any of the drivers currently installed. 15. Exit Windows to a DOS prompt. 16. Edit the AUTOEXEC.BAT file to move the NET START and ODIHLP.EXE lines so they execute after STARTNET.BAT. They need to be moved because they rely on LSL and the MLID drivers that are loaded as part of STARTNET.BAT. 17. Edit the NET.CFG file in the C:\NWCLIENT directory to verify that the correct frame type for your network is loading. IPX will only bind to one frame type. The frame type you want IPX to bind to should be the first one listed in the LINK DRIVER section. 18. Reboot. Start both networks; go into Windows; and verify that both networks are functioning correctly by mapping drives to both networks, printing to printers on both networks, and so forth. Note: Currently, the PERSONAL NetWare network diagnostics will not function properly if Windows for Workgroups is running. To use the diagnostics, verify that the diagnostics pieces are loading (see your PERSONAL NetWare documentation) and exit Windows. You will have to use NET DIAGS (the DOS version). ---------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ----------------------------------------------------------------