AMD 10Base-T, Installing A Universal Boot ROM

Installing A Universal Boot ROM

Table of Contents

Located in the BOOTROM directory of an AMD driver diskette is a file called "netrom.hex." Boot ROM support is provided for the PCnet-ISA, PCnet-ISA+, PCnet-ISA II, PCnet 32, and PCnet-PCI devices. Remote boot is allowed from the following servers:


  Novell Server
  Microsoft LAN Manager (Server)
  IBM LAN Server

The Boot ROM is based on the IBM RPL protocol. To install the universal Boot ROM, follow the steps listed below:

1 Obtain a Boot ROM from AMD or borrow a PROM with the netrom.hex file. This hex file is in Intel MCS-86 hex format.

Note:Currently, any EEPROM greater than or equal to 16K in size can be used. Also, this EEPROM should be 250 ns or faster.

2 Insert the Boot ROM into the 28-pin socket.

3 If you are using a PCnet-ISA adapter card, then go to step 3.1 below. Otherwise, go to step 3.2 below.

3.1 For a PCnet-ISA adapter card:

a. Install the Boot ROM jumper to enable the Boot ROM. Next, set the jumpers for the I/O base address, IRQ channel, and DMA channel.

b. For PCnet-ISA, you must use one of the four configurations listed below when setting the jumpers:


Config Option    I/O Addr    IRQ     DMA        Boot ROM Addr

     1             300h       3       5            C80000h

     2             320h       4       6            CC000h

     3             340h       5       7            D0000h

     4             360h       9       3            D4000h

Note:Boot ROM Addresses listed above are not jumper settings.

c. Go to step 4 below to continue.

3.2 For PCnet 32 and PCnet-PCI adapter cards:

a. Run the AMINSTAL Utility by typing at the system prompt:


  AMINSTAL

Then press <Enter>.

b. In screen two of the AMINSTAL utility titled "PCnet Utility step 1 of 2: "CONFIGURATION" set the I/O base address, IRQ channel, DMA channel, and Boot ROM address. Support is provided for all possible combinations.

c. Exit from the AMINSTAL Utility.

d. Go to step 4 below to continue.

4 Follow the Boot ROM installation procedure outlined in the Novell Installation Manual, Microsoft LAN Manager Server Manual, or IBM LAN Server Manual to prepare the server to support RPL.

5 If you are going to do a remote boot for an OS/2 workstation on Microsoft LAN Manager, follow the steps listed below prior to performing a remote boot from the server. Otherwise, go to step 6 below to continue.

a. Edit the file "os213bb.cnf." The path to this file is as follows:


  C:\LANMAN\RPL\BBLOCK\NETBEUI\PCNTD

Notes:1) The file "os213bb.cnf" is a remote boot configuration file for OS/2 Version 1.3. If you are running a different version of OS/2 on your workstation, the file name may be slightly different.

2) In the path for the "os213bb.cnf" file, "NETBEUI" may be different depending on which protocol you are using.

b. Edit the following line in the "os213bb.cnf" file:


  DRV BBLOCK\NDIS\pcntnd.DOS ~ ~ ~

Note: The "DRV" line shown above is the default. The tildes ("~") represent parameter fields. By default a tilde means "0." Change the second tilde to a value of "10."

c. The "DRV" line should now look like:


  DRV BBLOCK\NDIS\pcntnd.DOS ~ 10 ~

Save the "os213bb.cnf" file.

d. Go to step 6 below to continue.

6 Next, perform a remote boot from the server. The diskless workstation will display some sign on messages followed by:


  To boot from Novell Server, press 1
  To boot from IBM LAN Server 2x and 3x, press 2
  To boot from IBM LAN Server 4x, press 3
  To boot from Microsoft LAN Manager, press 4
  To boot from the first available server, press 5
  If no selection within 30 seconds, will use choice 5
  Please, make your choice now!

You may now make a selection by pressing the appropriate number. If nothing is selected within 30 seconds, the appropriate server will be selected by auto detect. This is also used to support workstations without a keyboard and monitor.

After the selection is made, the remote boot process is started.

Note: This version of Boot ROM does not display the "Boot from Network (Y/N)" message. Make sure you do not have a bootable device in the system (i.e., no "A" or "C" drive). In a diskless system without a bootable device, this Boot ROM will take over the boot process.