Hewlett-Packard Application Notes Whole Product Alliance Program for the OmniBook Family Last Revision 5/9/95 Company Confidential / Preliminary Hewlett-Packard supplies the procedures herein without warranty and will not be liable for damages arising from their use. 6 HP OMNIBOOK 4000 RUNNING OS/2 WARP AND A NOVEMLL CLIENT WORKSTATION - INSTALLING THE OLICOM TOKEN-RING PC CARD Disclaimer: The products listed are not products of the Hewlett-Packard Company, but rather products of third party developers. Such products have not been fully tested and only partially evaluated by HP, and are not endorsed, warranted, or supported by HP. HP expressly disclaims all responsibility and liability for the manufacturing, distribution, marketing, licensing, installation, use performance, maintenance, and support of such products. Readers of this guide are advised to make their own independent verification of the information provided for such products by third party developers. ABOUT THIS DOCUMENT This quick reference guide aids in the installation of an Olicom Token-Ring PC CARD (PCMCIA) card on your Hewlett-Packard OmniBook 4000 running OS/2 Warp and the Novell OS/2 Client Workstation software. Many of the details this quick reference guide are specific to the Omnibook 4000. It is beyond the scope of this guide to provide many of the details of OS/2, Netware Client software for OS/2, or the IBM LAPS installation program. It is assumed that you have experience with DOS, OS/2, and in setting up a network system. To aid in understanding and prevent damage, please read the user reference guides supplied with the software. It is also beyond the scope of this guide to introduce the many different types of networks available and to configure OS/2 for those networks. MINIMUM CONFIGURATION The following table outlines the minimum configuration required to install the Olicom token ring card on an Omnibook 4000. OmniBook 4000 * 8MB of system memory * OS/2 Warp installed prior to using the guide * A copy of LAPS supplied by IBM * Novell OS/2 Client diskettes Olicom Token- * The Olicom Token-Ring Driver Disk Ring PCMCIA version D26.0 card DESCRIPTION To take advantage of OS/2's multitasking capabilities it would be a great advantage to be able to use a LAN card and modem simultaneously. In order to make PC CARDs function properly and to promote standards, the PCMCIA standard body defined card and socket services. The card and socket services is the software interface between a PC CARD or it's drivers and the hardware. Without card and socket services, a different card driver would have to be written for every notebook. Protocol drivers are different, however. A unique LAN protocol driver must be used for the various LAN operating systems and transport protocols desired. This protocol driver must be written to use card and socket services and the desired LAN protocol. OS/2 comes with it's own card and socket services. However, as of this writing, Olicom does not have an OS/2 Warp driver that supports the card and socket services with the ODI or IPX protocol. Olicom does support a driver for NDIS that does uses card and socket services. By installing the Olicom NDIS driver and using a ODI to NDIS translator, IBM's card and socket services can be used. An alternative would be to use the Olicom enabler, OCTENABLE.DOS. However, this enabler captures control of the PCMCIA interface chip and does not allow the IBM card and socket services to work properly, thus preventing the use of modem and other PCMCIA cards. INSTALLATION INSTRUCTIONS The instructions for installing the PC CARD are divided into two parts. In Part 1, you will be asked to install the Novell OS/2 Client software. In Part 2, you will use LAPS to install the correct drivers to enable OS/2 with socket services allowing simultaneous use of the Olicom Token-Ring PC CARD and other PC CARDs such as modems. PART 1: INSTALL THE NOVELL OS/2 CLIENT SOFTWARE Stop: Before going further it is recommended that you make a complete backup copy of your hard disk. If you can't make a complete backup of the entire hard disk, backup the OS/2 CONFIG.SYS file. This file will be modified. If there is a problem you will be able to recover your original configuration by replacing any modified file with the backup. 1. Install the Novell OS/2 Client software on the disk. To do so open a OS/2 window and execute the Install program. This is on the Novell OS/2 client diskette WS0S2-1. 2. Pull down the Installation menu and click on Requester on workstation. 3. When the installation program pops up a dialog box entitled Step 1 - Choose the ODI LAN Driver, insert the Olicom diskette Token- Ring Driver Disk. Type into the dialog box a:\ibm\ndis. You will be loading the Olicom NDIS driver at this step. 4. Complete the Install procedure for the Novell OS/2 Client. If you will be running OS2-Win, it's a good idea to install all the support for DOS and Windows sessions. Make sure you load the NetBios Emulation for OS/2 Sessions by clicking on the check box. You may need this later and now is a good time to add it. At one point you will be asked to Copy the ODI LAN Driver Files. You may cancel this step as this will be installed by the IBM LAPS install program. 5. You now need to edit the NET.CFG file to point to the correct IO address of the card. Pull down the Configuration menu in the installation window. Now click on This workstation... Edit the NET.CFG file. Add the appropriate protocols. A typical NET.CFG file may look like this: Link Support Buffers 10 4216 Link Driver OCTOK16 Frame TOKEN-RING Frame ethernet_802.2 Protocol IPX E0 TOKEN- RING Port A80 You have just told socket services to change the default port address of the LAN portion of the PC CARD. In order for this change to become effective, the system must be rebooted. However, you should wait until after completing Part 2 before booting. PART 2: INSTALLING THE PROTOCOL DRIVERS USING LAPS In Part 2 you will be installing the LAN protocol drivers using the IBM supplied LAN Application Protocol Support program. 1. At this point you should still be in an OS/2 Window. Execute LAPS from either a diskette or, if already installed, from the hard disk. 2. Once in the LAPS main dialog window, click on the Install button. The Install Additional Network Drivers dialog box will pop up. Insert the Olicom Token-Ring Driver Disk in the OB4000 diskette drive. Type in A:\IBM\NDIS.OS2 in the box labeled Source. Click the OK button. The Olicom .NIF file and drivers will now be copied to the disk by LAPS. 3. In the LAPS main dialog windows, click on the configure button. The Configure Workstation dialog box will pop up. You will see the Olicom Token-Ring PCMCIA Card in the Network Adapters list box. Click on it to highlight the selection and then click on the Add button. 4. Now add the Protocols you will be using. Click on the IBM Netware Requester item under the Protocols box to highlight it. Now click on Add. Also add the IBM OS/2 NETBIOS support in the same way. Click on the OK button. 5. At this point you need to change some of the default parameters of the configuration. Double click on the Olicom Token-Ring PCMCIA Card... under the Current Configuration box. The Parameters for Olicom Token-Ring PCMCIA Card dialog box will pop up. The dialog box with the title Parameters for Olicom Token-Ring PCMCIA Card will appear. Here are the recommended answers to the parameters: Question Recommended Answer Select card I/O 0A80 addressses Use PCMCIA Card YES Services Ring Speed 4 or 16 Network adapter must be unique address and be in the range of 400000000000- 4FFFFFFFFFFF e.g. 411141114111. Disable NDIS 2.02 NO support 6. Click on the OK button after changing the parameters. 7. Double click on the IBM OS/2 NETBIOS under the Current Configuration window. Add the Network adapter address specified above, e.g. 411141114111. 8. Repeat the step above but for the IBM Netware Requester Support. Click on the OK button when done. 9. The LAPS main dialog box will be displayed. Click on EXIT. Let LAPS update the system files for you and exit the LAPS program. 10. In this step you will have to do some hand editing. Enter your favorite text editor and open the CONFIG.SYS file. LAPS entered all the IBMCOM statements at the end of the configuration file. These statements must be placed before the Netware Requester statements. Use the editor to move these statements. Once completed the tail end of the config.sys file should look like the file fragment below. Note the statement RUN=C:\IBMCOM\OLITOKD.EXE has been added manually. This allows hot insertion according to the Olicom manual. This file can be found on the Olicom Token-Ring Driver Disk. BASEDEV=PCMCIA.SYS BASEDEV=PCM2ATA.ADD /S:2 DEVICE=C:\OS2\MDOS\VPCMCIA.SYS DEVICE=C:\OS2\BOOT\COM.SYS (3,3e8,10) DEVICE=C:\OS2\MDOS\VCOM.SYS (3,3e8,10) DEVICE=C:\OS2\BOOT\AUTODRV2.SYS C:\OS2\AUTODRV2.INI BASEDEV=IBM2TOS1.SYS /s0=2 /c0=15 DEVICE=C:\OS2\APPS\SYSIOS2.SYS rem ************** Added for olicom lan card ********* rem device=c:\os2\olicom\octenabl.os2 ba=A80 ia=11 (see note) NOTE: Used for the point enabler. Ignore RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE RUN=C:\IBMCOM\LANMSGEX.EXE DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2 DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2 DEVICE=C:\IBMCOM\MACS\OLITOK16.OS2 run=c:\ibmcom\olitokd.exe (see note) NOTE: added manually REM --- NetWare Requester statements BEGIN --- SET NWLANGUAGE=ENGLISH DEVICE=C:\OS2\NETWARE\LSL.SYS RUN=C:\OS2\NETWARE\DDAEMON.EXE DEVICE=C:\IBMCOM\PROTOCOL\ODI2NDI.OS2 REM -- ODI-Driver Files BEGIN -- rem DEVICE=C:\OS2\NETWARE\A:\IBM\NDIS (see note) NOTE: not needed REM -- ODI-Driver Files END -- REM DEVICE=C:\OS2\NETWARE\ROUTE.SYS DEVICE=C:\OS2\NETWARE\IPX.SYS DEVICE=C:\OS2\NETWARE\SPX.SYS RUN=C:\OS2\NETWARE\SPDAEMON.EXE DEVICE=C:\OS2\NETWARE\NMPIPE.SYS rem DEVICE=C:\OS2\NETWARE\NPSERVER.SYS RUN=C:\OS2\NETWARE\NPDAEMON.EXE DEVICE=C:\OS2\NETWARE\NWREQ.SYS IFS=C:\OS2\NETWARE\NWIFS.IFS RUN=C:\OS2\NETWARE\NWDAEMON.EXE DEVICE=C:\OS2\NETWARE\NETBIOS.SYS RUN=C:\OS2\NETWARE\NBDAEMON.EXE DEVICE=C:\OS2\MDOS\LPTDD.SYS REM --- NetWare Requester statements END --- Now plug in the Olicom card, connect it to the LAN and reboot the system. Login as directed to you by your system administrator and now you're wired. OTHER CONSIDERATIONS Now that you've gotten your card installed there are some considerations to think about. * When the OmniBook 4000 is suspended, either by timing out or by pressing the suspend button (upper right corner of the keyboard), power to the PC CARD is normally turned off. This conserves power and gives longer battery life. Unfortunately, losing power removes any configuration loaded on the card and it will not respond to the network after coming out of suspend. You can modify this by changing the BIOS setup. Press [Fn] F2 when the machine is on, enter the POWER screen (press F5), and enable PC CARD Power During Suspend. Please refer to the OmniBook 4000 Operating Guide for more information. If power during suspend is not enabled, the machine will have to reboot after each suspend for the card to become initialized. * The OmniBook 4000 shuts off power to the card when the power button is pressed or after suspend to disk. After the computer is turned on power is restored to the card. The card will be not be initialized until after the boot procedure. CONCLUSIONS In this quick start guide you learned how to install the Olicom Token Ring card on the OB4000 running IBM OS/2 Warp. You also learned how to install the Token Ring and NDIS network drivers. After the installation you learned about other salient features of the Omnibook by reading the Other Considerations section. This helped you to become more familiar with your OmniBook 4000 and network usage. Although this application note configured WfW network using the ODI driver, much of what is covered is applicable to NDIS only and other protocol drivers. If later you find yourself having to change network protocol, this application note may help you. REFERENCES HP OmniBook 4000 Quick Start Guide; First Edition: 1994. HP OmniBook 4000 Users Guide; First Edition: 1994. Token-Ring PCMCIA Card Guide to Operations; Publication: OC-3950 v 2.0 Copyright Olicom A/S, Denmark, April 1994 Copyright Hewlett-Packard Co. 1995 This information is subject to change without notice and is provided "as is" with no warranty. Hewlett-Packard shall not be liable for any direct, indirect, special, incidental or consequential damages in connection with the use of this material.