heeelppp !!! my pc wont boot after usin 7 boot loader
Posted 08 February 2012 - 04:37 PM
help me , what i gotta do .. i even tried to fix the prblm with my win7 dvd but in vain (((
Posted 08 February 2012 - 04:56 PM
What you say doesn't make sense, if no grldr then how can you type chainloader command???
Posted 08 February 2012 - 06:24 PM
i entred these commands n i got this
Root (hd0,0) ------> filesystem type is ntfs , partition type 0x27
find --set-root /bootmgr ---------> (hd0,0)
geometry(hd0,0) ----------> drive 0x80 (lba) : c/h/s= 1024/255/63, sector count /size =625141760/512
partition num 0 active, filesystem type is ntfs, partition type 0x27
partition num 1 filesystem type is ntfs, partition type 0x7
partition num 2 filesystem type is ntfs, partition type 0x7
geometry(hd0,0) --------> partition type for (hd0,0) is 0x27
then i type boot but i get a message that says "kernel must be loaded"
so i type tchainloader /bootmgr ------> will boot ntldr from drive=0x80 , partition=0x0 (hidden sectors=0x800)
n then i can boot ..
but when i reboot again i get the First message "failure to boot"
Posted 08 February 2012 - 06:41 PM
title boot to HDD
find --set-root /bootmgr
Posted 08 February 2012 - 07:13 PM
Posted 08 February 2012 - 07:32 PM
Posted 08 February 2012 - 07:34 PM
shady_alaa, you already found out how - whatever is your actual condition - when the PC boots *somehow* the root is established to (hd0,0) (active partition) so, when "chainloader /bootmgr" is entered the PC boots allright.
... when i write "chainloader /bootmgr" it boots normally !!!!! ((((((((((((((((((
So, once the good advice by steve6375 has been tested you will be in a condition when you will be prompted by grub4dos to "boot to HDD".
In order for the suggested menu.lst to work, it must be in the same partition where grldr is.
Boot to grub4dos prompt and issue these commands:<p>
most probably you will get as feedback "(hd0,0)".
find --set-root /grldr
This represents the first partition on the hard disk that from what you already posted should be the small (100 or 200 Mb) Windows 7 "boot" partition.
This is not normally mounted, so you should:
- boot manually with "chainloader /bootmgr", then open Disk Management and assign a drive letter to the first partition.
On normal Windows 7 machine the C: drive letter is assigned to second partition, whilst it is very likely that your BOOTMGR and bootBCD (as well as grldr) are on the first partition (as said not normally mounted/assigned a drive letter).
Then, next steps will be finding out HOW exactly grub4dos is loaded then re-set the machine so that BOOTMGR is loaded directly.
There are three main possibilities:
- BIOS->standard MBR->grub4dos PBR of active partition (invoking grldr)->grldr
- BIOS->standard MBR->Standard PBR of active partition (invoking *something else*)->*something else*->grldr
IF this is the case, you can run MBRFIX:
MbrFix /drive 0 fixmbr /win7
BEFORE attempting the above, it would be advised to inspect the MBR and PBR of first partition to check their contents.
How familiar are you with Hex/disk editors?
Can you run one (like TIny Hexer) and access sector 0 of physical drive 1?
Or can you issue this command (at grub4dos prompt):
cat --hex --skip=288 --length=222 (hd0)+1
and describe what you can read?
Posted 08 February 2012 - 07:39 PM
Posted 08 February 2012 - 07:42 PM
use diskpart if you don't know the letter of the boot partition:
sel disk 0
detail disk (here you can see the letter of the boot partition)
bootsect /nt60 x: /force /mbr
where x: is the letter of the boot partition.
Posted 08 February 2012 - 08:01 PM
does BCDBOOT replace the MBR?
yes, do this at same time as BCDBoot to replace MBR.
or it simply restore the boot files?
anyway I don't think the problem is in the boot files.
Seems shady_alaa used a tool that writes a not standard NT 6x mbr in the order to call a loader tha IT IS NOT the bootmgr
Posted 08 February 2012 - 09:03 PM
Posted 09 February 2012 - 08:59 AM
thank u veryy much guys !!
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users