Copyright: 3Com Boot Image Editor © Copyright 1999, 3Com Corporation or its subsidiaries. All rights reserved.
Citation: © Copyright 1999, 3Com Corporation or its subsidiaries. All rights reserved.


Title Page
Boot Image Editor for Windows 9x & NT


About Boot Image Editor

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

Boot Image Editor combines and enhances the IMAGEGEN, IMGGEN, MAPGEN, and Multiple Image File Editor (MULTI_ED) DOS utilities previously available from Lanworks Technologies Co. Specifically, with Boot Image Editor, you can:

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

•	View and modify the contents of boot image files directly, without creating or accessing boot diskettes.

•	Create a menu boot file and designate a list of boot options from which end users can choose at boot time.

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

•	Configure boot image file options, such as whether they are read-only or writable or have extended or normal capacity.

•	Convert boot image files between environments, such as TCP/IP images to NetWare images and vice versa.

Like Novell’s legacy DOSGEN utility, 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 Boot Image Editor can be installed on any computer, it is usually implemented on a network server or a network administration PC.

See Also

About Boot Image Files

What's New About Creating Boot Image Files

Overview of Pre-OS Technology

Using 3Com's DynamicAccess boot services Components Together

Main Boot Image Editor Window

Overview of TCP/IP Boot Image Files

Overview of NetWare Boot Image Files

Overview of PXE Boot Image Files

Overview of Editing Boot Image Files


About Boot Image Files

Boot Image Editor allows you to create and manage boot image files. Boot image files are always stored on network drives so that network administrators can maintain, update, and assign them to the appropriate client PCs at the appropriate time. The boot image files that you create with Boot Image Editor can be set up afterward such that:

•	A single boot image file is shared among multiple client PCs.

•	Each client PC is associated with a unique boot image file.

•	End-users of the client PC have the option to select one of up to 16 boot image files, menu boot files, or the hard drive at boot time or to accept the assigned default.

Boot image files can be created for TCP/IP, NetWare, and Preboot eXecution Environments (PXE). No matter which network environment you work in, creating boot image files involves two basic steps:

•	Copy the boot files required to start the client PC (and, for a Pre-OS boot image, any desktop management agents) to a DOS-formatted boot diskette.

•	Take a snapshot of the boot diskette with Boot Image Editor.

In Boot Image Editor, you can work with two main types of image files: boot image files and menu boot files.

Boot Image Files

Boot Image Editor consolidates the contents of a regular boot diskette (or diskettes) into one boot image file. Boot image files contain files capable of booting a PC, such as COMMAND.COM, MSDOS.SYS, IO.SYS, DRVSPACE.BIN, AUTOEXEC.BAT, CONFIG.SYS, and network drivers, but they can also include any other boot file, device driver, or configuration-related file that you deem necessary.

For example, boot image files can be designed with Pre-OS capabilities. With a Pre-OS-enabled boot image file and the right maintenance tools, you can, for example, perform the following tasks all before the main operating system is loaded from the local hard drive:

• Scan for viruses.	• Update files (for example, drivers).
• Search a hard disk for file system inconsistencies.	• Make a backup of the local hard disk.

•	Scan for changes in hardware and software components.

Boot image files that create a Pre-OS connection load a temporary version of DOS, perform the specified maintenance tasks, unload DOS, and then resume (with the PBOOT utility rather than user intervention) loading the operating system from the hard drive, whatever form that operating system takes. Creating a Pre-OS connection, in a way, is like booting from a floppy drive, removing the boot floppy, and then rebooting from a hard drive.

Menu Boot Files (Formerly Known as Multi-Boot Files)

After you have created boot image files for TCP/IP, NetWare, or PXE environments, end users can select one of the boot image files at boot time. To provide boot option choices to the end user, you can create a menu boot file with Boot Image Editor. A menu boot file:

•	Presents up to 16 boot options to the end user in menu format.

•	Stores the name of the default boot option to be loaded after a specified time interval.

•	Is loaded into memory at the client PC instead of a regular boot image.

•	References boot image files, other menu boot files, or the local hard drive.

•	Was formerly called a multi-boot file.

•	Is called network bootstrap file in some PXE environments.

Menu boot files usually have *.MNU or *.PXE extensions and require no more than 6 KB of disk space on the network server and memory at the client PC. Numerous menu boot files can coexist. They are helpful when end users regularly change the hardware at their client PC and when multiple end users are sharing the same workstation, for example.

See Also…

About Boot Image Editor

What's New About Creating Boot Image Files

Using 3Com's DynamicAccess boot services ComponentsTogether

Creating TCP/IP Boot Image Files

Creating NetWare Boot Image Files

Creating PXE Menu Boot Files


Overview of Pre-OS Technology

With the boot image files constructed by Boot Image Editor, a pre-operating system (Pre-OS) connection can be established between the client PC and the network. This Pre-OS connection enables a client PC to download and execute centrally administered desktop management agents from a network server before loading the end user’s preferred operating system from the local hard drive. Pre-OS technology works as follows:

•	End-user powers on or restarts the client PC.

•	Boot ROM connects to the network server and transfers the boot image file.

•	Pre-OS connection is created by the boot image file on the network server. No end user awareness or intervention is required.

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

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

•	The PC loads the end user’s operating system from the local hard drive.

•	End-user logs into the network as usual.

Benefits of Using Pre-OS Connections

Pre-OS technology can help you to ensure that maintenance and administrative tasks are performed regularly and consistently, whether you are working in TCP/IP, NetWare, or PXE environments. Depending on the administrative tools you have on-hand, these Pre-OS tasks can include:

•	Scanning for and eradicating local hard disk viruses.

•	Searching the hard disk for file system inconsistencies. Then, if necessary, retrieving and replacing the damaged components automatically or allowing the network administrator to perform a remote rescue from the IT-management console.

•	Updating outdated drivers, batch files, and software on the client hard drive.

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

•	Making backups of the entire hard drive.

Pre-OS Framework

In the past, client PCs using remoteboot ROMs could start in only one of two ways: from a server-based boot image file or from their local drives. Pre-OS technology provides an alternative solution in which the initially booted operating system is not the ultimate operating system but rather a temporary environment created for executing management applications. Client PCs terminate the Pre-OS connection (or conduct a very soft Ctrl+Alt+Del) with the PBOOT utility and continue to boot from the local hard drive. Additional points about Pre-OS images follow:

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

•	Most boot images use a network connection to map network drives. Regular network drivers may be loaded from the boot image file.

•	If network login for executing Pre-OS agents is required, it is typically as a guest user so that user intervention is not necessary.

•	Pre-OS desktop management agents can reside either within the image or can be executed from a mapped network drive.

•	Pre-OS environments are supported by 3Com Managed PC Boot Agents configured for TCP/IP (BOOTP or DHCP), PXE, or NetWare protocol configurations. RPL configurations are not supported.

See Also…

Defining Boot Image File Content for Pre-OS Connectivity

Using 3Com's DynamicAccess boot services Components Together

Creating TCP/IP Boot Image Files

Creating NetWare Boot Image Files

Creating TCP/IP Boot Image Files for Use with PXE


What's New About Creating Boot Image Files

If you are a longtime user of Lanworks Technologies Co. BootWare or Managed PC Boot Agent (MBA) products, you may be familiar with the IMAGEGEN/IMGGEN, MAPGEN, and MULTI_ED DOS-based utilities. Boot Image Editor replaces these utilities and enhances your ability to create and manage boot image files and menu boot files (also called network bootstrap programs and formerly known as multi-boot files). Now, not only can you perform all the required tasks from Microsoft Windows, you can work with one application rather than three to perform image-related tasks.

With Boot Image Editor, now you can:

•	View and alter the contents of the boot image files with a user-friendly Windows interface.

•	Create directories within boot image files.

•	Change a NetWare boot image file to a TCP/IP boot image file (and vice versa).

•	Create boot image files for PXE.

•	Transfer a boot image file to a floppy diskette instead of just transferring the contents of a boot diskette to a network-based boot image file.

•	Enable or disable Pre-OS capabilities for a boot image file.

•	Enable and disable the capability of loading the entire boot image into memory by selecting the new Loader option (for NetWare environments).

•	Create menu boot files for TCP/IP and PXE environments as well as NetWare environments.

•	Quickly assign a default boot image file within a menu boot file.

Boot image files created with IMAGEGEN/IMGGEN are accessible and effective in the new Boot Image Editor environment and useful with 3Com Managed PC Boot Agents and legacy BootWare products.

See Also…

About Boot Image Editor

About Boot Image Files

Using 3Com's DynamicAccess boot services Components Together

Main Boot Image Editor Window


Using 3Com's DynamicAccess Boot Services Together
Using 3Com's DynamicAccess boot services Components Together

The Boot Image Editor is bundled with the 3Com Bootstrap Protocol (BOOTP), BOOTPTAB Editor, Trivial File Transfer Protocol, and Preboot eXecution Environment (PXE) Server software to offer bootstrap flexibility. This software suite can be used in several ways:

•	Use each software component independently.

•	Combine BOOTP and TFTP.

•	Combine PXE server and TFTP.

•	Use the BOOTPTAB Editor with BOOTP or PXE server.

•	Launch the Boot Image Editor from within the BOOTPTAB Editor.

•	Use the Boot Image Editor with the 3Com Managed PC Boot Agent.

•	Use any of the software components with third-party boot services.

You can mix applications and services, but you cannot use all boot services components together or simultaneously. The BOOTP and the PXE server software cannot be used together because of port number conflicts.

See Also…

About Boot Image Editor

About Boot Image Files

Overview of Pre-OS Technology

What's New About Creating Boot Image Files


3Com Managed PC Boot Agent (3Com MBA)

3Com Managed PC Boot Agent (3Com MBA) is a package of multiprotocol preboot firmware and software tools that enables you to remotely administer software, operating systems, and applications over the network, eliminating the need to visit client PCs in person. 3Com Managed PC Boot Agent is available as a network interface card (NIC) ROM or as a BIOS update for motherboards that contain network interface hardware. With 3Com Managed PC Boot Agent installed at client PCs, client PCs can boot from the network regardless of the contents of local hard drives or, in some cases, without any local drives at all.

Refer to the 3Com Managed PC Boot Agent User Guide for more information.


Bootstrap Protocol (BOOTP)

The Bootstrap Protocol (BOOTP) is used instead of the Dynamic Host Configuration Protocol (DHCP) to enable a client PC to discover its IP address. The IP address is static and is specified by the network administrator in the BOOTPTAB database file. The BOOTPTAB database file contains an entry for each applicable client PC on the network or subnet.

In remoteboot and preboot environments, BOOTP and the Trivial File Transfer Protocol (TFTP) work together. BOOTP not only provides an IP address—it can provide a boot image filename. TFTP enables the client PC to download the boot image file after receiving data from BOOTP.

More information on BOOTP is available in the 3Com BOOTP online help.


3Com PXE Server

The Preboot eXecution Environment (PXE) server software is an extension of the Dynamic Host Configuration Protocol (DHCP). 3Com PXE server is installed on a Wired for Management network boot server to reply to client PC requests for a Network Bootstrap Program (NBP—also known as a menu boot file) after DHCP provides an IP address.

Menu boot files are created with the Boot Image Editor and are usually assigned to client PCs via a BOOTPTAB database file. If you want all the clients on your network to download the same menu boot file, you do not need to implement the PXE server—you can specify the menu boot file in the DHCP configuration utility. If you want to support multiple menu boot files on your network, PXE server is essential.

PXE server and DHCP can be installed in two ways:

•	On the same network server.

•	On different network servers (remote or local).

PXE server adds tags to DHCP reply packets to direct client PCs to network boot servers. An optional ProxyDHCP feature is used when PXE server are installed on a different network server than DHCP.

Additional information on the PXE server software is available in the 3Com PXE server online help.


3Com BOOTPTAB Editor

The BOOTPTAB Editor is a utility for creating, editing, and maintaining BOOTPTAB database files. Specifically, BOOTPTAB Editor enables you to:

•	Add, modify, and delete individual client PC entries.

•	Add, modify, and delete templates.

•	Search based on any field.

•	Sort on any field.

•	Replace elements of the file quickly.

•	Update individual client PC entries with new boot image files, menu boot files, IP addresses, and templates. You can even jump to the Boot Image Editor to edit and create appropriate boot image files and menu boot files.

•	Properly format and easily adhere to the mandatory syntax of the file.

•	Support Carnegie Mellon University (CMU) industry-standard BOOTPTAB files.

Refer to the BOOTPTAB Editor online help for additional information.


Trivial File Transfer Protocol (TFTP)

The Trivial File Transfer Protocol (TFTP) is a simple form of the File Transfer Protocol (FTP). TFTP reads, writes, and transfers files on TCP/IP networks but does not provide the sophisticated features (such as directory listings, password protection, and user authentication) that FTP supplies. TFTP was designed to be small and to fit in size-limited media (for example, a boot ROM). In addition to booting client PCs, you can use TFTP to configure and upgrade X-terminals and firmware for switches, hubs, print servers, routers, and other network devices.

