argon audio 9130TXA, 9130TXA-M User Manual

PDF Download

Document

The World's Choice for Network Booting Solutions

QUICK START GUIDE

10/100Mbps PCI

Fast Ethernet Adapter

User’ s

Guide

9130TXA-M (Managed)

includes Argon Managed PC Boot Agent

(MBA) Boot ROM for remote management.

9130TXA (Unmanaged)

with empty Boot ROM socket

9 1 3 0 T X A - M ( M a n a g e d ) / 9 1 3 0 T X A ( U n m a n a g e d ) U S E R ’ S G U I D E

L32-bit PCI 10/100Mbps Fast Ethernet Adapter with

Boot ROM Socket and PCI 2.2 ACPI/WOL

High Performances

This card supports speeds of up to 100Mbps, thus increasing network response time and reducing network congestion.

Supports NWay Auto-Negotiation and Full-Duplex

This card automatically negotiates with switches/hubs to select a network speed that will optimize your network performance. Also with full-duplex function, this card can provide a bandwidth of up to 200Mbps in your network.

Support Wake On LAN

When this card receives a wake-up frame or magic packet from a network management station, it will work with the system's ACPI interface to power up the

PC and enable the PC to be remotely managed by the dministrator.

9 1 3 0 T X A - M ( M a n a g e d ) / 9 1 3 0 T X A ( U n m a n a g e d ) U S E R ’ S G U I D E

Features:

Fully complies with the IEEE 802.3, IEEE 802.3u and IEEE 802.3x industrial standards.

Supports 32-bit, 33MHz PCI Local Bus Master Version 2.2/2.1.

10/100Mbps Auto-Negotiation, full-/half- duplex.

Supports Wake-on-LAN power management function.

Socket for Boot-ROM.

Plug-and-Play installation.

Achieve Microsoft Certifications including 95/98/Me/NT/2000/XP.

Specifications:

Product

Network Standard

Bus Architecture

Network Port

Network Drivers

Fast Ethernet Adapter

IEEE 802.3, IEEE 802.3u, IEEE 802.3x

PCI V.2.2/2.1, 32-bit, 33MHz

UTP x 1

DOS, Windows 95/98/98SE/Me/NT/2000/XP, Windows for

Workgroup 3.11, Netware Server 3.x/4.x/5.x, Netware

ODI for DOS, Netware ODI Client 32, Packet Driver,

ACPI/Wake On LAN

Linux, Unix and MAC

PCI V2.2

LEDs Link/Activity

Dimension 121 × 40 mm (4.76 × 1.57 in.)

Weight

Operating Temperature

Operating Humidity

Certification

48g / 0.11lb.

32-131 (0-55 )

10-95% (Noncondensing)

FCC Class B, CE Mark, C-Tick

9 1 3 0 T X A - M ( M a n a g e d ) / 9 1 3 0 T X A ( U n m a n a g e d ) U S E R ’ S G U I D E

FCC COMPLIANCE STATEMENT

This equipment has been tested and found to comply with the limits of a Class B computing devices, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications.

If you suspect this product is causing interference, turn your computer on and off while your radio or TV is showing interference. If the interference disappears then when you turn the computer off and reappears then you turn the computer on, something in the computer is causing interference.

You can try to correct the interference by one or more of the following measures :

1. Reorient/Relocate the receiving antenna.

2. Increase the separation between the equipment and

receiver.

3. Connect the equipment into an outlet on a circuit

difference from that to which the receiver is

connected.

4. Ensure that all expansion slots (on the back or side

of the computer) are covered. Also ensure that all

metal retaining brackets are tightly attached to the

computer. h t t p : / / w w w . A r g o n T e c h n o l o g y . c o m

9 1 3 0 T X A - M ( M a n a g e d ) / 9 1 3 0 T X A ( U n m a n a g e d ) U S E R ’ S G U I D E

Introduction

Thanks you for purchasing our 10/100Mbps Fast Ethernet Adapter. This guide is to provide the installation and usage of this adapter for network installers and users.

The 10/100 network adapter complies to PCI 2.1 and PCI 2.2 specification and supports half/full duplex feature which can double network speed.

This adapter supports both 10Mbps and 100Mbps network speed, 100BaseTX operates on two pairs of category 5 UTP cable and 10BaseT operates on Category

3,4,5 UTP cable.

With the Auto-Negotiation technology, network speed is auto detected. When you connect the adapter to 10BaseT hub via UTP cable, the network speed becomes

10Mbps. Similarly, if you connect the adapter to 100BaseTX hub, the network speed is 100Mbps. If the hub is a switching hub which supports full duplex function, then the speed will be doubled to 20Mbps/200Mbps.

Real hassle free installation is achieved by conforming to PCI bus. Just plug in the card and all setup is done automatically. No more software to run !

Furthermore, this adapter support the Wake On LAN (WOL) feature allows users to configure network adapters that are capable of “listening to” network packets even when the computer is turned off.

This adapter supplies many drivers including NetWare Server 3.x/4.x/5.x, NetWare

ODI for DOS, NetWare ODI Client 32, NDIS driver for Windows

95/98/98SE/Me/NT/2000/XP, Windows for Workgroup 3.11, Linux, Unix, MAC and

Packet Driver for TCP/IP software. Whatever your requirements are ease of installation, superior performance or responsive support backed up by unlimited technical support, this adapter is the superior choice.

9 1 3 0 T X A - M ( M a n a g e d ) / 9 1 3 0 T X A ( U n m a n a g e d ) U S E R ’ S G U I D E

Features & Specifications

(1) Features & Benefits

Supports 32-bit PCI Bus Master for high performance

and low processor utilization.

Complies to PCI 2.1 and PCI 2.2 specification

Complies with the IEEE 802.3 CSMA/CD,

100BaseTX and 10BaseT standard.

Full duplex design to double the performance to

20Mbps/200Mbps.

One STP connector for 100Mbps or 10Mbps network

speed.

Support Auto-negotiation function.

Built-in FIFO buffers to eliminate external memory.

Auto-setups IRQ and I/O address.

Supports early interrupt on transmit to increase

performance.

Supports NetWare Server 3.x/4.x/5.x, NetWare ODI for

DOS, NetWare ODI Client 32, NDIS driver for

Windows 95/98/98SE/Me/NT/2000/XP, Windows for

Workgroup 3.11, Linux, Unix, MAC and Packet Driver

for TCP/IP software.

Provides diagnostic software and one LED to

indicate network link/activity.

9 1 3 0 T X A - M ( M a n a g e d ) / 9 1 3 0 T X A ( U n m a n a g e d ) U S E R ’ S G U I D E

(2) Technical Specification

Topology: Star

Connector: RJ-45

Standard: IEEE 802.3 10BaseT

IEEE 802.3u 100BaseTX

Transmission Rate: 10Mbps or 20Mbps

100Mbps or 200Mbps

Hardware Required: IBM compatible PC with

available PCI slot

( PCI 2.1 or PCI 2.2 )

IRQ Line: Assigned by system

I/O Address: Assigned by system

Drivers: NetWare Server 3.x/4.x/5.x,

NetWare ODI for DOS, NetWare

ODI Client 32, Windows

95/98/98SE/Me/NT/2000/XP,

Linux, Unix, MAC, Packet

Driver for TCP/IP software

Temperature: 0 0 C to 55 0 C (Operating)

Humidity: 10% to 90% (Non-condensing)

Certification: FCC Class B, CE Mark, C-Tick

Dimension: 120 x 40 mm

Weight: 50 g

Power consumption : 1.8W (Max.)

9 1 3 0 T X A - M ( M a n a g e d ) / 9 1 3 0 T X A ( U n m a n a g e d ) U S E R ’ S G U I D E

Installation

(1) Hardware Installation

To insert the network adapter into your PC, follow the steps bellow :

1. Turn off the computer and remove its cover.

2. Insert the adapter into a PCI slot.

3. Secure this adapter to the rear of the computer

chassis and put back the computer cover.

4. Connect the adapter to the network using twisted-

pair cable.

(2) Hardware Requirement for Wake On LAN

If your motherboard support the PCI 2.1 only, then

the motherboard must provide a 3-pin WOL

connector.

(Some computers may require you to change a setting

in your computer’s BIOS or setup program to enable

the WOL feature.)

If the motherboard support PCI 2.2, we don’t need

the 3-pin WOL connector. ( the function will be

provided from the PCI bus directly )

ATX 2.01 power supply.

Note : Install only one active WOL adapter per

computer. You can install additional,

non-WOL adapters.

(3) Hardware Installation for Wake On LAN

If your motherboard support the PCI 2.2 standard, no other procedure is needed. But, you still can follow the steps (for PCI

2.1) below on the PCI 2.2 motherboard, and all the function include the WOL will work normally.

9 1 3 0 T X A - M ( M a n a g e d ) / 9 1 3 0 T X A ( U n m a n a g e d ) U S E R ’ S G U I D E

If the motherboard support PCI 2.1 only, please follow the next procedure,

1. Unpack the 3-pin auxiliary power cable.

2. Insert the 3-pin auxiliary power cable into the

connector on the adapter.

3. Attach the 3-pin auxiliary power cable to the

connector on the PC motherboard.

(4) Driver Installation

Use the drivers supplied by the diskette included in this product. For detail description, please refer to readme.doc or readme.exe in the diskette provides by this product.

9 1 3 0 T X A - M ( M a n a g e d ) / 9 1 3 0 T X A ( U n m a n a g e d ) U S E R ’ S G U I D E

Trouble-shooting

If you experience any problems with the adapter, first make sure the appropriate driver is loaded, the proper cable is connected to the adapter port and the hub complies with the adapter specification, such as 10Mbps 10BaseT or 100Mbps 100BaseTX, then check the LED.

The adapter provides one LED to indicate network status.

● Link/Activity

A LED indicates if the UTP port has been LINK ok or not. When the light is OFF, it indicates that the UTP port has not been connected or LINK not ok. When the light is ON, it indicates that the UTP port

LINK ok. When the light is BLINKING, it indicates that there is traffic flow on the network which the adapter is connected to.

9 1 3 0 T X A - M ( M a n a g e d ) / 9 1 3 0 T X A ( U n m a n a g e d ) U S E R ’ S G U I D E

( Wake On LAN )

● The PC can not boot up after installing the

adapter.

1. Remove the 3-pin cable from the PC connector.

2. Boot up the PC, run setup program to configure the

adapter as “Active Low”(Default setting is “Active

High”)

3. Turn off the PC and reconnect the 3-pin cable to the

PC.

4. Boot up the PC again.

● The PC does not boot up when a Magic

Packet or Wake Up Frame is sent.

1. Check the specification of this PC meets the

hardware requirement in chapter 2.

2. Verify the BIOS setting of Wake On LAN is

configured properly. (Please check your computer

owner’s manual or contact your dealer for more

information.)

3. Remove the PC cover and check the 3-pin cable

connection.

4. Run configure program to check the setting of this

adapter.

5. If the adapter still does not wake up, install a known

good working Wake On LAN adapter and 3-pin

auxiliary power cable in the PC and recheck the PC.

[!] Contact your dealer if problem persist.

A r r g o n M a n a g e d P C B o o t t A g e n t t

U s e r r G u i i i d e

J u n e 2 0 0 2

No part of this document may be reproduced in any form or by any means or used to make derivative work (such as translation, transformation, or adaptation) without prior written permission from Argon

Technology.

The information in this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Argon Technology. Argon Technology assumes no responsibility or liability for any errors or inaccuracies that may appear in this document or any software that may be provided in association with this document. Argon Technology may make improvements or changes in the product(s) and/or the program(s) described in this document at any time.

All other brands and product names are trademarks or registered trademarks of their respective owners.

Other product and corporate names may be trademarks of other companies and are used only for explanation and to the owners’ benefit, without intent to infringe.

Chapter 1: Introduction........................................................... 17

Manageable PCs .....................................................................17

Argon Managed PC Boot Agent (MBA) ........................................17

Features................................................................................19

Boot Image Editor...................................................................19

Chapter 2: Installing MBA........................................................ 21

MBA ROM Installation ..............................................................21

Types of MBA Installation .....................................................21

ROM Installation .................................................................21

Boot Image Editor Installation ..................................................24

Chapter 3: Configuring MBA .................................................... 25

Programming Your MBA ROM Using the MBAFLASH Utility.............25

Setting the Boot Order on PCs with BBS BIOS.............................26

Configuring MBA's Options .......................................................26

Configuration Tables ...............................................................27

Changing the Options ..........................................................35

Using the MBA-Based Configuration .......................................36

Using the MBACFG Utility .....................................................37

Changing Configuration Options Using a Configuration File ........38

Changing Configuration Options from the Command Line..........40

Updating to a Newer MBA Version .........................................40

Restoring a Previously Backed-up Version...............................41

Chapter 4: Using MBA Base Code............................................. 44

Boot Failure ...........................................................................44

Displaying Verbose Status Information (v or Ctrl+Alt).................45

Displaying MBA Information (Shift+Shift)...................................45

Troubleshooting .....................................................................46

Compatibility Problems with Option ROMs for Hard Disk or SCSI Controllers

........................................................................................46

Chapter 5: Using Pre-OS.......................................................... 47

Introduction...........................................................................47

Pre-OS Framework..................................................................48

PC Pre-OS Bootup Sequence.................................................49

Creating Pre-OS Boot Images ...................................................49

Defining Boot Image Content................................................50

Creating TCP/IP or PXE Pre-OS Boot Images ...........................51

Creating NetWare Pre-OS Boot Images ..................................51

Sample Pre-OS Frameworks .....................................................51

TCP/IP or PXE Pre-OS Sample...............................................52

NetWare Pre-OS Sample ......................................................54

Technical Information..............................................................55

Chapter 6: Using MBA in TCP/IP Environments ....................... 56

TCP/IP-Specific Features ......................................................56

Network Requirements ........................................................56

Setting Up the Server..............................................................57

BOOTP Service ...................................................................57

DHCP Service .....................................................................57

TFTP Service ......................................................................57

Creating a Boot Diskette ......................................................57

Creating a Boot Image File Using Boot Image Editor ................58

Boot Screen .......................................................................59

Other Tools............................................................................60

FREEMEM: Free RAM Disk Memory.........................................60

BPPATCH: Supporting Replaceable Parameters ........................60

Application Notes....................................................................61

Using Memory Managers ......................................................61

Troubleshooting .....................................................................62

Quick Fixes: What to Check First ...........................................62

MBA Messages....................................................................62

File Transfer Error Messages.................................................62

Chapter 7: Using MBA in a Wired for Management Environment Using PXE

.............................................................................. 64

Introduction...........................................................................64

Quick Setup ...........................................................................66

Boot Screen .......................................................................66

Creating a PXE Boot Image File Using Boot Image Editor ..........66

Chapter 8: Using MBA in NetWare Environments..................... 68

Introduction...........................................................................68

Network Requirements ........................................................68

Quick Setup ...........................................................................69

Boot Screen .......................................................................70

Creating a Boot Image File Using Boot Image Editor ....................71

Boot Using MBA ..................................................................74

Creating Additional Boot Image Files......................................74

Creating and Editing the BOOTCONF.SYS Boot Index File ..........74

Avoiding AUTOEXEC.BAT Conflicts in SYS:LOGIN .....................76

Using Boot Image Editor to Create Additional Boot Image Files ..77

Selecting Different Images at Boot Time ....................................77

Multiple Servers: How the MSD NLM Can Help ............................77

Installing MSD ....................................................................78

MSD Command Line Options.................................................78

NODEFAULT Mode ...............................................................79

MSD Console Display ...........................................................79

MSD PC Messages ...............................................................79

Application Notes....................................................................80

Using Novell's Client 32 for DOS/Windows with MBA ................80

Formatting Diskettes Using Windows .....................................80

Transferring From the Boot Image to SYS:LOGIN ....................81

Troubleshooting .....................................................................81

Quick Fixes: What to Check First ...........................................81

MBA Messages....................................................................82

Batch File Missing Messages and How to Avoid Them ...............83

Chapter 9: Using MBA in Remote Program Load Environments 84

Introduction...........................................................................84

RPL-Specific Features ..........................................................84

Quick Setup ...........................................................................85

Troubleshooting .....................................................................85

Appendix A: Technical Support................................................ 88

Online Technical Services.........................................................88

Argon Technology Web Site ..................................................88

Support from Your Distributor...............................................88

Support from Argon ............................................................88

Argon Software License Agreement......................................... 92

Glossary 98

C h a p t t e r 1 : : I I n t t r r o d u c t t i i o n

Thank you for choosing Argon Managed PC Boot Agent (MBA), the world's bestselling network preboot solution for PC networks. MBA is a package of multiprotocol firmware and software tools that enables a network administrator to remotely administer software, operating systems, and applications over the network, eliminating the need to visit the client's desktop in person. MBA is a universal, easy to configure preboot solution that is compatible with today's client and network operating systems.

With MBA installed, your client PCs can boot from the network regardless of the contents of their local hard drives or, in some cases, without any local drives at all. MBA makes sure your users connect to the network every time.

MBA enables new and existing PCs to take advantage of preboot management technology to perform operating system and application installations or upgrades as well as desktop disaster recovery. MBA includes the Wired for Management

(WfM) standard Preboot eXecution Environment (PXE) protocol, but goes beyond that to include legacy boot protocol support for networks such as NetWare and

UNIX. MBA is the most universal, pervasive preboot solution available on the market today.

M a n a g e a b l l e P C s

To take advantage of current and emerging Managed PC applications, companies need PCs that can cooperate in the management process. These PCs have management-ready network interface cards (NICs) with functions implemented in firmware, software, and hardware. While some features are applicable only to newer PCs, many can be implemented on existing PCs through a software download, flash ROM update, or ROM upgrade.

In selecting management-ready PC NICs, companies can smooth the transition to a centrally-managed environment by choosing products that support the widest range of industry-standard protocols, existing network administration services and tools, and management applications. Wise choices will also help to future-proof investments for what is sure to be a period of emerging technology developments and rapid change.

A r r g o n M a n a g e d P C B o o t t A g e n t t ( ( M B A ) )

What It Does

The Argon Managed PC Boot Agent (MBA) enables a PC to boot from a remote server even if the local operating system (OS) is unable to boot or is nonexistent.

It enables administrators to perform a wide range of preboot management tasks such as virus scanning, backups, disaster recovery, reconfiguration, and applications and OS installation and updates. MBA can automate a multicast boot, bringing up hundreds of PCs simultaneously. All of these preboot processes are transparent to the user, since the PC behaves as if the boot took place from the local hard drive.

Benefits

MBA improves IS productivity and responsiveness as well as end-user satisfaction by eliminating most of the need for on-site troubleshooting and disaster recovery.

Instead, the vast majority of software problems can be solved remotely and rapidly. Because boot failures typically make it impossible for users to connect with the network, even the most sophisticated enterprise management tools at the administrator's disposal are of no use.

MBA guarantees that every PC on the network—even those with damaged operating systems and new PCs with no OS and unformatted hard disks—will connect to the network. The ability to boot under management control also protects PCs when they are most vulnerable to boot sector viruses. In addition,

MBA improves IS productivity by enabling administrators to configure or update any number of PCs very efficiently by making changes to a single image on a network server.

How MBA Works

PCs can be configured to boot from a server using a combination of configuration files, boot image files, and software residing on the server's hard disk. MBA retrieves the required information (for example, an operating system, memory managers, network drivers) from these files on the server when the PC starts.

This process has commonly been described in the past as remotebooting.

Traditional remotebooting may not be adequate in establishing a complete work environment due to requirements imposed by today's GUI operating systems and applications. In this case, MBA can become a compelling administrative tool when configured to perform a Pre-OS boot prior to every local boot. Using MBA software and utilities including Pre-OS, a network administrator can make use of diagnostics, configuration, or maintenance tools prior to completing the local boot process.

F IGURE 1: H OW MBA W ORKS

Standards Supported

MBA supports Wired for Management (WfM). It also supports all major boot protocols, including not only Preboot eXecution Environment (PXE) protocol originally defined in the Net PC specification, but also existing protocols such as

BOOTP, DHCP, RPL, and NCP/IPX. Customers thus have the flexibility to use

Microsoft NT, Windows 2000, or to “roll their own” management solutions using the booting support built into other platforms such as NetWare, Linux, HP UX, Sun

Solaris, and OS/2 WARP.

What You Need to Use MBA

To implement the Argon Managed PC Boot Agent you need:

A NIC with preboot agent firmware (MBA). The agent, which acts as an additional layer of BIOS, can also be installed on an existing NIC as a chip in the Boot ROM socket or through a system BIOS flash upgrade.

A central boot configuration server

F e a t t u r r e s

MBA includes the following features:

Supports local and network operating systems including DOS, Windows 3.x,

Windows 9x, Windows NT, Windows 2000, Windows XP, Linux, Novell

NetWare, and others

Fully configurable boot options to enable client PCs to use MBA in various environments, with or without local hard drives

Available as a network interface card (NIC) ROM; also available as a BIOS update for motherboards which contain network interface hardware. Can be in BIOS even if the PC has a separate NIC

Supports flash ROM configuration and update changes locally or over the network, depending on the NIC ROM or BIOS version

Supports multiple boot protocols and network environments such as PXE,

TCP/IP, NetWare, and RPL

B o o t t I I m a g e E d i i t t o r r

Boot Image Editor is a Windows-based utility that enables network administrators to create and manipulate PXE, TCP/IP, and NetWare boot images. The boot image files created with the Boot Image Editor allow network client PCs to boot from servers instead of local drives or to perform Pre-OS tasks before booting from the client PC’s local drive.

With Boot Image Editor, you can:

Create boot image files (from boot diskettes) that contain standard startup files and reside on a server

Create boot image files up to 16 MB in size

View and modify the contents of boot image files

Create a menu boot file and designate a list of boot options from which endusers can choose at boot time

Create Pre-OS boot image files that can execute third-party desktop management agents on the client PC before it boots from the local drive

Boot Image Editor takes a snapshot of a boot diskette. Without Boot Image Editor, creating, examining, and modifying boot image files is a tedious exercise.

Although the Boot Image Editor can be installed on any computer, it is usually

implemented on a server or a network administration PC. For installation instructions, see “ Boot Image Editor Installation ” in Chapter 2 “Installing MBA.”

C h a p t t e r 2 : : I I n s t t a l l l l i i n g M B A

M B A R O M I I n s t t a l l l l a t t i i o n

This section shows you how to install an MBA ROM on your NIC.

Types of MBA Installation

MBA is available on a PC in one of the following ways:

Installation MBA Type

Integrated into the PC BIOS by the PC manufacturer *

Contained in a

ROM that is preinstalled on the

PC's NIC

Contained in a

ROM that must be installed on the

PC's NIC.

Not needed

Install the ROM. The following section describes how to install this ROM.

Additional Steps

Required

Go to Chapter 3

“ Configuring MBA ”

Go to Chapter 3

“Configuring MBA”

Go to Chapter 3

“Configuring MBA”

* You can determine whether the MBA is integrated into the BIOS by viewing the phrase “BIOS integrated” displayed beside the version number when MBA is executed, or by viewing the MBA information screen. Refer to “ Displaying MBA Information ” in

Chapter 4 “Using MBA Base Code.”

ROM Installation

Installing the MBA ROM is a straightforward task, but you must take care to ensure that components are not damaged. Be sure you understand the following instructions before installing MBA.

C A U T I O N : Risk of equipment damage

Before removing a NIC, attach an earth ground to the PC chassis. If an earth ground is unavailable, ensure that the power is switched off and plug in the PC's grounded AC power cord.

Wear an anti-static wrist strap when handling ROMs. As an additional measure, do not touch the ROM's connectors. Leave the ROM in its conductive foam packaging when not in use.

• If you are installing MBA on a NIC that is already in your PC, remove the NIC from the PC. If you are not familiar with inserting and removing cards in your PC, refer to your NIC user guide for instructions.

• Locate the boot ROM socket on your NIC. You may need to refer to the NIC's user guide to locate the correct ROM socket.

• Depending on your NIC, you may have either a DIP socket (rectangular socket with two rows of pins), or a PLCC socket (small, square socket with pins on all sides). Follow the applicable procedure for either the DIP Socket Installation or the PLCC Socket Installation, then follow the procedure Installing the NIC into the

PC.

DIP Socket Installation

The DIP socket should have a notch that can be indicated by a small half circle, a small triangle, or a small indentation at one end of the socket. The circuit board may also have a white rectangle around the socket which should have a notch indicated at the same end. This notch indicates the Pin 1 end of the socket. See

Figure 2.

F IGURE 2: I NSERTING THE DIP ROM

1. Look at the MBA ROM while it is still in its protective foam. When the label on the top of the ROM is right side up, you should see a small half circle at the left edge of the ROM. This indicates the ROM's Pin 1 notch.

• Remove the MBA ROM from its protective foam. The pins on the ROM are very delicate, so be careful not to damage them. Align the notch on the top of the

MBA ROM with the notch in the ROM socket on the NIC.

C A U T I O N : Risk of equipment damage

If you install the MBA ROM backwards, you will destroy it! Make sure the notch in the socket is lined up with the notch in the

MBA ROM before doing anything else.

• Align the pins on the ROM with the pin receptacles in the ROM socket. Press down gently and evenly on the ROM to ensure that it is seated correctly in the socket.

PLCC Socket Installation

The PLCC socket has three square corners and one angled corner. The angled corner of the ROM must be oriented to match the angled corner of the socket. See the top left corner in Figure 3.

IGURE

3: I

NSERTING THE

PLCC ROM

2. Remove the MBA ROM from its anti-static packaging, and align the angled corner of the MBA ROM with the angled corner of the ROM socket on the NIC.

• Press down gently and evenly on the ROM to ensure that it is seated correctly in the socket.

Installing the NIC into the PC

Now that the ROM has been inserted into the NIC, you can install the NIC into the

PC.

3. Insert the NIC into the PC. Refer to the NIC's user guide for installation instructions.

• Some NICs have a switch, jumper or software setting that needs to be changed to enable the boot ROM socket; this is usually determined by the NIC's bus architecture:

Adapter Type

PCI NICs and Plug and Play

ISA NICs

ISA (legacy, non Plug and

Play) NICs

Configuration

Often the PC automatically configures the NIC to enable the ROM to a nonconflicting address. However, sometimes you may need to run a utility to enable the ROM socket on the NIC. Refer to the NIC's user guide for information on how to set up the

NIC.

Use either NIC configuration software or jumpers/switches to enable the

ROM region to the desired memory address and size.

B o o t t I I m a g e E d i i t t o r r I I n s t t a l l l l a t t i i o n

The Boot Image Editor software can be found on the MBA Utility Disk.

To install Boot Image Editor:

4. Create a directory, for example, IMGEDIT, on the PC Boot Image Editor will be used on.

• Copy the all the files from the IMGEDIT directory on the MBA Utility Disk to the new directory.

• Run the IMGEDIT.EXE application. The program detects that this is the first time it has been executed on the PC and takes you through a quick installation and configuration procedure, where you can select the appropriate network type and make file associations.

C h a p t t e r 3 : : C o n f f i i g u r r i i n g M B A

This chapter shows you how to configure MBA options.

P r r o g r r a m m i i n g Y o u r r M B A R O M U s i i n g t t h e

M B A F L A S H U t t i i l l i i t t y

If MBA was not preinstalled on the NIC, the ROM you installed must be programmed with the correct MBA software for your specific NIC. To do this, run the MBAFLASH utility (MBAFLASH.EXE) that is included in the UPDATE directory on the MBA Utility Disk. The MBAFLASH utility programs your boot ROM chip with

MBA software.

N O T E : If MBA is integrated into the PC BIOS you cannot update it with the MBAFLASH utility.

N O T E : If you are using Windows, the MBAFLASH utility operates only in MS-DOS real mode, not from a DOS window.

The MBAFLASH utility detects which NIC you are using. If your NIC is one of the supported NICs, the MBAFLASH utility displays three prompts. Use the following steps to respond to these prompts:

Step 1 - Read the License Agreement

The MBAFLASH utility asks if you agree with the License Agreement. If you have not reviewed the License Agreement, we recommend that you do so.

5. To view the License Agreement, press R to exit the program and return to

DOS. Next, run the BWVIEW utility -- found in the root directory on the MBA

Utility Disk -- and select the License Agreement menu item.

• If you have reviewed and agree with the License Agreement, press A to continue the MBAFLASH utility process.

Step 2 - Back up your ROM software

The MBAFLASH utility displays a prompt asking whether you wish to make a backup of the current software in your ROM before it programs the ROM with the new MBA software.

Answer Yes. The MBAFLASH utility reads the current software from your

ROM and saves it to a .ROM file on a floppy disk.

After the MBAFLASH utility has programmed your ROM with the new MBA software, you can revert to the previous software using this .ROM file with the MBAFLASH utility. Refer to “Updating your MBA ROM” later in this chapter.

Step 3 - Program your ROM

The MBAFLASH utility displays a prompt asking whether you wish to continue with the process of programming your ROM with the correct MBA software for your NIC.

6. Answer Yes. The MBAFLASH utility completes the process.

• When the MBAFLASH utility is complete, run the MBACFG utility to verify that

MBA options are correct for your requirements. Options are shown in the configuration tables in this chapter.

Command Line Options

Although you can use the MBAFLASH utility interactively, you can also automate some of the process using command line options. This feature is helpful if you wish to use the MBAFLASH utility as part of a batch file. The command line options are:

Usage: mbaflash [.ROM Filename] [/?] [/p] [/b] options:

.ROM Filename - filename of a .ROM file that you wish to program into your ROM chip. Refer to “ Updating your MBA ROM ” later in this chapter. Required only if you want a different version of MBA than the one contained within the

MBAFLASH utility (for example, if you want to revert to the previous version using the .ROM file created by the

MBAFLASH utility in step 2 above).

/? - show this help

/p - display no prompts

/b - do not create a backup of current ROM contents

B I e

I t t

O t t i i

S n g t t h e B o o t t O r r d e r r o n P C s w i i t t h B B S

A PC that supports Plug and Play can automatically detect and set up devices such as CD-ROM drives, hard disks, and NICs. The BBS specification (developed by

Compaq, Phoenix, and Intel) specifies how the system BIOS identifies boot devices in a PC, allows the user to select the boot order of these devices, and then sequentially attempts to boot from each device in the specified order.

N O T E : PC manufacturers may call their BBS support by other names such as Multiboot.

PCs that are Plug and Play BBS-BIOS compatible allow you to specify the boot order in the PC’s BBS-BIOS Setup menus. Because these BIOSs can detect the existence of MBA UNDI, you can specify the position of MBA UNDI in the boot order with respect to the other boot devices. If you want the PC to always boot from the network first, be sure to put MBA UNDI at the top of the boot order list.

You can also use the MBACFG utility to make MBA UNDI first in the BBS boot order. MBACFG provides a menu command that makes MBA UNDI the first boot device.

If the PC's BIOS is not BBS-compliant, MBA UNDI attempts to control the boot process (this behavior is configurable with MBA UNDI) and perform a network or local boot, depending on the configured options.

C o n f f i i g u r r i i n g M B A ' ' s O p t t i i o n s

MBA has many operating options that you can configure. For a complete list of all possible options refer to the configuration tables in this chapter.

Some versions of MBA may not allow you to configure all the options listed in the tables, or a version of MBA may have some extra options for your specific NIC.

Refer to the Configuration Supplement for a description of any exceptions or additions for your version of MBA. Configuration Supplements are text files that can be found on the Utility Disk. If there is no Configuration Supplement for your

NIC, then there are no exceptions or additions. In this case, use the options exactly as listed in this guide.

C o n f f i i g u r r a t t i i o n T a b l l e s

Tables on the following pages show the configuration options available for each boot method. To see the available options, select your boot method and go to the appropriate table.

Boot Method Go To

TCP/IP

PXE

NetWare

RPL

Table 1 : TCP/IP Configuration Options

Table 2 : PXE Configuration Options

Table 3 : NetWare Configuration Options

Table 4 : RPL Configuration Options

In addition, MBA UNDI startup options are shown in Table 5 : Startup Options.

T ABLE 1: TCP/IP C ONFIGURATION O PTIONS

Option

Name

Possible

Values

Description Default

Protocol

Default

Boot

Local Boot

Config

Message

DHCP, BOOTP

Network

Local

Enabled

Disabled

Enabled

Disabled

Enabled

Disabled

Choose the specific protocol for TCP/IP boot method.

Choose whether MBA will perform a network boot or a local hard disk boot by default. If Network boot is chosen as the default, the Local Boot

Message is displayed at boot time (if a bootable device exists and Local Boot is enabled). If Local boot is chosen as the default, the Network Boot message is displayed at boot time. Not available with BBS-BIOS.

Choose between allowing or disallowing a local boot from a hard disk or diskette. When local booting is disabled, the PC is forced to boot from the network even if a bootable diskette is inserted in drive A:, or if the local hard disk contains an active partition. Not available with BBS-BIOS.

Choose whether to prevent access to the

Configuration Screen that is built into the MBA

ROM. When Disabled, the Configuration Message is not displayed. Also, when Disabled, the only method to modify the MBA options is by using the

MBACFG utility.

Choose whether to display or hide the message the MBA displays indicating to the user which hot keys to press to enter the MBA Configuration

Screen, i.e. “Press Ctrl+Alt+B to configure…”. You may want to hide this message so users do not

DHCP

Local

Enabled

know how to change MBA options, possibly making

MBA function incorrectly in your environment.

When the message is hidden, the hot keys can still be pressed to enter the Configuration Screen. To display the message, set this option to Enabled. To hide the message, set this option to Disabled.

T ABLE 1 CONTINUED : TCP/IP C ONFIGURATION O PTIONS

Option

Name

Possible

Values

Description

Message

Timeout

Boot Failure

Prompt

Boot Failure

TFTP

Secure

Mode

Booting

Messages

Forever

Wait for

Timeout

Wait for

Key

Next Boot

Device

Reboot

Enabled

Disabled

(User

Defined)

The amount of time (in seconds) that the prompt message is displayed and waits for user input. This includes messages such as the Configuration

Message, the Local and Network Boot Messages, and the Boot Failure Prompt.

The Forever setting only applies to the Local and

Network Boot Messages. If Forever is selected, the other messages default to 3 seconds. This setting takes affect the next time the PC is booted.

If a network boot cannot be completed, choose whether MBA displays a message and then waits for the user to press a key before continuing or waits for

3 seconds before continuing. MBA continues by following the behavior specified by the Boot Failure option.

If a network boot cannot be completed, choose whether MBA will reboot the PC or allow the PC to boot from the next boot device. On a PC with a BBScompliant BIOS, the next boot device is the next device in the boot order list. On a PC that does not have a BBS-compliant BIOS, the next boot device is normally the hard disk.

Choose whether MBA uses the secure mode feature of TFTP. In secure mode, only the filename is sent to the TFTP Service.

Choose the message text and hot key that is used to instruct the user how to boot locally when the

Default Boot is set to Network, and how to boot from the network when the Default Boot is set to Local.

Not available with BIOS-integrated MBA.

TCP/IP

