README File for Updating Network Interface Card (NIC) Microcode 28 June 2000 Contents ________ 1.0 Overview 1.1 Printer Requirements 1.2 General Steps 1.3 Finding Information 2.0 Obtaining the NIC Microcode from the World Wide Web 3.0 Updating the NIC Microcode 3.1 Using NPM 3.2 Using TELNET 4.0 Adding the HTTP Service To Access Web Pages 5.0 About Embedded Web Pages 5.1 Embedded Web Page Requirements 5.2 Embedded Web Page Administrator Functions 5.3 Resetting Fast Ethernet Speed and Mode 6.0 Solving Problems 7.0 Printing a Printer Configuration Page 8.0 Hints and Tips 9.0 Trademarks 1.0 Overview _____________ This file explains how to update the microcode in the network interface card (NIC). To update the microcode, you can use either: o IBM Network Printer Manager (NPM) Version 1.10 or later for Windows NT and Windows 95 o TELNET and the command line interface Using NPM is generally easier than using TELNET. NPM is available on the World Wide Web and on CD-ROM (see the section "Finding Information"). NPM uses the term "printer network card" instead of "network interface card (NIC)". 1.1 Printer Requirements -------------------- The 7.33 NIC microcode cannot be installed on the Infoprint Color 8 or the Infoprint 21 printers. The 7.33 microcode is supported on the Ethernet and Token Ring NICs for the following printers: IBM Network Printer 12, 17, 24, and the InfoPrint 20, 32, and 40. 1.2 General Steps __________________ To update the microcode in the NIC, you: 1. Obtain the new microcode and put it on a host system (the load host) that is running TCP/IP: o If you use NPM, the load host system is the workstation that runs NPM. o If you use TELNET, the load host system is the system that has TCP/IP installed and that runs a Trivial File Transfer Protocol (TFTP) daemon program. NOTE: IBM does not recommend loading directly from a diskette. 2. Update the microcode and check the results: o If you use NPM, NPM updates the microcode and displays the results. o If you use TELNET, you connect to the NIC and enter commands to tell the NIC to get the new microcode from the load host system. 3. If you are updating from the 5.17 or earlier level of microcode to the 5.18 or later level, you must also: o Reset the NIC to factory defaults so that the values in the new microcode level take effect. o Reset any NIC configuration values that were previously set. 4. Add the HTTP service at port 80 so you can access the web pages. See "Adding the HTTP Service to Access Web Pages" section for details. 1.3 Finding Information ________________________ This file refers to these sources of information: CD-ROM for IBM Network Printers LCD4-0816-03 or later Contains software products and books for the IBM Network Printer 12, 17, 24, the IBM Network Color Printer, and the InfoPrint 20, 32, and 40. Also contains NPM for Windows NT and Windows 95, which you can use to update NIC microcode IBM Printing Systems Home Page on the World Wide Web http://www.printers.ibm.com IBM Network Printers: Ethernet and Token Ring Quick Configuration Guide, G544-5499 Comes with the NIC; is also available on the World Wide Web and on CD-ROM 2.0 Obtaining the NIC Microcode from the World Wide Web ________________________________________________________ 1. Make a directory for the microcode, such as C:\IBMNIC. 2. Access the IBM Printing Systems Home Page on the World Wide Web (www.printers.ibm.com). 3. Navigate to select Utilities and Microcode, and to select Network Interface Card microcode. 4. Download the self-extracting file NICnnn.EXE into the IBMNIC directory. 5. To unpack the files, enter this command: filename d:path /d For "filename", use the name of the downloaded file. For "d:path", use the location where you want the files to be placed: o If you use NPM, for "d:path" use "npm\NIC". For "npm", use the name of the directory where you installed NPM, such as the default directory: For Windows 95: c:\ibmnpm95\nic For Windows NT: c:\ibmnpmnt\nic For example: nic730.exe c:\ibmnpm95\nic /d o If you use TELNET, for "d:path" use the location on your system where you have configured the TFTP daemon to search for files. For example: nic730.exe c:\tftpdir /d 6. These items are unpacked into the target location: NICREAD.TXT This README file NCE733.SYS 7.33 Ethernet microcode NCX733.SYS 7.33 Fast Ethernet microcode (For part # 11L6573 and FRU # 11L6575 only) NCT733.SYS 7.33 Token Ring microcode IBMPSCPG.SYS 7.30 Embedded Web pages (note that this file is required so that the embedded web page code can be automatically downloaded when you download microcode for your NIC) TFTPD.EXE For OS/2 only: the TFTP daemon for OS/2 containing APAR 12482 for TCP/IP Versions 2.0 and 3.0 3.0 Updating the NIC Microcode _______________________________ You can update the NIC microcode using either: o IBM Network Printer Manager (NPM) Version 1.10 or later for Windows NT and Windows 95 o TELNET and the command line interface Using NPM is generally easier than using TELNET. NOTES: With either method: 1. If you are updating from the 5.17 or earlier level of microcode to the 5.18 or later level: o You must also reset the NIC to factory defaults so that the values in the new microcode level take effect, and then reset any NIC configuration values that were previously set. o You cannot download the microcode from the load host to the printer across source routing bridges. 2. You might lose contact with the printer after you reset the NIC to factory defaults because of an IP address change. 3.1 Using NPM ______________ NOTES: 1. If you are using the IPX version of NPM, make sure the workstation also has the Windows TCP/IP protocol network software installed. The TFTP daemon does not work without the TCP/IP protocol. 2. Make sure you update the microcode with NPM running on a workstation that is on the same network segment as the printer. Otherwise, you might lose contact with the printer when you load the new microcode. To update the NIC microcode using NPM: 1. From the NPM folder, select the TFTP daemon. 2. From the NPM folder, select NPM. 3. Print a NIC configuration page to use as a reference: a. From the NPM Main Window, select the printer. b. From the menu bar, select Network. From the Network pull-down menu, select Print Network Configuration Page. 4. Update the NIC microcode: a. From the NPM Main Window, select the printer. b. From the menu bar, select Network. From the Network pull-down menu, select Update Network Card Software. c. You see the Update Network Card Software Wizard dialog. Follow the instructions at the top of each page of the wizard. In the Load File Name field, specify the name of the NIC file that was unpacked into the target location ("NCEnnn.SYS" for Ethernet or "NCTnnn.SYS" for token ring). In the IP Address field, specify the IP address of the workstation that is running NPM. Make sure the IP Subnet Mask and IP Default Gateway fields correspond to the appropriate values for the printer. d. Select Finish. NPM updates the microcode. In a few minutes, NPM finishes the update and rediscovers the printer. e. You see a message telling you the results of the software update. f. If necessary, correct any error conditions and try the update again. g. When you are finished, select Exit or Cancel. h. If you see a message that NPM lost contact with or cannot contact the printer, follow the directions in the message to reconnect the printer and then look in the Printer - Software Update Results dialog to see the results of the software update. 5. If the update did not load the new level of microcode, see the section "Solving Problems." 6. If you are updating from the 5.17 or earlier level of microcode to the 5.18 or later level, reset the NIC to factory defaults so that the values in the new microcode level take effect: a. From the menu bar, select Network. From the Network pull-down menu, select Reset to Defaults. b. NPM resets the NIC to factory defaults. The reset takes a few minutes. c. The NIC resets the assigned IP address, subnet mask, and gateway. The NIC tries to automatically obtain this information after the reset. Depending on your network configuration, the NIC may obtain all, some, or none of this information. 7. If NPM does not rediscover the printer after the reset: a. Enter the information manually from the printer console or through ARP and TELNET commands from the workstation, using the values from the NIC configuration page that you printed. Follow the instructions in the "IBM Network Printers: Ethernet and Token Ring Configuration Guide." b. Use NPM to rediscover the printer. 8. After NPM rediscovers the printer, verify the IP address information: a. From the NPM Main Window, select the printer. b. From the menu bar, select Network. c. From the Network pull-down menu, select Properties. d. From the Network Properties dialog, select the TCP/IP tab. e. Verify that the IP address, subnet mask, and default gateway are correct. 9. Reset any NIC configuration values that were previously set. Use the values from the NIC configuration page that you printed. 3.2 Using TELNET _________________ To update the NIC microcode using TELNET and the command line interface, you: 1. Prepare the load host. 2. Download the microcode. NOTES: 1. Make sure you update the microcode with the load host that is on the same network segment as the printer. Otherwise, the transfer of the microcode from the load host to the NIC might not work. 2. IBM does not recommend loading directly from a diskette. PREPARING THE LOAD HOST This section explains how to prepare an OS/2 or AIX load host system from which you load the microcode into the NIC. TFTP Server software packages for other operating systems (for example, Windows NT, Windows 95, and DOS) are available from many vendors. However, IBM does not support them and this file does not explain them. PREPARING TO LOAD FROM OS/2 This procedure is for OS/2 Warp Connect with TCP/IP support enabled. 1. Open an OS/2 window or full screen. 2. Stop the TFTP daemon (TFTPD.EXE) if you are running it. 3. Make C:\TFTPDIR the active drive and directory. This directory will contain the new TFTPD.EXE program and the microcode files that you downloaded. 4. Enter this command from C:\TFTPDIR to start the TFTPD program: tftpd 5. You see the response "IBM TCP/IP for OS/2 - TFTP Server ver...ready", which indicates that the session is now running the TFTP daemon. You do not see any further messages. PREPARING TO LOAD FROM AIX 1. Verify the load host configuration for TFTP: a. Change the directory to /etc. b. Edit the file inetd.conf. c. Look for an entry for TFTP that is similar to: tftp dgram upd nowait nobody /etc/tftpd tftpd -n d. If the entry is commented out with a pound sign (#), remove the pound sign and save the file. Then, enter this command to restart the inetd daemon: refresh -s inetd 2. Put the microcode files in either the \tftpboot directory or in another directory, such as the root directory. If you put them in another directory, be sure to specify the full path name in Step 6 in the section "Downloading the Microcode." 3. Set the file permissions to "READ" for all users. DOWNLOADING THE MICROCODE 1. Print a printer configuration page to check the microcode level of the NIC (see the section "Printing a Printer Configuration Page"). 2. Log in to the NIC: a. Enter this command from an OS/2 window or full screen or on the AIX command line to TELNET into the NIC: For OS/2: telnet -p 2048 your_ip_address For AIX: telnet your_ip_address 2048 For "your_ip_address", use the IP address of the NIC. For example: For OS/2: telnet -p 2048 138.239.252.83 For AIX: telnet 138.239.252.83 2048 b. When you see the # prompt, enter this password (the password is not displayed as you type): access c. When you see the Local prompt, enter this command to change to supervisor mode: su d. When you see the Password prompt, enter this password (the password is not displayed as you type and, on some systems, you might have to press the Backspace key first): system 3. Print a NIC configuration page to use as a reference: show server config port 1 4. Enter these commands to verify that the IP address and the subnet mask are set correctly in the NIC loader software: define server ip your_ip_address define server subnet mask your_subnet_mask For "your_ip_address", use the IP address of the NIC. For "your_subnet_mask", use the subnet mask for the NIC. For example: define server ip 138.239.252.83 define server subnet mask 255.255.255.0 5. Enter this command to set the NIC to load new microcode: define server load tftp 6. Enter this command to specify the full path name of the file to be downloaded: define server software your_filename For "your_filename", use NCE733.SYS (for Ethernet), NCT733.SYS (for token ring), or NCX733.SYS (for Fast Ethernet) 7. Enter this command to specify the IP address of the load host system performing the TFTP load: define server preferred load ip your_ip_address For "your_ip_address", use the IP address of the load host system. 8. Enter this command to specify the IP address of the router or gateway for the NIC, if any (required if one or more routers are between the load host system and the printer): define server gateway load ip your_gateway_ip_address For "your_gateway_ip_address", use the IP address of the gateway node. 9. Enter these commands to reboot the NIC and start downloading the microcode (they also break the TELNET connection): sync init delay 0 flash 10. During the download, the printer console displays "I/O INITIALIZING". Wait about ten minutes for the download to be completed. Do not turn the printer off while you see "I/O INITIALIZING". When the download is completed, the printer console displays "READY". 11. Print a printer configuration page to verify that you successfully downloaded the new level of microcode (see the section "Printing a Printer Configuration Page"). 12. If the update did not load the new level of microcode, see the section "Solving Problems." 13. If you are updating from the 5.17 or earlier level of microcode to the 5.18 or later level, reset the NIC to factory defaults so that the values in the new microcode level take effect: a. Log in to the NIC (see Step 2 in this section). b. Enter this command to reset the NIC to factory defaults: init delay 0 default c. The NIC resets the assigned IP address, subnet mask, and gateway. The NIC tries to automatically obtain this information after the reset. Depending on your network configuration, the NIC may obtain all, some, or none of this information. d. Print a printer configuration page to verify that the IP address, subnet mask, and gateway are correct (see the section "Printing a Printer Configuration Page"). e. If any information is not correct, enter it manually from the printer console or through ARP and TELNET commands from the workstation, using the values from the NIC configuration page that you printed. Follow the instructions in the "IBM Network Printers: Ethernet and Token Ring Configuration Guide." f. Reset any NIC configuration values that were previously set. Use the values from the NIC configuration page that you printed. 4.0 Adding the HTTP Service To Access Web Pages ________________________________________________ If you have upgraded to level 7.20 or 7.3x microcode on the IBM Network Card for Token Ring or the IBM Network Card for Ethernet 10BaseT/10Base2, you need to use any one of the following procedures to add the HTTP service at port 80. Note! The HTTP service is automatically available on the IBM Network Card for Ethernet 100BaseTx, and any other IBM Network Card for Token Ring or IBM Network Card for Ethernet 10BaseT/10Base2 that ships with level 7.20 or greater microcode. You do not need to add the service for these cards. Procedure 1 -- Using telnet 1. telnet into the NIC 2. Enter the following command from the telnet prompt: change service HTTP 80 port 3 telnet disable Procedure 2 -- Using NPM 1. Start IBM Network Printer Manager and select the printer with 7.20 or 7.30 microcode. 2. From the Network Services tab on the Network/Properties notebook, create a new Network Service with the name of HTTP, TCP port 80, and with only the TCP/IP network Protocol selected. HTTP is not case sensitive. NPM displays an error if this service already exists. Procedure 3 -- Resetting the NIC 1. Print a NIC configuration page for future reference. 2. Reset the NIC to factory default settings. (The reset NIC will have the HTTP service at port 80.) See the Ethernet/Token Ring Configuration Guide for instructions on printing a NIC configuration page and resetting the NIC. 5.0 About Embedded Web Pages _____________________________ 7.20, 7.30, and 7.33 microcode for IBM Network Cards supports embedded web pages. With embedded web pages, you can use your web browser to: o Access status information about the printer o Display current printer settings o Display and print the NIC configuration page o Configure the NIC o Upgrade the NIC o Restart or reset the NIC o View help that describes how to use the embedded web pages o Access the IBM Printing Systems Company website, where you can get documentation, drivers, and information about support, supplies, and optional features To access the embedded web pages, go to the following location from your web browser: http://n.n.n.n where "n.n.n.n" is the IP address of the printer. For detailed information about using the embedded web pages, view the online help directly from the web pages. 5.1 Embedded Web Page Requirements ___________________________________ o You must have one of the following browsers: Netscape Communicator 4.0 or greater, Microsoft Internet Explorer 4.0 or greater o Your printer must have a TCP/IP address, subnet mask, and gateway address assigned to it. o Your screen resolution must be set to at least 800x600. o For an IBM Network Card for Token Ring or an IBM Network Card for Ethernet 10BaseT/10Base2 that has been upgraded with level 7.20 or greater microcode, you need to complete one of the procedures in "Adding the HTTP Service to Access Web Pages" on page 3 before you can access the web pages. NOTE: If you use telnet to access the NIC, IBM recommends specifying 2048 as the port number. Using 23 as the port can cause conflicts when you try to access the embedded web pages. 5.2 Embedded Web Page Administrator Functions _________________________________________ Some embedded web page functions, such as reconfiguring the NIC or downloading microcode, require user and password verification. The initial value for user is "su" and the initial password is "system" (the same value used by the telnet function). You can change the password directly from the embedded web pages. 5.3 Resetting Fast Ethernet Speed and Mode __________________________________________ Although the default speed and mode settings for the IBM Network Card for Ethernet 100BaseTx should be correct, you can, if necessary, reset these values directly from the embedded web pages or, if you use telnet to log in to the NIC, using commands. NOTE: IBM recommends leaving the default values unless problems occur. Using telnet To Set Fast Ethernet Speed and Mode Use the following command to set the speed and mode for the IBM Network Card for Ethernet 100BaseTx. define server lan speed [10hdx | 10fdx | 100hdx | 100fdx | auto] 10HDX 10Mbps, 10BaseT, Half Duplex mode 10FDX 10Mbps, 10BaseT, Full Duplex mode 100HDX 100Mbps, 100BaseTx, Half Duplex mode 100FDX 100Mbps, 100BaseTx, Full Duplex mode AUTO Auto Sense LAN speed, media type, and duplex mode (This is the factory default setting for the NIC) NOTE: IBM recommends leaving the default value unless problems occur. Displaying the Fast Ethernet Speed and Mode Use the following commands to display the speed and mode for the IBM Network Card for Ethernet 100BaseTx. show server network list server network or show config 6.0 Solving Problems _____________________ If the update did not load the new level of microcode: 1. Log in to the NIC (see Step 2 in the section "Downloading the Microcode"). 2. Enter this command to display the Debug Display for Server: show server debug 3. If the load was successful, you either do not see any response or you see the line "Network Load Error = FF" near the top left side. 4. If the download was not successful, you see the line "Network Load Error =" near the top left side. It contains hex values that indicate one or more errors. Check the first hex value on the left. Table 1 lists some of the error codes and how to fix them. If you receive other error codes, contact IBM using one of the methods in the section "Hints and Tips." +-------------------------------------------------------------+ 3 Table 1. Microcode Error Codes 3 +-------+----------------------+------------------------------+ 3 HEX 3 DESCRIPTION 3 USER ACTION 3 3 CODE 3 3 3 +-------+----------------------+------------------------------+ 3 0x01 3 At least one flash 3 Try downloading again. If 3 3 3 sector was 3 the error persists, replace 3 3 3 write-protected 3 the NIC. 3 +-------+----------------------+------------------------------+ 3 0x02 3 Flash erase error 3 Try downloading again. If 3 3 3 3 the error persists, replace 3 3 3 3 the NIC. 3 +-------+----------------------+------------------------------+ 3 0x03 3 Flash write error 3 Try downloading again. If 3 3 3 3 the error persists, replace 3 3 3 3 the NIC. 3 +-------+----------------------+------------------------------+ 3 0x04 3 LAN cable not 3 Attach the LAN cable, make 3 3 3 connected 3 sure the LAN is working 3 3 3 3 correctly, then try 3 3 3 3 downloading again. 3 +-------+----------------------+------------------------------+ 3 0x05 3 LAN chip 3 Try downloading again. If 3 3 3 initialization error 3 the error persists, replace 3 3 3 3 the NIC. 3 +-------+----------------------+------------------------------+ 3 0x06 3 Wrong loadfile for 3 Try downloading again using 3 3 3 the hardware 3 the correct file (Ethernet 3 3 3 3 or token ring) for the NIC. 3 +-------+----------------------+------------------------------+ 3 0x07 3 Ran out of buffers 3 Try downloading again. If 3 3 3 3 the error persists, replace 3 3 3 3 the NIC. 3 +-------+----------------------+------------------------------+ 3 0x10 3 Selfload image in 3 Try downloading again. If 3 3 3 flash is corrupted 3 the error persists, replace 3 3 3 3 the NIC. 3 +-------+----------------------+------------------------------+ 3 0x11 3 Compressed header 3 Try downloading again. If 3 3 3 error 3 the error persists, replace 3 3 3 3 the NIC. 3 +-------+----------------------+------------------------------+ 3 0x20 3 Undefined TFTP error 3 Try downloading again. If 3 3 3 3 the error persists, replace 3 3 3 3 the NIC. 3 +-------+----------------------+------------------------------+ 3 0x21 3 TFTP file not found 3 Correct the access to the 3 3 3 3 file through the TFTP 3 3 3 3 interface and try 3 3 3 3 downloading again. 3 +-------+----------------------+------------------------------+ 3 0x22 3 TFTP access 3 Correct the access 3 3 3 violation error 3 permission to the file, then 3 3 3 3 try downloading again. 3 +-------+----------------------+------------------------------+ 3 0x23 3 TFTP disk full or 3 This error does not apply to 3 3 3 allocation exceeded 3 microcode downloads. 3 3 3 error 3 3 +-------+----------------------+------------------------------+ 3 0x24 3 TFTP illegal 3 An internal error occurred. 3 3 3 operation 3 Try downloading again. If 3 3 3 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x25 3 TFTP unknown 3 An internal error occurred. 3 3 3 transfer ID error 3 Try downloading again. If 3 3 3 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x26 3 TFTP file exists 3 This error does not apply to 3 3 3 3 microcode downloads. 3 +-------+----------------------+------------------------------+ 3 0x27 3 TFTP no such user 3 Try downloading again. If 3 3 3 error 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x28 3 Unable to send TFTP 3 Try downloading again. If 3 3 3 ACK 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x29 3 TFTP packet sequence 3 Try downloading again. Make 3 3 3 error 3 sure you are loading from a 3 3 3 3 hard drive, not directly 3 3 3 3 from a diskette. If the 3 3 3 3 error persists, contact IBM 3 3 3 3 Service. 3 +-------+----------------------+------------------------------+ 3 0x2A 3 TFTP data packet 3 Try downloading again. If 3 3 3 error 3 the error persists, contact 3 3 3 3 your network administrator. 3 +-------+----------------------+------------------------------+ 3 0x2B 3 Error sending TFTP 3 Try downloading again. If 3 3 3 request 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x2C 3 Timeout waiting for 3 Verify that the NIC is 3 3 3 TFTP packet from 3 communicating with the load 3 3 3 load host 3 host, then try downloading 3 3 3 3 again. If the error 3 3 3 3 persists, contact your 3 3 3 3 network administrator. 3 +-------+----------------------+------------------------------+ 3 0x2D 3 Timeout waiting for 3 Does not apply to downloads. 3 3 3 TFTP put 3 3 +-------+----------------------+------------------------------+ 3 0x30 3 Error sending BOOTP 3 Verify that the NIC is 3 3 3 request 3 communicating with the BOOTP 3 3 3 3 server system, then try 3 3 3 3 downloading again. If the 3 3 3 3 error persists, contact your 3 3 3 3 network administrator. 3 +-------+----------------------+------------------------------+ 3 0x31 3 Timed out waiting 3 Verify that the NIC is 3 3 3 for BOOTP response 3 communicating with the BOOTP 3 3 3 3 server system, then try 3 3 3 3 downloading again. If the 3 3 3 3 error persists, contact your 3 3 3 3 network administrator. 3 +-------+----------------------+------------------------------+ 3 0x40 3 Error sending ARP 3 Try downloading again. If 3 3 3 request 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x41 3 Error sending ARP 3 Try downloading again. If 3 3 3 reply 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x42 3 Timed out waiting 3 Try downloading again. If 3 3 3 for ARP reply 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x50 3 Error sending DHCP 3 Try downloading again. If 3 3 3 request 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x60 3 Cannot find host 3 Try downloading again. If 3 3 3 with loadfile 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x61 3 Not a MOP packet or 3 Verify that the NIC is 3 3 3 no data in packet 3 communicating with the MOP 3 3 3 3 support host. Try 3 3 3 3 downloading again. If the 3 3 3 3 error persists, contact your 3 3 3 3 network administrator. 3 +-------+----------------------+------------------------------+ 3 0x62 3 MOP received a 3 Verify that the NIC is 3 3 3 packet from a 3 communicating with the MOP 3 3 3 different host 3 support host. Try 3 3 3 3 downloading again. If the 3 3 3 3 error persists, contact your 3 3 3 3 network administrator. 3 +-------+----------------------+------------------------------+ 3 0x63 3 MOP packet type not 3 Verify that the NIC is 3 3 3 memory load or load 3 communicating with the MOP 3 3 3 parameters 3 support host. Try 3 3 3 3 downloading again. If the 3 3 3 3 error persists, contact your 3 3 3 3 network administrator. 3 +-------+----------------------+------------------------------+ 3 0x70 3 Lower address limit 3 An internal error occurred. 3 3 3 error 3 Try downloading again. If 3 3 3 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x71 3 Upper address limit 3 An internal error occurred. 3 3 3 error 3 Try downloading again. If 3 3 3 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x72 3 PIDATA error 3 An internal error occurred. 3 3 3 3 Try downloading again. If 3 3 3 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x73 3 Transfer address 3 An internal error occurred. 3 3 3 error 3 Try downloading again. If 3 3 3 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0x74 3 Invalid OMF record 3 An internal error occurred. 3 3 3 3 Try downloading again. If 3 3 3 3 the error persists, contact 3 3 3 3 IBM Service. 3 +-------+----------------------+------------------------------+ 3 0xFF 3 Load was successful 3 None. 3 +-------+----------------------+------------------------------+ 7.0 Printing a Printer Configuration Page __________________________________________ To check the microcode of the printer and the NIC, print a printer configuration page: 1. If the printer is off, turn it on. 2. When the printer has warmed up and displays "READY", press Online to take the printer offline. 3. Press Menu to display "TEST MENU". 4. Press Item to display "CONFIG PAGE". 5. Press Enter to print the printer configuration page. 6. After the page has printed, press Online to put the printer back online. 7. Look at the lower right side of the printer configuration page for the column called "Printer Details" and for the row called "Code Levels". 8. These lines in the row "Code Levels" show the microcode levels: Printers: CTL NICs: EN (Ethernet) TR (token ring) 8.0 Hints and Tips ___________________ The methods for obtaining IBM service for IBM network printers are: o Technical Service: 1-800-358-6661 o WWW home page: http://www.printers.ibm.com o Electronic BBS: Montreal (514) 938-3022 Toronto (905) 316-4255 Vancouver (604) 664-6464 9.0 Trademarks _______________ These terms are trademarks of their respective companies in the United States or other countries or both: AppleTalk Apple Computer, Inc. AIX, IBM, NetBIOS, IBM Corporation Network Printer Manager, OS/2 NetWare and Novell Novell, Inc. PCL Hewlett-Packard Company PostScript Adobe Systems, Inc. Microsoft, Windows, and the Windows 95 logo are trademarks or registered trademarks of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Other company, product, and service names may be trademarks or service marks of others. * * * End of File * * *