Keywords; The Include Keyword - Neoware e140 - Thin Client User Manual

Neoware image manager 4.6 user manual
Hide thumbs Also See for Neoware e140 - Thin Client:
Table of Contents

Advertisement

The mPXELdr Configuration File

Keywords

The Include
Keyword
256
Keywords
Syntax:
Include = <Filepath>
Examples:
1
Include = MyIncludeFile.ininc
2
Include = /MyIncludeFile.ininc
3
Include = SomeRelativePath/MyIncludeFile.ininc
4
Include = /SomeAbsolutePath/MyIncludeFile.ininc
Default value: None
The
is either absolute (expressed starting relative to the
<Filepath>
TFTP root directory) or relative (to the directory where the mPX-
ELdr boot program resides).
A leading '
' or '
' in the
/
\
which will be passed "as is" to the TFTP server, while anything else
indicates a relative path which will be prepended to whatever is set
in the data part of the
Therefore, using examples 1 to 4 above and assuming
is located in subdirectory
the TFTP path of mPXELdr is
1 will resolve to:
LdrPath/MyIncludeFile.ininc
2 will resolve to:
/MyIncludeFile.ininc
3 will resolve to:
LdrPath/SomeRelativePath/MyIncludeFile.ininc
4 will resolve to:
/SomeAbsolutePath/MyIncludeFile.ininc
As the TFTP OS can be hosted in either a Windows, Linux or UNIX
server, mPXELdr will get the default
ELdr file path (that comes from the DHCP information), and use the
path separators ('
' or '
/
the path separators that it finds in the
and never alters them either. In other words, mPXELdr never inserts
or removes any path separators. It merely uses those that it collects
indicates an absolute path
<Filepath>
parameter.
Include
of the TFTP root directory (i.e.
LdrPath
LdrPath\mPXELdr.bin
.ini
') that it finds there. mPXELdr will also use
\
.ini
mPXELdr.bin
:
file path from the mPX-
file, whatever they are,

Advertisement

Table of Contents
loading

This manual is also suitable for:

Image manager 4.6

Table of Contents