This is from dictation.
One more time, I'll try to give a clear and concise answer to the original question.
The short answer is, no you can't do what you want.
The long answer is: yes, it could be done and has been done with a lot of effort and some additional hardware the old mediated to finish the task.
Here are the assumptions I make in providing this response.
The poster has an older motherboard that was made a few years ago and does not have the firmware needed to support booting the 64-bit version of Windows on a GPT disk drive. My assumption is that the 0P has a 32-bit version of Windows and wishes to put it on the GPT drive, even though his B IOS does not have the firmware support needed. Furthermore, the 0P does not wish to add another MBR drive to act as the boot loader for Windows.
There are solutions that have been presented on the Internet on different forms. And yes, it is possible to have the drive as a GPT and have Windows 32-bit Windows 7 installed on it. However, it requires some additional hardware. One of the options available is to modify the existing firmware in such a way as to provide some type of extension that will allow the system to boot from the GPT drive. This is not the kind of thing that is supported by Microsoft. This is the kind of thing that is done by experimenters who have experience with both Windows and Linux. Linux has pointed bit of flexibility about how you boot it and make it run. It has been that way for many years.
The position that Microsoft takes is that you should have a modern motherboard and you should be using a 64-bit version of Windows. Never expect Microsoft to change this position. Only a small group of individuals would benefit from some kind of change Microsoft might make or could make to their Windows operating system. Therefore, the alternative is to do some kind of thing that is often called a hack. In this context hack means something that is bizarre or unusual or breaks the general rules.
Your standard B IOS wants to boot from a device that has something like an MBR or is either an optical drive or a USB stick.
One solution is to make the GPT drive a highbred drive that has a very small MBR loader on it and the rest of the drive is GPT. This is called a hack because it is bizarre and not supported by anybody. The people who do this are independent experimenters who did it just because they wanted to show that it could be done.
A less radical approach is to have some kind of boot device inside the system that will start up the boot loader and then switch over to the GPT drive. One candidate would be a Solid-State Drive with about maybe 32 gigabytes of space. You would start up the system in that configuration and then later work it over so that most of Windows would be actually residing on the GPT drive. Another possibility would be to get a USB stick and eventually mounted somewhere inside the case of the computer and have it connected to one of the USB ports. The system would start from the USB drive and then a special loader would transfer over to the GPT key drive to load the rest of Windows. Again, this is not supported by Microsoft and has been documented by independent experimenters who have posted their results on the Internet and you can find it if you look for. But do not expect to find it in any of the mainstream forms. Like I said, it is considered a hack and is not considered to be something that the average future would attempt to do.
This is somewhat akin to the problem that commercial server operators have had when using RAID array. It is just not practical to try to boot the operating system from
RAID array. So then, the commercial operator will try to create some kind of highbred boot scheme to give the operating system the advantage of the speed of the array. Again, it is not something that most people would want to attempt because there is no support from Microsoft or anybody else as far as I know. And yes, I could be wrong. Maybe there is somebody somewhere that actually offers commercials support for a highbred system that starts out acting like an MBR and then switches over to something else during the boot up process.
I have carefully researched this material to the best of my ability, and I believe that the comments that made above are representative of the state-of-the-art at this time.
As mentioned, there is little modification for Microsoft or others to try to solve this problem for you because the problem can be solved simply by getting a new motherboard. The cost of a new motherboard would be much less than even the minimum wage you have to pay for a technician or engineer to figure this out for you.
This may sound like sarcasm, but that is not my intent. I'm trying to be as frank and concise as possible. Frankly, you are trying to do something that is probably beyond your abilities. As for myself, I don't know if I can do it. I do know that I would not be motivated to do it if I could just go out and buy new motherboard and solve the problem. If I did, I would probably sell the old motherboard or maybe give it to a school as a gift.
Again, no disrespect is intended here. I think you're trying to do something that is beyond a reasonable effort.
This was done from dictation, and has not been thoroughly proofread. Please understand that I have some limitations that don't allow me to spend a lot of time proofreading things like this.
End of dictation.