Image

Filename

(User

Defined)

Default filename of the boot image file if a filename is not provided in either the DHCP or BOOTP response from the server.

Default

Wait for

Timeout

Next Boot

Device

Disabled

“Press H to boot from

Hard Disk”

“Press N to boot from

Network”

MBA.IMG

T ABLE 2: PXE C ONFIGURATION O PTIONS

Option

Name

Possible

Values

Description

Default

Boot

Local Boot

Config

Message

Timeout

Boot Failure

Prompt

Network

Local

Enabled

Disabled

Enabled

Disabled

Enabled

Disabled

Forever

Wait for

Timeout

Wait for

Key

Choose whether MBA will perform a network boot or a local hard disk boot by default. If Network boot is chosen as the default, the Local Boot Message is displayed at boot time (if a bootable device exists and Local Boot is enabled). If Local boot is chosen as the default, the Network Boot message is displayed at boot time. Not available with BBS-BIOS.

Choose whether to prevent access to the

Configuration Screen that is built into the MBA ROM.

When Disabled, the Configuration Message is not displayed. Also, when disabled, the only method to modify the MBA options is by using the MBACFG utility.

Choose whether to display or hide the message the

MBA displays indicating to the user which hot keys to press to enter the MBA Configuration Screen, i.e.

“Press Ctrl+Alt+B to configure…”. You may want to hide this message so users do not know how to change MBA options, possibly making MBA function incorrectly in your environment. When the message is hidden, the hot keys can still be pressed to enter the Configuration Screen. To display the message, set this option to Enabled. To hide the message, set this option to Disabled.

The amount of time (in seconds) that the prompt message is displayed and waits for user input. This includes messages such as the Configuration

Message, the Local and Network Boot Messages, and the Boot Failure Prompt.

The Forever setting only applies to the Local and

Network Boot Messages. If Forever is selected, the other messages default to 3 seconds. This setting takes affect the next time the PC is booted.

If a network boot cannot be completed, choose whether MBA displays a message and then waits for the user to press a key before continuing or waits for

3 seconds before continuing. MBA continues by following the behavior specified by the Boot Failure option.

Default

Local

Enabled

Wait for

Timeout

T ABLE 2 CONTINUED : PXE C ONFIGURATION O PTIONS

Option

Name

Possible

Values

Description

Boot Failure

Booting

Messages

Next Boot

Device

Reboot

(User

Defined)

If a network boot cannot be completed, choose whether MBA will reboot the PC or allow the PC to boot from the next boot device. On a PC with a

BBS-compliant BIOS, the next boot device is the next device in the boot order list. On a PC that does not have a BBS-compliant BIOS, the next boot device is normally the hard disk.

Choose the message text and hot key that is used to instruct the user how to boot locally when the

Default Boot is set to Network, and how to boot from the network when the Default Boot is set to

Local. Not available with BIOS-integrated MBA.

Default

Next Boot

Device

“Press H to boot from

Hard Disk”

“Press N to boot from

Network”

T ABLE 3: N ET W ARE C ONFIGURATION O PTIONS

Option

Name

Possible

Values

Description

Protocol

Default

Boot

802.2,

802.3,

Ethernet II

Network

Local

Choose the specific frame type for NetWare boot methods.

Local Boot

Config

Enabled

Disabled

Enabled

Disabled

BIOS.

Not available with BBS-BIOS.

Choose whether to prevent access to the

Configuration Screen that is built into the MBA

ROM. When Disabled, the Configuration Message is not displayed. Also, when disabled, the only method to modify the MBA options is by using the MBACFG utility.

Default

802.3

Local

Enabled

T ABLE 3 CONTINUED : N ET W ARE C ONFIGURATION O PTIONS

Option

Name

Possible

Values

Description

Config

Message

Timeout

Boot Failure

Prompt

Boot Failure

MSD

Enabled

Disabled

Forever

Wait for

Timeout

Wait for

Key

Next Boot

Device

Reboot

Enabled

Disabled

Choose whether to display or hide the message the

MBA displays indicating to the user which hot keys to press to enter the MBA Configuration Screen, i.e.

The amount of time (in seconds) that the prompt message is displayed and waits for user input. This includes messages such as the Configuration

Message, the Local and Network Boot Messages, and the Boot Failure Prompt.

The Forever setting only applies to the Local and

Network Boot Messages. If Forever is selected, the other messages default to 3 seconds. This setting takes affect the next time the PC is booted.

If a network boot cannot be completed, choose whether MBA displays a message and then waits for the user to press a key before continuing or waits for 3 seconds before continuing. MBA continues by following the behavior specified by the Boot Failure option.

If a network boot cannot be completed, choose whether MBA will reboot the PC or allow the PC to boot from the next boot device. On a PC with a

BBS-compliant BIOS, the next boot device is the next device in the boot order list. On a PC that does not have a BBS-compliant BIOS, the next boot device is normally the hard disk.

Choose whether to use the MSD functionality to direct a PC to boot from a particular server. Refer to

“ Multiple Servers: How the MSD NLM Can Help ” for a further description on MSD.

Default

Enabled

Wait for

Timeout

Next Boot

Device

Enabled

T ABLE 3 CONTINUED : N ET W ARE C ONFIGURATION O PTIONS

Option

Name

Possible

Values

Description

Scan

BOOTCONF.

SYS

NetWare

Image

Filename

Booting

Messages

Enabled

Disabled

(User

Defined)

(User

Defined)

Choose whether MBA scans the BOOTCONF.SYS file to determine the boot image filename for the PC. If disabled, MBA uses the default boot image filename.

Default filename of the boot image file. The filename is used if no entry is found in

BOOTCONF.SYS or if the file contents in

BOOTCONF.SYS are not found. If this file is not found then NET$DOS.SYS is used. Not available with BIOS-integrated MBA.

Choose the message text and hot key that is used to instruct the user how to boot locally when the

Default Boot is set to Network, and how to boot from the network when the Default Boot is set to

Local. Not available with BIOS-integrated MBA.

Default

Enabled

NET$DOS.

SYS

“Press H to boot from

Hard Disk”

“Press N to boot from

Network”

T ABLE 4: RPL C ONFIGURATION O PTIONS

Option

Name

Possible

Values

Description

Default

Boot

Local Boot

Config

Network

Local

Enabled

Disabled

Enabled

Disabled

BIOS.

Not available with BBS-BIOS.

Choose whether to prevent access to the

Configuration Screen that is built into the MBA

ROM. When Disabled, the Configuration Message is not displayed. Also, when disabled, the only method to modify the MBA options is by using the MBACFG utility.

Default

Local

Enabled

T ABLE 4 CONTINUED : RPL C ONFIGURATION O PTIONS

Option

Name

Possible

Values

Description

Config

Message

Timeout

Boot Failure

Prompt

Boot Failure

Booting

Messages

Enabled

Disabled

Forever

Wait for

Timeout

Wait for

Key

Next Boot

Device

Reboot

(User

Defined)

Choose whether to display or hide the message the

MBA displays indicating to the user which hot keys to press to enter the MBA Configuration Screen, i.e.

The amount of time (in seconds) that the prompt message is displayed and waits for user input. This includes messages such as the Configuration

Message, the Local and Network Boot Messages, and the Boot Failure Prompt.

The Forever setting only applies to the Local and

Network Boot Messages. If Forever is selected, the other messages default to 3 seconds. This setting takes affect the next time the PC is booted.

If a network boot cannot be completed, choose whether MBA will reboot the PC or allow the PC to boot from the next boot device. On a PC with a

BBS-compliant BIOS, the next boot device is the next device in the boot order list. On a PC that does not have a BBS-compliant BIOS, the next boot device is normally the hard disk.

Choose the message text and hot key that is used to instruct the user how to boot locally when the

Default Boot is set to Network, and how to boot from the network when the Default Boot is set to

Local. Not available with BIOS-integrated MBA.

Default

Enabled

Wait for

Timeout

Next Boot

Device

“Press H to boot from

Hard Disk”

“Press N to boot from

Network”

The following startup options are available only when an MBA UNDI is used. If an

UNDI developed by another vendor is used with the MBA base code, these options are not available.

T ABLE 5: S TARTUP O PTIONS

Description Option

Name

Boot

Control

ROM MBA

Base Code

Possible

Values

Auto

Detection

Interrupt 19

Interrupt 18

BBS Boot

Order

Enabled

Disabled

Choose the method that MBA UNDI participates in the PC's booting process. All PCs have two system interrupts involved when the PC starts—Interrupt

18 (ROM BASIC/Boot Failure) and Interrupt 19

(Bootstrap Loader). Before the BBS specification was created, boot firmware such as MBA would take control of one or both of these interrupts so it would be executed during the PC boot process. With the

BBS specification, this is no longer required and the

PC's BIOS executes the boot device, such as MBA, as specified in the boot order.

Choose Auto Detection to enable MBA UNDI to detect whether the PC has a BBS-compliant BIOS. If so, BIOS executes MBA UNDI as its position in the boot order dictates. If not, MBA UNDI takes over interrupt 18 and 19 and forces its execution when the PC boots.

Choose Interrupt 18 or Interrupt 19 to have MBA take control of these settings. This may be necessary if MBA UNDI incorrectly detects that the

PC has a BBS BIOS when in fact it does not. If either of these interrupts is selected on a PC that has a BBS BIOS, the BBS boot order is ignored and the PC is always booted using MBA UNDI. MBA behavior and options are present as though the PC does not have a BBS BIOS.

Choose the BBS Boot Order setting to enable the

MBA UNDI to execute as specified in the boot order of a BBS BIOS. This may be necessary if MBA UNDI incorrectly detects that the PC does not have a BBS

BIOS when in fact it does. If this setting is selected on a PC that does not have a BBS BIOS, MBA UNDI will never be executed.

You should be familiar with the technical aspects of the PC boot process before modifying these settings.

If your MBA is integrated in a ROM on a NIC and not integrated into the BIOS, you can disable the

MBA base code. When the MBA base code is disabled and the MBA UNDI is executed (either by a

BBS BIOS or by taking control of Interrupt 18 and/or 19), the MBA UNDI tries to locate another

PXE-compatible base code (which could reside in the PC's BIOS). This allows the MBA UNDI on a specific NIC to use a base code that is different than the base code contained in the ROM.

Default

Auto

Detection

Enabled

T ABLE 5 CONTINUED : S TARTUP O PTIONS

Option

Name

Possible

Values

Description

Network

Service

Boot

Enabled

Disabled

Network Service Boot (NSB) allows the user to force a network boot when the PC is booting up regardless of the position of MBA in the BBS boot order. When this option is enabled, MBA displays the message “Press F12 to boot from network”. If the user presses F12, MBA will force a network boot. This is useful in the case where a client PC normally boots the operating system from its local hard disk, but on a specific occasion (when the user requires an operation at boot time to be performed remotely from a server) the user can press F12 to force a network boot.

On a BBS-PC, if this option is used, then MBA should not be first in the BBS Boot order. If it is, then Network Service Boot is not needed since the

PC normally boots from the network anyway.

On a non-BBS PC, this option isn’t applicable because Network booting and Local booting are controlled by the Default Boot and Local Boot options in MBA. On non-BBS PCs, this option is ignored.

Some BIOSs have their own implementation of

NSB. If these BIOSs are compliant with the System

Management BIOS (SMBIOS) Reference

Specification v2.3, they have an indication whether they have NSB functionality implemented. MBA checks for this indication and, if it indicates that

NSB is implemented by the BIOS, MBA will not perform NSB functionality. The BIOS’s NSB implementation takes precedence and MBA ignores this NSB option. In this case, you must enable or disable NSB via the BIOS’s setup screen.

If a BIOS has implemented NSB but does not have the indication (because it is not SMBIOS v2.3 compliant) then you should disable this NSB option in MBA and use the BIOS’s implementation.

Otherwise, you may get two messages that prompt the user to press F12, and the MBA and BIOS implementation may conflict if F12 is pressed.

Default

Disabled

Changing the Options

You can configure, view, and change the options in two ways:

using the MBA-based Configuration Screen that is built into the MBA base code. (Accessed by pressing Ctrl+Alt+B) It is not available if the MBA base code is disabled.

using the MBACFG utility

For security reasons, not all options are available from the MBA-based

Configuration Screen. However, all options are available to the administrator using the MBACFG utility. Both methods are described in the following sections.

Using the MBA-Based Configuration

When the MBA is executed, it displays a configuration message as follows:

“ Initializing MBA. Press Ctrl+Alt+B to configure…”

If you press the hot keys while the message is displayed, you enter the MBAbased Configuration Screen.

You can specify the amount of time that the configuration message is displayed, whether the message should not be displayed, and whether access to the MBAbased configuration should be disabled.

F IGURE 4: MBA-B ASED C ONFIGURATION S CREEN

The options that are available from the MBA-based configuration screen are:

Boot Method

Protocol

Default Boot

Local Boot

Configuration Message

Message Timeout

Boot Failure Prompt

Boot Failure

Using the MBACFG Utility

F IGURE 5: MBACFG M AIN M ENU

This utility is located on the Utility CD. When you use MBACFG, you may change

MBA options in one of the following ways:

Use MBACFG’s menus interactively

Specify options on MBACFG’s command line

Specify a configuration file that contains all the options

N O T E : If you are using Windows, MBACFG operates only in MS-DOS real mode, not from a DOS window.

MBACFG syntax

Usage: mbacfg [/x] [/i] [/sX] [@configuration file | parameter list] options:

/? - show this help

/x - reboot the PC after configuring with the new settings

/I - display ROM information

/sX - if multiple NICs with MBA are in the PC, select MBA number X in the list

When you execute MBACFG on a PC containing more than one NIC with MBA,

MBACFG will display a selection menu listing the MBAs that it finds. You can then select the MBA that you wish to configure. The selection menu will show some technical information on each MBA; such as the PCI Device and Vendor IDs, the

PCI Bus and Slot numbers, and whether the MBA resides on a NIC or is integrated into the PC BIOS. You may use this information to identify the specific MBA that you wish to select. You may also use the /s command line option to automatically select a NIC from the selection menu list.

F IGURE 6: MBACFG U TILITY S CREEN

Changing Configuration Options Using a

Configuration File

MBACFG can create a .CFG file that lists all configurable options and their possible settings supported by MBA.

The .CFG file, named MBA.CFG, is NIC-specific. The following is an example of the format of the configuration file.

To select an option, remove the comment symbol (;) at the start of the line. When the .CFG file is created, the current settings are uncommented, allowing you to use the file to easily reprogram other ROMs to the same configuration.

;Boot Method

;-----------

;Boot Method=TCP/IP

;Boot Method=NetWare

;Boot Method=RPL

;Boot Method=PXE

;NetWare Protocols

;-----------------

;Protocol=802.3

;Protocol=802.2

;Protocol=Ethernet II

;TCP/IP Protocols

;----------------

;Protocol=BOOTP

;Protocol=DHCP

;General settings

;----------------

;Boot Failure=Next BBS Device

;Boot Failure=Reboot

;Config Menu=Enabled

;Config Menu=Disabled

;Config Message=Enabled

;Config Message=Disabled

;Message Timeout=Forever

;Message Timeout=3 seconds

;Message Timeout=6 seconds

;Message Timeout=12 seconds

;Boot Failure Prompt=Wait for Timeout

;Boot Failure Prompt=Wait for Key

;Netware Options

;---------------

;MSD=Enabled

;MSD=Disabled

;Scan BOOTCONF.SYS=Enabled

;Scan BOOTCONF.SYS=Disabled

;TCP/IP options

;--------------

;TFTP Secure Mode=Disabled

;TFTP Secure Mode=Enabled

;Startup options

;---------------

;Boot Control=Auto Detection

;Boot Control=Interrupt 19

;Boot Control=Interrupt 18

;Boot Control=BBS Boot Order

;ROM MBA Base Code=Enabled

;ROM MBA Base Code=Disabled

;Network Service Boot=Disabled

;Network Service Boot=Enabled

;Text options

;------------

;Network prompt=H,Press H to boot from hard disk.

;Network prompt=N,Press N to boot from network

;Boot file name=

To use the configuration file to re-configure MBA, include the filename on the

MBACFG command line preceded by “@” as follows: mbacfg @mba.cfg

Changing Configuration Options from the

Command Line

MBA options can also be entered on the MBACFG command line, a convenience if you need to change only a few values. The option name is the same as shown in the previous sample configuration file. When typing the option on the command line, change all spaces to an underscore character, or enclose the option in quotes. For example, the default boot device could be entered as either of the following:

"default boot=network" or default_boot=network

Updating to a Newer MBA Version

As operating systems, hardware platforms, and protocols evolve, you may need to update to a newer version of MBA that supports your environment. You may also want to upgrade to take advantage of enhanced functionality or problem resolution.

If your NIC supports updateable (that is, flashable) ROMs, you can update your

ROM using the MBAFLASH utility (MBAFLASH.EXE). The MBAFLASH utility contains the MBA software within itself and will program your ROM chip with this software.

Therefore, you must obtain the MBAFLASH utility for the version of MBA that you want to program into your ROM. You can obtain the MBAFLASH utility for the latest MBA upgrades from the Argon web site at www.ArgonTechnology.com.

N O T E : If your MBA is integrated into the system BIOS you must contact your PC vendor for updates.

Command Line Options

Although you can use MBAFLASH interactively, you can also automate some of the process using command line options. This feature is helpful if you wish to use

MBAFLASH as part of a batch file. The command line options are:

Usage: mbaflash [.ROM Filename] [/?] [/p] [/b] [/0] [/sX] options:

.ROM Filename - filename of a .ROM file that you wish to program into your ROM chip instead of using the MBA version that is within MBAFLASH.EXE

/? - show this help

/p - display no prompts

/b - do not create a backup of current ROM contents

/0 - reset all MBA options to default values after updating MBA

/sX - if multiple NICs with MBA are in the PC, select MBA number X in the list

N O T E : If you are using Windows, MBAFLASH operates only in MS-DOS real mode, not from a DOS window.

If your NIC does not support updateable ROMs, you must remove the NIC from the PC and replace the ROM chip with a newer version.

When you execute MBAFLASH on a PC containing more than one NIC, MBAFLASH will display a selection menu which lists the NICs that it finds. You can then select the NIC that you wish to update with MBA software. The selection menu will show some technical information on each NIC; such as the PCI Device and Vendor IDs, the PCI Bus and Slot numbers, and the name of the NIC. You may use this information to identify the specific NIC that you wish to select. You may also use the /s command line option to automatically select a NIC from the selection menu list.

Restoring a Previously Backed-up

Version

The MBAFLASH utility contains within itself MBA software code that it programs into the ROM chip on your NIC. You can override this self-contained MBA software and instruct the MBAFLASH utility to use another version of MBA software instead.

To do this you must specify, on the command line, the filename of the .ROM file that contains the MBA software that you want the MBAFLASH utility to use; for example: mbaflash 8109401.ROM

This method is used to restore a backup version of ROM code that was created by the MBAFLASH utility. When you use the MBAFLASH utility to update your ROM, it asks you whether you wish to make a backup of the current software in your ROM before it programs your ROM with a different version. If you answer Yes to this prompt, the MBAFLASH utility creates a .ROM file that contains the backup version. If you wish to go back to the backup version, you simply run the

MBAFLASH utility and specify the backup ROM file that the MBAFLASH utility created.

Understanding .ROM File Names

MBA .ROM filenames used by the MBAFLASH utility are in the following format: xyyyzzz.ROM

Where

x is the protocol (7=Tri-protocol, 8=MBA)

yyy is the unique MBA type number corresponding to the PC's NIC

zzz is the MBA version number

C h a p t t e r 4 : : U s i i n g M B A B a s e C o d e

When you turn on your PC, the following sequence of events occur:

Your PC performs its usual initial tests and setup, such as a memory test.

MBA displays its configuration message “Initializing MBA. Press Ctrl+Alt+B to configure…”

If you press the hot key sequence while the message is displayed, you enter the MBA-based Configuration Screen where you can view or change various

MBA options, including the option to disable the display of this configuration message.

The subsequent events vary depending on whether your PC contains a BBScompliant BIOS.

With a non-BBS BIOS

If a diskette is detected in drive A:, and local boot options are enabled, drive A: is treated as the boot device without any intervention from the user. MBA removes itself from the system memory at this point.

The message: “Type H to boot from Hard disk” or “Type N to boot from

Network” appears (depending on how MBA is configured, and whether there is a hard disk present in the PC). You have a period of time (based on the

Message Timeout option) to press the appropriate key before the default boot device is selected automatically. At this point you can press any key other than H or N to tell MBA to boot from the default boot device without waiting the full time period.

If the hard disk is chosen as the boot device, MBA removes itself from the system memory. If the network is chosen as the boot device, MBA attempts to transfer the boot files from the network server and then transfer control to these boot files.

With a BBS BIOS

If “MBA UNDI” is positioned first in the boot order (refer to “ Setting the

Boot Order on PCs with BBS BIOS ” in Chapter 3), MBA attempts to transfer the boot files from the network server and then transfer control to these boot files.

If “MBA UNDI” is not positioned first in the boot order, it is executed only if the devices that preceeded MBA UNDI in the boot order fail to boot.

At this point, if MBA attempts to perform a network boot and fails, it may be because you have not set up your server to support network booting. See the appropriate chapter of this guide for your network protocol.

B o o t t F a i i l l u r r e

If network booting is unsuccessful (for example the server is down), MBA’s behavior depends on the current settings of the Boot Failure Prompt and Boot

Failure options.

Before MBA performs any action, it will check the current setting of the Boot

Failure Prompt option. If the option is set to Wait for Key, MBA will display a message indicating what the next action will be (i.e. either reboot or continue), prompt the user to press a key, and then wait for a key to be pressed. If the

option is set to Wait for Timeout, MBA will wait for 3 seconds and then perform the action.

The action MBA takes is based on the current setting of the Boot Failure option.

MBA will either reboot the PC or allow the PC to boot from the next boot device. On a PC with a BBS-compliant BIOS, the next boot device is the next device in the boot order list. On a PC that does not have a BBScompliant BIOS, the next boot device is normally the hard disk.

D i i s p l l a y i i n g V e r r b o s e S t t a t t u s I I n f f o r r m a t t i i o n

( ( v o r r C t t r r l l + A l l t t ) )

During a normal boot, MBA displays minimal information on the screen. If an error occurs during the boot process, an error message is displayed. However, if you wish to see more status information during the boot process you can set MBA to a special verbose mode.

To display more status information, press and hold the v key or Ctrl+Alt before

MBA begins to execute. On most PCs, you can do this immediately after the completion of the memory test. Release the key(s) once MBA has started to execute.

D i i s p l l a y i i n g M B A I I n f f o r r m a t t i i o n ( ( S h i i f f t t + S h i i f f t t ) )

You can have MBA display information about itself; such as internal version numbers and settings. This information is useful when reporting any problems to technical support.

To display MBA information, press and hold both Shift keys simultaneously before

MBA begins to execute. On most PCs, you can do this immediately after the completion of the memory test. MBA displays a green information screen.

F IGURE 7: MBA I NFORMATION S CREEN

T r r o u b l l e s h o o t i i n g

The following troubleshooting notes apply to all MBA environments.

Compatibility Problems with Option ROMs for Hard Disk or SCSI Controllers

If your PC's BIOS is not BBS-compatible, then compatibility problems may arise when using MBA in PCs that contain certain types of hard disk controller or SCSI controllers, specifically those that have BIOS option ROMs on board.

MBA uses the same method as the hard disk or SCSI controller to control the PC's boot process. The device that initiates this method last controls the boot process for the PC and the other device is not usable. This is not a problem for PCs with a

BBS-compatible BIOS. Selecting Interrupt 19 or Interrupt 18 boot control may solve these problems. Refer to Table 5: Startup Options for more information.

MBA Not Executing

Your MBA may not seem to be executing at all. If you do not see general MBA messages displayed on the screen such as “Managed PC Boot Agent (MBA)”, the

MBA version number, and the 3Com copyright statement, it may be because your

PC has a BBS-compliant BIOS and the MBA is not positioned properly in the boot order. Refer to “ Setting the Boot Order on PC's with BBS BIOS ” for an explanation of how to do this. You may also have the Base Code disabled. See " Table 5:

Startup Options .”

C h a p t t e r 5 : : U s i i n g P r r e O S

I I n t t r r o d u c t t i i o n

Pre-OS software, included with MBA, enables a PC to download and execute centrally-administered desktop management agents from a network server prior to actually loading the client operating system from the local hard drive. This is accomplished by the PC remotebooting using any of the MBA protocols except

RPL. After loading and executing the remote operating system, agents and other software, the PC can exit the Pre-OS boot and boot from its local hard disk.

F IGURE 8: H OW P RE -OS WORKS

Agents from the popular desktop management applications could perform a variety of tasks including:

Initial installation of the operating system and applications to the PC hard drive (including initial formatting and partitioning if required)

Scanning for and eradicating local hard disk viruses

Searching the hard disk for file system inconsistencies. If critical components are missing or damaged, they can be retrieved and replaced; alternatively, the desktop management software allows an administrator to perform a remote rescue by examining the crippled client environment and fixing it from their management console

Updating outdated drivers found on the client hard drive with newer ones located on the file server

Scanning for changes in PC hardware and software components, and logging them centrally

Once all desktop management agents complete execution the PC continues booting as usual from its local hard drive. No user awareness or intervention is required.

F IGURE 9: W HAT P RE -OS D OES

In the past, client PCs using remoteboot ROMs could boot in only one of two ways: from a server-based boot image file or from their hard drives. The Pre-OS approach is a hybrid; the centrally-booted operating system is not the ultimate operating system but rather a temporary environment created for executing management applications. Ultimately, clients exit the Pre-OS environment and continue to boot from their local hard drive. Exiting the Pre-OS environment is similar to executing a very soft Ctrl+Alt+Del where the PC continues to load the

OS on the hard disk.

This entire concept, which we call “Pre-OS managed booting”, or simply “Pre-OS”, is based on existing MBA firmware capabilities, extended by any desktop management agents contained in a special boot image file.

P r r e O S F r r a m e w o r r k

The Pre-OS framework is essentially a DOS client with optional network connectivity. The Pre-OS boot image is executed as a drive A: RAM disk residing in extended memory.

Most Pre-OS environments use a network connection to map network drives.

Regular network drivers may be loaded from the Pre-OS image, and this in no way affects the Pre-OS environment or RAM drive operation.

If any network login is needed during the Pre-OS phase, it is typically as a guest user, so that the user is not prompted to provide login name or password information.

Pre-OS desktop management agents themselves may reside either within the image, or may be executed in place from a mapped network drive.

Pre-OS environments are supported by MBA configured for: TCP/IP (BOOTP,

DHCP), PXE, or NetWare protocol configurations. RPL configurations are not supported.

PC Pre-OS Bootup Sequence

Boot image files that create a Pre-OS connection cause the PC to:

7. Load a temporary version of DOS

8. Perform the specified maintenance tasks

9. Unload DOS

10. Resume (with the PBOOT utility rather than user intervention) loading the operating system from the hard drive whatever form that operating system takes

Connection, in a way, is like booting from a floppy drive, removing the boot floppy, and then rebooting from a hard drive.

From the user's point of view, the sequence is as follows:

11. The end-user powers on or restarts the client PC.

12. A Pre-OS connection is created by the boot image file on the server. No enduser intervention or awareness is required.

13. The specified desktop maintenance applications are executed and the required actions can be taken.

14. Control is passed from the Pre-OS image to the hard drive.

15. The PC loads the end-user's operating system from the local hard drive.

16. The end-user logs into the network as usual.

C r r e a t t i i n g P r r e O S B o o t t I I m a g e s

Creating Pre-OS boot image files involves two steps very similar to creating remoteboot images:

Copying needed files onto a DOS-formatted system diskette

Taking a snapshot of this disk with the Boot Image Editor

Refer to the Boot Image Editor online help for instructions.

F IGURE 10: C REATING PRE -OS BOOT IMAGES

Boot Image Editor contains a feature that you can use to create boot image files with Pre-OS capabilities. To use this feature, select the Pre-OS checkbox in the

Options area of the appropriate Create Image File dialog box. The Boot Image

Editor utility is included with MBA. To install Boot Image Editor, see “ Boot Image

Editor Installation ” in Chapter 2 “Installing MBA.”

Another tool, PBOOT.EXE, is always used as the last file in the Pre-OS

AUTOEXEC.BAT file. PBOOT terminates (soft Ctrl+Alt+Del) the Pre-OS environment and continues booting the PC using the operating system resident on the drive C: active partition.

Defining Boot Image Content

Pre-OS Boot Image is based on a DOS boot disk. Within the Pre-OS environment you may load memory managers, network drivers, virus checkers, backup routines, software updating agents and other executables. You may also map network resources and execute any of this software from the network.

N O T E : When loading HIMEM.SYS, be sure to specify the

/TESTMEM:OFF parameter, otherwise the boot image RAM drive in extended memory may become corrupted.

Pre-OS executables may be loaded and executed from the boot image (mapped to

A: drive during boot), or they may be executed in place from a network drive, or a combination of the two. Executables loaded from drive A: have read/write access but have limited disk space available for the boot image. Executables loaded from the network usually have read-only access but have no size restrictions for disk space.

To terminate the Pre-OS image and directly boot another OS from the hard drive, the PBOOT command must be the last command in the AUTOEXEC.BAT file executing within the boot image.

The command line for PBOOT.EXE is as follows:

Usage: pboot [/nologo] options:

/nologo - to suppress the display of the large Pre-OS banner

For both TCP/IP and NetWare environments, refer to Sample Pre-OS frameworks in this chapter.

Defining NetWare Boot Image Content

For NetWare environments, you should use 16-bit NetWare clients in Pre-OS environments.

Defining TCP/IP or PXE Boot Image Content

For PCs booting from NT Server, we recommend that you use the Microsoft

Network Client Version 3.0 for MS-DOS configured for TCP/IP support. Other

DOS-based clients could be built using NFS servers and DOS client software that usually consists of TCP/IP-based TSRs and packet drivers.

Creating TCP/IP or PXE Pre-OS Boot

Images

Once you have prepared a Pre-OS diskette, use Boot Image Editor to take a snapshot of the diskette and create a Pre-OS boot image.

To specify a Pre-OS image, use the Boot Image Editor Pre-OS option. See the

Introduction section of the Boot Image Editor online help for details.

Place Pre-OS executables or agents not present within the Pre-OS image file into a network directory that is accessible to the guest username during the Pre-OS phase.

On the server, you must have either DHCP or BOOTP enabled, and also TFTP

(Trivial File Transfer Protocol).

If you are using DHCP, you must configure DHCP option 67 (Bootfile Name) to provide the image file name to MBA. If you are using DHCP in a PXE environment, you can use a BINL service to provide the boot image file name. Refer to the documentation for your DHCP or BINL server.

Creating NetWare Pre-OS Boot Images

Once you have prepared a Pre-OS bootable diskette, use Boot Image Editor to take a snapshot of the diskette and create a Pre-OS boot image on the server’s hard disk. To specify a Pre-OS image, use the Boot Image Editor Pre-OS option.

See the Introduction section of the Boot Image Editor online help for details.

Unless you've named your boot image file NET$DOS.SYS, the default NetWare boot image file name, you need to edit BOOTCONF.SYS to map a specific PC address to a given boot image file. Follow instructions provided in Chapter 8

“ Using MBA in NetWare Environments .”

S a m p l l e P r r e O S F r r a m e w o r r k s

Skeletal frameworks are provided for both TCP/IP and NetWare environments.

These samples show how to load network drivers, run Pre-OS applications, and finally, terminate the Pre-OS phase.

In the following examples, the Pre-OS framework is used to detect and correct differences in a critical file on the PC's hard drive.

TCP/IP or PXE Pre-OS Sample

CONFIG.SYS: device=himem.sys /TESTMEM:OFF device=emm386.exe noems dos=high,umb files=60 device=\net\ifshlp.sys lastdrive=z

AUTOEXEC.BAT: cd\net net initialize netbind.com umb.com tcptsr.exe tinyrfc.exe nmtsr.exe emsbfr.exe rem assumes username = "preos", password = "password", mapped drive = z: net logon preos password /savepw:no /yes rem Pre-OS agents are loaded here… fc /b c:\windows\system.dat z:\critical\systems.dat > c:\temp\compare.txt find /i "no difference encountered" c:\temp\compare.txt >nul if errorlevel 2 echo Error in string search. Cannot report if matches found. if errorlevel 1 goto CriticalFilesDifferent if errorlevel 0 goto CriticalFilesNotDifferent

:CriticalFilesDifferent echo Critical files have changed. Restoring files now… copy z:\critical\system.dat c:\windows\system.dat /v /y goto END

:CriticalFilesNotDifferent echo Critical Files intact…proceeding to local disk boot…

:END delete c:\temp\compare.txt pboot

N O T E : Access to drive z: in this example is based on mapping that drive before image file creation. Drive mappings are stored when using the MS Network Client for MS-DOS v3.0.

SYSTEM.INI:

[network] sizworkbuf=1498 filesharing=no printsharing=no autologon=yes computername=PREOS lanroot=A:\ username=PREOS workgroup=WORKGROUP reconnect=yes dospophotkey=N lmlogon=0 logondomain=WORKGROUP preferredredir=basic autostart=basic maxconnections=8

[network drivers] netcard=el90x.dos transport=tcpdrv.dos,nemm.dos devdir=A:\

LoadRMDrivers=yes

[386enh]

TimerCriticalSection=5000

UniqueDosPSP=TRUE

PSPIncrement=2

[Password Lists]

*Shares=A:\Shares.PWL

PREOS=A:\PREOS.PWL

PROTOCOL.INI:

[network.setup] version=0x3110 netcard=tcm$el90x,1,TCM$EL90X,1 transport=tcpip,TCPIP lana0=tcm$el90x,1,tcpip

[TCPIP]

NBSessions=6

SubNetMask0=255 0 0 0

IPAddress0=0 0 0 0

DisableDHCP=0

DriverName=TCPIP$

BINDINGS=TCM$EL90X

LANABASE=0

[protman]

DriverName=PROTMAN$

PRIORITY=MS$NDISHLP

[TCM$EL90X]

DriverName=el90x$

NetWare Pre-OS Sample

CONFIG.SYS: device=himem.sys /TESTMEM:OFF device=emm386.exe noems dos=high,umb files=60 buffers=20,0 lastdrive=z

AUTOEXEC.BAT: set NWLANGUAGE=English lsl.com

3c90x.com ipxodi.com vlm.exe fc /b c:\windows\system.dat f:\login\critical\systems.dat > c:\temp\compare.txt find /i "no difference encountered" c:\temp\compare.txt >nul if errorlevel 2 echo Error in string search. Cannot report if matches found. if errorlevel 1 goto CriticalFilesDifferent if errorlevel 0 goto CriticalFilesNotDifferent

:CriticalFilesDifferent echo Critical files have changed. Restoring files now… copy f:\login\critical\system.dat c:\windows\system.dat /v /y goto END

:CriticalFilesNotDifferent echo Critical Files intact…proceeding to local disk boot…

:END delete c:\temp\compare.txt pboot

NET.CFG:

Link Driver 3C90X frame ETHERNET_802.2

NetWare DOS Requester

FIRST NETWORK DRIVE = F

NETWARE PROTOCOL = NDS BIND

PREFERRED SERVER = LANTECH 1

T e c h n i i c a l l I I n f f o r r m a t t i i o n

The following specification applies to the Pre-OS phase only.

Memory requirements: Available conventional memory is reduced by 3 KB, and available extended memory is reduced by the size of the boot image.

C h a p t t e r 6 : : U s i i n g M B A i i n T C P / / I I P E n v i i r r o n m e n t t s

TCP/IP-Specific Features

Supports network booting of operating systems such as DOS and Windows from any TCP/IP network which has a BOOTP or DHCP and a TFTP service

Includes Boot Image Editor and other utilities for creating, examining, and editing boot image files on the server

Includes BPPATCH utility to insert BOOTPTAB or DHCP fields into text and batch files

Network Requirements

MBA requires that a BOOTP or DHCP Service or daemon exists on the server to provide the IP address assignment and the filename and location of the boot image file. MBA also requires a TFTP server to enable the transfer of the boot image file to the PC.

F IGURE 11: MBA IN T RADITIONAL TCP/IP E NVIRONMENTS

How MBA Works in a TCP/IP Environment

To boot the PC, the MBA ROM first sends a broadcast to all of the servers on the network to see if one of them is running a BOOTP or DHCP service and has the

required information for the PC (PC's IP address and boot image file name). The response from the server provides the PC with its IP address, the name of the boot image file and the IP address of the server that has the image file.

The PC then sends a TFTP request to the server to transfer a copy of the boot image file. This image file is stored in the PC's memory as a RAM disk. When the entire file is received, MBA passes control over to the downloaded file. The PC boots just as it would from a diskette.

After the PC has fully booted and connected to the network, the FREEMEM utility can be used to remove the boot RAM disk, and restore drive A: to the local floppy drive, if it exists.

S e t t t t i i n g U p t t h e S e r r v e r r

Before a PC can use MBA for network booting, you must set up a server to provide the PC with the information it needs.

If there are multiple servers on the network, only one of them needs to be set up for remote booting. This server must have the following services installed:

BOOTP or DHCP service

TFTP service

The BOOTP or DHCP service provides the PC with its IP address and the name of the image file to boot. The Trivial File Transfer Protocol (TFTP) service is used during the transfer of the boot file to the PC.

BOOTP Service

The BOOTP service may be included with the server TCP/IP package; check your documentation.

If you do not have the service, contact technical support for your operating system to see if it is available.

The BOOTP service uses a file (normally called BOOTPTAB) which contains information for all PCs.

This file must contain at least the IP address and boot image file name for each PC.

DHCP Service

A DHCP service may have been provided with your server software. Servers providing this MBA-compatible service include Sun Solaris, Windows NT Server,

OS/2 Warp Server, and Red Hat Linux.

TFTP Service

The boot image file is transferred to the PC using TFTP. The TFTP service should be included with your TCP/IP package, but may be disabled; see your TCP/IP documentation for information.

When setting up TFTP you should create a directory for all of the image files.

The suggested directory name is TFTPBOOT.

Creating a Boot Diskette

17. Format a diskette as a DOS system diskette.

• Copy all the files to the boot diskette that are needed to connect the PC to the network.

This must include a CONFIG.SYS and any device drivers and an

AUTOEXEC.BAT to load the required network files.

If you are mapping network directories to a local drive, the AUTOEXEC.BAT file on the diskette should transfer control to a .BAT file on the network drive.

N O T E : If you are using a memory manager see “ Using Memory

Managers ” in this chapter, as some restrictions may apply.

Here is a sample AUTOEXEC.BAT file mapping the /PUBLIC directory, on the server called TEST, to local drive E: lsl fasteth (or whatever your ODI driver is named) odipkt ethdrv idrive idmnt unix test /public e: pcnfs nobody e: init

At the end of this AUTOEXEC.BAT file, control is transferred to another .BAT file

(INIT.BAT) located on the network drive. This second .BAT file should change the

DOS COMSPEC variable so that DOS can find a copy of COMMAND.COM after the image is released from memory. The FREEMEM program is then executed to release all the memory used during booting and to restore drive A: as a local drive. FREEMEM must be run from a network drive. For additional information see

“ FREEMEM: Free RAM Disk Memory ” under “Other Tools.” set comspec = e:\dos\command.com freemem

Following FREEMEM, you may run any other commands needed to start the PC.

Once the boot diskette is created, boot the PC using this disk to confirm that it is working correctly. When you are confident the boot diskette is correct you can use it to create the image file.

When creating boot image files, it is necessary to ensure that each PC booting with MBA has a licensed copy of the operating system being used (e.g. DOS).

Creating a Boot Image File Using Boot

Image Editor

Boot Image Editor is a utility that creates a boot image file from the contents of a boot diskette. You can find Boot Image Editor on the MBA Utility Disk.

Use the procedures in “Working with Boot Image Files for TCP/IP Environments” in the Boot Image Editor online help to copy the contents of a boot diskette to a directory on a file server.

When you have created the boot image file store the boot diskette you have just created in a safe place; it may be required at a later date. The PC can now be booted using MBA.

You have now created a single boot image file that any PC with MBA can load and boot from the network (assuming the PCs are using the same type of NIC). If there are PCs on your LAN using MBA that require different boot configurations

(e.g. different NICs, different CONFIG.SYS options), you will need to create additional boot image files. If the server does not provide an image filename on the DHCP or BOOTP reply, MBA uses MBA.IMG for the default filename.

You can now reboot the PC to make sure the image file was built correctly.

Boot Screen

When booting with MBA, the PC screen looks similar to Figure 13 or 14.

If the PC does not boot correctly, see “ Troubleshooting ” at the end of this chapter.

F IGURE 12: N ORMAL TCP/IP BOOT SCREEN

F IGURE 13: V ERBOSE TCP/IP BOOT SCREEN

O t t h e r r T o o l l s

In addition to the TCP/IP-specific tools mentioned in this chapter, the MBA Utility

Disk includes other tools that help simplify the installation and use of MBA. These tools are outlined in this section.

FREEMEM: Free RAM Disk Memory

FREEMEM releases all the memory used to transfer the boot image file from the server after the PC has booted. It also changes drive A: back to the local floppy drive (drive A: is used as a RAM disk while the PC is booting from the image file).

N O T E :

Before you can use FREEMEM you must change your DOS

COMSPEC variable to a DOS directory on the network, otherwise you will get an error when DOS tries to reload

COMMAND.COM after FREEMEM terminates.

FREEMEM can not be included in the image file; it must be executed from a network drive (or local hard drive).

After using FREEMEM you should have about 2 KB less memory available than you have when you boot from the diskette used to create the image file.

BPPATCH: Supporting Replaceable

Parameters

The BPPATCH program is used to replace parameters from the BOOTP/DHCP reply packet into text files. This allows one common image file to be used by several

PCs, with the parameters unique to each PC (like the IP address) being specified in the BOOTPTAB file on the server and replaced in the image file when the PC boots.

N O T E : BPPATCH must be run before FREEMEM.

Using BPPATCH

To use BPPATCH you must first put tags into your text files (batch files, configuration files etc.) to indicate which BOOTP fields you want to replace. You then run BPPATCH and specify the files to be patched on the command line. You can specify more than one file at a time. For example if you want to patch the files

START.BAT and PCTCP.INI, your command line is: bppatch start.bat pctcp.ini

N O T E : To patch parameters for commands in your AUTOEXEC.BAT file you must place these commands in a second batch file, so you can run BPPATCH before the second batch file is executed. For example, if you put all the commands in a file called

START.BAT, your AUTOEXEC.BAT file would be as follows: bppatch start.bat start

Tags

All tags begin with the character sequence “#@” followed by a three character tag name. Following the tag name are additional # characters used to specify the tag length. The total tag length is counted from the first # character to the last # character. It is important to make the tag large enough to contain all the characters that may be in the field. If the field is smaller than the tag length, the field is padded with spaces. If the field is larger than the tag length then it is truncated.

For definitions of tags that can be used with BPPATCH, view the file BPPATCH.TXT on the MBA Utility Disk. The test file BPTEST.TXT includes all tags. Use this file as an example, and for testing BPPATCH on your system.

A p p l l i i c a t t i i o n N o t t e s

This section lists some techniques for using MBA in TCP/IP environments.

Using Memory Managers

Currently the only supported memory manager is EMM386.

EMM386

If you are using EMM386 with Windows 3.x you must add the “/y” command line option. The “/y” option allows you to specify a path for EMM386 after the PC has booted. If you try to run Windows after booting from the network you get an

“Invalid path for EMM386” message. This is because Windows needs access to the

EMM386 file and, since the PC was booted from the network, the original file is no longer available. Using the “/y” option you can specify a network path so Windows can access EMM386 from the network. For example: device=emm386.exe /y=e:\dos\emm386.exe

HIMEM.SYS

If you are using MSDOS 6.2 or higher you must use the “/TESTMEM:OFF” option with HIMEM.SYS to disable the extended memory RAM test. The resulting command line is: device=himem.sys /TESTMEM:OFF

T r r o u b l l e s h o o t i i n g

Quick Fixes: What to Check First

When things do not work, the best way to diagnose problems is to interpret MBA's

PC screen using MBA's verbose mode. See “ Displaying Verbose Status

Information ” in Chapter 4. Refer to the following section for explanations of MBA screen messages.

MBA Messages

BOOTP

DHCP

If the PC has stopped at this prompt and the progress dots (….) are increasing, it means that no reply has been received from the BOOTP or DHCP service on the server, and you should check the following:

A proper connection to the file server. Try to connect to the server if you boot from a floppy or hard drive.

(BOOTP case only) Your server is running a BOOTP service. You may want to try running the service in stand-alone mode to see if it is getting the request from the PC. The service should also have a debug mode where it displays information on the screen for each request it gets and replies to.

Transferring boot image file (x-y) (only in verbose mode)

The two numbers in the brackets, x and y, indicate retries and packet number respectively. During a normal transfer the first number, the retries, should remain at 1 and the second number, the packet number, should increase.

If the retry count is increasing but the packet number is not, it indicates the PC is not receiving any packets from the TFTP service. If the packet number remains at

1 make sure your server is running TFTP.

If both the retry count and the packet number are increasing it indicates the transfer is progressing correctly, but the PC is not receiving packets as quickly as it can process them. This normally indicates a busy network.

File Transfer Error Messages

Most file transfer errors originate at the server. Some common file transfer errors are:

File transfer error:

If you see “File transfer error” with no description, it indicates the PC received an error packet, but the sending server did not indicate what the error was.

File transfer error: File not found

This message comes from the TFTP service on the server. It means the

TFTP service could not find the file the PC requested. The full filename is displayed on the PC screen; make sure this filename is correct and that the file does exist.

File transfer error: Access violation

This message comes from the TFTP service on the server. It usually indicates the boot image file does not have world read permission. This message may also occur if you are running the TFTP service in secure mode.

C h a p t t e r 7 : : U s i i n g M B A i i n a W i i r r e d f f o r r M a n a g e m e n t t

E n v i i r r o n m e n t t U s i i n g P X E

I I n t t r r o d u c t t i i o n

MBA supports the Preboot eXecution Environment (PXE 2.x), as specified in the

Wired for Management (WfM V2.0) and Microsoft PC 98 and PC 99 guidelines. PXE software allows PCs to communicate with server-based workstation management applications, which adhere to WfM specifications, to perform such tasks as:

Software installation

Configuration

Administration

Problem diagnostics and resolution

The PCs can be normal legacy PCs (upgraded with MBA ROMs), new Managed PCs, or Net PCs.

F IGURE 14: MBA IN A W F M PXE ENVIRONMENT

How MBA Works in a Wired for Management Environment using PXE

The MBA ROM first sends a broadcast to all of the servers on the network to see if one of them is running a DHCP service and has the required information for the PC

(i.e. the PC’s IP address). The response from the DHCP service provides the PC with its IP address. Also, a Proxy DHCP service running on a Boot Server will respond to the PC with the IP address of the Boot Server.

The PC then sends a special DHCP request to the Boot Image Negotiation Layer

(BINL) service running on the Boot Server, to get the filename of the network bootstrap program. The BINL Service replies with the filename.

The PC then sends a TFTP request to the Boot Server to transfer a copy of the bootstrap file that is stored in the PC's memory as a RAM disk. When the entire file is received, MBA passes control over to the downloaded file. The bootstrap then performs the function that it was programmed to do—this may include downloading further files from the server using TFTP.

N O T E : A WfM transaction works in a manner that is similar to a traditional TCP/IP environment using DHCP, as described in

Chapter 6 . However, WfM provides a mechanism to include a separate Boot Server into the transaction. This Boot Server contains the services that provide the bootstrap filename and transfers the file to the PC. If the DHCP Service provides the filename of the bootstrap program in its initial reply then the PC will download the file through TFTP and execute it, skipping the steps that involve the DHCP proxy and BINL Services. In this case, the WfM transaction is the same as that of traditional

TCP/IP using DHCP.

Q u i i c k S e t t u p

When configured for PXE, MBA can be used in conjunction with the following products:

Remote Installation Services from Microsoft

Symantec Ghost

ON Command CCM from ON Technology

Unicenter TNG from Computer Associates International, Inc.

Altiris Express

LANClient Control Manager from IBM

Refer to the documentation for the management application for instructions regarding proper setup, configuration, and image file creation.

Boot Screen

When booting with MBA your screen looks similar to Figure 15.

F IGURE 15: PXE BOOT SCREEN

Creating a PXE Boot Image File Using

Boot Image Editor

To create a PXE boot image file using the Boot Image Editor, see “Working with

Boot Images for Wired for Management Environments” in the Boot Image Editor

online help. To install Boot Image Editor, see “ Boot Image Editor Installation ” in

Chapter 2 “Installing MBA.”

C h a p t t e r 8 : : U s i i n g M B A i i n N e t t W a r r e E n v i i r r o n m e n t t s

I I n t t r r o d u c t t i i o n

MBA has the following features when used in NetWare environments:

Supports all current versions of NetWare

Supports all current versions of DOS

Does not require RPL.NLM to be loaded on the server; boots using a native, routable protocol

Handles multiple file servers on the network; optional MSD NLM (included) directs boot requests to the correct file server and image file

Allows the selection of different boot images for each PC at boot time

Includes boot management utilities

Includes Boot Image Editor and other utilities for creating, examining, and editing boot image files on the server

Network Requirements

MBA supports all current versions of NetWare using NCP/IPX protocol and transport layers. Unlike RPL-style ROMs, MBA for NetWare communicates using native, routable NetWare protocols and does not require any NLMs to be loaded at the server to support network booting. This ensures complete compatibility with all current versions of NetWare, and Ethernet frame-type independence.

Most Ethernet versions of MBA are configurable to support 802.3, 802.2, or

Ethernet II (type-8137) frame types. For version 3.12 and higher of NetWare,

802.2 is the default frame type; older versions of NetWare default to the 802.3 frame type. Make sure the Ethernet frame type selected by MBA is also supported at the file server used to boot the PC.

F IGURE 16: MBA IN N ET W ARE E NVIRONMENTS

Q u i i c k S e t t u p

These abbreviated instructions are for those who are experienced with MBA installation in NetWare environments; refer to information presented later in this chapter for more detailed instructions.

Step 1 - Create a boot image file

18. Format a bootable diskette, and copy to it all the files needed to make a boot diskette. Alternatively, you may copy an existing boot image file and modify it using the Boot Image Editor utility (found on the MBA Utility Disk). To install

Boot Image Editor, see “ Boot Image Editor Installation ” in Chapter 2

“Installing MBA.”

• If you are using Windows 3.x and loading EMM386 in CONFIG.SYS, be sure to add the “/y=” option to define the network path where EMM386.EXE is located. If your NIC has a memory-mapped RAM region, be sure to exclude this region from your memory manager.

• In AUTOEXEC.BAT, ensure that RPLODI.COM is loaded immediately after

LSL.COM (if using the Boot Image Editor Loader option, RPLODI is not required).

• If you are supporting more than one boot image, rename AUTOEXEC.BAT to a different name, and create a new AUTOEXEC.BAT that contains only this unique

.BAT file name. This avoids problems with sharing the same AUTOEXEC.BAT in the LOGIN directory.

• In the .BAT file that invokes the network shell such as VLM.EXE or Client32, add the following statements just before VLM: set path= set comspec=x:command.com where X: is the drive letter that is later mapped to the DOS directory by the

PC. Do not place a backslash after the drive letter (X:)

Avoid explicit references to drive A: anywhere within the boot diskette.

• Using Boot Image Editor (located on the MBA Utility Disk), or Novell's

DOSGEN.EXE, create a boot image file in the SYS:LOGIN directory. If using

DOSGEN, copy the .BAT file that invokes the network shell from the diskette to the SYS:LOGIN directory.

Step 2 - Add PC information to BOOTCONF.SYS

Skip this step if all PCs are sharing the same NET$DOS.SYS boot image file:

In the SYS:LOGIN directory, either create a BOOTCONF.SYS file or edit the existing one. If using the MSD NLM option, you must use BOOTEDIT to edit

BOOTCONF.SYS. BOOTEDIT is easy to use and helps you avoid syntax and sorting problems in the BOOTCONF.SYS file.

Step 3 - Verify the PC boots correctly

19. Boot the PC, noting whether the desired file server and boot image file are being accessed.

• If the PC has problems booting, follow the detailed steps provided in the following section. If problems persist, read the “ Application Notes ” and “ Troubleshooting ” sections at the end of this chapter.

Boot Screen

When booting with MBA, your screen looks similar to Figure 17 or 18:

F IGURE 17: N ORMAL N ET W ARE BOOT SCREEN

F IGURE 18: V ERBOSE N ET W ARE BOOT SCREEN

C r r e a t t i i n g a B o o t t I I m a g e F i i l l e U s i i n g B o o t t

I I m a g e E d i i t t o r r

Step 1 - Create a boot diskette

20. Format a diskette as a DOS system diskette.

• Copy needed files to the boot diskette. Copy all required device drivers, NetWare client drivers, and any other files you would normally place on a boot diskette.

• If using EMM386 along with Windows 3.x, be sure to add the “/y=” option to define the network path where EMM386.EXE is located. For example, device=emm386.exe /y=x:\dos\v6.20\emm386.exe

If the NIC has a memory-mapped RAM region, be sure to exclude this region from your memory manager.

• When using the VLM client for your network shell, copy the Novell RPLODI.COM file onto your boot diskette, and modify your AUTOEXEC.BAT file so that RPLODI is loaded immediately after LSL. Alternatively, you may use the Loader option in

Boot Image Editor.

• Add the following SET statements to your AUTOEXEC.BAT file, just before the network shell statement: set path= set comspec=x:command.com where X: is the drive letter that is mapped to a server DOS directory during login. This ensures that COMMAND.COM will be accessed correctly while loading VLM with DOS 6.x.

• When using the VLM client for your network shell, verify that your

AUTOEXEC.BAT file on the boot disk looks similar to the following:

Comments lsl rplodi fasteth ipxodi set path= set comspec=x:command.com must be used with all odi drivers or whatever your odi driver is called f: login drive letter of first network drive

When creating boot image files, it is necessary to ensure that each PC booting with MBA has a licensed copy of the operating system being used

(for example, DOS).

Step 2 - Run Boot Image Editor

21. Create a boot image file using the Boot Image Editor. See “Working with Boot

Image Files for NetWare Environments” in the Boot Image Editor online help for details.

The boot image file created by the Boot Image Editor must be placed in the

SYS:LOGIN directory of your current server using the files contained on the boot diskette in drive A:. MBA will use the default filename NET$DOS.SYS unless another image file is specified in either BOOTCONF.SYS or the

NetWare image file name option in MBA. An MBA ROM installed on a NIC uses this file to load the operating system, network drivers, and other information needed to boot from the network.

Boot Image Editor can create an image file that is installed as a RAM disk by using the Loader option. This option transfers the entire image file into extended memory, closes the network connection, and boots the workstation from RAM drive A:. To remove the RAM disk from memory use the FREEMEM.COM utility.

• Check to make sure the boot image file exists in the SYS:LOGIN directory.

• The .BAT file that loads VLM.EXE (or NETX.EXE) must be copied from the diskette to the LOGIN directory. If not copied, you will see a “Batch File Missing” message as VLM or NETX transfers from drive A: to SYS:LOGIN but does not find the .BAT file that was running on drive A:.

F IGURE 19: C OPYING B ATCH F ILES TO THE L OGIN D IRECTORY

If you see a “Batch File Missing” message when your PC has booted, you may also need to copy AUTOEXEC.BAT into the default directory that is specified by the user's LOGIN script, or follow other steps listed under

“ Batch File Missing Messages and How To Avoid Them ” in this chapter.

• Store the boot diskette you have just generated in a safe place, as it may be required at a later date.

Boot Using MBA

The PC can now be booted using MBA. Perform the following steps as needed:

22. For multiple PCs to boot using this file, it must be flagged as shareable. When

Boot Image Editor creates an image file it automatically flags the file as shareable. If you need to set it manually (for example, if you created the image with DOSGEN), use the NetWare FLAG command: flag net$dos.sys sh (for netware 4.x and 5.x) or flag net$dos.sys s (for netware 3.x)

• If your network has more than one file server, copy the boot image file and

AUTOEXEC.BAT to each server's SYS:LOGIN directory. If you use the optional

MSD NLM, you do not need to worry about copying these files across all file servers. See “ Multiple Servers: How the MSD NLM Can Help ” in this chapter.

You have now created a single boot image file that any PC with MBA installed can load and boot from the network. If your MBA-equipped PCs have different booting requirements, there are two ways to meet these requirements:

You may use the CHKID and ROMTYPE utilities (provided with MBA) which allow you to load drivers conditionally based on node address or NIC type.

You may have to create additional boot image files if different operating systems are used. See “ Supporting Different PCs with One Boot Image ”, and “ Creating Additional Boot Image Files .”

Creating Additional Boot Image Files

It is likely that more than one boot image file will be required to suit the differing needs of the PCs on your network, especially if different operating system versions need to be supported. Supporting multiple boot images requires an understanding of three important issues:

Creating/editing the BOOTCONF.SYS boot index file

Avoiding AUTOEXEC.BAT conflicts in SYS:LOGIN

Using Boot Image Editor to create different boot images

Creating and Editing the BOOTCONF.SYS

Boot Index File

The default boot image file is NET$DOS.SYS. When you need to support more than one boot image file, you must name these files in a special boot index file called BOOTCONF.SYS.

The BOOTCONF.SYS file is an index of all the boot image file names and the network address and node address of each PC that must access those files. This file must be in the SYS:LOGIN directory.

MBA (or the MSD NLM, if loaded) scans the contents of BOOTCONF.SYS during PC boot, and if no entry is found which matches the PC's network and node address, the default boot image file is used.

The BOOTCONF.SYS file may be created and edited in the following ways:

Using the BOOTEDIT utility (provided with MBA) ensures correct syntax, offers search/sort capabilities, and other helpful features. BOOTEDIT must be used when loading the optional MSD NLM.

Using an ASCII editor (such as the MS-DOS editor, EDIT). This is recommended only in emergencies, or when BOOTCONF.SYS contains only a few entries. Avoid using EDIT when MSD is being used, because

BOOTCONF.SYS must be sorted.

Editing BOOTCONF.SYS using BOOTEDIT

BOOTEDIT is the BOOTCONF.SYS editor supplied with MBA. This editor hides all

BOOTCONF.SYS syntax requirements and offers helpful features such as searching, sorting, undo, automatic address insertion, and more. BOOTEDIT conforms to the extended BOOTCONF.SYS syntax requirements of the MSD NLM options supported by MBA.

BOOTEDIT has the following syntax:

Usage: bootedit [servername] [/mono]

If the file server name is omitted, the current file server is used. BOOTEDIT automatically detects monochrome screen modes, but this mode may be forced with the “/mono” parameter. BOOTEDIT uses the full height of a screen or window

(that is, 43 rows); the minimum required size is 80x25 characters.

When BOOTEDIT loads BOOTCONF.SYS, any errors detected in the data format are displayed and BOOTEDIT will not enter the edit mode. If any PC entries with comments over 40 characters long are found, a warning is displayed.

BOOTEDIT has a capacity of approximately 3,000 records, depending on the amount of free conventional memory.

For further information on using BOOTEDIT, refer to online help information by pressing F1 from within BOOTEDIT.

Editing BOOTCONF.SYS Using an ASCII Editor

Each line of BOOTCONF.SYS should be entered using the following format:

0x[network],[node]=[image file name] where if the network number is 1, the node address is 00A024D6055F, and the boot image filename is WRKSTN2.SYS, then the appropriate syntax is:

0x1,00a024d6055f=wrkstn2.sys

N O T E : The first character of a BOOTCONF.SYS entry is a ZERO (not the letter O). Although most node addresses are 12 digits long, you do not need to include the leading zeros.

To avoid confusion and problems related to network numbers, you should enter wild cards for the network number followed by the node address which can be obtained from the NIC. To use wildcards insert eight question marks (?) instead of the network numbers as follows:

0x????????,[node]=[image file name]

Entries in this format must be generated for each PC that needs a boot file other than the default NET$DOS.SYS.

Wild cards can also be used for the node address. This allows several workstations to use the same image file. A common use of wildcards in the node address is to use question marks for the last 6 characters of the address. This will allow all NICs

from the same manufacturer to use the same image (the first 6 characters of the node address indicate the NIC manufacturer). The placement of the wild card entries is important; they should be at the end of the file so they do not override any specified addresses. In Figure 21, all NICs that have the first 6 characters

00104B

will use SALES.SYS, except for

00104B267345, because it has its own entry above the wild card entry.

N O T E : To find the PC's node address, check the MBA boot screen or use the configuration program that comes with your NIC.

You may put comments on each line entry in BOOTCONF.SYS, as long as there is at least one space separating the boot image file name and the comment. In general, it is a good idea to keep comments reasonably short, as MBA must scan through them. Too many comments may delay the PC's boot procedure.

0x00000020,0000c0516776=image1.sys Tyler’s boot image

0x00000021,00c0f987b345=andrew.sys Andrew’s boot image

0x00000021,00000f456787=brody.sys Brody’s boot image

0x????????,00104b267345=jenn.sys Jenn’s boot image

0x????????,00104b??????=sam.sys Default image for Sam

0x????????,????????????=win.sys Default image

IGURE

20: S

AMPLE

BOOTCONF.SYS

Avoiding AUTOEXEC.BAT Conflicts in

SYS:LOGIN

When more than one boot image file exists in a server's SYS:LOGIN directory, you must take care to avoid conflicts with AUTOEXEC.BAT files. When a PC executes

VLM or NETX during its boot sequence, the remainder of the currently running

.BAT file is loaded from the SYS:LOGIN directory, not from the boot image.

The easiest way to avoid any problems is to ensure that each boot image file executes VLM or NETX from a uniquely named .BAT file, not from AUTOEXEC.BAT.

Within each boot diskette or boot image:

23. Rename the original AUTOEXEC.BAT to a unique .BAT filename.

N O T E : Using the same name as the image file helps you keep track of which boot image file a .BAT file belongs to.

• Create a new AUTOEXEC.BAT within the boot image or boot disk that invokes this uniquely named .BAT file. Refer to Figure 22.

F IGURE 21: U SING UNIQUE BATCH FILES

When VLM (or NETX) is loaded from IMAGE1.BAT in the image file, it continues executing from IMAGE1.BAT in SYS:LOGIN. Each image disk can have its own batch file name to avoid conflicts in SYS:LOGIN.

Using Boot Image Editor to Create

Additional Boot Image Files

See “Working with Multiple NetWare Boot Image Files” in the topic “Working with

Boot Image Files for NetWare Environments” in the Boot Image Editor online help.

Select a file name that helps you remember something about the contents of the image file, (for example MSDOS62.SYS). If no file extension is specified, .SYS is the default.

N O T E : We recommend using the .SYS extension for boot image files.

S e l l e c t t i i n g D i i f f f f e r r e n t t I I m a g e s a t t B o o t t T i i m e

See “Working with Multiple NetWare Boot Image Files” in the topic “Working with

Boot Image Files for NetWare Environments” in the Boot Image Editor online help for details.

N O T E : Be sure to modify the PC's entry in BOOTCONF.SYS to refer to the menu boot filename in place of the original boot image filename. If BOOTCONF.SYS is not used, name your menu boot file NET$DOS.SYS.

M u l l t t i i p l l e S e r r v e r r s : : H o w t t h e M S D N L M C a n

H e l l p

When multiple servers exist on a network, MBA must know the server from which to obtain the boot information.

To indicate which server is to be used, MBA includes an optional server NLM called

MSD (Multi Server Director). If the MSD option is enabled in the MBA configuration, MBA attempts to locate a server running the MSD NLM. If located, this server directs MBA to the proper server and image to boot from.

If a server running MSD NLM cannot be located or the MSD option is disabled,

MBA locates the nearest server and attempts to boot from that server.

Because of the random nature of finding a particular server (it depends on how busy a server is, and how quickly it responds), it is absolutely necessary that you copy all boot image files, AUTOEXEC and other .BAT files, and BOOTCONF.SYS files across all file servers in your internetwork. Failure to do so may cause MBA to occasionally issue an “Error Opening Boot File” message as it connects to a server that doesn't contain the required boot image files.

With the MSD NLM option, you can specify the file server(s) from which an MBAequipped PC will boot, and maintain boot image files only on the designated servers.

A full-featured MSD NLM is provided with MBA. This version is unrestricted and includes activity logging.

How MSD Works

At boot time, MBA-equipped PCs first broadcast a “Get nearest MSD” request. See

Figure 17. One or more file servers reply with the address of the nearest MSD

NLM. MBA then sends a request to the MSD NLM asking for the name of the server and image file. Upon receiving this request, the NLM looks for the PC's boot information in the BOOTCONF.SYS file. If a matching entry is found, MSD replies to the MBA PC with the information.

If no matching PC entry is found, MSD replies with the name of a boot image file which is specific to the PC's type of NIC (except in cases where the NODEFAULT option is used). You can obtain the ROMTYPE number from the MBA Information screen. Also see “Other Tools: ROMTYPE: Conditional Execution based on MBA

Type ” in this chapter.

If the PC receives no reply from the MSD NLM in two seconds, MBA defaults to its normal mode of operation and attempts to boot from the nearest file server.

Installing MSD

The MSD NLM is installed on a NetWare file server, although the boot image files themselves may exist on any file server in the network.

Copy the file MSD NLM from the MBA Utility Disk to the SYSTEM directory on the

SYS: volume of the server that is used to load the MSD NLM.

The MSD NLM requires the following additional Novell NLMs:

AFTER311.NLM (on NetWare 3.x servers)

CLIB.NLM (must be version 3.12 or higher)

N O T E : If you are using NetWare 3.x you must load AFTER311.NLM before MSD. CLIB.NLM is loaded automatically by MSD.

MSD is loaded using the LOAD command on the System Console on your NetWare server. You must have access to the System Console screen of the server, either directly at the server, or through RCONSOLE.

MSD Command Line Options

There are several command line parameters that can be specified when loading

MSD:

Usage: msd <msd_name> [max=] [nodefault] [log] options

[max=] - sets the maximum number of workstations which MSD will accept when processing BOOTCONF.SYS. The default number is 512. Each entry requires about 100 bytes of server memory, so the more entries you allow, the more memory MSD will require.

[nodefault] - tells MSD not to reply to any workstations that are found in the BOOTCONF.SYS file

[log] - tells MSD to create a log file of all its activities

The first parameter specifies the unique name to be assigned to this instance of

MSD; if no name is specified, MSD assumes the name of the server on which it is running.

Add a line to your server AUTOEXEC.NCF to load MSD when the server is started.

The following are examples of valid MSD command lines: load msd

Loads MSD, assumes the name of the server it is running on, and uses the default maximum number of 512 workstation entries. load msd main

Loads MSD, names it “main” and uses the default maximum number of 512 workstation entries. load msd main max=1024

Loads MSD, names it “main” and sets a maximum number of 1024 workstation entries. load msd test log max=100 nodefault

Loads MSD, names it “test”, creates a status log file, sets a maximum of 100 workstation entries, and tells MSD to use nodefault mode.

MSD may be unloaded from your server at any time with the NetWare “unload” system console command: unload msd

NODEFAULT Mode

If MSD does not find a PC entry in the BOOTCONF.SYS file, it normally responds with a boot image file name based on the MBA type code for the ROM in the PC.

This default image name has the format MSD$<type>.SYS. For example, the default image file name for a PC with an NIC which has a MBA type code of 003 would be MSD$003.SYS. This allows you to create boot image files based on the

NIC type, without adding an entry in the BOOTCONF.SYS file.

If you do not want MSD to respond with these default image filenames, use the

“NODEFAULT” command line option. In NODEFAULT Mode MSD responds to the PC with an error message instead of an image filename. This is a security feature and prevents any PC that is not defined in BOOTCONF.SYS from booting.

MSD Console Display

For a full description of the MSD console display, view the file MSD.TXT on the

MBA Utility Disk.

MSD Messages

There are several messages related to MSD operation that may appear at an MBAequipped PC.

MSD: no reply: (only in verbose mode)

The MBA ROM in the PC has broadcast a message in an attempt to communicate with MSD, but no reply was received. This message occurs only in cases where MSD is not installed on at least one server on the network, or if the server in which the MSD NLM is loaded is not currently operating.

This message may also occur within the first few minutes of the MSD NLM being loaded at a file server, as it takes several minutes for all file servers on the network to be aware of the NLM's existence.

After this message is issued, MBA defaults to its normal operation, and attempts to contact any available file server for its boot image.

MSD: [msdname] Found server <servername>:

This message appears at the PC during normal operation, and indicates the name of the MSD NLM that serviced the request, and the name of the file server from which the boot image file is retrieved.

MSD: [msdname] Server <servername> is unavailable:

This message appears at the PC if MSD is unable to locate the file server that was specified in the BOOTCONF.SYS entry defined for the PC.

After this message is issued, MBA in the PC defaults to its normal operation and attempts to contact any available file server for its boot image. When a file server is finally reached, MBA attempts to open the filename specified for its PC in BOOTCONF.SYS; if this fails, MBA attempts to open the default boot image file, NET$DOS.SYS.

A p p l l i i c a t t i i o n N o t t e s

This section lists some techniques for using MBA in NetWare environments:

Using Novell's Client 32 for DOS/Windows with MBA

Proceed as follows when using Novell's 32-bit client for DOS/Windows (updated information may be available from Argon or 3Com):

When loading Windows 3.x, NIOS.EXE attempts to reload itself from the default boot drive. In MBA's case, this is drive A:, and since the boot image no longer exists, an error message is displayed, preventing Windows from loading in enhanced mode. Unlike EMM386, NIOS does not support an optional path parameter to facilitate the reload process. One solution is to map a network drive containing NIOS.EXE to drive A:, which would allow

Windows to load.

Formatting Diskettes Using Windows

When you boot with MBA, Windows does not allow you to format a diskette in drive A:; if you try, the message, “Cannot format the MS-DOS startup drive” appears. As a preventive measure, Windows does not allow you to format a diskette in the drive from which you booted.

The easiest way to format a diskette is in a DOS box. If you want to format a bootable diskette with system tracks, you need a diskette with a copy of DOS on it. The format program prompts you to insert this diskette so it can copy the system tracks from it.

Transferring From the Boot Image to

SYS:LOGIN

This section describes the interactions between VLM (or NETX) and MBA, and how it affects .BAT file execution.

When you execute VLM from image disk, you are normally doing so from within a

.BAT file such as AUTOEXEC.BAT. DOS sees this .BAT file as a text file containing command lines of variable length. After reading a command line from the .BAT file, DOS remembers the starting position (or file offset) of the next line in the file.

After completing execution of the current command line, execution in the .BAT file continues at the previously retained offset.

When you execute VLM (or NETX) from the image disk batch file, VLM senses that

MBA was used to boot the PC, and tells MBA to clean up. After MBA does some housekeeping and removes itself from memory, the image file is closed, and drive

A: is restored. VLM (or NETX) then transfers control to the same .BAT file in

SYS:LOGIN, at the point where it left off in the image disk. In this guide, this is called the “VLM Transfer Point”. Understanding this transfer point is important in solving problems with missing batch files, and in supporting more than one boot image file in the SYS:LOGIN directory.

T r r o u b l l e s h o o t i i n g

Quick Fixes: What to Check First

When things do not work, check the following situations to resolve the most likely problems:

If you are not using the Boot Image Editor Loader option, check that

RPLODI is loaded after LSL.COM and before the ODI driver. If RPLODI is not loaded, the boot image hangs while loading the ODI driver, or shortly afterwards.

Check that the Ethernet frame type configured in MBA is the frame type that is loaded at the file server.

Within an image file, check for explicit references to drive A: within any pathname; avoid explicit drive A: references.

DOS 6.x sets COMSPEC to A:\COMMAND.COM, and may set PATH to A:\.

Just before loading VLM, clear PATH and change the COMSPEC variable to the DOS search drive that is established after login, as follows: set path= set comspec=x:command.com vlm

If the PC hangs at the “Jumping to Boot Record” message, it could be one of the following:

8 The diskette you used to create the boot image file was infected with a boot sector virus. Check the original diskette, or use Boot Image Editor to map the image to drive A: and scan for virus infections.

8 When the “invalid path for EMM386” error message is displayed while loading Windows 3.x, add the “/y” parameter to the EMM386 command line in the boot image file to define the network path where EMM386.EXE is located. For example, device = emm386.exe /y=x:\dos\v6.22\emm386.exe

MBA Messages

This section describes all of the MBA for NetWare generic messages. There may be other error messages specific to your version of MBA.

MSD: no reply (only in verbose mode)

This is not an error message, but merely an indication that MBA could not locate the optional MSD NLM on your network. See “ Multiple Servers: How the MSD NLM

Can Help ” for further information.

File server could not be found

The file server is either down or not responding to connection requests. Check that your PC is connected to an active network cable segment.

Error opening boot file

The main reason why this message could appear is that you have more than one file server on your network, and some of them do not have the needed boot files in their SYS:LOGIN directories. See “ Multiple Servers: How the MSD NLM Can

Help ” for further information.

It is also possible that the file exists, but it is open and locked by another PC.

Check that the file exists and is flagged as shareable. Load the MONITOR NLM on the file server console to check if the file is in use by another connection.

Another reason could be that you've run DOSGEN to generate your boot image file

(NET$DOS.SYS or equivalent), but you generated this file in the SYS:SYSTEM directory. All boot image files need to be in the SYS:LOGIN directory.

Error reading boot diskette file

An error occurred while reading the boot image file. This problem is usually a hardware-related difficulty or a virus infection that caused the read to fail after many retries, and earlier error messages. If other messages were displayed, refer to their explanation for suggestions on what the problem could be.

Rx2 (only in verbose mode)

This message may appear when in the verbose mode during the boot process on a heavily congested network. There is no cause for alarm if you see several of these messages in a row, but if many of them appear consecutively, it usually indicates a network problem.

Rx2 indicates that MBA timed out while waiting for a packet. If you have an

Ethernet version of MBA, this message may appear continuously, indicating that the Ethernet frame type MBA is using to communicate is not supported at the server.

With some ODI drivers, you may see Rx2 messages if you have forgotten to load

RPLODI before loading the ODI driver; check that RPLODI.COM is being loaded. In other cases, Rx2 may appear, indicating an improper network cable connection.

“<”, “>”

The “>” and “<” messages appear only after IPXODI.COM (or your board-specific

ODI driver) has loaded, but before VLM or NETX has finished loading. The “>” indicates that the IPX layer had problems transmitting data on the network, while the “<” indicates that there was a problem with receiving data from IPX. Since

MBA has managed to get this far in the boot sequence, it is usually a configuration mismatch between your NIC and IPX that is causing the problem.

There are several reasons why the “>” message could appear: either you have loaded the wrong ODI driver (perhaps for a different NIC), or the driver you have loaded does not match your NIC's configuration. If the version of MBA you are using does not use interrupts, check that the NIC's interrupt jumper is set to that expected by the ODI driver.

If the “<” message appears repeatedly on an Ethernet PC, it is likely that the

Ethernet frame type for which the ODI driver is configured is not loaded at the server.

Batch File Missing Messages and How to

Avoid Them

A cause of the “Batch file missing” message is a user login script which changes the mapping of the first network drive from the SYS:LOGIN to some other directory. You can avoid this problem by leaving the first network drive mapped to

SYS:LOGIN throughout the entire LOGIN script.

The LOGIN script supports a command called EXIT, which can be used to run a

.BAT file upon exiting from the LOGIN script. If you are running the LOGIN command from a .BAT file in SYS:LOGIN, and there are further command lines in this file, then you EXIT from your login script with a .BAT file specified, the remainder of the SYS:LOGIN .BAT file is processed and only then is your EXIT

.BAT file processed.

C h a p t t e r 9 : : U s i i n g M B A i i n R e m o t t e P r r o g r r a m L o a d

E n v i i r r o n m e n t t s

I I n t t r r o d u c t t i i o n

Remote Program Load (RPL) is a protocol originally defined by IBM that allows PCs to start by downloading files from a file server.

Servers that support the RPL boot protocol include:

IBM LAN Server

IBM Warp Server

N O T E : The RPL protocol within MBA does not support the Novell

NetWare RPL protocol. NetWare users should use MBA for

NetWare.

Throughout this chapter, information is provided for using MBA in Microsoft NT

Server environments, the most popular RPL server. For information on other RPL servers, refer to documentation provided by the server vendor.

RPL-Specific Features

Supports remoteboot of DOS, Windows 9x and OS/2 (network operating system dependent)

IGURE

22: MBA

RPL E

NVIRONMENTS

Q u i i c k S e t t u p

Because of the diversity and complexity of RPL environments, we are unable to provide brief instructions in this guide. Instead, see the file NTRPL.TXT on the MBA

Utility Disk. This file contains abbreviated instructions for those who are experienced with MBA installation in NT server RPL environments. For more detailed instructions, refer to information presented later in this chapter.

T r r o u b l l e s h o o t i i n g

When things do not work, check these situations to resolve the most likely problems:

Unknown Client NIC ID

If an “unknown client NIC ID” line appears within the NT Server Remoteboot

Manger console while attempting a PC boot, it indicates the PC’s prefix

(VendorName) is not defined. Use the following example to define the prefix. The

VendorName field is a unique six-digit value assigned to the NIC vendor; this value is the most significant six digits of the NIC’s Ethernet address.

Even though it appears a valid VendorName exists for your NIC, it may be that you have a newer NIC that had a different VendorName value. To correct this problem, create a new remoteboot configuration or add the NIC to an existing

profile as outlined in the Windows NT Server Installation Guide. Follow the example and add the new six-digit prefix to the VendorName parameter.

You must use the RPLCMD utility to add the new VendorName (the first six digits of the NIC’s node ID) to the NIC’s profile. The following example demonstrates how to add the new VendorName to an existing profile and assumes that

VendorName is 002F00. Enter the correct VendorName for your NIC. c:\winnt\rpl> rplcmd adapter boot config profile service vendor wksta [quit}: b add del enum: a bootname=dosh vendorname=002f00 bbcfile=bblock\netbeui\feth\dosbb.cnf bootcomment= abc fastethernet windowsize=0

Searching for DLC RPL Server, retries=nnnnnn

If you see the PC screen stopping at this message and the retry count is increasing, it indicates that MBA cannot find an active NT server running the

Remoteboot Service.

Check the following:

Does a proper connection to a file server exist?

Is at least one server running the Remoteboot Service?

Is the NT Server RPL service rejecting PC requests because the RPL service does not support the NIC you are using? See “ Unknown Client

NIC id ” in this section.

Is there a Remoteboot Manager console for an existing PC entry for the

NIC? If one does not exist, refresh the screen (View Refresh) to see if the NIC’s RPL broadcast was received.

Is there a Remoteboot Service error in the Event Viewer log?

Are there routers between the server and the PC? Routers between the server and the PC will cause problems because the RPL protocol is not routable

NDIS Drivers Require More Memory to Load

After the NDIS driver is loaded, you may see the following message:

The program below needs more memory XX K (NDIS driver name)

The workstation failed to boot where XX indicates the amount of additional memory (in kilobytes) needed.

In the DOSBB.CNF file, the second parameter of a DRV entry specifies the amount of additional memory to allocate to the driver. For example, if the original NDIS DRV entry is: drv bblock\ndis\feth.dos ~ ~ ~ and the boot block reports that 5 KB of additional memory is needed, change the entry to: drv bblock\ndis\feth.dos ~ 5 ~

Boot Block Fails to Load DOS

After RPLBIND1 and RPLBIND2 are executed, the boot block prints the following message:

Non-system disk or disk error Replace and press any key when ready

The message is printed when the boot block fails to load DOS from the server. Check that the DOS system files are copied correctly to:

\\%systemroot%\rpl\rplfiles\binfiles\dosxxx.

Make sure the attributes HIDDEN and SYSTEM are removed from the files,

IO.SYS and MSDOS.SYS. If you are using IBM PC-DOS, rename

IBMBIO.COM and IBMDOS.COM to IO.SYS and MSDOS.SYS.

A p p e n d i i x A : : T e c h n i i c a l l S u p p o r r t t

O n l l i i n e T e c h n i i c a l l S e r r v i i c e s

Argon Technology Web Site

Access the latest information on remote booting and PC management from the

Argon Technology web site: http://www.ArgonTechnology.com/

This site provides access to information on our Argon Managed PC Boot Agent and

Pre-OS technology, along with other Argon products. Additionally, there are a number of information sources detailing current support issues and tips for utilizing MBA technology.

Support from Your Distributor sIf additional assistance is required, contact your distributor. Many distributors are qualified to provide at least a minimum level of support for Argon products.

When you contact your network supplier for assistance, have the following information ready:

Product model name, part number, and serial number

A list of system hardware and software, including revision levels

Error messages

Details about recent configuration changes, if applicable

If you are unable to contact your distributor, see the section below on how to contact Argon.

Support from Argon

If you are unable to obtain assistance from the Argon online technical resources or from your distributor, Argon offers technical support through e-mail. Because of the possibly large amount of technical detail required to resolve a support issue, e-mail is the preferred vehicle for providing technical support.

• By E-mail: [email protected]

When you contact Argon for assistance, have the following information ready:

In all cases:

1) A detailed description of the problem, including any error messages given on client or server.

2) An indication of where in the boot process that the error occurred.

