PDA

View Full Version : Vista repair;The ENIGMA that is Vista; The riddle or puzzle


Jimmy Carter
01-29-2008, 07:06 AM
Vista repair…The ENIGMA that is Vista; The riddle or puzzle if you will! !

Working from a Windows XP OS on a different hard drive on the same computer
I saved a 195 GB Vista OS from a different hard drive {320GB’s} on the same computer onto an external hard drive….

I than used partition magic and resized the 195 GB Vista OS to 55 GB’s.

I than erased the hard drive that had the 195 GB Vista OS and made the first partition 55 GB’s on the new erased hard drive. Since it was a 320 GB hard drive I made five other partitions….two primary and three logical.

I than used powerquest drive image 7.0 and copied {restored} the saved resized 55 GB Vista OS to the blank 55 GB partition on the hard drive.

I unplugged the other three hard drives on the PC and only left the 320 GB hard drive plugged in and booted the computer and it boot to BLACK SCREEN “HAL,dll” missing reinstall “HAL,dll”.
So I ran the boot magic floppy and set partition one as visible and it booted to “DISK READ ERROR”.

I than put the Vista DVD in the drive and booted and selected “R” for repair and it would not repair and booted to “DISK READ ERROR”.

I than connected a Windows XP hard drive and booted to it and opened partition magic and deleted the 55 GB partition containing the Vista OS.

I than unplugged the Windows XP hard drive and again booted to the deleted Vista OS and it booted to “MISSING OPERATING SYSTEM”.

I than put the Vista DVD in the drive and booted and selected “R” for repair and in a split second it repaired it and booted perfectly into the Vista operating system that used to be 195 GB’s but is now 55 GB’s…

When it loaded it ran disk check and corrected a bunch of stuff…

PS: The reason I even tried it is because I suspected it would work.

N5RDC
01-29-2008, 07:54 AM
I had more or less the same problem when changing partitions in Vista (not a dual-boot configuration), & after booting with Hiren's Boot CD & running some tests, I found that the problem was in the boot.ini pointing to the wrong partition after the changes were made. Editing boot.ini to point to the correct partition solved the problem.