Ok it boots up normally and shows the BIOS loading screen
then turns blank
I tried using the F12 boot menu and tried booting from the hard disk drive C: Nothing is happening
tried the primary master drive
it keeps sying "hit F1 to retry Reboot" and i do and it doesnt reboot, Normal boot doesnt work either
Alright, I'm no expert with Windows systems but I'd say that it's either an issue with the bootloader or some of the required boot files are missing. I'm doubtful of the latter as normally that should give a more in-depth error message and with the former it's more likely to simply do nothing.
Regardless of what the issue is, access to the BIOS alone won't be enough, although it's good to see that you can at least boot to BIOS. We're gonna need to boot from a CD/DVD or even USB for this. The course of action depends on if you have a windows recovery disk or not. These days most people don't, meaning that in order to access your files, your harddrive, etc and see what the issue is we're gonna either have to rely on a Linux LiveCD or one of those unofficial Window LiveCDs like
BartPE. Regardless of which choice you choose, I'd advise that you have someone local who's fairly computer-literate so we can see what the actual problem is and use either of the Live Environements to fix it.
Oh and in case you need some explanations of the above, the order of things from boot tends to go like this: Power on -> BIOS -> Master Boot Record (MBR, where the Bootloader is stored) -> Bootloader loads kernel and rest of OS.
With a LiveCD (or LiveUSB or even DVD) you adjust the BIOS options to boot from CD/DVD or USB and it goes: Power on -> BIOS -> CD -> Load data from CD into RAM and read additional data from CD when needed. This way we get an environement we can work with without messing about with the hard drive. LiveCDs are slow (CDs have much slower read speeds than hard drives) and most can't save data from the session. Most can access the drive though and let you look through the files and run programs included on the LiveCD to either continue doing normal tasks or try to recover things.
As I say though, this is where things get murky though and you really need someone there to be able to see things. I'd probably suggest going with something like BartPE as it was made for recovering windows so I'd imagine you'd have more luck with that. I'm afraid I can't help you anymore than that without having physical access to the machine. Sorry.