3) A description of the ROM and the ROM label, including version and date.

4) A description of the network environment and configuration from server to workstation, including all hardware used establishing connectivity between the two.

5) A description of the client PC involved, with the following (if possible):

- PC model and mfg.

- Motherboard model and mfg. speed

- BIOS version and mfg.

- System memory present

NetWare:

1) A copy of the image file in question, preferably compressed and attached to e-mail. If it is not possible to send the image file, send copies of CONFIG.SYS, AUTOEXEC.BAT, NET.CFG, and any other batch files called during boot.

2) A compressed BOOTCONF.SYS (from the LOGIN directory) attached to e-mail. This is preferred to sending it as a fax or within the contents of the e-mail, as this will not indicate embedded CRLF(s),

512 byte boundaries, etc.

3) The settings used on the ROM (protocol, etc.)

4) The settings on the server - version of NetWare, Service Patch level, network adapter cards (NICs), frame types, and network numbers assigned to each NIC.

TCP/IP:

1) A copy of the image file in question, preferably compressed and attached to e-mail. If it is not possible to send the image file, send copies of CONFIG.SYS, AUTOEXEC.BAT, and any other batch files called during boot.

2) A) If using the BOOTP protocol, a copy of the BOOTPTAB file, preferably compressed and attached to e-mail.

