nVidia RAID configuration and Windows 7

forums.techarena.in/vista-setup-install/1128278.htm

The infamous Grub error! When installing which distro? ubuntu or  another? you inadvertently allowed Grub to be installed onto the array instead of seeing it installed to the new sata drive you added in.
When installing Grub where any Windows installations are present on one of the drives with Linux going onto a separate hard drive you use the custom option when reaching the partitioning section to designate the root as the "/" mount point and simply click on the Linux drive when asked where Grub will be installed. That will generally leave the Windows mbr intact.
The bootrec /scanos command at the prompt while booting from the Vista dvd was the correct method to start with. Once answering Y for yes and seeing the installation shown successfully added message you then use the Fixboot and Fixmbr commands to correct the Vista mbr seeing the Grub entries removed. You may have to do this a few times to actually see Windows booting normally again.

booted into the Windows Recovery Environment and did the following:

X:\Sources>

bootrec /rebuildbcd

  Scanning all disks for Windows installations.
  Please wait, since this may take a while...
 Successfully scanned Windows installations.
 Total identified Windows installations: 1
  [1] C:\Windows
  Add installation to boot list? Yes(Y)/No(N)/All(A):Y
  *Element not found.*
So what's 'Element not found.'?
The element not found is when the rebuild tool is unable to detect the installation presently on the system. That can be for different reasons like the order you type the commands in. 

Try typing the bootrec /scanos entry before using the bootrec /rebuildbcd. 

Once successfully added you simply type the bootrec /fixmbr and /fixboot commands.
Another option if the BCD store itself isn't able to be rebuilt is to delete the present one. The second section seen on the MS page for this is at 'Error message when you start Windows Vista: "The Windows Boot Configuration Data file is missing required information"'
http://support.microsoft.com/kb/927391
The easier commands to use at the command prompt are:
bcdedit /export C:\BCD_Backup (C being used here for the single OS/system drive)
c:
cd boot
attrib bcd -s -h -r
ren c:\boot\bcd bcd.old
bootrec /RebuildBcd

-------------

Are you loading the RAID controller driver in the recovery environment?

--------------

There's a freeware BCD editing tool recommended by an article titled "'Tech Solution: Vista Boot Error 0×000000f (C:\boot\BCD)'
(http://alextaldren.wordpress.com/2008/12/27/tech-solution-vista-boot-error-0x000000f-cbootbcd/)"
that may be just what you need there along with the repair tools. 'Tech Solution: Vista Boot Error 0×000000f (C:\boot\BCD) « The AT Wire'
alextaldren.wordpress.com/200...000f-cbootbcd/)
Shortly after Vista's initial release I ran across the free tool mentioned there available at 'Download EasyBCD 2.- NeoSmart Technologies'

neosmart.net/
The general documentation for use is seen at 'List Pages - Tree View -NeoSmart Technologies Wiki'
neosmart.net/wiki/pages/listp...ageInHierarchy
For the problem you are seeing there however there's a page seen with other commands to enter for seeing the boot loader repaired in the last section called "Step Four: Nuclear Holocaust" seen at 'Recovering the Vista Bootloader from the DVD - NeoSmart Technologies Wiki'
neosmart.net/wiki/display/EBC...r+from+the+DVD

The NeoSmart Forums' 

neosmart.net/forums/showthread.php?t=3302

---------------

It looks that way since that would clean everything up. Most of the commands are assuming that Vista is on a single drive not an array. That would be something to consider as well. When correcting a ubuntu glitch some time back that trashed the Vista mbr the quick the use of the bootrec commands at the prompt saw the Grub error taken care of. But that was with Vista on one single drive.

--------------
Did you attempt to reinstall Vista back onto the array or the new sata drive you added in? It sounds like you left the boot drive for the array left default in the bios setup even if you installed over ubuntu on the new sata drive you added in. The fast method is to look at which drive is set as default there.
The first thing to look at when setting up a dual boot of simply two versions of Windows if not two OSs is just which drive is set as default especially when adding a new drive onto the system. That includes  external usb hard drives and usb flash drives at times since the new drive will tend to offset the order.
Now you have to find out which drive or paritition/drive saw the fresh install go to and see that set as default since the original host drive still sees the altered mbr info on that.

----------------------

One way I saw a working dual boot with ubuntu was to first unplug the Vista drive after running into the same Grub error problem. Once ubuntu went on an extra drive at the time and the Vista was plugged back later I first saw the root partition made the "/" mount point seeing Grub installed to that drive.
Later I simply used a free tool called EasyBCD to see the Linux entry
added in with one item definitely checked off namely the "Grub isn't installed into bootsector" box.
(http://www.freeimagehosting.net/imag...1f29de8af9.jpg) 

You can still see ubuntu work. But you have to play it smart in order to prevent the Vista mbr from being trashed while doing it.

--------------------- 

Got it fixed! :D
What I ended up doing was using KillDisk to completely erase the SATA drive, then I unplugged the SATA drive so as not to 'confuse' the windows recovery environment. Then I ran startup recovery, fixmbr, and fixboot, and then I could boot into Vista successfully. After this, I plugged the SATA drive back in and formatted it and everything's back to normal--and a little faster too, since I have a clean install of Vista.
I think I've had enough of trying to dual boot--for awhile at least, especially since I use this computer for school!
Thanks, NightHawk, for your prompt replies and all. I'll have to get someone who can physically look over my shoulder and help me out when I decide to pursue Linux again! But not for a little while. Hope this thread helps anybody else out having similar issues. 

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

How to safely update the nForce SataRaid drivers of a running Vista x86/x64
Warning: The update of the nForce IDE (S-ATA/RAID) drivers is dangerous, because this is a severe modification of the system with a lot of changes within the registry. There is always the risk, that the reboot into Vista will fail after the update. Exactly this is the main reason why I suggest to load the newest/best available nForce IDE drivers during Vista Setup.
Advice: Before you are going to update any mass storage controller driver, you should do a backup of your running Vista partition by using a tool like Acronis True Image.
If you are going to update the nForce SataRaid drivers and just follow the advices of Vista's driver update pop-up windows, you probably will get a BSOD.
Warning: DON'T REBOOT UNLESS YOU HAVE UPDATED ALL NVIDIA SATA AND RAID DEVICE DRIVERS (even the usually hidden ones)!
Here is the exact procedure (detected by TheMaxx32000) for an update of the nForce S-ATA and RAID drivers:

• Open the "Device Manager", select "View" and check the "Show hidden devices" option.
• Search for devices named "NVIDIA nForce Serial ATA Controller" (within the "IDE ATA/ATAPI Controllers" or "Storage Controllers" section) and update ALL listed devices with the said name by loading the SATA_IDE driver folder of your prepared new nForce driver package. DO NOT REBOOT!
• Open the "Storage Controllers" section and update ALL listed the "NVIDIA RAID Controller" devices and ALL listed devices named "NVIDIA RAID DEVICE" by loading the SATARAID driver folder of your prepared new nForce driver package. DO NOT REBOOT!
• Check the driver version of all previous mentioned devices to verify, that all of them have properly updated drivers.
• NOW YOU CAN REBOOT.
• Have fun with the updated nForce S-ATA and RAID drivers.

Notice:
1. If you are trying to load any modded or not yet WHQL certified driver, you have to force the driver update by choosing the "Browse my computer ...." - "Let me pick ...." - "Have Disk" options. Otherwise Vista will give a message, that it has already installed the best driver software.
2. If you want to update just the RAID driver, you have to do all steps shown above except the second one.[/list]

cleaning and tweaking tools

http://filepig.org/software/cleaning_and_tweaking/

Portable Windows XP Live USB

Source
Portable Windows XP Live USB Edition 2008 V2.2



Welche Art: System Programm
Sprache:
Deutsch, English, ich wisst schon eigentlich alle Sprachen^^
Vollversion: [x] Ja [ ] nein
Passwort: [ ] Ja [x] nein
Eure Persöhnliche Note: Also ich persönlich finde dieses Programm sehr gut, weil es auf einen kleinen 256Mb Stick passt un man im Notfall sein System damit retten kann.
Euer Eindruck: Das könnt ihr mir ja den sagen^^
Installation :
1) Benenne den Stick nach HPUSBFW.exe um und Formatiere in mit dem Fat Dateisystem System. 
2) Kopiere all Daten aus dem Archiv auf den Usb Stick
Start :
1) Starte den Computer neu.
2)Gehe im Bios auf Quick-boot menu ( kann auch anders heißen ) und wähle Boot from USB ( auch dies kann anders heißen also ein bisschen probieren^^
Größe:
Gepackt: ca. 60 MB 
Entpackt: ca. 80 MB
Download:

rapidshare.com/files/212374059/Portable_Windows_XP_Live_USB_Edition_2008_V2.2.rar

 

bcdedit.exe and bootrec.exe

BCDEDIT - How to Use
forums.techarena.in/vista-setup-install/1128278.htm
 X:\Sources>bootrec /rebuildbcd
> Scanning all disks for Windows installations.
>
> Please wait, since this may take a while...
>
> Successfully scanned Windows installations.
> Total identified Windows installations: 1
> [1] C:\Windows
> Add installation to boot list? Yes(Y)/No(N)/All(A):Y
> *Element not found.*
> So what's 'Element not found.'?
The element not found is when the rebuild tool is unable to detect the installation presently on the system. That can be for different reasons like the order you type the commands in. Try typing the bootrec /scanos entry before using the bootrec /rebuildbcd. Once successfully added you simply type the bootrec /fixmbr and /fixboot commands.

Another option if the BCD store itself isn't able to be rebuilt is to delete the present one. The second section seen on the MS page for this is at 'Error message when you start Windows Vista: "The Windows Boot Configuration Data file is missing required information"'
(http://support.microsoft.com/kb/927391)
The easier commands to use at the command prompt are:
X:\>
(c:) ????

bcdedit /export C:\BCD_Backup (C being used here for the single OS/system drive)
c:
cd boot
attrib bcd -s -h -r
ren c:\boot\bcd bcd.old
bootrec /RebuildBcd


bootrec /fixmbr
bootrec /fixboot
-------------------------------------------------- 

Use the WinPe setting in EasyBCD.
EasyBCD 2.2 - The NeoSmart Forums

Attached Thumbnails

 

neosmart.net/wiki/display/EBC...r+from+the+DVD

Let's start by telling the recovery console to fix our MBR and bootsectors:

Replace x: in the commands below with the letter to your CD drive as detected by the Windows Recovery environment

bootrec.exe /fixmbr
x:\boot\bootsect.exe /nt60 all /force

Then ask it (nicely!) to try and rebuild your BCD data from scratch:

del C:\boot\bcd
bootrec.exe /rebuildbcd

If you're lucky, this'll work and you'll see a message telling you everything went OK.

Reboot your PC by typing in this command or by closing all the dialogs:

shutdown -r -t 0

Don't forget to remove your Windows Vista DVD or Recovery DVD from the drive!

Step Four: Nuclear Holocaust

Windows Vista doesn't have its share of haters for no reason: when the going gets tough, the tough gets going.

So Windows Vista can't even fix itself - god, that's what we love about EasyBCD! If you were in Windows Vista right now, you could have used EasyBCD's "Reset BCD Data" feature to have EasyBCD actively search for any and all discrepancies in your bootloader, zero out your old BCD data, and re-create it all from scratch. But you're not and it's no use lamenting what you could be doing with our super-cool app if you can't even use it in the first place now, is it? 

Go ahead and select "Command Prompt" yet again from that list. Roll up your sleeves, and prepare to be tortured.

The first order of business is to make sure the MBR and bootsector contain the right references to the Vista bootloader:

Replace x: in the commands below with the letter to your CD drive as detected by the Windows Recovery environment

bootrec.exe /fixmbr
x:\boot\bootsect.exe /nt60 all /force

Now we get rid of the old BCD registry, and create a new one instead.
Note: We're assuming that the boot drive is drive C: below. If your computer is configured differently, be sure to use the appropriate drive letter here instead.

del C:\boot\bcd
bcdedit /createstore c:\boot\bcd.temp
bcdedit.exe /store c:\boot\bcd.temp /create {bootmgr} /d "Windows Boot Manager"
bcdedit.exe /import c:\boot\bcd.temp
bcdedit.exe /set {bootmgr} device partition=C:
bcdedit.exe /timeout 10
del c:\boot\bcd.temp

Now we have a clean, working Vista bootloader. But we need to add a Vista entry to it:

bcdedit.exe /create /d "Windows Vista" /application osloader

bcdedit.exe should return a message with a GUID for the newly-created entry, something like this:
The entry {c0dfc4fa-cb21-11dc-81bf-005056c00008} was successfully created.

You'll need to use the value that bcdedit.exe returned for you below, along with the drive letter for the drive that Windows Vista is installed to:

bcdedit.exe /set {c0dfc4fa-cb21-11dc-81bf-005056c00008} device partition=C:
bcdedit.exe /set {c0dfc4fa-cb21-11dc-81bf-005056c00008} osdevice partition=C:
bcdedit.exe /set {c0dfc4fa-cb21-11dc-81bf-005056c00008} path \Windows\system32\winload.exe
bcdedit.exe /set {c0dfc4fa-cb21-11dc-81bf-005056c00008} systemroot \Windows

And, last of all, tell the Vista bootloader to boot the new entry by default:

bcdedit.exe /displayorder {c0dfc4fa-cb21-11dc-81bf-005056c00008}
bcdedit.exe /default {c0dfc4fa-cb21-11dc-81bf-005056c00008}

Now the Vista bootloader has been nuked and rebuilt from scratch. If you got this to work, feel free to consider yourself one of the finest graduates of the NeoSmart Technologies Institute of BCD Learning.

At this point, you have a clean, untouched, and (hopefully) fully-working bootloader with one entry for Windows Vista. Go ahead and reboot your PC, get into Windows Vista, and use EasyBCD to further tweak the bootloader to your heart's content. We advise backing up the BCD registry immediately with EasyBCD before making any changes.

http://www.sevenforums.com/installation-setup/67751-boot-wim.html
creating a 2 OS thumb drive

"The boot selection failed

 because a required device is inaccessible" Windows 7/Vista error
Source

Windows failed to start. A Recent hardware or software change might be the cause. To fix the problem: 

1. Insert your windows installation disc and restart your computer.

2. Choose your langugae settings, and then click next

3. Click "repair your computer."

Status: 0xc000000e

Info: The boot selection failed because a required device is inaccessible.

Then I tried to run the Windows 7 installation disk, I go to the cmd prompt and run the

Quote:

DISKPART diskpart list disk select Disk X (X=disk where I installed all the OS, should be Disk 0) list partition select Partition X (X=partition containing OSX) Virtual Disk Service error: The pack is not online

and then i run the Bootrec /ScanOS, it came with 0 identified Windows Installations, this is why I come into the cmd prompt as I could not select the installed OS 

I've tried that from bootable cd to repair the install but the partition of windows7 is not recognized still.

Solution

I had the same problem - number 0xc000000e, after changing hdd physical order.

Download EasyBCD.

(It is required other Live Windows or brought disk to someone with Windows OR

run probably bcdedit command from recovery dvd_win7_disk)

Then look at your item which boot Win! My item had a record with unknown device or similar Deleted partition drive. I suppose correctly there must be something like C:\. 

So instead of delete that item I prefer added next and selected right drive for it. 

It can be one of C:\,D:\,E:\,... with your Windows directory (where you have installed it). More interesting is that it didnt have to be equal letter as it appears after boot in different computer, different hdd order, ...

After reset - booting without problems

Source

You can do this easier by using Easy BCD. I had this exact same problem but I no longer have a copy of Windows 7 and Microsoft stopped the free download.

Download Easy BCD here: 

http://neosmart.net/dl.php?id=1

Once you have it installed start it up and click view settings. You will most likely see that it says 'Partition Deleted' or something to that effect under the Windows 7 entry beside 'Drive:'.

Click on 'Change Settings'. Under 'Entry-Based Settings', choose Windows 7 and change 'Drive' to the drive letter of your Windows 7 partition and then Save Settings.

When you reboot you should be able to boot into Windows 7 again.

Source

Its a well known fact that if one or more required boot files are found to be missing or corrupt, a Windows system might fail to boot. Such problems can be resolved by using Windows installation disc. But still if it is not resolved, the the only solution remains is to install the operating system, which causes data loss.

Now, if no valid data backup is available, you need to use windows data recovery utilities.

Reasons:

1. 
   
   
   One of more Windows boot items, like MBR, BCD store etc., are missing or corrupt
2. 
   
   
   Incorrect BIOS settings for the boot device, usually hard drive. This might occur if you have recently performed some changes in system BIOS settings. 

Solution

If after changing the BIOS settings, Windows is unable to boot, then configure BIOS to default fail-proof settings and after that set hard drive as the primary boot device. And if it is not OK then we should repair Windows startup files using windows recovery environment as follows:

• 
  
  
  Insert Windows Vista or Windows 7 installation disc into the computer and boot the system
• 
  
  
  Press any key for starting the repair process when prompted for
• 
  
  
  You need to then select the time, language and currency and the desired input method
• 
  
  
  Click 'Next' and select 'Repair your computer' option
• 
  
  
  The 'System Recovery Options' dialog box appears, at which you need to select the Windows installation you need to repair. Click 'Next'.
• 
  
  
  You can then select the 'Startup Repair' option. Instead, you can also run 'Bootrec.exe' through 'Command Prompt'

If the above steps fail to boot Windows successfully, then it is suggested to reinstall the operating system and use your recent data backup to restore the lost data. If no data backup is available, use windows data recovery software for extracting the data. These software are embedded with high-end scanning algorithms. The software also enable you to perform comprehensive Partition Recovery in all cases of logical crashes.

Source

Cause

The above error might occur due to any of the below reasons:

• 
  
  
  Incorrect BIOS settings for the boot device, usually hard drive. This might occur if you have recently performed some changes in system BIOS settings.
• 
  
  
  One of more Windows boot items, like MBR, BCD store etc., are missing or corrupt

Solution

If Windows is unable to boot due to changed BIOS settings, you should configure BIOS to default fail-proof settings and set hard drive as the primary boot device. If this is not the case, you should repair Windows startup files using Windows Recovery Environment as follows:

• 
  
  
  Insert Windows Vista or Windows 7 installation disc into the computer and boot the system
• 
  
  
  Press any key for starting the repair process when prompted for
• 
  
  
  You need to then select the time, language and currency and the desired input method
• 
  
  
  Click 'Next' and select 'Repair your computer' option
• 
  
  
  The 'System Recovery Options' dialog box appears, at which you need to select the Windows installation you need to repair. Click 'Next'.
• 
  
  
  You can then select the 'Startup Repair' option. Instead, you can also run 'Bootrec.exe' through 'Command Prompt'

If the above measures don't boot Windows successfully, you should reinstall the operating system. You should then use your recent data backup to restore the lost data. If no clean data backup is available, use data recovery software for efficiently extracting it. data recoveryutilities are powerful third-party tools embedded with high-end scanning algorithms. The software also enable you to perform comprehensive partition recovery in all cases of logical crashes.

Stellar Phoenix Windows Data Recovery is an advanced and fully-featured recovery utility designed for Windows 7 RC1, Vista, XP, 2003 and 2000. It is a non-destructive data recovery software providing advanced options including Drive Status, Disk Cloning, Disk Imaging and RAW File Recovery. The software supports FAT32, VFAT, NTFS and NTFS5 file systems.

"Repair your computer" F8 boot option not working

Status: 0xc000000e
Info: The boot selection failed because a required device is inaccessible.

 Start an elevated command prompt and type bcdedit /enum all

Attach the ouput of this command to your next post. Also, confirm that you have the folder C:\Recovery on your disk. You will need to enable the display of both hidden and protected operating system files in order to see it.
alextaldren.wordpress.com/2008/12/27/tech-solution-vista-boot-error-0x000000f-cbootbcd/

Raid Recovery Software

Source
Reconstruct all types of corrupted RAID arrays

Recover corrupted RAID arrays in a fully automatic mode. Raid Recovery is the first tool to automatically detect the type of the original RAID array while still allowing for fully manual operation. Raid Recovery is no doubt a highly valuable tool for users of all types of RAID arrays, whether hardware, native, or software. The drag-and-drop user interface allows specifying parts of the RAID array by simply dragging and dropping icons representing the disks.

Reconstruct all types of arrays just as easily as a single hard disk. Raid Recovery recognizes all imaginable configurations of various types of arrays, including RAID 0, 1, JBOD, RAID 5, and 0+1, no matter whether they are connected to a dedicated RAID controller or a RAID-enabled motherboard from NVidia, Intel, or VIA. Microsoft software raids (also called Dynamic Disks) are also supported, including JBOD (span), RAID 0, 1, and 5 configurations. Version 1.5 and higer works with Adaptec RAID Controllers and DDF compatible devices

Detecting the right type of an array is vital for correct recovery. Raid Recovery supports both manual and fully automatic detection of essential parameters such as type of array, type of RAID controller, stripe size, and disk order.

Assemble RAID configurations manually

Assemble RAID configurations manually via a simple drag-and-drop operation. Raid Recovery re-constructs an array from the available hard disks being simply dragged and dropped, and detects the right type and size or the array as well as the order of the disks automatically. Anyone can recover broken RAID arrays with Raid Recovery!

Raid Recovery gives top priority to your data, allowing you to recover and back up all files from the corrupted array before attempting to fix it. You can store the files on another hard disk or partition, use a recordable CD or DVD, or even upload the files over FTP. Raid Recovery uses advanced search algorithms that allow recovering important files such as documents, pictures and multimedia even if there is a missing disk in the array, or if the file system is missing or damaged.

Try it now. You can download a full-featured trial version of DiskInternals Raid Recovery for free.

RAID degraded

HDDs, Optical Drives and RAID
HDDs, Optical Drives and RAID
degraded RAID 1
Remember that a 2TB drive will give about 1.6TB of usable space after formatting.
This article explains how to setup a RAID 1.
Windows XP recovery console /p c:" 
For everything since, its "chkdsk /f  C:"
The problem can be two fold:
1. the meta data (sits in a hidden area on the drive) has been removed that identifies it as a member of that raid.
2. possibly some data has been erased off the drive.
In the first case, a raid recovery application will be able to recover the data, in the second case, its going to be a lot more work and you will likely have lost a lot of data.
You can look around for some software to do the recovery (like http://www.diskinternals.com/raid-recovery/ although I am sure there are others, thats the only one I have played with) or you could send it off to professionals to recover (like Seagate or http://www.drivesaversdatarecovery.com/ not used the second one, but have heard some good stories about them) they are not cheap, but if you need your data and don't mind paying, they will get it. 

NVraid takes forever to rebuild, would be much faster to put in the 2 new drives, use something like acronis to duplicate the raid (don't resize it, better to do that in windows sevens drive manager).

To do the rebuild in the BIOS utility you'd probably have to delete the old array and redefine it - watch you don't use the "delete data" which will overwrite the MBR and render your disk empty; to recover from that BTW it's useful to have a floppy with BootitNG (www.bootitng.com) on it to undelete the MBR info. The nVidia BIOS utility is kinda dumb compared with, e.g. Promise' stuff, but if anything is wrong with an array's specs, i.e. it's "broken", you just have to start as if from scratch.
For the Windows software utility, it would surprise me if Gigabyte had deleted it from the nVidia driver pack - it is most definitely in there. At worst, you can DL the same driver set on the Gigabyte CD from nVidia's Archive site, unzip it manually with Winzip and look for the "raidtool" folder, under ...IDE\WinXP\ and copy it to your hard disk. I've seen no way to "install" the software - just run it from the folder; I think it's also necessary to run the .BAT file in the folder first to register the Wizard as a service... at least that worked for me. Then just run NvRaidMan.exe and you'll see how to proceed with a rebuild... which is BLOODY slow: about 12GB/hour and no tuning

forums.nvidia.com/index.php?showtopic=173620

Set the drive up without raid turned on, run the seagate Tools tests over it, if it gives you an error number write it down, if it finds bad sectors tell it to repair them (sometimes a lot of times), then if it passes test, its ok, if it still fails, check it for warranty 

Recovering from degraded raid 1
Failed Motherboard with raid1. How move to new Motherboard?
RAID 1 problems
Rather than a 3 drive raid5 (slow under NV raid) why not have a 2 drive stripe (for the speed) and use the 3rd drive externally as a backup? (windows backup works great for this btw)
forums.nvidia.com/index.php?showtopic=177090
You probably forgot to break the RAID before you tried to install Win7 onto the single WD hdd.
Do the following:

1. Boot into the RAID Utility (where you set the RAID array).
2. Break the RAID into 2 single non-RAID hdd's.
3. Enter the BIOS and set the SATA Controllers to "IDE Mode".
4. Shut down the PC and remove the old hdd.
5. Boot into the mainboard BIOS and make sure,
   1. that the DVD-ROM is the first and the HDD the secod bootable device and
   2. that the WD HDD is on top of the "HARD DISK BOOT PRIORITY" settings.
6. After having done that, you can boot off the Win7 DVD and install the OS onto your WD HDD.