How To Make Bootable Cd Winpe 2.0, down load link toWAIK (Vista PE) Options

[Ben_Mott]

down load details VISTA WAIK(windows automated instruction kit)Free down load site:
down load page

<a href="http://blogs.msdn.com/winre/" target="_blank">http://blogs.msdn.com/winre/</a>
instruction and Batch files for down load
<a href="http://www.boxpost.orangehome.co.uk/vistaimaging.htm" target="_blank">http://www.boxpost.orangehome.co.uk/vistaimaging.htm</a>

<a href="http://vista.elemneo.pl/2007/03/11/vista-l...softmod-update/" target="_blank">http://vista.elemneo.pl/2007/03/11/vista-l...softmod-update/</a>

<a href="http://blogs.msdn.com/wga/archive/2007/04/...bios-hacks.aspx" target="_blank">http://blogs.msdn.com/wga/archive/2007/04/...bios-hacks.aspx</a>


<a href="http://www.magiciso.com/tutorials/miso-mag...sc-overview.htm" target="_blank">http://www.magiciso.com/tutorials/miso-mag...sc-overview.htm</a>


<a href="http://www.microsoft.com/downloads/details...;displaylang=en" target="_blank">http://www.microsoft.com/downloads/details...;displaylang=en</a>


<a href="http://technet.microsoft.com/en-us/windows...905120.aspx#EPB" target="_blank">http://technet.microsoft.com/en-us/windows...905120.aspx#EPB</a>


<a href="http://www.911cd.net/forums//index.php?showtopic=18758" target="_blank">http://www.911cd.net/forums//index.php?showtopic=18758</a>


<a href="http://www.911cd.net/forums//index.php?showtopic=19010" target="_blank">http://www.911cd.net/forums//index.php?showtopic=19010</a>

<a href="http://vistape.boot-land.net/eng/index.html" target="_blank">http://vistape.boot-land.net/eng/index.html</a>
BitLocker useful info:
<a href="http://apps.wharton.upenn.edu/brainstorm/i...p;entry_id=1175" target="_blank">http://apps.wharton.upenn.edu/brainstorm/i...p;entry_id=1175</a>


<a href="http://www.microsoft.com/windowsvista/expe...ces/backup.mspx" target="_blank">http://www.microsoft.com/windowsvista/expe...ces/backup.mspx</a>

works with PE2
<a href="http://selfimage.excelcia.org/" target="_blank">http://selfimage.excelcia.org/</a>
Opera works with PE 2
(wired connection to router)
firefox works too

<a href="http://www.multibooters.co.uk/cloning.html" target="_blank">http://www.multibooters.co.uk/cloning.html</a>
<a href="http://www.acronis.com/homecomputing/products/trueimage/" target="_blank">http://www.acronis.com/homecomputing/products/trueimage/</a>

For those who have had to use the command prompt based bcdedit.exe in the past, you will be impressed with the ease of use and functionality that VistaBootPRO provides.Free Beta: Personally I find BCDEDIT.exe very complicated.

<a href="http://www.vistabootpro.org/track/click.php?id=2" target="_blank">http://www.vistabootpro.org/track/click.php?id=2</a>

<a href="http://www.vistabootpro.org/" target="_blank">http://www.vistabootpro.org/</a>
the above tool is good if you got Vista installed on HDD but is not working in VistaPE
if any body can get it working in Vista PE please post the solution

Instructions for above down load
1. Click the Download button on this page to start the download
2. Click Save or Save this program to your computer. Windows AIK is distributed as an .iso file.
3. Burn the saved iso to a DVD
4. Insert the DVD into the machine
5. Click Windows AIK Setup to begin the installation

detail instruction to make windows PE2 bootable CD and how to use it
http://www.svrops.com/svrops/articles/winvistape2.htm


<a href="http://www.apcstart.com/node/3894" target="_blank">http://www.apcstart.com/node/3894</a>

<a href="http://www.multibooters.co.uk/multiboot.html" target="_blank">http://www.multibooters.co.uk/multiboot.html</a>
<a href="http://www.multibooters.co.uk/cloning.html" target="_blank">http://www.multibooters.co.uk/cloning.html</a>
Vista Boot Floppy
<a href="http://www.multibooters.co.uk/floppy.html" target="_blank">http://www.multibooters.co.uk/floppy.html</a>

....................................
GPT FAQ
<a href="http://www.microsoft.com/whdc/device/storage/GPT_FAQ.mspx#E2" target="_blank">http://www.microsoft.com/whdc/device/storage/GPT_FAQ.mspx#E2</a>





related articles:

<a href="http://www.apcstart.com/site/jbannan/2006/...talls-made-easy" target="_blank">http://www.apcstart.com/site/jbannan/2006/...talls-made-easy</a>
<a href="http://www.apcstart.com/site/jbannan/2006/...im-format-with-" target="_blank">http://www.apcstart.com/site/jbannan/2006/...im-format-with-</a>

imagex
<a href="http://www.apcstart.com/site/dwarne/2006/0...e-based-install" target="_blank">http://www.apcstart.com/site/dwarne/2006/0...e-based-install</a>
<a href="http://www.apcstart.com/site/jbannan/2006/...sta-install-dvd" target="_blank">http://www.apcstart.com/site/jbannan/2006/...sta-install-dvd</a>

<a href="http://technet2.microsoft.com/WindowsVista...3.mspx?mfr=true" target="_blank">http://technet2.microsoft.com/WindowsVista...3.mspx?mfr=true</a>

<a href="http://technet.microsoft.com/en-us/windows...a/aa905070.aspx" target="_blank">http://technet.microsoft.com/en-us/windows...a/aa905070.aspx</a>


<a href="http://blogs.msdn.com/winre/archive/2006/09/18/760295.aspx" target="_blank">http://blogs.msdn.com/winre/archive/2006/09/18/760295.aspx</a>
<a href="http://blogs.msdn.com/winre/" target="_blank">http://blogs.msdn.com/winre/</a>

..............................................
copy imageX.exe to ISO folder before making WinPE2.0 CD , ISO image so it will be in the root of CD (D:) for access.

To capture and store the installation onto a network share
In this step, you will capture image of your master computer using Windows PE and ImageX. You will then store that image onto a network share.
1. On your master computer, insert your Windows PE media and restart the computer.
Windows PE will start and launch a command-prompt window.
Note When you boot your master computer, you must override the boot order to boot from the CD/DVD-ROM drive. During initial boot, select the appropriate function key to override the boot order.
2. Capture an image of the master installation by using ImageX located on your Windows PE media. For example, from the command-prompt window, type:
d:\tools\imagex.exe /compress fast /capture c: c:\myimage.wim "my Vista Install" /verify
3. Copy the image to a network location. Windows PE provides network support. For example, from the command-prompt window, type:
net use y: \\network_share\images (works with wired networks not wireless)
copy c:\myimage.wim y:
If necessary, provide network credentials for appropriate network access.
Deploy an Image
After you have an image of your master installation, you can deploy the image onto new hardware by using ImageX and Windows PE.
The basic process includes:
1. Assembling new hardware.
2. Booting new hardware using Windows PE media.
3. Formatting the hard drive.
4. Connecting to your network share and copying the custom image down to your local hard drive.
5. Applying the image by using ImageX.
To deploy a custom image from a network share
In this step, you will use DiskPart to format the hard drive, and then copy an image down from the network share. For this example, use your master computer as your destination computer.
1. On your destination computer, insert your Windows PE media and restart the computer.
Windows PE will start and launch a command-prompt window.
Note Because this was your master computer, the hard drive contains an active partition. You must override the boot order to boot from the CD/DVD-ROM drive. During initial boot, select the appropriate function key to override the boot order. If this is a newly assembled computer, the hard drive would be unformatted and this step could be skipped.
2. Format the hard drive to reflect the required disk configuration requirements by using DiskPart. For example, from a command prompt, type:
diskpart
select disk 0
clean
create partition primary size=20000
select partition 1
active
format
exit
Note You can script this information by saving this information to a text file and storing it in the same location as your image. To run the script from a Windows PE command prompt, type diskpart /s scriptname.txt
3. Copy the image from the network share to your local hard drive. For example, from the command prompt, type:
net use y: \\network_share\images
copy y:\myimage.wim c:
If necessary, provide network credentials for appropriate access.
4. Apply the image to the hard drive using ImageX located on your Windows PE media. For example, from the command-prompt window, type:
d:\tools\imagex.exe /apply c:\myimage.wim 1 c:
Your custom image is now deployed onto your destination computer. The computer is ready for customer delivery. You can repeat the previous steps for each additional machine you want to ship.
..........................................................................

Now that you have an .iso file, winpe.iso, all you have to do is burn a CD/DVD from the winpe.iso file and you will have a bootable WinPE 2.0 CD/DVD.


8. Instead of a creating a bootable CD, you can also create a bootable UFD (USB Flash Drive). To do this, do the following:

Place a USB flash drive in a USB port on a Windows Vista PC.
(a 1GB flash drive is more than big enough).
Delete any files on the USB drive.
Partition and format the USB flash drive using Diskpart (next).

Note: According to the Windows PE documentation, the following Diskpart commands must be done on a Windows Vista PC. This is because Windows Vista Diskpart.exe has the ability to see and use USB flash drives. Earlier version of Diskpart do not. (see Additional Notes below)

This set of commands assumes your USB flash drive is detected as disk 1. You should double check this by listing the disks before cleaning the USB drive. Open a command prompt window and type the following commands, pressing <enter> after each command.

• Diskpart
• List disk
(this command is important. It will show you what disk your USB Flash Drive is. Most likely it will be Disk 1. You don’t want to format your C: drive !)

• select disk 1
• clean
• create partition primary
• select partition 1
• active
• format fs=fat32
• assign
• exit




You will now have a partitioned and formatted USB flash drive. All that is needed to create a bootable USB WinPE 2.0 flash drive is to copy the Winpe\ISO folders and files onto the USB flash drive. Insert the USB flash drive into a USB port on the Technician PC - that you have the c:\winpe directory structure on, open a command prompt window, and run the following command to copy the contents to the USB flash drive:

xcopy c:\winpe\iso\*.* f:\ /e/h/f <enter>

change f:\ to reflect your USB flash drive.

That's it. You now have a bootable USB WinPE 2.0 flash drive.

Note: You will have to set your PC BIOS to boot from a USB device in order to boot from the WinPE USB Flash Drive.

REF:
<a href="http://www.svrops.com/svrops/articles/winvistape2.htm" target="_blank">http://www.svrops.com/svrops/articles/winvistape2.htm</a>


===========================================================================



regards Ben


This post has been edited by Ben_Mott: Oct 24 2007, 03:29 AM

[Ben_Mott]

after down loading 849MB of *.img file and writing it as data using nero to a DVD
I can not get DVD to BOOT !!!!!
I do not know wether it is my Machine which is too old or wether the image file got corropted on down load .??
on the web site it says it is an ISO file but down load is .img file !!
I have not got to stage where I can down load and make the PE cd

I am going to open it up with ISO buster or winimage and have a look at file structures see if there is a way round this.
has any body else successfully downloaded and made a bootable DVD and installed the WAIk and
made the PE2 ?? on a bootable CD ??/

Regards Ben

[Björn Kaiser]

the ISO image contains the WAIK including the parts to build WinPE 2.0. That is the reason why your DVD is not bootable. You need to install the WAIK and then build the PE ISO Image.

[Ben_Mott]

first thanks to Bjoran Kaser for replying.
success
I opened that image file (849 GB ) in windows XP (SP2) using win image
then I extracted all the files and folders to a temperary folder(tempPE2) then when I looked on that folder it had
autorun.inf file and had a look at that and that pointed to start cd.exe
so i double clicked on that and it opened the menu which was supposed to open up when you booted the DVD
from that menue(still in windows XP) i clicked install windowsAIK
and it successfully installed the aik on the c:\program files\windowsaik\
then i opened a command window and navigated to c:\program files\windowsaik\tools\petools
and in there i typed
copype.cmd x86 c:\temp\X86_PE

it copied the files to that folder took 2 or 3 minutes still in same directory that is petools
i typed the command to make iso which was:
OSCDIMG -bc:\temp\x86_pe\etfsboot.com -n -o c:\temp\x86_pe\iso c:\temp\x86_pe.iso
and it success fully made iso
note that bc are attached togerther I first thought it was wrong and put space in middle and got error message
so I changed it to above and all went well

I am going to copy the ISO (176MB ) to an ordinary CD-r and then test it
thanks again Ben

[Nuno Brito]

Nice link Ben!

When I get my DVD of Vista for christmas I'll surely try it out..


I've noticed that sometimes the output contents are modified when using these image extraction programs, like empty folders available on the image wich are not created on the output and even changing the filecase of filenames to uppercase.

I would recommend taking a look on this freeware virtual drive to load the .img and simply copy/install the files using windows explorer:
http://www.pobieralnia.com/Article1064.htm

This feature is also available from Alcohol 120% (not freeware) or Daemon tools (wich installs adware).


Does the CD boot up quickly?

[Ed_P]

after down loading 849MB of *.img file and writing it as data using nero to a DVD
I can not get DVD to BOOT !!!!!
I do not know wether it is my Machine which is too old or wether the image file got corropted on down load .??
on the web site it says it is an ISO file but down load is .img file !!
I have not got to stage where I can down load and make the PE cd

This happens because of an IE security setting for downloading files based on content rather than on extention. When prompted with IE's Save the file window, change the Save as type: to All files before clicking on the Save button.

To prevent this problem from reoccuring go to Control Panel>Internet Properties>Security tab>Custom Level button and scroll down to the Open files based on content, not file extention option and change the selection from Enable to Disable. Now your system won't rename files you download.

If you renamed the .img to .iso and burned it to a DVD/CD rather than copying it as data it would have booted ok.

[Ben_Mott]

Ed thanks for all your very informative advise.
going to write it down some where for the future.

any way i think I claimed success too quickly
I wrote that X86_PE.ISO
to CD-R using Nero(as data just write command)thinking the ISO would be bootable .
as there was a mention of a bootable file (etfsboot.com) in the instruction.
any way the resulting CD-R is not booting .
also tried it on another Pc no joy

back to drawing board
and a good hard think
Regards Ben

[Björn Kaiser]

weird. don't know what could have gone wrong. Your OSCDIMG command looks correct, the size of the ISO is as mine was without additions.
You didn't write the ISO as a file did you? You have to write a CD from an Image in Nero. If you can see the ISO as a file on the CD, well throw it away.

[Nuno Brito]

In case you've written the ISO correctly, you should also check if both the image and the CD have the exact number of folders and that files remain in their original upper/lower cases.

I've recently had some experiences in wich this interfered with the boot CD and caused booting to fail, it was based on ReactOS liveCD but might be a similar issue to this case:
http://www.boot-land.net/forums/index.php?...post&p=5885

[Ben_Mott]

Thanks to Nuno Brito, Ed and Bjon kaiser,
I managed to make a bootable ISO from the X86_PE.ISO
I think I was a bit Thick using the new version of Nero Express I got with my New(fairly) DVD rewriter
this time i used the right section on the menu which was "disk image or saved project"
when it boots it asks to press a key to boot from cd and it takes a few minutes to load properly to the command line option mentioned on one of those links.
this time when you look at the cd in windows it has :
BOOT folder
EFI folder
SOURCE folder
bootMGR (file 429 K)
..........................
before Iwas just seeng the .ISO file
...........................
thanks for all your help and taking the time to give such valuable advise
I feel much happier that I have got this far
I am going to read all the links and play around with it tomorrow.
.................
Regards Ben

[Ed_P]

[Ben_Mott]

the bootablle PE is command line and a bit minimulistic.
it seems that winpe.wim is the image file of vista
and reside in 2 places
C:\programfiles\windowsaik\tools\petools\X86
C:\programfiles\windowsaik\tools\petools\amd64
I had a look at
COPYPE.CMD
....................
@echo off
setlocal

set _P=%~dp0%
set TEMPL=ISO

if /i "%1"=="" goto usage
if /i "%2"=="" goto usage
if /i not "%3"=="" goto usage
set SOURCE=%_P%%1
set DEST=%2

if not exist "%SOURCE%\winpe.wim" (
echo Invalid architecture: %1
goto :EOF
)

if exist "%DEST%" (
echo Destination directory exists: %2
goto :EOF
)

mkdir "%DEST%"
if errorlevel 1 (
echo Unable to create destination: %2
goto :EOF
)

echo.
echo ===================================================
echo Creating Windows PE customization working directory
echo.
echo %DEST%
echo ===================================================
echo.

mkdir "%DEST%\%TEMPL%"
if errorlevel 1 goto :FAIL
mkdir "%DEST%\mount"
if errorlevel 1 goto :FAIL

if exist "%SOURCE%\bootmgr" copy "%SOURCE%\bootmgr" "%DEST%\%TEMPL%"
if errorlevel 1 goto :FAIL
if exist "%SOURCE%\bootmgr.efi" copy "%SOURCE%\bootmgr.efi" "%DEST%\%TEMPL%"
if errorlevel 1 goto :FAIL
if exist "%SOURCE%\boot\etfsboot.com" copy "%SOURCE%\boot\etfsboot.com" "%DEST%"
if errorlevel 1 goto :FAIL
if exist "%SOURCE%\boot\efisys.bin" copy "%SOURCE%\boot\efisys.bin" "%DEST%"
if errorlevel 1 goto :FAIL
if exist "%SOURCE%\boot" xcopy /cherky "%SOURCE%\boot" "%DEST%\%TEMPL%\boot\"
if errorlevel 1 goto :FAIL
if exist "%SOURCE%\EFI" xcopy /cherky "%SOURCE%\EFI" "%DEST%\%TEMPL%\EFI\"
if errorlevel 1 goto :FAIL
mkdir "%DEST%\%TEMPL%\sources"
if errorlevel 1 goto :FAIL
copy "%SOURCE%\winpe.wim" "%DEST%\winpe.wim"
copy "%SOURCE%\winpe.wim" "%DEST%\%TEMPL%\sources\boot.wim"
if errorlevel 1 goto :FAIL

endlocal
echo.
echo Success
echo.
echo Updating path to include peimg, oscdimg, imagex
echo.
echo %~dp0
echo %~dp0..\%PROCESSOR_ARCHITECTURE%
echo.

set PATH=%PATH%;%~dp0;%~dp0..\%PROCESSOR_ARCHITECTURE%
cd /d "%2"

goto :EOF

:usage
echo Usage: copype [x86 ^| amd64] destination
echo.
echo Example: copype x86 c:\windowspe-x86
goto :EOF

:FAIL
echo Failed to create working directory
.........................................
it needs a knowlageble person to make that image a GUI one
how to inject programs etc into the Image file ?????
edited11dec 06

sorry I think from now on i am in wrong forum as i managed the bootable CD part and need to go to the PE forum
http://www.911cd.net/forums//index.php?showtopic=18758
the above Link seems to be what I am looking for .

Regards Ben

[Ben_Mott]

just a quick update:
went to above link very useful instructions

as i had touble making Burning the ISO earlier with nero express this time I draged and droped it in
our SKEWITeck application (chap who is member of bootable Cd forum)
................................................................................
........
Unzip the contents of bellow and then drag and drop an ISO file onto the ISO2EXE script... it

does the rest." from SKEWITEK
http://www.boxpost.orangehome.co.uk/iso2exe.zip
.................................................
any way it worked straight away 1st it compressed the ISO to 166MB as an executable then when I double clicked the executable it copied the ISO to CD-R as a bootable Cd without asking a single question
......................................................
I find PE 2.0 very fast once it gets to the command prompt it is speedy gonzalez if Vista is as fast as that
it is great improvement.
or is it because it is working from RAM drive ????
Regards Ben

[edborg]

Naive questions:

1. What's Vista WAIK (849 MB) as compared with the Vista DVD?
2. Is the free Vista DVD (RC1/2) no longer available from the net? (It isn't from MS).
3. If the only solution is to buy the DVD, when/where will it be available?

Thanks
edborg

[Ben_Mott]

I think it is still available to MSDN Partners (or something like that )
any way it meant a lot of file filling and may be some sort of organizational comitment.
after filling a few forms and getting log in and pass word I still did not see the down load link
so I left it.
now that there is a PE builder available from our Russian Programmers ( some more Very clever people)
http://www.911cd.net/forums//index.php?showtopic=19010
http://vistape.boot-land.net/eng/index.html

I might go and have another go see if I can down load Vista even it it is for limited period .
I was reading the WAIK Vista Installation Help files many many pages and I was thinking
scratching my head !! that you need to be have IT Computer degree to install that Operating system across a network or get an image like ghost does with progs and drivers.
I nearly fell sleep reading all that bal bla , I am going to have another go at it .
................................................................................
................................................................................
.
......................
Requirements
To complete this scenario, you need the following:
 Window Vista product DVD.
 Windows AIK Download.
 A technician computer.
 A master computer.
 Network connectivity to simulate deployment.
 Floppy disk or Universal Flash Device (UFD), such as a USB memory key.
 One blank CD-R/RW disc.

The technician computer is the computer in your lab on which you install the Windows AIK. The technician computer can be any computer running Windows XP, Windows Server 2003, or Windows Vista. This computer requires a DVD-ROM drive and CD-R/RW-capable drive, or a combo drive that supports both.
A master computer, sometimes called a reference computer, is a fully assembled computer on which you install a customized installation using the Windows product DVD and your custom answer file. Once installed, you capture and store an image of the installation on a network share. There are no software requirements for this computer. Both technician and master computers require a network card and working network environment.
Note For the purposes of this example, the master computer will serve as your master and destination computer. The master/destination computer represents the computer you are about to deploy. After you build a master installation, you will capture and store an image of that installation on a network share. You will then reformat the hard drive, returning it to a blank state. The computer now becomes your destination computer. You will then deploy the image from the network share back onto the same computer. This process simulates an image-based deployment.
Build a Lab Environment
A lab environment is where you define and build your installation. A lab environment consists of two computers: a technician computer and a master computer.
To build a technician computer
 On your designated technician computer, download and install the Windows AIK. The Setup program will automatically start. Follow the online instructions.
To build a master computer
 Assemble the new computer. The computer must have a DVD-ROM drive, network card, and a floppy disk drive or USB support. There are no preinstalled software requirements.
Build an Answer File
The first step in creating a custom installation is to build an answer file. An answer file stores the custom settings that are applied during Windows Setup. The primary method for creating an answer file is to use Windows SIM.
The basic process includes:
1. Creating a new answer file.
2. Adding a component or package to an answer file.
3. Changing the value of a setting in an answer file.
4. Validating an answer file.
5. Saving an answer file to floppy disk or UFD.
After you have successfully created a basic answer file, you can build a master installation.
To create a new answer file
In this step, you will build a catalog and then a new blank answer file. A catalog (.clg) is a binary file that contains the state of all of the settings and packages in a Windows image.
1. From your technician computer, insert the Windows Vista product DVD into the local DVD-ROM drive.
2. From your desktop, navigate to the \sources directory on your DVD-ROM drive. Copy install.wim from the product DVD to a location on your technician computer.
3. Open Windows SIM. From your desktop, click Start, point to Programs, point to Microsoft Windows AIK, and then click Image Manager.
4. On the File menu, click Select Windows Image.
5. In the Select a Windows Image dialog box, navigate to the location where you saved install.wim, and then click Open.
6. In the Select an Image dialog box, select the appropriate version of Windows Vista, and then click OK.
7. On the File menu, click New Answer File.
Note A warning will appear that a catalog does not exist. Click OK to create a catalog. You must create a catalog for each version of Microsoft Windows Vista.
To add and configure Windows settings
In this step, you will define basic disk configuration and Windows Welcome options.
1. In Windows SIM, in the Windows Image pane, expand the Component node to display available settings.
2. From the expanded list of components, add the following components to your answer file by right-clicking the component and then selecting the appropriate configuration pass. This action will add the component to your answer file in the specified configuration pass. A configuration pass is a phase of Windows installation. Different parts of the Windows Vista operating system are installed in different configuration passes. You can specify settings to be applied in one or more configuration passes.

Component Configuration Pass
Microsoft-Windows-Setup\DiskConfiguration\Disk\CreatePartitions\CreatePartition 1 windowsPE
Microsoft-Windows-Setup\DiskConfiguration\Disk\ModifyPartitions\ModifyPartition 1 windowsPE
Microsoft-Windows-Setup\ImageInstall\OSImage\InstallTo 1 windowsPE
Microsoft-Windows-Setup\UserData 1 windowsPE
Microsoft-Windows-Shell-Setup\OOBE 7 oobeSystem
Microsoft-Windows-Shell-Setup\AutoLogon 7 oobeSystem
Microsoft-Windows-International-Core-WinPE 1 windowsPE

Note Expand the component list until you see the lowest setting listed above, and then add that setting to your answer file. This shortcut will add the setting and all parent settings to your answer file in one step.
3. All the settings you added should appear in the Answer File window pane. Select and configure each setting as specified below.
Component Value
Microsoft-Windows-Setup\DiskConfiguration WillShowUI = OnError
Microsoft-Windows-Setup\DiskConfiguration\Disk DiskID = 0
WillWipeDisk = true
Microsoft-Windows-Setup\DiskConfiguration\Disk\CreatePartitions\CreatePartition Extend = false
Order = 1
Size = 20000 (Note: This example creates a 20-GB partition.)
Type = Primary
Microsoft-Windows-Setup \DiskConfiguration\Disk\ModifyPartitions\ModifyPartition Active = true
Extend = false
Format = NTFS
Label = OS_Install
Letter = C
Order = 1
PartitionID = 1
Microsoft-Windows-Setup\ImageInstall\OSImage\ WillShowUI = OnError
Microsoft-Windows-Setup\ImageInstall\OSImage\InstallTo DiskID = 0
PartitionID = 1
Microsoft-Windows-Setup\UserData AcceptEula = true


Component Value
Microsoft-Windows-Setup\UserData\ProductKey Key = <product key>
WillShowUI = OnError
Microsoft-Windows-Shell-Setup\OOBE HideEULAPage = true
ProtectYourPC = 3
SkipMachineOOBE = true
SkipUserOOBE = true
Microsoft-Windows-International-Core-WinPE InputLocale = <Input Locale>
SystemLocale = <System Locale>
UILanguage = <UI Language>
UserLocale = <User Locale>
Microsoft-Windows-International-Core-WinPE\SetupUILanguage UILanguage = <UI Language>
Microsoft-Windows-Shell-Setup\AutoLogon Enabled = true
LogonCount = 5
Username = Administrator
Microsoft-Windows-Shell-Setup\AutoLogon\Password <strongpassword>

The settings above outline a basic unattended installation; no user input is required during Windows Setup.
To validate and save settings
In this step, you will validate the settings in your answer file and then save them to a file.
1. In Windows SIM, click Tools, and then click Validate Answer File. The setting values in the answer file are compared with the available settings in the Windows image.
2. If the answer file validates successfully, a “success” message appears in the Messages pane; otherwise, error messages appear in the same location.
3. If an error occurs, double-click the error in the Messages pane to navigate to the incorrect setting. Change the setting to fix the error, and then revalidate.
4. On the File menu, click Save Answer File. Save the answer file as Autounattend.xml.
5. Copy Autounattend.xml to the root of a floppy disk or UFD.
You now have a basic answer file that automates Windows Setup. For more information on building answer files, see “Phase 3: Preinstallation Customization”, in Waik.chm.
Build a Master Installation
A master computer is a customized installation of Windows that you plan to duplicate onto one or more destination computers. By using the Windows product DVD and an answer file, you can create a master installation.
The basic process includes:
1. Assembling new hardware.
2. Installing Windows from a Windows product DVD and answer file.
3. Verifying installation and customizations.
4. Shutting down the computer when the installation is complete.
To install Windows from the Windows product DVD
1. Turn on the new computer.
2. Insert removable media containing the answer file (Autounattend.xml) and Windows Vista product DVD into the new computer.
3. Restart the computer (CTRL+ALT+DEL).
This example assumes the hard drive is blank. Windows Vista Setup (Setup.exe) will begin automatically. By default, Windows Setup will search all removable media for an answer file called Autounattend.xml.
4. After Setup finishes, validate that all customizations were applied.
5. Reseal (generalize) and shut down the computer. From a command prompt, type: c:\windows\system32\sysprep\sysprep.exe /oobe /generalize /shutdown.
Sysprep will prepare the image for capture by cleaning up various user and machine settings and log files. The master installation is complete and ready to be imaged.
Create an Image
After you build a master installation, you can deliver the new computer to a user, and then repeat the previous steps for each new computer. However, it is more efficient to capture an image of the master installation and then deploy that image onto other new computers. The primary tools for completing this process are ImageX and Windows PE. ImageX is a command-line tool that enables you to capture, modify, and apply file-based disk images. Windows PE provides an environment from which you can capture and deploy an image.
In this example, ImageX is used in a Windows PE environment. For more information on these tools, see “Deployment Tools Technical Reference” in Waik.chm.
The basic process includes:
1. Creating a bootable Windows PE media.
2. Booting the master installation by using Windows PE media.
3. Capturing the installation image by using ImageX.
4. Storing the image on a network share.
To create bootable Windows PE media
In this step, you will create a bootable Windows PE RAM CD. You will use this CD to capture an image of your master computer and later deploy that image onto your destination computer.
1. From your technician computer, run the copype.cmd script to create a local Windows PE build directory. For example, from a command prompt, type:
cd Program Files\Windows AIK\Tools\PETools\
copype.cmd <arch> <destination>
Where <arch> can be x86, amd64, or ia64 and <destination> is a path to local directory. For example,
copype.cmd x86 c:\winpe_x86
2. Copy additional tools like ImageX into your Windows PE build directory. For example,
copy “c:\program files\Windows AIK\Tools\x86\imagex.exe” c:\winpe_x86\iso\
3. Optionally, create a configuration file called wimscript.ini using any text editor, for example Notepad. The configuration file will instruct ImageX to exclude certain files during the capture operation. For example,
[ExclusionList]
ntfs.log
hiberfil.sys
pagefile.sys
"System Volume Information"
RECYCLER
Windows\CSC

[CompressionExclusionList]
*.mp3
*.zip
*.cab
\WINDOWS\inf\*.pnf
4. Save the configuration file to the same location as ImageX as specified in the previous step. For example:
c:\winpe_x86\iso\
ImageX will automatically detect wimscript.ini if located in the same location.
5. Create an image (.iso) file by using the Oscdimg tool. For example, from a command prompt, type:
cd program files\Windows AIK\Tools\PETools\
oscdimg -n –bc:\winpe_x86\etfsboot.com c:\winpe_x86\ISO c:\winpe_x86\winpe_x86.iso
6. Burn the image (winpe_x86.iso) to a CD-ROM.
Windows AIK does not include CD-ROM burning software. Use any third-party software to burn the image to a CD-ROM.
You now have a bootable Windows PE RAM CD with ImageX. For more information on customizing Windows PE, see the Windows Preinstallation Environment (Windows PE) User’s Guide (Winpe.chm).
To capture and store the installation onto a network share
In this step, you will capture image of your master computer using Windows PE and ImageX. You will then store that image onto a network share.
1. On your master computer, insert your Windows PE media and restart the computer.
Windows PE will start and launch a command-prompt window.
Note When you boot your master computer, you must override the boot order to boot from the CD/DVD-ROM drive. During initial boot, select the appropriate function key to override the boot order.
2. Capture an image of the master installation by using ImageX located on your Windows PE media. For example, from the command-prompt window, type:
d:\tools\imagex.exe /compress fast /capture c: c:\myimage.wim "my Vista Install" /verify
3. Copy the image to a network location. Windows PE provides network support. For example, from the command-prompt window, type:
net use y: \\network_share\images
copy c:\myimage.wim y:
If necessary, provide network credentials for appropriate network access.
Deploy an Image
After you have an image of your master installation, you can deploy the image onto new hardware by using ImageX and Windows PE.
The basic process includes:
1. Assembling new hardware.
2. Booting new hardware using Windows PE media.
3. Formatting the hard drive.
4. Connecting to your network share and copying the custom image down to your local hard drive.
5. Applying the image by using ImageX.
To deploy a custom image from a network share
In this step, you will use DiskPart to format the hard drive, and then copy an image down from the network share. For this example, use your master computer as your destination computer.
1. On your destination computer, insert your Windows PE media and restart the computer.
Windows PE will start and launch a command-prompt window.
Note Because this was your master computer, the hard drive contains an active partition. You must override the boot order to boot from the CD/DVD-ROM drive. During initial boot, select the appropriate function key to override the boot order. If this is a newly assembled computer, the hard drive would be unformatted and this step could be skipped.
2. Format the hard drive to reflect the required disk configuration requirements by using DiskPart. For example, from a command prompt, type:
diskpart
select disk 0
clean
create partition primary size=20000
select partition 1
active
format
exit
Note You can script this information by saving this information to a text file and storing it in the same location as your image. To run the script from a Windows PE command prompt, type diskpart /s scriptname.txt
3. Copy the image from the network share to your local hard drive. For example, from the command prompt, type:
net use y: \\network_share\images
copy y:\myimage.wim c:
If necessary, provide network credentials for appropriate access.
4. Apply the image to the hard drive using ImageX located on your Windows PE media. For example, from the command-prompt window, type:
d:\tools\imagex.exe /apply c:\myimage.wim 1 c:
Your custom image is now deployed onto your destination computer. The computer is ready for customer delivery. You can repeat the previous steps for each additional machine you want to ship.
Summary
You have now completed a basic end-to-end deployment scenario using an image-based deployment method. You have successfully created a lab environment, your first answer file, a bootable Windows PE CD, and your first custom Windows image. You have a basic understanding of how to use Windows SIM and the ImageX and Windows PE technologies.
The next step is to make additional customizations to your answer file and expand your knowledge of the deployment tools. You can automate parts of the deployment process by scripting the Windows PE sections in this example. For a comprehensive description of the tools and other deployment methods, see the Windows Automated Installation Kit User’s Guide (Waik.chm
................................................................................
................................................................................
.
........................

after i mounted the boot.wim image using imagex /rw I tried to install some program like calcplus into it using
peimg install= ............ command and i got a weird eror message so
I went to mount directoryin windows explorer this time and had a look at i it was hidden and read only so i right clicked on it and
choose properties. and then unticked hidden and read only flags , windows Xp did some performance
and then i drilled down to windows folder and right cliked on that and choose properties. and removed the
flag there too. then drilled down to system32 folder and did the same and the opened it and copy and pasted the calcplus.exe and A43.exe to that folder.
then i ran the imagex /unmount ..................................../commit
and then made an iso and a bootable cd found that after PEvista loaded it had the calcplus on it in system32 folder and I could call it and it would show in GUI and work ok.
but I found that the same cd acts differntly on different computers the other computer which had 3 partitions on it did not run the vista PE (even with P4) as well as the computer with P3( 1partition).

Regards Ben

[Ben_Mott]

Just an observation or conflict which i had recently with winpe2 when i mount it
and try to have a look at it in windows explorer as soon as i open it the Pc crahes
it was not like this last week I couls even open the mount directory and add things to windows/system32 directory.
last week when i was in another forum some body suggested that Norton Restore and Recover had ghost32.exe on it .
so I thought i down load the Trial version and have look for my self as i thought that could come handy for Bart PE Bootable CD
any way to cut the story short the ghost32.exe was not on it even under another name and so i decided to
remove it which i did .
every thing was alright except this mounting of winpe.wim folder
so I restore back to a date before instullation then tested still problem(crash to black screen as soon as mount and try to open directory)
so i did a chkdsk /r still no good
it works in command line window using dir etc i can see all files which are mounted so can still make ISo etc.
so no big problem except very curious why imagex.exe or what did the Norton changed may be put an older DLL file etc who knows with windows .
when I looked at message from Microsoft it said it was device driver fault ( the usual wash your hand off the prob attitude).
I have a feeling a lot of older software are going to have problem with VISTA
any way Astalla VISTA
Regards Ben

here is some useful information:

How to install WinRE on the hard disk

So here's the simple four step process.

Step 1: Choosing a partition to install WinRE

The hardest part about installing WinRE seems to be deciding where to install it. The following considerations should go into deciding which partition to choose (listed in the priority order):

1. The partition should not be the same as the Windows OS partition. This is so that you can boot into WinRE even if your OS partition becomes corrupt or inaccessible for any reason. This helps maximize the chances that you would be able to boot into WinRE when your main Windows installation is in trouble.
2. The partition should be hidden so that users do not accidentally delete files or corrupt the WinRE installation in anyway. Microsoft has defined a special partition type for this specific purpose. On MBR disks, the partition should be assigned partition type 0x27. And on GPT disks, the partition should have the partition type GUID: {DE94BBA4-06D1-4D40-A16A-BFD50179D6AC}.
3. The partition should not interfere with any advanced volume management functionalities, such as dynamic volumes. Any hidden partitions after the Windows OS partition may interfere with dynamic volume creations. Therefore, the WinRE partition should be created before the Windows OS partition.

In the OPK and the WAIK, we have a couple of partition layout recommendations. These recommendations were made by following the above considerations. These recommendations are:

1. If the machine is not bitlocker enabled, then the partition should be a hidden recovery partition allocated before the OS partition. It should be assigned type 0x27 on MBR disks and type {DE94BBA4-06D1-4D40-A16A-BFD50179D6AC} on GPT disks. The partition should be at least large enough to hold WinRE WIM, 1.5GB should be plenty for the base WinRE.
2. If the machine is bitlocker enabled, then the BDE partition (a.k.a. the system partition) can be used for WinRE installation.



Note:- If you just want to experiment with WinRE without creating a separate partition for WinRE, you can choose any visible drive in Vista.



Step 2: Copying WinRE Files

For the purposes of this post, I am going to assume a WIM-based installation. If you want to install an expanded WinRE, please look at the OPK or the WAIK for appropriate documentation.

You need to copy the following two files to the root of the partition you chose in step 1 above.

1. winre.wim (you can build a winre.wim using the installation media and the WAIK, as described here)
2. boot.sdi (you can find it in the WAIK, under C:\Program Files\Windows WAIK\Tools\PETools\x86\boot)



Step 3: Configuring WinRE

To configure WinRE, you can use the SetAutoFailover.cmd script provided in the WAIK (under: C:\Program Files\Windows WAIK\Recovery). If you copied WinRE files on the D: in step 2 above, and assuming that D: is the first partition on the disk, you would use it as:

SetAutoFailover.cmd /target D: /wim /nohide

Note:- You need to run SetAutoFailover.cmd from an elevated command prompt. To open an elevated command prompt, search for cmd.exe in the search box off Start button, then right click on the cmd icon in search results and choose Run as administrator.



Step 4: Testing WinRE Installation

To test that WinRE is installed correctly on the hard disk - Restart your computer and press F8 very early during boot. If you press it early enough, you should see an Advanced boot menu. The first item on this menu should be "Repair your computer." Choosing this option will take you to WinRE.

http://blogs.msdn.com/winre/
................................................................................
................................................................................
.
..........
and here is the script of setautofailover.cmd:

@echo off

REM
REM Copyright © Microsoft Corporation
REM
REM Description:
REM
REM Sample script to configure the boot configuration data
REM of Windows Vista and WinRE to set auto failover.
REM
REM

:GLOABAL_INIT

setlocal & pushd & set RET=

set SCRIPTNAME=%~n0
set SCRIPTPATH=%~f0
if "%DEBUG%"=="1" (set TRACE=echo) else (set TRACE=REM)

if /i {%1} == {-?} (call :SHOW_USAGE & goto :EOF)
if /i {%1} == {/?} (call :SHOW_USAGE & goto :EOF)

call :MAIN %*

popd & endlocal & set RET=%RET%& set PATH=%PATH%

goto :EOF

REM
REM Main procedure
REM

:MAIN

set BCDEDIT=bcdedit.exe
set DISKPART=diskpart.exe
set DISK=0
set PARTITION=1
set MAINOS={default}

REM
REM Parse command line
REM

call :PARSE %*

REM
REM Check whether bcdedit exists or not
REM

%BCDEDIT% /?>nul

if %errorlevel%==9009 (
call :SHOW_USAGE
goto :EOF
)

if {%TARGET%} == {} (
call :SHOW_USAGE
goto :EOF
)

REM
REM Extract the drive name and root directory from the target
REM
for /f "delims=: tokens=1*" %%I in ("%TARGET%") do (
set DRIVE=%%I:
set WINRE_ROOT_DIR=%%J
)

if {%DRIVE%} == {:} (
call :SHOW_USAGE
goto :EOF
)

if not {%BCDSTORE%} == {} (
set BCDEDIT=%BCDEDIT% -store %BCDSTORE%
)

if {%ISWIM%}=={} (

REM
REM WinRE root directory should be NULL.
REM
if not {%WINRE_ROOT_DIR%}=={} (
echo ERROR: WinRE cannot be installed under a sub directory.
goto :EOF
)

call :CREATE_DIR_BCD_ENTRY

) else (

call :CREATE_WIM_BCD_ENTRY

)

REM
REM Mark this installation as the recovery OS. This recovery OS identifier
REM will be used by other components to enable/disable auto recovery.
REM
%BCDEDIT% -set %WINPE_GUID% custom:46000010 yes

REM
REM Set the recovery sequence
REM

%BCDEDIT% -set %MAINOS% recoverysequence %WINPE_GUID%
%BCDEDIT% -set %MAINOS% recoveryenabled yes

REM
REM Hide partition
REM

if not {%NOHIDE%}=={} (
goto :EOF
)

set TEMP_FILENAME=%SCRIPTNAME%_Temp_DiskPart.txt

echo sel disk %DISK% > %TEMP_FILENAME%
echo sel partition %PARTITION% >> %TEMP_FILENAME%

REM
REM Remove the drive letter for the partition before hiding it.
REM The system will not allow us to remove the drive letter after hiding it.
REM
echo remove >> %TEMP_FILENAME%

if {%GPT%}=={} (
echo set id=27 >> %TEMP_FILENAME%
) else (

REM
REM Set GPT_ATTRIBUTE_PLATFORM_REQUIRED attribute
REM
echo gpt attributes=0x0000000000000001 >> %TEMP_FILENAME%
)

%DISKPART% /s %TEMP_FILENAME%

del %TEMP_FILENAME%

REM
REM Done.
REM

goto :EOF

REM
REM Procedure to parse command line.
REM

:PARSE

if {%1} == {} goto PARSE_DONE

if /i {%1} == {-target} set TARGET=%2&& shift && goto PARSE_NEXT
if /i {%1} == {/target} set TARGET=%2&& shift && goto PARSE_NEXT

if /i {%1} == {-wim} set ISWIM=1&& goto PARSE_NEXT
if /i {%1} == {/wim} set ISWIM=1&& goto PARSE_NEXT

if /i {%1} == {-gpt} set GPT=1&& goto PARSE_NEXT
if /i {%1} == {/gpt} set GPT=1&& goto PARSE_NEXT

if /i {%1} == {-diskpart} set DISKPART=%2&& shift && goto PARSE_NEXT
if /i {%1} == {/diskpart} set DISKPART=%2&& shift && goto PARSE_NEXT

if /i {%1} == {-bcdedit} set BCDEDIT=%2&& goto PARSE_NEXT
if /i {%1} == {/bcdedit} set BCDEDIT=%2&& goto PARSE_NEXT

if /i {%1} == {-bcdstore} set BCDSTORE=%2&& goto PARSE_NEXT
if /i {%1} == {/bcdstore} set BCDSTORE=%2&& goto PARSE_NEXT

if /i {%1} == {-mainos} set MAINOS=%2&& goto PARSE_NEXT
if /i {%1} == {/mainos} set MAINOS=%2&& goto PARSE_NEXT

if /i {%1} == {-partition} set PARTITION=%2&& goto PARSE_NEXT
if /i {%1} == {/partition} set PARTITION=%2&& goto PARSE_NEXT

if /i {%1} == {-disk} set DISK=%2&& goto PARSE_NEXT
if /i {%1} == {/disk} set DISK=%2&& goto PARSE_NEXT

if /i {%1} == {-nohide} set NOHIDE=1&& goto PARSE_NEXT
if /i {%1} == {/nohide} set NOHIDE=1&& goto PARSE_NEXT

:PARSE_NEXT

shift
goto PARSE

:PARSE_DONE

goto :EOF

REM
REM Procedure to create a BCD entry for WinRE installed as a flat directory
REM

:CREATE_DIR_BCD_ENTRY

REM
REM Customize WinRE
REM

echo [LaunchApp] > %TARGET%\windows\system32\winpeshl.ini
echo AppPath=x:%WINRE_ROOT_DIR%\sources\recovery\recenv.exe >> %TARGET%\windows\system32\winpeshl.ini

REM
REM Set BCD
REM {572bcd55-ffa7-11d9-aae0-0007e994107d}, GUID for the WinPE boot entry
REM

set WINPE_GUID={572bcd55-ffa7-11d9-aae0-0007e994107d}

REM
REM Create WinRE boot entry
REM

%BCDEDIT% -create %WINPE_GUID% -d "Windows Recovery Environment" -application OSLOADER
%BCDEDIT% -set %WINPE_GUID% device partition=%DRIVE%
%BCDEDIT% -set %WINPE_GUID% path %WINRE_ROOT_DIR%\windows\system32\boot\winload.exe
%BCDEDIT% -set %WINPE_GUID% osdevice partition=%DRIVE%
%BCDEDIT% -set %WINPE_GUID% systemroot %WINRE_ROOT_DIR%\windows
%BCDEDIT% -set %WINPE_GUID% detecthal yes
%BCDEDIT% -set %WINPE_GUID% nx optin
%BCDEDIT% -set %WINPE_GUID% winpe yes

goto :EOF

REM
REM Procedure to create a BCD entry for WinRE installed as a WIM file
REM

:CREATE_WIM_BCD_ENTRY

REM
REM {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
REM
set RAMDISK_OPTIONS={ad6c7bc8-fa0f-11da-8ddf-0013200354d8}

REM
REM {572bcd56-ffa7-11d9-aae0-0007e994107d}, GUID for the WinPE boot entry
REM

set WINPE_GUID={572bcd56-ffa7-11d9-aae0-0007e994107d}

REM
REM Create Ramdisk device options for the boot.sdi file
REM
%BCDEDIT% -create %RAMDISK_OPTIONS% -d "Ramdisk Device Options" -device
%BCDEDIT% -set %RAMDISK_OPTIONS% ramdisksdidevice partition=%DRIVE%
%BCDEDIT% -set %RAMDISK_OPTIONS% ramdisksdipath \boot.sdi

REM
REM Create WinRE boot entry
REM

%BCDEDIT% -create %WINPE_GUID% -d "Windows Recovery Environment" -application OSLOADER
%BCDEDIT% -set %WINPE_GUID% device ramdisk=[%DRIVE%]\winre.wim,%RAMDISK_OPTIONS%
%BCDEDIT% -set %WINPE_GUID% path \windows\system32\boot\winload.exe
%BCDEDIT% -set %WINPE_GUID% osdevice ramdisk=[%DRIVE%]\winre.wim,%RAMDISK_OPTIONS%
%BCDEDIT% -set %WINPE_GUID% systemroot \windows
%BCDEDIT% -set %WINPE_GUID% detecthal yes
%BCDEDIT% -set %WINPE_GUID% nx optin
%BCDEDIT% -set %WINPE_GUID% winpe yes

goto :EOF


REM
REM Procedure to show usage information
REM

:SHOW_USAGE

echo.
echo This script configure auto failover settings for the specified WinRE.
echo.
echo Usage:
echo %SCRIPTNAME% /target (WinRE path) [Options]
echo.
echo Options:
echo.
echo /target (drive where WinRE is installed) [required]
echo The drive where WinRE is installed w/o the trailing backslash,
echo e.g., C:
echo.
echo /wim [optional]
echo Specifies that WinRE.wim file is installed on target drive. The script
echo assumes that the name of the WIM file is WinRE.wim and the
echo name of the SDI file is boot.sdi
echo.
echo /partition (partition number of the WinRE drive) [optional]
echo Partition number for the above WinRE drive. By default
echo the script assumes partition number 1.
echo.
echo /disk (disk number of the WinRE drive) [optional]
echo Disk number of the above WinRE drive. By default the script assumes
echo disk number 0.
echo.
echo /gpt [optional]
echo The target disk is a GPT disk. By default the script assumes
echo an MBR disk.
echo.
echo /mainos (guid of the main OS) [optional]
echo Use the specified GUID for the main OS. By default the script
echo assumes the current OS. Note -- always specify this option when
echo running from WinPE. To configure the default OS in BCD specify
echo {default}.
echo.
echo /nohide [optional]
echo Don't hide the winre partition
echo.
echo /bcdedit (Full path to bcdedit.exe) [optional]
echo Use the specified bcdedit.exe. By default the script assumes
echo that bcdedit.exe is in the PATH environment variable.
echo.
echo /bcdstore (Full path to BCD store) [optional]
echo Use the specified BCD store. By default the script assumes
echo the system BCD store.
echo.
echo /diskpart (Full path to diskpart.exe) [optional]
echo Use the specified diskpart.exe. By default the script assumes
echo that diskpart.exe is in the PATH environment variable.
echo.

goto :EOF

................................................................................
.........................................................................
some or most of the above is way over my head but I am intrested about Boot partition type what does all those figures mean???

the complicated part which I do not undrstand(the partition should be a hidden recovery partition allocated before the

OS partition. It should be assigned type 0x27 on MBR disks and type {DE94BBA4-06D1-4D40-A16A-BFD50179D6AC} on GPT disks. The

partition should be at least large enough to hold WinRE WIM, 1.5GB should be plenty for the base WinRE.)

does this mean that if you got big enough partition to put the mirror master image.wim of C: drive and you use F8 key you can reach the recovery Boot partition and remaster the C: to manufactured setting??? using imagex.exe command of some sort.???


Note:- If you just want to experiment with WinRE without creating a separate partition for WinRE, you can choose any visible

drive

You need to copy the following two files to the root of the partition you chose in step 1 above.

1. winre.wim (you can build a winre.wim using the installation media and the WAIK, as described here)
2. boot.sdi (you can find it in the WAIK, under C:\Program Files\Windows WAIK\Tools\PETools\x86\boot)

To configure WinRE, you can use the SetAutoFailover.cmd script provided in the WAIK (under: C:\Program Files\Windows

WAIK\Recovery). If you copied WinRE files on the D: in step 2 above, and assuming that D: is the first partition on the disk,

you would use it as:

SetAutoFailover.cmd /target D: /wim /nohide

Note:- You need to run SetAutoFailover.cmd from an elevated command prompt. To open an elevated command prompt, search for

cmd.exe in the search box off Start button, then right click on the cmd icon in search results and choose Run as

administrator.

Restart your computer and press F8 very early during boot. If

you press it early enough, you should see an Advanced boot menu. The first item on this menu should be "Repair your

computer." Choosing this option will take you to WinRE.
................................................................................
...............................
not having Vista Cd I can not experiment and find out
may be a knowledgeable person can explain the boot partition figures regarding type
................................................................................
................................
useful information:
You can run DriveImage XML from a WinPE boot CD-ROM.

http://www.runtime.org/dixml.htm


DriveImage
DriveImage XML V1.18

Price: Free

System Requirements:
Pentium Processor
256 MB RAM
Windows XP or 2003
................................................................................
.......................................................
useful info: Not for WinPe2(VistaPE) Tip
Installing drivers on a PE CD is pretty straight. There's no "universal" driver, though.

You can create an ISO of the CD, then run a program like ISO Buster to open it.
Then, just copy the Windows XP drivers that the manufacturer provides into the drivers and inf folders, save the new ISO, and burn yourself a shiny new CD.
The whole process takes about 10-15 minutes, once you've become a little familiar with it.
................................................................................
...................................................

This post has been edited by Ben_Mott: Jan 24 2007, 04:45 PM

[Ed_P]

I have a feeling a lot of older software are going to have problem with VISTA

This is a surprise how??? Buy new OS > buy new hardware, buy new sw, buy new system. It's how the pc cycle works and the final nail, should you not want to get caught up in the cycle, the vendor of the OS will stop supporting its nolder versions.

[Ben_Mott]

useful information regarding Vista :

Windows Vista and BitLocker

windows Vista Enterprise and Ultimate edition install Bitlocker automatically, but do require

that hard disk is partitioned .
other version of Vista do not support Bitlocker at all.

when it comes to security. Encrypting File System (EFS) never really caught on due to its

shortcomings. Among other things, EFS is a file encryption method which is useful under certain

circumstances, but it's not an ideal solution when it comes to mobile devices, such as laptops.

With the new BitLocker Drive Encryption (BitLocker) feature in Vista, we finally have a drive

encryption mechanism that offers data security to laptop users running Microsoft's operating

system.



Although there are numerous third-party drive encryption tools available today
Free alternatives:

http://www.ce-infosys.com
http://www.abylonsoft.de
http://www.gnupg.org
...........................................
and businesses

and government agencies around the world have been utilizing them for years, BitLocker is a

built-in feature of Windows Vista, and it's free for Enterprise and ultimate Vista and not available for other versions of vista.

BitLocker Drive Encryption in Windows Vista

http://technet2.microsoft.com/WindowsVista...3.mspx?mfr=true


http://technet.microsoft.com/en-us/windows...906017.aspx#EGB


http://certcities.com/editorial/columns/st...ditorialsID=213

TECH NET BitLocker Drive Encryption
BitLocker™ Drive Encryption addresses the very real threats of data theft or exposure from lost,

stolen or inappropriately decommissioned PC hardware with a tightly integrated solution in the

Windows Operating System.

BitLocker prevents a thief who boots another operating system or runs a software hacking tool

from breaking Windows Vista file and system protections or performing offline viewing of the

files stored on the protected drive.

This data protection feature is available in Windows Vista Enterprise and Ultimate.

http://technet.microsoft.com/en-us/windows...a/aa905065.aspx
http://technet.microsoft.com/en-us/windows...a/aa906018.aspx
http://news.bbc.co.uk/1/hi/technology/4229550.stm
http://technet.microsoft.com/en-us/windows...a/aa906017.aspx
................................................................................
......
For BitLocker to work, you must have at least two partitions on your hard disk. The first partition is the system volume and labeled S in this document. This volume contains the boot information in an unencrypted space. The second partition is the operating system volume and labeled C in This volume is encrypted and contains the operating system and user data.

To partition a disk with no operating system for BitLocker

1.

Start the computer from the Windows Vista product DVD.
2.

In the initial Install Windows screen, choose your Installation language, Time and currency

format, and Keyboard layout, and then click Next.
3.

In the next Install Windows screen, click System Recovery Options, located in the lower left of

the screen.
4.

In the System Recovery Options dialog box, choose your keyboard layout, and then click Next.
5.

In the next System Recovery Options dialog box, make sure no operating system is selected. To do

this, click in the empty area of the Operating System list, below any listed entries. Then click

Next.
6.

In the next System Recovery Options dialog box, click Command Prompt.
7.

Use Diskpart to create the partition for the operating system volume. At the command prompt,

type diskpart, and then press ENTER.
8.

Type select disk 0.
9.

Type clean to erase the existing partition table.
10.

Type create partition primary size=1500 to set the partition you are creating as a primary

partition.
11.

Type assign letter=S to give this partition the S designator.
12.

Type active to set the new partition as the active partition.
13.

Type create partition primary to create another primary partition. You will install Windows on

this larger partition.
14.

Type assign letter=C to give this partition the C designator.
15.

Type list volume to see a display of all the volumes on this disk. You will see a listing of

each volume, volume numbers, letters, labels, file systems, types, sizes, status, and

information. Check that you have two volumes and that you know the label used for each volume.
16.

Type exit to leave the diskpart application.
17.

Type format c: /y /q /fs:NTFS to properly format the C volume.
18.

Type format s: /y /q /fs:NTFS to properly format the S volume.
19.

Type exit to leave the command prompt.
20.

In the System Recovery Options window, use the close window icon in the upper right (or press

ALT+F4) to close the window to return to the main installation screen. (Do not click Shut Down

or Restart.)
21.

Click Install now and proceed with the Windows Vista installation process. Install Windows Vista

on the larger volume, C: (the operating system volume).

..........................................
Free alternatives:

http://www.ce-infosys.com
http://www.abylonsoft.de
http://www.gnupg.org
...........................................
regards Ben


This post has been edited by Ben_Mott: Jan 19 2007, 06:34 PM

[Ben_Mott]

has any body used their win PE2 to make an image with IMAGEX.exe ??
and then deploying it Back ????


has any body used imagex.exe to make an image of C:drive(XP say NTFS) to C: drive and then
epxnding it back into the C: drive again ????
in WAIK instruction for prepairing an image and deploying it
roughly it says :
put imagex.exe on the roout of your WIN VISTA PE (ie put it in ISO folder before making the ISO and subsequently the CD)
-->insert PE CD into master computer(the one you want to make the image of)and start the computer.

-->capture an imagage of master installation by using image X at command prompt type
d:\imagex.exe /compress fast /capture c:\myimage.wim

and to expand it back in a later date
boot with win PE again type:
D:\imagex.exe /apply c:\myimage.wim C:
what it says really is to copy it to an external drive then prepair and partion the HDD
and copy the image back to C: drive which would be empty and only has the image on it.
I was wondering if old windows is left in place what happens does it over wite it
or pops up an error message!!!????

before I do that(TO MY WINDOWS xp) I need to make a ghost image of my hdd TO AN EXTERNAL hdd FOR SAFE KEEPING.
WHICH IS OUT OF ACTION AT MOMENT
so I thought has any body else tried this and has it worked ???
because if it works it has advantage over ghost that you can copy the image to the same
partition on the same HDD .

I thought I ask before getting too curious and Knakering my pc Without a backup.

Regards Ben

[Ben_Mott]

I managed to do a Little experiment with imagex.exe to see if it works with windows XP
because as you know it is the latest MIcrosoft tool for windows Vista.
one of my computers P4 1.3 with 512MB RAM and 80GB Harddisk(PATA IDE) Windows XP SP2
so I checked in windows explorer and found out that I had 3.3GB used space and the rest of
HDD was empty and it was NTFS .
so I booted with PE with imagex.exe put on root of cd (put it on ISO folder before making ISO
and burning the CD)
I typed D: pressed enter
and then typed:
imagex /boot /capture C: C:\myimage.wim "windows XP "
and pressed enter and it starte making the image as you can see with /boot flag i was hoping
for a bootable image.
it said first
files and folders excluded from capture by default:
\windows\GSG
\recycler
\system volume information
\page file.sys
\hiberfiles.sys
\$ntfs.log
progress:xx% 12.15 remaining
....
.....
progess: 100%
successfully imaged C:

so I went into windows XP and cheked the size of the image myimage.wim (880,360KB)ie 880MB
a big reduction in size from 3.3MBto 0.880MB
so i thought it probably has only copied windows not my apps and data.
so I made a new directory on C: drive called mount
and mounted the image to that empty mount directory.opened a comand window(CMD)
and then typed
cd \
cd c:\Program Files\Windows AIK\Tools\x86

imagex /mountrw c:\myimage.wim 1 c:\mount
do not forget the 1

and went to windows explorer and chcked the size of that mount directory first it was 1.8MB
which ment that it nearly more than doubled in size.
when I looked in the c:\mount directory all my file and apps where there
at this stage I should have checked for files
NTLDR
NTDETECT.COM
BOOT.INI
and could have easily copied and pasted them to the files inside the image .

as I still did not have a back up of my drive I could not take the risk of installing it on that big 80GB HDD
so here where I went wrong I did a little calculation 1.82GB + 0.86 GB =2.68GB so I had an old 3 GB HDD so
I thought wrongly that there might be enough room on there .so I copied the image to that and unpluged the 80BG HDD and

pluged it into the 3GB HDD
booted with VistaPE2 and again D:
and typed:
imagex /apply C:\myimage.wim 1 c:
do not forget 1
progress:27% 11.20mins remaining
successfully applied image.
so I thought great restarted computer and it could not find boot HDD so I booted with XP boot floppy
http://www.postbox.wanadoo.co.uk/xpboot.exe
and choose first partition and it booted into windows
but it got stuck as I realized windows was configuring and adding files to C: drive and obviously 3.3BG do not fit in 3Gb
so I left it and replaced my 80 Gb hdd and booted back into windows I was thinking of trying it with that 80Bg HDD
but since I had put AWIK and DOT net fram work 2 and XML bla Bla Xp had become for some unknown reason more stable
so I thought better leave it and go to sleep instead.

.............................
I think the most important thing when making VistaPE2 is ti put Imagex.exe in a folder
called tools and copy that to ISO folder so when you make a VistaPE Bootable cd
it will be on the root of the CD.
the good thing about that is because imagex.exe make file base images the image of the C: drive
can be copied to the same partition. for example: boot with VistaPE in to computer which you

want to image.
then on the command line type this command
D:\tools\imagex.exe /capture C: C:\myimage.wim "myVistaImage"
and press enter this makes an image of the C: drive on the C: directory it self.
then you can hookup an external Hard drive to the USB port and copy and past the image into

external HDD for safe keeping.
to deploy the image boot with vistaPE again

copy F:\myimage.wim C:

D:\tools\imagex.exe /apply C: C:\myimage.wim 1 C:


do not try it with Xp it works but the image is not bootable .


regards BEN


This post has been edited by Ben_Mott: Mar 3 2007, 04:32 AM