?_Ā’’’’éy²©l! 23BrowseButtons()ZmainmainŅ€€   /&;)z4’’ € ’’’’HDKCTNTSŚāHDKFTSU–HDKLISTSnā|CONTEXT>Ŗ|CTXOMAP4Š|FONT&‡|SYSTEM|TOPICń|TTLBTREE’|bm0m²5‚,‚’’’’ 8’’’’D1ņ’’’’uƒD…FGeneralA …4 8€€˜˜€†"€€€‚’General›uD & €ė€˜€‚‚’This main screen displays general information about the network interface card (NIC). Use the tabs at the top of the window to open the Properties, Diagnostics, and Support screens. If you have more than one NIC installed, use the NIC Selection box to select a NIC.The information under the NIC selection box provides a summary of the current configuration, including:d+…„9 B€V€ŒŒā0„„€‰‚ā„„‰‚āŚƒ„‰‚’Device IDI/O AddressNode Address€\ $ €ø€˜€‚’Select NIC Details for more detailed information on the current card settings, including:BʄF| ʀ€ŒŒ‚3āū~„€‰ƒāŠ~„‰‚ā"}„‰ƒā&„‰‚ā÷|„‰ƒāYƒ„‰‚ā.ƒ„‰ƒā±„„‰‚āM}„‰ƒāQ„‰‚ā„~„‰ƒā|„‰‚’Boot PROM SizeMedia TypeBus NumberNetwork SpeedDevice NumberProduct CodeDivision CodeProduct Date CodeI/O Port RangeReceive FIFO SizeIRQ LevelTransmit FIFO Size1w1¶’’’’’’’’w¬15F¬% € €˜˜€‚’NIC Selection…aw1$ €Ā€˜€‚’The NIC selection box lets you select a network interface card if multiple NICs are installed.< ¬m1r’’’’~‚m įNIC Details31 % €€˜˜€‚’NIC Detailsa=m$ €z€˜€‚’The NIC details button displays NIC information including:ąÆ į1 0€_€ŒŒ€ƒ‚ƒ‚ƒ‚ƒ‚ƒ‚ƒ‚’Boot PROM SizeMedia TypeBus NumberNetwork SpeedDevice NumberProduct CodeDivision CodeProduct Date CodeI/O Port RangeReceive FIFO SizeIRQ Level Transmit FIFO Size11’’’’’’’’G•5įG% € €˜˜€‚’Device NumberN*•$ €T€˜€‚’The Device Number for the selected NIC.1GĘ1|’’’’’’’’ĘųC2 •ų% €€˜˜€‚’Bus NumberK'ĘC$ €N€˜€‚’The Bus Number for the selected NIC.1ųt1½’’’’’’’’tŖ6 6CŖ% €"€˜˜€‚’I/O Port RangeŒat6 + $€Ć€˜€€€‚’The I/O Port Range specifies which portion of the computer’s I/O address space will be used communication between the NIC and the computer. Make sure that no other device is using any I/O addresses in the same range. The NIC uses 16 bytes of I/O space, starting at the I/O base address. You cannot change this setting from the Properties screen.1Ŗg 1Å’’’’’’’’g ˜ , 1 6 ˜ % €€˜˜€‚’IRQ Level”ig , + $€Ó€˜€€€‚’The Interrupt Request Level is used by the NIC for communication between the NIC and the computer. The interrupt request level is the communications channel through which a device issues interrupts to the computer’s interrupt handler. You can not change this setting using the Properties screen. Make sure that no other device is using the same setting.1˜ ] 1~’’’’’’’’]  Ü 2 ,  % €€˜˜€‚’Media TypeM] Ü 7 <€-€˜€€€€€€€‚’Media Type lets you select the media type (Auto Select, 10BASE-T, 100BASE-TX, or 100BASE-T4), based on the type of network you are using. The Auto Select option lets the NIC automatically select the Media Type. You can change this setting using the Properties screen.1 1æ’’’’’’’’ CŃ6Ü C% €"€˜˜€‚’Boot PROM SizeŽj Ń$ €Ō€˜€‚’The size of the current boot PROM. This setting is only changed if you install a boot PROM on the NIC.1C1Č’’’’’’’’ 7 @5Ń7% € €˜˜€‚’Network Speed—s @$ €ę€˜€‚’For network speed, you can select 10 Mbps or 100 Mbps. You can change this setting using the Properties screen.7 @Ń17=@1ž’’’’’’’’ =@v@ć@9 @v@% €(€˜˜€‚’Receive FIFO SizemI=@ć@$ €’€˜€‚’The current receive FIFO Size is 3 K. You cannot change this setting.1v@A1Ÿ’’’’’’’’ ANA¼A:ć@NA% €*€˜˜€‚’Transmit FIFO SizenJA¼A$ €”€˜€‚’The current transmit FIFO Size is 5 K. You cannot change this setting.1NAķA1‘’’’’’’’’ ķA&B†B9¼A&B% €(€˜˜€‚’Product Date Code`<ķA†B$ €x€˜€‚’The Product Date Code is the release date of the product.1&B·B1’’’’’’’’ ·BģBKC5†BģB% € €˜˜€‚’Division Code_;·BKC$ €v€˜€‚’The Division Code is 6. You cannot change this setting.1ģB|C1’’’’’’’’|C°CD4KC°C% €€˜˜€‚’Product Code_;|CD$ €v€˜€‚’The Product Code is EC. You cannot change this setting.1°C@D1%’’’’’’’’@DsDgE3DsD% €€˜˜€‚’Enable TrayōĻ@DgE% €Ÿ€˜€‚’This is the Enable Tray Icon check box. When you check this box, the 3Com icon appears in tray at the bottom of your screen, and you can launch the 3Com NIC Diagnostics program by clicking the 3Com icon.8sDŸE1UA’’’’ŸEĪEņESummary/ gEĪE% €€˜˜€‚’Summary$ŸEņE" €€€’1ĪE#F1z’’’’’’’’#FUFžF2ņEUF# €€€‚’Node AddressI%#FžF$ €J€˜€‚’The node address for selected NIC.1UFĻF1}’’’’’’’’ĻFGNG3žFG% €€˜˜€‚’I/O AddressL(ĻFNG$ €P€˜€‚’The I/O address for the selected NIC.1GG1{’’’’’’’’G°GśG1 NG°G% €€˜˜€‚’Device IDJ&GśG$ €L€˜€‚’The device ID for the selected NIC.1°G+H1š’’’’’’’’+HZHĆH/ śGZH% €€˜˜€‚’WarningiE+HĆH$ €Š€˜€‚’Warning text shows up if there is a problem with the selected NIC.; ZHžH17žHBIHLPropertiesDĆHBI4 8€"€˜˜€†"€€€‚’Properties÷ŹžH9K- (€•€˜€€€‚‚‚’The Properties tab displays the Properties screen that allows you to change the configuration settings using the pull-down menus.Select Optimal settings to automatically configure the selected NIC. The configuration software chooses settings that do not conflict with the current computer configuration.If you want to customize the NIC configuration yourself, you can change the parameters listed under Individual Settings. These parameters include:‰HBIĀKA R€€ŒŒāµ†„€‰‚āŠ†„‰‚āź‹„‰‚ā_†„‰‚‚’Boot PROMFull DuplexMedia TypeNetwork Driver Optimization†b9KHL$ €Ä€˜€‚’If you are using PACE drivers, select PACE Configuration to open the PACE configuration window.1ĀKyL1Ü’’’’’’’’yL±L\M8HL±L% €&€˜˜€‚’Optimal Settings«†yL\M% € €˜€‚’The Optimal Settings button automatically configures your NIC to settings that do not conflict with other devices in your computer.1±LM1Ą’’’’’’’’MĒMVO:\MĒM% €*€˜˜€‚’PACE ConfigurationjMVO% €Õ€˜€‚’The PACE Configuration button displays the PACE configuration screen. PACE drivers support prioritization of packets for applications such as video conferencing and distance learning. With the 3Com PACE drivers, you can set a class of service for each application. This NIC uses PACE technology to evaluate network traffic and optimize network performance.IĒMŸO1Ŗ’’’’’’’’ŸOßOd€Configuration Parameters@VOßO% €6€˜˜€‚’Configuration ParametersyUŸOd€$ €Ŗ€˜€ßOd€VO‚’This combination box contains optional settings for the selected configurable item1ßO•€1’’’’’’’’•€Ų€­ƒCd€Ų€% €<€˜˜€‚’Network Driver OptimizationŸ{•€w$ €ö€˜€‚’The Network Driver Optimization setting specifies how to optimize the network driver for your network. Options include:ŒMŲ€‚? N€š€^ŒŒZ¬V„,:€ƒ€‚€ƒ€‚€ƒ€‚’nNormalnMinimized CPU utilizationnMaximized network performance Ŗ~w­ƒ, &€ż€˜€‚€€‚’For example, network driver optimization may use a larger percentage of the CPU under DOS to improve network throughput. On a server this may be inappropriate, so the driver will attempt to minimize CPU utilization in a server environment. For a multi-tasking workstation, it may be better to use the Normal option to balance the CPU utilization and the network performance.1‚Žƒ1°’’’’’’’’Žƒ„†3­ƒ„% €€˜˜€‚’Full Duplex“iŽƒ¤„* $€Ņ€˜€€€‚’Full Duplex is optimized for high-performance switched Ethernet. For this setting, options include:‡6„+…Q r€l€^ŒŒZ¬V„,:€ƒ€€€€ €€‚€ƒ€€‚€ƒ€‚’nAuto Select (N-Way)nEnablenDisablee.¤„†7 <€]€˜€€€€€€€‚’For Auto Select, the NIC automatically runs at the speed that the connected hub supports, in compliance with NWay, an IEEE 802.3 standard. The NIC also works with any other non-NWay 10BASE-T compliant products. Note: Full duplex is not available with the Fast EtherLink XL PCI 100BASE-T4 NIC.1+…Į†1®’’’’’’’’Į†ņ†oˆ1 †ņ†% €€˜˜€‚’Boot PROM}XĮ†oˆ% €±€˜€‚’The Boot PROM lets the computer start DOS operations through the network without using a local startup disk. The Disabled setting indicates that no boot PROM is installed or that you do not want it active. There is no boot PROM installed on this NIC. If you install a boot PROM, you can enable it here and select 8 K, 16 K, 32 K, and 64 K.1ņ† ˆ1T’’’’’’’’ ˆŅˆõŠ2 oˆŅˆ% €€˜˜€‚’Media TypeČ£ ˆš‰% €G€˜€‚’Media Type lets you specify the type of media your network is using. You must have the appropriate NIC installed that supports your selection. Options include:åzŅˆŠk ¦€ō€^ŒŒZ¬V„,:€ƒ€€ €€‚€ƒ€€ €€‚€ƒ€€ €€‚€ƒ€€ €€‚’nAuto Select (N-WAY)n100 BASE-TX (100 Mbps)n100BASE-T4 (100 Mbps)n10 BASE-T (RJ-45) (10 Mbps)vRš‰õŠ$ €¤€˜€‚’The Auto Select option allows the NIC to automatically select the type for you.< Š1‹1uƒn1‹v‹UDiagnosticsEõŠv‹4 8€$€˜˜€†"€€€‚’Diagnostics·’1‹-Œ% €%€˜€‚’The Diagnostics Tab opens the diagnostics screen. The list box contains the following diagnostic tests that you can run. These tests include:тv‹žŒO l€€ŒŒāi‹„€‰‚ā„‰‚āæ‹„‰‚ā”‹„‰‚āB„‰‚ā>‹„‰‚’EEPROM TestEncoder/Decoder Loopback TestEthernet Core Loopback TestFIFO TestInterrupt TestRegister Access TestW--ŒU* $€Z€˜€€€‚’The NIC self-test checks the NIC itself.1žŒ†1‚’’’’’’’’†³Ž-U³% €€˜˜€‚’StartQ-†Ž$ €Z€˜€‚’The Start button starts the selected test.1³5Ž1€’’’’’’’’5ŽaŽ°Ž,ŽaŽ% €€˜˜€‚’StopO+5Ž°Ž$ €V€˜€‚’The Stop button stops the selected test.1aŽįŽ1$’’’’’’’’ įŽ Ą-°Ž% €€˜˜€‚’TestsóČįŽ Ą+ $€‘€˜€€€‚’This box contains a list of the diagnostic tests you can run. The NIC self-test checks the NIC itself. The Echo test verifies the NIC's ability to send and receive data to and from another NIC. Ą°Ž1>Ą1‹’’’’’’’’!>ĄzĄŌĮ< ĄzĄ% €.€˜˜€‚’Register Access TestZ5>ĄŌĮ% €k€˜€‚’The Register Access Test verifies that the computer can access the NIC's registers correctly. If this test fails, check the I/O base address setting on the NIC and make sure that it does not conflict with another device using the same setting. Make sure that the NIC is installed in the appropriate slot.1zĄĀ1H’’’’’’’’"Ā8ĀOÅ3ŌĮ8Ā% €€˜˜€‚’EEPROM Testj=Ā¢Ć- (€{€˜€‚€€‚‚’The EEPROM Vital Data test verifies that the ASIC can access the EEPROM and checks the integrity of the nonconfigurable data in the EEPROM.The EEPROM Configurable Data test verifies that the ASIC can access the EEPROM and verifies the integrity of the user-configurable data in the EEPROM. If this test fails:­^8ĀOÅO l€½€^ŒŒZ¬V„,:€ƒ€€‚€ƒ€€‚€ƒ€€ €€‚’nCheck the I/O base address setting on the NIC and make sure that it does not conflict with another device using the same setting.nMake sure that the NIC is installed in the proper slot.nThe user-configurable data in the EEPROM may be corrupted. Reconfigure the NIC so that the configuration information is rewritten to the EEPROM.1¢Ć€Å1„’’’’’’’’#€Å±Å%Č1 OűÅ% €€˜˜€‚’FIFO Testä€ÅĒĘ2 2€É€˜€€€€€‚‚’The FIFO Built-in Self-test verifies the data integrity of the FIFOs. The FIFO Loopback test uses the FIFO loopback mode to verify the correct operation of the transmit and receive FIFOs.If the FIFO Loopback test fails:^±Å%ČI `€+€^ŒŒZ¬V„,:€ƒ€€‚€ƒ€€‚€ƒ€€‚’nCheck the I/O base address setting on the NIC and make sure that it is not being used by another device.nCheck the DMA channel setting on the NIC and make sure that it is not being used by another device.nMake sure that the NIC is installed in the proper slot.1ĒĘVČ1’’’’’’’’$VșČéŹC%șČ% €<€˜˜€‚’Ethernet Core Loopback Test«…VČDÉ& € €˜€‚‚’The Ethernet Core Loopback test verifies the NIC's ability to send and receive data through the Ethernet core.If this test fails:֙ČRŹ8 >€­€^ŒŒZ¬V„,:€ƒ€‚€ƒ€‚’nCheck the I/O base address setting on the NIC and make sure that it is not being used by another device.nCheck the DMA channel setting on the NIC and make sure that it is not being used by another device.—sDÉéŹ$ €ę€˜€‚’The NIC may be installed in a slot that does not support bus mastering. Install the NIC in a bus mastering slot.1RŹĖ17’’’’’’’’%Ė_ĖeĶE éŹ_Ė% €@€˜˜€‚’Encoder/Decoder Loopback TestƉĖĢ& €€˜€‚‚’The Encoder/Decoder Loopback test verifies the NIC's ability to send and receive data through the encoder/decoder.If this test fails:W_ĖeĶ@ N€/€^ŒŒZ¬V„,:€ƒ€‚€ƒ€‚€ƒ€‚’nCheck the I/O base address setting on the NIC and make sure that it is not being used by another device.nCheck the DMA channel setting on the NIC and make sure that it is not being used by another device.nMake sure that the NIC is installed in the appropriate slot.1Ģ–Ķ1­’’’’’’’’&–ĶĢĶHĪ6eĶĢĶ% €"€˜˜€‚’Interrupt Test|X–ĶHĪ$ €°€˜€‚’The Interrupt test verifies that the NIC can send interrupt requests to the computer.1ĢĶyĪ1’’’’’’’’'yĪ„ĪĻ,HĪ„Ī% €€˜˜€‚’Send\8yĪĻ$ €p€˜€‚’The Send button displays the Echo Test Sender screen.1„Ī2Ļ1“’’’’’’’’(2ĻaĻĆĻ/ ĻaĻ% €€˜˜€‚’Respondb>2ĻĆĻ$ €|€˜€‚’The Respond button displays the Echo Test Responder screen.: aĻ 1p ’’’’’’’’) =² Echo TestĆĻ ĆĻ1 ĆĻ=% €€˜˜€‚’Echo TestžŃ ;- (€£€˜€€€‚‚‚’The Echo test verifies the NIC’s ability to transmit and receive data while on the network. This test should be run on an inactive network. The NIC must be connected to a network that includes a second PC set up as an echo server. The echo server receives packets from the NIC being tested and echoes them back. The second PC is (the echo server) must contain a 3Com NIC. You can use any of the NICs listed below in the echo server:For 10 Mbps/s Ethernet:,Ä=gh ž€‰€^ŒŒZ¬V„,:€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€‚’nEtherLink II or II TPnEtherLink PlusnEtherLink 16 or 16 TPnEtherLink/MC or MC TPnEtherLink/MC 32nEtherLink II/16 or II/16 TPnEtherLink III FamilynEtherLink XL PCI?;¦$ €6€˜€‚’For 100 Mbps/s Ethernet:¤egJ? N€Ź€^ŒŒZ¬V„,:€ƒ€‚€ƒ€‚€ƒ€‚’nFast EtherLink XL PCI (10/100)nFast EtherLink EISA (10/100)nFast EtherLink ISA (10/100)5 ¦, &€€˜€€€‚‚’For more information, see the Fast EtherLink PCI 10/100BASE-TX/T4 Network Interface Card User Guide or the EtherLink XL Parallel Tasking PCI Bus Master Network Interface Card User Guide.The Echo test reports error counts and performance statistics, including:iJ•­ (Ó€ŒŒ‚±āє„€‰ƒā'•„‰‚āĖ‘„‰ƒā!’„‰‚āö‘„‰ƒāL’„‰‚āų’„‰ƒā¢’„‰‚āü”„‰ƒā\š„‰‚āŁ˜„‰ƒā¦”„‰‚āZ™„‰ƒāP”„‰‚ā/™„‰ƒāw’„‰‚āĶ’„‰ƒā™„‰‚ā{”„‰‚’Bad SSD ErrorsOversize PacketsBytes ReceivedPackets ReceivedBytes TransmittedPackets TransmittedCarrier Sense LostReceive overrunCRC ErrorsRunt PacketsExcessive CollisionsSingle CollisionsFrame Alignment ErrorsSQE ErrorsJabber errorsTransmit DeferralsLate collisionsTransmit underrunMultiple Collisions>Ó$ €4€˜€‚’If the Echo test fails:n•A ^ Š€!€^ŒŒZ¬V„,:€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€€ €‚’nCheck the I/O base address setting on the NIC and make sure that it is not being used by another device.nCheck the DMA channel setting on the NIC and make sure that it is not being used by another device.nCheck the transceiver setting on the NIC.nMake sure that the test is running on an inactive network.nCheck the NIC connection to the network.nIf you are testing a twisted-pair NIC, check the LED on the back of the NIC. If it is not lit, there is a problem with the loopback plug or the network.qBÓ² / .€„€^ŒŒZ¬V„,:€ƒ€‚’nMake sure that the NIC is installed in the appropriate slot.1A ć 1,’’’’’’’’*ć   2 ²  % €€˜˜€‚’Start EchoūÖć  % €­€˜€‚’The Start button begins the echo test. The echo test verifies the NIC's ability to transmit and receive data while on the network. The NIC must be connected to an inactive network that includes an echo server.1 A 1|’’’’’’’’+A r ½ 1  r % €€˜˜€‚’Stop EchoK'A ½ $ €N€˜€‚’The Stop button stops the echo test.1r ī 1–’’’’’’’’,ī  … 2 ½  % €€˜˜€‚’ContinuouseAī … $ €‚€˜€‚’Check the Continuous box to run the test until you click Stop.; Ą 1¦’’’’’’’’-Ą ņ gStatistics2 … ņ % €€˜˜€‚’StatisticsuQĄ g$ €¢€˜€‚’The Statistics list box lists the performance statistics obtained by the test.1ņ ˜1—’’’’’’’’.˜Ī46gĪ% €"€˜˜€‚’Bytes ReceivedfB˜4$ €„€˜€‚’Bytes Received is the number of bytes received during the test.1Īe1’’’’’’’’/ež@94ž% €(€˜˜€‚’Bytes TransmittedlHe@$ €€˜€‚’Bytes Transmitted is the number of bytes transmitted during tž@4he test.1žG@1›’’’’’’’’0G@@é@8@@% €&€˜˜€‚’Packets ReceivedjFG@é@$ €Œ€˜€‚’Packets Received is the number of packets received during the test.1@A1”’’’’’’’’1AUAÅA;é@UA% €,€˜˜€‚’Packets TransmittedpLAÅA$ €˜€˜€‚’Packets Transmitted is the number of packets transmitted during the test.1UAöA1'’’’’’’’’2öA0B&C:ÅA0B% €*€˜˜€‚’Transmit DeferralsöŠöA&C& €”€ ˜J€‚’Transmit Deferrals is the number of times the NIC deferred to another transmitting node while waiting to transmit. This number increases as other stations contend with this NIC for access to the Ethernet.10BWC1ć’’’’’’’’3WCŽC@D7&CŽC% €$€˜˜€‚’Receive Overrun²WC@D% €€˜€‚’Receive overrun is the number of lost packets that cannot be stored in the receive buffer because the computer's buffer is already full. 1ŽCqD12’’’’’’’’4qDØD©E7@DØD% €$€˜˜€‚’Late CollisionsÜqD©E% €¹€˜€‚’Late collisions A late collision occurs when another node on the Ethernet does not properly defer once the NIC has started transmitting. If a large number of late collisions occur, contact your network administrator.1ØDŚE1’’’’’’’’5ŚEFłF:©EF% €*€˜˜€‚’Carrier Sense LoståĄŚEłF% €€˜€‚’Carrier Sense Lost is the number of packets transmitted with carrier sense loss. This normally occurs as a result of collisions. For more information, refer to an Ethernet reference guide.1F*G1d’’’’’’’’6*G\GH2 łF\G% €€˜˜€‚’SQE Errors3*GH% €€˜€‚’SQE Errors are the number of times that the SQE signal was detected during transmission from the computer's NIC. This count should be zero or the same as the total number of packets transmitted. Any other number indicates that the NIC transceiver is malfunctioning.1\GĄH1’’’’’’’’7ĄHūHŠI;HūH% €,€˜˜€‚’Multiple CollisionsÕ°ĄHŠI% €a€˜€‚’Multiple Collisions are a normal occurrence on an Ethernet network; however, excessive collisions may indicate problems. If this occurs, contact your network administrator.1ūHJ1¼’’’’’’’’8J:JÅJ9ŠI:J% €(€˜˜€‚’Single Collisions‹gJÅJ$ €Ī€˜€‚’Single Collisions are the number of packets that had one collision during transmission from the NIC.1:JöJ1Ŗ’’’’’’’’9öJ,K„K6ÅJ,K% €"€˜˜€‚’Bad SSD ErrorsyUöJ„K$ €Ŗ€˜€‚’Bad SSD Errors may indicate network problems. Contact your network administrator.1,KÖK1r’’’’’’’’:ÖKLIM2 „KL% €€˜˜€‚’CRC ErrorsAÖKIM% €9€°€‚’Each packet sent on an Ethernet network has a calculated cyclic redundancy check (CRC) appended to it. When the packet is received, this CRC is compared with the calculated CRC If the calculated CRC is different from the CRC, the packet was corrupted, most likely by line noise. 1LzM1’’’’’’’’;zM²M…N8IM²M% €&€˜˜€‚’Oversize PacketsÓ®zM…N% €]€˜€‚’Oversize Packets are packets greater than 1,514 bytes. Even though such packets are theoretically illegal under Ethernet, they do occur on certain live Ethernet networks.1²M¶N1Ż’’’’’’’’<¶NźN–O4…NźN% €€˜˜€‚’Runt Packets¬‡¶N–O% €€˜€‚’Runt Packets are packets less than 60 bytes. Typically these are simply collision fragments. There are no problems on the network.1źNĒO1’’’’’’’’=ĒO€™€<–O€% €.€˜˜€‚’Excessive CollisionĒO€–OsŠfĒO™€$ €Ģ€˜€‚’Excessive Collisions may indicate network or cabling problems. Contact your network administrator.1€Ź€1’’’’’’’’>Ź€Ō9™€% €(€˜˜€‚’Transmit UnderrunѬŹ€Ō% €Y€˜€‚’Transmit underrun is the number of times a packet was transmitted without adequate data by the NIC. This may indicate a problem with the NIC or the computer's buffer. 1‚1ˆ’’’’’’’’?‚:‚‘‚5Ō:‚% € €˜˜€‚’Jabber ErrorsW3‚‘‚$ €f€˜€‚’Jabber errors may indicate noise on the network.1:‚Ā‚1B’’’’’’’’@Ā‚ƒ„>‘‚ƒ% €2€˜˜€‚’Frame Alignment ErrorsģĀ‚„% €Ł€˜€‚’Frame Alignment Errors are the number of alignment errors for the packets received by the PC. An alignment error is caused when an incoming packet does not end on a byte boundary and the CRC does not match at the last byte boundary.8ƒI„1+< AI„‹„…‰SupportB„‹„4 8€€˜˜€†"€€€‚’Support æšI„J…% €5€˜€‚’The Support Tab displays the 3Com Support screen. If you are having trouble with your NIC, you should follow the steps outlined on the Support screen..Ü‹„x‡R r€¹€^ŒŒZ¬V„,:€ƒ€ā°™„‰‚€ƒ€āŪ™„‰‚€ƒ€āš„‰‚’nRun Diagnostics first. The Run Diagnostics button opens the Diagnostic screen, which is the same screen displayed under the Diagnostics tab.nReview the Release Notes. The Release Notes button lets you review the KnowledgeBase, which contains known solutions for computer models, operating systems, and network operating systems.nCheck the 3Com BBS. Always check the BBS for the latest software, drivers, and technical information pertaining to your NIC. ĆJ……‰J b€‡€^ŒŒZ¬V„,:€ƒ€€ €‚€ƒ€āĀ¢„‰€ €‚’nCheck the 3Com WWW site. You can also go to 3Com’s World Wide Web site for the latest for the latest software, drivers, and technical information pertaining to your NIC.nRecord a Problem Report. If you cannot find a solution to your problem, use the Problem Report button to record a description of your network environment and the problem you are having, and to save it to a file. You send the completed report to 3Com using e-mail.1x‡¶‰1Œ’’’’’’’’B¶‰ķ‰HŠ7…‰ķ‰% €$€˜˜€‚’Run Diagnostics[7¶‰HŠ$ €n€˜€‚’The Diagnostics Button opens the Diagnostics screen.1ķ‰yŠ1‡’’’’’’’’CyŠ®ŠŒ5HŠ®Š% € €˜˜€‚’Release Notes«†yŠY‹% € €˜€‚’The Release Notes Button opens a library of information about the NIC. Select one of the following topics for detailed information.«R®ŠŒY ‚€¤€^ŒŒZ¬V„,:€ƒė)B¦€‰‚€ƒćTB¦€‰‚€ƒė™£„€‰‚’nRelease Notes.nFrequently Asked QuestionsnKnowledgeBase topics> Y‹BŒ1’’’’i‰DBŒ{Œ[ĮRelease Notes9Œ{Œ( €"€˜˜€€‚’Release Notes eBŒ†Ž¦ Ė€^ŒŒZ¬V„,:€ƒė\F¦€‰‚€ƒė1F¦€‰‚€ƒėĘP¦€‰‚€ƒėpP¦€‰‚€ƒė“G¦€‰‚€ƒėEP¦€‰‚€ƒėP¦€‰‚’n3Com PCI NIC Installation HintsnCompaq Prolinea 575 Computer NotificationnDiagnostics and configuration utilities run in DOSnEcho exchange test does not support crossover cablenPerformance Hint for Fast EtherLink XL NICs on HP NetServersnPerformance on Early Pentium Pro ModelsnResource Conflicts Under Windows NT7‹{ŒÉĄ¬ &€^ŒŒZ¬V„,:€ƒėN¦€‰‚€ƒć&V¦€‰‚€ƒćĪT¦€‰‚€ƒėėM¦€‰‚€ƒć£T¦€‰‚€ƒė8_¦€‰‚€ƒė _¦€‰‚€ƒė ]¦€‰‚’nRunning the DOS ODI Driver with a Non-Novell Protocol nSpurious Hardware Interrupts on the Compaq Proliant 5000nStopping the driver in a Windows NT SystemnWindows 95 Installation Not†ŽÉĄŒesnWindows NT 4.0 Incompatibility with Miniport DriversnSharing Interrupts Under Windows 95nToshiba Tecra 720 CDT and Tecra 500 CS PCsnDell Dimension XPS Pro 200n’G†Ž[ĮK f€Ž€^ŒŒZ¬V„,:€ƒė4]¦€‰‚€ƒėŒ^¦€‰‚’nOS/2 Warp 3.0nWarm Booting with DOS Based Drivers Runningm<ÉĄČĮ1ī’’’’S„EČĮ0ĀķĆPerformance Hint for Fast EtherLink XL NICs on HP NetServersh@[Į0Ā( €€€˜˜€€‚’Performance Hint for Fast EtherLink XL NICs on HP NetServers½—ČĮķĆ& €/€˜€‚‚’During testing of HP NetServers and the Fast EtherLink XL NIC, 3Com has observed that the performance can be maximized by customizing the NetServer's BIOS. Within the BIOS of the NetServer, access the Advanced Chipset Setup and set the DRAM Buffer Write to 0 and the Snoop Ahead to 1.NOTE: This was tested on an HP NetServer 466 LF and a 466 LC, but could apply to other models of the NetServer family.Z)0ĀGÄ1_’’’’’’’’FGÄœÄŹĘCompaq Prolinea 575 Computer NotificationU-ķĆœÄ( €Z€˜˜€€‚’Compaq Prolinea 575 Computer Notification.GÄŹĘ& €€˜€‚‚’3Com has observed issues with a particular system BIOS revision for the Compaq Prolinea 575 computer. If the system BIOS version is dated 7/26/95, it should be updated to a later revision. The Compaq Prolinea 575 Configuration and Diagnostics utility should be used to verify the revision date of the system BIOS (system ROM).Consult the manual for the Compaq Prolinea for instructions on verifying and updating the system ROM version and on obtaining updated system ROM software, or contact Compaq for assistance.PœÄĒ1ōG€"†GĒeĒ43Com PCI NIC Installation HintsK#ŹĘeĒ( €F€˜˜€€‚’3Com PCI NIC Installation HintsJ&ĒÆĒ$ €L€˜€ ‚’To install a PCI NIC in a PCI slot:s4eĒ"É? L€i€V˜˜øJ„8:€ ƒ€‚€ ƒ€‚€ ƒ€‚’1Select a PCI slot. Refer to your PC documentation if you need help.2Insert the NIC in the PC. Refer to your PC documentation.3Start the PC. In most cases, the PCI computer will automatically configure the NIC. If this does not happen, you may need to configure the PC to work with the NIC. „rÆĒĒŹ3 4€å€˜€€€‚€ ‚€‚’For more information, see the Fast EtherLink PCI 10/100BASE-TX/T4 Network Interface Card User Guide or the EtherLink XL Parallel Tasking PCI Bus Master Network Interface Card User Guide.Troubleshooting Installation Problems3Com has found that some PCI computers require additional configuration steps in order to install a PCI NIC. 3Com recommends these steps:Ļ~"É–ĶQ p€ż€V˜˜øJ„8:€ ƒ€ć‡F¦‰‚€ ƒ€‚€ ƒ€€ €€ €‚’1Determine whether you have the latest BIOS version for your computer. Contact your PC's manufacturer to make sure you are using the latest BIOS. Click here for the phone numbers for some PCI system manufacturers:2Make sure the BIOS is set up correctly. In some PCI computers, you may need to enable the PCI slot using the BIOS Setup program. This is especially common in PCI computers with a Phoenix BIOS.3After installing the NIC, turn on the computer and enter the Setup program during system initialization, usually by pressing [F1], [F2], or [Ctrl]-[Alt]-[S]). The correct key to press is shown on the screen.Š”ĒŹfĪ/ ,€C€V˜˜øJ„8:€ ƒ€‚’4Once in the Setup program, find the entry for PCI slots in the main menu or in Advanced System Configuration. Set the configuration parameters as follows:į–ĶĻ8 >€Ć€˜‚Ÿ€ ƒ‚€ƒƒƒƒƒƒ‚’BIOS System ParameterSettingPCI Slot NumberSlot where the 3Com PCI NIC is installed (1-3)MasterENABLEDSlaveENABLEDLatency Timer40InterruptChoose from available interruptsEdge or LevelLevel Triggered Interrupt©ƒfĪ4& €€˜€‚‚’(NOTE: The exact name of each parameter may vary.)Save the changes, exit the Setup prograĻ4ŹĘm, and continue with the installation.c2Ļ—1a;ņƒH—õ%Diagnostics and configuration utilities run in DOS^64õ( €l€˜˜€€‚’Diagnostics and configuration utilities run in DOS0—%+ $€ €˜€€€‚’3Com DOS Diagnostic and Configuration program runs in DOS-mode only. If you are running Windows 95 or windows NT, please use the 3Com NIC Diagnostic program, which is installed in your SYSTEM directory from the EtherDisk diskette when you install the NIC.d3õ‰1C;I‰čśEcho exchange test does not support crossover cable_7%č( €n€˜˜€€‚’Echo exchange test does not support crossover cableɉśI `€“€˜€€€€€€€€€€€€€‚’Because the Echo test verifies the NIC's ability to transmit and receive data while on the network, both the echo server and the echo client must be connected to a network. An EtherLink XL NIC uses link beats to determine whether it is connected to a network when the 10BASE-T, 100BASE-TX, or 100BASE-T4 Media Type is selected. A constant link beat is needed for the Echo Exchange test when the 10BASE-T, 100BASE-TX, or 100BASE-T4 Media Type is selected. Before starting the echo test, connect the echo server and the echo client together through a hub or a switch that generates a constant link beat. Using crossover cable to connect the echo server and the echo client directly does not work.X'čR1"†;JR„|Performance on Early Pentium Pro ModelsS+ś„( €V€˜˜€€‚’Performance on Early Pentium Pro ModelsײR|% €e€˜€‚’During testing, 3Com has observed that some early Pentium Pro models using Intel's (54x?) PCI chip sets do not fully support the full bandwidth throughput of the PCI bus. Symptoms can include an abnormal number of dropped packets or performance below what the wire can support. This problem can sometimes be fixed by getting a more recent BIOS from your system vendor. Contact your vendor to see if such an upgrade is available.T#„Š1N²’’’’KŠ < Resource Conflicts Under Windows NTO'| ( €N€˜˜€€‚’Resource Conflicts Under Windows NT–lŠµ * $€Ų€˜€€€‚’This information applies to Intel (x86)-based computers running one of the following operating systems:©r ^ 7 >€ä€^ŒŒZ¬V„,:€ƒ€‚€ƒ€‚’nMicrosoft Windows NT Workstation versions 3.5 and 3.51nMicrosoft Windows NT Server versions 3.5 and 3.51,µ Š ( € €˜€‚‚‚‚’On these computers, adding an EtherLink XL or Fast EtherLink XL can occasionally cause a PCI resource conflict. When this occurs, the system stops responding (hangs), or one or more of the PCI devices fail to operate.These resource conflicts occur because the Windows NT Hardware Abstraction Layer sometimes assigns overlapping I/O port addresses for the Fast EtherLink XL/EtherLink XL NIC(s) and other PCI devices.When a resource conflict occurs, one of the following procedures should provide a workaround.²a^ < Q r€Ā€^ŒŒZ¬V„,:€ƒć—N¦€‰‚€ƒćlN¦€‰‚€ƒćAN¦€‰‚’nChange the Load Order of DriversnSwap Slot Numbers in the RegistrynSwap Slots; Š w 1¾’’’’ņ Lw ­ :Swap Slots6< ­ ( €€˜˜€€‚’Swap Slotsbw :+ $€Å€˜€€€‚’If the conflict is with another plug-in PCI device, swapping the PCI slots of the Fast EtherLink XL/EtherLink XL NIC and the conflicting device may resolve the problem. Swapping the slots may cause the system BIOS to swap the I/O port addresses assigned to the two devices, which will eliminate the conflict that occurs later when Windows NT boots.R!­ Œ1‚ …€MŒŁNCSwap Slot Numbers in the RegistryM%:Ł( €J€˜˜€€‚’Swap Slot Numbers in the Registry晌¤B& €3€˜€‚‚’Ł¤B:If the conflict is between two Fast EtherLink XL/EtherLink XL NICs, try swapping the PCI slots of the two NICs. If this does not work, you must edit the System Registry using the Registry Editor. The Registry Editor can be found in the \WINNT35\SYSTEM32\REGEDT32.EXE file.In the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services tree of the Registry are keys for the two Fast EtherLink XL/EtherLink XL NICs, EL90X1 and EL90X2. In the Parameters subkey of each of these keys are two values, Slot and SlotNumber, which are the same. Swap the slot values for EL90X1 with the slot values for EL90X2. Make sure to swap both the Slot and the SlotNumber values.Ŗ…ŁNC% € €˜€‚’Changing these values causes the driver to register and activate the two NICs in a different order, which eliminates the conflict.Q ¤BŸC1Äņ ’’’’NŸCėC~GChange the Load Order of DriversL$NCėC( €H€˜˜€€‚’Change the Load Order of Drivers ūŸC F% €÷€˜€‚’If the previous procedures do not work, change the load order of the drivers for the Fast EtherLink XL/EtherLink XL NIC and the conflicting device. In the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services tree of the Registry Editor, you should find the driver keys for the Fast EtherLink XL/EtherLink XL NIC (EL90X) and the conflicting device. For the key that comes first in the tree, add a value with the name DependOnService and a string value that is the key of the driver for the other device.sNėC~G% €€˜€‚’For example, if the conflict is between an EtherLink XL and an EtherLink III PCI NIC, then the two driver keys are EL90X and EL59X. EL59X is first in the tree, so you would add the "DependOnService: EL90X" value to the EL59X key. This forces the EtherLink XL NIC driver to load first, instead of the EtherLink III PCI NIC driver.f5 FäG1®OäGFHĆJRunning the DOS ODI Driver with a Non-Novell Protocolb:~GFH( €t€˜˜€€‚’Running the DOS ODI Driver with a Non-Novell Protocol ą±äG&I/ ,€c€˜€€€‚€ ‚’Add the keyword NO_PIPELINE to your NET.CFG file when running the DOS ODI driver with a non-Novell protocol in a DOS environment. To add NO_PIPELINE to your NET.CFG file:EFHĆJX ~€‹€V˜˜øJ„8:€ ƒ€€ €‚€ ƒ€€ €‚€ ƒ€€ €‚’1Access the C:\NWCLIENT directory and open the NET.CFG file. Type:EDIT NET.CFG [Enter]2Scroll through the file to the LINK DRIVER 3C90X section and locate the following line:LINK DRIVER 3C90X3Add NO_PIPELINE after LINK DRIVER 3C90X. Your file should now look like this:LINK DRIVER 3C90XNO_PIPELINEN&IK1ÕS„;PKZK£€Windows 95 Installation NotesI!ĆJZK( €B€˜˜€€‚’Windows 95 Installation NotesŠdKäN& €É€˜€‚‚’When installing an EtherLink XL or Fast EtherLink XL NIC under Windows 95, the operating system automatically detects the presence of the NIC and asks for the diskette containing the driver software for the NIC (the EtherDisk diskette). At this point, you can choose to cancel the installation of driver software and install it later. Even though the driver installation has been canceled, the fact that the NIC is installed is recorded in the System Registry.Later, when you install the driver software using the Network applet in the Control Panel, the operating system assumes that you are installing another instance of a NIC, not installing software for the already recorded instance. This results in two instances of a NIC being recorded in the System Registry. The Fast EtherLink XL/EtherLink XL NIC will not operate correctly under these circumstances.³ŽZK£€% €€˜€‚’To fix this problem, open the System applet in the Control Panel. In the Device Manager dialog box, under Network NICs, the two instances of the Fast EtherLink XL/EtherLink XL NIC are shown. Remove the one that is marked disabled, and restart yäN£€ĆJour computer. The remaining entry for the Fast EtherLink XL/EtherLink XL NIC in the same dialog box should show that the NIC is operating correctly.i8äN 1wņƒ\Q l²‚Spurious Hardware Interrupts on the Compaq Proliant 5000`;£€l% €v€˜˜€‚’Spurious Hardware Interrupts on the Compaq Proliant 5000F! ²‚% €C€˜€‚’When running a server on the Compaq Proliant 5000, spurious interrupts warning messages may appear. 3Com has found that these warnings can be ignored and have no effect on normal operation. 3Com has noticed that these warnings also occur with NICs from other manufacturing companies.e4lƒ1u²Rƒsƒ·…Windows NT 4.0 Incompatibility with Miniport Drivers\7²‚sƒ% €n€˜˜€‚’Windows NT 4.0 Incompatibility with Miniport DriversDƒ·…% €?€˜€‚’3Com has observed occasional system shutdowns on some multiprocessor servers (servers with more than one CPU) that use Microsoft Windows NT 4.0 running miniport drivers, including the 3Com 3C90X.SYS miniport driver. This situation is not unique to the 3C90X.SYS miniport driver and may occur with other miniport architecture drivers used with Windows NT 4.0. A new SRV.SYS driver from Microsoft fixes this problem. This driver is included in the Microsoft Windows NT 4.0 Service Pack #1, and can be downloaded from the Microsoft web site.\+sƒ†1š\S†f†%ˆStopping the driver in a Windows NT SystemS.·…f†% €\€˜˜€‚’Stopping the driver in a Windows NT System暆%ˆ% €5€˜€‚’3Com has found that if you stop the driver while there are no protocols installed in your system it will crash with a blue screen error. When this error occurs, the system is dead and must be rebooted. Microsoft admits that there is a problem in Windows NT and is fixed in Service Pack 2.0. To avoid this problem, simply keep at least one protocol loaded, and Windows NT will not let you stop the driver.If†nˆ1µ’’’’’’’’Tnˆ²ˆAĄPCI-System ManufacturersD%ˆ²ˆ( €8€˜˜€€‚’PCI-System ManufacturersinˆŠQ p€1€VŒŒ!ć~„!e€€ƒ€€ƒ€€‚ƒƒ‚ƒƒ‚ƒƒ‚ƒƒ‚ƒƒƒ‚’CompanyPhoneWeb SiteAcer(800) 445-6495www.acer.comALR*(800) 257-1230www.alr.com/service/supportAmbra*(800) 465-2227Not availableAST*(800) 727-1278www.ast.com/americas/files.htmlAT&T*(800) 543-9935www.ncr.com/support/pc/pcdesc(800) 531-2222/machines.htmlåƲˆ‹6 :€_€VŒŒ!ć~†!Se€ƒƒ‚’Compaq*(800) 652-6672www.compaq.com/support/files/compaq.html(800) 345-1518(NOTE: Compaq DeskPRO XL should have a BIOS dated Oct. 1994 or later for best performance.)'ÓŠ'T v€§€R˜!ć~„!e€ƒƒ‚ƒƒ‚ƒƒ‚€€ƒ€€ƒ‚ƒƒ‚ƒƒ‚ƒƒ‚ƒƒ‚’Dell*(800) 626-4308www.dell.com/(800) 624-9896Digital Equipment*(800) 354-9000www.dec.com/Gateway*(800) 846-2070www.gateway2000.com/(800) 846-2301Hewlett-Packard*(800) 322-HPPCwww.hp.com/cposupport/cpoindex.html(800) 752-0900IBM*(800) IBM-3333www.pcco.ibm.com/Micron*(800) 438-3343www.mei.micron.com/services/bbs/techbbs.htmPackard Bell*(800) 733-4411www.packardbell.com/gfx/support/support.htmlUnisys*(800) 328-0440www.pc.unisys.com/¾Š‹å4 6€€R˜!ć~„!e€ƒƒ‚ƒƒ‚’Zenith*(800) 227-3360www.zds.com/htdocs/zds/htm/files.htmZEOS*(800) 554-7172www.mei.micron.com/Services/zeosbbs.htm(800) 228-5390žt'ƒŽ* $€č€˜€€€‚’In addition, here are the phone numbers and on-line addresses of several popular OEM motherboard manufacturers:ü“协H ^€i€R˜!ć~„!e€€ƒ€€ƒ€€‚ƒƒ‚ƒƒ‚ƒƒ‚’CompanyPhoneWeb SiteIntel*(503) 264-7999ftp://ftp.intel.com\pub\biosMicronics(510) 651-6837www.micronics.com/support/ASUS(408) 956-9084http://asustek.asus.com.twŒZƒŽĄ2 4€“€R˜Č:‚H€ƒ€€€‚’·Third-party trademarks and copyrights are the property of their respectivĄ%ˆe owners.*AĄ& €€˜˜€‚‚’T#Ą•Ą1¢w€U•ĄäĄUĀSharing Interrupts Under Windows 95O'AĄäĄ( €N€˜˜€€‚’Sharing Interrupts Under Windows 95qL•ĄUĀ% €™€˜€‚’If two or more PCI NICs in your PC use the same interrupt, you may get a blue screen or continuous PC reboots. To fix this problem, assign a different PCI interrupt number to the Fast EtherLink/EtherLink XL NIC using system setup. Consult your PC documentation for more information about changing the interrupt values on your PC.[*䥰Ā1ģ €V°ĀĆćÄToshiba Tecra 720 CDT and Tecra 500 CS PCsV.UĀĆ( €\€˜˜€€‚’Toshiba Tecra 720 CDT and Tecra 500 CS PCsŻ­°ĀćÄ0 .€[€˜€‚€€‚‚ƒ‚‚’3Com has identified issues with the Toshiba Tecra 720 CDT and Tecra 500 CS PCs, running DOS, with a DeskStation V+ docking station, which may cause data loss.To avoid this situation, when using the Fast EtherLink/EtherLink XL (3C905-TX or 3C900) NIC and the NetWare DOS ODI client driver, edit the NET.CFG file and turn off the pipeline feature. For example:LINK DRIVER 3c90xNo_PipelineSave the file and reboot your PC.LĆ/Å1ž5‹³„W/ÅvÅćĘDell Dimension XPS Pro 200nGćÄvÅ( €>€˜˜€€‚’Dell Dimension XPS Pro 200nmB/ÅćĘ+ $€…€˜€€€‚’When a 3C509B NIC is installed in the same PC as the Fast EtherLink/EtherLink XL (3C905/3C900) NIC, you may get a blue screen. When the 3C509B NIC is installed and configured for Plug and Play, the driver’s request for PCI resources are not granted. To avoid this situation, disable Plug and Play for the 3C509B NIC. > vÅ!Ē1JRƒO‡X!ĒZĒsŹOS/2 Warp 3.09ćĘZĒ( €"€˜˜€€‚’OS/2 Warp 3.0ą!Ē`Č& €Į€ ˜°€‚’3Com has noticed that during the install of early releases of OS/2 Warp 3.0 that the LAPS might incorrectly install the 3C90X NIC. If this does occur, the user will see the following message when the machine is rebooted:IZĒķÉD V€“€ ˜°Œ!Aa”€‚‚‚‚‚‚‚‚€€€‚‚’ LT00042: The EL90XIO2_nif MAC was not able to bind. Return code = 0x22PR00025: An error occurred when the program tried to bind LANDD to EL90XIO2_nifTo work around this issue, edit the PROTOCOL.INI file and locate the following section:[EL90XIO2_nif]Next, change the line DriverName = EL9X$ to DriverName = EL90X$†b`ČsŹ$ €Ä€˜€‚’Note that this problem only occurs to earlier release of OS/2 Warp 3.0 and not later releases. `/ķÉÓŹ1>³„ģ YÓŹ.Ė;ĶWarm Booting with the DOS based Drivers Running[3sŹ.Ė( €f€˜˜€€‚’Warm Booting with the DOS based Drivers Running ēÓŹ;Ķ& €Ļ€˜€‚‚’3Com has found that some PCs do not reset the PCI Bus when the key combination is used to restart the computer. If the PC does not reset the PCI Bus when a "warm boot" occurs the Fast EtherLink XL/EtherLink XL NIC family stay in a running state that can cause problems if there is any network activity before the driver is reloaded. This problem can be avoided by pressing the reset button if your PC has one or by turning the PC completely off before restarting. K.Ė†Ķ1/ēɃZ†ĶĢĶtFrequently Asked QuestionsF;ĶĢĶ( €<€˜˜€€‚’Frequently Asked Questions1‹†Ķ ¦ €^ŒŒZ¬V„,:€ƒć3G¦€‰‚€ƒćG¦€‰‚€ƒć‰G¦€‰‚€ƒćĄM¦€‰‚€ƒćI¦€‰‚€ƒć²F¦€‰‚€ƒć7I¦€‰‚€ƒćjM¦€‰‚€ƒć I¦€‰‚’nACERPOWER ROM configuration problem.nAre my drivers Novell-certified?nCannot execute programs loaded over the net.nDo I have to configure the NIC? nDoes my PCI NIC support shared interrupts? nIncorrect configuration set by BIOS.nIs my 3Com PCI NIC a 3.3 V or 5 V NIC? nIs the NIC compliant with PCI Spec 2.1? nMicrosoft EMM386.EXE problem.ĢĶ ;Ķ=„ĢĶI˜ ž€K€^ŒŒZ¬V„,:€ƒć^G¦€‰‚€ƒćbI¦€‰‚€ƒćøI¦€‰‚€ƒć•M¦€‰‚€ƒćķN¦€‰‚€ƒćOU¦€‰‚€ƒćzU¦€‰‚€ƒćūU¦€‰‚’nNetWare 3.11 server packet buffer problem.nWhat interrupts should I avoid? nWhich interrupt should I use? nWhich PCI slot is best for my PCI NIC? nWhich slots are bus mastering? nHow do I remove the 3Com icon from my system tray?nWhy does my PCI NIC appear disabled in Windows 95 OSR2?nWhy does the 3Com NIC diagnostics program say my NIC is not connected to the network?H¦ ‘¢ M€^ŒŒZ¬V„,:€ƒć~W¦€‰‚€ƒėŌW¦€‰‚€ƒė³\¦€‰‚€ƒėŽ\¦€‰‚€ƒėc_¦€‰‚€ƒė˜d¦€‰‚€ƒėc¦€‰‚’nHow can I tell which NIC is displayed in the PACE Configuration window?nHow do I know which Device ID corresponds to which 3Com XL NIC?nHow Can I use a 3C509B and the 3C905/3C900 NICs in the same PC?nHow can I get a SCO driver?nHow do I remove the Fast EtherLink/EtherLink XL Software?nWhy is dRMON bound to a non-3Com NIC?nWhy does my HP VA PC hang at POST during memory check?ć—ItL f€/€^ŒŒZ¬V„,:€ƒė@c¦€‰‚€ƒėkc¦€‰‚’nHow do I update my EtherDisk 2.0 driver to the EtherDisk 2.1 driver?nWhy does the Fast EtherLink/EtherLink XL NIC connect at half duplex?P‘Ä1Kš’’’’[Ä) Do I have to configure the NIC?K#t( €F€˜˜€€‚’Do I have to configure the NIC?ėÄ) / ,€×€˜€‚€€€‚’Do I have to configure my 3Com PCI NIC for my computer?PCI is a self-configuring bus architecture. Most of the time you will only need to install the board in your system; PCI does the rest. However, on some PCI computers (mostly with combination PCI/ISA or PCI/EISA buses in the same machine), you may be required to configure the computer's BIOS manually after installing your PCI NIC. If you need to configure your system manually, refer to the owner's guide for your computer. 3Com testing has shown, for example, that the AST Premmia GX P90 seems to require you to run the EISA configuration utility once you install the board to make sure that the I/O base address of the device does not conflict with other devices in the system.W&€ 1ŠŠā\€ Ņ q Which PCI slot is best for my PCI NIC?R*) Ņ ( €T€˜˜€€‚’Which PCI slot is best for my PCI NIC?Ÿp€ q / ,€į€˜€‚€€€‚’Which PCI slot is best for my 3Com PCI NIC?3Com PCI NICs are designed to work in any bus mastering PCI slot. The Fast EtherLink/EtherLink XL is not supported in "slave-only" slots. The NICs perform best in those slots that support bus mastering data transfers. Refer to your owner's manual for information on which slots support bus mastering data transfers.X'Ņ É 13Ž š]É   Is the NIC compliant with PCI Spec 2.1?S+q  ( €V€˜˜€€‚’Is the NIC compliant with PCI Spec 2.1?ŁÉ  ) €³€˜€‚€‚’Is the Fast EtherLink XL/EtherLink XL NIC compliant with the PCI Specification v. 2.1?3Com's Fast EtherLink XL/EtherLink XL NICs comply with PCI Spec 2.1. For further details, please see the product data sheet.O m 1³€Š^m · B@Which slots are bus mastering?J" · ( €D€˜˜€€‚’Which slots are bus mastering?Jm B@5 8€•€˜€‚€€€€€‚’Which PCI slot(s) are bus mastering in my PCI machine?Generally, if you have three PCI slots in a system, one slot will be designated as a "slave-only" slot (that is, it does not support bus mastering data transfers). Slots are not always marked clearly to distinguish between slave-only and bus mastering slots. It is best to refer to your owner's manual or contact your computer manufacturer for this information. Also, make sure that you have the latest version of your system's BIOS. Phone numbers for leading PCI sys· B@ tem manufacturers are included earlier in this help.N· @1„ZƒŽ _@Ł@MDWhich interrupt should I use?I!B@Ł@( €B€˜˜€€‚’Which interrupt should I use?t9@MD; D€s€˜€‚€€€€€€€‚’Which interrupt should I use with my 3Com PCI NIC?Unless your system is a PCI-ISA/EISA combination computer that requires manual configuration, you should not have to worry about setting interrupts. However, if your computer is not self-configuring, you will need to set your PCI NIC's interrupts manually. To do this, you may need to set a jumper on your motherboard or set the interrupt in the system's BIOS. In either case, you will need to assign the PCI interrupt (INTA) to any available interrupt not being used by an ISA or EISA add-in board already in your computer. Keep in mind that the interrupt configuration on your computer's motherboard and in your BIOS must match. Since PCI supports shared interrupts, multiple 3Com PCI NICs can use the same PCI interrupt (except as noted in the next topic).[*Ł@ØD1žʆ€`ØDžDkHDoes my PCI NIC support shared interrupts?V.MDžD( €\€˜˜€€‚’Does my PCI NIC support shared interrupts?m>ØDkH/ ,€}€˜€‚€€€‚’Does my PCI NIC support shared interrupts?The drivers for the Fast EtherLink XL/EtherLink XL Bus Master NICs support shared interrupts. However, because there is no industry-standard way to support shared interrupts, other NICs may support them differently, or not at all. If you have another PCI NIC that does not support shared interrupts (for example, a SCSI host NIC), either contact the manufacturer for a shared interrupt driver or try running the system setup program to assign it a different interrupt. 3Com has found that OS/2 version 1.3 does not support shared interrupts, but it is only a problem if you are using the OS/2 NDIS 2.01 driver in LAN Manager version 2.2. If this is a problem, try using the DOS configuration utility to give each NIC a different IRQ, and change the BIOS on your system to match.PžD»H1š‰Zƒa»HIęKWhat interrupts should I avoid?K#kHI( €F€˜˜€€‚’What interrupts should I avoid?ą±»HęK/ ,€c€˜€‚€€€‚’What interrupt should I avoid using with my 3Com PCI NIC?You should avoid using any interrupts used by ISA/EISA boards that do not properly support shared interrupts (level-triggered). If you do not know or are unsure whether your NIC supports shared interrupts, then avoid using them. In addition, try to avoid using the same interrupt as that of your local hard drive (normally IRQ 14 for IDE drives and IRQ 11 for most SCSI host NICs), since not all hard drives support shared interrupts at this time. For Novell NetWare servers, you should also avoid using IRQ 7 or 15. These IRQs only support nonshared devices and may cause problems if they are shared between two devices.W&I=L1ŲCŠʆb=LL6MIs my 3Com PCI NIC a 3.3 V or 5 V NIC?R*ęKL( €T€˜˜€€‚’Is my 3Com PCI NIC a 3.3 V or 5 V NIC?§=L6M( €ž€˜€‚€‚’Is my 3Com PCI NIC a 3.3 V or 5 V NIC?The 3Com NIC currently being shipped is a 5 V NIC. It will not fit in a 3.3 V slot.MLƒM1«؋š‰cƒMĖMEOMicrosoft EMM386.EXE problemH 6MĖM( €@€˜˜€€‚’Microsoft EMM386.EXE problemzEƒMEO5 8€‹€˜€€€‚€€€‚’Why won’t the 3Com PCI NIC driver load when EMM386.EXE is loaded?Microsoft's EMM386.EXE versions 4.48 and earlier may conflict with some PCI computer’s ROM BIOS. If you are using EMM386 version 4.48 or earlier, make sure you run A:\MSUPDATE\MSUPDATE.EXE, which replaces your current EMM386 with an updated version.\+ĖM”O1§śCŠd”O €ȃCannot execute programs loaded over the netW/EO €( €^€˜˜€€‚’Cannot execute programs loaded over the net”O €EOõĢ”O‚) €™€˜€‚€‚’The NIC works fine in DOS, but I can't execute programs loaded over the net when Windows is running.If the EMM386.EXE memory manager is not loaded by your CONFIG.SYS file, Windows loads an equivalent driver when Windows is started. The problem is that the EMM386 Windows emulator that ships with Windows 3.1 and Windows for Workgroups 3.11 is not compatible with PCI computers. To solve this problem, put the following statement in your CONFIG.SYS file:I! €J‚( €B€˜‘€‚€ ‚’DEVICE=C:\DOS\EMM386.EXE NOEMSE!‚‚$ €B€˜€‚’immediately following the lineBJ‚т( €4€˜‘€‚€ ‚’DEVICE=C:\DOS\HIMEM.SYS÷Ņ‚ȃ% €„€˜€‚’Make sure you are running version 4.49 or newer. If you are not sure which version of EMM386 you have, run EMM386UP.BAT on the EtherDisk 1 diskette. This program will update EMM386 if the update is needed.Z)т"„1YŲ؋e"„w„Ÿ†NetWare 3.11 server packet buffer problemU-ȃw„( €Z€˜˜€€‚’NetWare 3.11 server packet buffer problemžz"„…$ €ō€˜€‚’Two EtherLink XL NICs cannot be loaded in my NetWare 3.11 server. When the second one loads, it generates the message:‡Yw„œ…. ,€²€˜‘€‚€ €€ ‚’Attempt to reinitialize re-entrant module FAILED. LAN driver is not loaded."Ž…Ÿ†% €½€˜€‚’The default NetWare 3.11 Packet Receive Buffer is not large enough for the 3C90X NIC. Set the Minimum Packet Receive Buffer to 50 or more to resolve the problem. Consult Novell documentation for detailed instructions.T#œ…ó†1†+śfó†B‡—ˆACERPOWER ROM configuration problemO'Ÿ†B‡( €N€˜˜€€‚’ACERPOWER ROM configuration problemU,ó†—ˆ) €Y€˜€‚€‚’Why does the ACERPOWER system indicate that ROM is installed, but one is not present?The ACERPOWER BIOS (BIOS version V2.0 486/DX2 66 MHz) PCI system incorrectly indicates (through PCI information) that there is a ROM on the PCI NIC. Contact ACER to get an updated BIOS to correct this problem.Q B‡čˆ1 ’Ųgčˆ4‰ ŠAre my drivers Novell-certified?L$—ˆ4‰( €H€˜˜€€‚’Are my drivers Novell-certified?Ł°čˆ Š) €a€˜€‚€‚’Are my Fast EtherLink XL/EtherLink XL Bus Master ODI drivers Novell certified?3Com's Fast EtherLink XL/EtherLink XL Bus Master ODI drivers are Novell tested and certified.T#4‰aŠ1¾’’’’+haŠ°Š=Incorrect configuration set by BIOSO' Š°Š( €N€˜˜€€‚’Incorrect configuration set by BIOSžwaŠN‹' €ī€˜€€‚’When I attempt to run the DOS configuration utility for the 3C905-XL and 3C595-TX NIC, the following error appears:²‡°ŠŒ+ $€€˜‘€‚€ ‚’Incorrect configuration is set by the BIOS.Get an updated BIOS from the PC manufactureror try to install the NIC in another slot."=N‹=% €1€˜€‚’This error occurs in the Micron Millennia (M55HI) computer with BIOS version 3, and only in slots 1, 2, and 3. The solution is to install the NIC in slot 4, or if slot 4 is unavailable, disable Plug and Play in your system's BIOS. This eliminates the error in all four slots.c2Œ 1ŽnŸ i śWHow do I remove the 3Com icon from my system tray?Z5=ś% €j€˜˜€‚’How do I remove the 3Com icon from my system tray?]. W/ ,€]€˜€‚€€€‚’How do I stop the 3Com tray icon from appearing in my system tray?Double-click on the 3Com icon to start the NIC Diagnostics program. In the right bottom corner of the main window, click the Enable Tray Control box to remove the check mark. Exit the program and the icon will not appear anymore.e4ś¼1< ‚j¼$ĄsĀWhy does my NIC appear disabled in Windows 95 OSR 2?\7W$Ą% €n€˜˜€‚’Why does my NIC appear disable¼$ĄWd in Windows 95 OSR 2?O¼sĀ2 2€;€˜€‚€€€€‚’During the Windows 95 OEM Service Release 2 (OSR 2) over the network install using 3C90X NDIS, a dialog box appears saying I have an incompatible driver and that I have to get a Windows 95 compliant driver. Even if I bypass this message and proceed, the device appears disabled in Device Manager. Why?This failure has been observed with other NICs running setup of OSR2 over the network. This failure occurs only with the OSR2 version of Win95 and not with Win95 ‘gold release’. Please contact Microsoft for additional support.k:$ĄŽĀ1)Ÿ %„kŽĀ@Ć8ÅWhy does the 3Com Diagnostics say my NIC is not connected?b=sĀ@Ć% €z€˜˜€‚’Why does the 3Com Diagnostics say my NIC is not connected?ųĖŽĀ8Å- (€—€˜€‚€ €‚‚’Why does the 3Com NIC diagnostics program display this message when I select the AUI interface? What happens if I ignore the message?The NIC is not currently connected to a network. Please check the media type connections of the client and server and change if necessary.This is an erroneous message. The NIC will function correctly if the message is ignored. You could verify by running the Echo Server test with another 3Com NIC for reassurance.l;@ƤÅ1‚ž…l¤ÅĘģĒHow can I tell which NICs are displayed in the PACE Window?c>8ÅĘ% €|€˜˜€‚’How can I tell which NICs are displayed in the PACE Window?囤ÅģĒJ b€7€˜€€€€€€‚‚‚€€‚€€€€‚’If I install more than 1 NIC, in the PACE configuration window, using the ‘Properties’ tab in the 3Com NIC Diagnostics program, the display shows3Com Fast EtherLink XL/ EtherLink XL3Com Fast EtherLink XL/ EtherLink XL #2How can I tell which NIC is which?To determine the identification of the NIC, click the ‘General’ tab of the 3Com NIC Diagnostics program. This displays the NICs installed.g6ĘSČ1ä%„O‡mSȵČhŹHow do I know which Device ID applies to which XL NIC?b:ģĒµČ( €t€˜˜€€‚’How do I know which Device ID applies to which XL NIC?rNSČ'É$ €œ€˜€‚’The following is the corresponding list of Device Ids for the 3Com XL NICs:AɵČhŹx ¾€“€^ŒŒZ¬V„,:€ƒ€€ €€ €‚€ƒ€€ €€ €‚€ƒ€€ €€ €‚€ƒ€€ €€ €‚’n3C905-TX 3Com Fast EtherLink XL NIC - 9050n3C905-T4 3Com Fast EtherLink XL NIC - 9051n3C900-TPO 3Com EtherLink XL NIC - 9000n3C900-COMBO 3Com EtherLink XL NIC - 9001_.'ÉĒŹ1Äž…w nĒŹ!Ė“ĖCan I use the 3Com XL NIC on the DEC Alpha PC?Z2hŹ!Ė( €d€˜˜€€‚’Can I use the 3Com XL NIC on the DEC Alpha PC?“oĒŹ“Ė$ €Ž€˜€‚’Yes the NDIS driver for the DEC Alpha PC for Windows NT 4.0 ships with the Fast EtherLink/EtherLink XL NICs.e4!ĖĢ1n 5‹oĢyĢ¶ĻHow Can I Use a 3C509B-COMBO with a 3C905/3C900 NIC?`8“ĖyĢ( €p€˜˜€€‚’How Can I Use a 3C509B-COMBO with a 3C905/3C900 NIC?= Ģ¶Ļ0 .€€˜€‚€‚€€‚’The EtherLink III loses the network connection when I install a 3C905 NIC into the same PC with a EtherLink III 3C509B NIC. How can I resolve this issue?This situation only occurs if you attempt to run the 3Com NIC Diagnostics on the 3C905 NIC when the 3C509B (in Plug and Play mode) is still connected to the network. When the diagnostics run, the operating system reallocates resources to the 3C905 NIC which causes the 3C509B NIC to lose network connection.To avoid this network connection loss, boot the PC into MS-DOS mode and execute the Configuration and Diagnostic program for the 3C509B. Under Adapter Configuration, disable Plug and Play, and save the changes. Reboot with Windows 95 and Windows 95 will assign new resources and the driver will function properly.LyĢ13š‡RƒpUWHow Can I get a SCO Drive¶Ļ¶Ļr?G¶ĻU( €>€˜˜€€‚’How Can I get a SCO Driver?`<µ$ €x€˜€‚’You can get the driver from the 3Com world wide web site.ĄUŹU x€€V˜˜øJ„8:€ ƒ€€ €‚€ ƒ€‚€ ƒ€‚€ ƒ€‚€ ƒ€‚’1Enter the 3Com URL - http://www.3Com.com.2Go to the 3Com Customer Support section.3Click on Software Library.4Click on Latest Adapter Files.5Download the file you need.eµW( €Ź€˜€‚ƒ‚ƒ‚’There are two files:90XSCO3.EXE is for SCO Open Desktop v.390XSCO5.EXE is for OpenServer Rel.5j9ŹĮ1Ÿ€ŌqĮ&”How do I remove the Fast EtherLink/EtherLink XL software?e=W&( €z€˜˜€€‚’How do I remove the Fast EtherLink/EtherLink XL software?:Į`& €)€˜€‚‚’How do I remove the software that comes with Fast EtherLink/EtherLink XL NIC from my PC if I have a compatibility problem?3Com has developed a uninstall program for uninstalling the software that comes with the Fast EtherLink XL/EtherLink XL NIC, except for the 3Com dRMON SmartAgent PC Software. Unfortunately 3Com finished the development of the uninstaller after the manual was printed, so for more information and instructions on how to use the uninstaller please read UNINSTAL.TXT in the root of the EtherDisk 2 diskette.4&”1 2€€ ˜°Œ!Aa”€‚’V%`ź1P€µrź;Z Why is dRMON bound to a non-3Com NIC?Q)”;( €R€˜˜€€‚’Why is dRMON bound to a non-3Com NIC?ėµź& 6 :€k€ ˜°Œ!Aa”€€‚‚’Why is dRMON bound to non-3Com NIC according to the Properties screen? I thought dRMON is a feature for 3Com only.After the installation of a Fast EtherLink/EtherLink XL NIC and a 3rd party NIC, if you check the Bindings of the 3rd party NIC within the Properties screen, you will notice that there is a check mark in the box for "3Com dRMON SmartAgent". This check mark in the indicates that the dRMON agent is given the opportunity to bind with the 3rd party NIC if possible. It is not an indication that it is actually bound to it. dRMON will only bind to the first 3Com NIC that it finds and not to any other manufacturers' cards nor multiple 3Com NICs, even if it is installed.4;Z 1 2€€ ˜°Œ!Aa”€‚’g6& Į 1ŌšsĮ #  Why does my HP VA PC hang at POST during memory check?b:Z # ( €t€˜˜€€‚’Why does my HP VA PC hang at POST during memory check?ć«Į  8 >€W€ ˜°Œ!Aa”€€‚‚‚‚’After installing a 3C90X NIC in my HP VA machine and attached to the network, if I performs a warm boot, the machine will hang at POST during memory check.The PC only hangs if the NIC is installed onto a live network. Since HP implements a PCI RESET a bit differently than how the 3C90X detects this signal, the NIC is still active at the time of reboot. Please contact HP for an updated BIOS that resolves this issue.q@# w 1µtw ć ĘAHow do I update my EtherDisk 2.0 driver to EtherDisk 2.1 driver?lD ć ( €ˆ€˜˜€€‚’How do I update my EtherDisk 2.0 driver to EtherDisk 2.1 driver?Ē‘w Ŗ 6 :€#€ ˜°Œ!Aa”€€ƒ‚’If I have Windows 95 and the driver from EtherDisk 2.0 installed in my PC now, how do I update the Windows 95 driver from the 2.1 EtherDisk?}Jć '3 6€”€ ˜°Ž!±AŃa€‚‚’To update the driver and the support files follow these instructions: «Ŗ =@_ Œ€W€V˜˜øJ„8:€ ƒ€‚€ ƒ€‚€ ƒ€‚€ ƒ€‚€ ƒ€‚€ ƒ€‚€ ƒ€‚’1Open the Network Control Panel and click Add.2Select Adapter and Click Add.3Click Have Disk and insert the EtherDisk 2 Diskette into the A drive and click OK.4Select the NIC you have and click OK.5Remove all EtherLink XL adapters from the control panel by selecting them one at a time and clicking Remove.6Click OK. 7When Windows 95 asks the question'=@  'Do you wish to reboot the system', click YES.T'‘AB R€%€V˜˜øJ„8:€ ƒ€€‚€ ƒ€‚€ ƒ€‚’8When Windows 95 starts, it acknowledges the NIC, and the Windows 95 installing software message appears on the screen.9Select 'Driver from Disk Provided by Hardware Manufacturer' and click OK. 10Insert the EtherDisk 2 diskette in the A: drive and click OK.5=@ĘA2 4€€ ˜°Ž!±AŃa€‚’uD‘A;B1ך’’’’u;B«BQEWhy does the Fast EtherLink/EtherLink XL NIC connect at half duplex?pHĘA«B( €€˜˜€€‚’Why does the Fast EtherLink/EtherLink XL NIC connect at half duplex?¦l;BQE: B€Ł€ ˜°Œ!Aa”€€‚‚€‚’Why does the Fast EtherLink/EtherLink XL NIC only connect at half duplex when I connect it to a full duplex hub, when I configured the NIC's duplex to Auto Select?When the NIC duplex is configured for Auto Select and the diagnostics or the driver initializes, it attempts to establish a link with the hub to determine its duplex capability. If this communication is unsuccessful, the NIC will connect at half duplex for stability. If you know that the hub does support full duplex, you could force the NIC to connect at full duplex by running the configuration utility and setting the option of Duplex to full.E«B–E1’i‰’’’’v–EÖE7MKnowledgeBase Topics@QEÖE( €0€˜˜€€‚’KnowledgeBase Topics­ˆ–EƒF% €€˜€‚’The following KnowledgeBase entries are organized alphabetically by hardware platform, operating system, or network operating system. ^ÖE£HĀ R½€^ŒŒZ¬V„,:€ƒćŌ‚¦€‰‚€ƒć’‚¦€‰‚€ƒć*ƒ¦€‰‚€ƒć€ƒ¦€‰‚€ƒćUƒ¦€‰‚€ƒćś?¦€‰‚€ƒć{@¦€‰‚€ƒćų>¦€‰‚€ƒć#?¦€‰‚€ƒćN?¦€‰‚€ƒćžA¦€‰‚’nCompaq 4704 (USB) (Pentium 133)nCompaq DeskPro 2000 P5120nCompaq Presario 8702 (Pentium 133)nDell (Pentium 133)nDell Dimension XPS (Pentium 133)nDiamond Stealth 64 PCI Video NICnGateway 2000 (Pentium 133)nGateway P5133nGateway P590nHP Vectra XU-6150nIBM Clones With Award BIOS 4.50gŚHƒF}J’ ņ€‘€^ŒŒZ¬V„,:€ƒćØA¦€‰‚€ƒćP@¦€‰‚€ƒć%@¦€‰‚€ƒćĻ?¦€‰‚€ƒć¤?¦€‰‚€ƒė_]¦€‰‚€ƒė·^¦€‰‚’nMicron Milennia with Diamond Stealth 3D VideonTyan 16 Dual Pro with Matrox Video, PVRnWhat is PIPELINE in the NET.CFG file for the 3C90X NIC?nWindows 95 nWindows NT 3.51n3Com NIC Diagnostics fail on the Zenith Data System P5-75nTwo Fast EtherLink/EtherLink XL NICs in a NetWare Serverŗˆ£H7M2 2€€˜€‚€€€€‚’Notwithstanding the warranty for the 3Com Software which is mentioned in both the user guide and the warranty card accompanying the 3Com Products, the KnowledgeBase is being provided to you “AS IS” without any warranty of any kind, and 3Com specifically disclaims any and all warranties or conditions of merchantability and fitness for a particular purpose. The recommendations given here have not been subjected to formal testing and may not provide a solution for you. 3Com does not warrant that the solutions contained in the KnowledgeBase will meet your requirements or that the recommended solutions will work for all configurations.J}JM1»’’’’_ wMĘML€Compaq 4704 (Pentium 133)E7MĘM( €:€˜˜€€‚’Compaq 4704 (Pentium 133)f=M,O) €{€°€‚‚’Compaq 4704 (Pentium 133) with (Universal Serial Bus)Windows 95NetWare 3.12NIC not working properly in 95Whatever IRQ was assigned to the NIC, the Universal Serial Bus (USB) device used the same IRQ. Disable the USB in the BIOS (CMOS). For Compaq systems with USB capability, you must do one of the following:¦oĘMŅO7 >€Ž€^ŒŒZ¬V„,:€ƒ€‚€ƒ€‚’nDisable the USB to use the PCI bus master NICnUse an EISA/ISA NIC if you want to use the USB devices.n@,OL€. ,€€€˜€ėńP¦‰‚’ŅOL€7MFor an overview, click Universal Serial Bus implementation.NŅOš€1’’’’’’’’xš€ć€“‡Universal Serial Bus OverviewI!L€ć€( €B€˜˜€€‚’Universal Serial Bus Overview„tš€ˆƒ1 0€é€˜€€€€€‚’Compaq is licensing its own host controller design, which includes the essential technical "blueprints" for logically and electrically integrating the Universal Serial Bus (USB) controller into chip sets, so that vendors will not have to create their own ASIC designs from scratch. This will reduce the cost and time it would take companies to develop their own products, enabling USB-ready components to be available much more quickly and at lower costs. It should also help advance the implementation of USB within the PC industry while increasing the development of products that comply with industry-wide standards.ī怔…+ $€Ż€˜€€€‚’USB is an emerging industry standard that defines how a large number and wide variety of peripherals can be connected to a single physical connector at the back of the PC, ultimately replacing the multiple ports currently required. This is accomplished by having several peripherals "chained" to one another in a tree-like configuration. For example, the mouse, joystick, and telephone can be connected to the keyboard, which is connected to the monitor, which is connected to the system.܈ƒ“‡7 <€¹€˜€€€€€€€‚’USB is a serial bus capable of supporting up to 127 peripherals and operates at 12 megabits per second (Mbps), approximately the speed of Ethernet (10 Mbps). USB supports low- to mid-speed peripherals like keyboards, mice, joysticks, virtual-reality game input devices, audio, printers, and telephony devices. Phoenix has been involved with USB for over a year and has authored the USB PC Compatibility Specification and the Mass Storage Device Class Specification.J”…ž‡1y—‰ą yž‡Cˆ‹‹Compaq DeskPro 2000 P5120E“‡Cˆ( €:€˜˜€€‚’Compaq DeskPro 2000 P5120±‰ž‡ōˆ( €€˜€‚‚’Compaq DeskPro 2000 P5120Windows 95Does not detect NICOn booting, Windows 95 won't detect the NIC with the following configuration:ś¤Cˆī‰V z€I€^ŒŒZ¬V„,:€ƒ€‚€ƒ€€ €‚€ƒ€‚€ƒ€‚€ƒ€‚’nCompaq DeskPro 2000 P5120 MHz ( latest Compaq BIOS)n3C905-TX PCI NICnWindows 95nNetWare 3.12 = NOSnClient 32 for Windows 95 = (NDIS drivers)Į’ōˆƊ/ ,€%€˜€€€‚€ ‚’This is true -up even though the DOS diagnostics work correctly and the NIC is configured correctly.To get Windows 95 to recognize the NIC:Ü„ī‰‹‹7 <€K€V˜˜øJ„8:€ ƒ€‚€ ƒ€‚’1Plug the NIC into slot 1.2Go to the Control Panel, System icon, Device Manager, Other Devices, and remove any entries for Ethernet boards that are defined.S"ƊŽ‹1Ļ_ $ zŽ‹,ŒŹŽCompaq Presario 8702 (Pentium 133)N&‹‹,Œ( €L€˜˜€€‚’Compaq Presario 8702 (Pentium 133)'žŽ‹S) €ż€˜€‚‚’Compaq Presario 8702 (Pentium 133)Windows 95NetWare 3.12Will not connect to Novell Network You cannot see or connect to the Novell network running the Client for Microsoft NetWare networks under Windows 95 with the device drivers working properly.w ,ŒŹŽW |€A€V˜˜øJ„8:€ ƒ€‚€ ƒ€‚€ ƒ€‚€ ƒ€‚€ ƒ€‚€ ƒ€‚’1Go to the CMOS setup by pressing F10.2Go to System.3Go to PCI configuration, PCI Ethernet, and assign IRQ=10.4Reboot the machine and check the IRQ under Control Panel, System, Device Manager, Computer.5The PCI devices should now have their own interrupt.6Reboot.Q S1Žą " {gŠĮDell Dimension XPS (Pentium 133)L$ŹŽg( €H€˜˜€€‚’Dell Dimension XPS (Pentium 133)Ț;Ą. *€5€˜€‚€€‚’Dell Dimension XPS (Pentium 133)Windows 95NIC Is Not DetectedWhen Windows boots up, it can't find the 3g;ĄŹŽC905-TX NIC in the following configuration:ĆvgžĄM j€ģ€^ŒŒZ¬V„,:€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€€ €‚’nDell Dimension XPS P133 with the latest BIOSnNOS = Windows NT 3.51nOS = Windows 95nNIC = 3C905-TX Ņ¬;ĄŠĮ& €Y€˜€‚‚’The problem occurs even though the diagnostic runs without error. Different IRQ settings make no difference.Try inserting the NIC into the PCI slot closest to the CPU.CžĄĀ1Ā$ ņ„ |ĀQĀāĘDell (Pentium 133)>ŠĮQĀ( €,€˜˜€€‚’Dell (Pentium 133)rHĀĆĆ* "€‘€˜€‚‚‚’Dell (Pentium 133)Windows for WorkgroupsNetWare 3.12Could not hook up to HP 3000 mainframe using WRS Reflection Software.You can log in to a Novell NetWare 3.12 server and access the network, but cannot log in to the HP 3000 mainframe using the software Reflection Network Series for DOS version 2.1. The error message:O'QĀÄ( €N€˜‘€‚€ ‚’Searching for unique NS node name...äĆĆ!Å+ $€É€˜€€€‚’is displayed and the PC hangs. If the 3C905-TX is replaced with a 3C509 NIC, you can connect to the HP 3000 mainframe. The solution is to add Ethernet Only to the Protocol TCP2PDIS statement in the NET.CFG file, as follows:`*āĘ6 :€U€˜‘€‚€ ‚’Protocol TCP2PDISIPAddress0 xxx xxx xxx xxxHostsPath C:\WRQNETDefaultGateway0 xxx xxx xxx xxxTCPBufferSize 1526PCDNSHostName "USER.DOMAIN.ORG"TCPSessions 5Node NODENAMEDomain DOMAINOrganization ORGSubnetMask0 xxx xxx xxx xxxNumTCPBuffers 10DNSServerAddr xxx xxx xxx xxxETHERNET ONLYa=!ÅāĘ$ €z€˜€‚’You should now be able to connect to the HP 3000 computer.KĘ-Ē1" ę‡ }-ĒsĒĻŹGateway 2000 (Pentium 133)FāĘsĒ( €<€˜˜€€‚’Gateway 2000 (Pentium 133)ēæ-ĒZČ( €€˜€‚‚’Gateway 2000 (Pentium 133)Windows for WorkgroupsNetWare 3.12If the Network seems to be running slowly at login, add these extra statements to the NET.CFG file in the NetWare directory:‹_sĒåČ, (€¾€˜‘€‚€ ‚’LINK DRIVER 3C90XNO_PIPELINENETWARE DOS REQUESTERCACHE BUFFER SIZE = 1500PB BUFFERS = 10źøZČĻŹ2 2€q€˜€€€‚€€‚’On some Gateway systems running Windows 95, 3Com has noticed that the computer does not detect the NIC at boot-up. The driver appears to install correctly and all DOS diagnostics run successfully, but when you click on NIC driver description in the Device Manager, you get the error message: "device driver failure."Try inserting the NIC into slot 2. Slot 1 works fine for a 3C59X-TX NIC, but the 3C90X does not work in PCI slot 1.> åČ Ė1³ņ„ ~ ĖFĖ Gateway P51339ĻŹFĖ( €"€˜˜€€‚’Gateway P5133Ŗ ĖšĖ) €€˜€‚‚’Gateway P5133Windows 95NetWare 3.12Client 32 would not work with TCPIP.This problem occurred in the following environment:¾FĖ Ķ^ Š€}€^ŒŒZ¬V„,:€ƒ€‚€ƒ€€ €‚€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€‚’nGateway P5-133n3c905-TX NICnWindows 95nNetWare 3.12nClient for NetWare Networks and Client for Microsoft Networks installednIPX/SPX, NETBEUI, and TCP/IP protocols¼ŠšĖ 2 2€€˜€€€€€‚‚’You were able to connect to all NetWare 3.12 servers, Microsoft peer clients, and the protocols IPX/SPX, NETBEUI, and TCP/IP protocols without any problem. There were other workstations using Client 32. You did an over-the-network install of Client 32. Remove Client 32 through the Novell UNINSTALL utility and connect back to the Novell NetWare 3.12 server using the regular Client for NetWare networks. Reinstall Client 32 by deselecting the Default Option of " UPGRADE NDIS DRIVERS TO ODI AUTOMATICALLY, IF AVAILABLE. Finish the install, reboot, and log in through the Client 32 login script and browse the network using all resources. Ķ ĻŹ= ĶI1=ę‡ õ IGateway P5908 ( € €˜˜€€‚’Gateway P590 åI' €Ė€˜€‚‚’Gateway P590PCI Specification v2.0 Not Supported On a Gateway 2000 P590 PCI computer with a BIOS at 1.01.05.axy, an Adaptec 2940, and an ATI Mach 64 video card, Windows for Workgroups (WFW) does not load or bind the 3Com NIC properly. The Gateway P590 was made before the PCI 2.0 specification came out. So, the Adaptec card is not be supported in this machine, or is bus mastering. There are two newer levels of BIOS available, but they may not provide PCI 2.0 support as well.BĻ1y €Ļ THP Vectra XU-6150= ( €*€˜˜€€‚’HP Vectra XU-6150/Ļ;( €€˜€‚‚’HP Vectra XU-6150, Matrix VideoWindows NTNIC not recognized by 3Com Configuration & Diagnostics Program When Windows NT loads the driver, the machine does a screen dump. The 3C90X NIC is not recognized by 3Com's diagnostics for the following configuration.¶i ńM j€Ņ€^ŒŒZ¬V„,:€ƒ€‚€ƒ€€ €‚€ƒ€‚€ƒ€‚’nHP Vectra XU-6150nWindows NT 3.51, 3C905-TXnMatrox video cardnBIOS, revision GG.06.03c?;T$ €~€˜€‚’Put the 3C90X in slot 2 and the Matrix video card in slot 3.Q ń„1SÉ ’’’’„ńIBM Clones With Award BIOS 4.50gL$Tń( €H€˜˜€€‚’IBM Clones With Award BIOS 4.50g"ģ„6 :€Ł€˜€‚‚‚€€ƒƒƒ‚’IBM Clones With Award BIOS 4.50gWindows 95, Windows For WorkgroupsNIC using IRQ 0The Windows 95 and Windows for Workgroups configuration utilities running in IBM clones with Award BIOS 4.50g automatically set the 3Com NIC's IRQ to level 0, which caused the operating system to fail to detect the NIC installed in the computer.Set the PCI configuration for slot 1 in the BIOS setup program to:Slot 1 - RIGHT Latency Timer80 PCI Clock Using IRQ10 Trigger/RoutingLevel/Auto^-ńq1_ ¹ ‚qŹ³ Micron Milennia with Diamond Stealth 3D VideoY1Ź( €b€˜˜€€‚’Micron Milennia with Diamond Stealth 3D Video(õqņ 3 4€ė€˜€‚€€€€‚’Micron Millennia with Diamond Stealth 3D VideoIncorrect configuration is set by the BIOSWhen attempting to run the diagnostics for the 3C905-XL and 3C595-TX on a Micron Millennia M55HI with Stealth 3D video, the following error appears:ꏶ + $€3€˜‘€‚€ ‚’!! Error !!! Incorrect configuration is set by the BIOS.Get an updated BIOS from the PC manufacturer ortry to install the adapter in another slot. ż×ņ ³ & €Æ€˜€‚‚’The error appears in slots 1, 2, and 3, but not 4.Install the NIC in slot 4. If slot four is not available, disable the PnP option in the Advanced area of the BIOS. This eliminates the error in all four slots.X'¶  1÷“ É ƒ ^ $Tyan 16 Dual Pro with Matrox Video, PVRS+³ ^ ( €V€˜˜€€‚’Tyan 16 Dual Pro with Matrox Video, PVR ā h ( €Å€˜€‚‚’Tyan 16 Dual Pro with Matrix Video, PVRWindows NT 4.0 WorkstationNIC not recognized by 3Com Diagnostics Neither the 3Com diagnostics nor Windows NT 4.0 workstation recognizes the 3C90X NIC in the following configuration:&Ö^ ŽP n€­€^ŒŒZ¬V„,:€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€‚€ƒ€‚’nTyan motherboard 16 dual Pentium 200 MHz with 5 PCI slotsnAward BIOS 4.5nWindows NT 4.0 workstationnMatrox Video 2 Mb RAM (PCI)nDigital Perception video recorder (PCI) (used for video editing)–rh $$ €ä€˜€‚’Move the 3C90X NIC to slot 2, the Digital Perception video card to slot 3, and the Matrix video card to slot 4.h7ŽŒ1VI… _ „Œ @×EWhat is PIPELINE in the NET.CFG file for the 3C90X NIC?c;$ @( €v€˜˜€€‚’What is PIPELINE in the NET.CFG file for the 3C90X NIC?Œ @$Ó›ŒßB8 >€7€˜€‚€€€€€€‚’What is PIPELINE in the NET.CFG file for the 3C90X NIC?Novell implemented a new feature in its IPX protocol that allows a faster and robust hand-off from the driver to the protocol stack. This feature is known as pipeline mode. This means with the Parallel TaskingØ feature, even if the frame length of the packet is unknown because it has not been read yet, the driver can still pass up a “no known frame length” value to the protocol and have the protocol allocate a set buffer for the packet. This is implemented by setting the PB register to -1, which allows Novell's IPX protocol to take full advantage of 3Com's integrated Parallel Tasking feature.Ń« @°E& €W€˜€‚‚’Since pipeline is relatively new, only Novell's IPX protocol supports it. Other implementations of IPX from Microsoft, or from ODIPKT, ODINSUP, as well as older versions of LSL, IPXODI, do not support this feature and pipeline needs to be turned off in order for it to work. A routine in the driver checks to see if you are running Windows or not. If the pipeline feature is commented out in the NET.CFG file, the pipeline mode will be active until the user enters into Windows. At that point, pipeline mode is dynamically disabled until the user exits Windows. If the pipeline feature is turned off in the NET.CFG, pipeline is disabled whether the you are in DOS or Windows.'ßB×E$ €€˜€‚’Q °E(F12-‡ “ …(FtFuHDiamond Stealth 64 PCI Video NICL$×EtF( €H€˜˜€€‚’Diamond Stealth 64 PCI Video NICĄ(FuHA P€€˜€‚€€€€€€€€‚‚’Diamond Stealth 64 PCI Video NICWindows 95Cannot Transfer Large Files.When using the 3C905-TX NIC in a 100 MHz Pentium (Intel motherboard with Triton chip set) system running Windows 95 equipped with a Diamond Stealth 64 PCI video card (configured at IRQ 9) and the 3C905-TX NIC (configured at IRQ 11), and connected to a peer-to-peer network, large files do not transfer.Use a standard VGA driver for the Diamond Stealth video card.; tF°H1= I… †°HēH €Windows 957uHēH( €€˜˜€€‚’Windows 95 ™V°H€LC T€­€˜€‚€€€€€€€‚‚€€‚’Recognizes NIC improperly as PCI Ethernet ControllerAfter installing the 3C90X NIC, Windows 95 senses a generic PCI Ethernet NIC rather than a 3Com Fast EtherLink XL NIC (3C900-TPO, 3C900-COMBO, OR 3C905-TX).Windows 95 will not recognize the NICs by name because it does not contain a native version of the NIC driver.Make sure you click on the Insert Driver Disk from the Manufacturer option to find the hardware and install it correctly using the EtherDisk diskette. If you still have problems loading the NIC and browsing, select Control Panel, then System, and select Device Manager. If there is a subheading named "? Other Devices" double-click to view the description. If there is a PCI Ethernet controller listed, highlight and remove it. Next, select the refresh button. The NIC will now be recognized correctly by Windows 95.ó®ēHsNE X€]€˜€‚€€€€€€€€€‚€ ‚’CD Files Not Found When Windows 95 detects the 3C905-TX NIC and installs the drivers from the EtherDisk diskette, it asks for files from the Windows 95 CD-ROM (beginning with NETAPI.DLL). When you enter the correct path to the CD-ROM the files are not found. The new NIC is detected and the drivers were installed, but the CD-ROM had not yet been initialized by 95.When Windows 95 asks for files from the CD ROM: €%€L €[ „€K€V˜˜øJ„8:€ ƒ€‚€ ƒ€‚€ ƒ€‚€ ƒ€€ €‚€ ƒ€€ €‚’1Press Cancel.2Go to Device Manager in the Control Panel.3Highlight and Remove the NIC from Network Adapters List.4Select Refresh. Windows 95 will re-detect the NIC and ask for the EtherDisk diskette and Windows 95 CD.5Enter the correct path to the CD-ROM when asked.sN €uH@sNL€1õ -‡ ‡L€‡€^‚Windows NT 3.51; €‡€( €&€˜˜€€‚’Windows NT 3.51 äL€’' €É€˜€‚‚’Windows NT 3.51OEMSETUP.INF Error Message When installing the Windows NT driver from the EtherDisk diskette for the 3C90X NIC, the system displays the following error message saying that it can't find the OEMSETUP.INF file:]5‡€ļ( €j€˜‘€‚€ ‚’error occurred can't find A:\WINNT\WINNT\El90X.SYSoK’^‚$ €–€˜€‚’Download the latest driver 3C90XN.EXE from the 3Com Web site or the BBS.d3ļĀ‚1«O‡’ ˆĀ‚!ƒ›„3Com NIC Diagnostics fail on the Zenith Data System_7^‚!ƒ( €n€˜˜€€‚’3Com NIC Diagnostics fail on the Zenith Data SystemzQĀ‚›„) €£€˜€€‚‚’Why do the 3Com NIC Diagnostics fail when I am using the Fast EtherLink/EtherLink XL in a Zenith Data System P5-75?In this PC, IRQ 3 is an unstable IRQ which the BIOS may attempt to allocate to an installed PCI device. Force the BIOS to allocate another IRQ. Refer to your PC user guide that shipped with your PC to access the BIOS.b1!ƒż„1[w  ‰ż„Z…„‡Compaq Proliant 5000 detected as a PCI RAM device]5›„Z…( €j€˜˜€€‚’Compaq Proliant 5000 detected as a PCI RAM deviceŚż„]‡) €µ€˜€€‚‚’Why does Windows 95 detect the Fast EtherLink/EtherLink XL NIC as a PCI RAM device when I install the NIC in a Compaq Proliant 5000?The Compaq Proliant 5000 is equipped with a primary and secondary PCI bus. If the NIC is installed in the secondary bus, Windows 95 mistakes it as a PCI RAM device. To avoid this problem, install the NIC in the primary PCI bus. Although Windows 95 may still find a PCI RAM card, it will also detect the 3Com NIC and install it correctly.'Z…„‡$ €€˜€‚’[*]‡߇1’ š‡Šß‡5ˆŠToshiba Tecra 720 CDT and Tecra 500 CS PCsV.„‡5ˆ( €\€˜˜€€‚’Toshiba Tecra 720 CDT and Tecra 500 CS PCsŻ­߇Š0 .€[€˜€‚€€‚‚ƒ‚‚’3Com has identified issues with the Toshiba Tecra 720 CDT and Tecra 500 CS PCs, running DOS, with a DeskStation V+ docking station, which may cause data loss.To avoid this situation, when using the Fast EtherLink/EtherLink XL (3C905-TX or 3C900) NIC and the NetWare DOS ODI client driver, edit the NET.CFG file and turn off the pipeline feature. For example:LINK DRIVER 3c90xNo_PipelineSave the file and reboot your PC.k:5ˆ}Š1O‡w‹}ŠćŠĀŒTwo Fast EtherLink/EtherLink NICs in a NetWare 3.11 Serverf>ŠćŠ( €|€˜˜€€‚’Two Fast EtherLink/EtherLink NICs in a NetWare 3.11 Serverß±}ŠĀŒ. *€c€˜€‚€€‚‚‚’Two EtherLink XL NICs cannot be loaded in my NetWare 3.11 server. When the second one loads, it generates the message, "Attempt to reinitialize re-entrant module FAILED. LAN driver is not loaded."The default NetWare 3.11 Packet Receive Buffer is not large enough for the 3C90X NIC. Set the Minimum Packet Receive Buffer to 50 or more to resolve the problem. Consult Novell documentation for detailed instructions.1ćŠóŒ1Ā’’’’’’’’ŒóŒƍ+ĀŒ% € €˜˜€‚’BBS‘móŒƍ$ €Ś€˜€‚’Click the BBS button to display the telephone numbers for accessing the 3Com bulletin board service (BBS).1ą1¢’’’’’’’’ąŽ…4ƍŽ% €€˜˜€‚’Tech SupportqFą…+ $€€˜€€€‚’Please refer to your Fast EtherLink XL PCI 10/100BASE-TX/T4 Network Interface Card User Guide or the EtherLink XL Parallel Tasking PCI Bus Master Network Interface Card User Guide for technical support information. In addition, this information is also available in the \HELP\SUPPORT.TXT file on the EtherDisk 1 diskette.1Ž¶1Ļ’’’’’’’’Ž¶ Ą(Į6… Ą% €"€˜˜€‚’Problem Report¶ Ą…š¶(Į, &€į€˜€‚€€‚’Click the Problem Report button to record a Problem Report for reporting to 3Com Customer Support.The Problem Report utility guides you through an on-line form for organizing information about your site and the problem you are having.1 ĄYĮ1p’’’’’’’’YĮĮĢĮ4(ĮĮ% €€˜˜€‚’Company Name?YĮĢĮ$ €6€˜€‚’Enter your company name.1ĮżĮ1s’’’’’’’’żĮ5ĀwĀ8ĢĮ5Ā% €&€˜˜€‚’Customer AddressBżĮwĀ$ €<€˜€‚’Enter your company address.15ĀØĀ1’’’’’’’’‘ØĀÜĀ,Ć4wĀÜĀ% €€˜˜€‚’Contact NameP,ØĀ,Ć$ €X€˜€‚’Enter a contact name within your company.1ÜĀ]Ć1w’’’’’’’’’]Ć’ĆŲĆ5,Ć’Ć% € €˜˜€‚’Contact PhoneF"]ĆŲĆ$ €D€˜€‚’Enter the contact phone number.1’Ć Ä1x’’’’’’’’“ ÄGÄŽÄ>ŲĆGÄ% €2€˜˜€‚’Contact E-Mail AddressG# ÄŽÄ$ €F€˜€‚’Enter the contact email address.1GÄæÄ1‡’’’’’’’’”æÄńÄGÅ2 ŽÄńÄ% €€˜˜€‚’Model TypeV2æÄGÅ$ €d€˜€‚’Enter the computer manufacturer and model type.1ńÄxÅ1£’’’’’’’’•xÅ­ÅĘ5GÅ­Å% € €˜˜€‚’Machine UsagerNxÅĘ$ €œ€˜€‚’Indicate whether the computer is being used as a client, a server, or both.1­ÅPĘ1½’’’’’’’’–PĘ€Ę Ē0 Ę€Ę% €€˜˜€‚’CPU TypeŒbPĘ Ē* $€Ä€˜€€€‚’From the pull-down bar, select the type of CPU your computer is using from the list provided.1€Ę=Ē1õ’’’’’’’’—=ĒnĒ2Č1 ĒnĒ% €€˜˜€‚’PCI Slotsğ=Ē2Č% €?€˜€‚’Enter the physical slot numbers with NICs installed. Typically, slot #1 is the slot closet tot he power supply. Consult your PC user guide for verification.1nĒcČ1Æ’’’’’’’’˜cČžČĖ;2ČžČ% €,€˜˜€‚’Bus-Mastering Slots~JcČĖ4 6€•€˜€€€€€€‚’Enter the physical slot number(s) that support bus mastering. Generally, if you have three PCI slots in a system, one slot will be designated as a "slave-only" slot (that is, it does not support bus mastering data transfers). Slots are not always marked clearly to distinguish between slave-only and bus mastering slots. It is best to refer to your owner's manual or contact your computer manufacturer for this information. Also, make sure that you have the latest version of your system's BIOS. Phone numbers for leading PCI system manufacturers are included in this help.1žČMĖ1Ŗ’’’’’’’’™MĖ…ĖžĖ8Ė…Ė% €&€˜˜€‚’Operating SystemyOMĖžĖ* $€ž€˜€€€‚’Select the name of the computer operating system using the pull-down menu.1…Ė/Ģ1©’’’’’’’’š/ĢoĢēĢ@žĖoĢ% €6€˜˜€‚’Network Operating SystemxN/ĢēĢ* $€œ€˜€€€‚’Select the name of the Network Operating system using the pull-down menu.1oĢĶ1Ü’’’’’’’’›ĶEĶšĶ-ēĢEĶ% €€˜˜€‚’Speed«€ĶšĶ+ $€€˜€€€‚’Select the computer processor speed using the pull-down menu. Refer to your computer guide to identify the processor speed.1EĶ!Ī1}’’’’’’’’œ!Ī\ĪØĪ;šĶ\Ī% €,€˜˜€‚’Problem DescriptionL(!ĪØĪ$ €P€˜€‚’Enter the description of the problem.1\ĪŁĪ1™’’’’’’’’ŁĪĻyĻ8ØĪĻ% €&€˜˜€‚’3Com Case NumberhDŁĪyĻ$ €ˆ€˜€‚’Enter the 3Com case number, if assigned by 3Com Customer Support.1ĻŖĻ1š’’’’’’’’žŖĻßĻT5yĻßĻ% € €˜˜€‚’Reproducible?i?ŖĻT* $€~€˜€ßĻTyĻ€€‚’Select the reproducible options, using the pull-down menu.1ßĻ…1„’’’’’’’’Ÿ…¶*1 T¶% €€˜˜€‚’File NametP…*$ € €˜€‚’The default name is 3report.txt. You can enter a new filename for the report.1¶[1ž’’’’’’’’ [Žū3*Ž% €€˜˜€‚’View ReportmG[ū& €Ž€˜€‚‚‚’Press the View report button to view the completed Problem Report.1Ž’’’’1’’’’’’’’”’’’’’’’’’’’’Tms RmnSymbolHelvCourierTimes New RomanArialMS SerifMS Sans SerifTimesHelveticaSystemCourier NewNew YorkGenevaMarlettWingdings’’’      ŪŅś‘j Cp s ƒ @Źš;PŹš;ą`Źš;OpŹš;K€Źš;‚Źš;ŗ Źš;'°Źš;ĄŹš;ÄŠŹš;> ąŹš;€šŹš;r€Ėš; Ėš;f0Ėš;Ɓ@Ėš;ˆ‚PĖš;™‚`Ėš;Ģ‚pĖš;ƒ€Ėš;0ƒĖš;†ƒĖš;Š€ Ėš; †°Ėš;؆ĄĖš;-ˆŠĖš;ąĖš;ršĖš;K Ģš;10Ģš;z@Ģš;®PĢš;į`Ģš;€pĢš;Z€Ģš;„Ģš;†Ģš;° Ģš;ˆ°Ģš;·‰ĄĢš;ŠŠĢš;XŠąĢš; šĢš;īĶš;p  Ķš;Ņ 0Ķš;( @Ķš;€PĶš;o€`Ķš;Š€pĶš;²€Ķš;Q‚Ķš;BƒĶš;"  Ķš;„°Ķš;3…ĄĶš;÷…ŠĶš;o†ąĶš;цšĶš;ˆĪš; Īš;z0Īš;6@Īš;‚PĪš;}`Īš;ČpĪš;€Īš;į Īš;] Īš;½ˆ Īš;’€ °Īš;- ĄĪš;Z ŠĪš;– ąĪš;с šĪš;‚ Ļš;œ‚ Ļš; ƒ 0Ļš;æƒ @Ļš;† PĻš;†† `Ļš;܆ pĻš;r‡ €Ļš;­‡ Ļš;ˆ Ļš;C‚  Ļš;€ °Ļš; ĄĻš;j ŠĻš; šĻš;įƒњ;÷‡ њ; 0њ;  Pњ; `њ;<‡ pњ;m… €Ńš;€ Ńš;Š њ;…  Ńš;ś ĄŃš;Ż ŠŃš;ųąŃš;‡‰Ņš;K‚ Ņš;v„0Ņš;–@Ņš;&`Ņš;OpŅš;’€Ņš;'Ņš;Ņš;‡€°Ņš;cŠĄŅš;ĉŠŅš;醹Ņš;ˆƒšŅš;!€Ӛ;µ Ӛ;0Ӛ;@Ӛ;C†PӚ;,„`Ӛ; pӚ; €Óš;©€Ӛ;°  Óš;?°Óš;fĄÓš;rąÓš;6šÓš;! Ōš;“ Ōš;ąPŌš;q `Ōš;€Ōš;Z‚Ōš;;°Ōš;c„ŠŌš;8†šŌš;‡ ՚;4 @՚;? `՚;(ˆp՚;€Õš;qƒÕš;Ą՚;®  Õš;‚‡°Õš;* ŠÕš;„ąÕš;+€šÕš;½֚;ļ ֚;Ž0֚;]֚;ż°Šš;“‰ĄŠš;| ŠŠš; ąŠš;H šŠš;8 rœ‚ 2ŠA€0zT€r‡ u† F·‰S’€ ؆Ɓ1r2Kˆ p‚ \цb‚]ˆ^½ˆU²`za6PŅ D†qC‚ 3XŠˆ‚`’€ Rį v†† @ QEˆa- Š€ÄAī3°B" Kkw܆ @į †bZ 0ƒc– ądс f‚' ŗ> r€1®n}€PČ[o†m1-ˆ‚ˆ tæƒ 0OƒBZl†ƒ™‚­‡ C„Q( TŠ€Z÷…Y3…_VQ‚X„WBƒR€So€Ģ‚/&;)Lz’’¢j’’GeneralŠANIC Details;u©³. €]€¼€ W”~‚SummaryŠ‚¾‚ō‚&ƒuƒPropertiesś…“†ˆConfiguration Parametersd?£Diagnosticsr§Ł€Lõƒś…ꇦ‰ŠNŠ–ŠEcho Test’ā c StatisticsĮ  €Y€»€ ?‚-ƒ„…ć…^†Ćķ‡®ˆD‰f&inSupport¶’ēRelease NotesG€Performance Hint for Fast EtherLink XL NICs on HP NetServers‚Compaq Prolinea 575 Computer NotificationS„3Com PCI NIC Installation HintsDiagnostics and configuration utilities run in DOS;Echo exchange test does not support crossover cable;Performance on Early Pentium Pro ModelsResource Conflicts Under Windows NT‚ Swap Slotsņ Swap Slot Numbers in the Registry…€Change the Load Order of DriversņƒRunning the DOS ODI Driver with a Non-Novell Protocol"†Windows 95 Installation NotesSpurious Hardware Interrupts on the Compaq Proliant 5000\Windows NT 4.0 Incompatibility with Miniport Drivers²Stopping the driver in a Windows NT SystemzPCI-System Manufacturers€Sharing Interrupts Under Windows 95wToshiba Tecra 720 CDT and Tecra 500 CS PCsRƒDell Dimension XPS Pro 200n³„OS/2 Warp 3.0O‡Warm Booting with the DOS based Drivers Runningi‰Frequently Asked QuestionsāDo I have to configure the NIC?šWhich PCI slot is best for my PCI NIC?ŠIs the NIC compliant with PCI Spec 2.1?Ž Which slots are bus mastering?€Which interrupt should I use?ZƒDoes my PCI NIC support shared interrupts?ʆWhat interrupts should I avoid?š‰Is my 3Com PCI NIC a 3.3 V or 5 V NIC?CŠMicrosoft EMM386.EXE problem؋Cannot execute programs loaded over the netśNetWare 3.11 server packet buffer problemŲACERPOWER ROM configuration problem+Are my drivers Novell-certified?’Incorrect configuration set by BIOS< How do I remove the 3Com icon from my system tray?Å8’’Ÿ Why does my NIC appear disabled in Windows 95 OSR 2?‚Why does the 3Com Diagnostics say my NIC is not connected?%„How can I tell which NICs are displayed in the PACE Window?ž…How do I know which Device ID applies to which XL NIC?O‡Can I use the 3Com XL NIC on the DEC Alpha PC?š‡How Can I Use a 3C509B-COMBO with a 3C905/3C900 NIC?5‹How Can I get a SCO Driver?€How do I remove the Fast EtherLink/EtherLink XL software?ŌWhy is dRMON bound to a non-3Com NIC?µWhy does my HP VA PC hang at POST during memory check?šHow do I update my EtherDisk 2.0 driver to EtherDisk 2.1 driver?Why does the Fast EtherLink/EtherLink XL NIC connect at half duplex?ɃKnowledgeBase Topics—‰Compaq 4704 (Pentium 133) Universal Serial Bus Overview_ Compaq DeskPro 2000 P5120ą Compaq Presario 8702 (Pentium 133)$ Dell Dimension XPS (Pentium 133)" Dell (Pentium 133)ņ„ Gateway 2000 (Pentium 133)ę‡ Gateway P5133 Gateway P590õ HP Vectra XU-6150¹ IBM Clones With Award BIOS 4.50gÉ Micron Milennia with Diamond Stealth 3D Video_ Tyan 16 Dual Pro with Matrox Video, PVR“ What is PIPELINE in the NET.CFG file for the 3C90X NIC?I… Diamond Stealth 64 PCI Video NIC-‡ Windows 95 Windows NT 3.51w 3Com NIC Diagnostics fail on the Zenith Data System’ Compaq Proliant 5000 detected as a PCI RAM device Toshiba Tecra 720 CDT and Tecra 500 CS PCsģ Two Fast EtherLink/EtherLink NICs in a NetWare 3.11 ServerŪ N £ š€  K † ø ō 3‚ ‘‚ ž‚ ©ƒ † k† Ō† \‡ š‡ ń‡ \ ± Does my PCI NIC support shared interrupts?ʆWhat interrupts should I avoid?š‰Is my 3Com PCI NIC a 3.3 V or 5 V NIC?CŠMicrosoft EMM386.EXE problem؋Cannot execute programs loaded over the netśNetWare 3.11 server packet buffer problemŲACERPOWER ROM configuration problem+Are my drivers Novell-certified?’Incorrect configuration set by BIOS< How do I remove the 3Com icon from my system tray?ōŸ /&;)L4’’ś(ś’’’’Ž÷€°L­T" ©XE†KŒ‡L‡bė+‹Ü† t%S‹įĻO †éM’Z ē'š’0ƒL ‡“– cšąIĮošŃ 臀§f¬I®a±„Æ‚mć„Æ'_É0³ ń)·møŗųˆÕø> rŒ»r€Ė8™¼®Y½} UūÉ€1PĢČ>ˆĒŠo†„S Ń1p7Ń-ˆ""DÓˆ Įą{Öæƒ ē7ŁŚ1&ōŚO©£Žƒ¾8ZįZ/….憃ŗ„ī™‚@Hņļ­‡ ’Twõ„I_šū( J_šūŠ€K_šū÷…L_šū3…M_šūN_šūQ‚O_šū„P_šūBƒQ_šū€R_šūo€įtÜūĢ‚JÓPj }žp ­| ƒ v|„”|„ąĢ|„O÷|„K"}„‚M}„ŗ„~„'Š~„ū~„Ä&„> Q„€|„r€.ƒ„Yƒ„f„ƒ„Ɓƃ„ˆ‚Śƒ„™‚„„Ģ‚0„„ƒ[„„0ƒ†„„†ƒ±„„Š€Ž…„ † †„؆4†„-ˆ_†„Š†„rµ†„K’Š„1½Š„z芄®‹„į>‹„€i‹„Z”‹„„æ‹„†ź‹„°„ˆB„·‰m„Š˜„XŠƍ„ ī„ī ‘„p Ė‘„Ņ ö‘„( !’„€L’„o€w’„Š€¢’„²Ķ’„Q‚ų’„Bƒ#“„" P”„„{”„3…¦”„÷…є„o†ü”„ц'•„ˆŁ˜„™„z/™„6Z™„‚…™„}°™„ČŪ™„š„į 1š„] \š„½ˆ‰›„’€ “›„- ߛ„Z œ„– 5œ„с `œ„‚  „œ‚ = „ ƒ h „æƒ “ „† ¾ „†† é „܆ ”„r‡ ?”„­‡ j”„ˆ •”„C‚ Ā¢„€ ķ¢„ £„j C£„ ™£„įƒų>¦÷‡ #?¦ N?¦  ¤?¦ Ļ?¦<‡ ś?¦m… %@¦€ P@¦Š {@¦… ØA¦ś žA¦Ż )B¦ųTB¦‡‰1F¦K‚\F¦v„‡F¦–²F¦&G¦O3G¦’^G¦'‰G¦“G¦‡€ I¦cŠ7I¦ĉbI¦é†I¦ˆƒøI¦!€jM¦µ•M¦ĄM¦ėM¦C†N¦,„AN¦ lN¦ —N¦©€ķN¦° P¦?EP¦fpP¦rĘP¦6ńP¦! £T¦“ĪT¦ąOU¦q zU¦€ūU¦Z‚&V¦;~W¦c„ŌW¦8†*X¦‡\¦4 ]\¦? ³\¦(ˆŽ\¦ ]¦qƒ4]¦Ą_]¦® Œ^¦‚‡·^¦* _¦„8_¦+€c_¦½c¦ļ@c¦Žkc¦]˜d¦żŌ‚¦“‰’‚¦| *ƒ¦ Uƒ¦H €ƒ¦8 8y œ‚ Ć¢ÅŠMčo€õ""z‘!¤%½0t+r‡ Į ,† 1TX,·‰Ažź1’€ „<Ł2؆W‘Ž2Ɓ*iō4rb÷’8KA; ēćē@‚ DīBцEīB‚FīBˆGīB½ˆHīB²IīBzJīB6MīBŅ @3ųE†rMC‚ īˆąVXŠĶė±]ˆ‚­„b’€ źécfį ÅBdf†† „āk  zĒlJŻ>xˆ2y- =ØK{Š€±Z{Ä kb{ī0ų/lp0„„Ø_’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€Ę€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€@` @` @` @` €€€€€€€€€€€€€€€€€€€€€Ę€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€@ @ @ @ @ @ @ @ €€€€€€€€€€€€€€€€€Ę€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€@` @ @ @ @ @ @ @ @ @ @ @ €€€€€€€€€€€€€Ę€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€@` @` @ @ @ @ @ @ @ @ @ @ @ @ @ @ €€€€€€€€€Ę€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ €€€€€Ę€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ €Ę€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€@` @` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @Ę @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @Ę @ @ @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @Ę @ @ @ @ @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€@` @` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @Ę @ @ @ @ @ @ @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @``@ @ @ @ @ @ @ @ @ @Ę @ @ @ @ @ @ @ @ @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€ą€€€€€€€€€€€€€€€€€€€€€€@` @` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @``€ƒ’ĄĄ€Ü@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€ģ€€€€€€€€€€€€€€€€€€€€@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ€Ö@` @ @ @ @ @ @ @ @ @ @ @ @ @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€ņ€€€€€€€€€€€€€€€€€€@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @``@``@``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€Š@``@ @ @ @ @ @ @ @ @ @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€Ż€€€€€€€€€€€€€€@` @` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @``@``@``@``@``€å’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ@``@ @ @ @ @ @ @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€Ż€€€€€€€€€€€€@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @``@``@``@``@``@``@``€”’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€Į@ @ @ @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€Ż€€€€€€€€€€@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @``@``@``@``@``@``@``@``€§’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€»@` @ €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€@` @` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @``@``@``@``@``@``@``@``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ŽĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€µ@` €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€@` @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @``@``@``@``@``@``@``@``@``@``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĘĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€Ś€€€€@ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @``@``@``@``@``@``@``@``@``@``@``@``€č’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€€€€€€€€€€€€€€€€€€€Ś€€€€€€@ @ @ @ @ @ @ @ @ @ @ @ @ @``@``@``@``@``@``@``@``@``@``@``@``@``@``€Å’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€ž€€€€€€€€€€€€€€€€€€€€Ś€€€€@` @` @ @ @ @ @ @ @ @ @ @ @ @``@``@``@``@``@``@``@``@``@``@``@``@``@``@``€č’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€``€€€€€€€€€€€€€€€€Ė€€€€€€€€@` @` @` @` @ @ @ @ @ @ @ @``@``@``@``@``@``@``@``@`` — @``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ€†’ĄĄ’ĄĄ€Š’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€€€€€ŀ€€€€€€€€€€€€€€€@` @` @` @` @ @ @``@``@``@``@``@``@``@``— @``@``@``@``’ĄĄ’ĄĄ’ĄĄ€‰@@€ €†@€ €Ē’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€Ā€€€€€€€€€€€€€€€€€€€€€€€€@` @` @``@``@``@``@``@``@`` Ž @``@``@``@``€’ĄĄ’ĄĄ’ĄĄ’ĄĄ€``€Ų @€``@@@@ €``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€``€€€€¼€€€€€€€€€€€€€€€€€€€€€€€€€€€€@``@``@``@``@`` ” @``@``@``@``€Œ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€ˆ``@@ €Ķ’ĄĄ€``@ @@€``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€¶€€€€€€€€€€€€€€€€€€€€€€€€€€€€@``@``@`` š @`` @``@``@``@``€Œ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€ˆ @€ €†’ĄĄ€``€@@@@€ €²’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€³€€€€€€€€€€€€€€€€€€€€€€€€€€€€@``@``@``ø @`` @`` @``@``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ@€ ’ĄĄ@€ƒ’ĄĄ€†@@€…``€``€ŗ``@@@ €``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€Ȁ€€€€€€€€€€€€€€€€€€€€€€€€€@` @``@`` @`` @`` ˜@``@``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ€”@@ @€ ’ĄĄ€``@@@€``’ĄĄ€‚``€Ŗ@@ @@€``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€†€€€€­€€€€€€€€€€€€€€€€€€€€€€€€€€@``@``‚ †@`` ‰@``@``@``€’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€¦``€ € ’ĄĄ€``@@@€ ’ĄĄ€ @ ’ĄĄ€’’ĄĄ@ @ @@€ €’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€³€€€€€€€€€€€€€€€€€€€€€€€€€€@`` ‚ ‹ @``@``@``€­’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€ €``’ĄĄ€ €``€``@€ˆ``€ ’ĄĄ€²’ĄĄ@€``€``@@€``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€³€€€€€€€€€€€€€€€€€€€€€€€€€€@``@`` @``‚ ¾ @``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ@@€``’ĄĄ’ĄĄ’ĄĄ@€ €ƒ@€ƒ@€’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€``€€€€€€­€€€€€€€€€€€€€€€€€€€€€€€€€€@``@``†@`` Č@``@``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ@@@@€ @@@@@ @€Æ@ ’ĄĄ€``€ ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€Ŗ€€€€€€€€€€€€€€€€€€€€€€€€@``@``‚ ‰@``@``@``€˜’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€§@@@@@@@@@@@@@ €¬’ĄĄ€``€``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€°€€€€€€€€€€€€€€€€€€€€€€€€@``@`` ‹ @``@``@``€˜’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€Č@@@@@@@@@@@@@@€ €``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€‰€€€€€€°€€€€€€€€€€€€€€€€€€€€€€€€@``@``@`` ‹ @``@``@``€ć’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€ @@@@@@@@@@@@@@@@€ €``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€‰€€€€€€­€€€€€€€€€€€€€€€€€€€€€€€€@``@``@``’ @``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ@ @@@@@@@@@@@@@@@@@€``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€­€€€€€€€€€€€€€€€€€€€€€€@``@``@``@``Ż@``@``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ@@@@@@@@@@@@@@@@@@€ ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€­€€€€€€€€€€€€€€€€€€€€€€@``@``@`` ‰@``@``@``€˜’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€¶@@@@@@@@@@@@@@@@@@€ ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€€€­€€€€€€€€€€€€€€€€€€€€€€@``@``@`` ‹ @``@``@``€˜’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€Ł@@@@@@@@@@@@@@@@@@’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€€€Ŗ€€€€€€€€€€€€€€€€€€€€€€@``@``@``Ž @``@``@``@``€ō’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€ @@@@@@@@@@@@@@@@@@ ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€€€Ŗ€€€€€€€€€€€€€€€€€€€€@` @``@``@``ś @``@``@``@``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€``@@@@@@@@@@@@@@@@@€ ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€Œ€€€€€€€€Ŗ€€€€€€€€€€€€€€€€€€€€@``@``@`` ¼@``@``@``@``@``@``@``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€Ā@ @@@@@@@@@@@@@@€``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€Œ€€€€€€€€Ė€€€€€€€€€€€€€€€€€€€€@``@``@`` @``@``@``@``@``@``@``@``@``@``€§’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€¦``@@@@@@@@@@@@€£’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€€€Ė€€€€€€€€€€€€€€€€€€€€@``@``@``@``@``@``@``@``@``@``@``@``@``@``@``€°’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€ @@@@@@@@@€£’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€``€€€€€€€€€€Ė€€€€€€€€€€€€€€€€€€€€@``@``@``@``@``@``@``@``@``@``@``@``@``@``@``€¶’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€½``@ @@@@@@’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€@``@``@``@``@``@``@``@``@``@``@``@``@``@``@``@``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ŽĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€“``@@@@’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€€€€€ŀ€€€€€€€€€€€€€€€€€@``@``@``@``@``@``@``@``@``@``@``@``@``@``€ƒ’ĄĄ’ĒĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€˜@ € ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€€€€¼€€€€€€€€€€€€€€€€€€@``@``@``@``@``@``@``@``@``@``@``€ƒ’ĄĄ’ŁĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€€€€¶€€€€€€€€€€€€€€€€€€@``@``@``@``@``@``@``@``@``€%’ēĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€€€€€­€€€€€€€€€€€€€€€€@``@``@``@``@``@``@``€ƒ’ĄĄ’‚ĄĄ"’ŽĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€€€€€¤€€€€€€€€€€€€€€€€@``@``@``@``€ƒ’ĄĄ’‘ĄĄ’€€@’``’€€’``"’ÕĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€€€€€€€ž€€€€€€€€€€€€€€€€@``@``€"’ƒ€€’€”’€€’``’€€’``’``’€€’ĢĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€€€€€€€›€€€€€€€€€€€€€€€€’ĄĄ'’¤@’€€’ ’ @’€€’ ’``’ĄĄ’€€’``’ĄĄ’ĘĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€€€€€€€€€€€€€”€€€€€€€€€€€€€€€€€€€€`’Ą€’²€€’ €€€€€’``’``’€€’ ’``’ĄĄ’€€’``’``’ĄĄ’¦ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€’€€€€€€€€€€€€Ŗ€€€€€€€€€€€€€€€€€€€€€€€€€€`’Ą€’»€€’ €€€€€€€€€€’``’€€’``’ĄĄ’ĄĄ’ ’``’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€’€€€€€€€€€€€€³€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€`’Ą€’¦€€’ €€€€€€€€€€’``’‹ĄĄ’’’``’«ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€€€€€€€¼€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€`’Ą€’©€€’ €€€€€€€€€’ ’``’€€’€ˆ’``’€€’„ĄĄ’ĄĄ’ĄĄ’ĄĄ’ĄĄ€€`€€€€€€€€€€€€€€ŀ€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€`’Ą€’¦€€’ €€€€€€€€€’ ’``+’œĄĄ’ĄĄ€€€€€€€€€€€€€€€€Ī€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€`’Ą€’š€€’ €€€€’ ’``’ĄĄ+’ƒĄĄ’€˜`€€€€€€€€€€€€€€€€׀€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€`’Ą€’ˆĄĄ’€€’ĄĄ(’®ĄĄ’Ą€’€`€€€€€€€€€€€€€€€€€€€€€€€€€€ą€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€`’Ą€+’ƒĄĄ’€³`€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€退€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€`’Ą€’ÉĄĄ’Ą€’€`€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€󀀀€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€`’Ą€’€Ī`€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€’€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€Ę€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€lcc`°ŒglossaryGlossary of termsĄĄĄ’’’¼!³!5<Žp’’’’’’’Table of contents’’’’˜Yv|„Generalmain„”|„NIC Selectionpopup°ØĢ|„NIC DetailsÓ÷|„Device Numberpopupū"}„Bus Numberpopup'M}„I/O Port RangepopupN„~„IRQ LevelpopupvŠ~„Media Typepopup¢ū~„Boot PROM SizepopupĶ&„ Network SpeedpopupüQ„ Receive FIFO Sizepopup,|„ Transmit FIFO Sizepopup[±„„ Product Date Codepopup†.ƒ„ Division CodepopupYƒ„Product CodepopupŁ„ƒ„Enable Traypopupsłƃ„Summary#Śƒ„Node AddresspopupL„„I/O Addresspopup0„„Device IDpopup[„„Warningpopup’憄„PropertiesmainķŽ…„Optimal Settingspopup †„PACE ConfigurationpopupN4†„Configuration Parameters‡_†„Network Driver Optimizationpopup°Š†„Full Duplexpopup×µ†„Boot PROMpopupź‹„Media Typepopup '’Š„DiagnosticsmainJ½Š„Startpopupl芄Stoppopup±‹„ TestspopupĮ>‹„!Register Access Testpopupźi‹„"EEPROM Testpopup”‹„#FIFO TestpopupJæ‹„$Ethernet Core Loopback Testpopup…„%Encoder/Decoder Loopback TestpopupB„&Interrupt TestpopupÓC£„)Echo Testõm„'Sendpopup˜„(RespondpopupBƍ„*Start Echopopupiī„+Stop Echopopup‘#“„,Continuouspopup“ ‘„-StatisticsąĖ‘„.Bytes Receivedpopupö‘„/Bytes Transmittedpopup=!’„0Packets ReceivedpopupnL’„1Packets Transmittedpopupžw’„2Transmit DeferralspopupĖ¢’„3Receive OverrunpopupųĶ’„4Late Collisionspopup( ų’„5Carrier Sense LostpopupP P”„6SQE Errorspopup {”„7Multiple Collisionspopup° ¦”„8Single CollisionspopupÜ Ń”„9Bad SSD Errorspopup ü”„:CRC Errorspopup2 '•„;Oversize Packetspopup\ \š„<Runt PacketspopupŽ Ł˜„=Excessive Collisionspopup½ ™„>Transmit Underrunpopupč /™„?Jabber ErrorspopupZ™„@Frame Alignment ErrorspopupÄ@ …™„ASupportmainm °™„BRun Diagnosticspopup:˜ Ū™„CRelease NotespopupŃĀ )B¦DRelease Notesmain “G¦EPerformance Hint for Fast EtherLink XL NICs on HP NetServersmaina 1F¦FCompaq Prolinea 575 Computer Notificationmain \F¦G3Com PCI NIC Installation Hintsmain× ėM¦PWindows 95 Installation Notesmain EP¦JPerformance on Early Pentium Pro Modelsmaink pP¦IEcho exchange test does not support crossover cablemainŗ ĘP¦HDiagnostics and configuration utilities run in DOSmain N¦ORunning the DOS ODI Driver with a Non-Novell Protocol main^&V¦QSpurious Hardware Interrupts on the Compaq Proliant 5000«£T¦RWindows NT 4.0 Incompatibility with Miniport DriversļĪT¦SStopping the driver in a Windows NT System/P¦KResource Conflicts Under Windows NTmainVAN¦LSwap Slotsmain”lN¦MSwap Slot Numbers in the Registrymain—N¦NChange the Load Order of DriversmainŠTB¦ZFrequently Asked QuestionsmainH²F¦hIncorrect configuration set by BIOSmain…G¦gAre my drivers Novell-certified?mainÅ3G¦fACERPOWER ROM configuration problemmain ^G¦eNetWare 3.11 server packet buffer problemmainS‰G¦dCannot execute programs loaded over the netmainŒ I¦cMicrosoft EMM386.EXE problemmainĻ7I¦bIs my 3Com PCI NIC a 3.3 V or 5 V NIC?main bI¦aWhat interrupts should I avoid?mainRI¦`Does my PCI NIC support shared interrupts?mainŒøI¦_Which interrupt should I use?mainĒķN¦^Which slots are bus mastering?main jM¦]Is the NIC compliant with PCI Spec 2.1?mainN•M¦\Which PCI slot is best for my PCI NIC?mainĄM¦[Do I have to configure the NIC?main»™£„vKnowledgeBase TopicsmainńŌ‚¦wCompaq 4704 (Pentium 133)main'’‚¦yCompaq DeskPro 2000 P5120mainf*ƒ¦zCompaq Presario 8702 (Pentium 133)main£Uƒ¦{Dell Dimension XPS (Pentium 133)mainŅ€ƒ¦|Dell (Pentium 133)main {@¦}Gateway 2000 (Pentium 133)main3ų>¦~Gateway P5133main\#?¦Gateway P590mainŠN?¦€HP Vectra XU-6150main¶¤?¦‡Windows NT 3.51mainŽĻ?¦†Windows 95 mainś?¦…Diamond Stealth 64 PCI Video NICmaino%@¦„What is PIPELINE in the NET.CFG file for the 3C90X NIC?main³P@¦ƒTyan 16 Dual Pro with Matrox Video, PVRmainżØA¦‚Micron Milennia with Diamond Stealth 3D VideomainžA¦IBM Clones With Award BIOS 4.50gmain[š„ŒBBSpopup…1š„Tech Supportpopupt±Ā¢„ŽProblem ReportpopupŪ‰›„Company Namepopup “›„Customer Addresspopup3ߛ„‘Contact Namepopup^ œ„’Contact Phonepopup’5œ„“Contact E-Mail Addresspopupŗ`œ„”Model Typepopupå•”„•Machine Usagepopup  „–CPU Typepopup2= „—PCI Slotspopupch „˜Bus-Mastering Slotspopup‘“ „™Operating SystempopupĒ¾ „šNetwork Operating Systempopupźé „›Speedpopup”„œProblem DescriptionpopupI?”„3Com Case Numberpopupj”„žReproducible?popup›ķ¢„ŸFile Namepopup£„ View ReportpopupžńP¦xUniversal Serial Bus Overviewmain3‡F¦TPCI-System Manufacturersmain~OU¦iHow do I remove the 3Com icon from my system tray?ĖzU¦jWhy does my NIC appear disabled in Windows 95 OSR 2?ūU¦kWhy does the 3Com Diagnostics say my NIC is not connected?r~W¦lHow can I tell which NICs are displayed in the PACE Window?ÅŌW¦mHow do I know which Device ID applies to which XL NIC?main*X¦nCan I use the 3Com XL NIC on the DEC Alpha PC?main`_]¦ˆ3Com NIC Diagnostics fail on the Zenith Data Systemmain®\¦‰Compaq Proliant 5000 detected as a PCI RAM devicemainõ]\¦ŠToshiba Tecra 720 CDT and Tecra 500 CS PCsmainF³\¦oHow Can I Use a 3C509B-COMBO with a 3C905/3C900 NIC?main~Ž\¦pHow Can I get a SCO Driver?main¶ ]¦WDell Dimension XPS Pro 200nmainą4]¦XOS/2 Warp 3.0main,Œ^¦YWarm Booting with the DOS based Drivers Runningmainƒ·^¦‹Two Fast EtherLink/EtherLink NICs in a NetWare 3.11 ServermainŹ _¦VToshiba Tecra 720 CDT and Tecra 500 CS PCsmain 8_¦USharing Interrupts Under Windows 95main` c_¦qHow do I remove the Fast EtherLink/EtherLink XL software?main¢ ˜d¦rWhy is dRMON bound to a non-3Com NIC?mainõ c¦sWhy does my HP VA PC hang at POST during memory check?mainR!@c¦tHow do I update my EtherDisk 2.0 driver to EtherDisk 2.1 driver?mainkc¦uWhy does the Fast EtherLink/EtherLink XL NIC connect at half duplex?mainSuJu enuŽa~ßÓ°…óÄšsa Ł#d&Ø()-V-^1,7=:ü;ą<š> ?Y?'-anandasatbebutbycancan'tdodon'tforfromhaveheinitnotofonorsaidsayshethatthetheirthemtheretheythistowewhichwillwithwon'tyouabilityŠ?ableŽ?abnormalš?aboutž?abstractionŖ?access®?accompanyingĀ?accomplishedĘ?accordingŹ?acerĪ?acerpowerÖ?acknowledgesŽ?activateā?activeę?activityī?actuallyņ?adaptecö?adapterś?adapters @add@adding*@addition.@additional6@address:@addressesB@advanceN@advancedR@advantage^@afterb@agent~@ahead‚@all†@allocate¦@allows®@alpha¶@alphabeticallyŗ@alr¾@alreadyĀ@alsoŹ@altŽ@althoughę@alwaysź@amņ@ambraö@americasś@anotherž@anyAappear:Aappears>AappletNAappliesRAapplyZAapproximately^AarchitecturebAarefAareaĀAaroundĘAasicŹAaskĪAaskedŅAasksŚAassignęAassignedśAassignsBassistanceBassumes BastBasusBasustekBatiBattached"Battempt&Battempting:Battempts>BaudioBBauthoredFBautoJBautomaticallyRBavailablefBavoid†Bavoided¢Baward¦Baxy²Bback¶Bbandwidth¾BbaseĀBbasedĘBbatŅBbbsÖBbeatāBbeatsęBbecauseźBbeenžBbeforeCbeginningCbeing"Cbell2Cbelow6Cbest:CbetweenJCbindZCbindingsfCbiosjCbitĪCblueŅCblueprintsŚCboardŽCboardsęCbootīCbootingDbootsDbothDbound&Dbox.Dbrowse>DbrowsingBDbufferFDbuffers^DbusbDbusesšDbuttonžDcableŖDcache²Dcame¶DcancelŗDcanceledĀDcannotĘDcapabilityęDcapableīDcardņDcardsEcaseEcasesEcauseEcaused6Ecauses:EcdBEcdtFEcertifiedREcfgZEchainedvEchangezEchangesŽEchanging–EcheckžEchecks²EchipŗEchipsetĘEchooseŹEchoosesŅEcircumstancesÖEclassŚEclearlyŽEclickāEclickingśEclientžEclientsFclockFclonesFclosest&Fcmos*Fcode2Fcom:FcombinationBFcomboNFcomesZFcommentedbFcommonfFcommunicationjFcompaniesnFcompanyrFcompaq vFcompatibilityšFcompatible¢Fcompleted¦FcompletelyŖFcompliant®Fcomply¶Fcomponents¾FcomputerĀFcomputer'sGcomputersGconditionsGconfig"Gconfiguration&Gconfigurations~Gconfigure‚Gconfigured’Gconfiguring¢GconflictŖGconflictingĘGconflictsĪGconnectÖGconnectedīGconnectionHconnectorHconstant HconsultHcontactHcontain:Hcontained>HcontainingBHcontainsFHcontinueNHcontinuousRHcontrolVHcontrollerjHcopyrightsrHcorevHcorrectzHcorrectly†HcorrespondingžHcorresponds¢Hcost¦HcostsŖHcould®HcpoindexŗHcposupport¾HcpuĀHcreateĘHcrossoverŹHcsŅHctrlŽHcurrentęHcurrentcontrolsetņHcurrentlyśHcustomerIcustomizeIcustomizing IdataIdate.Idated6Idec>IdecoderFIdefaultJIdefaultgateway0VIdefinedZIdefines^IdelbIdellfIdependonservice~Idescription‚IdeselectingŽIdesign’Idesignated–IdesignedšIdesignsžIdeskpro¢Ideskstation®Idesktop¶IdetailedŗIdetailsĘIdetectĪIdetectedāIdetectsīIdetermineśIdevelopJdeveloped JdevelopmentJdeviceJdevices VJdiagnosticzJdiagnosticsŽJdialogĪJdiamondŅJdidŽJdifferenceāJdifferentęJdifferentlyöJdigitalžJdimensionKdirectlyKdirectoryKdisable&Kdisabled:KdisclaimsFKdiskJKdisketteRKdisplayednKdisplayszKdistinguishŠKdivisionŽKdll’Kdnsserveraddr–KdockingšKdocumentation¢Kdoes²KdomainLdosLdouble>LdownBLdownloadFLdramNLdriveRLdriverZLdriver'sĀLdrivernameĘLdrivers ŹLdrivesžLdrmonMdroppedMdualMdumpMduplexMduring*Mdx2BMdynamicallyFMeachJMearlierVMearlybMechonMedgevMeditzMeditingŽMeditor’MeepromšMeisažMeither®Mel59x¶Mel90xŗMel90x1ĘMel90x2ŹMel90xio2_nifĪMel9xŅMelectricallyÖMeliminateŚMeliminatesŽMemergingźMemm386īMemm386upśMemulatoržMenableNenabledNenabling NencoderNenoughNenterNenters*Nentrant.Nentries6Nentry>NenvironmentFNequipmentRNequippedVNequivalent^NerrorbNespecially~Nessential‚Nestablish†NetherdiskŠNetherlink ŖNethernet*OevenBOexactVOexampleZOexceptrOexchangezOexe‚OexecutešOexit¦OexitsŖOextra®Of1²Of10¶Of2ŗOfact¾OfailĀOfailedŅOfailureŚOfamilyŽOfastęOfasterVPfeatureZPfifojPfile rPfiles¦PfindŗPfindsÖPfineŚPfinishāPfinishedęPfirstźPfitöPfitnessśPfixžPfixedQfollow QfollowingQfollowsRQforceZQforcesbQformalfQfoundjQfour~Qframe†QfrequentlyŠQftpŽQfull’Qfully¢Qfunction¦QfurtherŖQgame®Qgateway²Qgateway2000ĘQgeneralŹQgenerallyĪQgeneratesŅQgenericŽQget āQgettingRgfx RggRgiveRgivenRgoRgranted2Rguide6RgxFRhadJRhalfNRhandVRhangZRhangsbRhappennRhardrRhardwarevRhasŠRhavingĘRhelpĪRhereŚRhewlettęRhighlightźRhimemīRhintņRhintsśRhkey_local_machineShook ShostShostspathShowShowever>ShpJShppcjShtdocsnShtmrShtmlvShttpzShub‚SibmŠSicon–SidžSideŖSidentified®Sids¶Sif#ŗSiiiFTimmediatelyNTimplementationRTimplementationsZTimplemented^TimplementsbTimproperlyfTincludejTincludedvTincludeszTincluding~Tincompatibility‚Tincorrect†Tincorrectly’TincreasingšTindicatežTindicates¢TindicationŖTindividual®Tindustry²TinfŗTinformation ¾TiniāTinitializationęTinitializedźTinitializesīTinputņTinsertöTinsertingUinstall Uinstallation:UinstalledJUinstalling‚UinstallsžUinstance¢Uinstances¦UinsteadŖUinstructions®UintaĀUintegratedĘUintegratingŹUintelĪUintel'sŚUinterfaceŽUinterruptęUinterruptsVinto"Vinvolved>VipBVipaddress0FVipxJVipxodiRVirq VVirqszVis-~Visa2WissueBWissuesNWitsZWitselffWjoystickjWjoysticksnWjumperrWkeepvWkeyzWkeyboard†WkeyboardsŠWkeysŽWkeyword–WkindšWknowžWknowledgebase®Wknown¶Wlan¾WlanddŹWlapsĪWlargeŅWlatencyāWlaterźWlatestžWlayerXlcXleading"Xlength&Xlets*Xlevel.Xlevels>XlfBXlibraryFXlicensingJXlikeNXlineVXlinkfXlist~XlistedŠXlive’Xload–Xloaded¦XloadingŗXloads¾XlocalĪXlocateŅXlogŚXlogicallyāXloginęXlookīXloopbackņXloseöXlosesśXlossžXlow YlowerYlslYlt00042Ym55hiYmac"Ymach&Ymachine*YmachinesFYmadeJYmailNYmainRYmainframeZYmake^Ymanager~YmanualšYmanually®Ymanufacturer¶YmanufacturersŅYmarkāYmarkedęYmassīYmasterņYmasteringZmatchZmatrixZmatrox"Zmaximized.Zmay2ZmbnZmbpsrZmeansvZmediazZmeet†ZmegabitsŠZmeiŽZmemory’ZmentionedžZmenu¢Zmenus¦ZmerchantabilityŖZmessage®ZmhzŹZmiceŚZmicronŽZmicronicsīZmicrosoftņZmicrosoft's [mid[might[milennia[millennia[mind&[minimum*[miniport2[mistakes6[mode:[modelsF[moduleV[monitor^[more b[most†[mostly’[motherboard–[mouse¦[moveŖ[ms®[msupdate²[much¶[multipleŗ[mustĘ[myÖ[name\named&\native*\ncr.\ndis2\needB\neededR\needsZ\neither^\net b\netapi†\netbeuiŠ\netserverŽ\netserver's’\netservers–\netware ž\networkŅ\networks]new"]newer.]next6]nic;B]nic's.^nics>^no†^no_pipeline’^node¢^nodenameŖ^noems®^non²^nonsharedĀ^norĘ^normallyĪ^nosŅ^noteŚ^notedź^notesī^noticeś^noticedž^notification_notwithstanding_novell _novell's>_nowB_nsV_nt Z_number‚_numbers–_numtcpbuffersŖ_nwclient®_observed²_obtaining¾_occasionallyĀ_occurĘ_occurredĪ_occursŚ_octö_odiś_odinsup`odipkt`oem`oemsetup`off"`ok2`older6`once:`one B`onlyn`onto¦`openŖ`opensĀ`openserverŹ`operateĪ`operatesÖ`operatingŚ`opportunityņ`optimalö`optimizationś`optionž`orderaorg"aorganization&aorganized*aos.aosr2>aother Baoutjaoutlinedraovervaoverlapping†aoverviewŠaown’aowner'sšaowners¦ap133Ŗap5®ap5120ŗap5133Āap590Źap90ŅapaceÖapackardŽapackardbellāapacketęapacketsöapanelśaparallelbparameterbparametersbparticular&bparty.bpass6bpath:bpb>bpcFbpc'sŽbpcco’bpcdesc–bpcdnshostnamešbpci%žbpcs2cpeerBcpentium Jcperrcperceptionvcperformzcperformance~cperformsŽcperipherals’cpertaining–cphoenixšcphone¢cphysical®cpipeline²cplatformĀcplayĘcpleaseŅcplugācpnpöcpointścpopulardportdportsdpossibledpostdpr00025"dpremmia&dpresario*dpresence2dpresent6dpress:dpressingBdpreviousNdprimaryRdprintedVdprintersZdpro^dproblemrdproblemsŗdproceduresŹdproductŅdproductsŚdprogram ādprograms eprolianteprolineaeprom"eproperly*eproperties>epropertyJeprotocolNeprotocolsbeprovidefeprovidedreprovideszepub~epull‚epurpose†eputŠepvr’equestionšequestionsžequickly¢eram¦erange®erather²ere¶ereadĀereadyŹerealityĪereallocatesŅerebootÖerebootedņerebootsöereceiveśerecent frecognizefrecognizedfrecognizes"frecommendations*frecommended.frecommends2frecord6frecorded:frecorder>freduceBfreferFfreflectionZfrefresh^fregedt32bfregisterffregistryrfregular‚freinitialize†freinstallŽfrel’frelatively–freleasešfreleases¦freloadedŖfremaining®fremove²freplacedĪfreplacesŅfreplacingÖfreportŚfrequestŽfrequesterāfrequireęfrequiredīfrequirementsöfrequiresśfresetžfresolvegresolvesgresourcegresources"grespective.gresponding2grest6grestart:grestartingBgresultsFgreturnJgreviewNgrevisionRgrightZgrobust^grombgrootvgroutinezgrouting~grun ‚grunning®grunsźgsame ņgsavehsaying2hsco6hscratch>hscreen Bhscreensjhscriptnhscrollrhscsivhsearching~hsecond‚hsecondaryŽhsection’hseežhseems¶hselect¾hselectedÖhselectingŽhselectionāhselfęhsendņhsensesöhserialśhseriesiserveriservers&iservice.iservices2iset >isetsjisettingrisettings‚isetupŽiseveral¦ishared®isharing¾isheetĘishippedŹishipsŅishould Śishowjshownjsignaljsince"jsingle2jsite6jsituationFjsizeVjslave^jslotjjslotnumber¦jslots ŖjslowlyŅjsmartagentÖjsnoopŽjsoājsoftware ņjsolutionksolutions*ksolve2ksome6ksometimesNkspecVkspecifically^kspecificationbkspeednkspuriousvkspxzkstability~kstack‚kstandard†kstandards’kstart–kstartedškstartingžkstarts¢kstate¦kstatementŖkstatements²kstation¶kstay¾kstealthĀkstepsĪkstillÖkstoppingźkstopsīkstorageņkstringöksubheadingśksubjectedžksubkeylsubnetmask0lsuccessfully lsuchlsummarylsupportlsupportedVlsupporting^lsupportsblsurerlswapŽlswappingšlswitch¢lsymptoms¦lsysŖlsystem²lsystem's&msystem322msystems6mt4FmtabRmtabs^mtakebmtaskingjmtcprmtcp2pdisvmtcpbuffersizezmtcpip~mtcpsessions‚mtechbbs†mtechnicalŠmtecra’mtelephonežmtelephony¢mtell¦mtestŖmtested¶mtesting¾mtestsĪmthanŅmthenŽmthese źmthirdnthosenthoughnthought"nthree&nthrough*nthroughput:ntime>ntimerRntogetherZntop^ntopicbntopicsfntoshibajntpovntrademarks~ntransfer‚ntransfers†ntransmitŽntray–ntreešntried¦ntriggerŖntriggered®ntriton¶ntroubleŗntroubleshooting¾ntrueĀntryĘnturnānturnedīnturningņntwöntwo śntx&otxtbotyanfotypenoultimately~ounavailable‚ounder †ounfortunatelyŖouninstal®ouninstall²ouninstallerŗouninstalling¾ouniqueĀounisysĘouniversalŹounknownŅounlessÖounstableŚounsuccessfulŽounsureāountilęoupźoupdatepupdatedpupdating*pupgrade.purl6pusb:puse FpusedrpuserŠpuses¢pusing¦pusuallyņputilitiesöputilityqv2qva"qvalue*qvalues2qvariety:qvary>qvectraBqvendorJqvendorsNqverifiesRqverifyVqverifyingZqversion ^qversions†qvga’qvideo–qview®qvirtual²qwant¶qwarm¾qwarpŹqwarrantŅqwarrantiesÖqwarrantyŚqwasŽqwayņqweböqwellrwererwfwrwhatrwhatever.rwhen2rwhere¢rwhether¦rwhile¶rwhy¾rwideŽrwindowźrwindowsörwinntfswinnt35jswirenswishrswithinvswithout‚swork Žsworkaroundŗsworkgroups¾sworkingŅsworksŚsworkstationāsworkstationsźsworldīsworryöswouldśswritetwrqnet twrstwwwtx86txl""txpsŖtxuŗtxxxĀtyearĘtyesŹtyetŅtyourŚtyourself.uzds2uzenith6uzeosBuzeosbbsFupP¦4]¦€ƒ¦ų>¦EP¦v|„8_¦øI¦P¦’Š„“G¦N¦€ƒ¦_]¦™£„ńP¦˜d¦‡F¦3G¦TB¦3G¦@c¦lN¦c¦%@¦Œ^¦˜d¦#?¦³\¦Ž\¦@c¦ØA¦@c¦Ļ?¦—N¦N¦øI¦@c¦€ƒ¦{@¦P¦‡F¦bI¦\F¦v|„ĄM¦P¦AN¦‡F¦ńP¦“G¦\F¦ØA¦%@¦\F¦N¦ĄM¦c_¦˜d¦c¦Ļ?¦˜d¦“G¦I¦bI¦²F¦@c¦™£„{@¦ų>¦ØA¦%@¦_]¦†„„%@¦*X¦™£„‡F¦ėM¦øI¦…™„ķN¦bI¦ńP¦\¦\F¦Œ^¦\¦…™„ķN¦_]¦‡F¦‡F¦AN¦ėM¦I¦²F¦ńP¦ØA¦_]¦Œ^¦•M¦øI¦bI¦˜d¦™£„’‚¦ų>¦TB¦²F¦@c¦{@¦ØA¦ėM¦P¦ŌW¦“G¦ńP¦ĄM¦†„„…™„\F¦ĘP¦lN¦—N¦ėM¦‡F¦ ]¦TB¦•M¦ķN¦I¦bI¦ I¦‰G¦G¦Ž\¦™£„’‚¦#?¦%@¦Ļ?¦ØA¦4]¦ńP¦Ļ?¦TB¦Ļ?¦ėM¦@c¦Ļ?¦8_¦øI¦I¦³\¦*ƒ¦AN¦Ō‚¦P¦1F¦ėM¦‡F¦ĄM¦‡F¦‡F¦#?¦c¦^G¦²F¦³\¦_]¦·^¦ØA¦kc¦ńP¦ńP¦kc¦žA¦†„„\F¦ėM¦ų>¦žA¦\F¦EP¦‡F¦øI¦ńP¦ų>¦#?¦ØA¦ _¦ ]¦TB¦bI¦³\¦\¦]\¦Œ^¦™£„žA¦P@¦#?¦ńP¦ų>¦EP¦ĄM¦)B¦P¦Œ^¦‰G¦…™„‡F¦¤?¦pP¦pP¦pP¦P¦I¦%@¦Ļ?¦ėM¦™£„ńP¦%@¦Ļ?¦pP¦Œ^¦#?¦Ļ?¦ėM¦øI¦7I¦™£„‡F¦EP¦‡F¦TB¦•M¦ķN¦lN¦—N¦ķN¦bI¦4]¦˜d¦#?¦˜d¦“G¦1F¦\F¦EP¦AN¦‡F¦TB¦ĄM¦ķN¦øI¦I¦ I¦3G¦²F¦c¦™£„Ō‚¦’‚¦Uƒ¦#?¦N?¦žA¦ØA¦P@¦_]¦c¦8_¦ ]¦ńP¦ĄM¦øI¦bI¦’‚¦v|„†„„Œ^¦³\¦c¦{@¦)B¦Œ^¦’‚¦AN¦Uƒ¦pP¦lN¦™£„TB¦˜d¦v|„’Š„ėM¦˜d¦ų>¦Ļ?¦“G¦TB¦^G¦{@¦%@¦·^¦{@¦v|„\F¦EP¦Œ^¦TB¦ĄM¦•M¦ķN¦I¦G¦Ō‚¦ńP¦#?¦\¦ĄM¦…™„Œ^¦Ļ?¦)B¦pP¦{@¦#?¦ėM¦Ļ?¦ėM¦…™„TB¦‰G¦^G¦*ƒ¦€ƒ¦ś?¦·^¦kc¦Ō‚¦ńP¦v|„\F¦™£„#?¦N?¦P@¦ś?¦\¦˜d¦øI¦\F¦P¦AN¦ _¦Œ^¦bI¦]\¦žA¦lN¦³\¦Ļ?¦)B¦ _¦]\¦TB¦G¦N¦ _¦™£„€ƒ¦{@¦%@¦]\¦ńP¦†„„P¦—N¦4]¦I¦\F¦³\¦lN¦8_¦…™„TB¦˜d¦c¦*ƒ¦’Š„%@¦EP¦ńP¦ś?¦“G¦\F¦ėM¦†„„ėM¦ńP¦ķN¦\F¦Ž\¦@c¦Ō‚¦{@¦Ļ?¦@c¦pP¦ _¦’‚¦*ƒ¦ų>¦]\¦ų>¦žA¦™£„žA¦Uƒ¦Ō‚¦*ƒ¦v|„4]¦‡F¦Ž\¦Œ^¦ĄM¦øI¦ŌW¦³\¦Ļ?¦—N¦c_¦%@¦\F¦kc¦ńP¦‡F¦)B¦1F¦‡F¦™£„Ō‚¦ńP¦’‚¦*ƒ¦\¦c_¦ńP¦‰G¦…™„Œ^¦TB¦jM¦jM¦ńP¦ńP¦†„„…™„)B¦1F¦\F¦ėM¦Œ^¦ĄM¦ķN¦øI¦²F¦*ƒ¦€ƒ¦{@¦#?¦žA¦ĄM¦øI¦ I¦\F¦P¦ĄM¦‰G¦™£„‰G¦v|„†„„)B¦1F¦\F¦ĘP¦TB¦ĄM¦øI¦I¦3G¦²F¦³\¦kc¦ńP¦’‚¦*ƒ¦Uƒ¦N?¦žA¦ØA¦P@¦™£„†„„\F¦TB¦ĄM¦ ]¦kc¦’‚¦ś?¦ĄM¦øI¦†„„P¦AN¦lN¦—N¦ĄM¦ I¦AN¦—N¦)B¦P¦pP¦TB¦kc¦*ƒ¦€ƒ¦ų>¦pP¦TB¦³\¦ńP¦ś?¦³\¦ńP¦pP¦1F¦8_¦^G¦·^¦1F¦\F¦EP¦ķN¦I¦3G¦c¦Ļ?¦™£„ėM¦’Š„…™„\F¦8_¦ėM¦@c¦’‚¦*ƒ¦Ļ?¦ńP¦Ļ?¦‡F¦’Š„\F¦3G¦Ļ?¦\F¦ėM¦’‚¦{@¦Ļ?¦\¦ŌW¦TB¦ńP¦ńP¦“G¦kc¦€ƒ¦‡F¦‡F¦Uƒ¦ńP¦)B¦pP¦)B¦ _¦]\¦\F¦Œ^¦v|„†„„ I¦lN¦—N¦7I¦ńP¦Ž\¦†„„“G¦pP¦ _¦•M¦jM¦ķN¦™£„_]¦]\¦v|„1F¦1F¦‡F¦‡F¦*X¦’Š„^G¦ų>¦·^¦€ƒ¦’‚¦ńP¦Œ^¦)B¦‡F¦ ]¦™£„Uƒ¦€ƒ¦—N¦…™„{@¦Ļ?¦ų>¦ńP¦ķN¦•M¦ńP¦‡F¦™£„’‚¦ _¦]\¦Ž\¦v|„^G¦·^¦v|„jM¦’‚¦{@¦žA¦Ļ?¦\¦Uƒ¦Ļ?¦\¦ėM¦c¦Ļ?¦\F¦pP¦kc¦ńP¦c_¦c_¦ńP¦v|„AN¦—N¦ėM¦TB¦ĄM¦‰G¦ŌW¦Ō‚¦ńP¦’‚¦*ƒ¦{@¦Ļ?¦_]¦\¦P¦AN¦ĄM¦bI¦Ō‚¦ńP¦’‚¦*ƒ¦Ļ?¦’Š„…™„ĘP¦³\¦Uƒ¦v|„’Š„…™„)B¦1F¦ĘP¦TB¦³\¦kc¦™£„’‚¦{@¦N?¦ØA¦P@¦_]¦ėM¦™£„ØA¦ś?¦ų>¦Uƒ¦lN¦8_¦I¦Uƒ¦I¦c¦‡F¦P@¦)B¦ ]¦™£„Uƒ¦pP¦ĘP¦N¦{@¦ ]¦²F¦³\¦Ō‚¦ØA¦ėM¦TB¦%@¦™£„@c¦Ļ?¦ĘP¦ėM¦‰G¦c_¦@c¦Ļ?¦¤?¦…™„TB¦€ƒ¦v|„†„„…™„¤?¦ķN¦v|„Ļ?¦€ƒ¦ _¦]\¦\F¦8_¦^G¦·^¦)B¦\F¦pP¦lN¦4]¦Œ^¦TB¦ĄM¦ķN¦I¦3G¦c¦kc¦™£„’‚¦{@¦#?¦N?¦Ļ?¦\¦€ƒ¦)B¦ĘP¦N¦ _¦Œ^¦I¦‰G¦²F¦³\¦’‚¦€ƒ¦{@¦%@¦]\¦Ļ?¦†„„Ž\¦¤?¦“G¦bI¦@c¦†„„)B¦lN¦—N¦N¦ėM¦ _¦Œ^¦TB¦I¦ I¦‰G¦^G¦*X¦³\¦Ž\¦@c¦kc¦{@¦N?¦%@¦ś?¦Ļ?¦¤?¦]\¦·^¦ ]¦4]¦†„„…™„)B¦P¦—N¦Œ^¦TB¦I¦G¦’‚¦*ƒ¦ų>¦Ļ?¦bI¦TB¦c_¦˜d¦EP¦™£„P@¦N?¦†„„TB¦kc¦“G¦\F¦EP¦4]¦TB¦c¦3G¦%@¦\F¦lN¦I¦4]¦ķN¦ I¦)B¦EP¦4]¦)B¦pP¦\F¦lN¦N¦ _¦4]¦]\¦P@¦lN¦—N¦’Š„ĄM¦øI¦bI¦Ō‚¦øI¦I¦—N¦—N¦4]¦¤?¦lN¦lN¦4]¦4]¦ńP¦AN¦lN¦²F¦ØA¦ńP¦TB¦ I¦‰G¦‰G¦‰G¦\F¦\F¦ńP¦’Š„^G¦·^¦\F¦N¦Ž\¦Ļ?¦%@¦^G¦·^¦™£„’‚¦\F¦ėM¦…™„N¦ų>¦‡F¦ś?¦\¦‰G¦4]¦²F¦Uƒ¦€ƒ¦{@¦ØA¦¤?¦\F¦ńP¦kc¦ĘP¦ėM¦TB¦‰G¦c_¦@c¦Ļ?¦¤?¦)B¦“G¦\F¦pP¦P¦AN¦lN¦—N¦ėM¦8_¦ _¦ ]¦Œ^¦TB¦•M¦jM¦I¦^G¦G¦ŌW¦*X¦³\¦c_¦˜d¦@c¦kc¦™£„Ļ?¦_]¦\¦]\¦·^¦’Š„ńP¦’‚¦*ƒ¦€ƒ¦Ļ?¦ėM¦˜d¦’‚¦Uƒ¦%@¦\F¦—N¦ _¦ĄM¦I¦ńP¦]\¦øI¦c_¦)B¦pP¦lN¦TB¦ I¦‰G¦Ž\¦¤?¦TB¦‰G¦³\¦\F¦%@¦{@¦\F¦*ƒ¦\F¦ėM¦P¦™£„žA¦_]¦^G¦·^¦{@¦“G¦Œ^¦)B¦“G¦\F¦P¦AN¦lN¦—N¦ėM¦8_¦ _¦ ]¦Œ^¦TB¦•M¦jM¦I¦G¦ŌW¦*X¦c_¦˜d¦kc¦™£„Ļ?¦_]¦\¦]\¦·^¦%@¦ _¦˜d¦%@¦]\¦v|„’Š„…™„lN¦N¦ _¦4]¦‰G¦Ž\¦™£„€ƒ¦{@¦%@¦¤?¦]\¦‡F¦Ž\¦@c¦ś?¦Ļ?¦…™„\F¦—N¦Uƒ¦Ļ?¦¤?¦\¦˜d¦‰G¦{@¦ų>¦c_¦…™„—N¦˜d¦7I¦™£„ėM¦8_¦EP¦…™„@c¦’Š„P¦N¦4]¦‰G¦²F¦ŌW¦™£„Ō‚¦’‚¦Uƒ¦ų>¦N?¦ØA¦P@¦¤?¦\F¦€ƒ¦kc¦_]¦—N¦™£„\F¦lN¦Œ^¦I¦Ļ?¦²F¦ØA¦%@¦TB¦‡F¦†„„EP¦kc¦%@¦EP¦³\¦jM¦ńP¦‡F¦™£„{@¦ų>¦#?¦‡F¦v|„ķN¦pP¦^G¦·^¦Ļ?¦8_¦ ]¦TB¦3G¦²F¦Ž\¦’‚¦{@¦ØA¦EP¦‡F¦N?¦I¦˜d¦™£„…™„Ž\¦’‚¦*ƒ¦Ļ?¦ ]¦\F¦ĄM¦™£„_]¦ĄM¦Ļ?¦TB¦kc¦%@¦TB¦c¦P¦c¦€ƒ¦\F¦bI¦)B¦P¦@c¦™£„Ļ?¦“G¦1F¦\F¦EP¦ėM¦ _¦4]¦Œ^¦ĄM¦I¦c_¦ńP¦{@¦%@¦]\¦…™„ńP¦\F¦ķN¦ńP¦\F¦‡F¦™£„‡F¦Ļ?¦‰G¦)B¦“G¦)B¦\F¦lN¦—N¦€ƒ¦I¦bI¦ńP¦€ƒ¦TB¦ŌW¦³\¦Ž\¦c_¦c¦@c¦ńP¦ĄM¦øI¦I¦)B¦“G¦‡F¦TB¦c¦™£„€ƒ¦N?¦‡F¦‡F¦‡F¦‡F¦‡F¦Ž\¦pP¦kc¦‡F¦™£„žA¦TB¦’‚¦v|„TB¦ŌW¦bI¦ _¦]\¦ŌW¦v|„†„„…™„1F¦\F¦ĘP¦EP¦AN¦lN¦—N¦8_¦4]¦Œ^¦ĄM¦ķN¦øI¦I¦bI¦ I¦‰G¦²F¦³\¦c_¦˜d¦c¦@c¦kc¦Ō‚¦€ƒ¦{@¦ų>¦ØA¦%@¦Ļ?¦\¦—N¦³\¦‰G¦Ō‚¦ńP¦%@¦%@¦c¦Ļ?¦†„„’Š„EP¦ķN¦ńP¦v|„)B¦TB¦²F¦ØA¦4]¦3G¦ńP¦3G¦3G¦˜d¦˜d¦†„„I¦ńP¦¤?¦v|„…™„\F¦P¦8_¦•M¦ķN¦3G¦c_¦4]¦\F¦Ļ?¦kc¦ńP¦\F¦@c¦Ļ?¦Uƒ¦{@¦\F¦ĘP¦ėM¦4]¦ĄM¦²F¦³\¦{@¦ų>¦ØA¦Ļ?¦\¦)B¦\F¦ėM¦˜d¦v|„\F¦ĘP¦ėM¦ ]¦3G¦˜d¦c¦@c¦ų>¦žA¦Ļ?¦_]¦\¦\F¦ėM¦ĄM¦c¦@c¦Ļ?¦¤?¦Ļ?¦ėM¦ėM¦—N¦1F¦^G¦c_¦@c¦·^¦øI¦%@¦ńP¦P¦‡F¦ś?¦EP¦v|„\F¦’Š„\F¦8_¦TB¦øI¦I¦bI¦*ƒ¦)B¦\F¦8_¦TB¦øI¦I¦bI¦³\¦@c¦ńP¦’‚¦Uƒ¦{@¦%@¦ńP¦ų>¦€ƒ¦ų>¦%@¦%@¦v|„I¦bI¦Ō‚¦*ƒ¦Uƒ¦žA¦ś?¦_]¦bI¦…™„1F¦\F¦ĘP¦pP¦EP¦AN¦lN¦—N¦ėM¦ ]¦4]¦Œ^¦TB¦ĄM¦•M¦jM¦ķN¦øI¦I¦7I¦ I¦‰G¦^G¦3G¦²F¦ŌW¦³\¦Ž\¦˜d¦c¦kc¦™£„ńP¦’‚¦Uƒ¦€ƒ¦#?¦N?¦ØA¦%@¦Ļ?¦_]¦\¦·^¦ĄM¦øI¦bI¦Ō‚¦4]¦³\¦c¦1F¦ _¦]\¦kc¦ńP¦%@¦’Š„ńP¦ńP¦øI¦øI¦\F¦—N¦Œ^¦ńP¦ńP¦lN¦—N¦N¦™£„TB¦bI¦ŌW¦kc¦…™„™£„…™„%@¦I¦^G¦·^¦4]¦4]¦^G¦ńP¦ś?¦·^¦\F¦žA¦1F¦AN¦ėM¦‡F¦4]¦…™„\F¦ķN¦Ž\¦’‚¦Uƒ¦¤?¦P¦“G¦ķN¦%@¦…™„v|„\F¦bI¦žA¦#?¦“G¦Ž\¦ńP¦N¦ńP¦N¦‡F¦4]¦‰G¦pP¦N¦ _¦kc¦{@¦]\¦’Š„ŌW¦Ļ?¦†„„Ļ?¦c¦P¦—N¦ I¦#?¦TB¦ I¦‰G¦^G¦·^¦Ļ?¦‰G¦^G¦N?¦·^¦bI¦N¦4]¦€ƒ¦ų>¦ńP¦{@¦ų>¦N¦’Š„³\¦³\¦ _¦³\¦]\¦ńP¦ńP¦%@¦4]¦²F¦ØA¦4]¦#?¦4]¦ĄM¦ķN¦c¦*ƒ¦#?¦N?¦‡F¦#?¦…™„v|„\F¦€ƒ¦\F¦lN¦ĄM¦ķN¦ I¦‰G¦Uƒ¦Ļ?¦ėM¦I¦‰G¦’‚¦*ƒ¦{@¦Ļ?¦1F¦•M¦ķN¦øI¦c_¦ĄM¦øI¦\F¦ķN¦I¦²F¦@c¦ØA¦Ļ?¦\F¦‡F¦ķN¦˜d¦˜d¦ėM¦ķN¦ńP¦\F¦I¦G¦Ō‚¦TB¦•M¦ķN¦#?¦øI¦I¦N?¦P@¦™£„N?¦P@¦“G¦\F¦AN¦8_¦ _¦ ]¦ĄM¦øI¦I¦bI¦ I¦™£„#?¦_]¦\¦]\¦P@¦ńP¦%@¦v|„†„„pP¦™£„ńP¦‡F¦TB¦‰G¦c¦™£„\F¦†„„™£„4]¦^G¦@c¦€ƒ¦{@¦¤?¦·^¦3G¦’‚¦P@¦ś?¦ńP¦‡F¦²F¦™£„ØA¦‡F¦P¦TB¦ I¦*ƒ¦ų>¦%@¦ I¦ńP¦4]¦™£„ØA¦²F¦ØA¦øI¦^G¦·^¦)B¦\¦ĘP¦³\¦%@¦…™„)B¦“G¦EP¦^G¦·^¦ńP¦v|„\F¦EP¦P¦8_¦^G¦c_¦ńP¦·^¦\F¦ĄM¦bI¦ĄM¦‡F¦øI¦P@¦ś?¦ńP¦P@¦³\¦ I¦ńP¦øI¦˜d¦ńP¦pP¦lN¦øI¦Ō‚¦TB¦ĄM¦•M¦ķN¦øI¦I¦bI¦7I¦^G¦G¦c_¦c¦@c¦·^¦\F¦—N¦^G¦€ƒ¦Ļ?¦·^¦Ļ?¦Ļ?¦‡F¦I¦*X¦’‚¦ų>¦\F¦ĄM¦øI¦Ž\¦pP¦‰G¦%@¦P@¦N¦ _¦TB¦‰G¦™£„€ƒ¦{@¦%@¦]\¦Ļ?¦ų>¦“G¦“G¦)B¦“G¦ _¦TB¦bI¦^G¦™£„Ō‚¦’‚¦*ƒ¦€ƒ¦{@¦ų>¦]\¦·^¦v|„†„„…™„\F¦pP¦ėM¦Œ^¦TB¦³\¦c¦@c¦™£„*ƒ¦€ƒ¦{@¦ų>¦ś?¦Ļ?¦*ƒ¦ų>¦³\¦%@¦Ļ?¦‰G¦#?¦4]¦øI¦Ļ?¦v|„†„„’Š„…™„)B¦“G¦\F¦ĘP¦pP¦P¦AN¦—N¦ėM¦8_¦ _¦ ]¦4]¦Œ^¦TB¦ĄM¦•M¦jM¦øI¦I¦bI¦7I¦ I¦‰G¦^G¦3G¦²F¦ŌW¦*X¦³\¦c_¦˜d¦c¦@c¦kc¦™£„Ō‚¦’‚¦Uƒ¦€ƒ¦{@¦ų>¦#?¦N?¦žA¦ØA¦P@¦%@¦ś?¦Ļ?¦¤?¦_]¦\¦]\¦·^¦pP¦øI¦kc¦žA¦)B¦“G¦lN¦ėM¦8_¦TB¦•M¦jM¦øI¦I¦bI¦^G¦ŌW¦*X¦˜d¦™£„Ļ?¦·^¦I¦Uƒ¦%@¦N¦ _¦{@¦]\¦v|„€ƒ¦€ƒ¦‰G¦)B¦N¦TB¦˜d¦bI¦˜d¦P@¦bI¦’‚¦Uƒ¦“G¦\F¦‡F¦4]¦øI¦…™„)B¦ėM¦˜d¦4]¦{@¦)B¦1F¦™£„)B¦N¦TB¦bI¦^G¦G¦*ƒ¦€ƒ¦ų>¦%@¦·^¦%@¦N¦@c¦*ƒ¦€ƒ¦Ļ?¦€ƒ¦)B¦ĘP¦P¦AN¦*X¦™£„Uƒ¦N?¦P@¦¤?¦v|„\F¦EP¦8_¦ńP¦\F¦P¦lN¦‡F¦ķN¦€ƒ¦N¦“G¦1F¦EP¦1F¦P¦P¦4]¦4]¦ų>¦¤?¦P¦AN¦4]¦Œ^¦²F¦³\¦Uƒ¦‡F¦)B¦N¦ _¦G¦ų>¦]\¦%@¦%@¦‡F¦¤?¦ _¦Œ^¦%@¦]\¦@c¦%@¦\F¦ĄM¦v|„P¦ėM¦Œ^¦ķN¦^G¦3G¦@c¦Ō‚¦ńP¦·^¦ĘP¦4]¦ĄM¦•M¦ķN¦I¦bI¦²F¦³\¦˜d¦c¦kc¦€ƒ¦%@¦c¦v|„†„„N¦ėM¦Ž\¦@c¦’Š„…™„Ž\¦P¦ėM¦ńP¦…™„P¦ėM¦³\¦™£„žA¦˜d¦†„„†„„kc¦ų>¦ØA¦Ļ?¦\F¦P¦lN¦—N¦%@¦€ƒ¦€ƒ¦™£„)B¦4]¦I¦Uƒ¦TB¦“G¦P¦—N¦ĄM¦I¦˜d¦’‚¦ų>¦%@¦Ļ?¦#?¦%@¦…™„TB¦‰G¦ńP¦ų>¦P¦Ō‚¦ńP¦ńP¦*ƒ¦ĄM¦•M¦ķN¦‡F¦Uƒ¦™£„ų>¦_]¦™£„’‚¦™£„ų>¦™£„#?¦ĄM¦†„„TB¦‡F¦‡F¦TB¦^G¦%@¦·^¦EP¦ėM¦@c¦’‚¦*ƒ¦Ļ?¦\F¦%@¦\F¦†„„\F¦lN¦1F¦™£„‡F¦˜d¦%@¦Ļ?¦{@¦%@¦\F¦‡F¦8_¦ _¦ ]¦Œ^¦TB¦²F¦*X¦³\¦c_¦c¦@c¦ńP¦€ƒ¦ØA¦_]¦]\¦\F¦‡F¦‡F¦€ƒ¦)B¦\F¦EP¦P¦AN¦lN¦—N¦‡F¦8_¦ ]¦Œ^¦TB¦ĄM¦•M¦jM¦ķN¦øI¦I¦bI¦7I¦ I¦‰G¦3G¦c¦™£„Ō‚¦’‚¦*ƒ¦Uƒ¦{@¦#?¦žA¦P@¦ś?¦Ļ?¦_]¦\¦)B¦ _¦Œ^¦]\¦ų>¦ś?¦)B¦EP¦™£„Ō‚¦*ƒ¦Uƒ¦€ƒ¦{@¦P@¦ś?¦ńP¦P@¦•M¦)B¦“G¦EP¦‡F¦c¦ńP¦…™„\F¦ńP¦\F¦‡F¦ķN¦ńP¦ _¦™£„%@¦]\¦™£„ ]¦²F¦³\¦ĘP¦jM¦c_¦c¦AN¦ ]¦²F¦³\¦’‚¦ØA¦ėM¦%@¦‡F¦v|„P¦AN¦ńP¦˜d¦TB¦c¦4]¦ĄM¦™£„*ƒ¦ėM¦3G¦\F¦Ļ?¦\F¦Œ^¦*ƒ¦—N¦\¦c_¦ńP¦)B¦EP¦ ]¦™£„P@¦…™„EP¦AN¦ėM¦8_¦4]¦Œ^¦TB¦I¦ I¦‰G¦^G¦3G¦c_¦Uƒ¦ų>¦\¦·^¦\F¦Œ^¦bI¦Ļ?¦P¦—N¦v|„jM¦™£„ńP¦\F¦ĘP¦4]¦TB¦I¦‰G¦³\¦c_¦N?¦žA¦TB¦‰G¦)B¦\¦)B¦1F¦v|„†„„bI¦³\¦Ō‚¦*ƒ¦#?¦v|„†„„˜d¦‡F¦)B¦N¦4]¦€ƒ¦%@¦ų>¦P¦™£„#?¦@c¦™£„v|„‡F¦†„„™£„‰G¦N?¦™£„P@¦@c¦TB¦ńP¦P@¦\¦v|„Ļ?¦^G¦Ļ?¦·^¦c_¦%@¦ńP¦ńP¦³\¦ _¦³\¦c¦@c¦*ƒ¦ų>¦]\¦4]¦8_¦v|„pP¦^G¦·^¦EP¦’‚¦Ļ?¦N?¦P@¦Ļ?¦P@¦Ļ?¦™£„™£„\F¦…™„ėM¦P@¦ńP¦\F¦ĄM¦•M¦ķN¦_]¦€ƒ¦Ļ?¦lN¦’Š„lN¦%@¦P¦lN¦—N¦ėM¦ų>¦^G¦·^¦ų>¦Ž\¦%@¦…™„)B¦4]¦4]¦Œ^¦ėM¦ėM¦TB¦c_¦@c¦’‚¦ų>¦Ļ?¦€ƒ¦ I¦ńP¦…™„ ]¦{@¦\F¦ĄM¦ĄM¦ńP¦™£„øI¦Œ^¦c¦AN¦^G¦³\¦·^¦c¦)B¦P¦ ]¦³\¦ų>¦‡F¦P¦ĄM¦ėM¦Œ^¦Œ^¦ėM¦4]¦…™„1F¦N?¦žA¦%@¦1F¦TB¦ I¦3G¦Ļ?¦c_¦%@¦žA¦’Š„…™„)B¦ĘP¦ĄM¦ I¦‰G¦²F¦³\¦{@¦ØA¦)B¦ĘP¦P¦N¦ _¦Œ^¦I¦‰G¦kc¦*ƒ¦{@¦žA¦%@¦ś?¦]\¦ĘP¦Uƒ¦…™„lN¦ėM¦8_¦ ]¦TB¦ĄM¦øI¦bI¦³\¦Ō‚¦…™„\F¦ _¦³\¦]\¦¤?¦TB¦Ž\¦ńP¦v|„†„„’Š„…™„\F¦8_¦ ]¦˜d¦@c¦N?¦v|„ų>¦N¦I¦bI¦€ƒ¦^G¦ńP¦·^¦\¦N¦4]¦Ž\¦\F¦EP¦4]¦jM¦*ƒ¦%@¦ĄM¦{@¦v|„†„„\F¦@c¦kc¦Ļ?¦†„„pP¦@c¦v|„’Š„ĄM¦øI¦…™„Ļ?¦Ō‚¦ńP¦€ƒ¦pP¦P¦TB¦^G¦™£„€ƒ¦ų>¦·^¦bI¦ų>¦‡F¦lN¦—N¦‡F¦“G¦\F¦TB¦øI¦^G¦²F¦žA¦ØA¦%@¦ś?¦·^¦EP¦ńP¦\F¦øI¦kc¦%@¦v|„†„„Uƒ¦“G¦\F¦8_¦I¦*ƒ¦žA¦‡F¦ńP¦TB¦øI¦I¦bI¦)B¦8_¦jM¦7I¦_]¦‰G¦*X¦…™„1F¦P¦—N¦N¦ėM¦‡F¦TB¦øI¦bI¦ńP¦*ƒ¦€ƒ¦ėM¦\F¦ėM¦ĄM¦c¦øI¦bI¦c¦%@¦ńP¦…™„‡F¦Ž\¦¤?¦ _¦ ]¦³\¦]\¦v|„{@¦\F¦•M¦ķN¦\F¦P¦lN¦TB¦•M¦ķN¦7I¦²F¦’‚¦Uƒ¦{@¦N?¦žA¦ØA¦P@¦lN¦\F¦P¦AN¦lN¦TB¦•M¦ķN¦²F¦ØA¦P@¦{@¦c_¦˜d¦“G¦—N¦c_¦ńP¦#?¦†„„…™„1F¦ėM¦TB¦Ž\¦c_¦@c¦™£„€ƒ¦…™„²F¦™£„€ƒ¦…™„™£„‰G¦\F¦EP¦Œ^¦ĄM¦ I¦{@¦EP¦P¦TB¦jM¦™£„jM¦ńP¦#?¦v|„ńP¦)B¦ų>¦kc¦%@¦I¦ńP¦ś?¦ńP¦\F¦‰G¦pP¦@c¦Œ^¦‰G¦€ƒ¦{@¦ _¦]\¦Œ^¦™£„ØA¦ś?¦…™„\F¦³\¦c¦%@¦Ļ?¦\¦)B¦P¦ńP¦—N¦Ļ?¦™£„lN¦€ƒ¦{@¦EP¦v|„v|„…™„)B¦pP¦EP¦‡F¦TB¦•M¦ķN¦I¦bI¦Ž\¦@c¦kc¦#?¦%@¦•M¦#?¦ńP¦øI¦bI¦ńP¦%@¦\F¦lN¦ĄM¦ķN¦ I¦‰G¦Ļ?¦P¦AN¦lN¦AN¦lN¦pP¦EP¦‰G¦¤?¦)B¦1F¦\F¦ĘP¦EP¦P¦AN¦lN¦—N¦ėM¦‡F¦8_¦TB¦ĄM¦ķN¦øI¦I¦3G¦³\¦@c¦™£„ńP¦’‚¦*ƒ¦žA¦ś?¦Ļ?¦¤?¦_]¦ķN¦øI¦²F¦lN¦…™„P¦Ō‚¦{@¦\F¦pP¦ŌW¦†„„’Š„…™„v|„ńP¦%@¦\F¦%@¦ų>¦€ƒ¦€ƒ¦ų>¦€ƒ¦‡F¦…™„ńP¦)B¦ _¦]\¦ńP¦ńP¦TB¦’Š„)B¦pP¦“G¦G¦“G¦EP¦ĄM¦™£„’Š„v|„c¦Ļ?¦—N¦bI¦Ļ?¦†„„’Š„\F¦P¦lN¦ėM¦bI¦@c¦{@¦‡F¦•M¦ėM¦’‚¦Uƒ¦˜d¦ķN¦pP¦N¦3G¦ų>¦EP¦ĄM¦bI¦c¦@c¦ńP¦\F¦žA¦pP¦v|„øI¦™£„)B¦ _¦]\¦ŌW¦Ļ?¦‡F¦ś?¦•M¦ķN¦v|„pP¦TB¦lN¦—N¦ńP¦4]¦žA¦\F¦bI¦ś?¦…™„\F¦’‚¦lN¦I¦bI¦²F¦Uƒ¦{@¦ØA¦\F¦ _¦]\¦%@¦Œ^¦‡F¦AN¦lN¦—N¦ėM¦8_¦bI¦^G¦Ž\¦™£„#?¦·^¦\F¦pP¦ _¦²F¦ŌW¦’‚¦Uƒ¦€ƒ¦{@¦ų>¦N?¦ØA¦ś?¦Ļ?¦]\¦c_¦™£„P@¦v|„†„„pP¦N¦ńP¦²F¦v|„†„„…™„)B¦P¦ėM¦8_¦³\¦*ƒ¦c_¦c_¦c_¦ų>¦c_¦c_¦€ƒ¦‡F¦Ō‚¦ńP¦%@¦øI¦_]¦kc¦bI¦%@¦\F¦ńP¦’‚¦Uƒ¦€ƒ¦{@¦%@¦TB¦‰G¦@c¦1F¦ I¦3G¦²F¦c¦ØA¦1F¦EP¦ų>¦Ž\¦™£„Ō‚¦ńP¦v|„…™„ĘP¦8_¦TB¦øI¦*X¦³\¦c_¦Ō‚¦ś?¦1F¦Œ^¦øI¦bI¦Ō‚¦P@¦\F¦4]¦™£„€ƒ¦%@¦_]¦pP¦†„„…™„\F¦pP¦EP¦lN¦ėM¦8_¦ _¦I¦bI¦ I¦€ƒ¦ų>¦žA¦ś?¦Ļ?¦_]¦]\¦\F¦)B¦ĘP¦žA¦1F¦ĄM¦I¦²F¦kc¦ų>¦3G¦#?¦TB¦c¦—N¦%@¦lN¦8_¦ńP¦\F¦™£„N?¦EP¦ńP¦pP¦1F¦1F¦1F¦\F¦ķN¦I¦ I¦‰G¦3G¦²F¦€ƒ¦Ļ?¦P¦ I¦%@¦ś?¦™£„#?¦N?¦ØA¦P@¦ś?¦Ļ?¦ńP¦†„„Ō‚¦)B¦Œ^¦c¦)B¦4]¦™£„™£„™£„“G¦4]¦c_¦Ō‚¦#?¦I¦…™„‡F¦Ž\¦¤?¦#?¦%@¦ų>¦Ļ?¦#?¦EP¦TB¦bI¦™£„%@¦Ō‚¦ĘP¦pP¦P¦AN¦N¦ėM¦ _¦ ]¦4]¦Œ^¦ I¦‰G¦^G¦²F¦³\¦@c¦kc¦Uƒ¦{@¦N?¦ØA¦ś?¦Ļ?¦¤?¦_]¦\¦]\¦·^¦\F¦\F¦pP¦bI¦%@¦pP¦ńP¦TB¦ I¦3G¦˜d¦c¦kc¦_]¦\¦…™„Ž\¦ńP¦v|„†„„TB¦)B¦ĘP¦P¦AN¦ėM¦8_¦TB¦‰G¦*X¦³\¦@c¦™£„Ō‚¦’‚¦*ƒ¦Uƒ¦€ƒ¦{@¦ų>¦#?¦N?¦žA¦P@¦%@¦ś?¦Ļ?¦¤?¦\¦¤?¦lN¦EP¦@c¦“G¦˜d¦ńP¦™£„Uƒ¦ų>¦\F¦pP¦lN¦—N¦4]¦•M¦™£„’‚¦{@¦ų>¦%@¦P¦‰G¦€ƒ¦{@¦#?¦žA¦Ō‚¦*ƒ¦‰G¦{@¦P¦P@¦ų>¦…™„Ž\¦øI¦—N¦ńP¦ų>¦“G¦€ƒ¦€ƒ¦…™„‡F¦Ž\¦P¦)B¦“G¦\F¦pP¦P¦AN¦lN¦—N¦ėM¦‡F¦8_¦ _¦ ]¦Œ^¦TB¦•M¦jM¦I¦^G¦G¦²F¦ŌW¦*X¦c_¦˜d¦@c¦kc¦™£„ØA¦Ļ?¦_]¦\¦]\¦·^¦)B¦ ]¦™£„Uƒ¦™£„N?¦€ƒ¦ńP¦*X¦@c¦%@¦Ļ?¦…™„\F¦ĘP¦EP¦N¦ėM¦8_¦ _¦Œ^¦ĄM¦•M¦ķN¦øI¦I¦bI¦ I¦‰G¦²F¦™£„_]¦]\¦†„„‡F¦‡F¦™£„_]¦‡F¦‡F¦