B) If using the DHCP protocol, the scope, scope range, lease duration, properties of reserved leases (used for static assignment of IP address), options (tags) used (particularly #67) and their values. Specify whether the options were assigned as default,

scope, and / or global settings.

C) If using the PXE protocol, and not using the DHCP service to provide the filename of the bootstrap program in its initial reply, please provide configuration details of the proxy DHCP and BINL service being used on the Boot Server. If a workstation management application is in use, refer to the vendor documentation for instructions and support regarding proper setup, configuration and image file creation.

3) Copies of all TFTP log files (if available) compressed and attached to e-mail. If TFTP has not generated log files, enable logging, recreate the problem and send the log file results. Describe TFTP settings: if transmit is set to secure or non-secure, the full path to image files used, etc. Indicate the name and version of the TFTP server used.

4) The version and service pack level of the server being used. In addition, please provide the IP address (of each NIC), subnet mask, and services/daemons running at the time of failure. A list of NT services can be obtained by running the command NET START and redirecting the command output to a text file. UNIX daemons can be listed by running PS -AUX and redirecting the output.

RPL (NT Remoteboot Service):

If the end user has an unsupported NIC (i.e. there is no boot block and configuration record for the adapter), then refer to "Creating

Remoteboot Configurations for New Adapters" in Chapter 15,

