Creating DVD images
For images larger than 4.5 GB, you must create a boot order file (Bootorder.txt) to ensure boot files are
located at the beginning of the image. For example,
oscdimg -m -n –yoC:\temp\bootorder.txt -bC:\winpe_x86\etfsboot.com
Where bootorder.txt contains the following list of files.
boot\bcd
boot\boot.sdi
boot\bootfix.bin
boot\bootsect.exe
boot\etfsboot.com
boot\memtest.efi
boot\memtest.exe
boot\en-us\bootsect.exe.mui
boot\fonts\chs_boot.ttf
boot\fonts\cht_boot.ttf
boot\fonts\jpn_boot.ttf
boot\fonts\kor_boot.ttf
boot\fonts\wgl4_boot.ttf
sources\boot.wim
Saturday, May 22, 2010
BCEDIT how to use on window vista, Win 7
BCEDIT
Boot Configuration Data (BCD) files provide a store that is used to describe
boot applications and boot application settings. The objects and elements in the
store effectively replace Boot.ini.
BCDEdit is a command-line tool for managing BCD stores. It can be used for a
variety of purposes, including creating new stores, modifying existing stores,
adding boot menu parameters, and so on. BCDEdit serves essentially the same
purpose as Bootcfg.exe on earlier versions of Windows, but with two major
improvements:
• Exposes a wider range of boot parameters than Bootcfg.exe.
• Has improved scripting support.
BCDEdit is the primary tool for editing the boot configuration of
Windows Vista and later versions of Windows. It is included with the
Windows Vista distribution in the %WINDIR%\System32 folder.
BCDEdit is limited to the standard data types and is designed primarily to
perform single common changes to BCD. For more complex operations or
nonstandard data types, consider using the BCD Windows Management
Instrumentation (WMI) application programming interface (API) to create more
powerful and flexible custom tools.
Syntaxes
BCDEdit /Command [] []
Syntax Description
/? = Displays a list of BCDEdit commands. Running this command without an argument displays a summary of the available commands. To display detailed help for a particular command, run bcdedit
/?, where is the name of the command you are searching for more
information about. For example, bcdedit /? createstore displays detailed help for the Createstore
command.
Parameters that Operate on a Store
Syntax Description
/createstore = Creates a new empty boot configuration data store. The created store is not a system store.
/export = Exports the contents of the system store into a file. This file can be used later to restore t
he state of the system store. This command is valid only for the system store.
/import = Restores the state of the system store by using a backup data file previously generated by using
the /export option. This command deletes any existing entries in the system store before the import takes place. This command is valid only for the system store.
/store = This option can be used with most BCDedit commands to specify the store to be used. If this option is not specified, then BCDEdit operates on the system store. Running the bcdedit /store command by itself is equivalent to running the bcdedit /enum active command.
Parameters that Operate on a Store
Syntax Description
/createstore = Creates a new empty boot configuration data store. The created store is not a system store.
/export = Exports the contents of the system store into a file. This file can be used later to restore the state of the system store. This command is valid only for the system store.
/import = Restores the state of the system store by using a backup data file previously generated by using the /export option. This command deletes any existing entries in the system store before the
import takes place. This command is valid only for the system store.
/store = This option can be used with most BCDedit commands to specify the store to be used. If this option is not specified, then BCDEdit operates on the system store. Running the bcdedit /store command by itself is equivalent to running the bcdedit /enum active command.
Boot Configuration Data (BCD) files provide a store that is used to describe
boot applications and boot application settings. The objects and elements in the
store effectively replace Boot.ini.
BCDEdit is a command-line tool for managing BCD stores. It can be used for a
variety of purposes, including creating new stores, modifying existing stores,
adding boot menu parameters, and so on. BCDEdit serves essentially the same
purpose as Bootcfg.exe on earlier versions of Windows, but with two major
improvements:
• Exposes a wider range of boot parameters than Bootcfg.exe.
• Has improved scripting support.
BCDEdit is the primary tool for editing the boot configuration of
Windows Vista and later versions of Windows. It is included with the
Windows Vista distribution in the %WINDIR%\System32 folder.
BCDEdit is limited to the standard data types and is designed primarily to
perform single common changes to BCD. For more complex operations or
nonstandard data types, consider using the BCD Windows Management
Instrumentation (WMI) application programming interface (API) to create more
powerful and flexible custom tools.
Syntaxes
BCDEdit /Command [
Syntax Description
/? = Displays a list of BCDEdit commands. Running this command without an argument displays a summary of the available commands. To display detailed help for a particular command, run bcdedit
/?
information about. For example, bcdedit /? createstore displays detailed help for the Createstore
command.
Parameters that Operate on a Store
Syntax Description
/createstore = Creates a new empty boot configuration data store. The created store is not a system store.
/export = Exports the contents of the system store into a file. This file can be used later to restore t
he state of the system store. This command is valid only for the system store.
/import = Restores the state of the system store by using a backup data file previously generated by using
the /export option. This command deletes any existing entries in the system store before the import takes place. This command is valid only for the system store.
/store = This option can be used with most BCDedit commands to specify the store to be used. If this option is not specified, then BCDEdit operates on the system store. Running the bcdedit /store command by itself is equivalent to running the bcdedit /enum active command.
Parameters that Operate on a Store
Syntax Description
/createstore = Creates a new empty boot configuration data store. The created store is not a system store.
/export = Exports the contents of the system store into a file. This file can be used later to restore the state of the system store. This command is valid only for the system store.
/import = Restores the state of the system store by using a backup data file previously generated by using the /export option. This command deletes any existing entries in the system store before the
import takes place. This command is valid only for the system store.
/store = This option can be used with most BCDedit commands to specify the store to be used. If this option is not specified, then BCDEdit operates on the system store. Running the bcdedit /store command by itself is equivalent to running the bcdedit /enum active command.
BCDBOOT what is this ?
BCDBOOT
BCDboot is a tool used to quickly set up a system partition, or to repair the
boot environment located on the system partition. The system partition is set
up by copying a small set of boot environment files from an installed
Windows® image. BCDboot also creates a Boot Configuration Data (BCD)
store on the system partition with a new boot entry that enables you to boot to
the installed Windows image.
You can run BCDboot from Windows® PE. For information on Windows PE,
see Windows PE Walkthroughs.
BCDboot is included with Windows® 7 and Windows Server® 2008 R2 in the
%WINDIR%\System32 folder. BCDboot is also available in the Windows
OEM Preinstallation Kit (OPK) and Windows Automated Installation Kit
(AIK) under the %Program Files%\\Tools directory, where
is either Windows OPK or Windows AIK.
BCDboot copies a set of boot environment files from a Windows image that is
already on the computer. BCDboot can copy boot environment files from
images of Windows Vista®, Windows Server® 2008, Windows 7, or Windows
Server 2008 R2. For information on applying a Windows image to a system, see
Capture and Apply Windows Images.
BCDboot uses the file: %WINDIR%\System32\Config\BCD-Template file to
create a new BCD store and initialize the BCD boot-environment files on the
system partition. Specific BCD settings can be defined in the BCD-Template
file. The tool also copies the most recent versions of boot-environment files
from the operating system image %WINDIR%\boot folder and
%WINDIR%\System32 folder to the system partition.
BCDboot copies files to the default system partition identified by the firmware.
You can create this partition by using a partitioning tool such as DiskPart. You
do not have to assign a drive letter to this partition for BCDboot to locate it.
For more information, see the DiskPart Help from the command line, or
Diskpart Command line syntax.
On BIOS-based systems, the system partition is the active partition on disks
using the Master Boot Record (MBR) disk format. BCDboot creates the \Boot
directory on the system partition and copies all required boot-environment files
to this directory.
On Unified Extensible Firmware Interface (UEFI)-based systems, the EFI
system partition is the system partition on disks using the GUID Partition Table
(GPT) disk format. BCDboot creates the \Efi\Microsoft\Boot directory and
copies all required boot-environment files to this directory.
BCDboot can update an existing boot environment to the system partition.
Newer file versions from the Windows image will be copied to the system
partition.
If a BCD store already exists on the system partition:
BCDboot will create a new boot entry in the existing BCD store, based
on settings in the BCD-Template file, and remove any duplicate boot
entries that reference the same Windows image.
If there is already a boot entry for the Windows image, and additional
BCD settings are enabled for that boot entry beyond the default values,
these settings can be retained the next time BCDboot is run by using
the /m option to merge the existing boot entry, identified by the OS
Loader GUID into the new boot entry created by BCDboot.
BCDboot is a tool used to quickly set up a system partition, or to repair the
boot environment located on the system partition. The system partition is set
up by copying a small set of boot environment files from an installed
Windows® image. BCDboot also creates a Boot Configuration Data (BCD)
store on the system partition with a new boot entry that enables you to boot to
the installed Windows image.
You can run BCDboot from Windows® PE. For information on Windows PE,
see Windows PE Walkthroughs.
BCDboot is included with Windows® 7 and Windows Server® 2008 R2 in the
%WINDIR%\System32 folder. BCDboot is also available in the Windows
OEM Preinstallation Kit (OPK) and Windows Automated Installation Kit
(AIK) under the %Program Files%\
BCDboot copies a set of boot environment files from a Windows image that is
already on the computer. BCDboot can copy boot environment files from
images of Windows Vista®, Windows Server® 2008, Windows 7, or Windows
Server 2008 R2. For information on applying a Windows image to a system, see
Capture and Apply Windows Images.
BCDboot uses the file: %WINDIR%\System32\Config\BCD-Template file to
create a new BCD store and initialize the BCD boot-environment files on the
system partition. Specific BCD settings can be defined in the BCD-Template
file. The tool also copies the most recent versions of boot-environment files
from the operating system image %WINDIR%\boot folder and
%WINDIR%\System32 folder to the system partition.
BCDboot copies files to the default system partition identified by the firmware.
You can create this partition by using a partitioning tool such as DiskPart. You
do not have to assign a drive letter to this partition for BCDboot to locate it.
For more information, see the DiskPart Help from the command line, or
Diskpart Command line syntax.
On BIOS-based systems, the system partition is the active partition on disks
using the Master Boot Record (MBR) disk format. BCDboot creates the \Boot
directory on the system partition and copies all required boot-environment files
to this directory.
On Unified Extensible Firmware Interface (UEFI)-based systems, the EFI
system partition is the system partition on disks using the GUID Partition Table
(GPT) disk format. BCDboot creates the \Efi\Microsoft\Boot directory and
copies all required boot-environment files to this directory.
BCDboot can update an existing boot environment to the system partition.
Newer file versions from the Windows image will be copied to the system
partition.
If a BCD store already exists on the system partition:
BCDboot will create a new boot entry in the existing BCD store, based
on settings in the BCD-Template file, and remove any duplicate boot
entries that reference the same Windows image.
If there is already a boot entry for the Windows image, and additional
BCD settings are enabled for that boot entry beyond the default values,
these settings can be retained the next time BCDboot is run by using
the /m option to merge the existing boot entry, identified by the OS
Loader GUID into the new boot entry created by BCDboot.
Friday, May 21, 2010
Follow these steps to connect one or more additional monitor to a desktop computer
Subject :Follow these steps to connect one or more additional monitor to a desktop computer
1. Turn off your computer and disconnect the power cable.
2. Open your computer case.
3. Find an unused PCI or AGP slot on your motherboard.
4. Remove the filler backplate next to the empty slot. Save the screw.
5. Insert your graphics card into the empty slot. Push it down (toward the motherboard) at the front and back to make sure it's firmly seated.
6. Use the screw that held the filler plate to attach the graphics card's connector panel to the back of the computer. You might have to loosen the screws on adjacent backplates to fit the graphics card's connector plate solidly against the mounting rail.
7.Plug the video cable from your second monitor into the VGA connector on the newly installed graphics controller.
8.Plug in the power cable on the new monitor and turn both monitors on.
9.Plug the power cable back into the computer and turn it on. Windows displays a "Found New Hardware" message and installs a device driver for the new graphics card. If Windows doesn't automatically find the device driver software, use the Browse button to identify the driver on the CD that came with the card or that you downloaded from the manufacturer's Web site.
10. Move your mouse cursor to a blank spot on the desktop and right-click. The Display Properties window opens.
11. Choose the Settings tabTurn on the Extend my Windows desktop onto this monitor option and click Apply. The second monitor comes to life, with the same background color and picture as the primary monitor
1. Turn off your computer and disconnect the power cable.
2. Open your computer case.
3. Find an unused PCI or AGP slot on your motherboard.
4. Remove the filler backplate next to the empty slot. Save the screw.
5. Insert your graphics card into the empty slot. Push it down (toward the motherboard) at the front and back to make sure it's firmly seated.
6. Use the screw that held the filler plate to attach the graphics card's connector panel to the back of the computer. You might have to loosen the screws on adjacent backplates to fit the graphics card's connector plate solidly against the mounting rail.
7.Plug the video cable from your second monitor into the VGA connector on the newly installed graphics controller.
8.Plug in the power cable on the new monitor and turn both monitors on.
9.Plug the power cable back into the computer and turn it on. Windows displays a "Found New Hardware" message and installs a device driver for the new graphics card. If Windows doesn't automatically find the device driver software, use the Browse button to identify the driver on the CD that came with the card or that you downloaded from the manufacturer's Web site.
10. Move your mouse cursor to a blank spot on the desktop and right-click. The Display Properties window opens.
11. Choose the Settings tabTurn on the Extend my Windows desktop onto this monitor option and click Apply. The second monitor comes to life, with the same background color and picture as the primary monitor
Using the Program Compatibility Wizard (Vista)
Installing a program is one thing; getting it to run after it’s installed is another. If an installed program won’t
start or isn’t working right, try using the Program Compatibility Wizard on it.
The Program Compatibility Wizard provides a step-by-step means of configuring and testing an older program
so that it will run in Windows Vista. Before you bother to use it, try running the installed program
without it. I mention this because I’ve seen people spend much time messing with this on the assumption
that it’s needed. When in fact, the assumption was wrong and they could have just run the program as-is!
If you’re sure an installed program isn’t running, or is not running correctly, follow these steps to start the
Program Compatibility Wizard:
1. Click the Start button and choose All Programs ➪ Accessories ➪ Program Compatibility Wizard.
2. Read the first wizard page and click Next>.
n I want to choose from a list of programs: If the program is already installed and has an icon
on the All Programs menu, choose this option.
n I want to use the program in the CD-ROM drive: If the program isn’t installed and needs to
be installed or run from a CD, choose this option.
n I want to locate the program manually: If the program isn’t on the All Programs menu, but
you know the path and filename of the program, choose this option.
4. Follow the instructions on the next wizard page. For example, if you chose the first option, scroll
through the list of program names and click the program you want to run in compatibility mode.
Then click Next>.
5. On the next page, choose the operating system that the program was written for, or the last operating
system on which you were able to run the program. Then click Next>.
6. The next wizard page will ask about display settings, such as 256 colors, 640 x 480 screen resolution,
and visual themes. If the program is an old game or educational program that fills the entire
screen with simple graphics, choose all three options. If the program runs in a program window,
you probably don’t need to choose any of those options. Click Next>.
7. The next page asks about running the program with full administrative privileges. Choose that
option only if you’re an administrator and the program doesn’t run at all. Click Next>.
8. You’re taken to a summary of your selected options. Click Next> again to test your choices.
The rest is trial-and-error. If the program runs, great. You can answer accordingly in the wizard and be done
start or isn’t working right, try using the Program Compatibility Wizard on it.
The Program Compatibility Wizard provides a step-by-step means of configuring and testing an older program
so that it will run in Windows Vista. Before you bother to use it, try running the installed program
without it. I mention this because I’ve seen people spend much time messing with this on the assumption
that it’s needed. When in fact, the assumption was wrong and they could have just run the program as-is!
If you’re sure an installed program isn’t running, or is not running correctly, follow these steps to start the
Program Compatibility Wizard:
1. Click the Start button and choose All Programs ➪ Accessories ➪ Program Compatibility Wizard.
2. Read the first wizard page and click Next>.
n I want to choose from a list of programs: If the program is already installed and has an icon
on the All Programs menu, choose this option.
n I want to use the program in the CD-ROM drive: If the program isn’t installed and needs to
be installed or run from a CD, choose this option.
n I want to locate the program manually: If the program isn’t on the All Programs menu, but
you know the path and filename of the program, choose this option.
4. Follow the instructions on the next wizard page. For example, if you chose the first option, scroll
through the list of program names and click the program you want to run in compatibility mode.
Then click Next>.
5. On the next page, choose the operating system that the program was written for, or the last operating
system on which you were able to run the program. Then click Next>.
6. The next wizard page will ask about display settings, such as 256 colors, 640 x 480 screen resolution,
and visual themes. If the program is an old game or educational program that fills the entire
screen with simple graphics, choose all three options. If the program runs in a program window,
you probably don’t need to choose any of those options. Click Next>.
7. The next page asks about running the program with full administrative privileges. Choose that
option only if you’re an administrator and the program doesn’t run at all. Click Next>.
8. You’re taken to a summary of your selected options. Click Next> again to test your choices.
The rest is trial-and-error. If the program runs, great. You can answer accordingly in the wizard and be done
Subscribe to:
Posts (Atom)