![]() ![]() Why in the world does there need to be a partition on the target drive at the time that the build OS starts for Ghost32 to produce a workable recovered disk? I reboot the system back into WinPE (source still receives drive C: as it is the only formatted partition)Įverything works as intended, sysprep runs and desktop comes up. I enter Diskpart and create a primary partition on disk 0 that is 10MB in size, unformated RAW and not ACTIVE. I run ghost32.exe as above and restore the disk from image over the newly created partition. I enter Diskpart and create a primary partition on disk 0 (Tried both RAW and formatted as NTFS on two different attempts). Once restored the newly created partition will receive a later letter (E: in this instance, the Cd-Rom drive receives D: ).īooted back into WinPE I enter Diskpart and reassign the drive letter of the source drive from C: to W: and exit Diskpart. When the target drive is blank the source drive receives the C: drive letter within WinPE. I boot into WinPE and CLEAN disk 0, then reboot again. (thinking that it may have something to do with the drive letter assignment within WinPE and changes that Ghost32 may make to the restored disk) If I reboot into WinPE and restore again at this point it will work, essentially the same as scenario 1 only it was working before hand. I run ghost32.exe as above and restore the disk from image. Run Diskpart, select disk 0 and CLEAN it. I then run ghost32.exe and navigate to local disk from image and select my image, targeting disk 0Įverything works as planned system boots sysprep runs we're good to go. (Leaving this step out will produce the same results) I run Diskpart, select the disk (0) and CLEAN it. (Target drive has a working bootable primary ntfs Windows XP partition on it taking up the entire drive.) (In each of these the boot media for WinPE is a Usb drive (which loads WinPE in RAM X:) and the target hard drive is a 74Gb internal SATA)Įdit: I thought that Diskpart may be the problem and retried these using Gdisk32 to complete the disk operations with no change to the outcome. ![]() I'll detail below the scenarios I've tried so far in hopes someone sees something I've missed. It appears that any time the target drive is completely blank after restoration and reboot I am stuck with an endlessly blinking cursor in the top left corner.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |