   Update information and troubleshooting
                                                                    v2.02
      
      
      NetWare* server, Windows NT*, and OS/2* users
      ---------------------------------------------
      
      If you have a Plug and Play BIOS and are running OS/2, Windows NT,
      or a NetWare server, make sure you disable Plug and Play on your
      adapter using NPROSET.EXE. Having Plug and Play enabled on your
      adapter may cause configuration problems because these environments
      don't support Plug and Play.
      
      
      Make sure you're using the latest NPROSET
      -----------------------------------------
      
      Make sure you're using the latest version of NPROSET (version 3.5
      or later) that came with your adapter. If you need the latest version,
      you can download it from Artisoft's BBS. See pages 1 and 2 of your
      adapter documentation for the BBS phone numbers.
      
      
      PCI/ISA computers
      -----------------
      
      If you install the adapter in a PCI/ISA computer, you should keep
      it configured for 16-bit mode. The adapter may not work properly if
      set to 8-bit mode.
      
      Also, if you have a PCI/ISA computer without a Plug and Play BIOS,
      your adapter's flash program may be disabled during installation
      due to ROM shadowing problems. To fix this, use your computer's
      BIOS setup program to disable ROM shadowing for the flash memory
      address.
      
      
      Undetectable IRQs
      -----------------
      
      NPROSET can reliably detect most IRQs used in a computer. However,
      some devices use IRQs in a way that NPROSET can't detect. If you
      have problems with the computer after installing the adapter, make
      sure no other device uses the same IRQ as the adapter.
      
      
      NE2000 adapters
      ---------------
      
      You can't run NPROSET when NE2000 drivers are loaded. If you're
      installing the adapter in a computer with an NE2000 adapter,
      restart the computer without loading the drivers before you run
      NPROSET.


      Troubleshooting
      ---------------

      The adapter can't connect to the network

      -- Make sure the cable is installed properly.

         The network cable must be securely attached at all connections.
         If the cable is attached but the problem persists, try a
         different cable. See the Help file called Cabling specifications
         for a list of recommended cables and information on how to
         properly install the cabling.
 
         If you're directly connecting two workstations with UTP cabling
         (without using a hub), there are special cabling considerations.
         See the Help file called UTP cabling specifications for more
         information.


      -- Check the LEDs on the adapter.

         The NodeRunner Pro adapter has two diagnostic LEDs above the
         cable connectors. These lights help indicate if there's a
         problem with the connector, cable or hub.
 
         If the cable is connected to the BNC port, the ACT light
         blinks whenever the adapter sees a signal on the cable. If
         the light stops blinking, either there's no network traffic or
         there may be a problem with the network.
 
         If the cable is connected to the UTP port and a hub, the LNK
         light should be on when the adapter receives a Link pulse from
         the hub. If the light is off, there may be a bad connector, bad
         cable or problem with the hub. See the Help file called UTP
         Cabling specifications for more information.


      -- Make sure the adapter is configured.

         The adapter must use configuration settings that aren't used
         by any other device in the computer. Make sure the I/O address and
         IRQ address assigned to the adapter are unique.

 
      -- Test the adapter.

         Follow the procedures for testing the adapter outlined in this
         guide. How you test the adapter depends on which operating
         system you're running.


      -- Look for your problem in the List of Common Problems and try
         the recommended solutions.

         The list below outlines some of the problems you may encounter,
         and offers possible solutions. If none of these solutions work
         for you, check the Updated information section above, or
         contact Artisoft Technical Support according to the instructions
         on page 11 in your adapter documentation.


      List of Common Problems and Solutions

      -- NPROSET can't find the adapter.

         - Make sure there's a NodeRunner Pro adapter installed in this
           computer.

         - Make sure the adapter is seated firmly in the slot.

         - Try a different slot. 

         - Try a different NodeRunner Pro adapter. 


      -- Diagnostics pass but the connection fails intermittently.

         - Make sure the network cable is securely attached.

         - See the Help file called Cabling specifications to make sure
           the cable you're using meets IEEE specifications. 

         - Try a different cable.


      -- The "Test adapter" option is grayed out

         - Unload the network drivers and run NPROSET again to test the
           adapter. Follow the steps below:

           1. Exit NPROSET.

           2. Restart without loading the network drivers.

	      LANtastic users -- add the REM command before the line
	      that reads: CALL C:\LANTASTI\STARTNET.BAT.

	      If you're using another type of network, or if the drivers
	      are located elsewhere, type REM in front of each line that
	      loads a driver.

           3. Run NPROSET again. This time you can select "Test adapter."

	      After you're finished testing the adapter, make sure you
	      reload the network drivers. To do so, remove any REM
	      commands that you added to your STARTNET.BAT or
              AUTOEXEC.BAT file.


      -- Another board stopped working after you installed the
         NodeRunner Pro adapter.

         - Make sure the NodeRunner Pro adapter's I/O address and IRQ
           setting don't conflict with those in use by the other board.

         - Make sure all boards are seated firmly in their slots.


      -- The adapter stopped working without apparent cause.

         - Try a different slot.

         - The network driver may be corrupt or deleted. Reinstall
           the driver.

         - Try a different NodeRunner Pro adapter. 


      -- You want to restore the adapter's default settings.

         - Insert the Configuration disk into a drive, switch to
           that drive and type: NPROSET /RESTOREEPROM <Enter>.

           You'll be prompted for more information to help NPROSET
           identify your adapter.


      -- The network driver fails to connect to the server.

         - Check the Help files or your LANtastic documentation to
           make sure you installed the driver correctly.

         - Make sure the network cable is securely attached.

         - Check Artisoft's BBS for an updated driver.


      -- No highlight bar shows on a monochrome screen.

         - Restart NPROSET by typing: NPROSET /MONO <Enter>.


      -- No highlight bar shows on a plasma screen.

         - Restart NPROSET by typing: NPROSET /PLASMA <Enter>.

      
      
      
      
      
            *  Third-party trademarks are the property of their
               respective owners.
      
      
      
      
      
      
      
      
      
      
      
      
      
      
      
      
      
      
