edit registry w/o Win 7?

seekermeister said:

I only read a few of the first posts of the thread, so I don't know how germane it is, but I recently had a problem very similar to this...did you use Paragon Partition Manager? If so, in the future use something else. My boot hung at the login screen also, until I disconnected drive 0 (non-OS). I think that PPM was also involved in the failure of that drive, when I later attempted to delete a raw partition at the front of that drive.

Like I said, I only scanned the thread, but I think that you said that Drive 0 is your OS drive, and if that is the case, I'm not sure what happened, but it must have to do with MBR, or MFT corruption.

I've just given him the procedure to make the other drives inactive.

Hopefully, this will solve the problem.

If not then its time to run Startup Repair three times.

but must wait and see. More than once he has charged ahead. Maybe this will be a lesson.

The Disk Part does not see the 1Tb SAT disk. I restarted a couple times with same results.
Only the Disk 0 is shown, the single partition that now is the C: drive

Please boot from the System Repair Disc.

I just restarted again into the System Repair disk. The only disk that shows after
List Disk
is Disk 0, the 76GB disk that now has C:

This is what I did earlier. I did not make myself clear. After seeing this, I restarted from the Win 7 Installation disk with the same results.

I appreciate your expertise and the time and effort you have put into trying to help me with this. I understand you are frustrated. Me too. If you are ready to wash your hands of this project, I understand.

Boot into the Bios.

Choose to use Default settings.

Boot again into bios.

Does your bios show drives connected?

If you do not know how to boot into your bios, let me know.

Excellent.

Now carry out the aforementioned procedure so that C and only C has an active partition.

DiskPart only lists the single 80Gg now C:

I've never known DiskPart to not see a drive when run from the System Repair Disc.

Are you running diskpart from X: which is the ram drive created by the System Repair Disc?

Unless I get smarter, the only thing I can suggest right now is to disconnect one of the other two drives and see if diskpart sees more than your C. After that then swap which one is disconnected and see if diskpart sees more than C.

If at anytime Diskpart sees more than just C, mark that other drive as inactive.


I have gotten smarter, but first let me know the results from this attempt.

ran DiskPart from
x:\windows\system32>diskpart
Restarting with new drive configuration