![]() Subsequent to that, using the SysInternals WinObj utility, I can now trace the Object name right back to I hope I’ve made the relationships clear enough for you, and that the diagram makes sense.Īs you can see from what I’ve said above and the screenshots of Disk Manager and the diagram to the left, the Disk my “old system” resides in, is currently known as “Disc 0” to Windows 7. Then after you’ve unzipped it somewhere (and scanned for viruses I might add), run it as Administrator – you’ll need to otherwise you won’t have permission to see the data you’re looking for.ĭiagram starts from the middle, top half for one disc, bottom half for the other. It’s part of the SysInternals utilties at. Search google for “Windows 7 WinObj” and download it from whichever source you trust/ are comfortable with. What I need to do is to tell Virtualbox to look specifically for the target hard drive, no matter what Windows decides to do that morning as I boot my machine up, so, here’s how I did it… This is Not A Good Thing, because of the way Virtualbox Raw Disk Access needs to be configured, at the time of writing this article. A lot of googling and it turns out that Windows 7 does in fact change Disc number assignments, seemingly at random during each boot. “How Can This Be!?!?!?” was the next question asked. The new 500GB system disk has been designated as “Disc 1” and the old disk as “Disk 0” – argh! ![]() There we go… upon bootup, Windows 7 has enumerated the hard disks in my machine differently from when I first set up Virtualbox! ![]() It all worked great, until I booted into Win7, fired up VirtualBox and tried to start the “OldSystem” VM… On the old hard drive I had Windows XP and Ubuntu 11.04, and I wanted access mainly to the old Ubuntu Installation, in case there was information on there that I needed for the fresh OS installs, so that was attached to a spare SATA interface as well, and I had set up Virtualbox 4.1 on WIndows 7 with raw disk access, to boot straight up into the old Ubuntu installation at my leisure. I recently updated one of my systems to multiboot Windows 7 64-bit and Linux Mint 64-bit, on a spare 500GB hard drive. The tl dr is that Microsoft placed a hard limit of 4 drives/partitions, because Windows NT (!!) could theoretically only boot from a maximum of 4 partitions it can get reports back from a system’s BIOS. UPDATE, : I’ve had people coming back saying they can’t see some drives using this method.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |