argon audio 9130TXA-M User Manual
  1. Manuals
  2. Brands
  3. argon audio Manuals
  4. Adapter
  5. 9130TXA-M
  6. User manual

argon audio 9130TXA-M User Manual

10/100mbps pci fast ethernet adapter
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
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
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
1

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 9130TXA-M and is the answer not in the manual?

Questions and answers

Related Manuals for argon audio 9130TXA-M

Summary of Contents for argon audio 9130TXA-M

  • Page 1 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 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...
  • Page 2 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...

  • Page 3: Specifications

    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.

  • Page 4: Fcc Compliance Statement

    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.
  • Page 5 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.
  • Page 6 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 &...
  • Page 7 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...
  • Page 8 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...
  • Page 9 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.
  • Page 10 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...
  • Page 11 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 ) ●...
  • Page 12 © 2002 Argon Technology All rights reserved. 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.

  • Page 13: Table Of Contents

    CONTENTS 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 ............
  • Page 14 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...
  • Page 15 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...

  • Page 17: Chapter 1: Introduction

    Thank you for choosing Argon Managed PC Boot Agent (MBA), the world's best- selling network preboot solution for PC networks. MBA is a package of multi- protocol 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.
  • Page 18 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.

  • Page 19: Features

    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).
  • Page 20 implemented on a server or a network administration PC. For installation instructions, see “Boot Image Editor Installation” in Chapter 2 “Installing MBA.”...

  • Page 21: Chapter 2: Installing Mba

    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: MBA Type Installation Additional Steps Required Integrated into Not needed Go to Chapter 3 the PC BIOS by “Configuring MBA”...
  • Page 22 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.
  • Page 23 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.

  • Page 24: Boot Image Editor Installation

    Installing the NIC into the PC Now that the ROM has been inserted into the NIC, you can install the NIC into the 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 •...

  • Page 25: Chapter 3: Configuring Mba

    This chapter shows you how to configure MBA options. 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.

  • Page 26: Setting The Boot Order On Pcs With Bbs Bios

    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.

  • Page 27: Configuration Tables

    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.
  • Page 28 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.
  • Page 29 2: PXE C ABLE ONFIGURATION PTIONS Option Possible Description Default Name Values Default Network Choose whether MBA will perform a network boot or Local Boot a local hard disk boot by default. If Network boot is Local chosen as the default, the Local Boot Message is displayed at boot time (if a bootable device exists and Local Boot is enabled).
  • Page 30 : PXE C ABLE CONTINUED ONFIGURATION PTIONS Option Possible Description Default Name Values Boot Failure Next Boot If a network boot cannot be completed, choose Next Boot Device whether MBA will reboot the PC or allow the PC to Device boot from the next boot device.
  • Page 31 ABLE CONTINUED ONFIGURATION PTIONS Option Possible Description Default Name Values Config Enabled Choose whether to display or hide the message the Enabled Message MBA displays indicating to the user which hot keys Disabled to press to enter the MBA Configuration Screen, i.e. “Press Ctrl+Alt+B to configure…”.
  • Page 32 ABLE CONTINUED ONFIGURATION PTIONS Option Possible Description Default Name Values Scan Enabled Choose whether MBA scans the BOOTCONF.SYS file Enabled BOOTCONF. to determine the boot image filename for the PC. If Disabled disabled, MBA uses the default boot image filename. NetWare (User Default filename of the boot image file.
  • Page 33 : RPL C ABLE CONTINUED ONFIGURATION PTIONS Option Possible Description Default Name Values Config Enabled Choose whether to display or hide the message the Enabled Message MBA displays indicating to the user which hot keys Disabled to press to enter the MBA Configuration Screen, i.e. “Press Ctrl+Alt+B to configure…”.
  • Page 34 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. 5: S ABLE TARTUP PTIONS Option Possible Description Default Name Values...

  • Page 35: Changing The Options

    ABLE CONTINUED TARTUP PTIONS Option Possible Description Default Name Values Network Enabled Network Service Boot (NSB) allows the user to force Disabled Service a network boot when the PC is booting up Boot Disabled regardless of the position of MBA in the BBS boot order.

  • Page 36: Using The Mba-Based Configuration

    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 MBA- based 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 MBA- based configuration should be disabled.

  • Page 37: Using The Mbacfg Utility

    Using the MBACFG Utility 5: MBACFG M IGURE 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 If you are using Windows, MBACFG operates only in MS-DOS real mode, not from a DOS window.

  • Page 38: Changing Configuration Options Using A Configuration File

    6: MBACFG U IGURE TILITY 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.
  • Page 39 ;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...

  • Page 40: Changing Configuration Options From The Command Line

    ;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...

  • Page 41: Restoring A Previously Backed-Up Version

    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.
  • Page 42 MBAFLASH utility and specify the backup ROM file that the MBAFLASH utility created.
  • Page 43 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...

  • Page 44: Chapter 4: Using Mba Base Code

    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.

  • Page 45: Displaying Verbose Status Information (V Or Ctrl+Alt)

    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.

  • Page 46: Troubleshooting

    7: MBA I IGURE NFORMATION CREEN 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.

  • Page 47: Chapter 5: Using Pre-Os

    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.

  • Page 48: Pre-Os Framework

    9: W -OS D IGURE 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.

  • Page 49: Pc Pre-Os Bootup Sequence

    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.

  • Page 50: Defining Boot Image Content

    10: C IGURE REATING PRE 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.

  • Page 51: Creating Tcp/Ip Or Pxe Pre-Os Boot Images

    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.

  • Page 52: Tcp/Ip Or Pxe Pre-Os Sample

    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...
  • Page 53 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$...

  • Page 54: Netware Pre-Os Sample

    [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...

  • Page 55: Technical Information

    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.

  • Page 56: Chapter 6: Using Mba In Tcp/Ip Environments

    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...

  • Page 57: Setting Up The Server

    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.

  • Page 58: Creating A Boot Image File Using Boot Image Editor

    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. If you are using a memory manager see “Using Memory Managers”...

  • Page 59: Boot Screen

    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;...

  • Page 60: Other Tools

    13: V TCP/IP IGURE ERBOSE BOOT SCREEN 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.

  • Page 61: Application Notes

    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.

  • Page 62: Troubleshooting

    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 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.
  • Page 63 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.

  • Page 64: Chapter 7: Using Mba In A Wired For Management Environment Using Pxe

    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...
  • Page 65 14: MBA M PXE IGURE IN A 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.

  • Page 66: Quick Setup

    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.
  • Page 67 online help. To install Boot Image Editor, see “Boot Image Editor Installation” in Chapter 2 “Installing MBA.”...

  • Page 68: Chapter 8: Using Mba In Netware Environments

    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...

  • Page 69: Quick Setup

    16: MBA IGURE NVIRONMENTS 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 Format a bootable diskette, and copy to it all the files needed to make a boot diskette.

  • Page 70: Boot Screen

    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.

  • Page 71: Creating A Boot Image File Using Boot Image Editor

    17: N IGURE ORMAL ARE BOOT SCREEN 18: V IGURE ERBOSE ARE BOOT SCREEN Step 1 - Create a boot diskette Format a diskette as a DOS system diskette. Copy needed files to the boot diskette. Copy all required device drivers, NetWare •...
  • Page 72 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.
  • Page 73 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:.

  • Page 74: Boot Using Mba

    Boot Using MBA The PC can now be booted using MBA. Perform the following steps as needed: 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.
  • Page 75 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.

  • Page 76: Avoiding Autoexec.bat Conflicts In Sys:login

    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.

  • Page 77: Using Boot Image Editor To Create Additional Boot Image Files

    21: U IGURE 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”...

  • Page 78: Installing Msd

    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.

  • Page 79: Nodefault Mode

    [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...

  • Page 80: Application Notes

    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.

  • Page 81: Transferring From The Boot Image To Sys:login

    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.

  • Page 82: Mba Messages

    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.

  • Page 83: Batch File Missing Messages And How To Avoid Them

    “<”, “>” 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 “<”...

  • Page 84: Chapter 9: Using Mba In Remote Program Load Environments

    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 The RPL protocol within MBA does not support the Novell NetWare RPL protocol.

  • Page 85: Quick Setup

    22: MBA RPL E IGURE NVIRONMENTS 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.
  • Page 86 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.
  • Page 87 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.

  • Page 88: Appendix A: Technical Support

    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.
  • Page 89 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. - CPU speed - BIOS version and mfg.
  • Page 90 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.
  • Page 91 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.

  • Page 92: Argon Software License Agreement

    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.
  • Page 93 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...
  • Page 94 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.
  • Page 95 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.
  • Page 96 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.
  • Page 97 * 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...

  • Page 98: Glossary

    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,...
  • Page 99 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.
  • Page 100 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.
  • Page 101 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.
  • Page 102 Remote Wake-Up (RWU) The ability of a managed computer to be remotely awakened from a sleeping state. 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.
  • Page 103 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, industry- supported effort to make Intel Architecture-based systems universally...

This manual is also suitable for:

9130txa

Table of Contents