For more information about the SSID, Infrastructure Mode, WEP, and other features of this adapter, documents are available at www.aironet.com, at the time of creating this README file. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ INSTALLATION/INITIAL CONFIGURATION: Tip: When you install OS/2 initially, you can select IBM NULL MAC driver as a "place holder" for the real MAC driver you will install later. This approach has several advantages. Since this "place holder" MAC driver uses no physical resources, it cannot cause IRQ or I/O conflicts. Another advantage is that you can install and configure the LAN an TCP/IP components without the MAC install files. NOTE: You must install Card Services for OS/2. If not, the wireless driver will not initialize properly. It is best to install Card Serives before you install the wireless driver. How can you determine if Card Services is installed? If a line containing "PCMCIA.SYS" (characters do not have to be upper case) is NOT in config.sys, card services is NOT installed. Obtain the installation diskette or set of installation files. The minimum set of files is AIRO340.OS2 and AIRO340.NIF. Type "mpts" on an OS/2 command line. Select Configure, Configure. NOTE: "Cisco Systems 340 is the newest name for an adapter which should be compatible with the Aironet PCM4800 adapter. After selecting the second "Configure" button, you will see the panel "Adapter and Protocol Configuration." Part 1, installing the driver files If "Cisco Systems 340" does not appear in the list "Network Adapters", select "Other Adapters" then type the path where these files are. The default is the A: drive. When the correct path is in the window select "OK". After the system installs the files, the "Adapter and Protocol Configuration" menu appears again. Part 2, Initial configuration After the Cisco Systems 340 adapter appears in the list, select it with the mouse. If you have already configured the protocols by using the IBM NULL MAC driver in the "Tip" section above, you can select "Change" to replace the "place holder" null driver, and your protocols may be configured correctly already. In either case, you must configure the adapter's Infrastructure Mode, SSID, and perhaps other MAC parameters via the "Edit" button (see below). If you have not created a "place holder" MAC, select "Add" instead of "Change". After the Cisco Systems 340 appears in "Current Configuration" in the lower part of the panel. Select "Edit" and, at a minimum, set the "Infrastructure" and "SSID" values. The values in these fields must match the other machines with which this machine will communicate. While the cursor is in a configurable field, the F1 key displays help for that field. Part 3, protocol configuration If you have not configured protocols using the "Tip" described above, or if you want to add or change protocols at this point, Go to "Protocols" in the upper right of the panel and add the protocols you want to use with this adapter. If you are using TCP/IP, invoke the configuration via the command TCPCFG or TCPCFG2, depending on which version of TCP/IP you are using. If you are using OS/2 Lan Requester or Lan Server, invoke the Lan Services File and Print install to add this adapter. Part 4, reboot After all this is finished, you must reboot to use the adapter. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ TROUBLESHOOTING: - CAN'T PING OTHER MACHINES (Obviously you should look at the TCP/IP configuration. One method is to run "NETSTAT -a" on the command line. If the other machine is an OS/2 machine, you should run netstat -a on that machine also. If it is Windows NT, you can view it via My Computer->Control Panel-> Network->Protocols.) Is the green light on the adapter on (solid or blinking)? Between the 2 machines that are trying to ping, both must display the green light in the same way, both solid green or blinking. If the green lights display differently, check "Infrastructure Mode" in mpts configuration below. If the green light does not appear, check the Interrupt Number and IRQ mask. In AD HOC mode, the green light should remain solid, while in Infrastructure Mode it should blink. Another cause of the device driver not initializing properly is that IBM Card Services is not installed. IBM card services must be installed in order for this device driver to function. If your machine is an IBM Thinkpad, you can download the latest version from www.pc.ibm.com/us/thinkpad/index.html. The card must be inserted correctly and fully into the PCMCIA slot. The adapter must be installed in the mpts adapter configuration (see above). Start mpts, select configure, configure, then select Cisco340 adapter, select EDIT. Infrastructure Mode must be set to same string, "YES" or "NO", as the other machine. If using access point, must be "YES". See the description of the green indicator light above. SSID must be set to same value as other machines and Access points. Enable WEP Key must be the same not only in machines using the wireless adapters, but also in any Access Points you are using. If Enable WEP Key = "YES" the same WEP key must be defined in all machines and Access Points. Interrupt Number and IRQ Mask select a set of IRQs that the system can assign to the adapter. The IRQ Mask is a more exact way to select an interrupt than Interrupt Number, since the system may not select the interrupt chosen in the Interrupt Number field. If the green light on the adapter does not appear or does not remain, there could be an IRQ conflict. Base I/O Address can usually be left blank, but you can change the I/O address if you believe that the address assigned by card services is incorrect. The configuration fields define the range of acceptable values - PERFORMANCE PROBLEMS: A mismatch of flash level between the adapters and/or Access Points may cause performance degradation. Flash images, at the time of this README.TXT file, are available at www.aironet.com. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ POWER MANAGEMENT: The proper way to remove the Cisco 340 PCMCIA adapter is: Stop all programs using the wireless card. Launch the PC Card Director GUI. Select "Actions" Select slot 1 or slot 2 Push the "Off" button Select "YES" Wait for both lights to go out on the CISCO340 adapter. Eject the card. To insert the card: First, physically insert the card. Wait until the green light on the card comes on and stays on. If you are running TCP/IP, immediately run setup.cmd (\MPTN\SETUP.CMD). Otherwise TCPIP functions will not succeed, and TCP/IP will interfere with other protocols. Did you remember to stop all programs using TCP/IP or other protocols (See "The proper way to remove" above)? If not, you may have to stop them and start them now. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ WEP (WIRED EQUIVALENT PRIVACY ENCRYPTION) There are 3 options in mpts adapter configuration which are directly related to WEP encryption. These are the options, and their help text. In the menu, if your cursor is in the editable value field, the F1 key displays the help information: Volatile WEP key "This parameter specifies the Volatile Wired Equivalent Privacy (WEP) Key. You should NOT define a value for both the Volatile and Nonvolatile WEP Keys. If you do so, the second WEP key will be ignored." Nonvolatile WEP key "This parameter specifies the Nonvolatile Wired Equivalent Privacy (WEP) Key. You should NOT define a value for both the Volatile and Nonvolatile WEP Keys. If you do so, the second WEP key will be ignored. Since it will remain in nonvolatile storage, once written to the adapter, it is not necessary to write it each time you boot the machine. Set the Nonvolatile WEP Key, and then reboot (the key will be written into nonvolatile storage during bootup). To make the key more secure, you may then erase the value in the Nonvolatile WEP Key using the delete key or the backspace key." Enable WEP key "This parameter enables or disables Wired Equivalent Privacy (WEP). NOTE: You should not set this parameter to YES until you have defined one of the WEP keys."