3.4. Working with OSCDImg
The Operating System CD
Image (OSCDImg) utility is a CD-ROM and DVD-ROM Premastering Utility,
which is actually not a new tool; however, it is getting some renewed
life as a critical element of the WAIK in its ability to generate ISO
files based on the content of your WIM file.
OSCDImg supports ISO 9660, Joliet, and Universal Disk Format (UDF) file systems. The syntax for the OSCDLmg command is:
OSCDIMG [options] SourceLocation TargetFile
The parameters shown here are described in the following list:
Options: Choose from a long list of available options to control the behavior of OSCDImg, which are detailed in Table 8.
SourceLocation: Specifies the location of the files that you intend to build into an .iso image (required).
TargetFile: Specifies the name of the .iso image file (required).
Table 8. Reviewing OSCDIMG Command Line Options
| Option | Purpose |
|---|
| -a | Causes the tool to display the allocation summary for files and directories. |
| -b <Location> | Specifies the location for the El Torito boot sector
file. An El Torito boot sector file is a simple disk image like that of
a boot floppy (including a boot sector and special CD-RO M structures).
It is included in the Windows PE distribution at
<WindowsPE>\etfsboot. com (where WindowsPE is the root
installation directory for your Windows PE tools). |
| -c | Directs the tool to use ANSI filenames instead of OEM filenames. |
| -d | Causes the tool to not force lowercase filenames to uppercase. |
| -e | Instructs
the tool to not use floppy disk emulation in the El Torito catalog.
This option can only valid for single boot entry images and cannot be
combined with any multi-boot entry switches. |
| -g | Directs the tool to use the Universal Coordinated Time (UCT) for all files instead of the local computer time. |
| -h | Causes the tool to include hidden files and directories. |
| -j1 | Instructs
the tool to encode Joliet Unicode filenames and generates
DOS-compatible 8.3 filenames in the ISO 9660 namespace.
Note: These filenames can be read by either Joliet systems or
conventional ISO 9660 systems, but OSCDImg may change some of the
filenames in the ISO 9660 name space to comply with DOS 8.3 and/or ISO
9660 naming restrictions. |
| -j2 | Instructs the tool to encode Joliet Unicode filenames without standard ISO 9660 names.
Note: A Joliet operating system is required to read files encoded this way. |
| -js<TextFile> | Directs the tool to override the default text file used with the j2 option (for example, -jsc:\Readme.txt). |
| -k | Causes the tool to continue creating an image even with it fails to open some of the source files. |
| -l<LableName> | Specifies
a desired volume label. Note: No spaces should be inserted between the
-l and <LabelName> (for example, -lMYLABEL). |
| -m | Instructs the tool to ignore the maximum size limit of an image. |
| -maxsize:<Limit> | Directs
the tool to override the default maximum size of an image. The default
value is configured to support a 74-minute CD-ROM (unless UDF is being
used, in which case there is no maximum default size). The Limit value
is specified in megabytes (for example, -maxsize:4096 limits the image
to 4096MB). |
| -n | Causes the tool to utilize long filenames |
| -nt | Causes the tool to utilize long filenames compatible with Windows NT 3.51. |
| -o | Instructs the tool to optimize storage by encoding duplicate files only once using a MD5 hashing algorithm to compare files. |
| -oc | Instructs
the tool to optimize storage by encoding duplicate files only once
using a binary comparison of each file (a method slower than the MD5
hash utilized by -o). |
| -oi | Instructs
the tool to optimize storage by encoding duplicate files only once
(when comparing files, this method ignores Diamond compression
timestamps). |
| -os | Instructs the tool to optimize storage by encoding duplicate files only once (shows duplicate files when creating the image). |
| -ois | Instructs
the tool to optimize storage by encoding duplicate files only once
(when comparing files, it will ignore Diamond compression timestamps and
will show duplicate files when creating the image). |
| -p | Allows
you to specify the value to use for the Platform ID in the El Torito
catalog (the default is 0×00, representing the x86 platform). This
option can only be used for single boot entry images and cannot be
combined with any multi-boot entry switches. |
| -t<Time> | Causes
the tool to use the provided timestamp for all files and directories.
The U.S.A. date format and 24-hour clock format should be used with no
spaces when specifying this value. Any delimiter may be used between the
items (for example: -t12/31/2008,23:59:59). |
| -u1 | Directs
the tool to produce an image that has both the UDF and ISO 9660 file
systems. The ISO 9660 file system will be written with DOS-compatible
8.3 file names. The UDF file system will be written with Unicode
filenames. |
| -u2 | Directs
the tool to produce an image that uses only the UDF file system. Any
system not capable of reading UDF will only see a default text file
alerting the user that this image is only available on computers that
support UDF. |
| -ur | Directs the tool to override the default test file used with the -u2 option (for example, -urc:\Readme.txt). |
| -us | Causes the tool to create a sparse file when available (this can only be used with the -u2 option). |
| -ue | Instructs the tool to create embedded files (this can only be used with the -u2 option). |
| -uf | Directs the tool to embed UDF file identifier entries (this can only be used with the -u2 option). |
| -uv | Causes
the tool to provide UDF Video Zone compatibility during DVD Video/Audio
disk creation (meaning that UDF 1.02 and ISO 9660 are written to the
disk). Additionally, the files in the VIDEO_TS, AUDIO_TS, and JACKET_P
directories are written first (these directories take precedence over
all other ordering rules used for this image). |
| -ut | Causes
the tool to truncate the ISO 9660 portion of the image during DVD
video/audio disk creation (when this option is used, only the VIDEO_TS,
AUDIO_TS, and JACKET_P directories are visible from the ISO 9660 file
system). |
| -w1 | Directs the tool to report all filenames or depths that are not ISO-compliant or Joliet-compliant. |
| -w2 | Directs the tool to report all filenames that are not DOS-compliant. |
| -w3 | Directs the tool to report all zero-length files. |
| -w4 | Directs the tool to report each filename that is copied to the image. |
| -x | Instructs the tool to compute and encode an AutoCRC value in the image. |
| -yd | Instructs the tool to silence warnings for nonidentical files with the same initial 64,000 bytes. |
| -yl | Causes the tool to produce long allocation descriptors instead of short allocation descriptors. |
| -y5 | Dictates file layout on disk by writing all files in an i386 directory first and in reverse sort order. |
| -y6 | Specifies that directory records be exactly aligned at the end of sectors. |
| -yo | Instructs
the tool to control the file layout using a supplied text file that has
a layout for the files to be placed in the image which follows these
rules:
The order file must be in ANSI format and the file must end in
a new line. You must list only one file per line. The files listed must
be specified relative to the root of the image and each file must be
specified as a long filename (no short names are allowed). Finally, each
file path cannot be longer than MAX_PATH, including volume name. It is
also helpful to note that not all files must be listed in the order file
— any that are not listed will simply be ordered as they would be if
there was no ordering file. |
| -yw | Causes the tool to open source files with write sharing. |
For example:
oscdimg -n -bc:\imaging\etfsboot.com c:\imaging\iso c:\imaging\
winpe.iso
This example creates a
bootable image named winpe.iso in the c:\imaging folder supporting long
filenames and using the standard El Torito boot sector file supplied
with Windows PE.
NOTE
Simply copying an .iso
file to a CD-ROM does not successfully apply the .iso file to a CD. To
create a bootable CD-ROM, you must use CD-recording software that
supports applying an .iso file as an image to a CD-ROM (a very common
feature among such software).
3.5. Working with vLite
vLite (Vista
Lite) is a freeware application written by Dino Nuhagic (AKA nuhi),
which provides features that allow you to customize a Windows Vista
setup prior to its use. Its features include:
Support for the integration of hotfixes, language packs, and drivers
Slipstreaming of Windows Vista service packs (not natively supported by Microsoft)
The ability to remove undesired components of the installation
Creation of an unattended setup
Splitting and merging of Windows Vista installation CDs
Creation of an ISO with the ability to burn it to a bootable CD or DVD
A facility to perform other changes and tweaks
Although it is not a
supported Microsoft tool, the features it offers are compelling and take
advantage of Windows Vista's new setup architecture in a compelling
way. The following section takes you through the following aspects of
vLite while covering its key functions:
Getting setup
Slipstreaming service packs
Integrating hotfixes, drivers, or language packs
Selectively excluding components from setup
Configuring defaults for certain options (tweaks)
Generating an unattended setup
Creating and/or burning an ISO image of the customized Windows Vista installation
Setting up vLite
The following steps take you through the download and installation of vLite:
Select a folder where the Windows Vista installation media is stored. This can be a local or network folder, a physical DVD, or a mounted virtual DVD ISO.
Select a file where the installation will be stored locally on the computer for modification (this should be an empty folder).
After the paths are specified, the files are copied from the source
media to the specified local folder. The files are about 2.5GB in total
so, depending on your computer, this could take several minutes.
Specify the editions of Windows Vista you want to work with.
Click the Tasks button on the left and select the boxes for each of the functions you want to exercise (see
Figure 4).
Slipstream ing with vLite
You can merge Vista
service packs into your image such as with Windows Service Pack 1.
Again, this feature was not provided by Microsoft so you should be
warned that using this function might result in an implementation of
Vista that is not supported by Microsoft. The following steps specify
how to slipstream Windows Vista Service Pack 1 into a Windows Vista
image.
If you have not already, you must choose Service Pack Slipstream from the task list. Any other tasks you choose along with this option will remain disabled until after the slipstream task has been completed.
Choose the slipstream button from the list on the left and click the Select button at the bottom-right of the screen.
Choose your downloaded service pack. vLite will immediately begin extracting what it needs from the service pack binary. This process can take up to an hour and a half to complete.
NOTE
To support the
slipstreaming feature of vLite, you must be working with a fresh image
of Vista RTM which has not been edited by vLite or any other
application. You can remove components and make other desired changes after slipstreaming (not before).
Integrating with vLite
The Integration task
allows you to integrate hotfixes, drivers, and language packs. Any
currently installed items are also displayed for your information. The
following steps take you through the integration options of vLite:
If
you have not already, you must choose Integration from the task list.
If you chose Service Pack Slipstream, you will need to complete this
task prior to any desired integration of hotfixes, drivers, and language
packs.
To make use of the tabs for each of the elements, select the Enable box at the top left of the selected tab.
Click the Insert button and browse to the source for the item to be integrated.
Repeat the process for any other elements you wish to integrate. You need not hit the Apply button until you have completed all of the desired changes across all tasks.
Excluding components with vLite
A core feature of vLite
is to allow for the creation of a more lightweight installation of
Vista. When choosing the Components task, you can specify any features
of Windows Vista that you do not want to include in your Windows Vista
installation. The following steps take you through how to exclude
components from a Windows Vista installation with vLite:
If
you have not already, you must choose Components from the task list. If
you chose Service Pack Slipstream, you need to complete this task prior
to any desired changes to the components and files to be included in
your Windows Vista installation.
The
first time you utilize this task, the Compatibility dialog appears so
that you may choose the features and applications you wish to utilize in
your Vista installation. Based on these choices, certain components may
be automatically included to support them.
To bring this dialog up in the future, choose Compatibility from the bottom of the Components window display.
Select the items you want to exclude from your installation of Windows Vista.
This main Compatibility task window provides a tree view of
accessories, drivers, games, hardware support, languages, multimedia,
network, services, and system components. When hovering over any of the
listed items, a simple description is provided to the right to help you
in your decision.
Choose
the Protect files menu item from the bottom of the Compatibility tasks
window for any files how wish to specifically include.
Repeat the process for any other components you wish to exclude. You need not hit the Apply button until you have completed all of the desired changes across all tasks.
NOTE
Service packs are
designed to update the entire installation. If you have used vLite to
remove any components, the installation of Windows Vista Service Pack 1
(and future service packs) may fail. The update issue applies only to
service packs; you will still get Windows Updates for the components you
did not remove.
Selecting Tweaks with vLite
There are a handful of
changes you may specify to control the default behavior of supported
options. These options are broken down into categories: security,
system, explorer, and Internet Explorer. You may specify if listed
options are to remain with their default setting or force them to be
enabled or disabled automatically when the installation of Windows Vista
is complete.
Follow these steps take you through how to make use of the Tweaks feature of vLite:
If you have not already, you must choose Tweaks from the task list.
If you chose Service Pack Slipstream, you will need to complete this
task prior to any desired changes to the setting default options for
your Windows Vista installation.
Select any of the groupings from the list on the left to see the available options for configuration.
Click
the value for the option to select the desired setting or double-click
the option name to toggle through the available settings.
Typically the options are default (don't change), enabled, or disabled.
For example to disable User Account Control (UAC) in your setup, choose
Disabled as the value for User Account Control (UAC) option listed
under Security.
Repeat the process for any other options you want to configure. You need not click the Apply button until you have completed all of the desired changes across all tasks.
Creating an unattended setup with vLite
Another feature
of vLite is a helpful interface to creating an unattended installation
file, which may be used to automate your customized installation. This
is typically done with Windows System Image Manager (Windows SIM).
Although Windows SIM is a powerful tool with many more capabilities,
vLite is handy because it is kept simple. Windows SIM can be a very
confusing tool when compared to the simplicity of this feature. The
following steps take you through how to create an unattended setup using
vLite:
If you have not already, you must select Unattended setup from the task list.
If you chose Service Pack Slipstream, you will need to complete this
task prior to specifying the desired options for an unattend.xml file.
Choose any desired User Data settings. You have a few choices including:
Specify product key or skip the prompt to collect it
Skip automatic activation
Accept the end user license agreement (EULA)
Specify the name and organization for the installation
Enter the desired computer name for the unattended installation
Choose any desired Welcome Center settings from the list provided:
Specify the network location (home or work, for example)
Set default computer protection options (disabled, only install updates)
Skip user creation
Set an administrator password
Specify the number of times an automatic admin logon should occur
A
second tab is also offered so that you may have the installation prompt
for such information (default). Alternatively, you can specify desired
regional settings, such as UI language, time, and currency format,
keyboard region, and time zone so that the installer will not be
prompted.
Creating and burning an ISO image with vLite
Before generating an ISO
image, you must apply your choices to the customized image. Click the
Apply button after you have completed all desired tasks. When you click
Apply you are prompted to choose a build method. You can simply save
your changes, rebuild the entire installation (all editions), or you may
build only the edition of Windows Vista that you are working with. When
working with editions other than Ultimate, this reduces the size of the
image by eliminating the need for them to be included in the image. It
is this last option (Rebuild one) that is recommended.
After you have applied
your changes, you may create an image and optionally burn it to writable
media using the ISO task. The following steps take you through how to
create and burn an ISO image using vLite:
Choose a mode: Direct Burn, Burn Image, Create Image or Erase RW. By default, the option is Create Image
When
creating an image (ISO) you need only specify a volume label (VistaLite
by default) and then click the Make ISO button at the bottom right to
be prompted for a filename. After a name is specified the process will begin and should take no more than a few minutes.
If you choose to burn an image, you may select the target device and burn speed.
Advanced settings are also provided to specify an alternate boot sector
and to control if burned contents should be tested, verified, or
erased.
Finally, you may also split the image into manageable sizes if you want by pressing the Split button.