Networking Guide, Windows NT 4.0 Resource Kit or Chapter 8,

Installation Guide, Windows NT 3.5x manuals.

If attempts have already been made to configure the adapter using the above resources, or if the adapter is one of those already supported by the Remoteboot service, then provide the following:

1) From a command prompt, path to \%SYSTEMROOT%\RPL . Run the following command and send the results: DIR /S >

RPLDIR.TXT

. This is needed to check for path naming inconsistencies in boot block and configuration records.

2) Open up a command prompt. Edit the properties of the window so that the screen buffer size height attribute is 500 lines or more.

Run RPLCMD.

3) Type "b" (boot block), "e" (enumerate), "2" (level of detail). Let it scroll. Scroll back up the start of the output and select, copy and paste the output to a text file.

4) From the same command prompt, Type "c" (configuration), "e"

(enumerate), "2" (level of detail). Let it scroll. Scroll back up the start of the output and select, copy and paste the output to a text file.

5) The NIC specific DOSBB.CNF and PROTOCOL.INI, found in the

\%SYSTEMROOT%\RPL\NETBEUI\NAME_OF_NDIS_DRIVER\ directory, compressed and attached to e-mail.

A r r g o n S o f f t t w a r r e L i i c e n s e A g r r e e m e n t t

I M P O R T A N T : : Read before using this product

ARGON TECHNOLOGY CORPORATION

END USER SOFTWARE LICENSE AGREEMENT

YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS

BEFORE USING THIS PRODUCT. IT CONTAINS SOFTWARE, THE USE OF WHICH

IS LICENSED BY ARGON TECHNOLOGY CORPORATION (ARGON) TO ITS

CUSTOMERS FOR THEIR USE ONLY AS SET FORTH BELOW. IF YOU DO NOT

AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT USE THE

SOFTWARE AND PROMPTLY RETURN IT TO ARGON AND YOUR MONEY WILL BE

REFUNDED. USING ANY PART OF THE SOFTWARE INDICATES THAT YOU ACCEPT

THESE TERMS.

GRANT OF LICENSE : In consideration of the payment of the license fee, which is part of the price you paid for this product, and your agreement to abide by the terms and conditions of this License

Agreement, ARGON grants to you a non-exclusive, revocable, personal, non-transferable license and right to use (the “ License ”) this copy of the accompanying software program(s) (the " Software ") subject to the terms and restrictions set forth in this License

Agreement.

(a) If you purchased an Argon Flash chip (Boot ROM), then the Software is licensed to be installed and used by you on either a single workstation or network server owned by or leased to you, provided that the Software is used only in connection with the Argon Flash Chip (Boot ROM) provided, and is used by only a single user on a single computer at one time.

(b) If you purchased the Argon PXE/MBA on Disk , then the Software is licensed to be used by you on either a single workstation or network server owned by or leased to you, provided that the Software is used only in connection with the Argon PXE/MBA on Disk provided, and is used by only a single user on a single computer at any one time.

2. RESTRICTIONS ON USE: You are not permitted to lease, rent, license, transfer, assign, distribute or sublicense, or otherwise provide access to the Software (including, without limitation, through internet/intranet/extranet website or via other electronic communication distribution methods) or any printed material, or to use the Software in any manner, in whole or in part, on a temporary or permanent basis, except as otherwise provided in this License

Agreement, or use the Software in any unauthorized or unlawful manner whatsoever. You may not reproduce, transmit, modify, adapt or translate the Software or any printed materials, in whole or in part.