3Com TFTP was developed in accordance with Requests for Comments (RFCs) 1350, 1783, and 2348. More information on TFTP is available in the 3Com TFTP online help.


BPPATCH Utility

BPPATCH allows one common boot image file to be used by several client PCs by replacing parameters from BOOTP (or DHCP) reply packets into text files. With BPPATCH, the parameters unique to each client PC (like the IP address) are specified in the BOOTPTAB database file on the BOOTP network server and replaced in the boot image file when the client PC boots.

To use BPPATCH, you put tags into the text files identified within the boot image file (batch files, configuration files, and so on) to indicate which BOOTP fields you want to replace. You then run BPPATCH and specify the files to be patched in the command line. For example, if you want to patch the files START.BAT and PCTCP.INI, your command line is:

bppatch start.bat pctcp.ini

The BPPATCH utility is included with the 3Com DynamicAccess boot services and on the 3Com Managed PC Boot Agent Utility Disk. Refer to the BPPATCH README file or the 3Com Managed PC Boot Agent User Guide for more information on BPPATCH.


Main Boot Image Editor Window

Boot Image Editor allows you to create and manipulate boot image files that can be stored on your network server and downloaded to client PCs at boot time. These boot image files can contain files from a standard boot diskette and can execute desktop maintenance agents such as virus scanners, file comparison and replacement tools, and hardware inventory utilities.

The buttons that appear in this window are dependent on the selections that you made in the Network Selection window.

	The Create a TCP/IP or PXE image file button allows you to create a new boot image file for booting from TCP/IP and PXE servers. If you are using PXE, you need to create both a TCP/IP image and a PXE menu boot file.
	The Create a TCP/IP menu boot file button enables you to create an executable menu boot file that is downloaded to a TCP/IP remoteboot client PC at boot time instead of a boot image file. The menu boot file allows the end user to select one of up to 16 boot options to boot the client PC.
	The Create a NetWare image file button enables you to create a new boot image file for booting from NetWare servers.
	The Create a NetWare menu boot file button enables you to create an executable menu boot file that is downloaded to a NetWare remoteboot client PC at boot time instead of a boot image file. The menu boot file created with this button allows the end user to select one of up to 16 boot options to boot the client PC.
	The Create a PXE menu boot file button provides a method of remotebooting with PXE. If you are using PXE, you need to create both a TCP/IP boot image file and a PXE menu boot file. Menu boot files are a form of network bootstrap program.
	The Edit an existing file button allows you to view, modify, add to, delete, and extract the contents of a TCP/IP, NetWare, or PXE boot image file or menu boot file. You can also convert the boot image file contents to a boot diskette.
	The System Menu gives you access to copyright and version information. It also gives you access to a window that you encountered when you installed Boot Image Editor—the Network Selection window.  The Network Selection window allows you to change the options and functionality of the main Boot Image Editor window and, more importantly, create images for different network environments.
	The Exit button quits the Boot Image Editor program.
	The Help button gives you access to Boot Image Editor online help.
See Also…

About Boot Image Editor

About Boot Image Files

Overview of Pre-OS Technology


Overview of TCP/IP Boot Image Files

A TCP/IP client PC can be configured to boot from:

•	A single TCP/IP boot image file that is shared by several similar PCs.

•	A customized TCP/IP boot image file designed just for that PC.

•	Any one of several designated boot image files referenced from a TCP/IP menu boot file, depending on the needs of the PC end user or the hardware at the time.

TCP/IP boot image files are used primarily with network servers that host the DHCP or BOOTP and TFTP protocols. With PXE technology, you must employ a TCP/IP boot image file with a PXE menu boot file. DHCP and BOOTP commonly work with Windows NT Server and UNIX, but Novell servers can also use TCP/IP. When you implement remotebooting in a mixed network, the boot image file must be created for the type of network server on which it will reside.

TCP/IP boot image files are not all that different from NetWare boot image files. The main differences are that TCP/IP boot image files have headers to assist in the file transfer from the network server to the client PC, can be writable, and are by default completely loaded into the memory of the client PC before booting begins. You can convert a TCP/IP boot image file to a NetWare boot image file by selecting an option and then moving it to a NetWare server configured for remotebooting.

See Also…

Overview of Using Menu Boot Files

About Boot Image Files

Creating TCP/IP Boot Diskettes

Creating TCP/IP Boot Image Files


Create Image File Window

The Create Image File window enables you to create new boot image files from standard boot diskettes and set the properties for remotebooting. You can create new boot image files or overwrite existing boot image files in this window.

Image file name:	The Image file name field enables you to assign a name and a path for the boot image file.  You can use long filenames for the boot image file. Boot image files normally have *.IMG (for TCP/IP environments) or *.SYS (for NetWare environments) file extensions, but you can type any extension. Boot image files are usually stored in the \TFTPBOOT (for TCP/IP environments) or SYS:LOGIN (for NetWare environments) directory on the network server. However, boot image files for TCP/IP can be stored in any directory accessible to the Trivial File Transfer Protocol (TFTP).
	The Browse button enables you to navigate to the drive and directory in which you want to store the new boot image file. If you want to overwrite an existing boot image file, you can locate it with this button.
Source drive:	The Source drive options (A and B) enable you to select which local floppy drive contains the boot diskette that you want to convert to a boot image file.
Normal disk capacity:	The Normal disk capacity option, when selected, indicates that the boot image file will have the same capacity as the original boot diskette.
Extended capacity:	The Extended capacity option enables you to specify the maximum size of the boot image file (maximum 16 MB) and to create a boot image file that is larger than the contents of a boot diskette.
Writable (for TCP/IP boot image files only):	The Writable option, when selected, enables you to create a writable boot image file for use in TCP/IP environments. If the Writable option is not selected, memory requirements will be minimized.
Loader (for NetWare boot image files only):	The Loader option, when selected, forces a NetWare boot image file to be loaded completely into memory before the client PC begins to boot.
Track copy:	The Track copy option, when selected, enables you to create an exact track-by-track duplicate of the boot diskette.
Pre-OS:	The Pre-OS option, when selected, allows you to run desktop management agents (such as virus scanners and file compare and repair utilities) before the ultimate operating system is loaded from the PC’s hard drive.
Don’t display banner:	This option is only available and relevant when you have selected Pre-OS. This option hides or displays the large “Entering 3Com Pre-OS…” banner when the PC boots.  The Pre-OS copyright message always appears if Pre-OS is enabled. The “Exiting 3Com Pre-OS…” banner is controlled by a PBOOT option.
(for TCP/IP boot image files only)	Selecting the Advanced button gives you access to the Advanced options window, which has two options that are required if you have included in your TCP/IP boot image a program that uses PXE APIs.
	Selecting the Help button gives you access to Boot Image Editor online help.
	Selecting the OK button activates the selected floppy drive and creates the image.
	Selecting the Cancel button quits the Create Image File window without creating a boot image file.

See Also…

Creating TCP/IP Boot Diskettes

Creating TCP/IP Boot Image Files

Advanced Options Window

Creating NetWare Boot Diskettes

Creating NetWare Boot Image Files


Advanced Options Window

