It appears you previously Or currently have an OS on F: because it's marked as active and system. The first active partition is where windows installs bootmanager making it the system partition.Startup repair thinks that if it moves bootmanager it's going to hose the OS on F:. The above application will probably work DaveHC seems to know his stuff but unfortunately i can offer no instruction as to it's use if you post back dave may notice and be able to clarify or it may be self explanatory. If you can use Discmanager to unmark F: as active startup repair may then recognize the problem normally you would do this in the boot tab of msconfig but it knows there is no OS on F: so it's not listed. You basically have to lose the active and system marks on F: so startup repair will recognize a problem last resort prior to reinstall would be to backup F: and reformat F: (probably using linux live CD or some type of bootable partition manager) then you will be in a no boot situation that startup repair can repair it may take a couple of passes. Post back your results before you try the next technique as they do become more dangerous as we go.
Hi Mog,
Disconnecting the drive has the same effect - as you found out.
If you get the same problem when you reconnect the storage drive, swap them around.
Plug the lead from your 7 drive into the motherboard socket that the storage drive was originally in , and the Storage drive into the one 7 drive was originally in.
Great you got it working