PC World Komputer 1996 May

home *** CD-ROM | disk | FTP | other *** search

/ PC World Komputer 1996 May / PCW596.iso / wtest / clico / sunsoft / pcnfspro / ndis / drivers / ethernet / ni6510 / readme.txt < prev

Wrap

Text File | 1995-10-30 | 44.5 KB | 1,409 lines

NI6510 Installation Manual Racal InterLan 950-1255-00 Rev. AB NOTICE The hardware described in this document is subject to change without notice. The information in this document is sub- ject to change without notice and should not be construed as a commitment by Racal InterLan. While reasonable precautions have been taken, Racal In- terLan assumes no responsibility for any errors that may appear in this document. No part of this document may be copied or reproduced in any form or by any means without the prior written consent of Racal InterLan. Ethernet is a registered trademark of Xerox Corporation. IBM and Personal Computer AT are regis- tered trademarks of International Busi- ness Machines Corporation. MS-DOS is a registered trademark of Mi- crosoft, Inc. InterLan is a registered trademark of Racal InterLan. IM-NI6510 Second Edition, September 1990 Copyright ∞ 1990 by: Racal InterLan 155 Swanson Road Boxborough, MA 01719 All Rights Reserved Printed in the United States of America TABLE OF CONTENTS PREFACE Who Should Read This Manual How This Manual Is Organized Service and Support Conventions Terminology If You Have Comments about This Manual CHAPTER 1. CHANGING THE CONFIGURATION 1-1 The Preset Configuration When to Change the Configuration How to Change the Configuration Changing the I/O Base Address Changing the Boot PROM Base Ad- dress Changing the Interrupt Request Level Changing the DMA Channel Changing the Network Type CHAPTER 2. INSTALLING THE NI6510 IN YOUR PC AT Before You Begin Installation CHAPTER 3. CONNECTING THE NI6510 TO YOUR NETWORK Before You Begin Connecting to Standard Ethernet Connecting to Thin Ethernet CHAPTER 4. USING THE NI6510 DIAGNOSTIC PROGRAM Before You Begin Starting the Diagnostics Testing the NI6510 after Installation Internal and Network Tests Running Tests Separately Customizing the Diagnostics APPENDIX A. DIAGNOSTIC ERRORS User-Correctable Errors I/O Base Address-Related Errors IRQ Level and DMA Channel-Related Errors Network Connection-Related Errors Hardware Failure Error Messages SUPPORT SERVICES PREFACE The Racal InterLan NI6510 Ethernet data link controller is a 16-bit, high-performance, low-cost expansion card for PC ATs and 100% IBM compatible personal computers adhering to the ISA (Industry Standard Architecture). Who Should Read This Manual You should read this manual if you are going to install an NI6510 in a PC AT and connect it to your network. Familiarity with installing boards in PC ATs, and with the components of Ethernet local area networks, are helpful but not necessary. How This Manual Is Organized This manual is organized as follows: Chapter 1 discusses the NI6510's preset configuration, why you might need to change it, and how to change it. Chapter 2 tells you how to install the NI6510 in your PC AT. Chapter 3 explains how to connect the NI6510 to the network. Chapter 4 describes how to use the diagnostic program. Appendix A lists all diagnostic error messages and explains what to do about them. Service and Support Information about service and support for Racal InterLan products is contained in the Support Services section at the end of this manual. Conventions The term "enter," when used in reference to user input, means to type the input and then to press the Enter key. Terminology The following terms are used in this manual: * ISA (Industry Standard Architecture) is a de facto industry standard for the architecture evolved from the original IBM PC system architecture. * PC AT refers to any personal computer AT, or AT clone, adhering to the ISA. * Network refers to either a standard Ethernet (IEEE 802.3 10BASE5) network, which uses the yellow or orange coaxial cable (RG-8), or a Thin Ethernet (IEEE 802.3 10BASE2) network, which uses thin blue or black coaxial cable (RG-58). * Standard Ethernet refers to Ethernet networks using RG-8 coaxial cable. If You Have Comments about This Manual The Technical Publications Department would like to receive any comments, corrections, or suggestions you have concerning this manual. Send cor- respondence to the following address: Technical Publications Department Racal InterLan 155 Swanson Road Boxborough, MA 01719 NI6510 Installation Manual CHAPTER 1. CHANGING THE CONFIGURATION This chapter describes the NI6510's preset configuration (the way the board is set up to work with your system), why you might need to change it, and how to change it. The Preset Configuration The NI6510's preset configuration settings are as follows: * I/O Base Address is 360 (hex). * Boot PROM is disabled. * Interrupt Request Level is 9 (IRQ9). * Direct Memory Access is set to channel 3 (DMA3). * Network Type is Thin Ethernet. When to Change the Configuration You must change the configuration if any of these conditions are true: * The software you are using with the NI6510 requires settings that conflict with the preset configuration settings. * The I/O base address, IRQ level, or DMA channel matches that of another board already installed in your PC AT. * You add a Boot PROM. * Your network is standard Ethernet. If you do not need to change the con- figuration, go to Chapter 2. How to Change the Configuration To change any configuration setting, you must locate and change the cor- responding jumper setting on the board. Jumpers are two-pin combina- tions each marked by a certain setting (address, level, or channel). A small plastic block, the jumper block, fits over two pins of a jumper to enable it. Follow these steps to change any jumper setting: 1. Choose a new setting. 2. Use your fingers or needle-nose pliers to remove the jumper block from its current location. 3. Reposition the jumper block to fit over the two pins that cor- respond to the new setting. Note: The NI6510 works only with the settings listed in each section of this manual. If these settings are all being used, you must change the configuration of another board. Changing the I/O Base Address To change the NI6510's I/O base ad- dress, follow these steps: 1. Choose a new address from the list below that does not con- flict with the I/O base address of another board, and that meets software requirements, if any. 300 (hex) 320 (hex) 340 (hex) 2. Position the jumper block on the pins to correspond to the new address. Note: The NI6510 I/O base address must be at least 10 (hex) below or 2 (hex) above the I/O base address of any other board in your PC AT. Changing the Boot PROM Base Address To change the NI6510's Boot PROM set- ting, follow these steps: 1. Choose a new address from the list below that does not con- flict with the Boot PROM base address of another board, and that meets the Boot PROM device requirements, if any. D0000 (hex) D4000 (hex) D8000 (hex) DC000 (hex) 2. Position the jumper block on the pins to correspond to the new address. Note: If no Boot PROM is to be in- stalled, the jumper block must be in the NO BOOT position. Changing the Interrupt Request Level To change the NI6510's interrupt re- quest level, follow these steps: 1. Choose a new level from the list below that does not dupli- cate the IRQ level of another board, and that meets software requirements, if any. IRQ12 IRQ15 IRQ5 2. Position the jumper block on the pins to correspond to the new setting. Changing the DMA Channel To change the NI6510's DMA channel, follow these steps: 1. Choose a new setting from the list below that does not con- flict the DMA channel of another board, and that meets software requirements, if any. DMA0 DMA5 DMA6 2. Position the jumper blocks on the pins to correspond to the new channel. Changing the Network Type To change the network type setting, follow these steps: 1. Locate the switch on the board's mounting bracket, at the rear of the host. It is marked in the following way: "ENET" for Standard Ethernet is UP "THIN" for Thin Ethernet is DOWN 2. With your finger or a pointed object, slide the switch up to the position marked "ENET". You can now connect to a standard Ethernet network. The opposite position is for connecting to Thin Ethernet. NI6510 Installation Manual CHAPTER 2. INSTALLING THE NI6510 IN YOUR PC AT This chapter describes how to: * Gain access to your PC AT's expan- sion slots. * Install the NI6510. Before You Begin Make sure you have these tools: * A flat blade screwdriver * A Phillips-head screwdriver Installation To install the NI6510 in an IBM PC AT or an AT clone, follow these steps: 1. Turn off your PC AT and dis- connect the power cord. 2. Open your PC AT to expose the expansion slots. (Consult the system documentation for in- formation on this procedure.) 3. Choose a full AT expansion slot, designated by a 16-bit ex- tension. Remove the screw and the expansion slot cover; save both. 4. Place the NI6510 in the ex- pansion slot, and push down gently until the board is fully seated in the slot. Caution: Do not force the board into the expansion slot. If you meet a great deal of resistance, remove the board and try again. 5. Align the mounting bracket and secure the board with the screw that you saved. 6. Close the PC AT and reconnect the power cord. You are now ready to connect the NI6510 to your network. NI6510 Installation Manual CHAPTER 3. CONNECTING THE NI6510 TO YOUR NETWORK This chapter explains how to connect your NI6510 to a standard Ethernet or Thin Ethernet local area network. Before You Begin To connect to a standard Ethernet network, you need: * The slide latch adapter, threaded clips, and screws that came with the board * An available AC-coupled trans- ceiver installed on a standard Ethernet RG-8 cable * A transceiver cable with a male and female 15-pin D-connectors To connect to a Thin Ethernet network, you need: * A Thin Ethernet RG-58 cable seg- ment no longer than 185 meters (610 ft) * A BNC T-connector (included with the NI6510) * A 50-ohm BNC terminator, if your PC AT is the first or the last workstation on the network Connecting to Standard Ethernet Follow these steps to connect the NI6510 to an external transceiver on the standard Ethernet cable: 1. Connect the transceiver cable's female connector to the trans- ceiver. Use the slide locks on the connector bracket to secure the connection. 2. Assemble the slide latch adapt- er plate at the male connector end of the transceiver cable as follows: a. Slide a threaded clip over the hole on each side of the adapter plate. Make sure that the smaller hole faces the transceiver cable. b. Insert a mounting screw into each threaded clip. c. Slide the adapter plate, bulging side away from the cable, over the cable's locking posts. 3. Attach the transceiver cable's male connector to the D-con- nector. Screw the two mounting screws into the two screw mounts. Connecting to Thin Ethernet Follow these steps to connect the NI6510 to a Thin Ethernet network. 1. Connect the T-connector's cen- ter barrel to the BNC connector on the mounting bracket. Push the T-connector in and turn it clockwise to lock it into place. 2. If your PC AT is the first or last workstation on the network, push a 50-ohm terminator in one end of the T-connector; turn it clockwise to lock. Attach the Thin Ethernet cable from the ad- jacent PC AT to the other end of the T-connector. 3. If your PC AT is not the first or last workstation on the network, attach the Thin Ethernet cable from the adjacent PC ATs to each end of the T-connector. Push the cables in and turn them clockwise to lock. NI6510 Installation Manual CHAPTER 4. USING THE NI6510 DIAGNOSTIC PROGRAM After installation, use the NI6510 Diag- nostic Program to test the board to make sure that it is installed properly, and that its network connection is func- tional. This chapter tells you how to: * Start the diagnostics. * Run "All Tests". * Customize the diagnostic para- meters. Before You Begin Copy the following files from the diagnostic diskette to a directory in the DOS path: * NI6510DG.HLP * NI6510DG.EXE Starting the Diagnostics 1. At the DOS prompt enter: NI6510DG The NI6510 Configuration Settings Table, which displays the config- uration settings, appears. If it does not, copy the files to a directory in the DOS path again, and repeat this step. Note: If you have a configuration conflict, a warning message ap- pears. Press any key to get to the Main Menu and exit the diagnostics. You must correct the conflict directly on the board(s) involved. Refer to Chapter 1 for information on how to do this. This table displays the configuration parameters read at startup. Check to make sure the values are correct. 2. Press any key to continue. The Diagnostic Main Menu allows you to: * Run all tests. * Access other menus or help screens. * Display the error log file. * Exit the program. You can now run all tests. However, if you want to change logging devices or run tests over a long period of time, first go to the "Customizing the Diagnostics" section later in this chapter. Testing the NI6510 after Installation You can run "All Tests" (all internal and network tests, except the Echo Test), to make sure the board and its connection are operating correctly. Follow these steps: 1. "All Tests" is highlighted by default when you begin. Press Enter. Each test will run the number of times specified by the Test Repetition value (the de- fault is one). 2. Check the status window, which appears to the right of the menu, for pass or fail (error) messages. For a list of diag- nostic error messages and what to do about them, refer to Ap- pendix A. Internal and Network Tests If a test fails, you can run it sepa- rately after running "All Tests". All internal tests are listed below. * "NI6510 Reset Test" performs a software reset, and verifies that the NI6510 responds cor- rectly. * "Internal Register Test" tests the two NI6510 registers' ability to accurately hold data patterns. * "Node Address PROM Test" reads the NI6510's Ethernet address PROMs, tests pattern bytes, and verifies that they are correct. * "Initialize NI6510 Test" tests the board's ability to communi- cate with the PC AT. * "Internal Loopback Test" tests the LAN controller's ability to transmit and receive data inter- nally, its CRC logic, and its collision detection/retry logic. * "External Loopback Test" tests the LAN controller's ability to transmit and receive data ex- ternally. All network tests are listed below: * "Transmit Test" tests the NI6510's ability to transmit frames to a target (ad- dress) station. * "Receive Test" programs the LAN controller to accept all incom- ing addresses from the network, and to count, check, and display each frame on the screen. * "ITP Echo Test" tests data in- tegrity on the network inter- face. * "ITP Echo Server" enables the NI6510 to be an echo server for another NI6510 network con- troller running the Echo Test. Note: Run network tests only after all internal tests have been run successfully. Running Tests Separately Follow these steps to run any inter- nal or network test: 1. Use the or key to highlight the appropriate menu, either "Internal Tests Menu" or "Network Tests Menu", and press Enter. 2. Use the or key to highlight the appropriate test. Press Enter and the test runs. Check the status window for pass or fail (error) messages. See Ap- pendix A for a list of all error messages and what to do about them. Customizing the Diagnostics Follow these steps to customize the diagnostics: 1. Choose "Diagnostic Parameters Menu" from the Main Menu with the or key and press Enter. 2. Use the or key to highlight any of the following three config- urable parameters, and press Enter. * Log File, if you want to set up a different logging device * Test Repetition and Max. Error Count, if you want to run tests over a long period of time 3. Enter a new value at the prompt and press Enter. The new value automatically appears in the Diag- nostic Parameters Menu. Note: The diagnostic program auto- matically opens up a log file, 6510_ERR.LOG, in the directory that the NI6510 diagnostic files are in. NI6510 Installation Manual APPENDIX A. DIAGNOSTIC ERRORS This appendix lists all error messages. The errors are either user-correctable or hardware failures (not user- correctable), and are grouped accordingly. User-Correctable Errors If you get a diagnostic error message in the status window, make a note of it. Check this section to see if it is a user-correctable error. If it is, reconfigure the necessary board(s) to correct the problem (refer to Chapter 1). Note: In the following messages, xxxx stands for variable data patterns that are not equal, and (n) is the phase number of the Internal Loopback Test. I/O Base Address-Related Errors If you get any of the following mes- sages, check your boards for an I/O base address conflict. Reconfigure the board(s) to correct the problem (see Chapter 1). * WARNING: Possible I/O address conflict. Reset Failure: Status Found: xxxx Expected: xxxx * WARNING: Possible I/O address conflict. Reg. 1 Data Failure: Found xxxx Expected xxxx * WARNING: Possible I/O address conflict. Reg. 2 Data Failure: Found xxxx Expected xxxx * WARNING: Possible I/O address conflict. NI6510 Node Address PROM Failure detected. I/O address xxxx Expected: xx Found: xx IRQ Level and DMA Channel-Related Errors If you get any of the following mes- sages, check your boards for an IRQ level or DMA channel conflict. Re- configure the board(s) to correct the problem (see Chapter 1). * INITIALIZE Complete interrupt not detected. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. * Int Lpbk ph.(n) Initialize Done Interrupt not found. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. * Int Lpbk ph.(n) Xmit Packet in- terrupt not detected. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. * Int Lpbk ph.(n) Rcv Packet in- terrupt not detected. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. * Ext Lpbk Initialize done inter- rupt not found. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. * Ext Lpbk Xmit Packet interrupt not detected. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. (See also the "Network Connection-Related Errors" section for this error.) * Ext Lpbk Rcv Packet interrupt not detected. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. * Transmit Packet Test: Xmit in- terrupt not detected. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. (See also the "Network Connection-Related Errors" section for this error.) * Echo Test Error: Xmit interrupt not detected. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. Network Connection-Related Errors If you get any of the following mes- sages, check your network connection (see Chapter 3), and make sure the Network Type switch properly reflects your network type. * Initialization Failure or Warn- ing detected. WARNING: No Heartbeat detected. Check coaxial cable connection. (If your network is not config- ured with heartbeat, ignore this error). * External Loopback Failure or Warning detected. WARNING: No Heartbeat detected. Check coaxial cable connection. (If your network is not config- ured with heartbeat, ignore this error). * Ext Lpbk Transmitter error detected. Transmitter detected loss of carrier. Check network cable connection, and thick/thin Ethernet switch for correct setting. * Transmit Packet Test: Trans- mitter error detected. Transmitter detected loss of carrier. Check network cable connection, and thick/thin Ethernet switch for correct setting. * Echo Test Error: Transmitter error detected. Transmitter detected loss of carrier. Check network cable connection, and thick/thin Ethernet switch for correct setting. * Echo server Error: Transmitter error detected. Transmitter detected loss of carrier. Check coaxial cable connection. * Ext Lpbk Xmit Packet interrupt not detected. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. (If your board is set to Thin Ethernet, check your cable connection.) * Transmit Packet Test: Xmit in- terrupt not detected. WARNING: Possible interrupt level conflict, or possible DMA channel conflict. (If your board is set to Thin Ethernet, check your cable connection.) * Echo Test Error: No response from broadcast. Either the cable is not con- nected, or there is no echo server on the network. * Echo Test Error: No response from server. Either the station running or executing the echo server became disconnected, or the execution of the echo server has been stopped. Hardware Failure Error Messages The following messages indicate a hardware failure that you cannot fix. If you get any of the following error messages, refer to the Support Ser- vices section at the end of this manual. * Initialization Failure or Warn- ing detected. Status Reg. Error: Transmitter timeout error. Transmitter on longer than maxi- mum packet time. * Initialization Failure or Warn- ing detected. Status Reg. Error: Missed pack- et error detected. Receiver ran out of receive buffers. * Initialization Failure or Warn- ing detected. Status Reg. Error: Memory error detected. Did not receive READY signal within 25.6uSec. * Internal Loopback failure detected. Status Reg. Error: Transmitter timeout error. Transmitter on longer than maxi- mum packet time. * Internal Loopback failure detected. Status Reg. Error: Missed pack- et error detected. Receiver ran out of receive buffers. * Internal Loopback failure detected. Status Reg. Error: Memory error detected. Did not receive READY signal within 25.6uSec. * Int Lpbk ph.(n) Transmitter error detected. Transmitter detected a buffer error. * Int Lpbk ph.(n) Transmitter error detected. Transmitter detected an un- derflow error. * Int Lpbk ph.(n) Transmitter error detected. Transmitter detected a late col- lision error. * Int Lpbk ph.(n) Transmitter error detected. Transmitter detected loss of carrier. * Int Lpbk ph.(n) Transmitter error detected. Transmitter detected a retry error. * Int Lpbk ph.(n) Receiver error detected. Incoming packet contained a frame error. * Int Lpbk ph.(n) Receiver error detected. Overflow error detected on in- coming packet. * Int Lpbk ph.(n) Receiver error detected. A CRC error detected on incoming packet. * Int Lpbk ph.(n) Receiver error detected. A Receive Buffer allocation error detected. * Int Lpbk ph.(n) Xmit-Rcv Pckt size mismatch error. The receive frame packet size did NOT match the size of the packet transmitted. * Int Lpbk ph.(n) data mismatch. Xmit=xx Rcv=xx. The receive packet data field did NOT match the transmitted packet data field. * Int Lpbk ph.(n) CRC error detected. NI6510 CRC=xxxxxxxx Calculated=xxxxxxxx The genera- ted hardware CRC did NOT match the software calculated CRC. * Int Lpbk 3 Error: Receiver in- terrupt detected. Phase 3 of the internal loopback test, the receive frame inter- rupt, should NOT occur. * Int Lpbk 3 Error: TMD3 Retry error bit not set. Phase 3 of the internal loopback test, the Retry bit, should have been set. * Int Lpbk 3 TMD1 error bit not set. Phase 3 of the internal loopback test, the Error bit, should have been set. * External Loopback Failure or Warning detected. Status Reg. Error: Transmitter timeout error. Transmitter on longer than maxi- mum packet time. * External Loopback Failure or Warning detected. Status Reg. Error: Missed pack- et error detected. Receiver ran out of receive buffers. * External Loopback Failure or Warning detected. Status Reg. Error: Memory error detected. Did not receive READY signal within 25.6uSec. * Ext Lpbk Transmitter error detected. Transmitter detected a buffer error. * Ext Lpbk Transmitter error detected. Transmitter detected an un- derflow error. * Ext Lpbk Transmitter error detected. Transmitter detected a late col- lision error. * Ext Lpbk Transmitter error detected. Transmitter detected a Retry error. * Ext Lpbk Receiver error detected. Incoming packet contained a frame error. * Ext Lpbk Receiver error detected. Overflow error detected on in- coming packet. * Ext Lpbk Receiver error detected. A CRC error detected on incoming packet. * Ext Lpbk Receiver error detected. A Receive Buffer allocation error detected. * Ext Lpbk Xmit-Rcv Pckt size mis- match error. The receive frame packet size did NOT match the size of the packet transmitted. * Ext Lpbk data mismatch. Xmit=xx Rcv=xx. The receive packet data field did not match the trans- mitted packet data field. * Transmit Packet Test: Trans- mitter error detected. Transmitter detected a buffer error. * Transmit Packet Test: Trans- mitter error detected. Transmitter detected an un- derflow error. * Transmit Packet Test: Trans- mitter error detected. Transmitter detected a late col- lision error. * Transmit Packet Test: Trans- mitter error detected. Transmitter detected a Retry error. * Receive Packet: Fatal Error detected. Incoming packet contained a frame error. * Receive Packet: Fatal error detected. Overflow error detected on in- coming packet. * Receive Packet: Fatal error detected. A Receive Buffer allocation error detected. * Echo Test Error: Transmitter error detected. Transmitter detected a buffer error. * Echo Test Error: Transmitter error detected. Transmitter detected an un- derflow error. * Echo Test Error: Transmitter error detected. Transmitter detected a late col- lision error. * Echo Test Error: Transmitter error detected. Transmitter detected a Retry error. * Echo Test Error: Receive error detected. Incoming packet contained a frame error. * Echo Test Error: Receive error detected. Overflow error detected on in- coming packet. * Echo Test Error: Receive error detected. A CRC error detected on incoming packet. * Echo Test Error: Receive error detected. A Receive Buffer allocation error detected. * Echo Test data mismatch: Found xx Expected xx. The receive packet data field did NOT match the transmitted packet data field. * Echo Server Error: Transmitter error detected. Transmitter detected a buffer error. * Echo Server Error: Transmitter error detected. Transmitter detected an un- derflow error. * Echo Server Error: Transmitter error detected. Transmitter detected a late col- lision error. * Echo Server Error: Transmitter error detected. Transmitter detected a Retry error. * Echo Server Error: Receiver error detected. Incoming packet contained a frame error. * Echo Server Error: Receiver error detected. Overflow error detected on in- coming packet. * Echo Server Error: Receiver error detected. A CRC error detected on incoming packet. * Echo Server Error: Receiver error detected. A Receive Buffer allocation error detected. If you get the following message, you do not have a problem with your NI6510. This message indicates ei- ther a problem with your network, or with the board that sent the message. * Receive Packet: Fatal Error detected. A CRC error detected on incoming packet. SUPPORT SERVICES This section explains how to get customer support and how to get informa- tion about Racal InterLan Service Programs. If You Purchased from a Reseller You must contact the reseller or dis- tributor who sold you your Racal In- terLan product(s) in any of these in- stances: * You received damaged product(s) * You received the wrong pro- duct(s) * You need ordering, servicing, or any technical assistance If You Purchased Directly from Racal In- terLan If you purchased product(s) directly from Racal InterLan, and you are ex- periencing any of the problems listed above, call Racal InterLan. In the United States, use this number: 1-800-LAN-TALK If you are calling from anywhere out- side the U.S., you must first obtain your country code for the United States from your International Opera- tor, then use it with this number: 1-(code)-508-263-9929 ext. 323 Racal InterLan Service Programs You may purchase any of Racal Inter- Lan's service programs, regardless of who sold you your product(s). For information about these programs, write to Racal InterLan at this ad- dress: Racal InterLan 155 Swanson Road Boxborough, MA 01719 Attn. Customer Support Administrator Comments and Suggestions If you have any comments or sugges- tions, contact Racal InterLan at this uucp mail address: uunet!interlan!engsup Or, you can use the darpa internet address: engsup@interlan.interlan.com Note: These two addresses are for comments and suggestions only; they are not for the purpose of technical assistance.