You may not alter, remove or cover proprietary notices in or on the

Software or any printed materials. Modification, reverse engineering, reverse compiling, or disassembly of the Software, or the creation of derivative works based on the Software is expressly prohibited.

(However, if you are a European Community (" EC ") resident, information necessary to achieve interoperability of the Software with other programs within the meaning of the EC Directive on the Legal

Protection of Computer Programs is available to you from ARGON upon written request.)

COPIES OF SOFTWARE: You may reproduce and provide one (1) copy of the Software and supporting documentation for each such workstation or network server on which the Software is used as permitted hereunder. Otherwise, the Software and supporting documentation may be copied only as essential for backup or archive purposes in support of your use of the Software as permitted hereunder. You must reproduce and include all copyright notices and any other proprietary rights notices appearing on the Software and the supporting documentation on any copies that you make.

4. OWNERSHIP OF SOFTWARE : ARGON owns and retains all right, title and interest, including all copyrights, patents, trade secrets, trademarks and other intellectual property rights (whether or not patentable or registerable under copyright, trademark, or similar legislation or subject to analogous protection) in and to the Software, including without limitation all software and associated media, enhancements, improvements, corrections and/or modifications to the

Software, as well as all related printed materials with this product.

Argon does not sell any rights in the Software, and reserves all rights with respect to the Software not expressly granted by this License

Agreement. Further, no license is granted to you in the human readable code of the Software (source code).

5. TRADE SECRETS: You acknowledge and agree that the structure, sequence and organization of the Software are the valuable trade secrets of ARGON and its suppliers. You agree to hold such trade secrets in confidence.

6. NO ASSIGNMENT : You may not transfer or assign the Software and/or this License Agreement to another party without the prior written consent of ARGON. If such consent is given and you transfer or assign the Software and/or this License Agreement, then you must at the same time either transfer any copies of the Software as well as the supporting documentation to the same party or destroy any such

materials not transferred. Except as set forth above, you may not transfer or assign the Software or your rights under this License

Agreement.

7. EXPORT RESTRICTIONS : The Software and all printed materials are subject at all times to all applicable export control laws and regulations in force from time to time. You agree that you will not export or re-export the Software or accompanying documentation (or any copies thereof) or any products utilizing the Software or such documentation in violation of any applicable laws or regulations of the

United States, Canada or the country in which you obtained them, as applicable from time to time.

8. UNITED STATES GOVERNMENT LEGEND: All technical data and computer software is commercial in nature and developed solely at private expense. The Software is delivered as Commercial Computer

Software as defined in DFARS 252.227-7014 (June 1995) or as a commercial item as defined in FAR 2.101(a) and as such is provided with only such rights as are provided in this License Agreement, which is ARGON's standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR 252.227-

7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion of any legend provided on any licensed program or documentation delivered to you under this License Agreement.

9. TERM AND TERMINATION : This License will expire fifty (50) years from the date that you first use the Software, if it is not earlier terminated. ARGON may terminate this License Agreement for any reason on 30 days prior notice to you. You may terminate it at any time by destroying the Software and documentation together with all copies of the Software in any form and providing Argon with a sworn declaration that all copies of the Software have been destroyed, or you may return the Software with notification of termination of this License

Agreement. This License Agreement will terminate immediately if you fail to comply with any term or condition of this License Agreement, and you agree to immediately cease using the Software and to return all copies of the Software and documentation immediately to ARGON.

The ownership of the Software, and the limited liability and indemnity provisions of this License Agreement shall continue in full force and effect after any termination of this License Agreement.

10. LIMITED WARRANTY : ARGON warrants to you that the storage media on which the Software is recorded is free from defects in

materials and workmanship under normal use and service for a period of thirty (30) days from the date of delivery to you as evidenced by the invoice. If such a defect exists, you may return the entire package, including packaging, postage prepaid with a copy of the invoice to

ARGON at the address listed below. ARGON may, at its option, (a) return the purchase price, or (b) replace the media. If failure of the media has resulted from accident, abuse, or misapplication, ARGON shall have no responsibility whatsoever to refund the purchase price or replace the media. In the event of replacement of the media, the replacement media will be warranted for the remainder of the original warranty period or fifteen (15) days, whichever is longer. This remedy is your exclusive remedy for a breach of this warranty, and ARGON’s entire liability and only warranty made with respect to the Software and printed materials. This limited warranty gives you specific legal rights, and you may have other rights which vary from jurisdiction to jurisdiction.

11. LIMITATION ON LIABILITY: OTHER THAN AS PROVIDED IN

SECTION 10 ABOVE AND TO THE MAXIMUM EXTENT PERMITTED BY

APPLICABLE LAWS, THE SOFTWARE AND PRINTED MATERIALS ARE

PROVIDED “AS IS” WITHOUT ANY WARRANTY OR CONDITION OF ANY

KIND, EITHER EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE,

INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OR

CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR

PURPOSE. SOME JURISDICTIONS DO NOT ALLOW LIMITATIONS ON

DURATION OF AN IMPLIED WARRANTY, SO THE ABOVE LIMITATION MAY

NOT APPLY TO THE LICENCEE. NO ORAL OR WRITTEN INFORMATION OR

ADVICE GIVEN BY ARGON, ITS DEALERS, DISTRIBUTORS, AGENTS OR

EMPLOYEES (COLLECTIVELY, “AGENTS”) SHALL CREATE A WARRANTY OR

IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY. YOU ASSUME THE

ENTIRE RISK AS TO THE USE AND

PERFORMANCE OF THE SOFTWARE OR

PRINTED MATERIALS IN TERMS OF CORRECTNESS, ACCURACY,

RELIABILITY, CURRENTNESS, OR OTHERWISE. IN NO EVENT SHALL

ARGON, ITS AGENTS OR ANYONE ELSE WHO HAS BEEN INVOLVED IN

THE CREATION, PRODUCTION OR DELIVERY OF THE SOFTWARE

AND/OR PRINTED MATERIALS BE LIABLE TO YOU OR ANY OTHER

PERSON FOR ANY DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL OR

INCIDENTAL DAMAGES (INCLUDING WITHOUT LIMITATION, DAMAGES

FOR LOSS OF REVENUES OR PROFITS, BUSINESS INTERRUPTION,

LOSS OF BUSINESS INFORMATION, AND THE LIKE) ARISING OUT OF

THE USE OR INABILITY TO USE THE SOFTWARE EVEN IF ARGON OR

ITS AGENTS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE OR CLAIM, OR IT IS FORESEEABLE. BECAUSE SOME

JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF

LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE

ABOVE LIMITATION MAY NOT APPLY TO YOU. IN NO EVENT SHALL

ARGON'S MAXIMUM AGGREGATE LIABILITY TO YOU EXCEED THE

AMOUNT PAID BY YOU FOR THE SOFTWARE AND PRINTED

MATERIALS. THE LIMITATIONS OF THIS SECTION SHALL APPLY

WHETHER OR NOT THE ALLEGED BREACH OR DEFAULT IS A BREACH

OF A FUNDAMENTAL CONDITION OR TERM.

12. INDEMNITY: You agree to indemnify and hold ARGON harmless from and against any loss, liability, cost, expense or damage arising out of any claim, suit, action, or judgment brought against ARGON or its directors, officers, employees, shareholders or agents related to any violation by you of any provincial, state, federal or other laws or regulations or any third party rights.

13. GOVERNING LAW . This License Agreement shall be governed by and construed in accordance with the laws of the Province of Ontario and the laws of Canada, as applicable. Each of the parties hereby irrevocably attorns to the exclusive jurisdiction of the courts of the province of Ontario without regard to conflicts of laws principles. The parties exclude in its entirety the application to this License Agreement of the United Nations Convention on Contracts for the International

Sale of Goods.

14. SEVERABILITY : In the event any provision of this License

Agreement is found to be invalid, illegal or unenforceable, such provisions shall be deemed severed from this License Agreement, and the validity, legality and enforceability of any of the remaining provisions shall not in any way be affected or impaired, and a valid, legal and enforceable provision of similar intent and economic impact shall be substituted therefore.

15. SUCCESSORS : This License Agreement and all terms and conditions contained herein shall inure to the benefit of, and shall be binding upon your heirs, administrators, successors or permitted assigns, and to Argon’s successors and assigns.

16. ENTIRE AGREEMENT : This License Agreement sets forth the entire understanding and agreement between you and ARGON, supersedes all prior or other agreements, whether written or oral, with respect to the Software, and may be amended only by a written agreement signed by both parties.

* ARGON and ARGON TECHNOLOGY are trademarks of Argon

Technology Corporation.

ARGON TECHNOLOGY CORPORATION

7895 Tranmere Drive, Suite 201A

Mississauga, Ontario

L5S-1V9 Canada www.ArgonTechnology.com

G l l o s s a r r y

This section briefly describes some of the terms used when working with preboot technology. Information in this section was supplied through the following sources:

PXE Specification 2.0 December 1998 by Intel Corporation with special contribution from SystemSoft

WfM 1.0, 1.1, 2.0 Summary and Review 1997, 1998 for 3Com Corporation /

Lanworks, Intel, Microsoft, ACER, Adaptec, AMI, Bay Networks, Compaq,

Computer Associates, Dell, FUJITSU / ICL, HP, IBM / Tivoli, Inference, Magic

Solutions, Mylex, NEC, Novell, Phoenix Technologies, Royal Blue, SCO, SNI,

Standard Microsystems, SUN, SYMBIOS, SystemSoft, Texas Instruments,

Toshiba, Vantive.

ACPI

Advanced Configuration and Power Interface; an interface between the OS and the hardware and BIOS designed to achieve independence between the hardware and the software.

API

Application Programming Interface.

Asset management

The process of maximizing the use of assets to produce revenue while minimizing their overall costs. Manageable systems contribute to asset management by capturing inventory and tracking information, which enables organizations to analyze key cost variables of their technology purchases. The data gathered by manageable systems can assist asset management issues such as inventory, consolidating and rationalizing license issues, leasing considerations, analyzing training costs, analyzing software upgrades for volume purchasing plans, evaluating the costefficiency of outsourcing, and improving warranty usage.

BAID

Acronym for a BIOS Aware IPL Device. The BIOS contains all code required to IPL from the device.

Base Memory

The first 640KB of memory in the system.

BINL

Boot Intervention Network Layer; extended DHCP service.

BIOS

Acronym for Basic Input/Output System, also known as ROM BIOS when resident in Read Only Memory or ROM. Resident on a PC’s motherboard and provides functionality and interfaces for the PC’s system hardware. Also performs PC’s basic booting functionality when the PC is powered up.

BOOTP

This is an earlier IETF-defined booting protocol that is much less flexible than DHCP. However, DHCP has been defined to be upwardly compatible with BOOTP and both these protocols can co-exist and function simultaneously in the same network. RFC 1534 defines how DHCP and

BOOTP must be implemented to ensure they can co-exist in the same network and inter-operate

BUSD Bus/Device

A BUSD option ROM may contain code to locate and initialize devices on a bus that is not supported in the BIOS Core. The BUSD API calls are used by the UNDI IPL routine and NBPs to enable and disable bus components and devices.

Common Information Model (CIM)

An object-oriented schema defined by the DMTF. CIM is an information model that provides a common way to describe and share management information enterprise-wide. It serves as the management information schema for WBEM, along with other specifications to be defined. CIM is designed to be extended for each management environment in which it is used.

DDIM

Device Driver Initialization Model. Under this model, all Option ROMs installed in a Plug and Play system which indicate that they support DDIM will be copied into RAM by the System BIOS. Documented in the [PnP] specification.

Desktop Management Interface (DMI)

A platform management information framework, built by the DMTF, designed to provide manageability for desktop and server computing platforms by providing an interface that is:

• Independent of any specific desktop operating system, network operating system, network protocol, management protocol, processor, or hardware platform.

• Easy for vendors to implement.

• Easily mapped to higher-level protocols.

Desktop Management Task Force (DMTF)

The DMTF is a standards organization comprised of companies from all areas of the computer industry. Its purpose is to create the standards and infrastructure for cost-effective management of PC systems. DHCP Dynamic

Host Configuration Protocol; used to get information from the configuration

server DMI compliance The DMTF owns the responsibility for the definition of DMI 2.0 compliance

DHCP

Dynamic Host Configuration Protocol. Used to get information from the configuration server. An industry standard Internet protocol defined by the

IETF. DHCP was defined to dynamically provide communications-related configuration values such as network addresses to network client computers at boot time. DHCP is specified by IETF RFCs 1534, 2131, and 2132.

DMI compliance

The DMTF owns the responsibility for the definition of DMI 2.0 compliance.

Extended Memory

Typically used to describe memory on an Intel architecture system above 1

MB.

GUID

A globally unique identifier. This is a 128-bit identifier generated via a specific algorithm that is extremely unlikely to be generated by the algorithm in another place or at another time.

IETF

Internet Engineering Task Force. The open industry body that owns the technical specifications for Internet standards (protocols, APIs, etc).

IID

An interface identifier and also a form of a UUID

(GUID).

IPL

Acronym for Initial Program Load, also known as the bootstrap or boot process.

LAN on Motherboard (LOM)

The concept of integrating the LAN subsystem onto the motherboard.

Management Information Base (MIB)

A collection of managed SNMP objects, residing in an information store.

Management Information Format (MIF)

An ASCII text file in the DMI architecture that describes a product’s manageable features and attributes. The DMI maintains this information in a MIF database and makes it available to operating systems and management applications. The DMTF has specified MIF formats for a variety of system types and peripheral devices.

MTFTP

Multicast Trivial File Transfer Protocol. PXE implements a proprietary implementation of MTFTP. Used to download NBP to many clients simultaneously.

100

NBP

Acronym for Network Bootstrap Program. The remote boot image downloaded by the PXE client via TFTP or MTFTP.

Network management

Along with server and system management, one of the three major components of managing a computing environment. Network management includes optimizing the performance, configuration, security, failure analysis, and repair of the infrastructure components in a LAN, WAN, or

Internet/intranet. Infrastructure components include items such as switches, adapter cards, routers, bridges, and gateways, but not the endnodes themselves.

NSB

Network Service Boot. A Network Service Boot is the ability for a PC user to request, at PC boot time, access to remote boot capabilities by invoking a special key (usually F12). NSB is implemented within MBA and also may be implemented in the PC BIOS.

Option ROM

ROM associated with a plug and play device. May be located on the device or in non-volatile storage on a system. MBA is implemented as an Option

ROM for a NIC.

PCI PM

PCI Bus Power Management Interface Specification.

POST

Acronym for Power On Self-Test. POST processing in the BIOS is responsible for initializing the system hardware and starting IPL.

Power management

Technology that allows a system to consume less power when not in use and to be fully operational when awakened.

Preboot Execution Environment (PXE)

A means by which agents can be loaded remotely onto systems to perform management tasks in the absence of a running OS. To enable the interoperability of clients and downloaded bootstrap programs, the client preboot code must provide a set of services for use by a downloaded bootstrap. It also must ensure certain aspects of the client state at the point in time when the bootstrap begins executing. 3Com's PXE solution is embedded in MBA.

Remote Procedure Call (RPC)

An industry-standard method for communication with remote, networked systems. DMI Version 2.0 specifies RPCs as the standard mechanism for remote access to manageable systems.

101

Remote Wake-Up (RWU)

The ability of a managed computer to be remotely awakened from a sleeping state.

RFC

Request for Comment. This is a class of document used by the IETF for proposing technologies for adoption by the IETF and setting these technologies on a standards track. Each RFC is assigned a unique integer document number. When a technology is adopted by the IETF as a standard, the corresponding RFC becomes the document that formally specifies the technology.

ROM

Acronym for Read-Only Memory.

RPL

Remote Program Load (RPL) is a protocol originally defined by IBM which allows workstations to start by downloading files from a server.

Shadow

A technique for mapping RAM into UMB space, potentially on top of ROM already occupying this space. Shadow memory may be write protected after initialization.

Simple Network Management Protocol (SNMP)

The most widely used protocol for communicating management information for networks. SNMP focuses primarily on the network backbone; it is complemented by standards such as DMI, which extend manageability to end systems.

System Management (SM) BIOS

A standard interface to management software via data structures through which system attributes are reported.

TFTP

Trivial File Transfer Protocol. An industry standard Internet protocol defined by the IETF to enable the transmission of files across the Internet. Used to download NBP from the TFTP server. Trivial File Transfer Protocol (TFTP,

Revision 2) to support NBP download is specified by IETF RFC 1350.

Total Cost of Ownership (TCO)

The lifetime costs of a product, including the initial hardware and software purchase price as well as installation, service, support, upgrades, training, downtime, and other factors.

UDP

User Datagram Protocol.

102

UNDI

Universal Network Device Interface; an API that provides a device independent network interface to the MBA base code and a download NBP.

Upper Memory

An area of system memory between the video buffers and the system ROM

BIOS. Typically between real mode segments C000 and F000.

Wired for Management (WfM)

The Wired for Management (WfM) Initiative is an Intel-led, industrysupported effort to make Intel Architecture-based systems universally manageable and universally managed, without sacrificing agility or performance. Through the WfM Initiative, Intel has worked with others in the industry, including 3Com, to develop guidelines for a new generation of platforms that can be centrally managed over networks to reduce Total Cost of Ownership (TCO). Systems based on these guidelines provide key technologies which, combined with management software applications, deliver capabilities that enable “down-the-wire management.” They also enable benefits in five critical areas of managing and controlling the computing environment: 1. Asset Management, 2. Universal Network Boot,

3. Off-Hours Maintenance (Power Savings), 4. System Diagnosis and Repair, and 5. Investment Protection.

103