Thanks again for all y'alls help with this problem. Since I'm not using the VM for games, I have the 3D acceleration uncheck marked should that be checked? I checked for an updated video driver, and there isn't work that Windows 7 found. So, I guess the question has changed from "How to get Windows 7" to work, to "Why did it fail, and how can one prevent a occurrence?Īnother question, if y'all don't mind, is how can the performance be improved? It has a Windows Experience Rating of 1, the lowest, because of the graphics. I fired up the VM this morning, and it worked. I chose to have it repair Windows It started to doing the repairs, and bombed out a few times, and finally started when it started, it installed a driver update for the processor, i5-7400, and said it needed to restart, which I did. At first, in got to the starting Windows splash screen, and aborted then it got to the point where it had a "text screen" saying "Windows didn't shut down properly do you want to repair Windows or start normally" (or some similar message, but that's the gist of it. Remember the definition of insanity being trying the same thing over and over expecting different results? Well, I went insane. This patch is strictly within the Windows 7 VM. Someone made a patch to bypass the CPU check for the updates to work, and that is what I installed and it worked with no problem, although that is now moot. In one of the updates, Microsoft put in something so that Windows 7 wouldn't update if it was installed on a "new" computer, i.e., one that "should" be running Windows 10 the objective was to not support unplanned hardware/software combinations. It's been over a year, so I don't remember the exact detail. Of course, you may still run into the usual issues surrounding any P2V conversion, such as hard disk driver issues and losing activation.Thanks for the response. There are tutorials on the Macrium website covering this conversion from a UEFI(GPT) disk to an MBR disk. One possible solution I can think of is to create a Macrium Reflect image of the original hard disk and then restore it into a Virtualbox VDI in MBR mode. Windows 7 guests are unable to boot with the Oracle VM VirtualBox EFI Mac OS X, Linux, and newer Windows guests are Note that the Oracle VM VirtualBox EFI support is experimental and will be enhanced asĮFI matures and becomes more widespread. The problem comes in that the the EFI implementation in Virtualbox is unable to boot Win 7. I can confirm that Windows 7 64 bit can indeed boot in EFI mode on real hardware (I've just checked it on a real PC), hence it's entirely possible that the original hard disk did boot Win 7 in EFI mode. to beat the 2TB size barrier, but was always a secondary or even removable drive. This drive was probably formatted using GPT for other reasons, e.g. I would not surprise me if the EFI and MS partitions are blank, like the partition names. ![]() ![]() In your case I am seeing the standard GUID values for EFI system partition and Microsoft private partition, but there are a couple of unexpected partitions before it.īasically, I stand by my assumption that this drive was never intended to be bootable, and cannot easily be made so. Partitions with attribute 0x0 should all be assigned drive letters, and that doesn't really make sense in your case. This would be the norm for boot manager and other hidden partitions. in Windows the partition will not be assigned a drive letter. 0x8000000000000000 means that the partition will not presented to the user, i.e. I assumed I must look up the GUID and display that name if I find a match, but in fact the partition name is encoded in the partition table itself - CloneVDI is simply reporting it verbatim.Īlso, I looked up the meaning of those partition attributes. I misremembered where those partition labels (e.g. You would need to understand how it ever booted in the past (if it ever did), and set up a similar apparatus in the VM.Įdit: p.s. However I don't believe this disk was ever bootable. If the disk was ever bootable then you could boot from a Win7 setup DVD and repair the boot info.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |