README.PCI 8/1/97 ................................................................ This file may be read online (about 1000 lines) or printed (approximately 15 pages) ................................................................ Please refer to the IBM PCI Token-Ring Adapter Installation and Testing Instructions manual (p/n 41H8875) for the appropriate information. During testing of the IBM PCI Token-Ring Adapter many environments were created and tested to assure proper operation. This README.PCI file will outline some limitations, prerequisites, and problems. Table of Contents: Chapter 1. System prerequisite PCI updates Chapter 2. Systems restricted to 1 IBM PCI Token-Ring adapter Chapter 3. Systems requiring manual PCI adapter configuration Chapter 4. Interrupt assignment and interrupt sharing Chapter 5. PCI bus parity checking and error handling Chapter 6. System PCI performance features Chapter 7. Device Driver Limitations Chapter 8. Machine Specific Limitations Chapter 9. Operating and Networking System Limitations Chapter 10. Installing Windows 95 Novell NetWare Client 32 Chapter 11. Novell NetWare OS/2 ODI Driver Updates Chapter 12. Novell NetWare 4.11 Server Installation Chapter 13. Remote Unattended Install of Windows 95 and NT Adapter Support Phone numbers: -- IBM PRODUCT SUPPORT 1-800-426-7299 Options by IBM HelpCenter 1-800-237-5511 IBM Support Services 1-800-772-2227 IBM Help Center 1-800-565-3344 HelpPC (Canada) -- IBM PC COMPANY BBS For new or updated versions of installation code or the device drivers: United States 919-517-0001 (directory 32) Vancouver 604-664-6464 Toronto 416-956-7877 Montreal 514-938-3022 Winnipeg 204-316-4255 Markham 905-316-4255 Halifax 902-420-0300 You can download the code from the BBS or the Internet. If you are outside the United States or Canada, contact your IBM Marketing representative. -- INTERNET Anonymous ftp to - lansupport.raleigh.ibm.com Or on a web browser: http://www.networking.ibm.com http://www.networking.ibm.com/nes/nestoken.htm http://www.pc.ibm.com ================================================================ CHAPTER 1. Pre-requisite PCI System updates System BIOS Code provides the interface to allow your software to utilize the system's hardware features. A BIOS update is done through software, and generally does not require any hardware changes. Some PCI systems may require a BIOS code update to work properly with high bandwidth PCI devices like the IBM PCI Token- Ring Adapter. If you suspect that your system needs an update, you should contact your system provider to confirm that an update is required, and to get the update for your system. The system's BIOS is used by the device driver to find and access the adapter. The IBM PCI Token-Ring Adapter requires system BIOS to support PCI BIOS Specification 2.0 or later. Symptoms that might indicate your system needs a BIOS update are: A) The IBM PCI Token-Ring Adapter Diagnostics report that no adapter is installed in the system and the adapter LEDs indicate that the adapter is awaiting initialization (alternate blinking of amber and green.) B) The system "hangs" when the IBM PCI Token-Ring Adapter Diagnostics start to access the adapter. These systems may require an update based on when they were manufactured: - IBM PC Server (model 8640) 8640-OPT (Pentium) Requires BIOS level T45 or above 8640-ONJ (486) Requires BIOS level T49 or above - IBM PC 300 and 700 (Pentium models 6575, 6585, 6875, 6885) Requires BIOS level 46 or above - IBM PC 300 (80486 models 6573, 6583) Requires BIOS level 58 or above - IBM ValuePoint Performance Series (models 6484, 6494 or Models 6482, 6492 with PCI feature installed) Requires BIOS level 58 or above - IBM Aptiva (Models 2144-Mxx AND 2168-Mxx) These models of APTIVA may need the latest BIOS, which you can obtain from the PC Company Bulletin Board: 919-517-0001 or by; World wide web - http://www.us.pc.ibm.com/files.html access the 'search form' and then enter MFLASH. Download and then execute the MFLASH.EXE self extracting zip file and follow the instructions in the README.TXT file. or by; Anonymous FTP site - ftp.pc.ibm.com MFLASH.EXE can be found in the pub/ps1aptiva/update_files/bios directory. - Compaq Deskpro XL (Pentium and 486 versions) Requires BIOS dated 8/5/94 or later - Gateway2000 P5-90 (P54C processor) Requires BIOS level 10 or above ----------------- NOTE for Users of IBM ValuePoint Performance Series (model 6384-189) ----------------------------------------------------------------- Requires riser board FRU #71G2782 installed, or the IBM PCI Token-Ring Adapter must be installed in the bottom PCI slot only. NOTE for users of the IBM PC Server, model 8640-0Nx (486): --------------------------------------------------------- Some of the earlier models of the 8640-0Nx will not function properly when the IBM PCI Token Ring Adapter, and a busmastering EISA adapter are used simultaneously. If the system hangs after installing the IBM PCI Token-Ring Adapter and an EISA busmastering adapter, the system may need an updated version of the system planar board (FRU=71G0033). Customers should contact the IBM PC Company Help Center at 800- 772-2227 for assistance. In Canada customers should call IBM's HelpPC at 800-565-3344. ----------------- NOTE for users of the IBM ValuePoint High Performance Models 6484 and 6494: ----------------------------------------------------------------- Some of the earlier models of the 64x4 will not function properly with the IBM PCI Token-Ring Token Ring Adapter. If the system hangs after installing the IBM PCI Token-Ring adapter, the system may need an updated version of the PCI riser card. Customers should contact the IBM PC Company Help Center at 800-772-2227 for assistance. In Canada customers should call IBM's HelpPC at 800-565-3344. NOTE for users of - DELL 466 Models: ----------------------------------- Some Dell 466 models (486DX2 - 66MHz) with a NetWare device driver are unable to find the adapter, but the diagnostic can. If you have such a Dell 466 model you must follow the instructions in the Installation and Testing Instructions, section 5-7 Expansion ROM and PCISETUP that discuss the manual installation of PCISETUP for all environments. ============================================================= Chapter 2. Systems restricted to 1 IBM PCI Token-Ring adapter Some systems can only support a single IBM PCI Token-Ring adapter due to limited PCI-to-memory bandwidth. Symptoms that might indicate a memory bandwidth restriction are: A) Single adapter can attach to the network, but fails if two adapters are active in the system. B) Adapters connect to the network, but then lose connection to the network when the LAN traffic on both adapters increases, or when other system I/O activity increases (disk, video, etc.) ============================================================= Chapter 3. Systems requiring manual PCI adapter configuration Some systems are electrically and physically PCI compatible, but require manual reconfiguration when adding PCI adapters. Repeated here are the required resources (as listed in the IBM PCI Token-Ring Adapter Installation and Testing Instructions, Chapter 2, page 15.) Some systems may only require that a few of these parameters be set manually. The IBM PCI Token-Ring Adapter requires these resources: - Adapter Enable = ON - Bus Master Enable = ON - I/O Location - any available 256-byte address range. - Memory Location - any available 256-byte address range. - Interrupt - Any available interrupt except 0 (IRQ0) (see Chapter 4 Interrupt section below) - ROM Location - Any available 2K-byte ROM address range. (see Chapter 3 ROM Mapping section below) - Latency timer - Any value above (40 hex) 64 decimal (see Chapter 6 Performance section below) ----------------- ROM Mapping: The following message was seen on one Gateway2000 system during the system boot sequence because all of the 'Shadow ROM' had been disabled from the system setup utility. "WARNING: Insufficient PCI Memory Block Use Setup to increase the PCI Memory Block Size." To correct this problem, follow the instructions in the system's user manual to properly configure any required ISA adapter ROM space utilization. Leave remaining ROM address ranges enabled for use by the PCI devices. The IBM PCI Token-Ring Adapter uses 16K bytes at initialize time which reduces to 2K bytes of ROM space at run time (located somewhere between 'C0000'h and 'EFFFF'h.) ================================================================ Chapter 4. Interrupt assignment and interrupt sharing Interrupt assignment and interrupt sharing are two areas in which system-adapter incompatibilities may occur. Interrupt assignment is done by the PCI initialization BIOS code, or manually on systems not providing automatic PCI configuration. There are a few critical factors regarding PCI interrupts: A) The IBM PCI Token-Ring Adapter must have a PCI 'level sensitive' interrupt line assigned. This allows multiple devices to share the interrupt. It is not the same as ISA 'edge triggered' interrupts, which cannot be shared. B) The interrupt assigned must not be shared with any ISA device. It is recommended that PCI interrupts not be shared with EISA, or Micro Channel adapters, although this will work in some systems. C) We recommend that each IBM PCI Token-Ring Adapter be assigned its own interrupt, when possible. Sharing interrupts among PCI devices is allowed by the PCI specification, but some early PCI systems have bugs that can be avoided by not sharing interrupts. D) Interrupt Request Level 0 is reserved for the system timer, and cannot be used for the IBM PCI Token-Ring Adapter. ----------------- When multiple PCI adapters share an interrupt, a problem with one adapter can appear as a functional problem with a different adapter. When debugging system problems try to isolate each adapter on its own interrupt, when possible. ================================================================ Chapter 5. PCI bus parity checking and error handling The PCI specification contains parity checking for all address and data information on the PCI bus. The PCI Specification also allows the system to disable PCI Parity checking. We suggest that for critical LAN attached systems, PCI parity checking be enabled. You may wish to verify with your system provider that PCI parity checking, especially for all memory accesses, is provided in the system. In addition to the PCI architected error checking, the IBM PCI Token-Ring Adapter maintains parity checking throughout the adapter's data path and buffers. This additional error checking is always enabled, even if the system error checking is disabled. ================================================================ Chapter 6. System PCI performance features Most PC systems are performance tuned for CPU and display performance benchmarks. The systems are optimized for CPU accesses to memory and video buffers (both slave devices). This leaves PCI Master devices like the IBM PCI Token-Ring Adapter susceptible to being locked out of memory. A program, called PCISETUP is provided with this adapter to adjust the CPU to PCI access buffering which corrects this problem. This program is resident in the adapter ROM and is automatically run each time you boot your computer. PCISETUP The PCISETUP program is provided in the ROM on the adapter, and is also an executable program on diskettes for those systems in which the ROM is not able to execute. The program looks for specific system chips based on their PCI Vendor ID and Device ID. Based on which chip(s) are found, corresponding modifications are made to specific bits within that chip's PCI configuration registers, or within The PCI configuration registers. Refer to section 5-7 Expansion ROM and PCISETUP of the Installation and Testing Instructions. If you have a different IBM PCI adapter that requires PCISETUP installed on your machine, and you are adding the IBM PCI Token- Ring Adapter, you may need to replace the PCISETUP file installed in your system with the PCISETUP file on Diskette 1 Diagnostics and LANAID. In any case you should use the PCISETUP file with the higher version number. Latency Timer: ------------- The PCI Master Latency Timer sets the limit for how long a PCI Master device can transfer data on the PCI bus. This has a small effect on overall adapter and system performance. On systems that automatically set the Latency Timer value, no change should be necessary. On systems that require manual configuration, we suggest that the Latency Timer be set to at least 64 (decimal), or '40'h (hexadecimal). This is a reasonable setting for all systems EXCEPT on multiple PCI bus systems across a PCI to PCI bridge, we suggest a setting of at least 192 (decimal) or 'C0'h (hexadecimal) because the PCI-PCI bridge must request the main PCI bus on behalf of several PCI devices. In no case should a non-network device driver (IDE, SCSI, etc) have a greater latency timer value than a network device. PCI Extended Commands: ---------------------- The IBM PCI Token-Ring Adapter utilizes PCI data transfer commands designed for high efficiency. 'Memory Read Line', 'Memory Read Multiple', and 'Memory Write and Invalidate' are each used as appropriate for maximum PCI bus throughput. On systems which do not yet implement these commands, they are executed as though they were basic read or write commands. 'Fast Back to Back' accesses allow this adapter to perform multiple data transactions without pausing in between each one. Measurements on currently available 32-bit systems utilizing 33Mhz memory (as in most '486 systems) show a sustained data transfer rate of 25MBytes/sec between memory and the PCI bus. Note: If the system does not allow burst transfers, the sustained data transfer rate will be limited to 8 MBytes/sec. Such systems will generally not support more than 1 IBM PCI Token-Ring Adapter. Measurements on currently available 64-bit systems utilizing 66- Mhz memory (as in most Pentium systems) show a sustained data transfer rate of 75 to 85 MBytes/sec between memory and the PCI bus. Note: If the system does not allow burst transfers, the sustained data transfer rate will be limited to 33 MegaBytes/sec. ISA Device Impact on PCI Performance: ------------------------------------ ISA devices are much less efficient transferring data than PCI, EISA, or Micro Channel devices. A system with the video and/or the disk controller on the ISA bus will have less memory bandwidth available for PCI bus devices to use. In many cases the effect on overall system performance is negligible. In some cases though, high speed graphics screen activity or extensive disk activity can hinder PCI memory transfers. In the extreme case, this can cause the IBM PCI Token-Ring Adapter to drop frames being transmitted or received. For this reason, we recommend that PCI video and PCI disk adapters be used in systems handling critical LAN traffic, rather than ISA based adapters. In some cases EISA video adapters have been shown to interfere with proper operation of the IBM PCI Token-Ring Adapter. ================================================================ Chapter 7. Device Driver Limitations DOS NDIS 2.0 used in WINDOWS FOR WORKGROUPS 3.11 Work Arounds and Restrictions ------------------------------------------------ The following restrictions and work arounds apply to the DOS NDIS 2.0 device driver when used with Microsoft Windows For Workgroups 3.11. IBM is currently working to remove these restrictions and the need for these work arounds in updated versions of this driver. Please check the documented electronic distribution locations or contact IBM support for updates in the near future. 1. No response from Windows (hang) when using Windows For Workgroups 3.11 and its supplied networking support configured for both "Microsoft NetBEUI" protocol and "IPX/SPX Compatible Transport with NetBIOS" on an IBM 6598-CXX. It has been observed on some above configurations that the machine will hang when network activity is started and Windows For Workgroups 3.11 is running. For example, when starting File Manager and remote drives are defined. In configurations using Windows For Workgroups 3.11 on an IBM 6598-CXX machine, it is recommended that the NDIS 3.0 driver for the IBM PCI Token-Ring Adapter or the IBM LAN Client product be used to provide networking support. If it is determined that the NDIS 2.0 driver must be used then one of the following actions must be taken until this problem is resolved. 1.1. Configure just one of the protocol drivers, either "Microsoft NetBEUI" or "IPX/SPX Compatible Transport with NetBIOS". 1.2. If using just one of the above protocols is not possible, then use a NetBIOS protocol stack other than the one supplied with Windows For Workgroups 3.11. For example, IBM LAN Support Program or IBM DOS LAN Services. 1.3. If the Windows For Workgroups 3.11 networking support must be used, then disable, or make unavailable, Interrupt Request level (IRQ) 9 of the machine if possible. 1.4. If disabling IRQ 9 is not possible, then the string /UseIRQ9 should be placed on the Netcard statement of the network drivers section of SYSTEM.INI. The line should look as follows: Netcard= ibmtrp.dos /UseIRQ9 NOTE: If after making the above changes the Network folder is opened and Network Setup is run, be sure to select "Cancel". If "Close" is selected the above change will be lost and SYSTEM.INI should be modified again. 2. Driver unable to load when using Windows For Workgroups 3.11 supplied networking support and the UMB parameter is placed on the DOS= statement in CONFIG.SYS. In certain configurations it has been observed that NET.EXE which loads the DOS NDIS 2.0 driver after DOS initialization is not supplying an adequate amount of memory for the driver to load. When your environment requires the DOS real mode driver (NDIS2) and the CONFIG.SYS line DOS=HIGH,UMB contact IBM for support or change the DOS= line in CONFIG.SYS to read DOS=HIGH. 3. Unable to configure for two adapters with Windows For Workgroups 3.11 networking support. If using only the NDIS 2.0 driver with the networking support of Windows For Workgroups 3.11, only one card can correctly be configured. The Network Setup function of Windows For Workgroups 3.11 does not permit two cards to be configured when using an NDIS 2.0 driver that loads once and drives multiple cards. However, simple manual changes to configuration files can be made to allow this configuration to work. When using the networking support of Windows For Workgroups and the NDIS 2.0 device driver to drive two IBM PCI Token- Ring Adapters, the following steps must be followed: 3.1. From the Network Folder click on the Network Setup icon. Click on the "Drivers" button to add a new Network Driver. On the Network Drivers Screen click on "Add Adapter..." Highlight "Unlisted or Updated Network Adapter" then click on "OK". Insert Disk2 for the IBM PCI Token-Ring Adapter. On the "Install Driver" panel update the drive letter with the location of the diskette that contains Disk2. Click on "OK" Choose the top choice on the "Unlisted or Updated Network Adapter" panel, "IBM PCI Token-Ring Adapter,NDIS2 only" by highlighting it. Click on "OK" 3.2. Do step one again for the second adapter. 3.3. Check to be sure you have selected the correct protocols for each adapter. 3.4. Click on "CLOSE" to return to the "Network Setup" panel 3.5. Click on "OK" to continue with the installation process. 3.6. Windows will now ask if you want to replace Enhanced Mode Protocol Manager files, replace only if necessary. 3.7. Windows will copy IBM PCI Token-Ring Adapter files from the diskette. 3.8. Windows will update the PROTOCOL.INI, CONFIG.SYS, and SYSTEM.INI. Click on "OK" for this information panel. 3.9. Click on "Continue", do not click on "Restart Computer" 3.10. Choose your favorite editor to do the following steps. 3.11. In the Windows Directory (normally \WINDOWS) 3.11a. Update the SYSTEM.INI -under the "network drivers" section locate the line for "netcard=", notice that there is no driver name stated. This only happens when configuring for two adapters. Change the line to read "netcard=IBMTRP.DOS" Save the file. 3.11b. Update the PROTOCOL.INI -under the IBM$TRPN22 section locate the line "DriverName=IBMTRP2$", notice that there is a 2 just before the dollar sign. Remove the "2" just from that line to read "DriverName=IBMTRP$" Save the file. 3.12. Shutdown and reboot the system. NOTE: If after making the above changes the Network folder is opened and Network Setup is run, be sure to select "Cancel". If "Close" is selected the above changes will be lost and steps 3.11a and 3.11b should be performed again. 4. No response from Windows (hang) when using high volume LAN traffic applications within a windowed DOS session of Windows For Workgroups 3.11. A recoverable hang condition has been observed in a couple of configurations where a DOS based LAN application that creates a large volume of LAN traffic is run within a windowed DOS session in Windows For Workgroups 3.11. Until the final solution is found for this situation, it is recommended that DOS based LAN applications creating a high volume of traffic be run in a DOS full screen session. IBM Networking Hardware development is working with Microsoft to resolve this problem within Windows For Workgroups 3.11. If this problem occurs, contact IBM for support. NDIS 3.0 used with WINDOWS FOR WORKGROUPS 3.11 Work Arounds and Restrictions ----------------------------------------------------------------- The following restrictions and work arounds apply to the NDIS 3.0 device driver. IBM is currently working to remove these work arounds and restrictions in updated versions of this driver. Please check the documented electronic distribution locations or contact IBM support for updates in the near future. 1. A recoverable hang condition has been observed when DOS based LAN applications that create a large volume of LAN traffic are run in two or more DOS sessions using the NDIS 3.0 device driver within Windows For Workgroups 3.11. Until this problem is resolved, it is recommended that high volume DOS based LAN applications be run only in one DOS session at a time. IBM Networking Hardware development is working with Microsoft to resolve this problem within Windows For Workgroups. NDIS 2.0 used with DOS and WINDOWS 3.x Restrictions and Work Arounds ------------------------------------------------------------- The following restrictions and work arounds apply to the DOS NDIS 2.0 device driver when used with Microsoft Windows 3.x. IBM is currently working to remove these restrictions and the need for these work arounds in updated versions of this driver. Please check the documented electronic distribution locations or contact IBM support for updates in the near future. 1. No response from Windows (hang) when using high volume LAN traffic applications within a windowed DOS session of Windows 3.x. A recoverable hang condition has been observed in a couple of configurations where a DOS based LAN application that creates a large volume of LAN traffic is run within a windowed DOS session in Windows 3.x. Until the final solution is found for this situation, it is recommended that DOS based LAN applications creating a high volume of traffic be run in a DOS full screen session. IBM Networking Hardware development is working with Microsoft to resolve this problem within Windows 3.x. If this problem occurs, contact IBM for support. 2. Certain software environments prevent the IBM PCI Token-Ring Adapter from correctly resetting when the Control-Alt-Delete key sequence is entered. This may cause the system to hang during the reboot process. If the machine hangs while rebooting, the machine must be turned off and then back on again. Many system vendors have a BIOS update that will correct this problem. If you experience this problem, please contact your system vendor for possible updates to the BIOS to disable the busmaster enable bit during system reset, as recommended by the PCI Special Interest Group (SIG). ================================================================= Chapter 8. Machine Specific Limitations ALL SERVERS and CLIENTS ----------------------- On some machines during boot up, the RPL Panel is displayed when you intend not to RPL the machine. You may correct this by either using the BIOS configuration utility of your machine to change the startup sequence boot from the hard file first, or disable the RPL option on the adapter by using LANAID or the Diagnostic. IBM PC SERVER 300 Models 8640-xPx --------------------------------- 1. These models of the IBM PC Server 300 only support one IBM PCI Token-Ring Adapter, working only in half-duplex mode. Call IBM service for the latest information. 2. A failure has been observed on an 8460-OPT system. When loading an NLM from the DOS partition (C:\) of the hard disk that also contains the NetWare partition (SYS:) the system may 'hang' with the hard drive activity light on. The problem only occurs when the hard drive and LAN adapter share the same interrupt, and the LAN is active. The problem can be avoided by installing all NLMs and other related files onto the NetWare partition; or, Load all required NLMs prior to starting the LAN connection (before 'BIND IPX to...') If you continue to experience problems with the IBM PC300 Model 8640-OPT using Novell's NetWare, please call IBM for further information. COMPAQ PRESARIO 9546 -------------------- The IBM PCI Token-Ring Adapter does not work reliably in the Compaq Presario 9546, and we do not recommend its use in this machine. MICRON MILLENNIA PLUS P133 ------------------------- A system cache data problem might exist when using the Micron Millennia Plus P133 (M54Hi system motherboard) with the IBM PCI Token-Ring Adapter. Please contact Micron or IBM Technical Support for the latest compatibility information. IBM 8272 TOKEN-RING SWITCH -------------------------- The microcode in the IBM 8272 Token Ring Switch must be at fix level 2.06a or higher. 8272 upgrades are available from the following web site: http://www.networking.ibm.com/nes/nesswitc.htm IBM PC SERVER 704 when running WINDOWS NT ----------------------- Machine will fail or results will be unpredictable. Problem is corrected by changing the Multi-Processor Specification (MPS) setting in the BIOS to 1.4 (vs. the default setting of 1.1). Select BIOS UPDATE; choose ADVANCED MENU; choose CHIP SET CONFIGURATION; click on MPS and select 1.4. IBM PC SERVER 720, MODEL 8642 ----------------------------- The IBM PC Server 720, Model 8642 does not currently support the IBM PCI Token-Ring Adapter. As of this writing (September 1996) IBM is preparing an update to the PC Server 720's "DPB Bridge Card" to correct a problem that can cause unreliable operation of some PCI bus master devices including the IBM PCI Token-Ring Adapter. When ready, the new DPB Bridge Card will be available as an update for existing systems, and will begin shipping in all newly manufactured systems. A preliminary assembly part number of 76H7133 has been assigned to the updated DPB Bridge Card. Contact IBM support for the latest information. IBM PC 100 MODEL 6260 --------------------- When the IBM PCI Token-Ring Adapter is installed in the IBM PC 100 Model 6260 with BIOS level 10, the machine will attempt to IPL from the network (RPL) when powered up or rebooted. To prevent this from happening, either: 1. Use the system BIOS utility to set the hard drive as the primary boot device, or 2. Run LANAID or the diagnostic and disable RPL on the adapter. ================================================================= Chapter 9. Operating and Networking System Limitations NOVELL NETWARE SERVER IBM LAN CLIENT NOVELL CLIENT32 ------------------------------------------------------------ In Novell'S NetWare Server, or IBM LAN Client, or Novell's Client32 if you want to use a second frame type, use the "frame=" parameter in the driver load statement to specify the second frame type. Novell CLIENT32 with Multiple IBM PCI Token-Ring Adapters --------------------------------------------------------- If more than 1 IBM PCI Token-Ring Adapter is to be used with Novell's Client32, please refer to Novell's documentation for information on how to properly load additional drivers. EMM386 earlier than RELEASE 4.49 -------------------------------- The IBM PCI Token-Ring Adapter's device drivers for DOS will occasionally hang or re-boot the system if an early level of EMM386 is active. EMM386 must be at Release level 4.49 or higher (included in versions of Microsoft DOS 6.3 or higher or IBM DOS 7.0) when utilizing 32-bit accesses to PCI BIOS, or ISA Plug and Play BIOS. If you use the IBM PCI Token-Ring Adapter with an older level of EMM386, your system may hang immediately when the adapter's device driver is loaded, or at some time later during operation of the adapter. Contact your operating system supplier, or Microsoft for information on obtaining an updated EMM386 driver. The latest EMM386 is available on Microsoft's BBS system. OS/2 LAN Server --------------- A potential data corruption problem exists with LAN Server versions 3.0, 4.0, and 5.0. The problem can occur with the IBM PCI Token-Ring Adapter and other LAN adapters when they are operating under heavy network traffic conditions. To fix the problem you must install the following: LAN Server 5.0 - WARP Server ---------------------------- + Fix Pack IP08260 + Fix Pack WR08210 for MPTS LAN Server 4.0 -------------- + Service Pack IP08222 + Fix Pack IP08227 + One of the following: - Fix Pack WR08210 for: - LAPS V2.60.5 (Warp Connect) - LAPS V2.60.6 (Comm Mgr 2.0) - LAPS V2.60.7 -or- - Fix Pack WR08163 for: - OS/2 2.x - LAPS prior to 2.60.5 NOTE: The above fixes are only available from IBM's Personal Software Solution Center. For assistance call: 1-800-992-4777 LAN Server 3.0 -------------- If the data corruption problem is encountered with LAN Server 3.0 it can only be corrected by upgrading to LAN Server 4.0 or later. ================================================================ Chapter 10. Installing Windows 95 Novell NetWare Client 32 The installation instructions in the IBM PCI Token-Ring Adapter manual assume that the NetWare Client 32 for Win95 software was installed on the computer before the adapter was inserted into the computer. If the NetWare Client 32 for Win95 software was not installed prior to inserting the adapter into the computer the installation procedure in the manual will fail. The steps below will correct this problem and install the NetWare Client 32 for Win95 correctly. (See notes below for additional setup information. For CD-ROM, replace A: with d:\IBMTRPCI\LANAID in these instructions.) 1) Have Windows 95 up and running on the computer. 2) Open the control panel and double-click on the System icon. Click on the Device Manager tab. 3) Click on the IBM PCI Token-Ring Adapter in the Network adapters section (there will be a red X over the adapter icon). Click Remove. Click OK in the Confirm Device Removal dialog box. When asked whether or not to reboot the computer, answer No. Click on Close. NOTE: The icon with a red X may not be present. If not, skip to step 4.) 4) Insert Diskette 3, ODI Drivers and LAN Client (A) into the floppy drive and at a MS-DOS prompt issue the following command: COPY A:\NOVELL\NETWARE\IBMTRPO.INF C:\WINDOWS\INF 5) Click Start and select Run from the menu. 6) Enter the location of the NetWare Client 32 for Win95 setup program in the Run dialog box. If installing from diskette, insert diskette 1 of the NetWare Client for Win95 installation set and enter A:\SETUP.EXE as the path. If installing from a network drive, consult your LAN administrator this pathname and further assistance. Click OK. 7) Continue with the installation as instructed on the panels until the Select Device dialog box is displayed. Insert Diskette 3, ODI Drivers and LAN Client (A) into the floppy drive. Click Have disk... and enter A:\NOVELL\NETWARE in the Install From Disk dialog box. 8) Select IBM PCI Token Ring Adapter from the adapter list and click OK. 9) Continue with the installation as instructed on the panels. When asked about configuration type, accept the default. Windows 95 must be rebooted in order for Client 32 changes to take effect. 10) Windows 95 might report that it has detected an additional IBM PCI Token-Ring Adapter during the next reboot. If it does, error messages could appear. These error messages can be ignored. They will not reoccur during following reboots. 11) Installation is complete. NOTES: Consult the documentation for NetWare Client 32 for Win95 for more information. A preferred Novell NetWare tree or server must be specified during the NetWare Client 32 for Win95 installation. Not doing so will cause problems with finding servers via the Network Neighborhood icon. To specify these default values, double click on Network in the Control Panel and then double click on Novell Client32 in the Network Window. ================================================================ Chapter 11. Novell Netware OS/2 ODI Driver Updates OS/2 NOVELL NETWARE REQUESTER ----------------------------- 1. The OS/2 ODI driver is now included in this kit (see diskette 3, directory \NOVELL\OS2). 2. Disregard the installation instructions, step 3 on page 4-22. Use the following: "3. On the next panel, specify the name of the IBM PCI Token-Ring Adapter driver - IBMTRPO.SYS (do not specify path, or insert driver diskettes at this time.)" 3. Corrections for "Appendix D - OS/2 ODI Driver Parameters" - the parameter "PCISLOT" should be "SLOT" - the default value for "TXBUFFERS" is 1 ================================================================ Chapter 12. Novell NetWare 4.11 Server Installation Use the following instructions when installing the IBM PCI Token-Ring Adapter under Novell NetWare 4.11 Server: If installing a new server: 1) Insert the adapter into the server machine before installing NetWare 4.11 2) During the NetWare 4.11 installation, the adapter will be automatically recognized and installed. Follow the on-screen instructions referring to the Novell documentation if necessary. NOTE: There may be a newer driver than the one provided on the NetWare 4.11 CD. To upgrade and alter the configuration of the Novell server, follow the instructions that follow under the heading "If installing in an existing server." To upgrade the driver without altering the server configuration follow these steps: 1) Log into the server as an administrative user (typically admin) 2) Insert the IBM PCI Token-Ring Adapter diskette 3 (ODI Drivers and LAN Client (A)) into the floppy drive on the client 3) Change directories into the SYS:\SYSTEM directory on the client 4) Issue the following commands on the client: COPY IBMTRPO.LAN TRPOLAN.OLD COPY IBMTRPO.LDI TRPOLDI.OLD COPY A:\NOVELL\NETWARE\IBMTRPO.LAN . COPY A:\NOVELL\NETWARE\IBMTRPO.LDI . 5) Down and restart the Novell server to reload the new drivers. If installing in an existing server: NOTE: If altering the configuration of a previously loaded adapter, unload that adapter before proceeding with these instructions. 1) Insert the IBM PCI Token-Ring Adapter diskette 3 (ODI Drivers and LAN Client (A)) into the server's floppy drive. 2) Issue the command "LOAD INSTALL" on the server 3) Select "Driver Options" 4) Select "Configure Network Drivers" 5) Select "Select drivers" 6) On the next screen press the Insert (INS) key to install an unlisted driver 7) Press F3 on the next screen to specify a different directory path 8) In the dialog box entitled "Specify a directory path" enter the following: A:\NOVELL\NETWARE 9) Follow the instructions on the following screens to complete the installation of the driver. If it is necessary to make any custom configuration changes to the driver, they can be done at this time. ================================================================ Chapter 13. Remote Unattended Install of Windows 95 and NT Remote Unattended Install of Windows 95 --------------------------------------- IBM now has a downloadable package on the World Wide Web to assist customers in setting up remote unattended install of Windows-95 from a Windows NT or 95 Server with the IBM PCI Token-Ring Adapter installed in the target Windows 95 workstation. To download the package from the IBM Networking Home Page http://www.networking.ibm.com Click on "Hardware Technical Support". Click on "Diskette images/Code updates/Fixes". Click on "Token ring Adapters". Click on "PCI Token Ring Adapter". Look for the item: "PCI Token Ring Win95 Remote Unattended Install". (The filename.ext to download is RUI_W95.exe) This file is a self-extracting diskette image file. After Down- loading, simply execute RUI_W95 to create the diskette and have a blank formatted 3.5" 1.44M diskette ready for your diskette drive when prompted. After creating the diskette, follow the instructions found in the README.1ST file in the root directory of the diskette. The diskette itself is a bootable real-mode connection diskette that can be used to initiate the remote unattended install process from the target workstation after the steps documented in README.1ST are performed to properly set up the server and customize the boot diskette. The diskette also provides sample NETIBM.INF, LAYOUT.INF, and MSBATCH.INF files that can be copied over to the server or can be used for reference when creating custom INF files to meet a customer's specific requirements. Remote Unattended Install of Windows NT --------------------------------------- IBM now has a downloadable package on the World Wide Web to assist customers in setting up remote unattended install of Windows-NT from a Windows NT or 95 Server with the IBM PCI Token-Ring Adapter installed in the target Windows NT workstation. To download the package from the IBM Networking Home Page http//www.networking.ibm.com Click on "Hardware Technical Support". Click on "Diskette images/Code updates/Fixes". Click on "Token ring Adapters". Click on "PCI Token Ring Adapter". Look for the item: "IBM PCI WNT Remote Unattended Install disk". (The filename.ext to download is RUI_NT.EXE ) This file is a self-extracting diskette image file. After Down- loading, simply execute RUI_NT to create the diskette and have a blank formatted 3.5" 1.44M diskette ready for your diskette drive when prompted. After creating the diskette, follow the instructions found in the README.1ST file in the root directory of the diskette. The diskette itself is a bootable real-mode connection diskette that can be used to initiate the remote unattended install process from the target workstation after the steps documented in README.1ST are performed to properly set up the server and customize the boot diskette. The diskette also provides sample NETIBM.INF, LAYOUT.INF, and MSBATCH.INF files that can be copied over to the server or can be used for reference when creating custom INF files to meet a customer's specific requirements. ================================================================ --END of FILE-- -hmg ...........................