What annoys you?

How many thousands of boot repairs do we need to do before badged members who help in these threads pick up the basic steps?

When the System flag - which signifies where the boot files have been placed - is on a data partition it has been incorrectly derailed there during install or repairs, likely because it was the first partition marked Active. The installer or Startup Repair will (re)write the System boot files to the first Active partition.

To correct this, mark the Win7 partition (or it's System Reserved partition if it is present) Active in Disk Mgmt or using Diskpart: Partition - Mark as Active

Then to write the System boot files to the Active partition run Startup Repair - Run 3 Separate Times until Win7 starts and holds the System Active flags.

If it will not mark Active it is likely a Logical partition which needs conversion to Primary first using Partition Wizard CD. PW also has a cool new feature on Disk tab to Rebuild MBR which may preclude the need to run Repairs x3.

If it will not repair it may have corruption requiring leaving it the way it is (wrong) or reinstall.

writhziden said:

JaidynM said:

writhziden said:

Should I be annoyed that I have done 18 out of the last 20 analyses in the crashes and debugging forum?

Before anyone takes that personally, I want to say that I have the utmost respect for everyone who helps in that forum. Just venting a little...

Sorry about that.

But it seems that I'm rarely online when the waves of Crashes and Debugging posts come. I live in Australia which means I'm quite a few hours ahead of America. A fair amount of Windows 7 users are American so if any American users post BSOD threads then I'll most likely be asleep (or busy). I might also note that Jan (JMH) is Aussie too but she's usually up late so it might not affect her as much as me.

I do try and post where I can though. :)

No problem. As I said, I was just looking to vent a little. I wasn't really mad at anyone; I was feeling the pressure of helping for so many hours straight. I appreciate all the work you do and understand the time difference. I imagine there are times when you still get quite a few threads from that part of the world or from night owls in the US.

Thanks for caring. Also, thank you for all you do to help on these forums. :)

Mike

You get used to the long hours and not knowing if they are fixed or not.

zigzag3143 said:

writhziden said:

JaidynM said:

Sorry about that.

But it seems that I'm rarely online when the waves of Crashes and Debugging posts come. I live in Australia which means I'm quite a few hours ahead of America. A fair amount of Windows 7 users are American so if any American users post BSOD threads then I'll most likely be asleep (or busy). I might also note that Jan (JMH) is Aussie too but she's usually up late so it might not affect her as much as me.

I do try and post where I can though. :)

No problem. As I said, I was just looking to vent a little. I wasn't really mad at anyone; I was feeling the pressure of helping for so many hours straight. I appreciate all the work you do and understand the time difference. I imagine there are times when you still get quite a few threads from that part of the world or from night owls in the US.

Thanks for caring. Also, thank you for all you do to help on these forums. :)

Mike

You get used to the long hours and not knowing if they are fixed or not.

Voluntary work at any Forum is just that.
We CHOOSE to do what we do.{ and one has to accept the consequences}

No prob. What's important is that these fundamentals are remembered to help others.

I have to disagree that running system repair x3 is the only or best solution to a boot problem. I have had occasion where it got it's knickers in a knot and eventually (after a long time) came back with a "cannot repair this computer". If you know you want to fix boot files then I recommend the "bootrec" sequence first and when it works as it generally does, it's a very quick process.