.. and where did it come from in the first place?
Now, I was always under the impression that Windows Boot Manager was only really needed if you wanted to have the option of booting from any one of two OS's (such as Linux and Windows) on the same hard drive, which is not one of my requirements.
All I want to do is to run a single copy of 64 bit Windows 7 SP2 from an OCZ Vertex 2 SSD in a PC which also contains a Seagate 500 GB 'standard' hard drive, which will be used for data storage etc only.
These are currently connected to the two 6.0 Gb/s connectors on a new Asus Mazimus IV Gene-Z/GEN3 motherboard, together with an optical (blu-ray) drive.
This particular motherboard does, of course, feature one of these new clever UEFI BIOS's, which is probably part of the problem, as when I was setting up the system, I have somehow ended up with the first Boot Option Priority as Windows Boot Manager, which I never even installed in the first place.. and, so far as I am concerned, have no need for.
I think the first time I installed Windows 7 (with a different motherboard in place actually) I think I left the Seagate drive connected, as it wasn't even formatted or anything at that stage, but when I rebuilt the system, and wanted to reinstall Windows, it got itself in a bit of a mess.
I then disconnected the Seagate, and installed Windows on the SSD as the 'C' drive (clearing everything first) and then reconnected it, and played around with the drive letters so that the Seagate was drive 'D' and the optical drive 'E', which made more sense to me.
Anyway, as I say, I have somehow ended up with the stupid Windows Boot Manager priority, which, if I change it, stops the system from going into Windows at all.
I am quite happy to start again from scratch, as it were, but would really like to know what is going on here first.
Sorry about the long post, which I hope makes sense!
Now, I was always under the impression that Windows Boot Manager was only really needed if you wanted to have the option of booting from any one of two OS's (such as Linux and Windows) on the same hard drive, which is not one of my requirements.
All I want to do is to run a single copy of 64 bit Windows 7 SP2 from an OCZ Vertex 2 SSD in a PC which also contains a Seagate 500 GB 'standard' hard drive, which will be used for data storage etc only.
These are currently connected to the two 6.0 Gb/s connectors on a new Asus Mazimus IV Gene-Z/GEN3 motherboard, together with an optical (blu-ray) drive.
This particular motherboard does, of course, feature one of these new clever UEFI BIOS's, which is probably part of the problem, as when I was setting up the system, I have somehow ended up with the first Boot Option Priority as Windows Boot Manager, which I never even installed in the first place.. and, so far as I am concerned, have no need for.
I think the first time I installed Windows 7 (with a different motherboard in place actually) I think I left the Seagate drive connected, as it wasn't even formatted or anything at that stage, but when I rebuilt the system, and wanted to reinstall Windows, it got itself in a bit of a mess.
I then disconnected the Seagate, and installed Windows on the SSD as the 'C' drive (clearing everything first) and then reconnected it, and played around with the drive letters so that the Seagate was drive 'D' and the optical drive 'E', which made more sense to me.
Anyway, as I say, I have somehow ended up with the stupid Windows Boot Manager priority, which, if I change it, stops the system from going into Windows at all.
I am quite happy to start again from scratch, as it were, but would really like to know what is going on here first.
Sorry about the long post, which I hope makes sense!
