NOTE: In case of problem, displaying the figures of this file, select "System Monospaced" font or any non-proportional font in your text editor option. If you use the E editor, select Set font from the Options pull-down menu. In the EPM editor, select Fonts Settings from the Preferences item in the Options pull-down menu. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 쿟his file contains the following important information concerning the � � IBM* Wireless LAN for an OS/2 environment � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 1. PRODUCT LIMITATIONS. 1.1 Current software level functional restrictions. 1.2 Unsupported systems. 1.3 IBM Wireless code installation. 1.4 RPL function. 1.5 DOS/Windows workstation messages. 1.6 DMA Arbitration level limitations. 1.7 Miscellaneous. 2. PCMCIA PORTABLE COMPUTER SUPPORT. 2.1 Card and Socket Services parameters. 2.2 IBM and OEM personal computer support using PlayAtWill. 2.3 Setting IO base address and Interrupt request level. 2.4 Using the Wireless utilities diskette. 3. GUIDELINES FOR TCP/IP INSTALLATION. 3.1 Installing IBM TCP/IP for DOS/Windows. 4. PARAMETERS TUNING AND PERFORMANCE OPTIMIZATION. 4.1 Netbios. 4.2 TCP-IP using NFS. 4.3 Using DXMT0MOD and DXME0MOD in a DOS/Windows workstation. 5. USING WINDOWS IN A WIRELESS WORKSTATION. 6. OTHER NDIS NETWORK OPERATING SYSTEM ON WORKSTATIONS. 6.1 Using Microsoft Windows for Workgroups (v3.1 or v3.11) 6.2 Using Artisoft LANtastic v5.0 6.3 Using Microsoft LAN MANager DOS Requester. 7. TROUBLESHOOTING / HINTS AND TIPS. 7.1 Workstation registration problem. 7.2 DOS/Windows PCMCIA Problems 7.3 Using 3270 emulation on OS/2 or DOS/Windows 7.4 Obtaining IBM Wireless code level. 7.5 Troubleshooting Worksheet. APPENDIX A : System files samples. APPENDIX B : Microcode upgrade from Utilities diskette. 1. PRODUCT LIMITATIONS. 컴컴컴컴컴컴컴컴컴� 1.1 Current software level functional restrictions. --------------------------------------------------- The current IBM Wireless LAN version does not support Lan Server version 4.0. For more details, contact your IBM Service Representative. 1.2 Unsupported systems. ------------------------ The IBM Wireless LAN does not support i286-based MCA systems. 1.3 IBM Wireless code installation. ----------------------------------- If you are reinstalling or upgrading the IBM Wireless Lan Software, you must stop all wireless applications before starting the Wireless installation procedure. 1.4 RPL function. ----------------- This function has a hardware adapter level prerequisite. Run the Diagnostics from the Utilities diskette and check that the last byte of the Product Change Level is 03 or above. This corresponds to a RPL PROM change level of : 80G2909. If the Product Change Level does not correspond to this prerequisite, contact your IBM representative. The RPL function is not supported on some IBM PS/1 models due to BIOS limitations. If you encounter problems with your IBM PS/2 8580-041 or 8580-071, ask your IBM representative for a BIOS PROM update. 1.5 DOS/Windows workstation messages. ------------------------------------- If you answer NO to automatic update of autoexec.bat, when prompted during installation, then you can retrieve IBM Wireless LAN messages by starting IBMWLDDM.EXE. This file is available from "IBM Wireless LAN DOS/Windows workstation" diskette under path A:\OS2. Along with the message pop-up window, a log file WIRELESS.LOG is created. 1.6 DMA Arbitration level limitations. -------------------------------------- PS/2 Model 9585 : Wireless Adapter DMA Arbitration level must be set to 7, when concurrently used with XGA-2 Video card. PS/ValuePoint : Wireless adapter DMA Arbitration level must be set to 0 or 3 (Possible conflict with Diskette Drive, Multimedia adapters, or Built-in devices). 1.7 Miscellaneous. ------------------ When using IBM Wireless MCA/ISA Adapter on 9577i system, two hang situations may be encountered: - When exiting the system configuration once Adapter installation and configuration is completed. - Any other situation requiring a reset performed through CLT ALT DEL sequence (for example after a system shutdown). This problem is bypassed in both cases by powering OFF ON the system. 2. PCMCIA PORTABLE COMPUTER SUPPORT. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� To operate a Wireless adapter and NDIS Device Driver in a PCMCIA machine, you need to have previously installed and configured the Card and Socket Services support. The chosen set of Card and Socket Services must match the machine model and Operating System used. 2.1 Card and Socket Services parameters. ---------------------------------------- - EMM386 users : (DOS or Windows) When DOS or Windows is used, the memory area used by the Resource Manager (DIRMU01.SYS) and the memory area used by EMS driver (EMM386.EXE) must not interfere with one another. If you are using an EMS manager (EMM386 for example), you must reserve 16K of memory to be used as attribute memory for PC cards. (MA parameter of the resource manager). Example: DEVICEHIGH=C:\DOS\EMM386.EXE RAM X=C000-C3FFF DEVICEHIGH=C:\THINKPAD\DICRMU01.SYS /MA=C000-C3FF - PCMCIA machine with double adapter slot : /S0=2 parameter should be added for Socket Services device. DEVICEHIGH=C:\THINKPAD\IBMDSS01.SYS /S0=2 2.2 IBM and OEM Personal Computer support using PlayAtWill. ----------------------------------------------------------- We recommend you to use PlayAtWill support when using OS/2 WARP. Compatibility problems may exist with non-IBM PCMCIA Card & Socket Services. In such case, "Universal" Card and Socket Services could be used, under product named "PlayAtWill" (Ref : 5764-085). For more information, contact IBM representative. In USA, Call 1-800-IBMCALL IBM, ask for S47. Note: When using PlayAtWill, make sure that no statement from a former Card and Socket Services installation are left in your CONFIG.SYS. 2.3 Setting IO base address and Interrupt request level. -------------------------------------------------------- IBM Wireless Device Driver operating in an OS/2 environment (NDIS), allows you to set-up an IO Base Address and Interrupt Level to operate. These parameters are accessible during installation as a Protocol.ini input (editable by LSP (dxmaid), LAPS or CUSTOM). As a first approach, these parameters may be left blank and once station is started, messages are displayed to indicate the initialized values for IO Base address and Interrupt level. Note that default values for IBM Wireless in NDIS environment are: IRQ= 11 and IOBASE= 0x400. The IOBASE default value or the one set in Protocol.ini file is used by the IBM Wireless software as starting value in the initialization routine. Warning: For IBM Thinkpad 755xx serie, IOBASE Address must be set to 0x220 in Protocol.ini file. The IRQ value set in Protocol.ini file is the value requested to the system. If this value is rejected or if no value is set in the Protocol.ini file, the initialization routine will iterate within the applicable range (11, 15, 5, 10), starting with the default value. Depending on the available resources in the machine you use, initialization routine may end up with another value within the applicable range. Warning: 컴컴컴컴 Sometimes the Resource Manager (part of Card and Socket Services support) returns an IRQ as valid, even if already used by the system. For example the Loud Speaker on Thinkpad 755C uses IRQ 10 by default, the Pen interface on Thinkpad 750P uses IRQ 5... Use your Thinkpad Utilities (PS2 on DOS) or specific PCMCIA System configuration in OS/2 to check what is really used by your machine, and decide to change the IRQ used by the system or by the Wireless application. Once potential conflict is identified, a switch could also be added to the Resource Manager Device statement in CONFIG.SYS file to specify the interrupt request levels that cannot be used by the PC card. Example for 755C with loud speaker using IRQ 10: DEVICE=C:\THINKPAD\DICRMU01.SYS /IX=10 In this case, IRQ 10 cannot be used by the PC Card and will be reserved to the loud speaker. Initialization failure: 컴컴컴컴컴컴컴컴컴컴컴� At boot time, IBM Wireless driver will return messages indicating if the initialization was successful or not. In case of initialization problem, a specific message will indicate the origin of the problem. Basically, these messages refer to Card and Socket Services problems (not found, improper version or not correctly parameterized), or to IObase Address or Interrupt level assignment problem. In case of IOBaseAddress or Interrupt problem, you will need to replace the default values by values taken from the applicable range. (Refer to range provided during LSP or LAPS edition). 2.4 Using the Wireless utilities diskette. ------------------------------------------ Utilities diskette provides a set of functions: Diagnostics, RSSI test, Microcode update. If you encounter problems when booting the Utilities diskette, you would need to modify your Utilities diskette CONFIG.SYS file to call Card and Socket Services support. This may be the case if your PCMCIA machine does not have an INTEL 82365SL port controller. To do so, refer to "Installing and Operating Your Network" ( ION Part 1, Chapter 4) to modify the CONFIG.SYS file of this diskette. If you have compatibility problems with Card Services you can remove Card Services to use the Socket Services Support. 3. GUIDELINES FOR TCP-IP INSTALLATION. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 3.1 Installing IBM TCP-IP for DOS/Windows. ------------------------------------------ Step 1: Follow IBM Wireless LAN Services Installation see Installation and Operating Your Network Part 3, chapter 11. Step 2: Install IBM TCP-IP. Step 3: Using a text editor, append file NDISWL.DDI (installed by step 1 in the wireless directory) on TOP of the file NDIS.DDI (installed by step 2 in the TCPIP directory, C:\TCPDOS\ETC ). Step 4: Run CUSTOM provided in step 2. Note 1: When prompted "insert IBM TCP/IP for DOS Disk D1", use "IBM Wireless DOS/Windows Diskette". Note 2: Editable IBM Wireless Adapter parameters must be entered with quotes, except for COUNTRYCODE, INT and PORT. Example : NETWORKID = "CELL01" COUNTRYCODE = 1 4. PARAMETERS TUNING AND PERFORMANCE OPTIMIZATION. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 This section provides some guidelines to optimize the performance of the IBM wireless LAN. In case of heavy traffic in your wireless LAN cell, it is IMPORTANT that you follow those guidelines. 4.1 Netbios. ------------ In each wireless workstation, Netbios parameters can be changed to increase traffic robustness and Performances. If you do so, you will have to set the same values in all your Netbios session partners : Workstations and Lan Servers (either located in your stand-alone Base or on your backbone). Under DOS these updates must be done using DXMAID. Under OS/2 these updates must be done using LAPS. For operating instructions, please refer to "IBM Wireless LAN, Installing and Operating Your Network": To run DXMAID see: Setting Up a DOS Wireless Workstation, IBM WIRELESS LAN NDIS DRIVER Installation. To run LAPS, see: Setting Up an OS/2 Wireless Workstation, IBM WIRELESS LAN NDIS DRIVER Installation. The following values are given for example, they reflect a medium wireless network (10 workstations). In case of problems running a higher number of workstations, you must increase mainly NETBIOSTIMEOUT, T1 and T2. Applicable range and parameters rules are available using specific Range and help pushbuttom during NETBIOS edition. 4.1.1 Parameters edition on OS/2 machine: ----------------------------------------- LAPS editable parameters for NETBIOS Protocol.ini output used on OS/2 machines. DLC Retries : 8 DLCRETRIES = 8 NETBIOS Retries : 8 NETBIOSRETRIES = 8 Query timeout : 500 NETBIOSTIMEOUT = 500 Adaptive windowing interval : 1000 ADAPTRATE = 1000 Response timer - T1 : 4000 T1 = 4000 Acknowledgment timer - T2 : 2000 T2 = 2000 4.1.2 Parameters edition on DOS/Windows machines: ------------------------------------------------- - NETBIOS using DXMT0MOD: In this case referenced parameters are not present in PROTOCOL.INI file, but are appended with DXMT0MOD.SYS device in CONFIG.SYS file. TT (Transmit.Timeout) 1 (500ms) TC (Transmit.Count) 8 RC (DLC.Retry.Count) 8 TI (DLC.Ti) 10 (30s) T1 (DLC.T1) 9 (4/5s) T2 (DLC.T2) 10 (2/2.4s) - NETBIOS using DXMJ0MOD: (Parameters edited from Protocol.ini file) DLCRETRIES 8 NETBIOSTIMEOUT 500 (ms) NETBIOSRETRIES 8 ADAPTRATE 1000 (ms) TI 30000 (ms) T1 4000 (ms) T2 2000 (ms) 4.1.3 DOS LAN Requester (Lan Server 3.0). ----------------------------------------- In the case of a large number of wireless workstations, you may need to change /WRK parameter in DOSLAN.INI file. This setting has an impact on the frame size. He splits the frame size by 2 and turns off windowing mechanism in data exchanges. This setting must be done to improve traffic robustness, but has a negative impact on pure performance. /WRK:111121101021211 (last bit turned to "1") 4.1.4 OS/2 LAN Requester (Lan Server 3.0). ------------------------------------------ In case of large number of wireless workstations, you may need to change following parameter in IBMLAN.INI file : sesstimeout = 3600 4.2 TCP-IP using NFS. --------------------- Depending on the number of wireless workstations, timeout may occur copying files. In order to prevent this problem, you must act on the following parameters: OS/2 Operating system: ====================== Edit "TCPSTART.CMD" file (C:\TCPIP\BIN) and add parameters on NFSSTART call as follow, example for 12 wireless workstations: call nfsstart -t10 -r10 where -t10 is the timeout (10 seconds). where -r10 is the number of retry (10 retries). DOS/Windows Operating system: ============================= edit "tcpdos.ini" file (C:\TCPDOS\ETC) and modify as follow in NFS section, example for 10 wireless workstations: Default.Timeout = 10 Default.Retries = 10 Default.Read = 2048 Default.Write = 2048 NOTE : If you still have some "extended error 51" , check that the MTU size of both your NFS client and NFS server are the same. Then if the problem is still present reduce the Default.Read and Default.Write values and increase Default.Timeout and Default.Retries values. 4.3 Using DXMT0MOD and DXME0MOD in a DOS/Windows workstation. ------------------------------------------------------------- DXMT0MOD coexistence with DXME0MOD implies that additional Adapter resources are added and some parameters tuned. (Mainly ES and EST for DXMT0MOD driver). Changes for DXMT0MOD must reflect the following: 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� DEVICE=C:\LSP\PROTMAN.DOS /I:C:\LSP DEVICE=C:\LSP\IBMWL.DOS DEVICE=C:\LSP\DXMA0MOD.SYS 001 DEVICE=C:\LSP\DXME0MOD.SYS N ,12 DEVICE=C:\LSP\DXMT0MOD.SYS ES=1 EST=1 C=16 N=16 O=N Basically, the "C=" parameter sets NETBIOS commands to be used by DOS LAN Requester. These are typically the defaults required for DLR. The parameter "O=N" states that the DXME0MOD.SYS driver will not open itself the adapter, but rely on an application to open it. The parameter "ES=" sets the number of non-NETBIOS SAPs to be opened. The parameter "EST=" sets the number of non-NETBIOS Link Stations to be opened. These requirements are not specific to Wireless and must be taken care of as for any Lan adapter using LSP support. Note that Dos Lan Requester has dependencies on these parameters. Please refer to Lan Support Program, LAN Server 3.0 NAR Volume 2 Performance Tuning Chapter 4 page 4-2 to 4-12 for more details. 4-12 for parameters combination. Along with parameters tuning, memory tuning should be considered. Basic rule is to move some device to High memory. Utilities like RAMBOOST may be used (or an equivalent, depending on the DOS version you are using). 5. USING WINDOWS IN A WIRELESS WORKSTATION: 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� If you are using a PC with an MCA bus, you must add MCADMA=OFF statement in the 386Enh section of the SYSTEM.INI file. When running the IBM Wireless LAN in the Windows environment, LAN applications running in a DOS Windows may encounter "loss of connection" problem when performing heavy data transfer. It is therefore recommended to use the "exclusive" attribute provided by Windows, and to use DOS full screen mode. 6. OTHER NDIS NETWORK OPERATING SYSTEM ON WORKSTATIONS 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 6.1 Using Microsoft Windows for Workgroups (v3.1 or v3.11). ------------------------------------------------------------ The Microsoft Windows for Workgroups version 3.1 or 3.11 Network Operating System supports the IBM Wireless Adapter as a new compliant adapter compatible with its Netbeui communication protocol. First follow step 1 (IBM wireless LAN services installation) for a windows Wireless Workstation in the "Installing and Operating your Network" guide. Then, install the IBM wireless LAN NDIS driver on the workstation: The IBM Wireless LAN DOS/Windows workstation diskette contains the OEMSETUP.INF file required to install a third party device driver. The required DOS Device drivers are in the DOS directory of the diskette. Refer to your Windows for Workgroups documentation to know how to install "Unlisted or Updated Network-Adapter Drivers" with this OEMSETUP.INF file. To configure the IBM Wireless LAN Adapter after installing it, access the Advanced Option windows according to your Windows documentation about changing Network-Adapters Settings. When the IBM Wireless Adapter Advanced Option window is displayed : o Keep YES selected for Compression if you want data compression on your wireless communications. o Select Country Code and Enter the Country Code Value. o If your network uses LAA's, select Locally Administrated Address and enter a value. o Select Network Name and enter the value. (always in Upper Case). o Select Workstation Name and enter the value. (always in Upper Case). o Do not fill in the Workstation Security code and the Data Masking fields at this time. o In addition, fill in PCMCIA Interrupt Level and I/O Base Address field if appropriate. Chapter 2 give information about PCMCIA machines support. Validate this installation and configuration, then restart your computer to start the IBM Wireless LAN network. Report to the "Installing and Operating your Network" for IBM Wireless LAN Installation Checking or for installing security in the network with the Advanced Options setting of the IBM Wireless Adapter. In the IBM Wireless Adapter Advanced Option window, you must enter the value of the workstation security code surrounded by double quotes. ex: workstation security code: "123456789123456789" 6.2 Using Artisoft LANtastic v5.0. ---------------------------------- The Artisoft LANtastic v5.0 /AI operating System supports the IBM Wireless LAN adapter and the IBM LAN support program NetBios Interface as a new compliant communication stack. Therefore, in addition to Lantastic, you need to install the IBM Lan Support program on your workstation. During the LANtastic installation, you need to select the option "Other NETBIOS compatible Network Adapter" in the field Network Adapter Installed. If you have installed it with another choice, you need to re-install Lantastic. Then, follow steps 1, 2 and 3 of the section "setting up a DOS wireless Workstation" (or "setting up a Windows Wireless Workstation) for OS/2 base", in "Installing and Operating your Network" guide. Netbios must be the protocol used above the IBM wireless LAN adapter in the Lan Support program installation. 6.3 Using Microsoft LAN MANager DOS Requester. ----------------------------------------------- The Microsoft LAN MANager DOS Requester version 2.2 supports the IBM Wireless as a new compliant adapter compatible with its Netbeui communication protocol. First follow step 1 (IBM wireless LAN services installation) for a DOS Wireless Workstation in the "Installing and Operating your Network" guide. Then, install the IBM wireless LAN NDIS driver on the workstation. The IBM Wireless LAN DOS/Windows NDIS driver will be installed on a Microsoft LAN MANager DOS requester as a 'third party' device driver. Refer to your LAN MANager documentation to know how to install "others Network Adapter" on your workstation. Note that during the installation, you will be prompted for the diskette containing the device driver and necessary configuration files. At that time, insert the IBM wireless LANDOS/Windows workstation diskette. Among other files, this diskette contains the IBMWL.NIF and PROTOCOL.INI file. To configure the IBM Wireless LAN Adapter after installing it, edit with a DOS editor the PROTOCOL.INI file located by default in the LANMAN.DOS directory and according to the information in it, change the needed values of the field depending on your configuration and according to their definitions. Remark : o Do not fill now all the security fields o Take care in editing this file because it is a critical one and its syntax is very important. o All lines beginning by a semi colon are comment lines. Validate this installation and configuration, then restart your computer to start the IBM Wireless LAN network. IBM Wireless LAN for LAN MANager DOS Requester networking workstation installation is now completed. Report to the "Installing and Operating your Network" for IBM Wireless LAN Installation Checking or for installing security in the network (you will need then to edit the PROTOCOL.INI file of LANMAN.DOS to change security parameters). 7. TROUBLESHOOTING / HINTS AND TIPS. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� This section give additional information, to be considered along with Part4. Appendix A. of the Installation and Operating Guide. Before calling your IBM Service Representative, we invite you to review usual error cases and then to fill in the Troubleshooting Worksheet. 7.1 Workstation registration problem. ------------------------------------- We remind you that an installation checker is available for DOS, Windows, and OS/2 workstations. It provides checking on System files (Config.sys, Protocol.ini... ). It is invoked from prompt with: CHKPARMS (OS/2), CHKPARMD (DOS) or CHKPARMW (Windows). A registration problem will correspond to a all "-" or all "red" RSSI indication, this could be due to an adapter not opened or to an open failure. Adapter opening results in the station to register to the base. In case of adapter "not OPENED", protocol and application Open conditions must be checked: Some protocol stacks like DXMT0MOD.SYS (DOS NETBIOS) will not initiate the open unless a specific keyword O=Y is specified. Otherwise, the adapter will be opened only if corresponding application is started (DOS Lan Requester). This the same condition when DXME0MOD.SYS (DOS 802.2) is used with PC3270. In case of OPEN failure, an error message is appended to the LANTRAN.LOG (OS/2) and WIRELESS.LOG (DOS and Windows) files. This message indicates the cause of the error. 7.2 DOS/Windows PCMCIA Problems ------------------------------- Compatibility Problem Determination To investigate why the IBM Wireless LAN device driver does not load on a PCMCIA environment at the initial boot after the installation, you may use the Utilities diskette to eliminate potential Card and an Socket Services compatibility problem. - Edit CONFIG.SYS file of the Utilities diskette, and add the Card and Socket Services statements used in the C:\CONFIG.SYS file. Then, boot your system with this diskette. CASE 1: If the Utility invoked works correctly, the problem is due to the C:\CONFIG.SYS file statements. . It is recommended to remove the EMM386 statement from the C:\CONFIG.SYS file. . If your applications require it, you can add it back later and you must exclude 16K from the EMS manager memory usage and specify the same memory range for the Card Services resource manager usage. CASE 2: If the diagnostics still do not work and as an alternative, the user can use the Card and Socket services of another terminal or buy an 'universal' package of Card and Socket Services such as the IBM PlayAtWill. 7.3 Using 3270 emulation on OS/2 or DOS/Windows. ------------------------------------------------ 3270 emulation requires that 802.2 protocol stack is bound to your Wireless Device Driver within your base station. Then your application 3270 profile (either for DOS using PC3270 or with OS/2 using Communication Manager) will need to be customized with the Host information provided by your network administrator, such as IDBLOCK, IDNUM and supported PIU size. When using 3270 emulation from a workstation, through an OS/2 Bridged Base, your Network administrator will need to check if the Base station Token-Ring MAC address is authorized to enter the ring your communication controller is on (Basically Lan Network Managers access control). Another case of failure could come from the number of hops needed to reach the communication controller ring segment from the Bridged Bases: All bridges present between the Bridged Base and the ring segment you want to reach will need to have the appropriate "Hop count". The IBM Wireless Lan OS/2 bridged base, must be considered as a Bridge. 7.4 Obtaining IBM Wireless code level. -------------------------------------- 7.4.1 Getting code levels for OS/2 BASE STATION : (BS, NSBS, NS) ----------------------------------------------------------------- 1/ Run "SYSLEVEL" from OS/2 Prompt and record IBM Wireless application level. 2/ Get Size and Time stamp for DD, typing : "DIR IBMWL*.OS2" from LAPS directory (C:\IBMCOM\MACS). 3/ ADAPTER MICROCODE level is available running Diagnostics from Utilities diskette in "Product Change Level" field. File information and report them to Troubleshooting Worksheet. 7.4.2 Getting code levels for OS/2 Remote Station -------------------------------------------------- 1/ Run "SYSLEVEL" from OS/2 Prompt and record IBM Wireless application level. 2/ Get Size and Time stamp for DD, typing : "DIR IBMWLO.OS2" from LAPS directory (C:\IBMCOM\MACS). 3/ ADAPTER MICROCODE level is available running Diagnostics from Utilities diskette in "Product Change Level" field. File information and report them to Troubleshooting Worksheet. 7.4.3 Getting code level for DOS/Windows Remote station ------------------------------------------------------- 1/ Run "IBMWLLV2" from DOS Prompt and record IBM Wireless application level. 2/ Get Size and Time stamp for DD, typing : "DIR IBMWL.DOS" from LSP directory. 3/ ADAPTER MICROCODE level is available running Diagnostics from Utilities diskette in "Product Change Level" field. File information and report them to Troubleshooting Worksheet. Note : In case of DOS TCP/IP support DD will reside on TCPIP/BIN directory. 7.5 Troubleshooting Worksheet. ------------------------------ PROBLEM RESOLUTION WORKSHEET 旼컴컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿛roblem Description � � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿏etailed symptom � � �- Occurrence � � �- Limitation � � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿎ode Level for � � 쿔BM Wireless LAN : � � �(Base and Remotes) � � �- Wireless Software � ........... � �- Device Drivers � ........... � �- Microcode � ........... � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿛S model and Type � � �(including BUS type)� � �- Base Station � ........... � �- Remote Station(s) � ........... � �- TR adapter type � ........... � � (if Bridged Base) � ........... � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿏isk type(ESDI/SCSI)� � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿚perating Systems � � 쿪nd Software levels � � �(including CSD nbr) � � �- OS/2, DOS, Win... � ........... � �- NTS/2 � ........... � �- TCP/IP � ........... � �- Lan Server � ........... � �- Novell Server � ........... � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿛rotocol Stacks list� � 쿯or each Device Drv/� � 쿌pplications used � � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿘ain errors in Logs:� � �- IBMWLERL.LOG � � �- IBMWLERL.LOG � � �- LANTRAN.LOG (OS/2)� � �- WIRELESS.LOG (DOS)� � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿌ny significant msg � � �(at boot, init, � � 쿪pplications start- � � � up). � � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿙etwork Config : � � � Number of Cells � � � Number of Bases � � � Number of Remotes � � � Backbone attachment� � � Other Bridges � � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿞YSTEM FILES � ODI NDIS � � � � � Copy listed files � AUTOEXEC.NCF (Base) CONFIG.SYS � � on a diskette and � STARTUP.NCF (Base) PROTOCOL.INI � � forward it to � NET.CFG (Remote) AUTOEXEC.BAT (DOS/Win)� � support center. � SYSTEM.INI (Windows) SYSTEM.INI (DOS/Win) � � � CONFIG.SYS � � � AUTOEXEC.BAT (Dos/Win) � � � � 읕컴컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� APPENDIX A: System file sample. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� A.1 CONFIG.SYS for DOS Thinkpad 750 ----------------------------------- DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\WINDOWS\EMM386.EXE NOEMS X=C000-DFFF FILES=30 BUFFERS=50 DOS=HIGH,UMB rem ------------------------ DEVICEHIGH=C:\THINKPAD\IBMDSS01.SYS /S0=2 DEVICEHIGH=C:\THINKPAD\IBMDOSCS.SYS DEVICEHIGH=C:\THINKPAD\DICRMU01.SYS /MA=C000-DFFF DEVICEHIGH=C:\THINKPAD\$ICPMDOS.SYS rem ------------------------ COUNTRY=033,850,C:\DOS\COUNTRY.SYS DEVICEHIGH=C:\DOS\DISPLAY.SYS CON=(EGA,,1) LASTDRIVE=Z STACKS=9,256 DEVICE=C:\IBMVESA\VESA.EXE DEVICE=C:\DOS\ansi.sys SHELL=C:\COMMAND.COM /E:2000 /P DEVICE=C:\LSP\PROTMAN.DOS /I:C:\LSP DEVICE=C:\LSP\IBMWL.DOS DEVICE=C:\LSP\DXMA0MOD.SYS 001 DEVICE=C:\LSP\DXMJ0MOD.SYS APPENDIX B : Microcode upgrade from Utilities diskette. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� You must upgrade the microcode on every station of your wireless Network. IMPORTANT: When you update the adapter functional code on a wireless workstation, data traffic on the wireless workstation is stopped. To update the adapter functional code, take the following steps: 1. Stop the activities: i.e. stop the traffic, bring the station down. 2. Insert the IBM Wireless LAN Utilities diskette in drive A. 3. To restart the computer, press Ctrl+Alt+Del keys. 4. Select "Wireless LAN Adapter Utilities" from the main menu and press Enter. 5. Select "Functional Code Update" from the main menu and press Enter. 6. On confirmation message select "Y" 7. When prompted Insert the diskette containing the code update files (IBMWLMC1.UPD for ISA/MCA and IBMWLMC2.UPD for PCMCIA machines) in drive A and press Enter. NOTE: Code update files are available from CSD distribution center, or from "IBM Wireless Utilities" diskette. 8. On completion message, remove the diskette containing the code update from the drive A. 9. Press F3 to exit. 10.The computer reboots automatically. 11.Resume your activities. ** OS/2,ThinkPad, PlayAtWill are registered trademarks of IBM Corporation. ** Windows, Microsoft LAN MANager DOS, Windows for Workgroups are registered ** trademarks of Microsoft Corporation. ** LANtastic /AI is a registered trademark of ARTISOFT Corporation.