Using a Boot.ini File in a Remote Boot Environment

The Boot.ini file can be used instead of using the settings within the Remote Boot manager to boot the appropriate image on a client device. You can create a custom Boot.ini file that is used to present the client device operator with a choice of images to load. If the default Boot Image and Boot Parameters fields are left empty and the Boot Image and Boot Parameters fields for the individual device are left empty as well in the Remote Boot manager, the Remote Boot client will download a Boot.ini file from the \Program Files\Windows Embedded\Remote Boot Service\Downloads directory to determine the run-time image to be used. You can force each Remote Boot device on your local network to boot using your custom Boot.ini file by verifying that the Use default settings to boot unspecified clients option has been selected in the Remote Boot manager.

Note The Boot.ini switch /3GB is not supported in remote boot environments.

The value of the Boot.ini switch /MAXMEM should be at least 64 MB greater than the size of the run-time image. If the client device fails to download the image, or crashes when attempting to boot the image, increase the size of the /MAXMEM switch.

The following example shows a Boot.ini file that allows the Remote Boot client operator to choose from two different images.

[boot loader]
timeout=30
default=ramdisk(0)\windows
[operating systems]
ramdisk(0)\windows="Maint Tools" /fastdetect 
/rdpath=net(0)\maint.sdi /rdimageoffset=4096
ramdisk(0)\windows2="Image being debugged" /fastdetect /rdpath=net(0)\myimage.sdi /rdimageoffset=4096 /debug 
/debugport=com1 /baudrate=57600

Note   F8 functionality is disabled.

See Also

Remote Boot Overview | Installing the Remote Boot Server | Configuring the Remote Boot Service Using Remote Boot Manager | Creating a Remote Boot Image | Preparing a Remote Boot Image for Deployment | Starting and Stopping Remote Boot Services | Configuring DHCP for Remote Boot Services | Remote Boot Response Time