HP Drive Key Boot Utility for Windows 7 64 Bit 133: A Guide to Create Bootable USB Drives

You must have the built-in Diskpart.exe and Bootcfg.exe utilities to create bootable mirror volumes on GPT disks. You can do some of these steps with the Disk Management console, but others you can do only with the built-in Diskpart.exe utility.

hp drive key boot utility for windows 7 64 bit 133

DOWNLOAD: https://9riopermulmu.blogspot.com/?wc=2vzGW8

Before you set up boot volume mirroring, it is a good idea have another GPT disk in the computer that contains an Extensible Firmware Interface (EFI) partition. The EFI partition contains the system files used to boot the operating system. If the primary system drive (disk-0) fails, you can use the EFI partition on the shadow drive (disk-1) to boot. This step creates and prepares new EFI and Microsoft Reserved (MSR) partitions on the shadow drive. You can use only the Diskpart.exe utility to create the required EFI and MSR partitions. You cannot use the Disk Management console to create or mirror EFI or MSR partitions.

Before you start, make sure that you have another BASIC disk with all unallocated free space of equal or greater capacity than the primary disks system and boot partitions. If you already converted the spare drive to dynamic, revert it back to basic before you follow these steps.

Open a new command prompt, and then use the format utility to format the EFI partition (S:) with the FAT file system. You must do this so that you can copy the system files from the primary EFI partition to this new EFI partition. Do not format with NTFS. The system cannot boot from an EFI partition unless it is formatted with the FAT file system.

Press ALT+TAB again to return to the other command prompt. Use the xcopy command to copy the system files from the primary EFI partition (P:) to the Shadow EFI partition (S:). You must do this to make sure that the shadow drive can boot the system if disk-0 fails. Make sure that you use the correct drive letters if you used different letters for your EFI partitions.

Before you can establish a mirror, both the primary (source) drive (Disk-0) and the shadow (destination) drive (Disk-1) must be converted to Dynamic. After the disks are Dynamic (after a reboot), you can then establish the mirror. You can do this step with either the Disk Management console or the Diskpart.exe utility.

After both the primary (disk-0) and shadow (disk-1) drives are dynamic, you can then establish the mirror of the boot volume to the shadow drive. You can do this step with either the Disk management console or the Diskpart.exe utility.

Now that you have successfully established the boot mirror, a new boot entry was automatically added to NVRAM so that you can boot to the shadow drive. This new entry is displayed as Boot Mirror C: - secondary plex on the boot menu. If you select it, it will boot into the operating system on the shadow drive. However, if something were to happen to any of the system files or the EFI partition itself on disk-0 or if disk-0 failed completely, you would have to boot from the EFI partition on disk-1. Before this will work, you have to add boot entries into NVRAM with the Bootcfg.exe utility.

At a command prompt, run the Bootcfg.exe utility to display the current boot entries. You have one boot entry for the main operating system (boot entry id:1), and one boot entry for the Mirror (shadow) drive (boot entry id:5).

Before you can add the new entries for the EFI partition and boot partition on the shadow drive to NVRAM, you have to list the existing partitions on disk-0 so that you can extract partition GUID information about the current EFI partition. Use the bootcfg /list command against disk-0 to display all the partitions:

Now you have the SOURCE and TARGET EFI GUID values that you have to clone the boot entries in NVRAM. The new entries use the new EFI partition GUID on the shadow drive to boot the system if disk-0 fails in any way. Use the bootcfg /clone command to add new NVRAM boot entries with your source and target GUID values recorded in steps 2 and 3.

To see the new Cloned entries added to NVRAM, use the bootcfg command and notice you now have seven entries instead of five. The bottom two entries are the cloned entries and will use the EFI partition on the shadow drive (disk-1) to boot.

You must now use the following procedure to recover the original operating system (shadow) drive. These following steps show you the whole process. The process includes replacing the failed disk-0, re-installing Windows on the new replacement disk, which creates a new EFI system partition, and then adding new boot entries into NVRAM so that you can boot back into the original operating system on the shadow disk-1.

Shut down the computer, and then restart it. Select the boot menu item Original Shadow Drive to boot into the original operating system. This brings the server back into production. To fix the mirroring so that you can use the new disk-0 as your primary operating system drive and again be in a fault tolerant environment, continue with the following steps.

While booted into the shadow drive (disk-1), you must "remove" the broken mirror, and then delete the missing disk. You can do this with either the Disk Management console or the Diskpart.exe utility.

I am unable to boot with Start Smart 5.05, POST is not taking the disk. I have tried to boot with SBS 2003 its getting booted but the error shows" HDD is not detected". As per my knowledge, I was tried to update the driver with StartSmart CD. Its not getting booted.

• Replace C: with the letter of the drive where Windows XP is installedPress Enter

• You can also run the equivalent of bootrec found in Vista, 7, 8 for Windows XP, the bootcfg:bootcfg /rebuild

• Press Enter

• When done, type exit, press Enter and restart the computer

I managed to get a copy of Windows 8 on a USB drive. In order to boot from the USB, I got into the Bios (using F2) and tried to "Add boot option," as there were no other boot options present. When I tried to do that, it asked me to provide a name. I entered "USB". It then added it & allowed me to edit properties of this option. When I tried to edit the property, it asked for File system path. Because this is a USB drive, I do not have a clue as to what this value should be & how to set this USB drive as the first priority.

Step 2) Choice your way to fix this because there is 2 ways to fix this: Install Windows To Go on Flash drive and boot it from PC\Laptop second way is use two flash drives one where is installation second flash drive is need to use for place OS like Windows 10,8,7,Vista,XP Linux, iOS etc.

Step 3) If you choose version Windows To Go you need only one flash where to install it before it you need to get Software called Rufus at site: -2...., after download it run and it will show drive to install choose your and select disc icon after that browse your selected ISO installation if it has Windows To Go Rufus will automatically show this option if it has, like almost all ISO downloaded from Microsoft, msdsn.microsoft.com etc. it will take long hours but you will get OS installation on any Flash drive where is enough free space, reboot PC\laptop make sure USB flash drive is in first BOOT UP place set by BIOS. All OS is on your flash without any BOOT option straight by Rufus

Step 4) If you choose version 2 flash drive version you need 1 flash with OS installation files like Windows 7 and 1 flash drive where to install it, you can use similar software Rufus to write in flash OS installation without checking Windows To Go version in Rufus this is fastest way to install OS. When it`s start up Windows boot from flash installation you just need to choose drive like new 1 flash drive it will 100% install to it if you select it in installation time when installation is started.

Step 5) Check Disk formation - if you ask about File system installation than you need to use program called Command prompt or CMD you must run as administrator this by making shortcut on Desktop by right mouse click on desktop->new->shortcut and locate your CMD like C:\windows\system32\cmd.exe, now on new made shortcut right click->properties->Shortcut tab->Advance->check Run as administrator->Ok->Ok now you have CMD with administrator rights. Now just open new shortcut->type diskpart-> hit enter-type list disk->hit enter->type select disk(your flash drive watch who it is like:1 now command to type looks like: select disk 1-> hit enter->list partition->select partition 1->Delete partition->create partition primary->Now go to my computer open Flash drive it will ask Format drive click on it, but remember files larger than 4GB need NTFS file system so use NTFS before formatting new flash drive->Click format. After formatting flash Drive in large file system like NTFS you can install most newest OS on your Flash drive if that`s you wished to know.

It was eventually determined that these size limitations could be overridden with a small program loaded at startup from a hard drive's boot sector. Some hard drive manufacturers, such as Western Digital, started including these override utilities with large hard drives to help overcome these problems. However, if the computer was booted in some other manner without loading the special utility, the invalid BIOS settings would be used and the drive could either be inaccessible or appear to the operating system to be damaged.

ATAPI devices with removable media, other than CD and DVD drives, are classified as ARMD (ATAPI Removable Media Device) and can appear as either a super-floppy (non-partitioned media) or a hard drive (partitioned media) to the operating system. These can be supported as bootable devices by a BIOS complying with the ATAPI Removable Media Device BIOS Specification,[45] originally developed by Compaq Computer Corporation and Phoenix Technologies. It specifies provisions in the BIOS of a personal computer to allow the computer to be bootstrapped from devices such as Zip drives, Jaz drives, SuperDisk (LS-120) drives, and similar devices.

These devices have removable media like floppy disk drives, but capacities more commensurate with hard drives, and programming requirements unlike either. Due to limitations in the floppy controller interface most of these devices were ATAPI devices, connected to one of the host computer's ATA interfaces, similarly to a hard drive or CD-ROM device. However, existing BIOS standards did not support these devices. An ARMD-compliant BIOS allows these devices to be booted from and used under the operating system without requiring device-specific code in the OS. 2ff7e9595c