The Advanced Options window allows you to enable and disable APIs for TCP/IP boot image files that were created for PXE environments. Refer to the Preboot eXecution Environment (PXE) Specification (available at http://www.developer.intel.com/ial/WfM) for more information, if necessary.

Keep base code in memory:	In most cases, this option is not enabled. The Keep base code in memory option should be selected if you are using a utility that requires the PXE base code (which encompasses Preboot, TFTP, and UDP APIs) and the Universal NIC Driver Interface (UNDI) API. If this option is selected, the Keep UNDI in memory option must be selected as well.
Keep UNDI in memory:	In most cases, this option is not enabled. The Keep UNDI in memory option should be selected when the utility operating at the client PC requires the Universal NIC Driver Interface (UNDI) API. The UNDI API controls and enables I/O through the NIC. UNDI provides a device-independent network interface to the network bootstrap program. This option can work with or without the Keep base code in memory option.
See also…

Create Image File Window

Overview of PXE Boot Image Files


Details on PXE APIs

3Com Managed PC Boot Agent 3.x or higher and PXE ROMs have data communication and networking programmatic interfaces (or APIs—Application Program Interfaces). These APIs can be used by other programs to provide data communication functionality (for example, transmit and receive packets) using the network interface card (NIC) in the client PC. There are high-level APIs (for example, TFTP and UDP) in the ROM’s base code, and low-level APIs in the ROM’s Universal NIC Driver Interface (UNDI).

Normally, after a boot image file is downloaded into the memory of the client PC and executed, the boot ROM code is removed from memory, and these APIs are unavailable. So, if you have a program in your boot image file that relies on any of these APIs, you need to check the appropriate option.

Refer to the Preboot eXecution Environment (PXE) Specification (available at http://www.developer.intel.com/ial/WfM) for more information.


Details on the Extended Capacity Option

Extended capacity boot image files are useful when you know you will be adding files that exceed the capacity of the original boot diskette. Boot Image Editor supports boot image files up to 16 MB.

A boot image file typically only takes as much space (on the network server and in memory) as required by the files it contains, even if you enter a larger number into the MB field. However, if you are working in TCP/IP environments and the boot image file is writable, all of the boot image file, even the unused extended capacity, is loaded into the memory of the client PC at boot time.

You cannot modify the capacity of a boot image file once it has been created.


Details on the Writable Option

Normally a boot image file is read-only just like a write-protected floppy diskette. If you need to write to the boot image file during remoteboot or preboot activity, you can make the TCP/IP boot image file writable.

Making a boot image file writable increases the amount of memory required by the boot image file. A normal read-only image only requires enough memory to hold all the files in the image. A writable boot image file requires the full boot image file capacity of memory. In other words, the number that you type in the MB field (beside the Extended option) might reflect the amount of memory that is required to boot properly.

Writable boot image files may be useful if you are using Pre-OS, for example. The applications that are executed before the operating system is loaded from a local drive may create temporary logs or text files in memory while they are running.


Creating TCP/IP Boot Diskettes

Before you can create a boot image file, you must prepare a boot diskette (or multiple diskettes). Creating a boot diskette to convert to a boot image file is the same as creating a regular boot diskette. In fact, you can continue to use the boot diskette in floppy drives after transferring its contents to a boot image file.

To create a TCP/IP boot diskette:

•	Format a diskette as a DOS system diskette.

•	Copy all the files that are needed to boot the client PC from the network to the boot diskette or diskettes.

Standard boot files and files to establish a Pre-OS connection, if applicable, should be included on the boot diskette. Boot Image Editor allows you to create a boot image file out of several boot diskettes, if required.

•	Boot the client PC using the new boot diskette to confirm that it is working correctly.

You have created a boot diskette to prepare a boot image file. When you are confident that the boot diskette is functioning properly, you can use it to create the boot image file in Boot Image Editor.

See Also…

Defining TCP/IP Boot Diskette Contents

Creating TCP/IP Boot Image Files

Defining the Boot Image File Content for Pre-OS Connectivity


Defining TCP/IP Boot Diskette Contents

Although the contents of boot image files are completely customizable, they generally contain the following types of files:

• DOS system files—COMMAND.COM, IO.SYS, MSDOS.SYS.	• Configuration files—such as CONFIG.SYS, AUTOEXEC.BAT.
• Device drivers.	• Memory managers.
• Network drivers.	• Pre-OS desktop management agents.
An AUTOEXEC.BAT file is required on boot diskettes to load the necessary 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. The network-based *.BAT file should change the DOS COMSPEC variable so that DOS can find a copy of COMMAND.COM after the boot image file is released from memory with the FREEMEM program. FREEMEM must be run from a network drive rather than from within a boot image file. Following are sample batch files:

A skeletal *.BAT file on the boot diskette follows:

rem network drivers load here

rem  NFS or other drive mapping command here

init.bat

INIT.BAT, located on the network server, is as follows:

set comspec = e:\dos\command.com

freemem

rem other commands may load now

Following is a partial sample AUTOEXEC.BAT file using PC/TCP software from FTP Software Inc. to map the /PUBLIC directory, on the network server called TEST, to local drive E. Control is transferred to the INIT.BAT file shown above at the end of the AUTOEXEC.BAT:

lsl

fasteth (or whatever your ODI driver is named)

odipkt

ethdrv

idrive

idmnt unix test /public e: pcnfs nobody

e:

init.bat

When creating and working with boot image files, be sure that each client PC has licensed copies of the operating system and utilities being used.

See Also…

Creating TCP/IP Boot Diskettes

Creating TCP/IP Boot Image Files

Defining Boot Image File Content for Pre-OS Connectivity


Defining Boot Image File Content for Pre-OS Connectivity

The contents of the boot images required to establish a Pre-OS connection are customizable and unique to the needs of your end users. With standard boot utilities, you can create a boot diskette that allows the client PC to load memory managers, network drivers, virus checkers, backup routines, software updating agents, and other executables from:

•	The boot image file (which is mapped as A: drive during the bootstrap procedure).

•	The local hard drive.

•	A network drive.

•	A combination of all three locations listed above.

One of the distinguishing characteristics of a boot image file with Pre-OS capabilities is the PBOOT utility. After Pre-OS tasks are complete, the PBOOT utility allows the preferred operating system to load from the hard drive. You cannot configure the boot process such that the final operating system is loaded from another boot image on the network server; the ultimate operating system must be started from the local hard drive.

Like other types of boot image files, boot image files with Pre-OS are usually based on simple DOS boot diskettes. Below are additional points about defining Pre-OS image content:

•	To terminate the Pre-OS connection and directly boot another operating system from the hard drive, the PBOOT command must be the last command in the AUTOEXEC.BAT file executing within the boot image. PBOOT has one option: /nologo. Typing PBOOT /nologo indicates that you want to suppress the display of the large stylized 3Com Pre-OS banner.

•	Executables loaded from drive A: have read-write access (only if the image is writable) but have limited disk space available for the boot image. Executables loaded from the network usually have read-only access but no size restrictions.

•	For NetWare environments, you should use 16-bit NetWare clients.

•	For client PCs booting from Windows NT Server, 3Com recommends 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 Windows-NT capable NFS servers and DOS-client software that usually consists of TCP/IP-based TSRs or packet drivers. Examples of these clients are: PC TCP/IP from FTP Software (http://www.ftp.com/product/pctcp/pctcp4.htm ) and NFS Maestro from Hummingbird Communications (http://www.hummingbird.com/products/maestro/).

See Also…

Overview of Pre-OS Technology

Converting Pre-OS Images to Regular Boot Image Files

Creating TCP/IP Boot Image Files

Creating NetWare Boot Image Files

Creating TCP/IP Boot Image Files for Use with PXE


Creating TCP/IP Boot Image Files

You can produce a new boot image file by copying and renaming an existing boot image file. However, if you need to create a totally new boot image file for TCP/IP or PXE environments, follow the instructions below.

To create a TCP/IP boot image file:

•	From the main Boot Image Editor window, select Create a TCP/IP or PXE image file.

•	Insert a prepared boot diskette for the client PC in floppy drive A or B.

Insert the first boot diskette if the chosen operating system configuration requires multiple boot diskettes.

•	Type a full path and a name for the new boot image file in the Image file name field.

If desired, you can select Browse to find the selected location. Boot image files are usually stored on the network server in the \TFTPBOOT directory, but you can save them in any directory indicated in the BOOTPTAB file or the DHCP configuration tool. Long filenames are acceptable. You can use any three-character extension, but *.IMG is recommended.

•	In the Source drive area, select the floppy drive letter that contains the boot diskette.

•	Select the Normal disk capacity option to indicate that the boot image file will be no larger than 1.44 MB (or the contents of a standard DOS boot diskette).

Or

Select the Extended capacity option and then specify the maximum capacity of the boot image file (up to 16 MB) in the MB field.

•	If desired, select the Writable option to permit the creation of, for example, temporary log and text files within the boot image file.

Writable images require enough memory to contain their entire capacity. Read-only images require only enough memory to host the combined size of all of the files present.

Writable boot image files are completely loaded (including the unused extended capacity of the boot image files, if applicable) in the client PC’s memory before booting occurs.

•	If desired, select Track copy option to create an exact track-by-track replica of the boot image file.

•	If desired, select the Pre-OS option to enable 3Com Pre-OS functionality.

If you enabled Pre-OS, you can select the Don’t display banner option to prevent the Pre-OS banner from displaying at the client PC.

•	If you are creating a boot image file that includes programs that use PXE APIs, select the Advanced button and then select the appropriate option in the Advanced Options window.

•	Select OK.

You have created a boot image file. If the network server components are configured for remotebooting, boot the client PC with the boot image file to ensure that everything is working properly. You can now add the boot image file to a TCP/IP menu boot file; associate it with a PXE network bootstrap program; copy, edit, and rename it to create a boot image file for another client PC; or edit the contents with Boot Image Editor. The boot diskette remains functional and intact.

See Also…

Create Image File Window

Creating TCP/IP Boot Diskettes

Defining TCP/IP Boot Diskette Contents

Defining the Boot Image File Content for Pre-OS Connectivity

Creating Menu Boot Files for Selecting Different Images at Boot Time

Overview of Editing Boot Image Files


Creating a Boot Image File from Multiple Boot Diskettes

Some operating systems and configurations require multiple boot diskettes. Converting multiple boot diskettes to an image involves creating a regular boot image file and then adding the other required files with the editing features in Boot Image Editor.

To create a boot image file from multiple diskettes:

•	Create an extended-capacity boot image file from the first boot diskette.

Note the total file sizes of all of the boot diskettes and then enter the total size (up to 16 MB) in the MB field. The first diskette should be used to create the initial boot image file.

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate and double-click the boot image file you just created.

•	Insert the next boot diskette in the floppy drive.

•	From the File menu, select Add, and then select all the files on the floppy that you want to copy.

Or

With Windows Explorer or another file management program running, drag and drop the files from the floppy drive to the View Image File window.

•	Repeat steps 4 to 6 for all of the original boot diskettes required to complete the boot image file.

•	Select Close.


Overview of PXE Boot Image Files

Boot Image Editor creates and supports boot image files designed for Preboot eXecution Environment (PXE) technology. With Boot Image Editor, you can create the TCP/IP boot image files and the PXE menu boot files (also known as network bootstrap programs) that are required for remotebooting in Wired for Management (WfM) environments. The WfM initiative is an industry effort to simplify the remote management of desktop, server, and mobile PCs (see http://www.3com.com/news/releases/pr99/mar0499b.html or http://developer.intel.com/ial/WfM for more information on the PXE protocol and WfM specifications).

PXE Boot Process

Remotebooting client PCs with PXE is usually a three-step process:

•	Power on (or restart) the client PC and allow the PC to download the PXE menu boot file.

•	If applicable, the end user can select the boot image file from the list of TCP/IP boot image files and boot options displayed on the screen. If there is only one boot option specified in the PXE menu boot file, that boot option will be executed automatically, without presenting the boot menu to the end user.

•	The PC downloads the selected TCP/IP boot image file into memory and boots the end user’s operating system.

Similarities Between PXE Menu Boot Files and TCP/IP Menu Boot Files

From the end user’s perspective, PXE menu boot files and boot image files are identical to TCP/IP menu boot files and TCP/IP boot image files. Even the process of creating PXE menu boot files and TCP/IP menu boot files is similar. Both TCP/IP menu boot files and PXE menu boot files can be set up so that there is:

•	Up to 16 boot options (boot image files, references to other PXE menu boot files, and the local hard drive) listed.

•	A default boot option.

•	A group of end users sharing the same menu boot file.

•	A single end user employing a private menu boot file.

Differences Between PXE Menu Boot Files and TCP/IP Menu Boot Files

Most of the unique elements of PXE menu boot files are internal, but a few of the distinguishing features of PXE menu boot files include:

•	PXE menu boot files are mandatory for all PXE-enabled client PCs, even if the end user only has one boot option. PCs in Wired for Management environments must be configured to remoteboot from a PXE menu boot file, whereas TCP/IP menu boot files are optional.

•	TCP/IP menu boot files usually have *.MNU extensions. PXE menu boot files have *.PXE extensions by default, but you can change them to any other three-character extension.

See Also…

Creating Menu Boot Files for Selecting Different Images at Boot Time

Creating TCP/IP Boot Image Files for Use with PXE

Creating PXE Boot Diskettes

Creating PXE Menu Boot Files


Creating PXE Boot Diskettes

Preboot eXecution Environment (PXE) boot diskettes are essentially TCP/IP boot diskettes. Only minor differences exist between creating startup diskettes for PCs in Wired for Management (WfM) PXE environments and creating startup diskettes for PCs in TCP/IP environments.

See Also…

Overview of PXE Boot Image Files

Creating TCP/IP Boot Image Files for Use with PXE

Creating PXE Menu Boot Files


Creating TCP/IP Boot Image Files for Use with PXE

TCP/IP boot image files are used within PXE menu boot files (which are also known as network bootstrap programs, or NBPs). The TCP/IP boot image files that are used with PXE can be configured with all of the same options offered for regular TCP/IP boot image files. The Advanced button on the Create TCP/IP Image File window offers two additional options of special interest to users in PXE environments.

TCP/IP boot image files and PXE menu boot files can be stored on the primary DHCP host server or on a separate boot server that hosts the PXE server protocol. PXE menu boot files and the boot image files referenced by them are usually stored in the same directory—either the \TFTPBOOT directory (especially when there is no separate boot server) or the directory dictated by the chosen PXE server protocol. If necessary, refer to your PXE protocol documentation for specific instructions on where to save these menu boot files.

After creating TCP/IP boot image files for PXE environments, you must add them to the PXE menu boot file.

See Also…

Creating TCP/IP Boot Image Files

Creating PXE Menu Boot Files


Creating PXE Menu Boot Files

PXE menu boot files (or network bootstrap programs) are mandatory in Wired for Management (WfM) environments. Each PXE menu boot file can contain up to 16 boot options, including TCP/IP boot image files, other PXE menu boot files, or the local hard drive. These menu boot files normally have *.PXE extensions and have a maximum size of 6 KB, no matter how many boot options are included, because boot options are merely referenced from the PXE menu boot file.

If there is only one boot option referenced in a PXE menu boot file, the end user does not see the boot menu interface—the boot option is loaded and executed automatically. These instructions assume you have already created at least one TCP/IP boot image file.

To create a PXE menu boot file:

•	From the main Boot Image Editor window, select Create a PXE menu boot file.

•	Select Add in the Files tab.

•	Select Browse to select an existing boot option for the Image file field.

Or

Type the path and name of the boot option in the Image file field.

Or

Select the Boot from hard drive option to enable the end user to boot from the client PC’s hard drive.

After selecting a TCP/IP boot image file or PXE menu boot file, you can select View to look at the contents of the boot option and ensure that the boot option is actually designed for PXE environments. The content of the Image file field is somewhat dependent on the Path field.

•	If desired, type a comment or description for the boot image file, PXE menu boot file, or hard drive boot option in the Menu description field.

•	Select OK.

•	Repeat steps 2 to 5 for each boot option you want to add.

•	Select a default boot option or set the menu boot file preferences.

•	Select Save and specify a filename and location for the new PXE menu boot file.

It is recommended that you use the standard *.PXE extension, but you can assign another extension.

See Also…

Creating TCP/IP Boot Image Files

Overview of PXE Boot Image Files


Overview of NetWare Boot Image Files

NetWare boot image files are used primarily with 3Com Managed PC Boot Agents to remoteboot or run Pre-OS utilities at client PCs. A NetWare client PC can be configured to boot from:

•	A single NetWare boot image file that is shared by several similar PCs.

•	A customized NetWare boot image file designed just for that PC.

•	Any one of several designated boot image files referenced from a NetWare menu boot file, depending on the needs of the PC end user or the hardware at the time.

NetWare boot image file options are not all that different from those found in TCP/IP boot image files. Aside from internal distinctions, the main differences are that NetWare boot image files are not writable and are not automatically loaded completely into memory before beginning the boot sequence like TCP/IP boot image files. If you want to load the boot image completely into the client PC’s memory before booting, you must configure it to do so by selecting the Loader option and using the FREEMEM utility to release the memory afterward. You can convert a NetWare boot image file to a TCP/IP boot image file and then move it to a TCP/IP network server configured for remotebooting.

NetWare boot image files and menu boot files are always stored in the SYS:LOGIN directory of NetWare servers. If you are working with multiple NetWare boot image files or menu boot files, reference should be made to these files in the BOOTCONF.SYS boot index file, which is also stored in the SYS:LOGIN directory. If all of the client PCs are accessing the same boot image file or if you are not using a BOOTCONF.SYS index file, you should name the boot image file NET$DOS.SYS. In fact, all NetWare boot image files have *.SYS extensions by default.

Refer to the 3Com Managed PC Boot Agent (MBA) User Guide for details on the configuration and management of NetWare boot image files and menu boot files.

See Also…

Overview of Using Menu Boot Files

About Boot Image Files

Creating NetWare Boot Image Files


Details on the Loader Option

The Loader feature creates a RAM disk mapped as drive A:, copies in the contents of the entire boot image file, severs the connection to the network server, and continues to boot the client PC with the RAM disk. For users familiar with Lanworks Technologies Co. BootWare or 3Com Managed PC Boot Agent products, the Loader feature in the Create NetWare Image File window replaces the BWLOADHI utility that was formerly available on the 3Com Managed PC Boot Agent Utility Disk.

The Loader feature is useful because it:

•	Provides a quick fix for many VLM-related COMSPEC and PATH problems.

•	Helps to overcome various compatibility problems with multiple protocol stacks, 32-bit clients, and other installations.

•	May speed booting or reduce network traffic.

•	Eliminates the need to copy boot image file-related *.BAT file to the SYS:LOGIN directory.

•	Eliminates the need to load RPLODI (see the 3Com Managed PC Boot Agent User Guide for information on RPLODI) within the boot image file.

To remove the RAM disk from memory, you must use the FREEMEM utility.


The FREEMEM Utility

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

Before you can use FREEMEM, you must change your DOS COMSPEC variable to a DOS directory on the network. Otherwise, you receive an error when DOS tries to reload COMMAND.COM after FREEMEM terminates.

FREEMEM cannot be included in or run from the boot image file. It must be executed from a *.BAT file within the primary boot directory (In SYS:LOGIN for NetWare environments. Usually \TFTPBOOT for TCP/IP environments.) on a network drive.

The FREEMEM utility is always used with TCP/IP boot image files (because the images are always completely loaded into memory before booting) and must be used when the Loader feature has been enabled for NetWare boot image files. After using FREEMEM, you should have all but 2 KB of memory available.


Creating NetWare Boot Diskettes

Before you can create a boot image file, you must prepare a boot diskette (or multiple diskettes) to create the boot image file from. Creating a boot diskette to convert to a boot image file is the same as creating a regular boot diskette. In fact, you can continue to use the boot diskette in floppy drives after transferring its contents to a boot image file.

To create a NetWare boot diskette:

•	Format a diskette as a DOS system diskette.

•	Copy all the files that are needed to boot the client PC from the network to the boot diskette or diskettes.

Standard boot files and files to establish a Pre-OS connection, if applicable, should be included on the boot diskette. Boot Image Editor allows you to create a boot image file from several boot diskettes, if required.

•	Boot the client PC using the new boot diskette to confirm that it is working correctly.

You have created a boot diskette to prepare a boot image file. When you are confident that the boot diskette is functioning properly, you can use it to create the boot image file in Boot Image Editor.

See Also…

Defining NetWare Boot Diskette Contents

Creating NetWare Boot Image Files


Defining NetWare Boot Diskette Content

Although the contents of boot image files are completely customizable, they generally contain or reference the following types of files and utilities:

•	DOS system files—COMMAND.COM, IO.SYS, MSDOS.SYS.

•	Configuration files—such as CONFIG.SYS, AUTOEXEC.BAT.

•	Device drivers.

•	Memory managers.

•	Pre-OS desktop management agents.

•	NetWare client drivers.

•	FREEMEM, CHKID, ROMTYPE, and other tools available on the 3Com Managed PC Boot Agent (MBA) Utility Disk.

The latest version of the 3Com Managed PC Boot Agent User Guide describes the contents of and issues related to the AUTOEXEC.BAT and CONFIG.SYS files within NetWare boot image files. It also provides samples and details on the usage and configuration of these images. The 3Com Managed PC Boot Agent User Guide is available on the 3Com Managed PC Boot Agent Utility Disk.

See Also…

Creating NetWare Boot Diskettes

Creating NetWare Boot Image Files

Defining Boot Image Content for Pre-OS Connectivity


Creating NetWare Boot Image Files

You can produce a new boot image file by copying and renaming an existing boot image file. However, if you need to create a totally new boot image file for NetWare environments, follow these instructions.

To create a NetWare boot image file:

•	From the main Boot Image Editor window, select Create a NetWare image file.

•	Insert a prepared boot diskette for the client PC in floppy drive A or B.

Insert the first boot diskette if the chosen operating system configuration requires multiple boot diskettes.

•	Type a full path and a name for the new boot image file in the Image file name field.

NetWare boot image files and menu boot files are always stored in the SYS:LOGIN directory of NetWare servers. If all of the client PCs are accessing the same boot image file or if you are not using a BOOTCONF.SYS index file, name the file NET$DOS.SYS.

If desired, select Browse to enter the path. Long filenames are acceptable, but the *.SYS extension is highly recommended.

•	In the Source drive area, select the floppy drive letter that contains the boot diskette.

•	Select the Normal disk capacity option to indicate that the boot image file will be no larger than 1.44 MB (or the contents of a standard DOS boot diskette).

Or

Select the Extended capacity option and then specify the maximum capacity of the boot image file (up to 16 MB) in the MB field.

•	If desired, select the Loader option to force a boot image file to be loaded completely into memory before the client PC begins to boot.

•	If desired, select the Track copy option to create an exact track-by-track replica of the boot image file.

•	If desired, select the Pre-OS option to enable 3Com Pre-OS functionality.

If you enabled Pre-OS, you can select the Don’t display banner option to prevent the Pre-OS banner from displaying at the client PC.

•	Select OK.

You have created a boot image file for NetWare environments. If the network server components are configured for remotebooting, boot the client PC with the boot image file to ensure that everything is working properly. You can now add the boot image file to a NetWare menu boot file; copy, edit, and rename it to create a boot image file for another client PC; or edit the contents with Boot Image Editor tools. The original boot diskette remains functional and intact.

See Also…

Create Image File Window

Creating NetWare Boot Diskettes

Defining NetWare Boot Diskette Contents

Defining the Boot Image File Content for Pre-OS Connectivity

Creating Menu Boot Files for Selecting Different Images at Boot Time

Overview of Editing Boot Image Files


Overview of Using Menu Boot Image Files

Although many client PCs can boot from the same boot image file, it is possible that more than one boot image file will be required to suit the differing needs of the end users and client PCs on your network, especially if different operating systems, versions, and hardware need to be supported. You can configure the remoteboot network such that each client PC has a unique boot file, or you can give PC end users the option of selecting an appropriate boot image file. In other words, rather than changing the network server configuration each time a PC end user wants to switch boot image files, you can create a menu boot file that they can operate from the client PC at boot time.

Menu boot files resemble boot image files in many ways. Like boot image files, menu boot files are created and managed with Boot Image Editor and appear as a single file when you view them outside of the Boot Image Editor utility. They are downloaded from the network server and are loaded into the memory of the client PC at boot time. However, unlike boot image files, menu boot files do not necessarily boot the client PC immediately. Instead, with a menu boot file, a PC end user can select a specific boot option from a list of up to 16 available boot options or, if applicable, wait for the time-out interval, at which time the default boot image is automatically loaded.

The 16 possible boot options within a menu boot file can include boot image files that load different drivers and operating systems, other menu boot files, and the client PC’s hard drive. Setting up menu boot files that direct an end user to other menu boot files essentially means that the end user can have unlimited boot options.

Menu boot files created with Boot Image Editor normally have *.MNU or *.PXE extensions (in PXE environments, menu boot files are sometimes called network bootstrap programs). However, they were formerly known as multi-boot files, had *.MLT extensions, and were created with a DOS utility named MULTI_ED. Legacy multi-boot files can be maintained with Boot Image Editor. However, the first time that an older, MULTI_ED file is opened with Boot Image Editor, it will be updated to the current version and the file can no longer be opened with MULTI_ED.

The ability to create menu boot files is one of the most useful features in Boot Image Editor. Menu boot files are advantageous, for example, in academic institutions where multiple operating systems or tools are required and the client PC must be reset for different students and sessions, in environments in which multiple end users share the same client PC, and in software development and testing situations.

See Also…

Creating Menu Boot Files for Selecting Different Images at Boot Time


The Files Tab of the Create Boot Menu File Window

The Files tab of the Create Boot Menu File window enables you to create a menu boot file that is downloaded to a client PC at boot time instead of a single boot image file. A menu boot file references up to 16 boot option entries—boot image files, menu boot files, or a hard drive—from which an end user can choose a boot method that suits his or her needs at startup.

A red arrow indicates that the selected boot option has been set as the default boot file.

The buttons in this tab are as follows:

	Selecting the Add button opens the Edit Entry window, where you can add a boot image file, menu boot file, or hard drive to the menu boot file.  You can also type a brief description about or a label for a boot option by selecting this button. The text that you enter appears in the menu on the client PC screen instead of the boot image filename.  One boot image file can be used in several menu boot files or as a stand-alone boot image file for one or several client PCs.
	Selecting a boot option and selecting the Delete button enables you to remove the boot option from the list.  Deleting a boot option only removes the reference to the file, not the actual file.
	Selecting a boot option in the list and selecting this Edit button gives you access to the Edit Entry window. In the Edit Entry window, you can change the description for the entry, substitute a different boot option, or view the contents of a boot image file or menu boot file. Double-clicking a boot option gives you the same results as selecting this button.
	Selecting a boot option and then selecting the Default button causes the selected boot option to be automatically selected at the end of the wait-time interval. An asterisk in the menu at the client PC and a red arrow in the Create Boot Menu File window indicate a default boot option. After the wait time has elapsed, the default boot option (whether it be a boot image file, hard drive, or another menu boot file) is executed or used to boot the client PC without end user intervention. If no wait-time interval has been set in the Options tab, the default boot option is disregarded.
	Selecting a boot option and then selecting the View button opens the View Image File window, where you can view or manipulate the contents of the boot image file or menu boot file.
	Selecting the Save button displays a standard Windows file dialog box in which you can save and name the file you just created.  In TCP/IP and PXE environments, it is recommended that you save the menu boot file on your network server in the \TFTPBOOT directory or any other directory that contains active boot image files or menu boot files. In NetWare environments, you must save the menu boot file in the SYS:LOGIN directory.
	Selecting the Cancel button closes the Create Boot Menu File window without saving the menu boot file or its contents.
	Selecting the Help button gives you access to the Boot Image Editor online help.
See Also…

The Options Tab of the Create Boot Menu File Window

Edit Entry Window

Creating Menu Boot Files for Selecting Different Images at Boot Time


The Options Tab of the Create Boot Menu File Window

The Options tab of the Create Boot Menu File window enables you to:

•	Assign a meaningful title to the menu so that the end user recognizes it or knows how to proceed when it is encountered.

•	Set the wait-time interval before the default boot option is used automatically, without end user intervention.

•	In TCP/IP and PXE environments, indicate the default path for the boot image files and menu boot files so that you do not need to enter a root directory for all 16 boot options.

The fields in the Options tab are as follows:

Menu title:	The Menu title field displays the title of the boot menu as it appears at the client PC. Giving this boot menu file a title (such as “Accounting Department Boot Options”) will distinguish it from others in the enterprise. You can also use this field to type an instruction (such as “Select a boot option and press Enter”).
Menu wait time:	The Menu wait time field indicates the amount of time (in seconds) to display the menu before the default boot option is used to boot the client PC.  A value of 0 indicates that there is no time-out and that the boot menu will remain on the client PC screen until the end user selects one of the boot options and presses Enter.
Path (for TCP/IP and PXE files only):	The Path field contains the location of the boot files on the network server. It saves entering the path for each menu boot file entry.
System:	The System field shows the type of boot menu file you are working with—TCP/IP, NetWare, or PXE.
	Selecting the Save button displays a standard file dialog box in which you can save and name the file you just created.  In TCP/IP and PXE environments, it is recommended that you save the menu boot file on your network server in the \TFTPBOOT directory or any other directory that contains active boot image files or menu boot files. In NetWare environments, you must save the menu boot file in the SYS:LOGIN directory.
	Selecting the Cancel button closes the Create Boot Menu File window without saving the menu file shell or contents.
	Selecting the Help button gives you access to the Boot Image Editor online help.
See Also…

The Files Tab of the Create Boot Menu File Window

Edit Entry Window

Creating Menu Boot Files for Selecting Different Images at Boot Time


Edit Entry Window

The Edit Entry window enables you to select the boot options within a menu boot file so that you can modify them. You can also view the contents of an existing menu boot file.

The fields and buttons of the Edit Entry window are as follows:

Image file:	The Image file field enables you to type the name and location of the boot image file or menu boot file that you want to work with. This field can be completed by entering a path manually or by selecting the Browse button and locating an existing boot image file. If the Path field of the Create Boot Menu File window contains the relevant directory, enter only a filename here.
	The Browse button enables you to locate the boot image file or menu boot file that you want to add. You can embed menu boot files within other menu boot files so that the end user at the client PC has access to even more boot options.
	Selecting the View button after the Image file field has been filled opens the View Image File window and shows you the contents of the selected boot image file or menu boot file.
Boot from hard drive:	The Boot from hard drive option, if selected, indicates that the boot option is actually the client PC’s local hard drive.  If you add multiple hard drive entries to a menu boot file, the entries all attempt to boot from the same hard disk. Boot Image Editor does not support booting from multiple hard disks at the client PC.  Entries in the grayed Image file field are ignored if this box is selected.
Menu description:	The Menu description field contains a comment about the boot option. You can use this field to differentiate this boot method from the other boot options listed, describe the contents, indicate the primary owner of this boot option, or give instructions to the end user.  If this field is filled, the comment appears on the client PC screen instead of the filename of the boot image.
	The Help button gives you access to the Boot Image Editor online help.
	The OK button accepts your changes.
	Selecting the Cancel button closes the Edit Entry window, without saving changes.
See Also…

The Files Tab of the Create Boot Menu File Window

The Options Tab of the Create Boot Menu File Window


Creating Menu Boot Files for Selecting Different Images at Boot Time

The selection of different boot options is made possible by using a menu boot file (formerly known as a multi-boot file). With a menu boot file, the end user at the client PC can manually select an option from a menu or wait for the timeout interval to automatically select the default boot option.

Each menu boot file can contain up to 16 boot options, whether those options are boot image files, other menu boot files, or the client PC’s local hard drive. These *.MNU files are less than 6 KB, no matter how many boot options are included, because boot files are merely referenced from the menu boot file.

Menu boot files are optional in TCP/IP and NetWare environments, but they are mandatory in PXE environments. This topic describes menu boot files for TCP/IP and NetWare environments only.

To create a TCP/IP or NetWare menu boot file:

•	From the main Boot Image Editor window, select Create a TCP/IP menu boot file or select Create a NetWare menu boot file.

•	Select Add in the Files tab.

•	Select Browse to select an existing boot image file or menu boot file for the Image file field.

Or

Type the path and name of the boot image file or menu boot file in the Image file field.

Or

Select the Boot from hard drive option to enable the end user to boot from the hard drive at the client PC.

After selecting a boot image file or menu boot file, you can select View to look at the contents of the boot option and ensure that the boot option is actually designed for TCP/IP environments. In TCP/IP environments, the contents of the Image file field are somewhat dependent on the Path field.

•	Type a description for the boot image file, menu boot file, or hard drive boot option in the Menu description field.

If you choose not to enter a description, the filename of the boot image file is shown in the menu at the client PC.

•	Select OK.

•	Repeat steps 2 to 5 for each boot option you want to add.

•	Select a default boot option or set the menu boot file preferences.

•	Select Save and specify a filename and location for the new menu boot file.

Use the recommended *.MNU extension, or assign another extension. In TCP/IP environments, it is recommended that you save the menu boot file in the \TFTPBOOT (or another directory that contains all of the boot image files for this TCP/IP environment). In a NetWare environment, you must save the menu boot file in the SYS:LOGIN directory.

See Also…

Creating PXE Menu Boot Files

The Files Tab of the Create Boot Menu File Window

The Options Tab of the Create Boot Menu File Window

Selecting a Default Boot Option for the Menu Boot File

Setting Menu Boot File Preferences

Overview of Using Menu Boot Image Files

Adding Boot Options to an Existing Menu Boot File

Deleting Boot Options from a Menu Boot File


Selecting a Default Boot Option for the Menu Boot File

When a client PC and boot services are configured to load a menu boot file on the client PC at boot time, an end user can choose any one of the boot options. One of these boot options should be tagged as the default boot option so that no keystrokes are needed to start the client PC at the end of the wait-time interval.

To select a default boot option for a menu boot file:

•	Create a new menu boot file by selecting the Create TCP/IP menu boot file, Create NetWare menu boot file, or Create a PXE menu boot file button in the main Boot Image Editor window.

Or

From the main Boot Image Editor window, select Edit an existing file and open an existing menu boot file.

•	Select the boot option that you want to designate as the default.

•	Select Default.

A red arrow appears beside the default boot image file to indicate that it is the default boot image file.

•	Type or review the menu timeout duration in the Menu wait time field of the Options tab.

The wait time is measured in seconds. A value of zero indicates that end user intervention is always required to boot the client PC.

•	Select OK or Save, depending on the window in which you are working.

You have designated a new default boot option. The next time the end user powers on or restarts the client PC, the revised menu boot file (with the new default boot option) will be loaded. An asterisk will appear beside the default boot option.

See Also…

Creating Menu Boot Files for Selecting Different Images at Boot Time

Setting Menu Boot File Preferences

Overview of Using Menu Boot Image Files


Setting Menu Boot File Preferences

Menu boot files have customizable settings. When creating or modifying a menu boot file, you can:

•	Enter a title, label, or instructions for the menu boot file.

•	Set the default boot option and the default wait time.

•	Set the standard path for boot options within the menu boot file in TCP/IP or PXE environments.

To set menu boot file preferences:

•	Create a new menu boot file by selecting the Create TCP/IP menu boot file, Create a PXE menu boot file, or Create a NetWare image file button in the main Boot Image Editor window.

Or

From the main Boot Image Editor window, select Edit an existing file and open an existing menu boot file.

•	Select the Options tab.

•	Type a title, label, comment, or instructions for the menu boot file in the Menu file field.

At boot time, this text appears at the top of the boot menu window at the client PC. Provide a meaningful name that distinguishes this list of boot options from other menu boot file listings (such as the department that employs these bootstrap procedures or the type of bootstrap procedures that are run with this boot menu file), or type an instruction (such as “Select a boot method and then press Enter”).

•	After selecting a default boot option, in the Menu wait time field, type the time interval that you want to pass before the default boot option is automatically chosen to boot the client PC.

Entering a value of 0 indicates that you want the client PC end user to always choose a boot option manually.

•	If desired (and if you are working in TCP/IP or PXE environments), in the Path field, type the network server and directory that hosts the boot image files and menu boot files.

The path that you type here is added to the beginning of the selected boot image file when booting.

•	Depending on the window you are working in, select OK or Save.

See Also…

Creating Menu Boot Files for Selecting Different Images at Boot Time

Selecting a Default Boot Option for the Menu Boot File

Overview of Using Menu Boot Image Files

Adding Boot Options to an Existing Menu Boot File

Deleting a Boot Option from the Menu Boot File


Details on the Path Field

An incorrect boot option path is one of the primary causes of remoteboot problems. Keep the following points in mind when working with the Path field:

•	The Path field is only available in TCP/IP and PXE environments. It is not applicable in NetWare environments.

•	All boot image files and menu boot files must be stored in one directory (usually dictated by the TFTP protocol) on the network server. This directory must be accessible by TFTP so that it can transfer the boot image file or menu boot file to the client PC when it boots. The directory that you are using to store all of the boot image files and menu boot files is the path you should enter into the Path field.

•	Entering a path in this field will expedite the process of defining the contents of the menu boot file, but it could pose problems if you work in TFTP secure mode. It is recommended that you leave the Path field blank if you are running in TFTP secure mode.

•	When you complete the Path field, at boot time, the menu boot file adds the path to the beginning of all of the files that you reference in the menu boot file. In other words, there is no need to repeatedly type the path, for example, \TFTPBOOT in the Image file field of the Edit Entry window every time you add a boot option.


Using the Boot Menu from the Client PC

From the perspective of the end user, selecting a boot option via a menu boot file (or network bootstrap program) is simple. Provided the end user knows what results will be achieved using the boot options, initiating the desired operating system setup in a TCP/IP or NetWare environment merely involves selecting a menu item and pressing Enter—a few keystrokes. However, if you are working with a menu boot file in a PXE environment, a boot menu may not appear on-screen at all if there is only one boot option.

This help topic explains the specific tasks that are required of the end user and describes the successful implementation of a Boot Image Editor menu boot file.

To select a boot option at boot time:

•	Power on or restart the client PC.

The menu boot file executable is downloaded from the network server and run, and a list of boot options is displayed on the screen.

•	Evaluate your booting needs for this session.

Each boot image file should be customized for a certain type of situation. For example, within a menu boot file, you can include boot image files that map to the network differently, contain drivers relevant to certain hardware you implement occasionally, run various Pre-OS desktop management agents, load specific operating systems and configurations, and so on. Each boot option listed should be distinguishable by its unique label, filename, or comment.

•	Use the arrow keys to select the appropriate boot option, and then press Enter.

Or

Wait for the timeout interval to pass, and let the menu boot file execute the default boot option (which is identified with an asterisk) automatically.

Control is passed to the selected boot option, and the appropriate commands are executed. If another menu boot file is loaded, you will have to select a boot option from that list as well.

See Also…

Overview of Using Menu Boot Image Files

Creating Menu Boot Files for Selecting Different Images at Boot Time


A PXE Menu Boot File from the End-User's Perspective

Each end user with a PXE-enabled client PC must have access to a PXE menu boot file, even if that client PC will only boot from one boot image file. If there is only one boot option within that PXE menu boot file, this boot option will boot automatically, without the appearance of the boot menu and the end user’s intervention. However, if the end user has multiple boot options, a boot option must be selected at boot time. PXE menu boot files are known as network bootstrap programs.


A Sample Boot Menu

A menu boot file displayed at the client PC resembles the following illustration.


Adding Boot Options to an Existing Menu Boot File

You can increase the number of options an end user has at boot time by adding extra boot image files, other menu boot files, or the hard drive to a menu boot file. A maximum of 16 boot options can be displayed in the menu.

These instructions assume that you have already created and tested the boot image file or menu boot file that you want to add.

To add a boot option to a menu boot file:

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate and select the menu boot file that you want to change.

Change the contents of the Files of type field to Menu files or All files (depending on the three-character extension you gave the menu boot file) to view the menu boot files instead of the boot image files.

•	Select Add in the View Image File window.

•	Type the name (and path, if necessary) of the boot image file or menu boot file that you want to add in the Image file field.

Or

Select Browse and then locate and select the boot option you want to include.

Or

Select the Boot from hard drive option.

•	If desired, type a description for the boot option in the Menu description field.

•	Select OK to close the Edit Entry dialog box.

•	Select OK again to return to the main Boot Image Editor window.

The boot option has been added. The revised menu boot file will be used the next time the client PC end user (or end users) boots the relevant client PC (or PCs).

See Also…

Overview of Editing Boot Image Files

Adding Files to Boot Image Files


Deleting a Boot Option from the Menu Boot File

If you no longer want to provide a certain boot option to the end user, you can delete it from the reference list for the menu boot file.

To delete a boot image file, menu boot file, or hard drive boot option from within a menu boot file:

•	From the main Boot Image Editor window, select Edit an existing file.

•	In the Select image file dialog box, locate and open the menu boot file that you want to change.

Change the contents of the Files of type field to Menu files or All files (depending on the three-character extension you gave the menu boot file) to see the menu boot files instead of the boot image files.

•	Select the boot option that you want to delete.

•	Select Delete.

•	Select Yes to confirm.

You have deleted a boot option. One less option will be included in the listing of boot options at those client PCs accessing this menu boot file. Assign a new default boot option if necessary. Only the reference to the boot image file has been deleted from this menu boot file. The boot image file itself remains on the network server.

See Also…

Deleting Files within Boot Image Files

Adding Boot Options to an Existing Boot Menu File


Overview of Editing Boot Image Files

Once boot image files have been created, you can edit them within Boot Image Editor. The editing features within Boot Image Editor allow you to view, manipulate, and change the contents of boot image files or menu boot files without involving the original boot diskettes. Specifically, with Boot Image Editor, you can:

•	Add, modify, rename, extract, and delete files within a boot image file or a menu boot file.

•	Create, rename, and remove directories within boot image files.

•	Transfer the contents of boot image files to diskettes.

•	View and modify the properties of the image file—change the image from TCP/IP-ready to NetWare-ready, a writable file to a read-only file, and vice versa.

•	Open small text files (such as *.BAT, *.INI, *.LOG) with a simple text editor.

•	Review the capacity (normal or extended) or current size of a boot image file.

All of these tasks can be performed from a central network administration client PC with Boot Image Editor installed. There is no need to visit the client workstation, except to test the results or affects of your changes.

Keep in mind the impacts of manipulating an existing boot image. If you copy, rename, delete, or move a boot image file, for example, you might need to update the BOOTPTAB file, BOOTCONF.SYS file for NetWare, DHCP management tool, or other components to reflect the change.

See Also…

Making Boot Diskettes from Boot Image Files

View Image File Window

Viewing the Contents and Properties of Boot Image Files

Image Properties Window

Adding Files to Boot Image Files

Deleting Files from Boot Image Files

Editing Text Files within Boot Image Files

Renaming Files within Boot Image Files

Extracting Files within Boot Image Files

Creating Directories within Boot Image Files

Renaming Directories within Boot Image Files

Removing Directories within Boot Image Files

Adding Boot Options to an Existing Menu Boot File

Deleting Boot Options from the Menu Boot File


View Image File window

The View Image File window enables you to view the contents of boot image files in a user-friendly Windows interface.

The components of the View Image File windows are as follows:

File menu:	The File menu item enables you to add, delete, rename, edit, and extract (or copy) files within a boot image file. This menu item pertains to the files within the boot image file rather than the boot image file itself. Long filenames are not supported within boot image files.
Directory menu:	The Directory menu item allows you to add, rename, and delete directories within a boot image file. Long filenames are not supported within boot image files.
Floppy menu:	The Floppy menu item allows you to create a standard boot diskette from a boot image file.
Properties menu:	The Properties menu item displays the characteristics of the open boot image file and provides a means to change them. This button does not pertain to the files within the boot image file—it pertains to the boot image file itself.
Capacity field:	The Capacity field indicates the maximum size of the boot image file. The maximum size was set by the person who created the boot image file. Common sizes are normal (1.44 MB) and extended (2 to 16 MB).
Free field:	The Free field indicates the amount of room available until you reach the maximum capacity.
	The Add button appends a bootstrap file, configuration file, device driver, or any other file type to the boot image file. You can also drag and drop files to add them.
	The Delete button enables you to remove files or directory from within a boot image file.
	The Extract button enables you to copy the selected file(s) and use it in another location. The duplicate file uses the same name as the original file, and the original file remains intact.
	The Up button enables you to maneuver between directories and subdirectories quickly. If you are viewing the contents of a subdirectory within the boot image file, you can quickly move to the root directory by selecting this button.
	The Properties button permits you to view and modify the properties of the boot image file rather than the contents of the boot image file.
	The Floppy button enables you to make a boot diskette from the current boot image file. This feature is only useful if the contents of the boot image file will fit on a regular floppy diskette (up to 1.44 MB).
	The Help button gives you access to the Boot Image Editor online help.
	The Close button closes the Edit Image Files window and takes you to the main Boot Image Editor window.

See Also…

Overview of Editing Boot Image Files

Viewing the Contents and Properties of Boot Image Files

Image Properties Window


The Files Tab of the View Menu File Window

The View Image File window enables you to view the contents of boot image files in a user-friendly Windows interface. There are two tabs in this window: The Files tab and the Options tab.

The components of the Files tab are as follows:

	Selecting the Add button opens the Edit Entry window, where you can add a boot image file, menu boot file, or hard drive to the boot menu file.  You can also type a brief description about or a label for a boot option by selecting this button. The text that you enter appears in the menu on the client PC screen instead of the boot image filename.  One boot image file can be used in several menu boot files or as a stand-alone boot image file for one or several client PCs.
	Selecting a boot option and then selecting the Delete button enables you to remove the boot option from the list.  Deleting a boot option only removes the reference to the file, not the actual file.
	Selecting a boot option in the list and selecting this Edit button gives you access to the Edit Entry window. In the Edit Entry window, you can change the description for the entry, substitute a different boot option, or view the contents of a boot image file or menu boot file. Double-clicking a boot option gives you the same results as selecting this button.
	Selecting a boot option and then selecting the Default button causes the selected boot option to be automatically selected at the end of the wait-time interval. An asterisk in the menu at the client PC and a red arrow in the View Image File window indicate a default boot option. After the wait time has elapsed, the default boot option (whether it be a boot image file, hard drive, or another menu boot file) is executed or used to boot the client PC without end user intervention. If no wait-time interval has been set in the Options tab, the default boot option is disregarded.
	Selecting a boot option and then selecting the View button opens another View Image File window, where you can view or manipulate the contents of the selected boot image file.
	Selecting the OK button saves the file you just viewed or modified.
	Selecting the Cancel button closes the View Image File window without saving the menu boot file or its contents.
	Selecting the Help button gives you access to the Boot Image Editor online help.

See Also…

The Options Tab of the View Menu File Window

Overview of Editing Boot Image Files

Viewing the Contents and Properties of Boot Image Files

Image Properties Window


The Options Tab of the View Menu File Window

The View Image File window enables you to view the contents of boot image files in a user-friendly Windows interface. There are two tabs in this window: The Files tab and the Options tab.

The components of the Options tab are as follows:

Menu title:	The Menu title field displays the title of the boot menu as it appears at the client PC.
Menu wait time:	The Menu wait time field indicates the amount of time (in seconds) to display the menu before the default boot option is used to boot the client PC.  A value of 0 indicates that there is no time-out and that the boot menu will remain on the client PC screen until the end user selects one of the boot options and presses Enter.
Path (for TCP/IP and PXE files only):	The Path field contains the location of the boot image files on the network server. It saves entering the path for each menu boot file entry.
System:	The System field shows the type of menu boot file you are working with—TCP/IP, NetWare, or PXE.
	Selecting the OK button saves the file you just viewed or modified.
	Selecting the Cancel button closes the View Image File window without saving the menu file shell or contents.
	Selecting the Help button gives you access to the Boot Image Editor online help.

See Also…

The Files tab of the View Menu File Window

Overview of Editing Boot Image Files

Viewing the Contents and Properties of Boot Image Files

Image Properties Window


Viewing the Contents and Properties of Boot Image Files

You cannot view the contents and configuration of a boot image file from Windows Explorer or other file management tools, but you can with Boot Image Editor. There are two ways to view the contents and properties of an existing boot image file. Both methods are explained below.

Option 1—From the Main Boot Image Editor Window

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate the boot image file that you want to view and then double-click it.

The View Image File window appears, with the contents of the boot image file in view.

•	Select Properties from the menu bar.

The Image Properties window appears.

You have viewed the contents of the current boot image file. Select Close twice to hide the Image Properties and the Edit Image Files window.

Option 2—While Creating a Menu Boot (Multi-Boot) File

•	Add a boot image file to the menu boot file list.

Or

Double-click a boot image file that appears in the menu boot file list.

The Edit Entry window appears.

•	Select View.

The View Image File window appears, with the files within the image in view.

•	Select Properties from the menu bar.

The Image Properties window appears.

You have viewed the composition of a boot image file. Select Close to hide the Image Properties window, select Close to hide the View Image File window, and then select Cancel to return to the main menu boot file window.

See Also…

Overview of Editing Boot Image Files

View Image File Window

Image Properties Window


Image Properties Window

The Image Properties window displays the characteristics of the current boot image file. Rather than revealing the contents of that boot image file, this window provides information on the higher-level options that were selected, such as whether the boot image file was intended for TCP/IP or NetWare systems. After you view the properties of the current boot image file, you have the option to change them.

The options of the Image Properties window are as follows:

System:	The System option indicates the network environment for which the boot image file was intended: NetWare or TCP/IP. PXE is not an option here because PXE booting is based on TCP/IP boot image files.
Pre-OS:	The Pre-OS option identifies whether desktop management utilities were enabled to work with this boot image file. When this option reads “Yes,” the ultimate operating system is launched from the local hard drive instead of a boot image file.
Banner:	The Banner option indicates whether 3Com Pre-OS banner is displayed. This option is relevant only when Pre-OS has been enabled.
Writable (for TCP/IP boot image files only):	The Writable option shows whether the boot image file is writable or read-only. If the boot image file is writable, the system can write to the boot image file as a RAM disk while the PC boots. The Writable option does not appear if the boot image file was created for a NetWare environment.
Loader (for NetWare boot image files only):	The Loader option indicates whether the entire boot image file will be loaded into the client PC’s memory before booting. You must use FREEMEM, a memory management utility available on the installation disk, if the Loader feature is enabled. This option does not appear for TCP/IP boot image files.
Created:	The Created field displays the date that the boot image file was created from a boot diskette.
Modified:	The Modified field shows the last date that the current boot image file contents or properties were updated.
Header Version (for TCP/IP boot image files only):	The Header Version field is used by the 3Com Technical Support Department to troubleshoot TCP/IP boot image files.
	The Help button gives you access to the Boot Image Editor online help.
	The Close button closes the Image Properties window and returns you to the View Image File window.
See Also…

Overview of Editing Boot Image Files

Viewing the Contents and Properties of Boot Image Files

View Image File Window


Changing Boot Image File Properties

From Boot Image Editor, you can change the qualities of a boot image file. You can modify most of a boot image file’s properties, but you cannot change the memory usage and capacity related details. For example, you can convert a boot image file designed for NetWare environments to one that runs in TCP/IP environments (and vice versa) or enable and disable Pre-OS settings by following these instructions.

The process for changing TCP/IP, NetWare, and PXE boot image files is fundamentally the same. The original boot image file will be overwritten with the new properties unless you make a copy of it.

To change the properties of an existing boot image file:

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate the boot image file that you want to modify and then double-click it.

The View Image File window appears, with the contents of the boot image file in view.

•	Select Properties.

•	Select Change.

•	Select the appropriate options.

•	Select OK.

See Also…

Overview of Editing Boot Image Files

Change Image Properties Window

Setting Menu Boot File Preferences


Change Image Properties Window

The Change Image Properties window enables you to change most of the characteristics of the boot image file that you set when you first created the boot image file. You must access this window from the Image Properties window.

The options of the Change Image Properties window are as follows:

Change System

NetWare:	Selecting the NetWare option makes the current boot image file appropriate for NetWare environments.
TCP/IP:	Selecting the TCP/IP option makes the current boot image file appropriate for TCP/IP environments.
Change Options

Pre-OS:	Selecting Yes in the Pre-OS option allows you to run desktop management agents (such as virus scanners and file compare and repair utilities) before the ultimate operating system is loaded from the PC’s hard drive. Selecting No in the Pre-OS option indicates that you want the client PC to launch the end user’s preferred operating system immediately, without executing any Pre-OS activities beforehand.
Banner:	This option is only available and relevant when you have selected Pre-OS. Selecting Yes in the Banner option indicates that you want to hide the 3Com Pre-OS banner from the end user.  Selecting No in the Banner option means that the 3Com Pre-OS banner will be shown on the client PC screen.
Writable (for TCP/IP images only):	Selecting Yes in the Writable option enables you to create a writable boot image file for use in TCP/IP environments. Selecting No in the Writable option means that the TCP/IP image is read-only, and memory requirements will be minimized.
Loader (for NetWare images only):	Selecting Yes in the Loader option forces a NetWare boot image file to be loaded completely into memory before the client PC begins to boot.  Selecting No in the Loader option means that you want to download the files within the boot image file only as they are needed. The client PC begins to boot before the entire boot image file is stored in its memory, so it communicates more frequently with the network server to access the contents of the boot image file.
	The Help button gives you access to the Boot Image Editor online help.
	The OK button enables you to save changes and close the window.
	The Cancel button enables you to close the window without making changes.
See Also…

Changing Boot Image File Properties

Image Properties Window

Overview of Editing Boot Image Files


Making Boot Diskettes from Boot Image Files

With Boot Image Editor, not only can you create a boot image file from a diskette, you can, conversely, create a boot diskette from a boot image file. Transferring the contents of the boot image file to a DOS-formatted diskette may be useful for:

•	Making a backup of a boot image file.

•	Ensuring the client PC can boot when network access is denied.

•	Creating a floppy as a template for a new boot image file.

•	Extracting all of the files within a boot image at once.

Boot diskettes can be created from boot image files only if the contents of the boot image file have the same capacity as a single diskette. Large boot image files (over 1.44 MB) cannot be converted to a boot diskette.

The original boot image file on the network server remains functional when you follow the steps below—all the files within the boot image file are merely copied and pasted onto the diskette. The process for TCP/IP, NetWare, and PXE environments is the same.

To transfer a boot image file to a diskette:

•	Insert a blank, formatted diskette into your floppy drive.

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate the boot image file that you want to transfer to diskette and double-click it.

The View Image File window appears, with the contents of the boot image file in view.

•	Select Floppy.

•	Select Create Disk.

Boot Image Editor verifies that the diskette is the same or of greater capacity as the boot image file. All of the files on the diskette are erased. The diskette becomes an exact copy of the boot image file.

•	Select Done.

You have copied the chosen boot image file to a diskette. You can insert this diskette into a drive at a client PC and boot from it, if desired.

See Also…

Overview of Editing Boot Image Files

Creating TCP/IP Boot Diskettes

Creating NetWare Boot Diskettes

Creating PXE Boot Diskettes


Converting Pre-OS Images to Regular Boot Image Files

Usually Pre-OS images are set up to temporarily boot DOS, perform the required maintenance tasks, and then return control to the local drive to start the ultimate operating system—the operating system that the end user employs. Because Pre-OS images can resemble regular boot image files in terms of content, with a few minor changes in the Boot Image Editor, you can configure a PC to boot from the network server instead of from a local drive.

The procedure to change a TCP/IP, PXE, and NetWare Pre-OS file to a boot image file is the same.

You can also convert an existing boot image file to a Pre-OS image file.

To convert a Pre-OS image to a boot image file:

•	From the main Boot Image Editor window, select Edit an existing image.

•	Locate and double-click the Pre-OS image you want to convert.

•	Select Properties.

•	Select Change.

•	Select the No option in the Pre-OS row.

•	Select OK and then select Close.

•	Review the contents of the new boot image file to ensure that they are appropriate given the change of status.

You will have to remove references to PBOOT in the AUTOEXEC.BAT; if you do not remove PBOOT, you might see a message explaining that Pre-OS state is not saved.

•	Select Close again.

•	Boot the PC to verify that it is starting the operating system indicated in the boot image file instead of from the local drive.

See Also…

Overview of Pre-OS Technology

Defining Boot Image File Content for Pre-OS Connectivity


Adding Files to Boot Image Files

A boot image file can contain core operating system files, configuration and setting files, device drivers, utilities (such as DRVSPACE.BIN, SCANDISK.EXE, HIMEM.SYS), and references to or copies of Pre-OS desktop management programs (such as virus scanners, file comparison and recovery tools). You can add any type of file to a boot image file, but keep in mind the size of the overall boot image file. Boot Image Editor will not allow you to exceed the initially assigned boot image file capacity (normal—1.44 MB or extended—up to 16 MB).

To add a file to a boot image file:

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate and then double-click the boot image file that you want to add to.

The View Image File window appears.

•	If necessary, double-click the appropriate boot image file subdirectory to which you want to add the file.

•	From the File menu, select Add.

Or

Select the Add button.

Or

Drag and drop the desired file from a file management tool.

•	Locate and then double-click the file that you want to add to the boot image file.

You have added a file to the boot image file. Select Close to hide the View Image File window and return to the main Boot Image Editor window or repeat steps 3 to 5 for all the files that you want to add.

See Also…

Adding Boot Options to an Existing Menu Boot File


Deleting Files from Boot Image Files

If a file is no longer required to boot a client PC, you can delete it from the boot image file. Some files, however, should not be deleted from the boot image file, just as they should not be removed from a boot diskette. To make sure end users can continue to boot successfully, consider making a backup of the boot image file before manipulating its contents.

To delete a device driver, configuration file, or any other type of file from a boot image file:

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate and then double-click the boot image file that contains the file or files that you want to delete.

The View Image File window appears, with the contents of the image file in view.

•	Select the file or files that you want to remove.

If you want to select multiple files, press the Ctrl key while selecting the relevant files. Hidden and standard files are shown in this window.

•	From the File menu, select Delete.

Or

Select the Delete button.

Or

Right-click and choose Delete from the popup menu.

•	Select Yes to confirm.

You have deleted the selected bootstrap file(s) from the boot image file. Select Close to hide the View Image File window.

See Also…

Extracting Files within Boot Image Files

Making Boot Diskettes from Boot Image Files

Deleting Boot Options from a Menu Boot File


Editing Text Files within Boot Image Files

Boot Image Editor includes a simple text editor to enable you to change the contents of small ASCII text files (up to 64 KB) within a boot image file. If the file that you want to edit is larger than 64 KB, you can extract it from the boot image file, open it in another ASCII text editor or word processor, edit and save it, and add it to the boot image file again. The instructions that follow describe how to edit a file under 64 KB.

To edit a text file from Boot Image Editor:

•	From the main Boot Image Editor, select Edit an existing file.

•	Locate and then double-click the boot image file that contains the file or files that you want to edit.

The View Image File window appears, with the contents of the boot image file in view.

•	Select the file that you want to edit.

•	From the File menu, select Edit.

Or

Right-click and select Edit from the popup menu.

The text editor opens, and then the text that comprises the file appears onscreen. If the file does not have a common extension for text files, you will be prompted to confirm that you want to edit it anyway. If you receive this prompt, select Yes to continue.

•	Change the text as needed.

Copy, paste, cut, undo, and delete functions are available under the Edit menu.

•	Select OK to save your changes.

You return to Boot Image Editor.

You have edited a text, configuration, or log file within a boot image file. Select Close to hide the View Image File window.

See Also…

Overview of Editing Boot Image Files

Changing Boot Image File Properties


Renaming Files within Boot Image Files

You can rename any of the files within a boot image file at any time for organizational reasons, backup purposes, or any other rationale. However, be careful not to alter one of the mandatory files (for example, COMMAND.COM, MSDOS.SYS, and IO.SYS when booting Windows) that may be required to boot the client PC.

To rename a file within a boot image file:

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate and then double-click the boot image file that you want to modify.

The View Image File window appears, with the contents of the boot image file in view.

•	Select the file that you want to rename.

•	From the File menu, select Rename.

Or

Right-click and select Rename from the popup menu.

•	Type the new name of the file.

The filename is limited to eight characters, with a three-character extension.

•	Select OK.

You have renamed a file within a boot image file. Select Close to hide the View Image File window and return to the main Boot Image Editor window.

See Also…

Renaming Directories within Boot Image Files

Editing Text Files within Boot Image Files


Extracting Files from Boot Image Files

“Extracting” refers to making a copy of a selected file. Extracting is helpful, for example, when you want to duplicate a file for use in another boot image file or a boot diskette. You can extract one file or multiple files at once using the instructions that follow, or you can extract all of the files by making a floppy from a boot image file.

To extract a file or files from within a boot image file:

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate and then open the boot image file that contains the file or files that you want to extract.

The View Image File window appears, with the contents of the boot image file in view.

•	Select the file or files that you want to copy.

If you want to select multiple files, press the Ctrl key while selecting the relevant files. Hidden and standard files are shown in this window.

•	From the File menu, select Extract.

Or

Select the Extract button.

Or

Right-click and select Extract from the popup menu.

The Browse for Folder window appears.

•	Locate and then double-click the drive and directory to which you want to add the extracted file or files.

•	Select OK.

After the files have been pasted in the new location, you see the View Image File window again. Boot Image Editor gives the duplicate files identical names as the original files; you cannot assign new filenames in Boot Image Editor.

You have extracted a file or files from the current boot image file. Select Close to return to the main Boot Image Editor window.

See Also…

Deleting Files from Boot Image Files

Deleting a Boot Option from the Menu Boot File

Renaming Files within Boot Image Files


Creating Directories within Boot Image Files

To organize the contents of a boot image file, you can create directories within it. Booting from a boot image file that contains subdirectories is no different than booting from a boot image file without directories.

To create a directory within an existing boot image file:

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate the boot image file that you want to modify and then double-click it.

The View Image File window appears, with the contents of the boot image file in view.

•	Select Directory and then Create from the menu bar.

•	Type the name of the directory, and then select OK.

You are limited to the 8.3 format—the files and directories within a boot image file cannot have long filenames.

•	Double-click the new directory name to open it.

•	Select File and then Add to append a file from any drive to the new directory.

If you want to move a file that is already contained in the image to the new directory, you have to delete or extract the file, open the new directory, and then add it again.

•	Locate the file that you want to add to the new directory and double-click on it.

•	Select Close to quit editing the contents of the boot image file.

Or

Double-click <…> (or select the Up button) to return to the root directory of the boot image file.

You have created a directory within a boot image file. Select Close to return to the main Boot Image Editor window.

See Also…

Renaming Directories within Boot Image Files

Removing Directories within Boot Image Files


Renaming Directories within Boot Image Files

You can rename a directory within a boot image file without creating a new boot diskette or creating a new boot image file. Renaming a directory usually has no impact on the way that the client PC boots, but it may improve organization and expedite maintenance if you frequently update the contents of one of the subdirectories.

To rename a directory within a boot image file:

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate the boot image file that you want to rename and then double-click it.

The View Image File window appears, with the contents of the boot image file in view.

•	Select the directory that you want to rename.

•	Select Directory and then Rename from the menu bar.

Or

Right-click and select Rename from the popup menu.

•	Type the new name, and then select OK.

You are limited to the 8.3 format—the files and directories within a boot image file cannot have long filenames.

You have renamed a directory within a boot image file. Select Close in the View Image File window to return to the main Boot Image Editor window.

See Also…

Creating Directories within Boot Image Files

Removing Directories within Boot Image Files


Removing Directories within Boot Image Files

You can delete directories within boot image files at any time, as long as the directory is empty.

To remove a directory within a boot image file:

•	From the main Boot Image Editor window, select Edit an existing file.

•	Locate the boot image file that you want to modify and then double-click it.

The View Image File window appears, with the contents of the boot image file in view.

•	Select the directory that you want to delete.

•	Select Directory and then Remove from the menu bar.

Or

Right-click and select Remove from the popup menu.

You have deleted an empty directory from the boot image file. Continue manipulating the contents of the boot image file or select Close in the View Image File window to return to the main Boot Image Editor window.

See Also…

Creating Directories within Boot Image Files

Renaming Directories within Boot Image Files


Network Selection Window

The Network Selection window allows you to select a network environment to streamline the Boot Image Editor user interface specifically for your needs. The option(s) that you select in this window changes the appearance of the main Boot Image Editor window and helps to ensure that you create the appropriate type of boot image files and menu boot files for your environment. If your network uses multiple protocols, select the option that matches the type of network server on which the boot image files and menu boot files will reside.

This window is accessible from the Boot Image Editor system menu and during the Boot Image Editor first-time installation process. You can change these settings at any time—your selections here do not affect the contents of existing boot image files or menu boot files in any way.

TCP/IP:	When selected, the TCP/IP option indicates that you want to create and edit boot image files and menu boot files for TCP/IP environments. This option controls access to the Create a TCP/IP or PXE image file button and the Create a TCP/IP menu boot file button on the main Boot Image Editor window.
NetWare:	When selected, the NetWare option indicates that you want to create and edit boot image files and boot menu files for use in NetWare environments. This option controls access to the Create a NetWare image file button and the Create a NetWare menu boot file button on the main Boot Image Editor window.
PXE:	When selected, the PXE option indicates that you want to create and edit boot image files and menu boot files for the Preboot eXecution Environment, which is part of the Wired for Management (WfM) specification. This option controls access to the Create a TCP/IP or PXE image file button and the Create a PXE menu boot file button. If necessary, refer to the following web sites for more information on WfM and PXE: http://www.3com.com/news/releases/pr99/mar0499b.html or http://developer.intel.com/ial/WfM
	Selecting the OK button saves your selections and closes the window. The OK button does not appear during installation.
	Selecting the Cancel button closes the window without saving your changes. During installation, selecting Cancel ends the installation process.
	Selecting the Back button during installation returns you to the Boot Image Editor Welcome window. This button does not appear after installation is complete.
	Selecting the Next button during installation advances you to the File Associations window. This button does not appear after installation is complete.
The Edit an existing file, Help, and Exit buttons always appear on the main Boot Image Editor window. You cannot enable and disable those buttons.

See Also…

Changing the Boot Image Editor Network Selections

File Associations Window


Changing the Boot Image Editor Network Selections

Boot Image Editor creates and edits boot image files and menu boot files for TCP/IP, NetWare, and PXE environments. To successfully remoteboot with a boot image file or menu boot file, the file must be designed for the host network server. If you change network protocols or move the images to a new location (for example, from NetWare to TCP/IP), you can convert the boot image files to match the new protocol and change the Boot Image Editor interface to ensure that you create images of the correct type.

To change the network selections and the appearance of the main Boot Image Editor window:

•	Launch Boot Image Editor.

•	Select the system menu button in the main Boot Image Editor window.

•	Select Networks.

The Network Selection window appears.

•	Select the appropriate options.

•	Select OK.

The appearance and functionality of the main Boot Image Editor window changes immediately based on your selections.

You have changed the network selections. Existing boot image files and menu boot files are still accessible and intact.

See Also…

Network Selection Window

Changing Boot Image File Properties


File Associations Window

If you want to be able to double-click boot image files within Windows (for example, with Windows Explorer) and open Boot Image Editor automatically, you should complete the fields in this window. Completing this window means that you do not need to manually make file and program associations in the View menu of My Computer or Windows Explorer for Boot Image Editor. Standard file extensions used by Boot Image Editor are *.IMG, *.SYS, *.MNU, and *.PXE.

This window is only available during the Boot Image Editor first-time installation procedure.

Enable file associations:	When the Enable file associations option is selected, you can create file associations for Boot Image Editor.  If this option is not selected, the next field is irrelevant.
File extensions to associate to Image Editor:	This field, by default, contains the standard file extensions for the files created with Boot Image Editor (and earlier DOS versions of the program—IMAGEGEN/IMGGEN, MULTI_ED). If you plan to use extensions other than the predetermined ones, consider entering them in this field so that they will be associated with Boot Image Editor. Other programs and files might use the same default extensions. If you have made previous file associations with any of the extensions presented, delete them from this field.  Following are explanations of the default file extensions:
	*.IMG	IMG is the default extension for TCP/IP and PXE boot image files.
	*.SYS	SYS is the default extension for NetWare boot image files.  Keeping this extension usually generates a message because Windows normally registers the *.SYS extension without associating it with a particular application. However, *.SYS is a commonly used extension that may already be associated to another application on your PC.  When you see the message, you will have an opportunity to overwrite the existing Windows file-type association. You should be safe in replacing the current association, unless you have deliberately associated *.SYS with another application.
	*.MNU	MNU is the default extension for TCP/IP and NetWare menu boot files.
	*.MLT	MLT is the default extension for multi-boot files that were created with the MULTI_ED legacy DOS utility. If you have existing multi-boot files that you want to view and edit with Boot Image Editor, keep the MLT extension.
	*.PXE	PXE is the default extension for PXE menu boot files (or network bootstrap programs), which are mandatory in PXE environments.
	Selecting the Back button returns you to the Network Selection window.
	Selecting the Finish button completes the installation and configuration process for Boot Image Editor.
	Selecting the Cancel button ends the installation and configuration process for Boot Image Editor.
See Also…

Making File Associations for Boot Image Editor


Making File Associations for Boot Image Editor

By default, Boot Image Editor creates files with the following extensions: *.IMG, *.SYS, *.MNU, *.MLT, *.PXE. To launch Boot Image Editor automatically when you double-click one of these file types (or any other file extension that you specify) in Windows, you need to create a file association. You can create file associations during the Boot Image Editor first-time installation process or from My Computer or Windows Explorer.

During Installation

When you are configuring Boot Image Editor during the installation process, the File Associations window appears. In this window, you can quickly make file associations between the program and any desired file extension.

To make Windows file associations while installing Boot Image Editor:

•	Ensure that there is a check mark next to the Enable file associations option of the File Associations window.

•	Review the default extensions in the File extensions to associate to Image Editor field.

•	If desired, remove any extension that you are using with other programs.

•	If desired, add any other extensions that you think you will be using to manage boot image files or menu boot files.

•	Select Finish.

You have installed Boot Image Editor and made file associations. You can change the file associations later by following the instructions in the After Installation section below.

After Installation

The File Association window in Boot Image Editor appears only during the first-time installation process. Instead of reinstalling Boot Image Editor to create or change a file association, you can use regular Microsoft Windows features.

To create or modify a Boot Image Editor file association:

•	Launch My Computer or Windows Explorer.

•	From the View menu, select Options, and then select the File Types tab.

•	Follow the instructions provided in the Microsoft Windows documentation.

See Also…

File Associations Window


Obtaining Technical Support

3Com provides easy access to technical support information through a variety of services:

•	Online Technical Services from 3Com

•	Support from Your Network Supplier

•	Telephone Support from 3Com

If necessary, you can also return products for repair.

Information contained in this online help is correct at the time of publication. For the very latest information, 3Com recommends that you access the 3Com Corporation World Wide Web site.

See Also…

Boot Image Editor Troubleshooting and FAQs


Online Technical Services from 3Com

3Com offers worldwide product support 24 hours a day, 7 days per week, through the following online systems:

•	3Com World Wide Web site

•	3Com Knowledgebase Web Services

•	3Com FTP site

•	3Com Bulletin Board Service (3ComBBS)

•	3ComFactsSM Automated Fax Service

See Also…

Boot Image Editor Troubleshooting and FAQs

Support from Your Network Supplier

Telephone Support from 3Com

Returning Products for Repair


3Com World Wide Web Site

Access the latest networking information on the 3Com Corporation World Wide Web site by entering this URL into your Internet browser:

http://www.3com.com/

This service provides access to online support information such as technical documentation and a software library, as well as support options ranging from technical education to maintenance and professional services.


3Com Knowledgebase Web Services

This interactive tool contains technical product information compiled by 3Com expert technical engineers around the globe. Located on the World Wide Web at http://knowledgebase.3com.com this service gives all 3Com customers and partners complementary, round-the-clock access to technical information on most 3Com products.


3Com FTP Site

Download drivers, patches, software, and MIBs across the Internet from the 3Com public FTP site. This service is available 24 hours a day, 7 days a week.

To connect to the 3Com FTP site, enter the following information into your FTP client:

•	Hostname:ftp.3com.com

•	Username: anonymous

•	Password: <your Internet e-mail address>

Note: You do not need a username and password with Web browser software such as Netscape Navigator and Internet Explorer.


3Com Bulletin Board Service

The 3Com BBS contains patches, software, and drivers for 3Com products. This service is available through analog modem or digital modem (ISDN) 24 hours a day, 7 days a week.

Access by Analog Modem

To reach the service by modem, set your modem to 8 data bits, no parity, and 1 stop bit. Call the telephone number nearest you:

Country	Data Rate	Telephone Number
Australia	up to 14400 bps	61 2 9955 2073
Brazil	up to 28800 bps	55 11 5181 9666
France	up to 14400 bps	33 1 6986 6954
Germany	up to 28800 bps	4989 62732 188
Hong Kong	up to 14400 bps	852 2537 5601
Italy	up to 14400 bps	39 2 27300680
Japan	up to 14400 bps	81 3 5977 7977
Mexico	up to 28800 bps	52 5 520 7835
P.R. of China	up to 14400 bps	86 10 684 92351
Taiwan, R.O.C.	up to 14400 bps	886 2 377 5840
U.K.	up to 28800 bps	44 1442 438278
U.S.A.	up to 53333 bps	1 847 262 6000
Access by Digital Modem

ISDN users can dial in to the 3Com BBS using a digital modem for fast access up to 64 Kbps. To access the 3Com BBS using ISDN, call the following number:

1 847 262 6000


3ComFacts Automated Fax Service

The 3ComFacts automated fax service provides technical articles, diagrams, and troubleshooting instructions on 3Com products 24 hours a day, 7 days a week.

Call 3ComFacts using your touch-tone telephone:

1 408 727 7021


Support from Your Network Supplier

If you require additional assistance, contact your network supplier. Many suppliers are authorized 3Com service partners who are qualified to provide a variety of services, including network planning, installation, hardware maintenance, application training, and support services.

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.

•	Diagnostic error messages.

•	Details about recent configuration changes, if applicable.

See Also…

Boot Image Editor Troubleshooting and FAQs

Online Technical Services from 3Com

Telephone Support from 3Com

Returning Products for Repair


Telephone Support from 3Com

If you are unable to obtain assistance from the 3Com online technical resources or from your network supplier, 3Com offers technical telephone support services. To find out more about your support options, call the 3Com technical telephone support phone number at the location nearest you.

When you contact 3Com 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.

•	Diagnostic error messages.

•	Details about recent configuration changes, if applicable.

Select a geographic area to obtain the correct technical telephone support numbers:

•	Asia Pacific Rim

•	Europe

•	Latin America

•	North America

See Also…

Boot Image Editor Troubleshooting and FAQs

Online Technical Services from 3Com

Support from Your Network Supplier

Returning Products for Repair


Telephone Support for Asia and the Pacific Rim

Country	Telephone Number
Australia	1 800 678 515
Hong Kong	800 933 486
India	+61 2 9937 5085
Indonesia	001 800 61 009
Japan	0031 61 6439
Malaysia	1800 801 777
New Zealand	0800 446 398
Pakistan	+61 2 9937 5085
Philippines	1235 61 266 2602
P.R. of China	10800 61 00137  Or 021 6350 1590
Singapore	800 6161 463
S. Korea (general) From Seoul, Korea	00798 611 2230 (0)2 3455 6455
Taiwan, R.O.C.	0080 611 261
Thailand	001 800 611 2000


Telephone Support for Europe

Country	Telephone Number
From anywhere in Europe, call:	+31 (0)30 6029900 phone +31 (0)30 6029999 fax

From the following European countries, you may use the toll-free numbers:

Austria	06 607468
Belgium	0800 71429
Denmark	800 17309
Finland	0800 113153
France	0800 917959
Germany	0130 821502
Hungary	00 800 12813
Ireland	1 800 553117
Israel	1800 9453794
Italy	1678 79489
Netherlands	0800 0227788
Norway	800 11376
Poland	0800 3111206
Portugal	0800 831416
South Africa	0800 995014
Spain	900 983125
Sweden	020 795482
Switzerland	0800 55 3072
U.K.	0800 966197


Telephone Support for Latin America

Country	Telephone Number
Argentina	AT&T +800 666 5065
Brazil	0800 13 3266
Chile	1230 020 0645
Columbia	98012 2127
Mexico	01 800 2273
Peru	AT&T +800 666 5065
Puerto Rico	800 666 5065
Venezuela	AT&T +800 666 5065


Telephone Support for North America

For telephone technical support in North America, call:

1 800 876 3266


Returning Products for Repair

Before you send a product directly to 3Com for repair, you must first obtain an authorization number. Products sent to 3Com without authorization numbers will be returned to the sender unopened, at the sender’s expense.

To obtain an authorization number, call or fax:

Country/Region	Telephone Number	Fax Number
Asia, Pacific Rim	+65 543 6500	+65 543 6348
Europe, South Africa, and Middle East	+31 30 6029900	+31 30 6029999
Latin America	1 408 326 2927	1 408 326 3355
U.S.A. and Canada	1 800 527-8677	1 408 326 7120 (not toll free)

From the following countries, you may use the toll-free numbers. Select option 2 and then option 2.

Country	Telephone Number
Austria	0800 297468
Belgium	0800 71429
Denmark	800 17309
Finland	0800 113153
France	0800 917959
Germany	0800 1821502
Hungary	00800 12813
Ireland	1800553117
Israel	1800 9453794
Italy	1678 79489
Netherlands	0800 0227788
Norway	800 11376
Poland	00800 3111206
Portugal	0800 831416
South Africa	0800 995014
Spain	900 983125
Sweden	020 795482
Switzerland	0800 55 3072
U.K.	0800 966197
See Also…

Boot Image Editor Troubleshooting and FAQs

Online Technical Services from 3Com

Support from Your Network Supplier

Telephone Support from 3Com


Boot Image Editor Troubleshooting and FAQs

This topic covers some of the common error messages that you can receive while working with Boot Image Editor. Refer to the 3Com Managed PC Boot Agent User Guide if you have trouble with the 3Com Managed PC Boot Agent or downloading the image, or refer to the relevant documentation for your NIC or boot ROM.

If you do not find the answers you need from this help system, access one of the 3Com technical support services.

Error or Problem	Explanation or Solution
Edit File: File too large.	This message usually appears when you select a text-based file within a boot image file and then select Edit from the File menu.  The text editor that is shipped with Boot Image Editor only opens files under 64 KB. To edit the selected file, extract the file, open it with a text editor or word processor outside of Boot Image Editor, and then add it to the boot image file again.
Error: Not enough space in image to add file	When you first create a boot image file with Boot Image Editor, you must specify the maximum capacity of the image file. If the size of the boot image file is approaching the specified maximum when you try to add another file, you receive this message.  You can solve the problem in two ways: • Delete any unnecessary bootstrap files from within the boot image file and then try adding the new file again. • If the intended client PC has enough memory to support a larger boot image file, create a boot diskette from the image and then create a new image. If the boot image file is larger than a standard floppy diskette, you must create a new image from scratch.
You receive a message related to the *.SYS file extension.	SYS is the default extension for NetWare boot image files.  This extension usually generates a message because Windows normally registers the *.SYS extension without associating it with a particular application.  You should be safe in replacing the current association, unless you have deliberately associated *.SYS with another application.
Boot Image Editor online help file is not opening properly.	If the online help is not launching correctly, add the ROBOEX32.DLL to the system that hosts Boot Image Editor. This DLL is available in the 3Com DynamicAccess boot services installation package.
Jumps to web sites from the Boot Image Editor help file are not working.  OR You receive a message related to the INETWH32.DLL.	The INETWH32.DLL adds Internet access functionality to Windows 95, 98 and NT Help systems. If you do not have this file in your WINDOWS\SYSTEM directory, you will not be able to open your default browser automatically to obtain further information on Boot Image Editor from the web.
Tool tips in Boot Image Editor are not appearing.	To display tool tips in Boot Image Editor, you need the most recent COMCTL32.DLL from Microsoft Corporation. Refer to the Microsoft web site for more information on this DLL (http://msdn.microsoft.com/library/sdkdoc/shellcc/ commctls/common/common.htm).
See Also…

Obtaining Technical Support

Online Technical Services from 3Com

Support from Your Network Supplier

Telephone Support from 3Com

Returning Products for Repair


Boot Image Editor Copyright and Trademarks

Copyright Information

© 3Com Corporation, August 1999, "All rights reserved." No part of this document may be reproduced in any form or by any means or be used to make any derivative work (such as translation, transformation, or adaptation) without permission from 3Com Corporation (or its subsidiaries).

3Com Corporation (or its subsidiaries) reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of 3Com Corporation (or its subsidiaries) to provide notification of such revision or change.

3Com Corporation (or its subsidiaries) provides this documentation without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. 3Com (or its subsidiaries) may make improvements or changes in the product(s) and/or the program(s) described in this document at any time.

Trademarks

Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries.

3Com, the 3Com logo, Managed PC Boot Agent, MBA, and Pre-OS are trademarks of 3Com Corporation or its subsidiaries.

Intel is a registered trademark of Intel Corporation. Microsoft, Windows 3.1, Windows 95, Windows 98, Microsoft Network Client Version 3.0, and Windows NT are registered trademarks of Microsoft Corporation. Novell, NetWare, and UNIX are registered trademarks of Novell, Inc.

Other brands and trademarks may be registered trademarks of their respective holders.