Lenovo ThinkPad R400 User Manual
Page 27
–
If
you
are
building
an
Ultra-Portable
Image
or
a
Portable-Sysprep
Image,
you
can
use
application
modules.
The
deployment
and
installation
of
the
applications
modules
are
controlled
by
base
maps.
–
If
you
are
building
a
Hardware-Specific
Image,
you
cannot
use
application
modules
in
conjunction
with
that
image.
All
applications
must
be
part
of
the
Hardware-Specific
Image.
v
Device-driver
modules:
Each
of
these
modules
contains
all
of
the
components
associated
with
a
specific
device
driver.
–
If
you
are
building
an
Ultra-Portable
Image
or
a
Portable-Sysprep
Image,
you
can
use
device-driver
modules.
The
deployment
and
installation
of
the
device-driver
modules
are
controlled
by
driver
maps.
–
If
you
are
building
a
Hardware-Specific
Image,
you
cannot
use
device-driver
modules
in
conjunction
with
that
image.
All
device
drivers
must
be
part
of
the
Hardware-Specific
Image.
During
the
deployment
process,
you
choose
which
base
map
and
which
driver
map
to
deploy.
This
enables
you
to
maintain
device-driver
modules
and
driver
maps
independently
of
the
operating-system
and
application
content
defined
by
base
maps.
In
addition
to
modules,
the
ImageUltra
Builder
program
enables
you
to
create
containers
in
the
repository.
A
container
is
a
special
type
of
module
that
enables
you
to
group
other
modules
together
under
a
single
identifier.
All
modules
in
a
container
must
be
of
the
same
type.
For
example,
you
might
want
to
group
all
of
the
device
drivers
used
for
a
specific
machine
type
into
a
device-driver
container.
Or,
you
might
want
to
group
a
Windows
2000
base
operating-system
module
with
all
of
its
associated
add-on
modules
into
an
operating-system
container.
If
you
build
an
I386
base
operating-system
module,
you
might
want
to
group
the
I386
base
operating-system
module,
the
appropriate
Primary
Partition
partitioning
module,
the
ImageUltra
Customizations
module,
the
Sysprep
module,
and
the
UNATTEND.TXT
module
into
a
single
operating-system
container
to
ensure
all
required
components
are
kept
together.
The
use
of
containers
is
optional,
but
you
might
find
containers
helpful
when
creating
maps
because
you
can
simply
insert
the
container
module
into
your
map
instead
of
inserting
each
individual
module.
All
maps
and
modules
are
stored
in
a
repository.
When
the
repository
is
viewed
through
the
ImageUltra
Builder
interface,
the
maps
and
modules
are
identified
by
descriptive
names.
The
actual
file
names
are
assigned
by
the
ImageUltra
Builder
program.
The
following
is
a
list
of
file
extensions
used
for
the
files
in
the
repository:
v
.CRI:
Metadata
about
the
module.
This
information
is
used
within
the
ImageUltra
Builder
interface.
v
.DMA:
Driver
maps
v
.BMA:
Base
maps
v
.IMZ:
Compressed
module
source
v
.WIM:
ImageX
file
Chapter
2.
An
overview
of
the
image
process
13